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

CLDR Ticket #8481(design)

Opened 4 years ago

Last modified 4 months ago

Introduce 'categories/context' for region display names

Reported by: jungshik Owned by: pedberg
Component: to-assess Data Locale:
Phase: rc Review:
Weeks: Data Xpath:


Description (last modified by jungshik) (diff)

Some region names have to be different depending on their usage/context.

For instance, in the pull down menu, 'Korea (South)' or 'Korea, South' would be the best for KR while 'South Korea' (the current CLDR value in English locale) would be best in a 'sentence'.


Change History

comment:1 Changed 4 years ago by jungshik

  • Description modified (diff)

comment:2 Changed 4 years ago by jungshik

We can also think of two 'orthogonal' attributes, 'context/usage' (ui vs in-sentence) and 'official_vs_casual/colloquial'. For KR,

  1. menu, casual : Korea (South)
  2. menu, official: Korea (Republic of) or 'Korea, Republic of'
  3. in-sentence, casual : South Korea
  4. in-stence, official : Republic of Korea

For most web products/computer applications, 'official' wouldn't be used much.

And, then, there's a 'beginning of sentenc' vs middle of sentence' attribute. It begins to explode ....

Last edited 4 years ago by jungshik (previous) (diff)

comment:3 Changed 4 years ago by jungshik

  • Component changed from unknown to main

comment:4 Changed 4 years ago by emmons

  • Status changed from new to design
  • Priority changed from assess to medium
  • Phase changed from dsub to rc
  • Milestone changed from UNSCH to 29
  • Owner changed from anybody to pedberg
  • type changed from spec to data

comment:5 Changed 4 years ago by pedberg

Also need to address e.g. gender variants for language names, etc. Look at a more comprehensive solution that can address those issues as well.

comment:6 Changed 3 years ago by emmons

  • Milestone changed from 29 to upcoming

comment:7 Changed 11 months ago by jungshik

  • Xref set to 3958

I merged ticket:3958 to this ticket without reading my initial ticket description. It seems to be a bit different. However, resolving this ticket can be used for the Chrome's use case in ticket:3958. So, I'll keep it duped to this one.

comment:8 Changed 11 months ago by jungshik

  • Keywords chrome added

comment:9 Changed 5 months ago by pedberg

  • Milestone changed from upcoming to UNSCH

CLDR 34 BRS closing item, move all upcoming → UNSCH

comment:10 Changed 5 months ago by mark

  • Component changed from main to other

comment:11 Changed 4 months ago by mark

  • Component changed from other to to-assess

Add a comment

Modify Ticket

as design

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

Note: See TracTickets for help on using tickets.