Skip to content

Update spec as if PR #645 was accepted #646

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

Closed

Conversation

catamorphism
Copy link
Collaborator

DO NOT MERGE

This PR is for reference purposes when reviewing #645, to show how the spec would change if the design doc in #645 was accepted. It should not be merged as-is, and also reflects a slightly earlier version of the design doc. It should still serve to give a sense of what the spec would look like if this design doc was accepted.

This change updates the formatting spec to reflect the
changes proposed in unicode-org#645. It should not be merged as-is.
It also uses slightly different terms than the design doc in unicode-org#645,
but should serve to give a sense of what the spec would look
like if the "composability" design doc was accepted.
@aphillips
Copy link
Member

(chair hat off)

I think this is too specific. We give implementations a lot of leeway about how to implement things internally. This is one good way of organizing it. There are elements that, on an initial read, I would nitpick, but let's discuss the high-level requirements before diving into that. I appreciate the effort, though.

@aphillips aphillips added the LDML46 LDML46 Release (Tech Preview - October 2024) label Feb 15, 2024
@aphillips aphillips added LDML46.1 MF2.0 Draft Candidate and removed LDML46 LDML46 Release (Tech Preview - October 2024) labels Sep 16, 2024
@aphillips aphillips closed this Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
LDML46.1 MF2.0 Draft Candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants