Bug 68918 - FILESAVE: Content loss results when saving in a different format (docx)
Summary: FILESAVE: Content loss results when saving in a different format (docx)
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.1.2 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: possibleRegression
Depends on:
Blocks:
 
Reported: 2013-09-04 07:15 UTC by Jonathan Camilleri
Modified: 2015-12-15 10:53 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Documents (803.50 KB, application/zip)
2013-09-04 07:15 UTC, Jonathan Camilleri
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Camilleri 2013-09-04 07:15:46 UTC
Created attachment 85173 [details]
Documents

Problem description: 

Steps to reproduce:
1. File > Save a document in .odt format
2. File > Save a document in .docx format

Current behavior:
It is noted that currently saving in a different format results in loss of content.  Similar behaviour had been noticed with my assignment, and, I had thought that I had done some mistake but I lost about two days of typing when I was copying and saving the documents.

Expected behavior:
No content loss is made when saving content or transposing to a different format.

Opportunity cost for this data loss in terms of intellectual property can be estimated as:
€50 x 16 hours = €800
excluding administrative expenses.
              
Operating System: Ubuntu
Version: 4.1.1.2 rc
Last worked in: 3.6.7.2 rc
Comment 1 Fridrich Strba 2013-09-04 07:49:32 UTC
(In reply to comment #0)
> Opportunity cost for this data loss in terms of intellectual property can be
> estimated as:
> €50 x 16 hours = €800
> excluding administrative expenses.

Thanks. It is to be noted that saving in any other format then .odt (the ISO approved open standard) can even incur more costs: medical expenditures, child psychologist expenditures and even some taxi bills for going to and from hospital. Since it is insane to want to use anything else :)
Comment 2 Robinson Tryon (qubit) 2013-10-17 00:02:11 UTC
Changing 'regression' -> 'PossibleRegression' until we have independent confirmation of a regression.
Comment 3 Robinson Tryon (qubit) 2013-10-17 00:14:09 UTC
Testing with Ubuntu 12.04.3 + LO 4.1.2.3

Following OP's steps to reproduce as closely as possible:
1. File -> Save a document in .odt format
2. File -> Save As -> 'All Formats' -> Microsoft Word 2007/2010 XML (.docx)

I see the following warning:

---
Confirm File Format

This document may contain formatting or content that cannot be saved in the
currently selected file format "Microsoft Word 2007/2010 XML".

Use the default ODF file format to be sure that the document is saved correctly.

[Button: Use Microsoft Word 2007/2010 XML Format]  [Button: Use ODF Format]

[checkbox: x] Ask when not saving in ODF format
---

3. Click "[Button: Use Microsoft Word 2007/2010 XML Format]"
4. (Current behavior:
It is noted that currently saving in a different format results in loss of content.)

RESULTS:
As described in Step #2, the user is warned about data loss before the document is saved in DOCX format.


Jonathan - What do you think about the content of the warning that is presented to the user? Do you have any suggestions on how we might better inform our userbase about incompatibilities or feature differences between file formats?

Thanks
Comment 4 QA Administrators 2014-05-17 00:33:47 UTC
Dear Bug Submitter,

Please read the entire message before proceeding.

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 5 QA Administrators 2014-06-01 20:29:45 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO
Comment 6 Robinson Tryon (qubit) 2015-12-15 10:53:31 UTC
Migrating Whiteboard tags to Keywords: (possibleRegression)
[NinjaEdit]