Page MenuHomePhabricator

Support pauses (concatenating multiple utterances)
Open, Needs TriagePublicFeature

Description

It is common practice to include or indicate multiple pronunciations in one transcription, as in /ˈkɑːtɑːr, kəˈtɑːr/ or /maɪˈn(j)uːʃ(ɪ)ˌiː/. Providing a button for each pronunciation, or each permutation (the latter stands for four variants at once), would add considerable clutter.

Currently on Beta Cluster, ˈkɑːtɑːr, kəˈtɑːr flat-out gives you a file with no sound (but not an error), and ˈkɑːtɑːr kəˈtɑːr sounds like the name of someone called "Catarca Tar".

We need an operator to use inside ipa="" that results in one file with multiple distinct, isolated utterances with pauses in between.

I believe this is possible by something like

<speak>
  <p><!-- and <s> if required -->
    <phoneme alphabet="ipa" ph="ˈkɑːtɑːr">Qatar</phoneme>
  </p>
  <p>
    <phoneme alphabet="ipa" ph="kəˈtɑːr">Qatar</phoneme>
  </p>
</speak>

or

<speak>
  <phoneme alphabet="ipa" ph="ˈkɑːtɑːr">Qatar</phoneme>
  <break strength="x-strong"/><!-- compare which strength is best? -->
  <phoneme alphabet="ipa" ph="kəˈtɑːr">Qatar</phoneme>
</speak>

Failing that, send multiple requests, and concatenate the files and add pauses locally.

Event Timeline

Change 864894 had a related patch set uploaded (by MusikAnimal; author: MusikAnimal):

[mediawiki/extensions/Phonos@master] i18n: simplify message about empty files

https://gerrit.wikimedia.org/r/864894

Change 864894 merged by jenkins-bot:

[mediawiki/extensions/Phonos@master] i18n: simplify message about empty files

https://gerrit.wikimedia.org/r/864894

@KSiebert Hi, what's going on? Are you removing all Phonos-related tasks from the CommTech board? If not, why just this one?

@Nardog: If a team does not plan to work on a task, the task should not be on the team's workboard.

But every single task in MediaWiki-extensions-Phonos is also tagged with Community-Tech except for this one, hence the question. @MusikAnimal's patch even indicates intention to work on it. @KSiebert If it is indeed your team's decision not to work on this, I'd like some explanation.