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.

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

Baked data-driven transliterators should support aliases #6258

Open
sffc opened this issue Mar 9, 2025 · 0 comments
Open

Baked data-driven transliterators should support aliases #6258

sffc opened this issue Mar 9, 2025 · 0 comments
Labels
C-transliterator Component: transliterator

Comments

@sffc
Copy link
Member

sffc commented Mar 9, 2025

For example, coming from CLDR JSON, we have

{
  "_visibility": "external",
  "_alias": "Bengali-Arabic",
  "_aliasBcp47": "und-Arab-t-und-beng",
  "_source": "Beng",
  "_direction": "forward",
  "_target": "Arab",
  "_rulesFile": "Bengali-Arabic.txt"
}

However, the alias "Bengali-Arabic" does not appear to be retained anywhere. We generate und-Arab-t-und-beng.json which does not have any aliases inside.

ICU4C supports referencing this transliterator at runtime as "Bengali-Arabic". I guess we should do, unless we just want to explicitly discourage that behavior.

@sffc sffc added the C-transliterator Component: transliterator label Mar 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-transliterator Component: transliterator
Projects
None yet
Development

No branches or pull requests

1 participant