-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLDR-17423 Placeholder for MessageFormat 2.0 spec, part 9 #3541
Conversation
- final spec will be poured in as CLDR-17424
fyi @aphillips @eemeli |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this. Some questions follow.
|
||
|Version|45 (draft) | | ||
|-------|------------------------| | ||
|Editors|Addison Phillips and [other CLDR committee members](tr35.md#Acknowledgments)| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to develop a separate acknowledgements section?
Also, how many names can we list as editors? A core group of contributors might be nice to have here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could be a future update - past Monday's deadline
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair enough for both of these questions. But I'd still like to know the answer (might not be you who can answer it). I can update both of these by Monday.
|
||
> _**A Unicode Technical Standard (UTS)** is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS._ | ||
|
||
_Please submit corrigenda and other comments with the CLDR bug reporting form [[Bugs](tr35.md#Bugs)]. Related information that is useful in understanding this document is found in the [References](tr35.md#References). For the latest version of the Unicode Standard see [[Unicode](tr35.md#Unicode)]. For a list of current Unicode Technical Reports see [[Reports](tr35.md#Reports)]. For more information about versions of the Unicode Standard, see [[Versions](tr35.md#Versions)]._ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we change this bit of boilerplate? We'll want to use a difference mechanism.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could be a future update - past Monday's deadline
- Message Format to MessageFormat
We have two acknowledgements lists.
In the spec: https://unicode.org/reports/tr35/#Acknowledgments
The big list: https://cldr.unicode.org/index/acknowledgments
We can add people to the spec or to both. The spec one tends to be major,
and also can list what they contributed. If you feel like those choices are
not optimal, we can discuss other options in the TC.
…On Wed, Feb 28, 2024 at 4:23 PM Addison Phillips ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In docs/ldml/tr35-messageFormat.md
<#3541 (comment)>:
> @@ -0,0 +1,69 @@
+## Unicode Technical Standard #35
+
+# Unicode Locale Data Markup Language (LDML)<br/>Part 9: Message Format
+
+|Version|45 (draft) |
+|-------|------------------------|
+|Editors|Addison Phillips and [other CLDR committee members](tr35.md#Acknowledgments)|
Fair enough for both of these questions. But I'd still like to know the
answer (might not be you who can answer it). I can update both of these by
Monday.
—
Reply to this email directly, view it on GitHub
<#3541 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJLEMEPT3VACN3DBMBQWA3YV7DADAVCNFSM6AAAAABD63O7UKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSMBXGY4TMMZZGY>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
@aphillips we also might consider putting this in, so that there's a part 9 to start pointing people to come Monday.. we'll already have a followon PR to put the actual text in, can easily make other updates. |
This PR is fine by me. I was hoping to get my paragraph out of message-format-wg#697, but we can change whatever we need to after Monday, I presume. |
|
||
This specification defines the data model, syntax, processing, and conformance requirements for the next generation of dynamic messages. | ||
|
||
This is a partial document, describing only those parts of the LDML that are relevant for message format. For the other parts of the LDML see the [main LDML document](tr35.md) and the links above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence doesn't make sense? There are no parts of LDML here, just the MF2 spec?
This is a partial document, describing only those parts of the LDML that are relevant for message format. For the other parts of the LDML see the [main LDML document](tr35.md) and the links above. | |
For the other parts of LDML see [main LDML document](tr35.md) and the links above. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, there are other parts of LDML. This is part 9 of 9 parts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all other parts have the same wording.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving so we have something on Monday, 4 March.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved (with Addison's agreement) as per email discussion.
CLDR-17423
ALLOW_MANY_COMMITS=true