File names for some Ethiopic transforms need improvement

Description

Some of the transforms with Ethiopic in the name should be renamed.

Ethiopic-Braille-Amharic

am_Ethi

am_Brai

Ethiopic-Ethiopic-Gurage

sgw_Ethi

Ethi

Ethiopic-Latin-TekieAlibekit

byn_Ethi

byn_Latn

Ethiopic-MorseCode-Amharic

am_Ethi

d0_Morse

Ethiopic-Latin-Xaleget

byn_Ethi

byn_Latn

When there is a language involved, the file name should indicate that. For #1, for example, it is Amharic that is being transformed. Similarly, we don’t have the file name Cyrillic-Latin/Russian. Either that or use a file name based on the codes, as is done in some other cases.

We are not completely consistent in names, but it would be good to change these before they go into a release, if feasible.

Activity

Show:

Steven R. Loomis July 25, 2022 at 6:43 PM

Missed your comment but yes it is a good time.

I think in the first example the file should be named am_Ethi-am_Brai.xml but looks like you can just name it with the bcp47 code: am-Brai-t-am-ethi.xml

For the latin orthographic ones, perhaps: und-Latn-t-und-ethi-m0-sera.xml (just going by the alias element)

would it make sense to just prefer using the bcp47 -t- filename for xml?

Daniel Yacob April 15, 2022 at 8:26 PM

Is it a good time to revisit this? Can someone add here a filename pattern template that would be preferred for transliteration files moving forward in CLDR? I’ll happily rename accordingly. thanks!

Mark Davis February 16, 2022 at 5:49 PM

NOTE: this is now for 42 (too late for 41)

Daniel Yacob February 14, 2022 at 11:06 PM

ohh… its my wording that is bad then. Sorry for that, a little hasty there. The test cannot run while the Jira issue status is “New”, thus blocking the merge.

Steven R. Loomis February 14, 2022 at 10:34 PM

the merge is blocked. But creating the PR isn’t blocked, right?

Fixed

Details

Components

Priority

Fix versions

Assignee

Reviewer

Reporter

Created February 10, 2022 at 9:17 PM
Updated July 27, 2022 at 3:43 PM
Resolved July 27, 2022 at 3:43 PM