Add binary prefix units #449
Labels
c: numbers
Component: numbers, currency, units
new unit
Request for a new unit in Intl.NumberFormat
s: blocked
Status: the issue is blocked on upstream
Small
Smaller change solvable in a Pull Request
Comments
sffc
added
c: numbers
|
If we are just adding the prefixes, then the work could be feasible.
However, it is very late in the cycle for us to be adding new data for
translation, so I will add this to the CLDR agenda tomorrow.
I think it would be bounded to the following (this is the English version):
16 strings per language. Does this look right, Shane?
long
<compoundUnit type="1024p1">
<unitPrefixPattern>kibi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p2">
<unitPrefixPattern>mebi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p3">
<unitPrefixPattern>gibi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p4">
<unitPrefixPattern>tebi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p5">
<unitPrefixPattern>pebi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p6">
<unitPrefixPattern>exbi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p7">
<unitPrefixPattern>zebi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p8">
<unitPrefixPattern>yobe{0}</unitPrefixPattern>
</compoundUnit>
short
<compoundUnit type="1024p1">
<unitPrefixPattern>KiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p2">
<unitPrefixPattern>MiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p3">
<unitPrefixPattern>GiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p4">
<unitPrefixPattern>TiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p5">
<unitPrefixPattern>PiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p6">
<unitPrefixPattern>EiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p7">
<unitPrefixPattern>ZiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p8">
<unitPrefixPattern>YiB{0}</unitPrefixPattern>
</compoundUnit>
Mark
…On Mon, Jun 1, 2020 at 8:32 PM Shane F. Carr ***@***.***> wrote:
Binary units such as KiB and MiB reduce ambiguity associated with kB and
MB. We have received numerous requests to add them to ECMA-402. This is
currently blocked by upstream CLDR not having locale data for these units.
Relevant CLDR discussions:
- https://unicode-org.atlassian.net/browse/CLDR-7214
- https://unicode-org.atlassian.net/browse/CLDR-11454
User requests:
- #32 (comment)
<#32 (comment)>
- https://goo.gle/devtools-si
@mathiasbynens <https://github.com/mathiasbynens> @markusicu
<https://github.com/markusicu> @macchiati <https://github.com/macchiati>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#449>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJLEMFCL7F432OIJ6W57QDRURXDVANCNFSM4NQK42IQ>
.
|
|
I created a ticket for discussion. Please add comments there:
https://unicode-org.atlassian.net/browse/CLDR-13848
Mark
…On Tue, Jun 2, 2020 at 2:35 PM Mark Davis ☕️ ***@***.***> wrote:
If we are just adding the prefixes, then the work could be feasible.
However, it is very late in the cycle for us to be adding new data for
translation, so I will add this to the CLDR agenda tomorrow.
I think it would be bounded to the following (this is the English
version): 16 strings per language. Does this look right, Shane?
long
<compoundUnit type="1024p1">
<unitPrefixPattern>kibi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p2">
<unitPrefixPattern>mebi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p3">
<unitPrefixPattern>gibi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p4">
<unitPrefixPattern>tebi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p5">
<unitPrefixPattern>pebi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p6">
<unitPrefixPattern>exbi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p7">
<unitPrefixPattern>zebi{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p8">
<unitPrefixPattern>yobe{0}</unitPrefixPattern>
</compoundUnit>
short
<compoundUnit type="1024p1">
<unitPrefixPattern>KiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p2">
<unitPrefixPattern>MiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p3">
<unitPrefixPattern>GiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p4">
<unitPrefixPattern>TiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p5">
<unitPrefixPattern>PiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p6">
<unitPrefixPattern>EiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p7">
<unitPrefixPattern>ZiB{0}</unitPrefixPattern>
</compoundUnit>
<compoundUnit type="1024p8">
<unitPrefixPattern>YiB{0}</unitPrefixPattern>
</compoundUnit>
Mark
On Mon, Jun 1, 2020 at 8:32 PM Shane F. Carr ***@***.***>
wrote:
> Binary units such as KiB and MiB reduce ambiguity associated with kB and
> MB. We have received numerous requests to add them to ECMA-402. This is
> currently blocked by upstream CLDR not having locale data for these units.
>
> Relevant CLDR discussions:
>
> - https://unicode-org.atlassian.net/browse/CLDR-7214
> - https://unicode-org.atlassian.net/browse/CLDR-11454
>
> User requests:
>
> - #32 (comment)
> <#32 (comment)>
> - https://goo.gle/devtools-si
>
> @mathiasbynens <https://github.com/mathiasbynens> @markusicu
> <https://github.com/markusicu> @macchiati <https://github.com/macchiati>
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#449>, or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACJLEMFCL7F432OIJ6W57QDRURXDVANCNFSM4NQK42IQ>
> .
>
|
|
Note that I fixed the typos in the ticket to drop the B from the short
forms.
Mark
…On Tue, Jun 2, 2020 at 2:45 PM Mark Davis ☕️ ***@***.***> wrote:
I created a ticket for discussion. Please add comments there:
https://unicode-org.atlassian.net/browse/CLDR-13848
Mark
On Tue, Jun 2, 2020 at 2:35 PM Mark Davis ☕️ ***@***.***> wrote:
> If we are just adding the prefixes, then the work could be feasible.
> However, it is very late in the cycle for us to be adding new data for
> translation, so I will add this to the CLDR agenda tomorrow.
>
> I think it would be bounded to the following (this is the English
> version): 16 strings per language. Does this look right, Shane?
>
> long
>
> <compoundUnit type="1024p1">
> <unitPrefixPattern>kibi{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p2">
> <unitPrefixPattern>mebi{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p3">
> <unitPrefixPattern>gibi{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p4">
> <unitPrefixPattern>tebi{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p5">
> <unitPrefixPattern>pebi{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p6">
> <unitPrefixPattern>exbi{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p7">
> <unitPrefixPattern>zebi{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p8">
> <unitPrefixPattern>yobe{0}</unitPrefixPattern>
> </compoundUnit>
>
> short
>
> <compoundUnit type="1024p1">
> <unitPrefixPattern>KiB{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p2">
> <unitPrefixPattern>MiB{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p3">
> <unitPrefixPattern>GiB{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p4">
> <unitPrefixPattern>TiB{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p5">
> <unitPrefixPattern>PiB{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p6">
> <unitPrefixPattern>EiB{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p7">
> <unitPrefixPattern>ZiB{0}</unitPrefixPattern>
> </compoundUnit>
> <compoundUnit type="1024p8">
> <unitPrefixPattern>YiB{0}</unitPrefixPattern>
> </compoundUnit>
>
> Mark
>
>
> On Mon, Jun 1, 2020 at 8:32 PM Shane F. Carr ***@***.***>
> wrote:
>
>> Binary units such as KiB and MiB reduce ambiguity associated with kB and
>> MB. We have received numerous requests to add them to ECMA-402. This is
>> currently blocked by upstream CLDR not having locale data for these units.
>>
>> Relevant CLDR discussions:
>>
>> - https://unicode-org.atlassian.net/browse/CLDR-7214
>> - https://unicode-org.atlassian.net/browse/CLDR-11454
>>
>> User requests:
>>
>> - #32 (comment)
>> <#32 (comment)>
>> - https://goo.gle/devtools-si
>>
>> @mathiasbynens <https://github.com/mathiasbynens> @markusicu
>> <https://github.com/markusicu> @macchiati <https://github.com/macchiati>
>>
>> —
>> You are receiving this because you were mentioned.
>> Reply to this email directly, view it on GitHub
>> <#449>, or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/ACJLEMFCL7F432OIJ6W57QDRURXDVANCNFSM4NQK42IQ>
>> .
>>
>
|
should be |
|
Thanks. I added
https://unicode-org.atlassian.net/browse/CLDR-13848?focusedCommentId=156911
Mark
…On Fri, Jun 19, 2020 at 8:53 AM Krzysztof Maczyński < ***@***.***> wrote:
yobe{0}
should be yobi
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#449 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJLEMA2IL2LZOKQSAFCBBTRXOCW5ANCNFSM4NQK42IQ>
.
|
|
CLDR now contains strings for the binary prefixes: https://github.com/unicode-org/cldr/blob/main/common/main/en.xml#L6128 https://github.com/unicode-org/cldr/blob/main/common/main/ar.xml#L10572 I had expected to see shorthand units like "KiB":
source: https://en.wikipedia.org/wiki/Kilobyte But it seems kibibyte and friends only have a "long" string specified. But perhaps that'd need to be a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Binary units such as KiB and MiB reduce ambiguity associated with kB and MB. We have received numerous requests to add them to ECMA-402. This is currently blocked by upstream CLDR not having locale data for these units.
Upstream ticket:
https://unicode-org.atlassian.net/browse/CLDR-13848
Relevant CLDR discussions:
User requests:
@mathiasbynens @markusicu @macchiati
The text was updated successfully, but these errors were encountered: