https://bugs.documentfoundation.org/show_bug.cgi?id=68573

Eyal Rozenberg <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|FORMATTING:Underline        |FORMATTING:Inconsistent
                   |enhancement (see comment 6) |underlining of text in
                   |                            |different fonts (see
                   |                            |comment 6)

--- Comment #16 from Eyal Rozenberg <[email protected]> ---
So, there are several potential problems with the underlining of adjacent
characters:

1. Inconsistency of stroke width
2. Inconsistency of vertical positioning of the underline
3. Horizontal discontinuity

Problems (1.) and (2.) do indeed still happen, and as Khaled explained that is
as was intended in the implementation; problem (3.) is a bit more elusive, but
I do believe I'm seeing it with one of the documents in the zip file. Please
help me confirm that aspect.

Now, about Khaled's comment:

(In reply to ⁨خالد حسني⁩ from comment #6)
> I’m not sure how this can be fixed since there is probably some good reasons
> to make this font dependant 

Yes, but font-dependent does not have to mean ignorant of other text on the
same line / same stretch of underlined text. For example, we can take the
maximum width, the minimum width, or the average; and height-wise, it would
probably make sense to choose the lowest vertical position and use that
consistently.

This should emulate what how real person would draw an underline (or overline
etc.) when faced with text in different fonts. They would definitely not draw
multiple disjoint line segments.

Then you may not even need configuration for this. (But I won't say no to
configurability of underlining.)


That being said - one can argue that text in different fonts should perhaps not
be underlined at all, since when handwriting, you don't switch fonts in the
middle of a line.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to