You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are several issues with how we currently handle multilingual names. This is an umbrella ticket to track them all, and decide on a general strategy.
Korean moved from `ko_rm` to `ko-Latn`. Same as Japanese deprecated `ja_rm` in advance of `ja-Latn`, but still have twice more records. For Japanese add Hiragana form.
fix#537
listed in #930
It would be good to have clarity on this, and for frequently used styles to be updated to match. Right now it's entirely unclear what third-party implementations of the OMT schema are meant to support - the spec says name, name_en and name_de, but styles appear to use name:latin or whatever.
There are several issues with how we currently handle multilingual names. This is an umbrella ticket to track them all, and decide on a general strategy.
name_de
andname_en
(first mentioned in Is 'name_de' not a waste of space ? #769, implemented in [BREAKING] Remove name_en and name_de #928)name:latin
->name_latin
orname-Latn
or ???name:nonlatin
->name_nonlatin
or ???name_int
The text was updated successfully, but these errors were encountered: