-
Notifications
You must be signed in to change notification settings - Fork 386
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
CLDR-17566 converting design proposals P3 (#3848)
- Loading branch information
Showing
5 changed files
with
767 additions
and
0 deletions.
There are no files selected for viewing
241 changes: 241 additions & 0 deletions
241
docs/site/development/development-process/design-proposals/day-period-design.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,241 @@ | ||
| --- | ||
| title: Day-Period Design | ||
| --- | ||
|
|
||
| # Day-Period Design | ||
|
|
||
| ## Problem: | ||
|
|
||
| The two part AM/PM day division is not universal and some cultures require greater granularity in day divisions to properly represent a time. For more information, please see CLDR bugs [169](http://unicode.org/cldr/trac/ticket/168), [992](http://unicode.org/cldr/trac/ticket/992), [1935](http://unicode.org/cldr/trac/ticket/1935). | ||
|
|
||
| ## Proposal | ||
|
|
||
| ### New dayPeriods.xml under Supplemental directory: | ||
|
|
||
| \<dayPeriodRuleSet> | ||
|
|
||
|  \<dayPeriodRules locales = "locale1 locale2 ... "> | ||
|
|
||
|   \<dayPeriodRule type = "typeName1" from | after = "HH:mm" to | before = "HH:mm"/> | ||
|
|
||
|   \<dayPeriodRule type = "typeName2" at = "HH:mm"/> | ||
|
|
||
| ..... | ||
|
|
||
|  \</dayPeriodRules> | ||
|
|
||
|  \<dayPeriodRules locales = "..." > | ||
|
|
||
| ... | ||
|
|
||
|  \</dayPeriodRules> | ||
|
|
||
| \</dayPeriodRuleSet> | ||
|
|
||
| ### New XML rules in locale xmls : | ||
|
|
||
| **\<dayPeriods>** | ||
|
|
||
|  **\<dayPeriodContext type="format">** | ||
|
|
||
|   **\<dayPeriodWidth type="wide">** | ||
|
|
||
|    \<**dayPeriod** type = "typeName1"> translation for typeName1\</dayPeriod> | ||
|
|
||
|    \<**dayPeriod** type = "typeName2"> translation for typeName2\</dayPeriod> | ||
|
|
||
| ... | ||
|
|
||
|   \<**/dayPeriodWidth>** | ||
|
|
||
|  **\</dayPeriodContext>** | ||
|
|
||
| ... | ||
|
|
||
| **\</dayPeriods>** | ||
|
|
||
| On "dayPeriods" in the future we can add an optional type if we need it, to support multiple rules for the same locale. For now we won't support that. | ||
|
|
||
| ### Definition and validation | ||
|
|
||
| 1. If locales are not defined in dayPeriods.xml, dayPeriods fallback to AM/PM. | ||
| 2. "from" and "to" are closed intervals(inclusive). | ||
| 3. "after" and "before" are open intervals(exclusive). | ||
| 4. "at" means starting time and end time are the same. | ||
| 5. There must be exactly one of {at, from, after} and exactly one of {at, to, before} for each dayPeriodRule. | ||
| 1. The set of dayPeriodRule's need to completely cover the 24 hours in a day (from 0:00 before 24:00), with **no** overlaps between each dayPeriodRule. | ||
| 6. Both hh:mm [period name] and hh [period name] can be parsed uniquely to HH:mm [period name]. | ||
| 1. For example, you can't have \<dayPeriod type = "morning" from="0:00" to="12:00"/> because "12 {morning}" would be ambiguous. | ||
| 7. One dayPeriodRule can cross midnight. For example: | ||
| 1. \<dayPeriodRule type="night" from="20:00" before="5:00"/> | ||
| 2. However, this should be avoided unless the alternative is awkward, because of ambiguities. While the use of the dayPeriods without hours is not recommended, they can be used. And if the user sees "Tuesday night" they may not think that that includes 1:00 am Tuesday. | ||
| 3. dayPeriodRule's with the same type are only allowed if they are not adjacent. Example: | ||
| - \<dayPeriod type = "twilight" from="5:00" to="7:00"/> | ||
| - \<dayPeriod type = "twilight" from="17:00" to="19:00"/> | ||
| 8. 24:00 is *only* allowed in *before*="24:00". A term for midnight should be avoided in the rules, because of ambiguity problems in most languages. | ||
| 1. *"Tuesday midnight" generally means at the end of the day on Tuesday (24:00)* | ||
| 2. *Most software does not format anything for 24:00, only for 00:00. And you don't want 00:00 Tuesday (the start of the day) to be formatted as midnight, meaning the end of the day.* | ||
| 9. When parsing, if the hour is present the dayperiod is checked for consistency. If there is no hour, the center of the first matching dayPeriodRule is chosen (starting from 0:00). | ||
| 10. Document that if people are rounding -- including the rounding done by the time format -- then the rounding needs to be done before the dayperiod is computed. | ||
|
|
||
| ### Examples: | ||
|
|
||
| New xml file: Supplemental/dayPeriods.xml | ||
|
|
||
| \<dayPeriodRuleSet> | ||
|
|
||
|  \<dayPeriodRules locales = "en"> \<!-- default for any locales not listed under other dayPeriods --> | ||
|
|
||
|   \<dayPeriodRule type = "am" from = "0:00" before="12:00"/> | ||
|
|
||
|   \<dayPeriodRule type = "pm" from = "12:00" to="24:00"/> | ||
|
|
||
|  \</dayPeriodRules> | ||
|
|
||
|  \<dayPeriodRules locales = "de it fr"> | ||
|
|
||
|   \<dayPeriodRule type = "earlyMorning" from="0:00" before="9:00"/> | ||
|
|
||
|   \<dayPeriodRule type = "morning" from="9:00" before="12:00"/> | ||
|
|
||
|   \<dayPeriodRule type = "noon" at = "12:00"/> | ||
|
|
||
|   \<dayPeriodRule type = "afternoon" after="12:00" before="17:00"/> | ||
|
|
||
|   \<dayPeriodRule type = "evening" from="17:00" before="21:00"/> | ||
|
|
||
|   \<dayPeriodRule type = "night" from="21:00" before="24:00"/> | ||
|
|
||
|  \</dayPeriodRules> | ||
|
|
||
|  \<dayPeriodRules locales = "zh"> | ||
|
|
||
|   \<dayPeriodRule type = "weeHours" from="00:00" before="4:00"/> | ||
|
|
||
|   \<dayPeriodRule type = "earlyMorning" from="4:00" before="6:00"/> | ||
|
|
||
|   \<dayPeriodRule type = "morning" from="6:00" before="12:00"/> | ||
|
|
||
|   \<dayPeriodRule type = "midMay" from="12:00" before="13:00"/> | ||
|
|
||
|   \<dayPeriodRule type = "afternoon" from="13:00" before="18:00"/> | ||
|
|
||
|   \<dayPeriodRule type = "night" from="18:00" before="24:00"/> | ||
|
|
||
|  \</dayPeriodRules> | ||
|
|
||
| **. . .** | ||
|
|
||
| \</dayPeriodRuleSet> | ||
|
|
||
| Examples in locale XML files: | ||
|
|
||
| In en locale file(en.xml) | ||
|
|
||
| \<dayPeriods> | ||
|
|
||
|  **\<dayPeriodContext type="format">** | ||
|
|
||
|   **\<dayPeriodWidth type="wide">** | ||
|
|
||
|    \<dayPeriod type = "am">AM\</dayPeriod> | ||
|
|
||
|    \<dayPeriod type = "am" alt="variant">a.m.\</dayPeriod> | ||
|
|
||
|    \<dayPeriod type = "pm">PM\</dayPeriod> | ||
|
|
||
|    \<dayPeriod type = "pm" alt="variant">p.m.\</dayPeriod> | ||
|
|
||
|   \<**/dayPeriodWidth>** | ||
|
|
||
|  **\</dayPeriodContext>** | ||
|
|
||
| \</dayPeriods> | ||
|
|
||
| // was: | ||
|
|
||
|   \<am>AM\</am> | ||
|
|
||
|   \<am alt="variant">a.m.\</am> | ||
|
|
||
|   \<pm>PM\</pm> | ||
|
|
||
|   \<pm alt="variant">p.m.\</pm> | ||
|
|
||
| *Also, in root, replace all instances (except in Gregorian) of* | ||
|
|
||
|   \<am>AM\</am> | ||
|
|
||
|   \<pm>PM\</pm> | ||
|
|
||
| *by* | ||
|
|
||
|   \<dayPeriods> | ||
|
|
||
|    \<alias source="locale" path="../../calendar[@type='gregorian']/dayPeriods"/> | ||
|
|
||
|   \</dayPeriods> | ||
|
|
||
| In de locale file(de.xml): | ||
|
|
||
| \<dayPeriods> | ||
|
|
||
|  **\<dayPeriodContext type="format">** | ||
|
|
||
|   **\<dayPeriodWidth type="wide">** | ||
|
|
||
|    \<dayPeriod type = "earlyMorning">morgens\</dayPeriod> | ||
|
|
||
|    \<dayPeriod type = "morning">vormittags\</dayPeriod> | ||
|
|
||
|    \<dayPeriod type = "noon">Mittag\</dayPeriod> | ||
|
|
||
|    \<dayPeriod type = "afternoon">nachmittags\</dayPeriod> | ||
|
|
||
|    \<dayPeriod type = "evening">abends\</dayPeriod> | ||
|
|
||
|    \<dayPeriod type = "night">nachts\</dayPeriod> | ||
|
|
||
|   \<**/dayPeriodWidth>** | ||
|
|
||
|  **\</dayPeriodContext>** | ||
|
|
||
| \</dayPeriods> | ||
|
|
||
|
|
||
|
|
||
| In zh locale file(zh.xml): | ||
|
|
||
| \<dayPeriods> | ||
|
|
||
|  **\<dayPeriodContext type="format">** | ||
|
|
||
|   **\<dayPeriodWidth type="wide">** | ||
|
|
||
|    \<dayPeriod type = "weeHours">凌晨\</dayPeriod> | ||
|
|
||
|    \<dayPeriod type = "earlyMorning">清晨\</dayPeriod> | ||
|
|
||
|    \<dayPeriod type = "morning">上午\</dayPeriod> | ||
|
|
||
|    \<dayPeriod type = "midDay">中午\</dayPeriod> | ||
|
|
||
|    \<dayPeriod type = "afternoon">下午\</dayPeriod> | ||
|
|
||
|    \<dayPeriod type = "night">晚上\</dayPeriod> | ||
|
|
||
|   \<**/dayPeriodWidth>** | ||
|
|
||
|  **\</dayPeriodContext>** | ||
|
|
||
| \</dayPeriods> | ||
|
|
||
| Code changes | ||
|
|
||
| - The example code needs to be changed to get the AM/PM data from the new location (high priority) | ||
| - LDML2ICU needs to change to map the new data. | ||
| - ICU code needs to use the new structure | ||
| - We need to have a chart for the dayPeriodRules, like we do for plurals. | ||
| - Add invariant testing in CheckAttributes. | ||
|
|
||
|  |
35 changes: 35 additions & 0 deletions
35
...pment/development-process/design-proposals/delimiter-quotation-mark-proposal.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| --- | ||
| title: Delimiter (Quotation Mark) Proposal | ||
| --- | ||
|
|
||
| # Delimiter (Quotation Mark) Proposal | ||
|
|
||
| ## Delimiter Consistency | ||
|
|
||
| The following is a proposal for how to handle the delimiter issues in CLDR, raised in bug [http://unicode.org/cldr/trac/ticket/4201](http://unicode.org/cldr/trac/ticket/4201). | ||
|
|
||
| There are qute a number of problems in our delimiter data. Most of these are in the ‘lesser vetted’ languages, but some are in major languages. Problems include use of ASCII quotes, and obvious inconsistencies in data. | ||
|
|
||
| The goal for the v49 release is to at least have consistent data, then have the translators look at the changes in the data submission phase for v50. | ||
|
|
||
| **Data Cleanup.** I went through the data, and cleaned up obvious problems (such as a generic ASCII quote on one side, and a curly quote on the other). I then compared it to the Wikipedia data where available; if there was a difference between CLDR and Wikipedia, I looked for original sources on the web. It is often a bit tricky, since there are be variant practices in many languages. The goal is to have it to be the most customary usage, but often it may not be clear which variant predominates. | ||
|
|
||
| Note that for a great many locales (especially African ones), there isn’t much to go on, so I left it at minor cleanup. I suspect that many of them are problematic; it might be worth asking whether they follow the conventions of another language, like French, rather than asking what the characters are. See below for the results. | ||
|
|
||
| **Bidi.** I tried to gauge from sources what the practice is. However, it is the visual practice, so we have two alternatives. | ||
|
|
||
| 1. Use the ASCII ugly quotes | ||
| 2. Reverse the two, which would be correct with all BIDI or with correct markup. | ||
|
|
||
| Personally, I lean towards #2. | ||
|
|
||
| The first sheet has recommendations for changing; the others are just scratch sheets. | ||
|
|
||
| - The Proposed columns contain the recommendations for v49. | ||
| - The Style columns just show a label for each type, since it is sometimes hard to distinguish the directions of the marks. | ||
| - The Old columns show the current values. | ||
| - And the last column shows the locales in question. | ||
|
|
||
| [**Quotation (Delimiter) Proposal**](https://docs.google.com/spreadsheets/d/1_7vjBSmjlmevIQfpM4xX1yMGYQdibd6h8PTrQEPzzkQ/edit?gid=2#gid=2) | ||
|
|
||
|  |
Oops, something went wrong.