Update supported languages and fix language codes#14406
Merged
Conversation
poire-z
approved these changes
Oct 3, 2025
poire-z
left a comment
Contributor
There was a problem hiding this comment.
Fine with me.
It will just make 25 pages instead of 14 in the Translate from/to> submenus, which I guess we all hardly ever visit.
Contributor
Author
Agree, it's a little inconvenient. Maybe a search bar there would be nice but implementing that is over my programming skills. |
0xstillb
pushed a commit
to 0xstillb/koreader-thai
that referenced
this pull request
May 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request significantly expands the set of supported languages in the
SUPPORTED_LANGUAGEStable infrontend/ui/translator.lua, updating the source to match the latest list from Google Translate and increasing coverage from 132 to 249 languages. It also updates some language codes and improves the mapping between alternate codes and their canonical forms.Issue
I have stumbled upon the fact that I can occasionally auto-translate from Crimean Tatar, but can't set Crimean Tatar as the translation source language. As smaller portions of Crimean Tatar text can be misinterpreted as Turkish, Azerbaijani, etc., it was not a comforting experience. To fix that, I've added languages presented in Google Translate UI and missing from the current list.
Expansion of supported languages:
Acehnese,Avar,Balinese,Cantonese,Crimean Tatar,Jamaican Patois,Santali, and many more.Updates and corrections to existing language codes:
KurdishtoKurdish (Kurmanji)andPortuguesetoPortuguese (Brazil)with the addition ofPortuguese (Portugal).Punjabi (Gurmukhi)andPunjabi (Shahmukhi), and differentiating betweenSantali (Latin)andSantali (Ol Chiki).This change is