[Bug 166835] Warn when first introducing an opened-file-format-incompatible aspect into a document

[bugzilla-daemon at bugs.documentfoundation.org]

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

--- Comment #10 from Eyal Rozenberg <eyalroz1 at gmx.com> ---
(In reply to jan d from comment #4)

> Aside of effort of implmentation,

This would certainly require some work. But - not being an LO developer myself,
I want to ask you to elaborate:

How much of an effort would you estimate this to be? That is, considering we do
need to know about what a format will and won't support, for doing
warn-or-save? And given that we have some support for "compatibility modes"
(which are with applications, but still).

> warn-on-incompatible-change seems to introduce a lot of open questions like
> how "incompatible change" is defined, when we assume "editing" (with intent
> to change the file in place) and when we assume "import" (with intent do
> store in another format).

When I think about this feature, the criterion for warning is: "If I were to
save the document (File > Save) after the action I've just requested - would I
get the warning-on-save?"

... and that's it. The first time after opening the document at which the
answer to this question becomes "Yes" - that's when you'd warn. And if it
doesn't become yes, then there's no reason to warn.

I believe this addresses all three questions (and if it doesn't - please say
so). Of course, LO might not be aware that a change is incompatible - but then
it wouldn't warn-on-save anyway. That would be an orthogonal issue.

> (an alternative pattern to warn-on-save is what some image editors do –
> differentiate between "save" (native format) and "export" (andthing else))

I'm not actually suggesting we drop warn-on-save; although if this is accepted,
the question might well come up.

-- 
You are receiving this mail because:
You are on the CC list for the bug.