Issue 11207 - Warning when saving or exporting to a significantly lossy format
Summary: Warning when saving or exporting to a significantly lossy format
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Linux, all
: P3 Trivial with 5 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-05 10:24 UTC by lukekendallhome
Modified: 2013-02-07 22:33 UTC (History)
1 user (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description lukekendallhome 2003-02-05 10:24:11 UTC
Refer to http://www.openoffice.org/issues/show_bug.cgi?id=11009

The suggestion is that it would be good to pop up a warning when saving
in a semantically dissimilar format.  (E.g. saving a Powerpoint
file as an Impress format file.)

The usability problem to solve is, that the nagging
warnings when saving in M$ formats instead of OO formats,
tend to limit the value of such a warning.

Ideally, this would be solved by actually recording a set of features
supported by the current format, subtracting the set of features supported
by the destination format, and popping up a very directed warning during
the save or export function.

This would mean that the warnings suddenly became serious concerns,
not something you could normally ignore safely!  Win-win.

That idea might even be patentatble (i.e., I'd suggest you protect
yourselves by filing a simple "register of invention": I hereby assign all
intellectual rights for this idea to the OpenOffice open source organisation.)

luke
Comment 1 matthias.huetsch 2003-02-05 18:34:05 UTC
This warning dialog is raised from layers well above the UCB, who only
provides the means of loading and saving documents.

As all applications (writer, calc, impress...) are affected, my best
guess is that this issue should belongs to the 'framework' project.

Reassigning...
Comment 2 thorsten.martens 2003-02-11 14:23:18 UTC
TM->BH: Please have a look at this issue. Maybe this wish for a
feature is worth to think about.
Comment 3 eric.savary 2003-04-16 15:30:09 UTC
Set to "NEW"
Comment 4 ace_dent 2008-05-16 02:40:24 UTC
OpenOffice.org Issue Tracker - Feedback Request.

The Issue you raised has the status 'New' pending further action, but has not
been updated within the last 4 years. Please consider re-testing with one of the
latest versions of OOo, as the problem(s) may have already been addressed.
Either use the recent stable version: http://download.openoffice.org/index.html
or consider trying the new OOo 3 BETA (still in testing):
http://download.openoffice.org/3.0beta/
 
Please report back the outcome so this Issue may be Closed or Progressed as
necessary - otherwise it may be Resolved as Invalid in the future. You may also
wish to search for (and note) any duplicates of this Issue that may have
advanced further by checking the Issue Tracker:
http://www.openoffice.org/issues/query.cgi
 
Many thanks,
Andrew
 
Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 5 lukekendallhome 2008-05-17 07:48:41 UTC
In OOo 2.3, the messages are still very general and basically contain just 1 bit
of information: that the format is somehow different.  I still think it would be
valuable to be much more precise about the features that may be in use that
can't be translated, but I do understand that it would be a reasonable amount of
work to implement the suggestion.

luke
Comment 6 bettina.haberer 2010-05-21 14:46:38 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".