Le mercredi 23 juillet 2008 à 13:49 -0400, Behdad Esfahbod a écrit : > > > > 4. Unfortunately, Java and OO.o have lots of problems with OpenType > > > > CFF fonts > > > > http://fedoraproject.org/wiki/Known_fonts_and_text_bugs > > > > (please comment and vote on the relevant issues to put some pressure > > > > on upstream) > > > > So shipping only OTF versions is likely not to go well with OO.o users > > > > > > Then lets fix OO.o and Java (we have a Free java now). Don't hold back > > > the OTF transition. There's a reason that OTF is backward compatible. > > > > > Or do you mean "OpenType CFF" when you say OTF? > > > > In my mail OTF = OpenType CCF, TTF = OpenType TTF > > > > OO.o does not support the first one at all. > > http://qa.openoffice.org/issues/show_bug.cgi?id=78858 > > http://qa.openoffice.org/issues/show_bug.cgi?id=43029 > > > > It supports the second one badly. > > http://qa.openoffice.org/issues/show_bug.cgi?id=78749 > > http://qa.openoffice.org/issues/show_bug.cgi?id=16032 > > http://qa.openoffice.org/issues/show_bug.cgi?id=79878 > > > > Maybe if you complain to the OO.o guys they'll start to do something > > about it. They've certainly not exhibited a lot of enthusiasm so far. > > Yeah, lets do that. It's much more promising now that they are porting > to cairo. Unfortunately I don't think they port their printing code any > time soon, but when they do, all fonts will be supported. (It just > happens that cairo is so lucky to have someone called Adrian Johnson who > implements support for all and every font types in the PDF backend... > Makes all other projects envious) I fear the cairo port is at least a year away http://qa.openoffice.org/issues/show_bug.cgi?id=88613 So it's not a solution to our next releases > > I really do not like it either. But I don't see how to keep both TTF and > > OTF users happy otherwise. > > If we want to install both, just put them side by side I guess with no > split packaging, and lets patch fontconfig if needed, to make it decide > deterministically. Can you patch fontconfig so apps get OTF (OpenType CFF) versions by default, unless they explicitely request OpenType TTF files? (when the same version of the same font is available in both formats) That would simplify the problem to just having OO.o use the second mode till it fixes its bugs (plus probably just hide any CFF font to apps using the second mode) I must admit my main motivation for split packaging was avoiding the QA hell of some users getting TTF in OO.o, others getting OTF, having OO.o fail, and open bug reports. -- Nicolas Mailhot
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
_______________________________________________ Fontconfig mailing list Fontconfig@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/fontconfig
