Apache OpenOffice (AOO) Bugzilla – Issue 93913
Open Type fonts handling in German version of OOO3.0RC1
Last modified: 2008-11-05 20:09:53 UTC
Open Type font families, for example MetaCondOT, are not recognised as single fonts. In font menues, only the font family name is visible. Single fonts cannot be assigned. Files with correctly assigned fonts appear OK on screen, but fonts are distorted when printed. No problem on Windows and on english version of OOO3.0RC1. Greeings, Christoph Maurer
Problem persists on 3.0RC2, german, as well as on 3.0RC2, french. No problem on 3.0RC3, english, no problem on Windows. --- Problembeschrieb auf deutsch: OpenType-Schriften mit PostScript outline, z.B. MetaCondOT von FontFont, werden in der deutschen Version nur als Familie im Schriftenmenü angezeigt. Die einzelnen Schnitte lassen sich nicht auswählen. Wird ein odt-File geöffnet, das die Schriften bereits korrekt zugewiesen enthält, ist die Darstellung zwar richtig, der Ausdruck jedoch unbrauchbar. Eine Zuweisung der Schnitte ist allerdings auch hier nicht möglich. Wird das gleiche Dokument auf dem gleichen Rechner in der englischen Version von OOo geöffnet, ist alles korrekt. Der Fehler ist nicht dokumentspezifisch. Der Fehler war in ersten Developer-Releases von OOo3 auch in der englischen Version noch vorhanden, wurde aber schon vor Monaten korrigiert. Die deutsche Version (wie übrigens auch die französische und ev. andere Sprachversionen) zeigen den Fehler weiterhin. OOo unter Windows geht auch in der deutschen Version richtig mit der (fileidentischen) Schrift um.
Error still exists on german version of OOo 3.0RC3. Please, have a look at it as this a killer criteria. I don't really understand how you manage to get different behaviours in original and in localised versions. Greetings, Christoph Maurer
could you please attach a sample document to this issue & the results of "Export to PDF" once with the english version that works, and once with the localized version? I guess it is not possible to provide a sample font that exhibits the problem A wild guess would be to delete the user-config directory (but basically cannot help, since both english and localized versions would use the same directory).. As a problem with OOo (the software, and not related to the german-lang project), and only occurs on mac (Windows is fine) → reassigning to porting
Created attachment 56930 [details] Font menu showing MetaCondOT in german localised version
Created attachment 56931 [details] Font menu showing MetaCondOT in original version
I just added 2 screenshots, one from OOO300m8 english, one from OOO300m8 german, both from the same computer and same user profile. For additional files and information on the font please visit http://idisk.mac.com/cmaurer-Public?view=web within the next few days. BTW: The PDF-files have not been created by exporting to PDF but by printing to PDF as OOo still does not support embedding .otf fonts within PDF files (might be addressed in 3.1 according to other issue reports)
Just an add-on to the comments above: There seem to be still some issues in the english version as well. Adobe Caslon Pro for example will only show "Adobe Caslon Pro" and "Adobe Caslon Pro Bold" in font menus. Available are Regular, Italic, Semibold, SemiboldItalic, Bold, BoldItalic. Setting Regular to bold within OOo will show and print Adobe Caslon Pro Bold. Setting Adobe Caslon Pro Bold to bold won't change anything. Adobe Arno Pro will work fine with all of its many subfonts. Adobe Minion Pro will work fine as well, even Semibold. Adobe Myriad Pro will show up everything with exception of Semibold. All of them came with Adobe CS3, AFAIK. All those fonts just show their font family names in german version of OOo. (Tested on Mac 10.5.5 only)
Most of the problems described looked like they have the same root cause as issue 93913. reassigning to me.
Hi hdu, please correct the link - it points to this issue itself. Now that OOo 3.0 final is available, I have to note that the error is still there - the german version does not show the fonts the same way as the english one. So I am not sure if this is only a general problem with the handling of OpenType fonts; there seem to be some code inside the localised versions that differs from the original one. Or have you got any other explanation for this really strange behaviour?
Indeed. The correct link should have been issue 93778. *** This issue has been marked as a duplicate of 93778 ***
close the duplicate