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

CLDR Ticket #9665(closed docs: as-designed)

Opened 23 months ago

Last modified 3 months ago

Document for vetters that the ISO currency code is always available, in addition to the symbol

Reported by: pedberg Owned by: kristi
Component: translation-guide Data Locale:
Phase: dvet Review: kristi
Weeks: Data Xpath:
Xref:

Description

To help alleviate confusion as in http://st.unicode.org/cldr-apps/v#/pl/C_SEEurope/4c90f7e23a1994cc, need to document that the 3-letter currency code is always available to CLDR clients in addition to whatever symbol is specified in the symbol field

Attachments

Change History

comment:1 Changed 23 months ago by pedberg

  • Owner changed from anybody to pedberg
  • Phase changed from dsub to spec-beta
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 30

comment:2 Changed 21 months ago by pedberg

  • Phase changed from spec-beta to dsub
  • Priority changed from assess to major
  • Milestone changed from 30 to 31

This is vetter documentation, move to 31

comment:3 Changed 17 months ago by pedberg

  • Phase changed from dsub to rc

comment:4 Changed 15 months ago by pedberg

  • Milestone changed from 31 to 32

comment:5 Changed 15 months ago by kristi

  • Cc kristi added

comment:6 Changed 15 months ago by kristi

  • Phase changed from rc to dsub

changing to dsub since the instruction will target linguists working during the submission phase.

comment:7 Changed 14 months ago by pedberg

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

There already was some information about this in the first table entry under http://cldr.unicode.org/translation/currency-names, but I edited the information slightly with the hope of making it more clear.

comment:8 Changed 9 months ago by kristi

  • Status changed from reviewing to reviewfeedback

The documentation is good, but I don't think the action for vetters is clear when you say "there is no need to "translate" them in a locale."

How about:
"You can vote for the ISO 4217 codes if that is the most commonly recognized. Or leave it as Abstain"??

Not really sure about the "or leave it as Abstain" here since we ask vetters to vote without skipping.

What action do you think vetters should do if they don't "translate"?

comment:9 Changed 9 months ago by pedberg

  • Phase changed from dsub to spec-beta

comment:10 Changed 9 months ago by pedberg

  • Phase changed from spec-beta to dsub
  • Milestone changed from 32 to 33

comment:11 Changed 7 months ago by kristi

  • Owner changed from pedberg to kristi
  • Phase changed from dsub to dvet
  • Status changed from reviewfeedback to accepted

comment:12 Changed 5 months ago by kristi

  • Component changed from currency to translation-guide

comment:13 Changed 3 months ago by kristi

  • Status changed from accepted to closed
  • Resolution set to as-designed

Closing since based on Comment 8. I take that we don't need to provide any additional clarity that was suggested.

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.