Skip to content
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

Merged
merged 2 commits into from
Mar 3, 2024

Conversation

srl295
Copy link
Member

@srl295 srl295 commented Feb 28, 2024

CLDR-17423

  • This PR completes the ticket.

ALLOW_MANY_COMMITS=true

- final spec will be poured in as CLDR-17424
@srl295 srl295 self-assigned this Feb 28, 2024
@srl295
Copy link
Member Author

srl295 commented Feb 28, 2024

fyi @aphillips @eemeli

Copy link
Member

@aphillips aphillips left a 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.

docs/ldml/tr35-collation.md Outdated Show resolved Hide resolved

|Version|45 (draft) |
|-------|------------------------|
|Editors|Addison Phillips and [other CLDR committee members](tr35.md#Acknowledgments)|
Copy link
Member

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.

Copy link
Member Author

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

Copy link
Member

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)]._
Copy link
Member

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.

Copy link
Member Author

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

@macchiati
Copy link
Member

macchiati commented Feb 29, 2024 via email

@srl295 srl295 requested a review from aphillips February 29, 2024 20:16
@srl295
Copy link
Member Author

srl295 commented Feb 29, 2024

@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.

@srl295 srl295 requested review from a team and removed request for aphillips February 29, 2024 20:18
@aphillips
Copy link
Member

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.
Copy link
Member

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?

Suggested change
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.

Copy link
Member Author

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.

Copy link
Member Author

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.

Copy link
Member

@aphillips aphillips left a 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.

Copy link
Member

@macchiati macchiati left a 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.

@macchiati macchiati merged commit 26faa9f into unicode-org:main Mar 3, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants