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

Justin L <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |minor

--- Comment #10 from Justin L <[email protected]> ---
While editing the document, this red colour is simply a direct formatting
character colour (because the internal paragraph style it came from did not
define font colour).

Upon saving, it must notice that the entire paragraph has the same font colour,
and so it transfers that to the paragraph style. Thus at load time, the
paragraph style colour is applied to the list number/bullet.

The same principle applies during editing as well. If you select the entire
paragraph and set the font colour, then the font colour is applied to the
paragraph style (and immediately gets applied to the list).

Obviously we don't want a simple carriage return at the end of a paragraph to
automatically convert the direct character formatting into a new paragraph
style right away.

Another set of "steps to reproduce" would be to hit enter after "Holle Wo".
After a round-trip, the last bullet point will become yellow. The same
principle applies: the new paragraph "rld" had every character with the same
yellow attribute, so on save it exported that colour into the automatic
paragraph style. Once again, I can't imagine that it would be smart to have LO
analyse both "new" paragraphs and immediately reconfigure their automatic
paragraph styles.


So, any attempt to "fix" this bug report will have to focus on the export
process. Why would LO not simply export the automatic styles as they are
instead of "optimizing"? (It is worth noting that this "optimization" does NOT
affect the in-memory document - it still uses the old styles.) I would have to
imagine that making changes to the export process will have many unintended
ramifications...

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

Reply via email to