To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=5930





------- Additional comments from paulwolstenho...@openoffice.org Wed Dec 15 
19:53:47 +0000 2010 -------
Let's not confuse the idea of encoding engineering format in a calc file (using
1000's grouping) with the issue of expressing engineering format in OOo's
equivalent to what excel describes as a 'custom code' string.

It would be confusing to make the user enter a comma in the format string just
because we have a (temporary?) situation that encodes his intention in a similar
manner to 1000's grouping.

It is consistent with the existing symbol definitions to express standard
engineering format as ##0.00E+00 since the # indicates the possible presence of
a digit with leading 0 supression.

Do we need to support leading zeros with engineering format?  I do not think so.
 Excel allows #00.00E+00 and 000.00E+00 to express engineering notation (i.e.
the exponent a multiple of 3) with a minimum of 2 or 3 digits before the decimal
point (i.e. leading zeros) and it does implement it.  Not wishing to be sexist,
I might suggest that a user of this format could be an extremely strange girl or
guy ;)  Perhaps a reasonable compromise here is to accept the code #00.00E+00
and show 1234 as 001.23E+03 (because I can't imagine a need to supress the first
leading zero but not the second).

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@sc.openoffice.org
For additional commands, e-mail: issues-h...@sc.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to