Unicode ranges in smart sets need to be decimal, not hex

RoboFont › Forums › Bugs › Unicode ranges in smart sets need to be decimal, not hex

Tagged: 

This topic contains 1 reply, has 2 voices, and was last updated by  frederik 6 years, 11 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • November 11, 2013 at 01:45 #5725

    Marcos Ojeda
    Member

    This is both something of a bug but also something of an undocumented detail of smart sets.

    The attached image shows a smart selection for a range in the PUA [0xF300, 0xF4FF], but in order to specify that range, you need to manually convert those unicode ranges back into base ten numbers. i understand that this is a fiddly issue, but it’s still a bit of a bug since each .glif ‘s unicode[hex] property is specified as a base16 number.

    hope this help others!

    Attachments:
    You must be logged in to view attached files.
    November 13, 2013 at 06:23 #5728

    frederik
    Keymaster

    Inside a glyph in UFO the unicode value is stored as decimal number. The search happens on that data. The value you see is just a representation of that value.

    Will see what I can do about that….

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

← Previous
Next →