https://bugs.documentfoundation.org/show_bug.cgi?id=90708

--- Comment #10 from [email protected] ---
(In reply to Matt Keveney from comment #9)
> (In reply to Laurent Balland from comment #7)
> ..subject originally raised in Bug 153993; moving discussion here.
>
> I agree that considering _units_ opens a huge can of worms.  Aside from the
> example you mention, one might expect that 10V / 1kΩ would produce a result
> in Amps: 12mA.  Such intelligence about units would be _far_ more complex
> than a simple display format.

This would indeed be a can of worms... except this is not what (as I perceive,
since I do have the exact same wish) the initial request is about. Gnumeric
indeed doesn't support unit conversion, we're only talking about _formatting_
here, e.g. display "m" (milli) instead of "E-03" or "k" instead of "E+03".
Having the exponent part makes (IMHO) cell values harder to read than the usual
SI prefix.


> And I think it's unnecessary to go that far.  I think prefix support alone,
> without considering units would be very useful and much simpler to implement.

Appending an SI unit in Gnumeric is supported in a list. It is up to the user
to select the appropriate unit given the formula they're using (if any). It's
not the responsibility of the program to do that. So only a transcription from
scientific notation (that is a "E" followed by a sign and two digits) to the
appropriate SI prefix ("k", "m", "n", "p", "M", "µ", "G", aso) is the object of
this request.

>From where I stand such a feature would make a __huge__difference as it is the
only reason I'm still using Gnumeric despite a long list of features that only
LOCalc/OOCalc provide.

Now as far as the unit is concerned, I see no need to support that from LO/OO
Calc as the user still can append a custom string to the format string. I
suppose the biggest challenge is to expose a "standard" way to format numbers,
while accounting for engineering notation...

Just wanted to add my 2¢.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to