Page MenuHomePhabricator

Glossaries, pronunciations, and dictionaries
Open, Needs TriagePublic0 Estimated Story Points


Type of activity: Pre-scheduled session.
Main topic: Handling wiki content beyond plaintext

The problem

In wikis using LanguageConverter to transliterate between different scripts, it is necessary to associate one or more "glossaries" (T484) to give the transliteration of various article-specific terms. For example, articles on movies will include the "Movie" glossary which gives localized titles for films and actors.

Pediaphon is a contribution to WikiProject:Spoken Wikipedia which uses speech synthesis to make Wikipedia articles accessible to visually-impaired users. It could benefit from a "glossary" mechanism which associated topic-specific pronunciations to articles.

A future extension of the Content Translation service would use machine translation to assist in keeping translated articles up-to-date as the source document was modified. It could also use a "glossary" that gave translations and other semantic information for topic-specific words. "fence" in the "crime" glossary would have a different translation than "fence" in the "landscaping" (or default?) glossary.

Perhaps we can come up with a general mechanism that would allow us to serve these use cases.

Expected outcome

Further development of T484 with an eye to uses beyond Language Converter. Collection of additional use cases. Nailing down the implementation details to back this functionality.

Current status of the discussion

T484 has been stalled for a while, but is about to become active again as Parsoid and Visual Editor implement support for language variants. This makes it an opportune time to bring this topic out of cold storage and try to build some consensus on the problem area and solution space.


Event Timeline

Qgil added a subscriber: Qgil.

Can you add projects/tags related to the topics discussed, please?

@cscott Hey! As developer summit is less than four weeks from now, we are working on a plan to incorporate the ‘unconference sessions’ that have been proposed so far and would be generated on the spot. Thus, could you confirm if you plan to facilitate this session at the summit? Also, if your answer is 'YES,' I would like to encourage you to update/ arrange the task description fields to appear in the following format:

Session title
Main topic
Type of activity
Description Move ‘The Problem,' ‘Expected Outcome,' ‘Current status of the discussion’ and ‘Links’ to this section
Proposed by Your name linked to your MediaWiki URL, or profile elsewhere on the internet
Preferred group size
Any supplies that you would need to run the session e.g. post-its
Interested attendees (sign up below)

  1. Add your name here

We will be reaching out to the summit participants next week asking them to express their interest in unconference sessions by signing up.

To maintain the consistency, please consider referring to the template of the following task description:

@cscott: Did this session take place?
If yes, are there any notes or action items to share? Are there any actionable items (tasks to create / link?) from this session?
If not, could you close this task as declined? Thanks in advance!

ssastry added a subscriber: Sarise298.
ssastry removed a subscriber: Sarise298.
StjnVMF triaged this task as Unbreak Now! priority.May 18 2018, 5:17 PM
StjnVMF set Security to Software security bug.May 18 2018, 5:19 PM
StjnVMF added a project: acl*security.
StjnVMF changed the visibility from "Public (No Login Required)" to "Custom Policy".
StjnVMF removed subscribers: srishakatux, Aklapper.
StjnVMF added a subscriber: StjnVMF.
Jdforrester-WMF lowered the priority of this task from Unbreak Now! to Needs Triage.May 18 2018, 5:42 PM
Jdforrester-WMF removed a project: acl*security.
Jdforrester-WMF changed the visibility from "Custom Policy" to "Public (No Login Required)".
Jdforrester-WMF removed a subscriber: StjnVMF.

This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!

For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)