Skip to content

Preparing the specification for LDML47 release #1007

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 29 commits into from
Feb 17, 2025
Merged

Preparing the specification for LDML47 release #1007

merged 29 commits into from
Feb 17, 2025

Conversation

@aphillips
Copy link
Member

@aphillips aphillips commented Feb 15, 2025 •
edited
Loading

This PR includes the changes necessary to prepare the specification for LDML47, which is the first Stable release of MF2.

Normative changes:

  • Activate the stability policy

Non-normative changes:

  • Fix header indentation to support ToC generation
  • Disambiguate headers where necessary

Fixes #1001

@aphillips
Preparing the specification for LDML47 release
0f2ca73 
This PR includes the changes necessary to prepare the specification for LDML47, which is the first Stable release of MF2.

Normative changes:
- Activate the stability policy

Non-normative changes:
- 


Fixes #1001
@aphillips
Update syntax.md
5e8783e
@aphillips
Update formatting.md
ee1c5c0 
- indent headers as appropriate
- make headings unique in the spec to assist with linking and TOC generation
@aphillips
Update appendices.md
70f25b2
@aphillips
Update errors.md
9a227bf
@aphillips
Update u-namespace.md
dc1d8b4
@aphillips
Update README.md
162e462
@aphillips aphillips added normative Issue affects normative text in the specification specification Issue affects the specification LDML47 labels Feb 15, 2025
@aphillips aphillips marked this pull request as ready for review February 15, 2025 19:26
macchiati
macchiati reviewed Feb 16, 2025
View reviewed changes
macchiati
macchiati reviewed Feb 16, 2025
View reviewed changes
eemeli
eemeli requested changes Feb 16, 2025
View reviewed changes
@aphillips aphillips requested a review from eemeli February 16, 2025 20:19
@macchiati
Copy link
Member

macchiati commented Feb 17, 2025

Another copy editing issue:

  1. Sometimes the wording is "MessageFormat 2.0" and sometimes "MessageFormat 2". It should be consistent.
  2. I think it is vital in the intro to use the term, and contrast it with "MessageFormat 1.0". We might even expand on the following (either in place or in an appendix) to provide context and contrast with MF 1.0.

The document is the successor to ICU MessageFormat,
henceforth called ICU MessageFormat 1.0.

  1. However, I think that in the body of the document simply using "MessageFormat" is cleaner (especially since going forward, it would be confusing to have LDML 49 MessageFormat 2.0 (or MessageFormat 2.2).

eemeli
eemeli reviewed Feb 17, 2025
View reviewed changes
@aphillips
Remove proposed
1149a5a
@aphillips
Remove proposed
6d326df 
Probably the note should be removed, since the whole function is Draft
@aphillips
Remove one stability policy item per discussion
c0cd745
@aphillips aphillips requested a review from eemeli February 17, 2025 15:53
eemeli
eemeli requested changes Feb 17, 2025
View reviewed changes
aphillips and others added 2 commits February 17, 2025 08:18
@aphillips
Copy link
Member Author

aphillips commented Feb 17, 2025

Merging these changes. Additional fast-tracks may be used for v47 cleanup.

@aphillips aphillips merged commit 3db33de into main Feb 17, 2025
1 check passed
@aphillips aphillips deleted the aphillips-v47-prep branch February 17, 2025 19:52
eemeli added a commit to messageformat/messageformat that referenced this pull request Mar 2, 2025
@eemeli
feat(mf2)!: Split functions into DefaultFunctions & DraftFunctions (u…
a258187 
…nicode-org/message-format-wg#1007)

The 'messageformat/functions/utils' endpoint is merged into 'messageformat/utils',
and functions are only published via:

    import { DefaultFunctions, DraftFunctions } from 'messageformat/functions';

By default, on DefaultFunctions are included in MessageFormat.
To use all available functions:

    import { MessageFormat } from 'messageformat';
    import { DraftFunctions } from 'messageformat/functions';

    const mf = new MessageFormat(locale, msgsrc, { functions: DraftFunctions });
@eemeli eemeli mentioned this pull request Mar 2, 2025
Merged
@eemeli eemeli added this to the LDML 47 milestone Jul 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@eemeli eemeli eemeli approved these changes

@macchiati macchiati macchiati approved these changes

Assignees

No one assigned

Labels

normative Issue affects normative text in the specification specification Issue affects the specification

Projects

None yet

Milestone

LDML 47

Development

Successfully merging this pull request may close these issues.

Fix spec details for pourover to v47 (and future)

4 participants

@aphillips @macchiati @eemeli