Unicode Symbol Modifiers

[Bran Kom]

Hi! I'm wondering how the glif xml specification handles unicode symbol modifiers? http://www.fileformat.info/info/unicode/category/Sk/list.htm Is this already supported by the specification?

Thanks,
Brian

[Tal Leming]

Hm. This hasn't come up before and it isn't something that I'm familiar with. What kinds of things do XML specifications need to do to handle them?

Thanks,

Tal

--
You received this message because you are subscribed to the Google Groups "Unified Font Object Specification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ufo-spec+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Adam Twardoch (List)]

I don't think anything special is needed there, but actually, I'd like to ask how GLIF/UFO should store the encoding information for glyphs that represent Unicode Variation Sequences (UVS), which need to end up being written in a format 14 "cmap" subtable as per

https://www.microsoft.com/typography/otspec/cmap.htm

In effect, they are not nuch different from a ligature glyph, only that the "ligation" behavior is happening on the Unicode codepoint level, not the OpenType GSUB level. 

http://unifiedfontobject.org/versions/ufo3/glif.html 

allows multiple "unicode" elements when one glyph can be accessed via different codepoints, but suggests that only a single codepoint can be stored in the element. With UVS, however, it needs to be a sequence of codepoints. 

Best,

Adam

Sent from my mobile phone.

[Tal Leming]

Good question. Could you open an issue on GitHub?

https://github.com/unified-font-object/ufo-spec/issues

This will almost definitely require a spec change.

Thanks,

Tal

[Behdad Esfahbod]

On 15-12-01 06:39 PM, Adam Twardoch (List) wrote:
> I don't think anything special is needed there, but actually, I'd like to ask
> how GLIF/UFO should store the encoding information for glyphs that represent
> Unicode Variation Sequences (UVS), which need to end up being written in a
> format 14 "cmap" subtable as per
> https://www.microsoft.com/typography/otspec/cmap.htm
>
> In effect, they are not nuch different from a ligature glyph, only that the
> "ligation" behavior is happening on the Unicode codepoint level, not the
> OpenType GSUB level.
>
> http://unifiedfontobject.org/versions/ufo3/glif.html
> allows multiple "unicode" elements when one glyph can be accessed via
> different codepoints, but suggests that only a single codepoint can be stored
> in the element. With UVS, however, it needs to be a sequence of codepoints.

Allowing sequences in "unicode" element sounds about right to me.

b

> Best,
> Adam
>
> Sent from my mobile phone.
>
> On 02.12.2015, at 02:02, Tal Leming <t...@typesupply.com

> <mailto:t...@typesupply.com>> wrote:
>
>> Hm. This hasn't come up before and it isn't something that I'm familiar
>> with. What kinds of things do XML specifications need to do to handle them?
>>
>> Thanks,
>> Tal
>>
>>
>>> On Dec 1, 2015, at 7:59 PM, Bran Kom <briankim...@gmail.com

>>> <mailto:briankim...@gmail.com>> wrote:
>>>
>>> Hi! I'm wondering how the glif xml specification handles unicode symbol
>>> modifiers? http://www.fileformat.info/info/unicode/category/Sk/list.htm Is
>>> this already supported by the specification?
>>>
>>> Thanks,
>>> Brian
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Unified Font Object Specification" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to ufo-spec+u...@googlegroups.com

>>> <mailto:ufo-spec+u...@googlegroups.com>.

>>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Unified Font Object Specification" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to ufo-spec+u...@googlegroups.com

>> <mailto:ufo-spec+u...@googlegroups.com>.

>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Unified Font Object Specification" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ufo-spec+u...@googlegroups.com

> <mailto:ufo-spec+u...@googlegroups.com>.