x

brockfrench's picture

x

riccard0's picture

y ;-)

paul d hunt's picture

z,pdq!

agisaak's picture

QED

André Isaak, PhD, TLA, esq. SPQR

hrant's picture

տ

We're talking about the body height of lowercase letters, right?

hhp

agisaak's picture

We're talking about the body height of lowercase letters, right?

No, left.

André

hrant's picture

But what about Mongolian?

hhp

brockfrench's picture

Solve for x:

Theunis de Jong's picture

x = NaN

Platform 3, encoding 1, language 1 is MS Windows, Unicode, English (from memory :-) and does not support encoding beyond the basic UC plane -- it maxes out just before U+FFFF. If these two characters are the only ones in this font, there is nothing to put into this encoding. Hence the error.

I understand it's recommended to always have a regular space in your font; perhaps that's all to make yours valid. (At least it won't take up excessive space. (g))

brockfrench's picture

Perfect. Thanks so much Theunis.

The faces I've made in the past have been quite simple; plunking in characters from illustrator, and playing with metrics. I'm trying to dive into additional features in earnest, and this is the first time I've had to add a range to my uranges.dat and created an alt character within this newly created range... so I tried it straight away, just in case...

I'm building two distinct typefaces of ~200 'display' emoticons, one is an outline, and the other is a filled form / tonal layer. Every character in each of the two faces is to have a stylistic alt. I'll be substituting Aa-Zz, 0-9 with similar nonsense, some are irrationally complex, so I promise the faces will be bloated by the time I'm finished.

Is there anything I can add to further optimize my Open Type code?

Thanks again!

Syndicate content Syndicate content