[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search
 
Modify

CLDR Ticket #10767(closed data: fixed)

Opened 8 months ago

Last modified 3 days ago

Short currency formats for pt (ST Forum)

Reported by: alanhzhao@… Owned by: kristi
Component: currency Data Locale:
Phase: dvet Review: kristi
Weeks: Data Xpath:
Xref:

Description

It looks like CLDR 32 changed the standard and accounting currency formats from "¤#,##0.00" to "¤ #,##0.00" for pt.

However, the short currency formats ("¤0 mil", etc.) still do not have a space. Should the space be added for consistency?

Attachments

Change History

comment:1 Changed 8 months ago by jungshik

BTW, note that it's not U+0020 (ASCII space) but U+00A0 (NBSP) that is between the currency symbol and the amount.

comment:2 follow-up: ↓ 7 Changed 8 months ago by alanhzhao@…

Yeah, also make sure that space in all pt currency formats is actually U+00A0. I did a copy-paste from the browser, and it looks like the current version might be U+0020.

comment:3 Changed 7 months ago by mark

  • Status changed from new to accepted
  • Priority changed from assess to medium
  • Phase changed from dsub to dvet
  • Milestone changed from UNSCH to 33
  • Owner changed from anybody to kristi
  • Type changed from unknown to data

Because these formats are to be as short as possible, people might be dropping the space to make it shorter.

comment:4 Changed 7 months ago by alanhzhao@…

I don't think everyone drops it though. Again, I'd favor consistency between small numbers formatted in full and large numbers using short formatting.

By the way, it looks like the number formats are still wrong? PT has ',' for decimal and '.' for grouping separator, which is correctly recorded in symbols, but not in decimalFormat or currencyFormat.

<symbols numberSystem="latn">
<decimal>,</decimal>
<group>.</group>

<decimalFormat>
<pattern>#,##0.###</pattern>
</decimalFormat>

<currencyFormat type="standard">
<pattern>¤ #,##0.00</pattern>
</currencyFormat>

comment:5 Changed 7 months ago by alanhzhao@…

Sorry, ignore the last part of #4. I see that separator characters are replaced now :)

comment:6 Changed 6 months ago by kristi

  • Milestone changed from 33 to 34

Regarding the original question "the short currency formats ("¤0 mil", etc.) still do not have a space. Should the space be added for consistency?"

The data was vetted by multiple vetters in CLDR v32 contribution. This is a fair question to vetters. I'll post this question when we open up the survey tool for v34 to all pt-BR vetters.

Comment #4 seems to be just a misunderstanding.

NBSP will follow up in a separate ticket.

comment:7 in reply to: ↑ 2 Changed 5 months ago by kristi

Replying to alanhzhao@…:

Yeah, also make sure that space in all pt currency formats is actually U+00A0. I did a copy-paste from the browser, and it looks like the current version might be U+0020.

I checked the truck, and it's U+00A0. I don't know where you saw the U+0020. Please open a new ticket for it with the specifics.

comment:8 Changed 5 months ago by kristi

NBSP U+00A0 is in the format. Per TC discussion, this should already be handled at input, so please open a separate ticket if you see issues with that.

This ticket will focus on the Translation issues as outlined in Comment 6.

comment:9 Changed 5 weeks ago by kristi

  • Status changed from accepted to reviewing
  • Review set to kristi

Posted the in the Pt forum about the spacing issue for the vetter to decide and respond to this feedback. http://st.unicode.org/cldr-apps/v#/pt/Compact_Decimal_Formatting/5825fdcd5f32c291

comment:10 Changed 9 days ago by kristi

  • Summary changed from Short currency formats for pt to Short currency formats for pt (ST Forum)

comment:11 Changed 3 days ago by kristi

  • Status changed from reviewing to closed
  • Resolution set to fixed

Changes are captured in Survey tool with the space.

View

Add a comment

Modify Ticket

Action
as closed
Next status will be 'new'
Next status will be 'closed'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.