Skip to content

Commit 8aedd9f

Browse files
authored
CLDR-18209 spec: split Modifications, Acknowledgments sections into Appendicies (#4902)
1 parent 440009e commit 8aedd9f

13 files changed

+455
-216
lines changed

docs/ldml/tr35-acknowledgments.md

Lines changed: 96 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
1+
## Unicode Technical Standard #35
2+
3+
# Unicode Locale Data Markup Language (LDML)<br/>Appendix B: Acknowledgments
4+
5+
|Version|48 (draft)|
6+
|-------|----------|
7+
|Editors|<a href="tr35-acknowledgments.md#acknowledgments">CLDR committee members|
8+
9+
For the full header, summary, and status, see [Part 1: Core](tr35.md).
10+
11+
### _Summary_
12+
13+
This is a partial document, describing only the acknowledgments of contributors to LDML. For the other parts of the LDML see the [main LDML document](tr35.md) and the links above.
14+
15+
### _Status_
16+
17+
_This is a draft document which may be updated, replaced, or superseded by other documents at any time.
18+
Publication does not imply endorsement by the Unicode Consortium.
19+
This is not a stable document; it is inappropriate to cite this document as other than a work in progress._
20+
21+
<!-- _This document has been reviewed by Unicode members and other interested parties, and has been approved for publication by the Unicode Consortium.
22+
This is a stable document and may be used as reference material or cited as a normative reference by other specifications._ -->
23+
24+
> _**A Unicode Technical Standard (UTS)** is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS._
25+
26+
_Please submit corrigenda and other comments with the CLDR bug reporting form [[Bugs](https://cldr.unicode.org/index/bug-reports)].
27+
Related information that is useful in understanding this document is found in the [References](#References).
28+
For the latest version of the Unicode Standard see [[Unicode](https://www.unicode.org/versions/latest/)].
29+
For more information see [About Unicode Technical Reports](https://www.unicode.org/reports/about-reports.html) and the [Specifications FAQ](https://www.unicode.org/faq/specifications.html).
30+
Unicode Technical Reports are governed by the Unicode [Terms of Use](https://www.unicode.org/copyright.html)._
31+
32+
## Parts
33+
34+
The LDML specification is divided into the following parts:
35+
36+
* Part 1: [Core](tr35.md#Contents) (languages, locales, basic structure)
37+
* Part 2: [General](tr35-general.md#Contents) (display names & transforms, etc.)
38+
* Part 3: [Numbers](tr35-numbers.md#Contents) (number & currency formatting)
39+
* Part 4: [Dates](tr35-dates.md#Contents) (date, time, time zone formatting)
40+
* Part 5: [Collation](tr35-collation.md#Contents) (sorting, searching, grouping)
41+
* Part 6: [Supplemental](tr35-info.md#Contents) (supplemental data)
42+
* Part 7: [Keyboards](tr35-keyboards.md#Contents) (keyboard mappings)
43+
* Part 8: [Person Names](tr35-personNames.md#Contents) (person names)
44+
* Part 9: [MessageFormat](tr35-messageFormat.md#Contents) (message format)
45+
* Appendix A: [Modifications](tr35-modifications.md#modifications)
46+
* Appendix B: [Acknowledgments](tr35-acknowledgments.md#acknowledgments)
47+
48+
## <a name="Contents" href="#Contents">Contents of Appendix B, Acknowledgments</a>
49+
50+
* [Acknowledgments](#acknowledgments)
51+
52+
## Acknowledgments
53+
54+
Special thanks to the following people for their continuing overall contributions to the CLDR project, and for their specific contributions in the following areas. These descriptions only touch on the many contributions that they have made.
55+
56+
* Mark Davis for creating the initial version of LDML, and adding to and maintaining this specification, and for his work on the LDML code and tests, much of the supplemental data and overall structure, and transforms and keyboards.
57+
* John Emmons for the POSIX conversion tool and metazones.
58+
* Deborah Goldsmith for her contributions to LDML architecture and this specification.
59+
* Chris Hansten for coordinating and managing data submissions and vetting.
60+
* Erkki Kolehmainen and his team for their work on Finnish.
61+
* Steven R. Loomis for development of the survey tool and database management.
62+
* Peter Nugent for his contributions to the POSIX tool and from Open Office, and for coordinating and managing data submissions and vetting.
63+
* George Rhoten for his work on currencies.
64+
* Roozbeh Pournader (روزبه پورنادر) for his work on South Asian countries.
65+
* Ram Viswanadha (రఘురామ్ విశ్వనాధ) for all of his work on LDML code and data integration, and for coordinating and managing data submissions and vetting.
66+
* Vladimir Weinstein (Владимир Вајнштајн) for his work on collation.
67+
* Yoshito Umaoka (馬岡 由人) for his work on the timezone architecture.
68+
* Rick McGowan for his work gathering language, script and region data.
69+
* Xiaomei Ji (吉晓梅) for her work on time intervals and plural formatting.
70+
* David Bertoni for his contributions to the conversion tools.
71+
* Mike Tardif for reviewing this specification and for coordinating and vetting data submissions.
72+
* Peter Edberg for work on this specification, monthPatterns, cyclicNameSets, contextTransforms and other items.
73+
* Raymond Wainman and Cibu Johny for their work on keyboards.
74+
* Jennifer Chye for her contributions to the conversion tools.
75+
* Markus Scherer for a major rewrite of Part 5, Collation.
76+
* [Shane Carr](https://www.sffc.xyz/) for his work on numbers and measurement units.
77+
* Robin Leroy for his work on compact plurals: Part 3, [Language Plural Rules](tr35-numbers.md#Language_Plural_Rules)
78+
* Rich Gillam for work on Person Names.
79+
* Alex Kolisnychenko for work on Person Names.
80+
* Mike McKenna for work on Person Names.
81+
82+
* * *
83+
84+
© 2001–2025 Unicode, Inc.
85+
This publication is protected by copyright, and permission must be obtained from Unicode, Inc.
86+
prior to any reproduction, modification, or other use not permitted by the [Terms of Use](https://www.unicode.org/copyright.html).
87+
Specifically, you may make copies of this publication and may annotate and translate it solely for personal or internal business purposes and not for public distribution,
88+
provided that any such permitted copies and modifications fully reproduce all copyright and other legal notices contained in the original.
89+
You may not make copies of or modifications to this publication for public distribution, or incorporate it in whole or in part into any product or publication without the express written permission of Unicode.
90+
91+
Use of all Unicode Products, including this publication, is governed by the Unicode [Terms of Use](https://www.unicode.org/copyright.html).
92+
The authors, contributors, and publishers have taken care in the preparation of this publication,
93+
but make no express or implied representation or warranty of any kind and assume no responsibility or liability for errors or omissions or for consequential or incidental damages that may arise therefrom.
94+
This publication is provided “AS-IS” without charge as a convenience to users.
95+
96+
Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. in the United States and other countries.

docs/ldml/tr35-collation.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
|Version|48 (draft) |
66
|-------|----------------|
7-
|Editors|Markus Scherer (<a href="mailto:[email protected]">[email protected]</a>) and <a href="tr35.md#Acknowledgments">other CLDR committee members</a>|
7+
|Editors|Markus Scherer (<a href="mailto:[email protected]">[email protected]</a>) and <a href="tr35-acknowledgments.md#acknowledgments">other CLDR committee members</a>|
88

99
For the full header, summary, and status, see [Part 1: Core](tr35.md).
1010

@@ -31,7 +31,7 @@ For the latest version of the Unicode Standard see [[Unicode](https://www.unicod
3131
For more information see [About Unicode Technical Reports](https://www.unicode.org/reports/about-reports.html) and the [Specifications FAQ](https://www.unicode.org/faq/specifications.html).
3232
Unicode Technical Reports are governed by the Unicode [Terms of Use](https://www.unicode.org/copyright.html)._
3333

34-
## <a name="Parts" href="#Parts">Parts</a>
34+
## Parts
3535

3636
The LDML specification is divided into the following parts:
3737

@@ -44,6 +44,8 @@ The LDML specification is divided into the following parts:
4444
* Part 7: [Keyboards](tr35-keyboards.md#Contents) (keyboard mappings)
4545
* Part 8: [Person Names](tr35-personNames.md#Contents) (person names)
4646
* Part 9: [MessageFormat](tr35-messageFormat.md#Contents) (message format)
47+
* Appendix A: [Modifications](tr35-modifications.md#modifications)
48+
* Appendix B: [Acknowledgments](tr35-acknowledgments.md#acknowledgments)
4749

4850
## <a name="Contents" href="#Contents">Contents of Part 5, Collation</a>
4951

docs/ldml/tr35-dates.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
|Version|48 (draft) |
66
|-------|------------------|
7-
|Editors|Peter Edberg and <a href="tr35.md#Acknowledgments">other CLDR committee members</a>|
7+
|Editors|Peter Edberg and <a href="tr35-acknowledgments.md#acknowledgments">other CLDR committee members</a>|
88

99
For the full header, summary, and status, see [Part 1: Core](tr35.md).
1010

@@ -31,7 +31,7 @@ For the latest version of the Unicode Standard see [[Unicode](https://www.unicod
3131
For more information see [About Unicode Technical Reports](https://www.unicode.org/reports/about-reports.html) and the [Specifications FAQ](https://www.unicode.org/faq/specifications.html).
3232
Unicode Technical Reports are governed by the Unicode [Terms of Use](https://www.unicode.org/copyright.html)._
3333

34-
## <a name="Parts" href="#Parts">Parts</a>
34+
## Parts
3535

3636
The LDML specification is divided into the following parts:
3737

@@ -44,6 +44,8 @@ The LDML specification is divided into the following parts:
4444
* Part 7: [Keyboards](tr35-keyboards.md#Contents) (keyboard mappings)
4545
* Part 8: [Person Names](tr35-personNames.md#Contents) (person names)
4646
* Part 9: [MessageFormat](tr35-messageFormat.md#Contents) (message format)
47+
* Appendix A: [Modifications](tr35-modifications.md#modifications)
48+
* Appendix B: [Acknowledgments](tr35-acknowledgments.md#acknowledgments)
4749

4850
## <a name="Contents" href="#Contents">Contents of Part 4, Dates</a>
4951

@@ -1708,7 +1710,7 @@ Note: A generic location format is constructed by a part of time zone ID represe
17081710
* "Pacific Daylight Time" (long)
17091711
* "PDT" (short)
17101712

1711-
**Localized GMT format:** A constant, specific offset from GMT (or UTC), which may be in a translated form. There are two styles for this:
1713+
**Localized GMT format:** A constant, specific offset from GMT (or UTC), which may be in a translated form. There are two styles for this:
17121714

17131715
The first is used when there is an explicit offset from GMT; this style is specified by the `<gmtFormat>` element and `<hourFormat>` element. The long format always uses 2-digit hours field and minutes field, with optional 2-digit seconds field. The short format is intended for the shortest representation and uses hour fields without leading zero, with optional 2-digit minutes and seconds fields. The digits used for hours, minutes and seconds fields in this format are the locale's default decimal digits:
17141716

@@ -1899,7 +1901,7 @@ Some of the examples are drawn from real data, while others are for illustration
18991901
* "Pacific Time (Whitehorse)"
19001902
5. For the location formats (generic or specific):
19011903
1. Get the _regionFormat_ format according to type (generic, standard, or daylight).
1902-
2. Determine whether there is only one timezone in the region associated with the timezone (see [Time Zone Identifiers](tr35.md#Time_Zone_Identifiers)).
1904+
2. Determine whether there is only one timezone in the region associated with the timezone (see [Time Zone Identifiers](tr35.md#Time_Zone_Identifiers)).
19031905
1. If there is only one timezone or if the zone id is in the `<primaryZones>` list, continue with short country name, if it exists, otherwise the country name.
19041906
2. Otherwise, continue with the localized name of the exemplar city for the zone.
19051907
3. Format the region format obtained in step 1 with the location obtained in step 2.

0 commit comments

Comments
 (0)