[Bug 166835] Warn when first introducing an opened-file-format-incompatible aspect into a document
bugzilla-daemon at bugs.documentfoundation.org
bugzilla-daemon at bugs.documentfoundation.org
Tue Jun 3 20:47:02 UTC 2025
https://bugs.documentfoundation.org/show_bug.cgi?id=166835
--- Comment #3 from Eyal Rozenberg <eyalroz1 at gmx.com> ---
(In reply to Heiko Tietze from comment #2)
> We pondered over this in the ESC considering the warning on save. Would be
> nice to learn what exactly is not compatible. But it requires every single
> aspect to be listed somehow in a table, hard to imagine.
... which is exactly why I would not suggest that.
> Your proposal goes even further.
But it's not going in the same direction :-(
> You assume users load _and save_ alien
> formats thinking only of Microsoft's proprietary file types. But how about
> reading a simple text file in order to store as ODF? Or to improve an alien
> document and eventually saving as ODF? Or CSV => ODS, MD => ODP, etc.
The question of what format will eventually be saved is something I suggest
explicitly not caring about here. The reference is just the original format.
So, for example, if you open a CSV and, say, change the font size or text
color,
- you would get notified that you won't be able to save those changes in the
open file's original format. Yes, you might intend to save it as an ODS, but LO
doesn't know about that while you're only editing and have not saved-as. Once
you _have_ saved as - this is a non-issue. So, if you first save as ODS, then
change the font size - no warning.
Same for MD => ODP or any other change.
So, what's the big benefit here? If we have a warning-on-save anyway?
It's the fact, for at least one change - the first format-breaking change, the
user will be _fully_ aware of what they're doing and what they're risking. Yes,
it might not be the most critical change that might be lost, but we would not
need to keep track of different kinds of changes, nor will the user need to
rummage through their memory and decide what's important. The first
format-breaking change is the _best_ time to warn the user, and when they are
the least invested in format-breaking change and will be the least frustrated.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Libreoffice-ux-advise
mailing list