Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Interesting Hoefler Text Ligature Bug in SL

http://discussions.apple.com/thread.jspa?threadID=2157605&tstart=100

iMac Intel/2C2D, eMac G4/700, Mac OS X (10.6), 10.5, 10.4, 10.3, 9.2

Posted on Sep 13, 2009 3:37 AM

Reply
51 replies

Sep 13, 2009 4:16 AM in response to Tom Gewecke

An attempt to address problems pointed out in the project white paper in the prereading archive and in parallel on this forum? Enabling imageable composition that is unsupported by character information in application-independent archives is inherently detrimental to information society.

Note that ability to draw typographic ligation without direct depiction onto character codes in a coded character set is the argument advanced again and again and again for the character-glyph model in conventional Modern English composition.

/hh

Sep 13, 2009 6:30 AM in response to Henrik Holmegaard

An attempt to address problems pointed out in the project white paper in the prereading archive and in parallel on this forum?


I doubt that the inability to type the word "afflict" using Hoefler Text could be considered an "attempt to address problems." Seems like a bug. Various other fonts that do ligatures including Minion Pro and Zapfino seem to work OK.

If I remember right, you are the only person among us who can see this "project white paper in the prereading archive", so there is no way to know exactly what you are referring to. If this is not the case, then the url would be useful.

Sep 13, 2009 7:22 AM in response to Tom Gewecke

Various other fonts that do ligatures including Minion Pro and Zapfino seem to work OK.


For clarification of this post so that previous unclarities in posts are prevented:

Output or rendering transform from chacters to glyphs composes correctly in authoring application when working with Adobe Minion Pro and Linotype Zapfino: Yes? No?

Input or referencing transform from glyphs to characters decomposes correctly in application-independent PDF 1.3 archive when working with Adobe Minion Pro and Linotype Zapfino: Yes? No?

/hh

Sep 13, 2009 8:13 AM in response to Henrik Holmegaard

Output or rendering transform from chacters to glyphs composes correctly in authoring application when working with Adobe Minion Pro and Linotype Zapfino: Yes? No?


Yes. There is no problem using Pages 09 in Snow leopard to type the sequence "ffli" with Minion Pro or Zapfino (or anything else I have tried). Trying to do so in Hoefler Text (or even just switching the font used for the sequence to that) crashes Pages. In TextEdit the sequence disappears.

From further testing it looks like the sequence can be typed in Hoefler Text in both apps if you turn off all ligatures in its typography pane, but they crash if you then select the text. Sometimes the crash messages refer to the SFWordProcessing plug-in.

As far as I can tell all other ligatures in Hoefler Text and other fonts work just fine.

Sep 13, 2009 11:01 AM in response to KOENIG Yvan

As Hoefler is able to make an existing document unreadable, I think that the problem is completely different than your "fly sodomization exercise"


To repeat, while the Latin, Cyrillic and Greek scripts are commonly called complex because more of the drawing is done in character space than in glyph space, the Indic scripts and Arabic are commonly called complex because more of the drawing is done in glyph space than in character space. Typographic ligation is simply the lithmus test of any implementation of the Unicode character-glyph model for the Latin script, that is, if typographic ligation does not function for the implementation then the implementation does not function. This is simple set theory for primary school, and for pensioned French potters -:).

/hh

Sep 13, 2009 11:06 AM in response to Henrik Holmegaard

Henrik Holmegaard wrote:

Why are you bringing such emphasis on the word "complex" which I didn't use in my message ?

If something was wrong in the general ligature treatment, we may assume that it would strike other fonts.

Here we have several different problems with a single font. I would be surprised to learn that there is a link between these problems and your favorite subject 😉

Yvan KOENIG (VALLAURIS, France) dimanche 13 septembre 2009 20:06:56

Sep 13, 2009 12:29 PM in response to KOENIG Yvan

Why are you bringing such emphasis on the word "complex" which I didn't use in my message?


Sigh, if you spent time studying technical specifications, which is a useful thing to spend time on when participating in a discussion forum on computing, you would be aware that the technical terms 'simple script' and 'complex script' refer to converting computerised communication into computerised composition when the mapping of characters to glyphs is linear and simple as opposed to when it is non-linear and complex.

/hh

Sep 13, 2009 12:44 PM in response to Henrik Holmegaard

I understand the meaning of complex but don't see the connection with the described problem.

I repeat, I would be surprised if Hoefler is using, for the embedded ligatures, a structure different of the one used in other fonts delivered by Apple.

For those who are bored by the Hoefler behavior under Snow, I put the 'old' version on my idisk.
<http://idisk.me.com/koenigyvan-Public?view=web>
Download
For_iWork:Hoefler Text.dfont.zip
compress the new one (version 6.1d6e1 2009/07/16) from the Finder menu
replace the font itself by the one which will be given after double clicking the downloaded file.

It will bring nothing to your theorical course but maybe it will give a usable workaround.

Yvan KOENIG (VALLAURIS, France) dimanche 13 septembre 2009 21:42:47

Oct 19, 2009 4:25 PM in response to KOENIG Yvan

The biggest problem I'm having with Hoefler Text under Snow Leopard isn't ligatures, but the extra leading that completely screws up all the layouts... it's like the line spacing is increased 200% or so. I've just downloaded the version you posted, but it doesn't solve this problem. Any other ideas as to workarounds? I've tried saving it as TT, OT, T1 with FontXChange, but without success. What else might I try?

Interesting Hoefler Text Ligature Bug in SL

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.