Issue 45927 - No need to mess with the display font
Summary: No need to mess with the display font
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 2.0 Beta
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2005-03-24 11:36 UTC by
Modified: 2013-08-07 14:38 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description 2005-03-24 11:36:35 UTC
The Writer code has some code, which deals with the ancient problem, that in the
old times when most display fonts were not printable then finding a well
matching display font for a printer font required some magic. It does this by
measuring the layouted widths of a test string on the output device with the
requested font, on the reference device with the requested font and on the
output device with the best matching font from the reference device.

The problem with the "fixed test string method" is, that this test string often
has no relevance to the text which the font is used for.  E.g. using an english
test string to determine which Thai font to use causes more problems than it solves.
Comment 1 2005-03-24 11:38:22 UTC
HDU reminder: also see #119763#
Comment 2 frank.meies 2005-03-30 11:05:43 UTC