There are different ways to represent the individual codes (known as Unicode transformation formats or UTF, and Glyphs uses the hexadecimal UTF-16 convention. Unicode is a table that maps codes to symbols and a bunch of metadata. Something like a huge table for all characters of all scripts, essentially everything you could possibly ever want to enter as a part of a text anywhere. So, to cut a long story short, we need a way to keep track of everything. Plus hundreds and thousands of symbols, figures, punctuation signs et cetera et cetera et cetera. Then, there’s much, much, much more than just the Latin script. First, we have all sorts of diacritics, special letters, (almost) everything in both upper- and lowercase. Over the centuries, the alphabet has become more complicated than the regular a to z. So, to sum up, a glyph is a picture, either of a character, or of many characters or as a part in other glyphs.
You can, for instance, use separate glyphs for your serifs. Sometimes, a glyph only serves as a part for other glyphs. If ‘eight-bit’ does not tell you anything, please erase everything you read within these parentheses from your memory immediately, keep calm and continue reading.)
Choke symbol glyphs code#
f_f can have the U+FB00 LATIN SMALL LIGATURE FF code point.
(Well, actually, some ligatures do have legacy codes, but solely for backwards compatibility with outdated encodings from the long-gone, dark ages of eight-bit computing. Ligatures do not have Unicodes, because the separate characters already have codes and the the fact that it’s a ligature does not change the meaning of its parts. It represents three f characters in a row. A glyph can also represent more than one character at once.
0 kommentar(er)
