<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with unicode]]></title><description><![CDATA[A list of topics that have been tagged with unicode]]></description><link>https://forum.robofont.com/tags/unicode</link><generator>RSS for Node</generator><lastBuildDate>Wed, 12 Aug 2026 02:23:50 GMT</lastBuildDate><atom:link href="https://forum.robofont.com/tags/unicode.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 24 Feb 2021 06:25:13 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[ [[qanda:topic_solved]] TTF &amp; OTF types next letter on keyboard instead of one being typed]]></title><description><![CDATA[Ran into this recently and wanted to add that I required a '.notdef' glyph, additionally, in order to export correctly as a ttf.
]]></description><link>https://forum.robofont.com/topic/899/ttf-otf-types-next-letter-on-keyboard-instead-of-one-being-typed</link><guid isPermaLink="true">https://forum.robofont.com/topic/899/ttf-otf-types-next-letter-on-keyboard-instead-of-one-being-typed</guid><dc:creator><![CDATA[shannpersand]]></dc:creator><pubDate>Wed, 24 Feb 2021 06:25:13 GMT</pubDate></item><item><title><![CDATA[ [[qanda:topic_unsolved]] Adding new glpys cause error]]></title><description><![CDATA[@gferreira Editing binary of U not solved the problem. This time it throws an error for u. After removing both Udieresis and udieresis characters it compiled successfuly.
How I solve my problem?
I created a new font file and move all glyps to the new font file then compile.
]]></description><link>https://forum.robofont.com/topic/706/adding-new-glpys-cause-error</link><guid isPermaLink="true">https://forum.robofont.com/topic/706/adding-new-glpys-cause-error</guid><dc:creator><![CDATA[cyb3rsalih]]></dc:creator><pubDate>Fri, 04 Oct 2019 19:03:10 GMT</pubDate></item><item><title><![CDATA[ [[qanda:topic_solved]] Non-standard unicode chars and execution from shell]]></title><description><![CDATA[Gustavo, thank you a lot!
It works!
]]></description><link>https://forum.robofont.com/topic/701/non-standard-unicode-chars-and-execution-from-shell</link><guid isPermaLink="true">https://forum.robofont.com/topic/701/non-standard-unicode-chars-and-execution-from-shell</guid><dc:creator><![CDATA[Max Ilinov]]></dc:creator><pubDate>Fri, 27 Sep 2019 16:38:22 GMT</pubDate></item><item><title><![CDATA[Find the unicode range name for a glyph (and other fun unicode things)]]></title><description><![CDATA[When you're building a large multiscript characterset it may be necessary to find out which unicode range a specific glyph belongs to. Sometimes you can guess from the glyphname, but that is not very reliable.
The glyphNameFormatter.reader module (built in RF, thanks!) has a couple of useful functions (full list here), particularly the Unicode To Range, or u2r can help.
glyphNameFormatter.reader has a couple of special dicts: uni2name maps all unicodes with a GNUFL entry to anames. Its keys will then be "all the unicodes we can do something with"
from glyphNameFormatter.reader import *

allUnis = list(uni2name.keys())

for v in allUnis[-200:]:
    print(hex(v), chr(v), u2r(v))

This will print something like this:
0x1f6e3 🛣 Transport and Map Symbols
0x1f6e4 🛤 Transport and Map Symbols
...
0x1f6f8 🛸 Transport and Map Symbols
0x1f6f9 🛹 Transport and Map Symbols

Suppose you want to find all the unicode values that belong to the Armenian range (for instance).
from glyphNameFormatter.reader import *

allUnis = list(uni2name.keys())

for v in allUnis:
    if u2r(v) == "Armenian":
        print(hex(v), chr(v), u2r(v))

Prints this:
0x531 Ա Armenian
...
0x58f ֏ Armenian

This is how you can get a list of all the supported range names:
from glyphNameFormatter.reader import *
print(rangeNames)

['Basic Latin', 'Latin-1 Supplement', 'Latin Extended-A', 'Latin Extended-B', 'IPA Extensions', 'Spacing Modifier Letters', 'Combining Diacritical Marks', 'Greek and Coptic', 'Cyrillic', 'Cyrillic Supplement', 'Armenian', 'Hebrew', 'Arabic', 'Arabic Supplement', 'Devanagari', 'Bengali', 'Gurmukhi', 'Gujarati', 'Oriya', 'Tamil', 'Telugu', 'Kannada', 'Malayalam', 'Sinhala', 'Thai', 'Tibetan', 'Hangul Jamo', 'Ethiopic', 'Cherokee', 'Runic', 'Mongolian', 'Vedic Extensions', 'Phonetic Extensions', 'Phonetic Extensions Supplement', 'Combining Diacritical Marks Supplement', 'Latin Extended Additional', 'Greek Extended', 'General Punctuation', 'Superscripts and Subscripts', 'Currency Symbols', 'Letterlike Symbols', 'Number Forms', 'Arrows', 'Mathematical Operators', 'Miscellaneous Technical', 'Control Pictures', 'Optical Character Recognition', 'Enclosed Alphanumerics', 'Box Drawing', 'Block Elements', 'Geometric Shapes', 'Miscellaneous Symbols', 'Dingbats', 'Miscellaneous Mathematical Symbols-A', 'Braille Patterns', 'Glagolitic', 'Latin Extended-C', 'Supplemental Punctuation', 'CJK Symbols and Punctuation', 'Hiragana', 'Katakana', 'Bopomofo', 'Hangul Compatibility Jamo', 'Enclosed CJK Letters and Months', 'CJK Compatibility', 'Latin Extended-D', 'Javanese', 'Latin Extended-E', 'Cherokee Supplement', 'Private Use Area', 'Alphabetic Presentation Forms', 'Arabic Presentation Forms-A', 'Vertical Forms', 'CJK Compatibility Forms', 'Small Form Variants', 'Arabic Presentation Forms-B', 'Halfwidth and Fullwidth Forms', 'Specials', 'Zanabazar Square', 'Domino Tiles', 'Playing Cards', 'Enclosed Alphanumeric Supplement', 'Miscellaneous Symbols and Pictographs', 'Emoticons', 'Transport and Map Symbols']

Finally, if you want to find out more about these really useful functions in glyphNameFormatter.reader have a look at the github repo
Thanks!
]]></description><link>https://forum.robofont.com/topic/659/find-the-unicode-range-name-for-a-glyph-and-other-fun-unicode-things</link><guid isPermaLink="true">https://forum.robofont.com/topic/659/find-the-unicode-range-name-for-a-glyph-and-other-fun-unicode-things</guid><dc:creator><![CDATA[erik]]></dc:creator><pubDate>Wed, 26 Jun 2019 16:20:09 GMT</pubDate></item><item><title><![CDATA[ [[qanda:topic_unsolved]] Glyph Construction&#x2F;Builder doesn&#x27;t automatically set unicode]]></title><description><![CDATA[@gferreira ah I understand. Thanks for the heads up, will give that a shot!
]]></description><link>https://forum.robofont.com/topic/640/glyph-construction-builder-doesn-t-automatically-set-unicode</link><guid isPermaLink="true">https://forum.robofont.com/topic/640/glyph-construction-builder-doesn-t-automatically-set-unicode</guid><dc:creator><![CDATA[youbringfire]]></dc:creator><pubDate>Tue, 14 May 2019 21:27:52 GMT</pubDate></item><item><title><![CDATA[ [[qanda:topic_solved]] Custom auto unicodes?]]></title><description><![CDATA[Thanks! That is the exactly what I was looking for
]]></description><link>https://forum.robofont.com/topic/595/custom-auto-unicodes</link><guid isPermaLink="true">https://forum.robofont.com/topic/595/custom-auto-unicodes</guid><dc:creator><![CDATA[RafaŁ Buchner]]></dc:creator><pubDate>Fri, 08 Mar 2019 12:11:02 GMT</pubDate></item><item><title><![CDATA[ [[qanda:topic_solved]] Copying uppercase to lowercase (including kerning), and auto-add unicodes]]></title><description><![CDATA[@tal said in Copying uppercase to lowercase (including kerning), and auto-add unicodes:

Here's a little demo script that will copy kerning.

Hmm, at least initially, when run, that causes an error:
File "lib/fontObjects/doodleKerning.pyc", line 13, in _set_dirty
mm4.MetricsMachineError: Glyph a is in more than one side 1 group.

For now, I'll do some (partially) manual things in MetricsMachine to sort out kerning. I'll loop back with a suggested fix if I can loop back and figure something out!
]]></description><link>https://forum.robofont.com/topic/591/copying-uppercase-to-lowercase-including-kerning-and-auto-add-unicodes</link><guid isPermaLink="true">https://forum.robofont.com/topic/591/copying-uppercase-to-lowercase-including-kerning-and-auto-add-unicodes</guid><dc:creator><![CDATA[StephenNixon]]></dc:creator><pubDate>Sat, 02 Mar 2019 15:23:09 GMT</pubDate></item><item><title><![CDATA[𝕮𝖔𝖓𝖛𝖊𝖗𝖙 𝖙𝖊𝖝𝖙 𝖙𝖔 𝖘𝖎𝖑𝖑𝖞 𝖀𝖓𝖎𝖈𝖔𝖉𝖊 𝖒𝖆𝖙𝖍]]></title><description><![CDATA[😄 This was excellent to find as the top post today.
RoboFont forum titles might be my favorite usage of this.
I wonder if that would wreck the SEO, though ...
]]></description><link>https://forum.robofont.com/topic/590/topic</link><guid isPermaLink="true">https://forum.robofont.com/topic/590/topic</guid><dc:creator><![CDATA[StephenNixon]]></dc:creator><pubDate>Thu, 28 Feb 2019 19:14:09 GMT</pubDate></item><item><title><![CDATA[GlyphBrowser with Unicode 11]]></title><description><![CDATA[
New names
Drag and drop UFO / ttf / otf to the names list to extract unicodes.
Available from Mechanic2 and GitHub

]]></description><link>https://forum.robofont.com/topic/548/glyphbrowser-with-unicode-11</link><guid isPermaLink="true">https://forum.robofont.com/topic/548/glyphbrowser-with-unicode-11</guid><dc:creator><![CDATA[erik]]></dc:creator><pubDate>Wed, 05 Dec 2018 08:51:48 GMT</pubDate></item><item><title><![CDATA[ [[qanda:topic_unsolved]] Set placeholder character for glyph?]]></title><description><![CDATA[mmm, see Character Set Preferences
There is a default font and a fallback when there is no unicode. I guess its up to the user to pick a font that contains the glyph.unicode, if a unicode is not in the selected font, the system fallback font is used to draw the template glyph.
]]></description><link>https://forum.robofont.com/topic/525/set-placeholder-character-for-glyph</link><guid isPermaLink="true">https://forum.robofont.com/topic/525/set-placeholder-character-for-glyph</guid><dc:creator><![CDATA[frederik]]></dc:creator><pubDate>Tue, 23 Oct 2018 17:18:21 GMT</pubDate></item><item><title><![CDATA[ [[qanda:topic_solved]] Unicode Category of Glyph]]></title><description><![CDATA[@benedikt
FWIW, the glyphNameFormatter in RF has a couple of functions that might be useful. It uses the glyphNamesToUnicodeAndCategories.txt names list which is buried somewhere in RF. This is not the full unicode list (I think CJ and K is not included), but it contains a lot of good stuff.
import glyphNameFormatter.reader
name = "flyingSaucer"
value = 0x1F6F8

# unicode to name
print(glyphNameFormatter.reader.u2n(value))
&gt; "flyingSaucer"

# name to unicode
print(glyphNameFormatter.reader.n2u(name))
&gt; 128760

# unicode to category
print(glyphNameFormatter.reader.u2c(value))
&gt; "So"

# name to category
print(glyphNameFormatter.reader.n2c(name))
&gt; "So"

]]></description><link>https://forum.robofont.com/topic/522/unicode-category-of-glyph</link><guid isPermaLink="true">https://forum.robofont.com/topic/522/unicode-category-of-glyph</guid><dc:creator><![CDATA[erik]]></dc:creator><pubDate>Tue, 23 Oct 2018 09:57:41 GMT</pubDate></item><item><title><![CDATA[ [[qanda:topic_solved]] Add unicode codepoint to newly added glyph.ss01 …]]></title><description><![CDATA[Dear Frederik,
thank you for your answer!

Why would an alternate version get a unicode value?
It’s not allowed to provide two glyphs with the same unicode value. Thinking from a typesetting point of view: which one should it take?

I see, so … there’s no problem here, but it’s actually right that the alternates named e.g. A.alt or A.ss01 don’t have the same unicode value as A itself … thank you for clarifying this.

I would recommend you to write an OpenType feature to switch the A to the alternate A.ss01 in InDesign:

I see! So it seems I’ll try to read the Robofont page on features and the documentation from Adobe and then I can hopefully figure out what to write in that feature file as now it’s completely empty.
I mean, maybe this feature files needs to have lines like the following:
 # Script and language coverage
 languagesystem DFLT dflt;
 languagesystem latn dflt;

And afterwards I could manually add what you proposed for A–Z and 0–9 in ss01, ss02, and ss03.
feature ss01 {
    sub A by A.ss01;
    # ...
} ss01;

I saw something like A.alt in some free and open source .ufo files and was wondering what it is, i.e. why would I write .alt instead of some styleset like .ss01 …
EDIT:
I just discovered an article about opentype features on i love typography dot com which lists features like aalt “All alternates“, calt “Contextual alternates“, salt “Stylistic alternates”, et cetera (which I already know from CSS).
So I think for another stylistic version of the figures 0–9, salt would be a kinda semantically correct feature name.
]]></description><link>https://forum.robofont.com/topic/520/add-unicode-codepoint-to-newly-added-glyph-ss01</link><guid isPermaLink="true">https://forum.robofont.com/topic/520/add-unicode-codepoint-to-newly-added-glyph-ss01</guid><dc:creator><![CDATA[fooness]]></dc:creator><pubDate>Fri, 12 Oct 2018 12:37:32 GMT</pubDate></item><item><title><![CDATA[ [[qanda:topic_solved]] Can&#x27;t update robofont]]></title><description><![CDATA[There are some non-ascii characters in your fea file. You can remove the non-ascii by right-clicking the UFO file and choosing Show Package Contents; open the feature.fea file in a code editor and remove the second line. I hope this makes sense. Or wait until the update is posted.
This issue is fixed and will be present in the next update.
for your reference: https://github.com/typesupply/ufo2fdk/commit/a792785fb6bd146215d8af8f7a74fbdcad19138b
]]></description><link>https://forum.robofont.com/topic/507/can-t-update-robofont</link><guid isPermaLink="true">https://forum.robofont.com/topic/507/can-t-update-robofont</guid><dc:creator><![CDATA[frederik]]></dc:creator><pubDate>Tue, 04 Sep 2018 12:37:04 GMT</pubDate></item><item><title><![CDATA[ [[qanda:topic_solved]] Space Center is mixing suffixes and not responding to suffix changes.]]></title><description><![CDATA[Awesome, thanks for the added clarifications and advice, @gferreira and @frederik!
]]></description><link>https://forum.robofont.com/topic/472/space-center-is-mixing-suffixes-and-not-responding-to-suffix-changes</link><guid isPermaLink="true">https://forum.robofont.com/topic/472/space-center-is-mixing-suffixes-and-not-responding-to-suffix-changes</guid><dc:creator><![CDATA[StephenNixon]]></dc:creator><pubDate>Fri, 11 May 2018 12:16:44 GMT</pubDate></item><item><title><![CDATA[ [[qanda:topic_solved]] Strings into Names]]></title><description><![CDATA[@gferreira
Thanks!
Works perfectly!
]]></description><link>https://forum.robofont.com/topic/447/strings-into-names</link><guid isPermaLink="true">https://forum.robofont.com/topic/447/strings-into-names</guid><dc:creator><![CDATA[RafaŁ Buchner]]></dc:creator><pubDate>Sun, 21 Jan 2018 18:36:14 GMT</pubDate></item><item><title><![CDATA[ [[qanda:topic_solved]] [1.6] Crash when template glyphs with unicode &gt; 0xffff should be displayed]]></title><description><![CDATA[This is already solved in the upcoming release
even support for emoji as a template preview :)
]]></description><link>https://forum.robofont.com/topic/346/1-6-crash-when-template-glyphs-with-unicode-0xffff-should-be-displayed</link><guid isPermaLink="true">https://forum.robofont.com/topic/346/1-6-crash-when-template-glyphs-with-unicode-0xffff-should-be-displayed</guid><dc:creator><![CDATA[frederik]]></dc:creator><pubDate>Thu, 25 Feb 2016 22:01:21 GMT</pubDate></item><item><title><![CDATA[ [[qanda:topic_solved]] Multiple Unicode]]></title><description><![CDATA[Perfect! Thank you, that's exactly what I was looking for.
]]></description><link>https://forum.robofont.com/topic/302/multiple-unicode</link><guid isPermaLink="true">https://forum.robofont.com/topic/302/multiple-unicode</guid><dc:creator><![CDATA[fortress]]></dc:creator><pubDate>Wed, 12 Mar 2014 18:18:55 GMT</pubDate></item><item><title><![CDATA[How to access&#x2F;create a dictionary mapping unicode values to glyphnames?]]></title><description><![CDATA[many thanks joanca : )
this is spot on what I needed
best
david
]]></description><link>https://forum.robofont.com/topic/276/how-to-access-create-a-dictionary-mapping-unicode-values-to-glyphnames</link><guid isPermaLink="true">https://forum.robofont.com/topic/276/how-to-access-create-a-dictionary-mapping-unicode-values-to-glyphnames</guid><dc:creator><![CDATA[david_demainlalune]]></dc:creator><pubDate>Thu, 08 Aug 2013 20:33:12 GMT</pubDate></item><item><title><![CDATA[Spaces show the undefined glyph when installed on a PC]]></title><description><![CDATA[check the unicode of your "space" glyph!
]]></description><link>https://forum.robofont.com/topic/272/spaces-show-the-undefined-glyph-when-installed-on-a-pc</link><guid isPermaLink="true">https://forum.robofont.com/topic/272/spaces-show-the-undefined-glyph-when-installed-on-a-pc</guid><dc:creator><![CDATA[frederik]]></dc:creator><pubDate>Tue, 23 Jul 2013 20:43:33 GMT</pubDate></item><item><title><![CDATA[Error on generating .otf: UnicodeDecodeError]]></title><description><![CDATA[euhm, does the path where you generate the file to contains anything out of an ascii range?
(first thing that pops up in my head)
If not, you can send me the UFO file, if you can.
thanks
]]></description><link>https://forum.robofont.com/topic/270/error-on-generating-otf-unicodedecodeerror</link><guid isPermaLink="true">https://forum.robofont.com/topic/270/error-on-generating-otf-unicodedecodeerror</guid><dc:creator><![CDATA[frederik]]></dc:creator><pubDate>Tue, 16 Jul 2013 07:16:54 GMT</pubDate></item></channel></rss>