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

CLDR Ticket #6773(closed defect: fixed)

Opened 5 years ago

Last modified 4 years ago

ru: AM/PM should be untranslated in Russian

Reported by: fredrik Owned by: fredrik
Component: main Data Locale: ru
Phase: Review: pedberg
Weeks: Data Xpath:
Xref:

Description

We have several reports that the AM/PM indicators should be left in English for Russian. Right now we have a couple of different variants floating around:

<field type="dayperiod">

<displayName>ДП/ПП</displayName>

and

<dayPeriods>

<dayPeriodContext type="format">

<dayPeriodWidth type="abbreviated">

<dayPeriod type="am" draft="contributed">до полудня</dayPeriod>
<dayPeriod type="pm" draft="contributed">после полудня</dayPeriod>

</dayPeriodWidth>
<dayPeriodWidth type="narrow">

<dayPeriod type="am" draft="contributed">дп</dayPeriod>
<dayPeriod type="pm" draft="contributed">пп</dayPeriod>

</dayPeriodWidth>
<dayPeriodWidth type="wide">

<dayPeriod type="am">до полудня</dayPeriod>
<dayPeriod type="pm">после полудня</dayPeriod>

</dayPeriodWidth>

</dayPeriodContext>

</dayPeriods>

Russia typically uses the 24-hour clock, but when they do have 12-hour format, they use AM/PM in latin script. Also the current spelt out version cause clippings in UI.

Suggest we revert all of these to AM/PM.

Apple ref: <rdar://problem/14619901>

Attachments

Change History

comment:1 Changed 5 years ago by emmons

  • Owner changed from anybody to fredrik
  • Priority changed from assess to medium
  • Status changed from new to assigned
  • Milestone changed from UNSCH to 25M1

comment:2 Changed 5 years ago by fredrik

  • Review set to pedberg

comment:3 Changed 5 years ago by pedberg

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

comment:4 Changed 5 years ago by pedberg

For the format-style dayPeriods, narrow falls back to abbreviated, which falls back to wide. If they are all the same, from a data standpoint we can just provide the wide version. However, providing all of them does emphasize that AM/PM is desired for all widths, so it is probably best to keep the data for all widths in CLDR. We should eliminate the redundant data when converting for ICU (there is a separate bug for that).

comment:5 Changed 4 years ago by emmons

  • Milestone 25M1 deleted

Milestone 25M1 deleted

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.