Semantic elements
Properties are displayed in the following order:alias
= corrected name. Obsolete. Now tracked with a separate database, but remains for Unicode 1.0 names.
*bc
= bidi (bidirectional) category , R etc*bm
= bidi mirrored or Y*cc
= combining class osition of diacritic*decomposition
type or gc
= general category etter, symbol, digit, punctuation, case behaviour, etc.*nv
= numeric type and value f a digit If numeric type is 'decimal', all 3 slots are filled. If 'digit', the first will be null. (This has been discontinued.) If 'numeric', then the first two will be null and only the last will be used.
The property between alias
and upper case
is obsolete and is now null for all Unicode characters.
Name and alias
A Unicode character is assigned a unique ''Name'' (na). The name is composed of uppercase letters A–Z, digits 0–9,Unicode 1.0 names
In version 2.0 of Unicode, many names were changed. From then on the rule "a name will never change" came into effect, including the strict (normative) use of alias names. Disused Unicode 1.0 names were moved to the property Alias, to provide backward compatibility. For example, has the Unicode 1.0 name "LATIN SMALL LETTER BABY GAMMA".Character name alias
Starting from Unicode 2.0, the published name for a code point will never change. Therefore, in the event of a character name being misspelled or if the character name is completely wrong or seriously misleading, a formal ''Character Name Alias'' may be assigned to the character, and this alias may be used by applications instead of the actual defective character name. For example, has the character name alias "" in order to mitigate the misspelling of "bracket" as in the actual character name; has the character name alias because, contrary to the character name, it does not have a fixed syllabic value. In addition to character name aliases which are corrections to defective character names, some characters are assigned aliases which are alternative names or abbreviations. Five types of character name aliases are defined in the Unicode Standard: * Correction: corrections for misspelled or seriously incorrect character names; * Control: ISO 6429 names for C0 and C1 control functions (which are not assigned character names in the Unicode Standard); * Alternate: alternative names for some format characters (only which has the alias ); * Figment: Documented labels for some C1 control code functions which are not actual names in any standard; * Abbreviation: Abbreviations or acronyms for control codes, format characters, spaces, and variation selectors. All formal character name aliases follow the rules for permissible character names, and are guaranteed to be unique within both the character name alias and the character name namespaces (for this reason, the ISO 6429 name "BELL" is not defined as an alias for because U+1F514 is named "BELL"; U+0007 instead has the alias "ALERT"). As of Unicode 16.0, 35 formal character name aliases are defined as corrections for defective character names. Apart from these normative names, ''informal names'' may be shown in the Unicode code charts. These are other commonly used names for a character, and do not have the same character restriction. These informal names are not guaranteed to be unique, and may be changed or removed in later versions of the standard.General Category
Each code point is assigned a value for General Category. This is one of the character properties that are also defined for unassigned code points and code points that are defined "not a character".Punctuation
Characters have separate properties to denote they are aWhitespace
Whitespace is a commonly used concept for a typographic effect. Basically it covers invisible characters that have a spacing effect in rendered text. It includes spaces, tabs, and new line formatting controls. In Unicode, such a character has the property setWSpace=yes
. In version , there are 25 whitespace characters.
Casing
The Case value is normative in Unicode. It pertains to those scripts with uppercase and lowercase letters. Case-difference occurs in Adlam, Armenian, Cherokee, Coptic, Cyrillic, Deseret, Garay, Glagolitic, Greek, Khutsuri and Mkhedruli Georgian, Latin, Medefaidrin, Old Hungarian, Osage, Vithkuqi and Warang Citi scripts. Different languages have different case mapping rules. In Turkish, corresponds to instead of . Similarly, when corresponds to instead of . In Nawdm, the letter Ĥ corresponds to ɦ in lowercase instead of the usual case mappings being Ĥĥ and Ɦɦ. In Greek, the letter sigma has different lowercase forms depending on where it is in a word. converts to if it is at the start or middle of a word, and converts to if it is at the end of a word. In Lithuanian, the dot in lowercase i and j is preserved when followed by accents. For example: Í in lowercase is i̇́. Despite the existence of , corresponds to "SS". Unicode encodes 31 titlecase characters. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *Other general characteristics
Ideographic, alphabetic, noncharacter.Combining class
Some common codes: :0 = spacing letter, symbol or modifier (e.g. , , ) :1 = overlay :6 = Han reading (CJK diacritic reading marks) :7 = nukta (diacritic nukta in Brahmic scripts) :8 = kana voicing marks :9 =Bidirectional writing
Six character properties pertain to bi-directional writing: ''Bidi_Class'', ''Bidi_Control'', ''Bidi_Mirrored'', ''Bidi_Mirroring_Glyph'', ''Bidi_Paired_Bracket'' and ''Bidi_Paired_Bracket_Type''. One of Unicode's major features is support of bi-directional (''Bidi'') text display right-to-left (R-to-L) and left-to-right (L-to-R). The Unicode Bidirectional Algorithm UAX9 describes the process of presenting text with altering script directions. For example, it enables a Hebrew quote in an English text. The ''Bidi_Character_Type'' marks a character's behaviour in directional writing. To override a direction, Unicode has defined special ''formatting control characters'' (''Bidi-Control'' characters). These characters can enforce a direction, and by definition only affect bi-directional writing. Each code point has a property called ''Bidi_Class''. It defines its behaviour in a bidirectional text as interpreted by the algorithm: In normal situations, the algorithm can determine the direction of a text by this character property. To control more complex Bidi situations, e.g. when an English text has a Hebrew quote, extra options are added to Unicode. 12 characters have the property : ALM, FSI, LRE, LRI, LRM, LRO, PDF, PDI, RLE, RLI, RLM and RLO as named in the table. These are invisible formatting control characters, only used by the algorithm and with no effect outside of bidirectional formatting. Despite the name, they are formatting characters, not control characters, and have General category ''Other, format (Cf)'' in the Unicode definition. Basically, the algorithm determines a sequence of characters with the same strong direction type (R-to-L ''or'' L-to-R), taking in account an overruling by the special Bidi-controls. Number strings (Weak types) are assigned a direction according to their strong environment, as are Neutral characters. Finally, the characters are displayed per a string's direction. Two character properties are relevant to determining a mirror image of a glyph in bidirectional text: indicates that the glyph should be mirrored when written R-to-L. The property can then point to the mirrored character. For example, parentheses , are mirrored this way. Shaping cursive scripts such as Arabic, and mirroring glyphs that have a direction, is not part of the algorithm.Numeric values and types
Decimal
Characters are classified with a ''Numeric type''. Characters such as fractions, subscripts, superscripts, Roman numerals, currency numerators, encircled numbers, and script-specific digits are type Numeric. They have a ''numeric value'' that can be decimal, including zero and negatives, or a vulgar fraction. If there is not such a value, as with most of the characters, the numeric type is "None". The characters that do have a numeric value are separated in three groups: Decimal (De), Digit (Di) and Numeric (Nu, i.e. all other). "Decimal" means the character is a straight decimal digit. Only characters that are part of a contiguous encoded range 0..9 have numeric type Decimal. Other digits, like superscripts, have numeric type Digit. All numeric characters like fractions and Roman numerals end up with the type "Numeric". The intended effect is that a simple parser can use these decimal numeric values, without being distracted by say a numeric superscript or a fraction. Eighty-three CJK Ideographs that represent a number, including those used for accounting, are typed Numeric. On the other hand, characters that could have a numeric value as a second meaning are still marked Numeric type ''None'', and have no numeric value. E.g. Latin letters can be used in paragraph numbering like "II.A.1.b", but the letters "I", "A" and "b" are not numeric (type ''None'') and have no numeric value.Hexadecimal digits
Block
A ''block'' is a uniquely named, contiguous range of code points. It is identified by its first and last code point. Blocks do not overlap, nor do they extend across planes. The number of code points in each block must be a multiple of 16. A block may contain code points that are reserved, not-assigned, etc. Each character that ''is'' assigned, has a single "block name" value from the 338 names assigned as of Unicode version . Unassigned code points outside of an existing block have the default value "No_block".Script
Each assigned character can have a single value for its "Script" property, signifying to which script it belongs. The value is a four-letter code in the range Aaaa-Zzzz, as available in ISO 15924, which is mapped to aNormalization properties
Decompositions, decomposition type, canonical combining class, composition exclusions, and more.Age
''Age'' is the version of the standard in which the code point was first designated. The version number is shortened to the numbering ''major.minor, although there more detailed version numbers are used: versions 4.0.0 and 4.0.1 both are named 4.0 as Age. Given the releases, Age can be from the range: 1.1, 2.0, 2.1, 3.0, 3.1, 3.2, 4.0, 4.1, 5.0, 5.1, 5.2, 6.0, 6.1, 6.2, 6.3, 7.0, 8.0, 9.0, 10.0, 11.0, 12.0, 12.1, 13.0, 14.0, 15.0, 15.1, and 16.0. The long values for Age begin in a V and use an underscore instead of a dot: V1_1, for example. Codepoints without a specifically assigned age value have the value "NA", with the long form "Unassigned".Deprecated
Once a character has been defined, it will not be removed or reassigned. However, a character may be deprecated, meaning its "use is strongly discouraged". As of Unicode version , the following fifteen characters are deprecated:Boundaries
The Unicode Standard specifies the following boundary-related properties: * Grapheme cluster * Word * Line * SentenceAlias name
Unicode can assign ''alias names'' to code points. These names are unique over all names (including regular ones), so they can be used as identifier. There are five possible reasons to add an alias: ;1. Abbreviation :Commonly occurring abbreviations or acronyms for control codes, format characters, spaces, and variation selectors. :For example, has alias . Sometimes presented in a box: . ;2. Control : ISO 6429 names for C0 and C1 control functions and similar commonly occurring names, are added as an alias to the character. :For example, has the alias . ;3. Correction :This is a correction for a "serious problem" in the primary character name, usually an error. :For example, is actually a ''lowercase'' p, and so is given alias name : "actually this has the form of a lowercase calligraphic p, despite its name, and through the alias the correct spelling is added." In descriptions, with preceding symbol ※. ;4. Alternate :A widely used alternate name for a character. :Example: has the alternate alias . ;5. Figment :Several documented labels for C1 control code points which were never actually approved in any standard ( figment meaning "feigned, in fiction"). :For example, has the figment alias . This name is an architectural concept from early drafts of ISO/IEC 10646-1, but it was never approved or standardized.External links
References