Hello, Is the character code for “wasla-ar” in Unicode FBC2?
If this is the case, why does NiceName lack a code or does Unicode characters lack a category and NiceName?
The nice name is wasla-ar. Do you mean the production name?
There’s a tutorial called Unicode that explains the details.
I think the issue Hojat is asking about is that wasla-ar has no Unicode value in GlyphData.xml, so when you add it as a new glyph to a font, the new glyph has no Unicode value. The production value is default, so it ends up as just waslaar in the exported font.
The same appears to be true (for whatever reason) of most/all the non-spacing Arabic marks, as far as I can see from a quick glance. You have to manually add the Unicode values to the glyphs or use a custom GlyphData.xml file to be able to input these marks by their Unicode values in the exported font.
1 Like
The glyph “wasla-ar” is meant to be used as a component in glyphs that contain a wasla, e.g. alefWasla-ar (0671). The unicode FBC2 is for a “standalone”, spacing wasla (symbol). The difference is kind of like with the latin legacy and combining marks (e.g. acute vs acutecomb).
So if you need a glyph that is accessible by Unicode FBC2, you need an extra glyphs (e.g. with the name “waslaSymbol-ar”).