Issue 89284 - Underline size and position should be taken from font information
Summary: Underline size and position should be taken from font information
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: OOo 2.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2008-05-10 19:58 UTC by mightypete
Modified: 2017-05-20 11:22 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description mightypete 2008-05-10 19:58:53 UTC
There is another big problem with the underline. The program defaults to a
underline size I'm guessing at -250 and 50 wide which is fine I guess but the
program fails to look in the font and use the settings that is set there for the
underline. 50 wide is bigger than my text and -250 is so far down it's no longer
a underline. More like a roof for the next line. Wordpad gets it correct.

On expensive fonts where people have taken great care setting up the size and
position of the underline and setting it up inside the font then to be
completely ignored and defaulted to a size that breaks the font.

This is in version 2.1 so I'm sure it's still in the next beta too. Yes I know I
haven't installed the latest yet. I have it but just have not clicked run yet.
Comment 1 michael.ruess 2008-05-13 11:20:27 UTC
MRU->HDU: maybe somehow OOo could really take the font information about
underline. But we have to be aware of the fact, the "old" documents may look
differently then, so a kind of compatibility mode might be needed.
Comment 2 T. J. Frazier 2009-04-23 16:22:23 UTC
If we take rendering information from the font, any change in the appearance of
"old" documents should be an improvement, as compared to our current arbitrary
/fiat/ settings. If not, the problem is with the font, not with us; the users
should find a font that looks right to them (or complain to the foundry). If not
all fonts carry these settings, the current code may be needed as a fallback.
Adding me as CC.
Comment 3 2009-04-24 07:40:04 UTC
I agree that the font info should be used. When I implemented exactly that in the old times the then lead 
of the GSL project vetoed it and I had to remove all traces of that blasphemous thing from the code...
Comment 4 T. J. Frazier 2009-07-08 11:02:45 UTC
TJ->HDU: While I'm not a lawyer, there is a legal issue here.
We are not rendering the fonts as the designers intended. This could be seen as
a copyright violation, and/or as damaging to the foundry's reputation.

Therefore, IMHO, we should fix this promptly, before somebody sues us.

You might mention ;-) that anyone who objects may be running the risk of being
named a co-defendant, and held personally liable . . .
Comment 5 Marcus 2017-05-20 11:22:00 UTC
Reset assigne to the default "".