Page MenuHomePhabricator
Create Task
Maniphest T151883

Handle unsupported page language
Open, LowPublic12 Estimated Story Points
Actions

Description

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?)

Related Objects
Search...

Event Timeline

Lokal_Profil created this task.Nov 29 2016, 2:37 PM
Lokal_Profil mentioned this in T144156: Use correct language when reciting.
Lokal_Profil moved this task from Incoming to Proposed for next sprint on the Wikispeech board.Nov 29 2016, 2:42 PM
Lokal_Profil added a parent task: T151786: Publically accessible demo (player) [Stage 1+2].
Lokal_Profil mentioned this in T151786: Publically accessible demo (player) [Stage 1+2].Nov 29 2016, 2:44 PM
Lokal_Profil triaged this task as Low priority.Nov 29 2016, 3:36 PM

Based on need in T151786

Lokal_Profil updated the task description. (Show Details)Nov 30 2016, 2:32 PM
Lokal_Profil set the point value for this task to 3.
Lokal_Profil moved this task from Proposed for next sprint to Sprint 2016-11-30 on the Wikispeech board.
Lokal_Profil edited projects, added Wikispeech (Sprint 2016-11-30); removed Wikispeech.
Lokal_Profil moved this task from Sprint 2016-11-30 to Sprint 2016-12-14 on the Wikispeech board.Dec 13 2016, 2:35 PM
Lokal_Profil edited projects, added Wikispeech (Sprint 2016-12-14); removed Wikispeech (Sprint 2016-11-30).
Lokal_Profil added a comment.Dec 19 2016, 5:20 PM

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.

Lokal_Profil edited projects, added Wikispeech; removed Wikispeech (Sprint 2016-12-14).Jan 24 2017, 1:24 PM

This should ideally await T153841

Lokal_Profil moved this task from Incoming to Proposed for next sprint on the Wikispeech board.Jan 24 2017, 1:24 PM
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
Sebastian_Berlin-WMSE subscribed.

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
Sebastian_Berlin-WMSE moved this task from Backlog to Known bugs on the Wikispeech-WMSE board.Nov 8 2017, 9:28 AM
Sebastian_Berlin-WMSE edited projects, added Wikispeech-Text-to-Speech; removed Wikispeech, Wikispeech-Player.Oct 25 2019, 7:01 AM
Sebastian_Berlin-WMSE moved this task from Unsorted to Player on the Wikispeech-Text-to-Speech board.
Sebastian_Berlin-WMSE added a project: Wikispeech-Jobrunner.Nov 13 2019, 4:12 PM
Sebastian_Berlin-WMSE moved this task from Incoming to Backlog on the Wikispeech-Jobrunner board.Jan 30 2020, 11:38 AM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL