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

CLDR Ticket #9717(design docs)

Opened 16 months ago

Last modified 4 weeks ago

ST confusion about dayPeriods not define in English

Reported by: pedberg Owned by: kristi
Component: other Data Locale:
Phase: dvet Review:
Weeks: Data Xpath:
Xref:

Description

The way we display dayPeriods in Survey Tool causes vetter confusion for dayPeriods that are not defined for English. Consider the following example for morning1 and morning2; the latter is defined for Swahili, but not English, as follows:

# en, format & standalone
<dayPeriodRule type="morning1" from="06:00" before="12:00"/> <!-- morning -->
# sw, format & standalone
<dayPeriodRules locales="sw">
<dayPeriodRule type="morning1" from="04:00" before="07:00"/> <!-- alfajiri = "dawn" -->
<dayPeriodRule type="morning2" from="07:00" before="12:00"/> <!-- asubuhi = "morning" -->

The ST display is shown in the attached screenshot. In the main Swahili locale, for morning1, even though the English shown is "morning", the vetters have correctly chosen the Swahili word for "dawn" (alfajiri), and for morning2 (empty in English) they chose the Swahili word for "morning" (asubuhi)

But in the sw_KE sub locale, the vetter tried to translate morning1 "morning" using the equivalent Swahili word asubuhi, which leads to an error because it conflicts with the inherited translation for morning2. See second screenshot.

Similar things happened in several other regional sublocales, such as zh_Hant_HK; the vetters are really only considering the translations that appear to be mismatched. We need to find a way to suggest that they should not necessarily be translating the English name.

Attachments

ST30-sw-dayPeriods.png (52.6 KB) - added by pedberg 16 months ago.
ST30-sw-dayPeriods
ST30-sw_KE-dayPeriods.png (59.0 KB) - added by pedberg 16 months ago.
ST30-sw_KE-dayPeriods

Change History

Changed 16 months ago by pedberg

ST30-sw-dayPeriods

Changed 16 months ago by pedberg

ST30-sw_KE-dayPeriods

comment:1 Changed 16 months ago by pedberg

  • Owner changed from anybody to emmons
  • Status changed from new to accepted
  • Milestone changed from UNSCH to 31

comment:2 Changed 11 months ago by emmons

  • Phase changed from dsub to rc

comment:3 Changed 11 months ago by emmons

  • Owner emmons deleted
  • Phase changed from rc to dsub
  • Status changed from accepted to new
  • Milestone changed from 31 to 32

No way I'm going to get to this anytime soon.

comment:4 Changed 9 months ago by emmons

  • Owner set to mark
  • Status changed from new to accepted

comment:5 Changed 7 months ago by mark

  • Owner changed from mark to kristi

Documentation

comment:6 Changed 5 months ago by kristi

  • Phase changed from dsub to spec-beta

comment:7 Changed 4 months ago by kristi

We could handle with some Survey tool UI changes or in documentation:

  1. Propose change in the survey tool. For example, instead of leaving the English column blank, we could have <Not available in English>; and hover over could show the day period that the translation should target.
  1. Document in the translation guide (http://cldr.unicode.org/translation/date-time-names#TOC-Day-Periods-AM-PM-etc.- ). Information about Day Periods being language specific and how to handle translations when English is empty is already there; we should figure out why it's not working for vetters and update.

comment:8 Changed 4 months ago by kristi

  • Milestone changed from 32 to 33

Created a separate ticket for #1 http://unicode.org/cldr/trac/ticket/10562

Will address #2 with this ticket prior to v34 contribution cycle.

comment:9 Changed 4 months ago by kristi

  • Type changed from survey to docs
  • Component changed from survey-ui-design to other

comment:10 Changed 4 weeks ago by kristi

  • Keywords Comitted added
  • Phase changed from spec-beta to dvet
  • Status changed from accepted to design
View

Add a comment

Modify Ticket

Action
as design
Author


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

 
Note: See TracTickets for help on using tickets.