Description: In the "other" spreadsheet program, I would be able to apply a format of '#,##0_._0_0' to request that space for a decimal point and two fractional digits be reserved, but not printed; with horizontal-alignment of "right" the above format would align correctly with numbers formatted at '#,##0.00'. However, with Calc, the _ formatting directive doesn't seem to work. It allows me to create a user-defined format, but when the document is saved and then reloaded, all formats with the _x type of directive are replaced with modified formats that have trailing quoted spaces instead of the _x directive(s). And the number of spaces does not seem to be correct for ensuring vertical alignment. Steps to Reproduce: 1.Format a number using the _0 (or any other _x) 2.Save document, exit program 3.Restart program, open document, observe formatting changes Actual Results: format string for affected numeric fields is changed to include " " (number of spaces varies). Expected Results: Specified formatting (with the _ directive) should be retained. Alternatively, if the conversion to " " formatting is absolutely essential, at least the amount of space being inserted should correspond to the intended behavior (ie, proper alignment). Reproducible: Always User Profile Reset: No Additional Info: According to Mike Kaganski, he has reproduced this on 5.3.3.2 and requested that I file this bug report. User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0
Reproducible with Version: 5.3.3.2 (x64) Build ID: 3d9a8b4b4e538a85e0782bd6c2d430bafe583448 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; Layout Engine: new; Locale: ru-RU (ru_RU); Calc: group According to https://help.libreoffice.org/Common/Number_Format_Codes#Spaces , this must work. Actually after save-and-reload, a " " with twice as much spaces is created in format code instead of _._0_0 part (as if separate space for both "_" and following character).
** 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
This bug is still present as of version 6.1.1.2 (built from sources on NetBSD 8.99.22 host, x86_64 platform). A format of ###_._0_0 gets converted to ###" " by a save/open sequence.
Dear Paul Goyette, 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
This bug is still present in: Version: 6.3.1.2 Build ID: 30(Build:2) CPU threads: 16; OS: unknown; UI render: default; Locale: en-US (C); UI-Language: en-US Calc: threaded This build was compiled from sources using NetBSD pkgsrc on an amd64 host running NetBSD 8.99.51.
The problem here is that an underscore plus character leads to a *visual* replacement with an approximated width of that character, i.e. for '_.' one space is used and for '_0' two spaces are used. The ODF file format has no notion of this visual relation and no <number:visually-blank> element or such. When storing the definition of the number format the number formatter is asked for the representation, which for the '_._0_0' sequence results in 5 blanks. The #,###_._0_0 format is stored as <number:number-style style:name="N121"> <number:number number:decimal-places="0" loext:min-decimal-places="0" number:min-integer-digits="0" number:grouping="true"/> <number:text> </number:text> </number:number-style> with 5 literal spaces in the trailing <number:text> element. Technically when displaying a number formatted such the result is the same as with _._0_0
*** This bug has been marked as a duplicate of bug 152724 ***