Page MenuHomePhabricator

Handle unsupported page language
Open, LowPublic12 Estimated Story Points


When a page is in a language that the TTS server does not support we want to ensure that the user gets relevant feedback and that unnecessary requests to the TTS are not made.

Things to consider:

  • Determine if page language is supported before triggering cleaner/segmenter. Making use of Languages available for TTS.
    • Make sure js can deal with cleaner/segmenter not being triggered.
  • Should behaviour be different on mono- and multilanguage wikis?
  • Output error message?
  • Hide buttons?
  • Allow user to try synthesizing the text in a different language? (Are there cases where using a similar language makes sense?)

Event Timeline

Lokal_Profil set the point value for this task to 3.
Lokal_Profil edited projects, added Wikispeech (Sprint 2016-11-30); removed Wikispeech.

A thought on this.

It might be best to store supported languages in the config. The default value would be "all languages which we currently support in the TTS". That way if a new language is included only the default config would need to updated.

The benefit is that you don't need a call to the TTS for every page and any non-WMF wiki using Wikispeech could choose to only allow (or even install) certain languages.

Of course it wouldn't be bad to have a build test which ensures the default config languages are the same as those supported by the TTS.

Sebastian_Berlin-WMSE lowered the priority of this task from Low to Lowest.Feb 7 2017, 2:37 PM
Sebastian_Berlin-WMSE changed the point value for this task from 3 to 12.Feb 7 2017, 2:44 PM

Changed story points to new system

Sebastian_Berlin-WMSE raised the priority of this task from Lowest to Low.Sep 20 2017, 1:55 PM