Apache OpenOffice (AOO) Bugzilla – Issue 18963
diacritic symbols are printed in wrong font
Last modified: 2004-07-20 16:20:10 UTC
slackware 9, cups 1.1.19 when printing file with diacritic symbols in the text that has different font from bitstream vera serif they all are replaced by corresponding bitstream vera serif symbols (at least it seems to be that one font). this doesn't happen with ?(zh) and ?(sh). attached : testcase, try printing it. all diacritic symbols except ? and ? should be bigger, bolder and different-looking
Created attachment 8946 [details] file with diacritic symbols
TM->US: MRU mentioned, that you might have a look. Thanks !
additional testing : 1. added times new roman font, tried using it - results are the same (diacritic symbols replaced by corresponding symbols from bitstream vera sans (or serif, latvian diacritic symbols in them seem to be identic)). 2. added printer through spadmin, removed all font replacements. still all latvian diacritic symbols in times & tnr fonts are printed incorrectly (probably also other fonts have this problem) i hope it is ok to change component and version like this
I also have this. Diacritical characters (Polish) are printed in wrong font (always same) if the selected font for the text is TrueType. Type1 fonts do not show this behaviour. Gentoo, cups 1.1.19
Created attachment 11312 [details] Polish diacritical character test.
@submitter: I do not seem to catch the issue. The bugdoc you provided uses Times. Times on Linux is an XFont that can not be printed. Thus a printable font is searched for each glyph and uploaded to the printer. When selecting the TrueType fonts "Bitstream Vera Serif" or "Lucida Sans" (that one coming with the Sun j2re 1.4) in the wordprocessor, also these fonts are used for the printout. @AstralStorm: assuming you have installed all the fonts named in the bugdoc on your Linux host and use Xft/fontconfig these fonts currently are served to OOo by X. Thus I'd suggest to introduce these fonts to OOo with the spadmin tool. Then they should also be used for the printout. (Refer to issue 8144 for the utilization of fontconfig API.)
Yes, I do have all the fonts. I found TrueType ones in X11 font dirs, but at first I couldn't add any Type1 fonts. Then I realised that TrueType fonts had perms +r, u+w, while Type1 fonts had only +r. I 'fixed' that and OOo found them. Why it needed them, I don't know. Still, adding them to font list didn't fix printing problem. It worked with TrueType fonts.
hmm. 1. i've never quite understood all these font things - what does it mean that font can not be printed ? and why only diacritic sumbols are replaced ? 2. if it is impossible to resolve this then probably the problem is with interaction with user - real life scenario : user receives a document that uses times new roman font. this font is replaces by times. he takes a look, all is sort of fine, prints it. blah. something's wrong. i've heard such a complaints from many users so this could be called a common problem. maybe some warning should be produced - like "the document you are going to print contains non-printable font <name>, it may look different. originally used font was <name>. [print] [cancel]" - this way user would be saved from useless fiddling around with printer drivers, fonts, oo.org...
I'll try to explain this feature. When looking closely you'll experience that already on the screen the font has been altered to be able to display the requested characters, which are not provided in the font the user has chosen. This feature is called GlyphFallback and prevents unexperienced users who chose the wrong font from the annoying representation of 'open rectangles'. The same is true for the printout. But due to normally higher resolutions on printouts compared to the screen this effect can be seen more easily. Solution: select a capable font then it doesn't get altered.