Re: [Freefont-bugs] New glyphs are unixxxx while other glyphs are uniXXXX.

[Steve White]

Hello, Tae Wong,

If I understand you correctly, you are referring to the *names* of
glyphs in the font, as
opposed to their encoding.

It is true that sometimes uppercase hex digits are used and sometimes lowercase.
That could be considered aesthetically displeasing, but usually I
don't regard any
reasonable name for a glyph as a *bug* -- our policy is that glyphs in
a Unicode font
must be referred to *only* by their Unicode encoding, and that the
name is *only* for
human consumption.

I'm not familiar with SC UniPad, and you didn't say quite what effect
you are seeing with it.
If it uses glyph names to refer to glyphs in the font, I would call
that a bug with that software.

If you could give us a test case so we could see for ourselves, it
would be clearer
what is going on.

Let us know!

On Fri, Jun 21, 2013 at 3:22 PM, Tae Wong <address@hidden> wrote:
> New glyphs are unixxxx while other glyphs are uniXXXX.
>
> For example, in FreeSerif Regular, the glyph 0x1D29 is named uni1d29
> and not uni1D29.
>
> This is because the maintainer created some glyphs that use the
> unixxxx part. SC UniPad is not updated and does not use Unicode 6.0.
>