Problem description: FILESAVE FORMATTING saving sheet as xml loses user-defined date format. Defining a user-defined format like DD-MMM-YYYY is not properly saved when the sheet is saved using "as Microsoft XMl format (*.xml)" Steps to reproduce: 1. create new sheet 2. set a cell with value 1-Apr-2015 3. right click > format cell > format code 4. enter "DD-MMM-YYYY" spreadsheet shows 1-Apr-2015, as expected. 5. file > save "as Microsoft XML 2003 (*.xml)" 6. close sheet. open saved xml sheet Current behavior: Date appears formatted as 1-Apr-14. User-defined format got lost while saving as *.xml If you open the xml file you can confirm that is was saved as <NumberFormat ss:Format="Medium Date">, hence losing the specific format. Expected behavior: xml file should be able to save ("remember") the user-defined format.
Can you please open a ods file with a date formatted as needed. After that set the bug back to UNCONFIRMED
I can confirm: If i save with ods format and then re-open, the date shows properly formatted.
Created attachment 111721 [details] ods file. when saved as xml, loses date format user defined format works on ods files. when saved "as" *.xml format, the file loses the uer-defined date format.
I see 04-Di-2015 Not sure why 14.04.2015 would display that way. Maybe due to Locale: de_? OSX 10.10.1 Version: 4.5.0.0.alpha0+ Build ID: 2d59c0c940ac61240992502256c966b2cb4f9daa TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2015-01-04_01:16:22 Locale: de_ Re-opening the saved .xml file shows 14-4-15 instead of the previous 04-Di-2015. When I look at the cell formatting I see that it's set to date and the last possible option is set (just as previously was the case). I'm not entirely sure what to make of this, but can confirm that date format changes after saved to .xml thus NEW.
Dear Bug Submitter, 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 This NEEDINFO message was generated on: 2015-07-18
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 Message generated on: 2015-09-03