Hey,
First time here, didn't see a similar post about this topic:
I'm having difficulties creating a Hebrew font (No Latin characters at all) - While it seems to work just fine on Macs, PC users experience a warning notice: "Missing Glyph Protection had occurred. The new font could not be applied to all selected text. Please use Ctrl+Alt to override".
Then, when using Pro Graphic programmes - Our Hebrew font simply cannot be used with PC (crossed squares appear instead of the font).
It seems that Office needs at least some latin in the font to recognize it. It needs more than A-z, The letters from the Codepage 1252 can do the trick - However, is there is a way to build a hebrew only font?
I'm using Glyphs BTW.
Thanks alot!
Gil Givoni
0
Comments
That's what we've been doing - and there are no problems with Mac Users, but all of our PC users experience the same problem (X-ed squares instead of characters).
Goerg (Glyphs developer) was the one that brought me to attention that Office needs Latin in order to recognise the font - and perhaps there is a similar problem with other graphic apps and programs on PCs.
I was wondering if this problem occurs with other non-Latin languages and what were the walk-arounds used.
g
Could you copy in a minimal set of glyphs from an open-source font?
It seems that Windows-1252 (or CP-1252) is the "minimum" required for it to work.
But it doesn't explain why Adobe programs (namely InDesign) don't recognise the font and display the X-ed squares.
Thoughts or ideas?
Cheers, Si
I found a nice little bug? about makeOTF in the process. If you have a font that contains /ecircumflex, makeOTF will set the bit for CP1252.
If you set the CP1252 bit in the OS/2 table, the font family name in the font menu is rendered with boxes and no hebrew shows up but you can apply the font and see the glyphs from the font. So the only "problem" with this setting is the preview in the font menu (Bullet list work fine, only the paragraph sign is required, otherwise you get a notdef).
I tested this in Office 2003 so this might be fixed already in newer versions.