https://bugs.documentfoundation.org/show_bug.cgi?id=152724
--- Comment #7 from Eike Rathke <[email protected]> --- (In reply to ady from comment #6) > That´s somewhat confusing. I mean, a custom Format Code should allow for one > “0” to be displayed while leaving additional leading zeros as not_forced, > and places should be respected, all as described by the official help files. These format codes are an Excel thing. For saving in ODF they are transformed into an XML description of the properties of the format, the format code itself is not saved; and when loading, a format code is assembled from the XML elements. That ? and _x are preserved only for Excel file formats (until implemented for ODF as well) should probably be mentioned in the help text. > Do I understand your reply correctly? > > #0 is supported but > ?0 is not supported? Yes. > And, if the underscore is not supported, then how built-in codes such as: > #,##0_);(#,##0) > are indeed supported They are equally not, in ODF they get saved/loaded as #,##0" ";(#,##0) > > For everything else an ODF file format extension would be needed. > Is _another_ (new) bug report needed for such enhancement request? No. It means that we'd have to come up with an extension to the file format, and if that works propose it to the OASIS OpenDocument Format standard body. -- You are receiving this mail because: You are the assignee for the bug.
