Glyph Builder: uniXXXX glyph name doesn’t trigger unicode value

Reply to Glyph Builder: uniXXXX glyph name doesn’t trigger unicode value on Fri, 21 May 2021 08:40:08 GMT

martin — Fri, 21 May 2021 08:40:08 GMT

Hi,

When I generate glyphs with Glyph Builder those with uniXXXX names don't trigger a unicode value. (I have ticked the Auto Unicodes checkbox.)

uni1E83 = w + acute@top

This happens in RF 2007102200 as well as in the 4.0b 2104222316.

Reply to Glyph Builder: uniXXXX glyph name doesn’t trigger unicode value on Fri, 21 May 2021 13:05:25 GMT

roberto arista — Fri, 21 May 2021 13:05:25 GMT

Hi @martin,
thanks for your feedback, that's probably an issue with the extension. I'll open an issue on the github tool repository and report to the main headquarter :)

Reply to Glyph Builder: uniXXXX glyph name doesn’t trigger unicode value on Fri, 21 May 2021 13:15:49 GMT

roberto arista — Fri, 21 May 2021 13:15:49 GMT

meanwhile, you could get the unicodes in the glyph objects using a script like this

import re
pattern = re.compile('uni[0-9A-F]{4}')

for eachGlyph in CurrentFont():
    if pattern.match(eachGlyph.name) and eachGlyph.unicode is None:
        eachGlyph.unicode = int(eachGlyph.name[-4:], 16)

note: it adds the unicode value only if not assigned and it assumes that the letter component of the hexadecimal number (from the glyph name) is uppercase

Reply to Glyph Builder: uniXXXX glyph name doesn’t trigger unicode value on Fri, 21 May 2021 13:23:54 GMT

roberto arista — Fri, 21 May 2021 13:23:54 GMT

or you could express explicitly the unicode value, like this

uni1E93 = w + acute@top | 1E93

Reply to Glyph Builder: uniXXXX glyph name doesn’t trigger unicode value on Fri, 21 May 2021 19:46:06 GMT

frederik — Fri, 21 May 2021 19:46:06 GMT

moved to a github issue on GlyphConstruction: https://github.com/typemytype/GlyphConstruction/issues/56