https://bugs.documentfoundation.org/show_bug.cgi?id=125268
--- Comment #43 from Telesto <tele...@surfxs.nl> ---
(In reply to Heiko Tietze from comment #41)
> We discussed the topic in the design meeting. While introducing a color
> palette is the easiest solution it cripples our features for no good reason.
How does a MSO color palette cripple the features of Libo? And is
interoperability not a good reason. In this line of argument I would question
the capability to export to different formats in general. ODT or nothing.
> MSO might change the behavior at any time.
Yes, but the have the same backward compatibility issue. Not every-one is
running the latest version of MSO. Pushing something like that is only possible
with MSO cloud only solutions. Where everbody is forced to work with latest and
greatest version.
>
> The better approach is to warn in detail what attribute in the current
> document might not work when saved as docx (or other formats). That means to
> analyze the document, compare against a list of incompatibilities, and show
> it to the user.
I'm not really convinced here. Specific to highlighting. I have a created a
document, with tons of highlighting. I want to share it somebody with MSO
(docx/doc).
On export (say after 20 hours of work) I get a warning "A character background
cannot be represented using MSO's highlighting and will be approximated to
[this color]". Grumble. I see three outcomes:
1. Export anyway with approximated color (Current situation)
2. Export the document with highlight saved as background color (which can't be
edited in MSO easily (or at least unconventional). So ending up with questions
for MSO user (situation before 5.0)
3. Redo the document with the limited color palette (The LibO user has tones
fixes to do anyway)
More in general: it would set a president to do this for all types for
compatibility issues. Which is probably quite a long list of all types of
stuff. What so happen when a anchor is positioned differently (or different
one is used in MSO). Exported DOC/DOCX maybe look the same, but technically
different [no knowledge if this problem really exists, but expect something
similar to do so]
> The newly introduced mso-highlight.soc palette is questionable.
Please explain why. I know you don't like it. Is it the own identity of LibO?
It feels a bit like MS arrogance. Set a standard and force others into it. With
the difference that MS Office has large part of the office marked?
Compatibility issues is the reason why people don't want to use LibreOffice or
turn the back on LibreOffice after the run into trouble.
I'm personally quite content with the mso-highlighting color palette. It at
least gives the possibility to work MSO complaint (which wan't possible
before).
I would opt for renaming mso-highlight to mso-compability-highlight (should fit
in dialog). Which would be a subtitle warning & proper documentation. And maybe
optionally set mso-compability-highlight default for doc/docx. But only if this
type of problem is really limited docx/doc. Btw, are palette setting also saved
inside the ODT? If this is the case, it would also fix the DOCX/doc to ODT
variant. [Note: not suggestion palette setting should be saved, if this isn't
the case currently.]
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
