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.

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

CLDR-17982 Fix links on 46 release page #4079

Merged
merged 1 commit into from
Sep 25, 2024
Merged

CLDR-17982 Fix links on 46 release page #4079

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/site/downloads/cldr-46.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,12 +12,12 @@ title: CLDR 46 Release Note

The data is available at [release-46-beta2](https://github.com/unicode-org/cldr/releases/tag/release-46-beta2),
and the specification is available at [tr35/proposed.html](https://www.unicode.org/reports/tr35/proposed.html).
Feedback is welcome via [tickets](https://github.com/unicode-org/cldr/blob/main/docs/requesting_changes.md#requesting-updates-to-locale-data-through-a-ticket). (The CLDR site is undergoing a migration to Markdown, so the UI for navigation is temporary.)
Feedback is welcome via [tickets](https://cldr.unicode.org/requesting_changes). (The CLDR site is undergoing a migration to Markdown, so the UI for navigation is temporary.)

## Overview

Unicode CLDR provides key building blocks for software supporting the world's languages.
CLDR data is used by all [major software systems](https://cldr.unicode.org/index#TOC-Who-uses-CLDR-)
CLDR data is used by all [major software systems](https://cldr.unicode.org/index#who-uses-cldr)
(including all mobile phones) for their software internationalization and localization,
adapting software to the conventions of different languages.

Expand Down Expand Up @@ -138,7 +138,7 @@ For a full listing, see [¤¤BCP47 Delta](https://unicode.org/cldr/charts/46/del

### [Locale Changes](https://unicode.org/cldr/charts/46/delta/index.html)

1. Major changes to emoji search keywords and short names (see below)
1. Major changes to emoji search keywords and short names ([see below](#emoji-search-keywords))
2. Major changes to Chinese collation, reflecting new data in Unicode 16.0
3. Added iso8601 patterns to root.
These will use localized months, days of the week, day periods, and timezones.
Expand All @@ -151,7 +151,7 @@ Full localization will await the next submission phase for CLDR.
For a full listing, see [Delta Data](https://unicode.org/cldr/charts/46/delta/index.html)

### Message Format Specification
The CLDR Technical Committee decided to continue the tech preview phase for Message Format in version 46.
The CLDR Technical Committee decided to continue the tech preview phase for [Message Format](https://cldr-smoke.unicode.org/spec/main/ldml/tr35-messageFormat.html#Contents) in version 46.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok for now will need to move when we branch

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We discussed that today. We clearly need the pages on the maint-46 branch still to be staged; it doesn't appear that during that period we need to have the main branch staged. We'll need to discuss more.

The plan is to have a final version of the specification in a 46.1 release before the end of 2024.

Implementers should be aware of the following normative changes after the start of the tech review period.
Expand Down
Loading