-
Notifications
You must be signed in to change notification settings - Fork 372
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-16438 document filtering out unneeded data #2761
Conversation
-Simply return parameter unchanged for WebContext.decodeFieldString -Comments
-Revise SurveyForum.userCanUsePostType, isPhaseReadonly only matters for non-TC -Refactor with boolean isTC to avoid calling userIsTC repeatedly
Bumps [actions/cache](https://github.com/actions/cache) from 2 to 3. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](actions/cache@v2...v3) --- updated-dependencies: - dependency-name: actions/cache dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…2756) Bumps [json](https://github.com/douglascrockford/JSON-java) from 20190722 to 20230227. - [Release notes](https://github.com/douglascrockford/JSON-java/releases) - [Changelog](https://github.com/stleary/JSON-java/blob/master/docs/RELEASES.md) - [Commits](https://github.com/douglascrockford/JSON-java/commits) --- updated-dependencies: - dependency-name: org.json:json dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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.
Definite improvement.
At some point we should make sure the wording here is harmonized with https://cldr.unicode.org/index/cldr-spec/coverage-levels for example.
Also the Coverage level section I linked to says:
That structure is primarily intended for internal use in CLDR tooling — it is not anticipated that users of CLDR data would need it.
May need to revise the above if they are no longer internal.
Co-authored-by: Steven R. Loomis <srl295@gmail.com>
Co-authored-by: Steven R. Loomis <srl295@gmail.com>
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.
LGTM. Excellent addition to the spec, very consumer oriented. I expect as with any newer 'public surface' of the project we may have some bumps and questions but they can shake out over time.
Co-authored-by: Shane F. Carr <shane@unicode.org>
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 looks good. Definitely good to explicitly state this in the spec.
I think there's room to improve this section further (more emphasis on explicit algorithms rather than left-to-the-reader guidelines), but that needs more thought and doesn't need to be done right away.
Sorry, had wrong target. Can you restamp? |
Messed up in github, so created new PR #2766 |
Good. I agree that we can flesh this out over time. We might even want to
break out a new "Part" that has implementation techniques, where we can
gather them all together.
…On Mon, Mar 6, 2023 at 5:23 PM Shane F. Carr ***@***.***> wrote:
***@***.**** approved this pull request.
This looks good. Definitely good to explicitly state this in the spec.
I think there's room to improve this section further (more emphasis on
explicit algorithms rather than left-to-the-reader guidelines), but that
needs more thought and doesn't need to be done right away.
—
Reply to this email directly, view it on GitHub
<#2761 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJLEMF7MJS33OREKKXC7MDW22EZNANCNFSM6AAAAAAVQRBUQU>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
It's a trade off. That was the goal of the implementers guide ( stub | toc ) … I'm not sure the TR is the right place for too much implementation guidance vs. some more informal cookbook. However, no other vehicles have 'stuck' in the meantime. |
We could have an additional github document, eg LDML Implementers Guide |
This is for tickets https://unicode-org.atlassian.net/browse/CLDR-16438 and https://unicode-org.atlassian.net/browse/CLDR-16340.
CLDR-16438
ALLOW_MANY_COMMITS=true