Hi Rick, On Monday, 2016-01-25 16:26:53 -0500, Rick C. Hodgin wrote:
On Mon, Jan 25, 2016 at 3:21 PM, Rick C. Hodgin <rick.c.hodgin@gmail.com>On Tue, Jan 12, 2016 at 8:00 AM, Eike Rathke <erack@redhat.com> wrote:On Friday, 2016-01-08 19:52:49 -0500, Rick C. Hodgin wrote:The category is called *"Metric."* When conveying fractional values, such that 1.2345E-08 (which is 0.000,000,012,345), it would do so in a metric-relative way using the standard milli (10^-3), micro (10^-6), nano (10^-9), pico (10^-12), andsoon... In the example, the *Metric* display would cause the value to show up as "*12,345 pu*" (pico-units) if the thousands separator was used.Could you give some examples what you think how the format code actually should look like?Eike, I never heard back from you after my reply. The format would be "Metric" with "Metric:seconds" given for a specific override for the units name. And there are a few other options that I would like to append including a bias that the data may already be in, such as kilo-units ("Metric[:seconds][:bias=kilo]") and an override base to use, such as always displaying in milli-units ("Metric[:seconds][:bias=kilo][affix:milli]").Please forgive my dyslexia. It should be: Metric[:seconds][:bias=kilo][:affix=milli] Each of the [] portions are optional, and would actually appear in a form like this: Metric:seconds:bias=kilo:affix=milli
I don't see how that would fit into the existing number format code syntax. It looks like something completely different. Eike -- LibreOffice Calc developer. Number formatter stricken i18n transpositionizer. GPG key "ID" 0x65632D3A - 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A Better use 64-bit 0x6A6CD5B765632D3A here is why: https://evil32.com/ Care about Free Software, support the FSFE https://fsfe.org/support/?erack
Attachment:
signature.asc
Description: PGP signature