Created attachment 133342 [details] Not possible to save XML after edit After I edit the attached file, and try to save it, it says: "Error when trying to save text_ui_news document: Error: Writing error. Not possible to write the file." (I'm using Hungarian language, so I translated the error message the best I could). I tried a lot of previous versions of LibreOffice, stable and beta, still the same problem. Turned off antivirus, UAC, I'm the only user. File is not write protected. If I use Microsoft Excel, instead of LibreOffice, there is no problem when saving the file after edit.
I can reproduce it in Version: 5.4.0.0.alpha1+ Build ID: 74d2e606fd3605fe0a585f596eaa215ae4e20d18 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Locale: fo-FO (ca_ES.UTF-8); Calc: group However, MSO Excel 2010 doesn't even open it alleging there's a problem in the table. Are you sure you attach the correct file ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
I haven't tried Microsoft Office 2010, I'm using Microsoft Office 2016, and there's no problem with that, so editing and saving works there. However when trying the same with LibreOffice, it fails to save.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still present in LibreOffice 6.0.4 and 6.1.0 beta x64.
from 6.1 LO cannot save as Microsoft Excel 2003 XML. Until Bug 121100 this one is WontFix.
Repro 6.2+ for Export.
(In reply to Timur from comment #6) > Repro 6.2+ for Export. Hi Timur, Which are the steps to reproduce it? Save as works fine in Version: 6.2.0.0.alpha1+ Build ID: 1cfa1d9e1041b0e82d9be90847c428adfd01476e CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: threaded
Oh, I found it. File - Export - Export to Microsoft Excel 2003 XML
@Kohei, I thought you could be interested in this issue...
This is unfortunately not a bug, but a side affect of how the current filter management system works. "Fixing" this would unfortunately involve a large scale (and risky) refactoring that I'm not personally interested in partaking, and personally it's not worth the risk.
There was a duplicate bug filed for this, and it was closed as NOTABUG. I can't find that issue now, but let me just close this one the same way as well.