Currently getPageLanguage() uses wfGetLangObj() on the database language when a database language exists. wfGetLangObj() returns a Language object when the language code is supported and returns $wgContLang when the language code is not supported.
Expected result: getPageLanguage() should continue with getting the language from the content handler when the language code from the database is not supported.
Other language functions like getPageViewLanguage() should do the same.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Title::getPageLanguage: Fallback to content handler language | mediawiki/core | master | +2 -4 |
Change 441529 had a related patch set uploaded (by Fomafix; owner: Fomafix):
[mediawiki/core@master] Title: Introduce getDbPageLanguage()
Change 441529 had a related patch set uploaded (by Fomafix; owner: Fomafix):
[mediawiki/core@master] Title: Introduce getDbPageLanguage()
Change 829110 had a related patch set uploaded (by Fomafix; author: Fomafix):
[mediawiki/core@master] Title::getPageLanguage: Fallback to content handler language
I find the task description insufficient to understand what behavior might be changing and what are the pros and cons of the current vs. proposed behavior.
Anyway, this feels like MediaWiki core thing that has no or limited overlap with the expertise in the Language team. I'll follow this task myself though.
Change 829110 merged by jenkins-bot:
[mediawiki/core@master] Title::getPageLanguage: Fallback to content handler language