A contributor raised a usability concern on GitHub:
Why can't I find jv-Java by typing ‘Jawa’ in the language list? (I had to type ‘java’). It's not natural for our speakers and users to find Javanese keyboards by typing ‘Jawa’, then ask them to find jv-Java keyboards by typing ‘Java’.
This creates a barrier for native speakers, who intuitively search using "Jawa". When using the ULS (Universal Language Selector) language list, typing "Jawa" should should match both scripts and return both input options:
- jv (Javanese in Latin script) - Jawa
- jv-java (Javanese in Javanese script) - ꦗꦮ
What needs to be done:
Update the language search index in the ULS extension so that "Jawa" returns both relevant input methods. Add "Jawa" as a search alias for both jv and jv-java entries in:
data/LanguageNameSearchData.php in extensions/UniversalLanguageSelector.
This change would help improve search behavior and script discoverability for native users.