[Libreoffice-bugs] [Bug 125268] Wrong text highlight color when export document to doc/docx

[bugzilla-daemon at bugs.documentfoundation.org]

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

--- Comment #44 from Mike Kaganski <mikekaganski at hotmail.com> ---
The issue with "It took many hours to make this, and now it tells me it can't
be saved into DOCX is a serious one (although if one would try to save to, say,
TXT, many would agree that it's not an issue ;-))". But instead of creating
sets of UI for different scenarios, maybe a service that could dynamically
check the document for "compliance" with currently active filter could be
better? (I don't see a problem in compatibility palettes; the problem is when
to use one.)

E.g., the service could work in the background, like spellchecker; and when it
finds an issue like this one, it adds a warning info panel (similar to "read
only") with explanation. Or it could react to uno commands, analyze the result,
and show a tooltip. The warning message in the info panel or tooltio could be
something like "This color cannot be saved as highlight in DOCX". As that would
popup right when user made the change (or 10 seconds later, if run in the
background), it would be easy to act timely, and not stack problems until it
takes a full re=creation of the document from scratch.

However, this doesn't remove the need for save-time check. No amount of magic
would prevent a user to create a new document, add any formatting (while it
doesn't have a chosen filter yet), then decide to save to DOCX. Only save-time
dialog with enough information could help then.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20200327/ba49291c/attachment.htm>