Skip to content

Conversation

@srl295
Copy link
Member

@srl295 srl295 commented Jan 5, 2026

CLDR-19123

  • This PR completes the ticket.

ALLOW_MANY_COMMITS=true

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

✨ This commit deployed to https://83907f03.cldr.pages.dev
✨ This PR deployed to https://pr5271.cldr.pages.dev

Changed Pages in the last commit:

@github-actions github-actions bot added the Site Update Updates docs/site label Jan 5, 2026
@srl295 srl295 requested review from a team and markusicu and removed request for a team and markusicu January 5, 2026 19:22
@srl295 srl295 changed the title CLDR-19123 site: update CLDR 42-43-44 wording around keyboard files 🚧 CLDR-19123 site: update CLDR 42-43-44 wording around keyboard files Jan 5, 2026
@miloush
Copy link
Contributor

miloush commented Jan 5, 2026

At two places it says "not compatible, were not maintained". Could we also point out they are not all correct and shouldn't be used? For example "not compatible, were not maintained and contained factual errors" or something like that.

@srl295
Copy link
Member Author

srl295 commented Jan 5, 2026

At two places it says "not compatible, were not maintained". Could we also point out they are not all correct and shouldn't be used? For example "not compatible, were not maintained and contained factual errors" or something like that.

factual errors sounds good. I'll update each location to say that.

- Bengali, Assamese Phonetic Keyboard (PR \#[3368](https://github.com/unicode-org/cldr/pull/3368))
- French AZERTY optimisé (PR \#[3220](https://github.com/unicode-org/cldr/pull/3220))

**Note**: prior keyboard data files are not compatible, were not maintained and have also been removed. The prior keyboard files are still available from earlier CLDR downloads, but are not recommended for use as they are known to be incorrect, and are not compatible with the current DTD.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we should give a version number rather than prior keyboard data files, e.g. v1.0 keyboard data files from CLDR v23-v41 (I don't know the exact version numbers).

And say, 'were not maintained and hence have been removed in CLDR v42"

Copy link
Member Author

Choose a reason for hiding this comment

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

instead of prior, we could say "data files before v44"?

Copy link
Member Author

Choose a reason for hiding this comment

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

I will make it say 'removed in v44'

@github-actions
Copy link

github-actions bot commented Jan 6, 2026

✨ This commit deployed to https://f3b14200.cldr.pages.dev
✨ This PR deployed to https://pr5271.cldr.pages.dev

Changed Pages in the last commit:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Site Update Updates docs/site

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants