Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[RU] Decode pronunciations #1376

Open
BoboTiG opened this issue Sep 2, 2022 · 0 comments · May be fixed by #2195
Open

[RU] Decode pronunciations #1376

BoboTiG opened this issue Sep 2, 2022 · 0 comments · May be fixed by #2195

Comments

@BoboTiG
Copy link
Owner

BoboTiG commented Sep 2, 2022

Russian pronunciations are using the transcriptions-ru LUA script. We should port it to Python to display proper pronunciations.

Note that it will be easier to tackle after #1174.

Upvote & Fund

  • We're using Polar.sh so you can upvote and help fund this issue.
  • We receive the funding once the issue is completed & confirmed by you.
  • Thank you in advance for helping prioritize & fund our backlog.
Fund with Polar
BoboTiG added a commit that referenced this issue Sep 2, 2022
I reviewed completely how pronunciations were retrieved in order
to tackle that task, including changing where pronunciations were
looked for: before we were using the whole word wikicode, now we
only use `head_sections` wikicode (faster, and more efficient).

It has the following nice side-effects (on top the having
local-specific formatting like `\...\` for French, `[...]` for German, etc.):

- `EN`, `FR`: now supports multiple cross-sections pronunciations
  (like ones from Middle English combined to ones from Old English
  sections, for instance on English data)
- `FR`: pronunciations outside the French section are no more taken
  into account (like using values from Gaulois or other locale sections,
  that was incorrect)
- `PT`: a lot more pronunciations are correctly found now
- `SV`: multiple pronunciations are now supported
- `RU`: it will be way easier to tackle #1376 then
BoboTiG added a commit that referenced this issue Sep 3, 2022
I reviewed completely how pronunciations were retrieved in order
to tackle that task, including changing where pronunciations were
looked for: before we were using the whole word wikicode, now we
only use `head_sections` wikicode (faster, and more efficient).

It has the following nice side-effects (on top the having
local-specific formatting like `\...\` for French, `[...]` for German, etc.):

- `EN`, `FR`: now supports multiple cross-sections pronunciations
  (like ones from Middle English combined to ones from Old English
  sections, for instance on English data)
- `FR`: pronunciations outside the French section are no more taken
  into account (like using values from Gaulois or other locale sections,
  that was incorrect)
- `PT`: a lot more pronunciations are correctly found now
- `SV`: multiple pronunciations are now supported
- `RU`: it will be way easier to tackle #1376 then
@polar-sh polar-sh bot added the Fund label Jul 23, 2024
@BoboTiG BoboTiG self-assigned this Oct 15, 2024
@BoboTiG BoboTiG linked a pull request Oct 16, 2024 that will close this issue
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant