Benches Uncategorized

7

Font Book vs. Font Panel: Apple Support Communities

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I don't understand why Font Book shows a different font than Font Panel. An example would be Corsiva Hebrew which shows a pretty English font in Font Panel but in Font Book Corsiva Hebrew shows a font that may be Hebrew except for the numbers. I thought Font Panel and Font Book would show the same characters. I just would like to understand the difference please.

Shirley Allan

7 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Corsiva Hebrew does not have any Latin characters in it, which FontBook reflects. In Font Panel and other apps, other fonts substitute when you select a font that does not cover the range required for the text. So you are actually seeing a different font, Apple Chancery I think.

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yes, I would agree with you because it does look like Apple Chancery as I remember it but I have a new iMac and Apple Chancery does not show up in the Font Book or the Font Panel so how could it substitute?

    SJ Allan

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have a new iMac and Apple Chancery does not show up in the Font Book or the Font Panel so how could it substitute?

    You must have it somewhere, it is part of the standard install of 10.6 in Library/Fonts.

    http://www.prepressure.com/fonts/basics/snow-leopard-fonts/list

    Make sure you look at the very bottom of the font list in Font Panel.

  4. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yep, found Apple Chancery at the bottom of the list in Pages. It still doesn't make sense to me though. Why should we keep those that are unreadable in Font Book in English such as the afore mentioned Corsiva Hebrew and others such as Ayuthaya and Bagdad if they are unusable in Apple branded apps. and when chosen, use a substitute?

  5. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Why should we keep those that are unreadable in Font Book in English such as the afore mentioned Corsiva Hebrew and others such as Ayuthaya and Bagdad if they are unusable in Apple branded apps. and when chosen, use a substitute?

    These are all usable in Apple branded apps for reading and writing the languages they are designed for -- Hebrew, Thai, and Arabic. For writing you have to switch your keyboard layout from US to the one required for those languages in system prefs/language & text/input sources. Apple gets 40% of its revenues from outside the US, so this capability is important. That some fonts cannot be used to read/write English is irrelevant (Ayuthaya actually does include Latin).

  6. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    It can sometimes be hard to track the twists and turns of Apple's text composition engine, but it is trying to help.

    Basically when it has to render text on screen it sees if it can draw all the Unicode characters from the font that you have selected. If it can't then it looks for another font with the missing characters to complete the text.

    Where this works well is on a web page in Safari. You may have English/Latin text mixed up with Hebrew, Arabic, Chinese whatever. The system will find appropriate fonts for all of those.

    Better if you stick with fonts like Lucida Grande which have large character sets so the text looks more consistent, but there are very few (very large) fonts which have the super size character set that cover all languages (well almost).

    The alternative is to have one or 2 huge fonts or to patch together several fonts to do the job.

    You may have some older pre Unicode fonts on your system from other software installs which are fouling up the system, but Ayuthaya and Bagdad are not amongst them.

    Pages and TextEdit have problems though with right to left text. TextEdit is somewhat better but still bad enough to make it unusable IMHO. Whilst you can cut and paste right to left text and maintain its text direction it is impossible to insert non R to L text in the correct position.

    I just did it with some sample Arabic and Hebrew, picking a point immediately left of the punctuation at the end of a sentence in each case, then inserting left to right text. It will insert the text somewhere else.

    If I carefully add two spaces in RtoL text then insert my LtoR text inbetween those I get the same result.

    The closest I get is if I paste in 2 LtoR spaces between the RtoL text then paste my LtoR text between those. But then the punctuation is on the wrong side it is not where it should be for the Hebrew it is to the left of the English. Forget about inserting English expressions amidst the other Hebrew or Arabic text.

    That is how Apple ruined my foreign language DTP publishing when it introduced OSX.

    Peter

  7. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I just did it with some sample Arabic and Hebrew, picking a point immediately left of the punctuation at the end of a sentence in each case, then inserting left to right text. It will insert the text somewhere else.

    I think TextEdit may have improved in 10.6. I seem to be able to type RTL then LTR then RTL without having stuff go in the wrong place. If you have a chance to test it like you have described here, I'd be interested in your opinion.