On Sat, Oct 11, 2008 at 06:11, Douglas St.Clair wrote: > The point is that if Open Office wants to allow the production of high > quality typeset pages then they need to support all the glyphs and that would > mean properly supporting ligatures, diacritical marks, etc and supporting > them means more than simply printing them. It means minimally the spell > checker needs to recognize words with those glyphs embedded in them.
+1 >Is it planned to become more like PageMaker or stay more like Word? Considering that an RFE that would enable OOo to create documents in some writing systems was rejected because "OOo is not, and never will be allowed to become a Desktop publishing program", I think one can say that it is doomed to copy MSO, and the limitations that it has --- until it has been forked, and both Sun and Novell have been thrown to the Lion's Den. > should it handle large documents even sets of volumes with all the cross > referencing and indexing tools such a project requires? >> Automatic ligatures are not what the average keyboard user desires. > Automatic ligatures are nice but how would you implement them? This points to another failure of the ODF specification --- the inability for a document to specify the writing system that is used. I won't write my rant about that myopic failure here. > I think they're pretty and that's that! <grin> >> For many situations ie databases, unicode recommend againsts ligature use[4]. > The problem I expect is that if you use the code for the glyph instead of > recognizing the ligature for example and displaying the glyph for the letter > pair then data entry might get screwed up with some entries having the > ligature and others having the letter pair. That "problem" exists only when the programmer doesn't consider what writing system the database uses. > If Open Office were to fully support ligatures both automatically as well as > manually then if you consider the flexibility of Type 1 fonts you can see > that special rather complex glyphs can be constructed locally which could > save a lot of time for people at their computer just like the ligatures did > for the typesetter. +1 That failure is one reason why Huna can't be correctly written using OOo. :( xan jonathon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
