Apache OpenOffice (AOO) Bugzilla – Issue 22529
Charater spacing wrong at large sizes for some fonts
Last modified: 2004-04-23 14:40:54 UTC
When using some fonts at large size the characters are spaced much too close such that they overlap. Bookman is used in my example but other are similarly affected, eg, Avant Garde, Palatino, Zapf Chancery. Attachments coming up...
Created attachment 11328 [details] OOo document
Created attachment 11329 [details] Screen grab of OOo
Created attachment 11330 [details] Output file
I cannot reproduce in win xp, OOo 1.1 so It maybe solaris problem. I will attach the screenshot
Created attachment 11357 [details] OK on win xp, OOo 1.1, but problem on solaris
> I cannot reproduce in win xp, OOo 1.1 So what? Had you considered reproducing the conditions that I reported as causing the problem? PLEASE, PLEASE, investigate these issues properly. > so It maybe solaris problem. I know it is a Solaris problem, why do you think I pointed it out first time around only to have you say "maybe"? Stop wasting time.
reassigned to hdu hi hdu, this is a duplicate of that Issue we talked about last week, at the moment I just don't know the Issue number....
The problem seems to be that the only Bookman font available for the display is not scalable and is available only in a very few selected bitmap sizes. Please attach the results of the command xlsfonts | grep -i bookman to this issue, so we can check if this explanation makes sense.
$ xlsfonts | grep -i bookman -itc-bookman-demi-i-normal--0-0-0-0-p-0-iso8859-1 -itc-bookman-demi-r-normal--0-0-0-0-p-0-iso8859-1 -itc-bookman-light-i-normal--0-0-0-0-p-0-iso8859-1 -itc-bookman-light-r-normal--0-0-0-0-p-0-iso8859-1 -urw-itc bookman-demi-i-normal--0-0-0-0-p-0-iso8859-1 -urw-itc bookman-demi-i-normal--0-0-72-72-p-0-iso8859-1 -urw-itc bookman-demi-i-normal--10-100-72-72-p-61-iso8859-1 -urw-itc bookman-demi-i-normal--12-120-72-72-p-72-iso8859-1 -urw-itc bookman-demi-i-normal--14-140-72-72-p-85-iso8859-1 -urw-itc bookman-demi-i-normal--6-60-72-72-p-36-iso8859-1 -urw-itc bookman-demi-i-normal--8-80-72-72-p-48-iso8859-1 -urw-itc bookman-demi-r-normal--0-0-0-0-p-0-iso8859-1 -urw-itc bookman-demi-r-normal--0-0-72-72-p-0-iso8859-1 -urw-itc bookman-demi-r-normal--10-100-72-72-p-60-iso8859-1 -urw-itc bookman-demi-r-normal--12-120-72-72-p-73-iso8859-1 -urw-itc bookman-demi-r-normal--14-140-72-72-p-84-iso8859-1 -urw-itc bookman-demi-r-normal--6-60-72-72-p-36-iso8859-1 -urw-itc bookman-demi-r-normal--8-80-72-72-p-48-iso8859-1 -urw-itc bookman-light-i-normal--0-0-0-0-p-0-iso8859-1 -urw-itc bookman-light-i-normal--0-0-72-72-p-0-iso8859-1 -urw-itc bookman-light-i-normal--10-100-72-72-p-56-iso8859-1 -urw-itc bookman-light-i-normal--12-120-72-72-p-66-iso8859-1 -urw-itc bookman-light-i-normal--14-140-72-72-p-80-iso8859-1 -urw-itc bookman-light-i-normal--6-60-72-72-p-35-iso8859-1 -urw-itc bookman-light-i-normal--8-80-72-72-p-45-iso8859-1 -urw-itc bookman-light-r-normal--0-0-0-0-p-0-iso8859-1 -urw-itc bookman-light-r-normal--0-0-72-72-p-0-iso8859-1 -urw-itc bookman-light-r-normal--10-100-72-72-p-57-iso8859-1 -urw-itc bookman-light-r-normal--12-120-72-72-p-69-iso8859-1 -urw-itc bookman-light-r-normal--14-140-72-72-p-80-iso8859-1 -urw-itc bookman-light-r-normal--6-60-72-72-p-35-iso8859-1 -urw-itc bookman-light-r-normal--8-80-72-72-p-46-iso8859-1 bookman-demi bookman-demiitalic bookman-light bookman-lightitalic
Does it help if you enable the checkbox in the menue Tools -> Options -> Text Document -> General -> Use Printer Metrics? If yes, then the problem is probably related to issue 23597.
Yes (for the widths), and no because using the printer metrics bring there own horrible set of problems. See Issue 11191. I understood that "Use Printer Metrics" only existed as a back compatibility with a quirk of SO 5.2.
HDU->PL: Is there any good reason why "/usr/openwin/lib/X11/fonts/TrueType" is not in the default search path for fonts? And while you are at it please also add ghostscript's font path. Finding these font files is absolutely essential for getting good metrics. HDU->JamesLee: The best solution for you seems to be to use the "spadmin" tool (in OOo's program directory) to make a scalable Bookman font visible to OOo. E.g. from the font directory /usr/openwin/lib/X11/fonts/TrueType. Also ghostscript from http://www.sunfreeware.com/ has a Bookman font in /usr/share/ghostscript/fonts/. The use of printer metrics for formatting is a good idea when the fonts you use are e.g. only existant on the printer. HDU->HDU: the problem that X11 fonts will be limited to a maximum height of 250 pixel will be addressed in issue 23597.
> HDU->JamesLee: The best solution for you seems to be to > use the "spadmin" tool (in OOo's program directory) to make > a scalable Bookman font visible to OOo. E.g. from the font > directory /usr/openwin/lib/X11/fonts/TrueType. /usr/openwin/lib/X11/fonts/TrueType doesn't have Bookman fonts as such, they are called BookmanOldStyle. If I load it as a TT the name won't be Bookman-Demi. This means the print file will not use (ask for from printer) Bookman but include its own BookmanOldStyle. Neither are there some of the other fonts which have the same problem provided as TTs, eg, Palatino. > Also ghostscript from http://www.sunfreeware.com/ http://www.blastwave.org/packages/ghostscript (and note the maintainer.) > has a Bookman font in > /usr/share/ghostscript/fonts/. On Solaris it shouldn't. > The use of printer metrics for formatting is a > good idea when the fonts you use are e.g. only > existant on the printer. The back-compatibility problem with printer metrics makes the option unusable. Please can you explain something here, if the font is only on the printer, how does OOo know anything about it's metrics or is able to show it? There seems to be a fundamental problem here, with using the screen's font metrics. If a screen provides a slightly different font won't the page layout change? Shouldn't the metrics always come from OOo and not the X-server (which can be another machine). Also consider exchange of documents between machines and OSes, how are the metrics know and kept constant between Solaris, Mac & MSW? What is ./share/psprint/fontmetric/Bookman-Demi.afm for?
> If I load it as a TT the name won't be Bookman-Demi. This means the print > file will not use (ask for from printer) Bookman butinclude its own > BookmanOldStyle. The edit field in the font combo box is freestyle. If you type "Bookman" in there and set the Bold attribute, then most probably Bookman-Demi will be used if this gets printed to a PS printer. It is a little unfortunate that only two weights Bold/Non-Bold and two slants Italic/Non-Italic are available to the user even if a font has many more variations. If you think it would be a major enhancement to be able to select all of the variations I suggest to submit a feature task to "BH". > Please can you explain something here, if the font is only on the printer, how > does OOo know anything about it's metrics or is able to show it? The AFM files have the metrics and the license for them is usually very liberal, so they are easily available. OOo shows them on the display by using the font with a matching name or its fallbacks. E.g. Bookman could fall back to Bookman Oldstyle. This only happens for printer dependent formatting. > There seems to be a fundamental problem here, with using the screen's font > metrics. If a screen provides a slightly different font won't the page layout > change? Yes, that is a problem, but for printer independent formatting only the metrics from the display fonts are available. Are you suggesting that even for printer independent formatting the metrics of the standard postscript fonts should be used, even if a font with a matching name is available on the system that has different metrics? > Also consider exchange of documents between machines and OSes, how are the > metrics know and kept constant between Solaris, Mac & MSW? The well known fonts and their aliases are usually metrically compatible. E.g. Helvetica<->Arial, Times<->TNR, etc. Other than that it is impossible to know all metrics of all fonts. The idea is that if you want to use the same font on many different systems, this same font must be available on all these systems. We are considering to add font embedding though. > What is ./share/psprint/fontmetric/Bookman-Demi.afm for? This is for printer dependent formatting if the printer description in ./share/psprint/driver/ claims that the printer has a builtin font named "Bookman-Demi". > The back-compatibility problem with printer metrics makes the option unusable. I'm quite sure that at least for PS printers the different layout between different printers would be solved, if they were set to the same device resolution (File->PrinterSettings->Advanced->Device->Resolution). > (and note the maintainer.) :-) Nice to meet you. HDU->OS: There is of course also the issue that even for printer independent formatting you ask the printer for its fonts and create the list in the font combobox for it. Would you like to comment on the philosophy behind using the printer font names for printer independend formatting?
The 'philosophy' hasn't changed with introducing printer independent layout. I submitted issue 23712 to change this.
Will add the font path /usr/openwin/lib/X11/fonts/TrueType to the standard search path.
added said font path to default search, fixed in CWS vclpp3bugs
verified in CWS vcl7pp3bugs
integrated in 645m38, closing