-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove untranslated locales from page generation and the locale chooser #4224
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving contingent on asking whether it's worth holding off on this as strictly part of the Nuxt 3 experimentation or if we definitely wish to exclude these now, even with our current non-technically problematic handling of very many routes. Fine by me, just wanted to clarify for sure (the issue is ambiguous about this in light of the relationship to the Nuxt 3 work).
@sarayourfriend I see this as a significant user experience improvement that was identified by and happens to be relevant to the Nuxt 3 experimentation project. It's worth doing as soon as we can in its own right to make the locale chooser more useful. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm surprised at how small the change was :) We remove ~130 items from the list.
We removed 130?! That's a lot, almost two-thirds of the close to 200 locales in total. Sad to see and hard to believe they were all 0% translated. |
Add Saraiki in locale chooser. Saraiki is being translated, |
@mpQadir Thanks for the ping. Our script is meant to automatically include locales once they have translated strings, which I thought would cover what you're asking... However, I checked and saw that Saraiki isn't in our list. Because you said it is being translated, I kept looking, and I think there might be a bug in our script or integration with Glotpress, because Saraiki has a 0% translation when our script downloads it, even though there are 64 translations for Saraiki. @WordPress/openverse-frontend are any of y'all equipped to look into this? Saraiki definitely has translated strings, but when I run |
I tried it just now @sarayourfriend and it's appearing in the valid list of locales for me and showing up in the chooser as well. I suspect that because these translations have been added very recently and frontend staging has not had a chance to be deployed since, Saraiki was not a valid language when this PR was merged. I'm very confident that Saraiki will be added to staging in the next deploy. Additionally, I logged the output in the console and |
Okay! I wonder if I did something wrong when I tried it just now. Thanks for checking and confirming it will go in. @mpQadir just to clarify for you, that means Saraiki should start appearing on openverse.org sometime next week. |
Thanks very much.
…On Wed, May 1, 2024, 7:54 AM sarayourfriend ***@***.***> wrote:
Okay! I wonder if I did something wrong when I tried it just now. Thanks
for checking and confirming it will go in. @mpQadir
<https://github.com/mpQadir> just to clarify for you, that means Saraiki
should start appearing on openverse.org sometime next week.
—
Reply to this email directly, view it on GitHub
<#4224 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXPYAW2PBVX4KGRERHTNA3TZABKNFAVCNFSM6AAAAABG664AUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBXHEYDANRXGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@sarayourfriend @dhruvkb Please Saraiki language be deployed in the website in locale chooser. It is not appearing. Waiting |
Hi @mpQadir, you've actually helped reveal a bug in Openverse. We currently only include languages which use languages defined in the https://en.wikipedia.org/wiki/ISO_639-1 specification. Saraiki is in version 639-3 https://iso639-3.sil.org/code/skr. I will make a pull request to fix this today. Thank you! |
Hello @mpQadir, following up on your very useful messages, Saraiki is now available on Openverse: Thank you so much for your help here and your translations. |
Glad to hear it!
…On Tue, May 28, 2024, 12:33 AM zack ***@***.***> wrote:
Hello @mpQadir <https://github.com/mpQadir>, following up on your very
useful messages, Saraiki is now available on Openverse:
https://openverse.org/skr
Thank you so much for your help here and your translations.
—
Reply to this email directly, view it on GitHub
<#4224 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXPYAW6U7ZZKXGKGTRMUDKTZEODCBAVCNFSM6AAAAABG664AUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZTHE3TEMRTGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Fixes
Fixes #4196 by @zackkrida
Description
Removes untranslated locales from the frontend.
Testing Instructions
Run the frontend locally and verify that no languages in
untranslated-locales.json
are present in the locale chooser in the site footer.Checklist
Update index.md
).main
) or a parent feature branch.Developer Certificate of Origin
Developer Certificate of Origin