Website manual glaxnimate in Dutch
Julius Künzel
julius.kuenzel at kde.org
Thu Jun 13 07:54:27 BST 2024
Hi!
The problem for Sphinx websites is that we need to enable every language individually (ie. there is no switch to enable all at once).
Also there are two issues I see with enabling languages if they are not translated (yet):
- usability: it pretends the language is available and users are confused
- technically (this is the main reason I disabled everything): Sphinx unfortunately has a very very bad performance when it comes to building the site with translations. I made some tests together with sysadmins when we migrated from Jenkins to GitLab and under some circumstances one language can take up to 20-30 minutes to build! Hence we should only enable languages that are worth it ie. that have a translation coverage of more than just 2 or 3 percent.
This means if you translate a Sphinx website you should check if your language is enabled and otherwise enable it or ask the maintainer to do so.
I hope this makes sense to you and answers your question well!
Cheers,
Julius
12.06.2024 22:48:32 Albert Astals Cid <aacid at kde.org>:
> El dissabte, 8 de juny del 2024, a les 12:11:29 (CEST), Freek de Kruijf va
> escriure:
>> The translations for the website with the manual for glaxnimate is almost
>> 100% translated.
>>
>> I wonder where I can find this website? https://docs.glaxnimate.org/nl/ ?
>
> Good question.
>
> Julius I see you disabled translations on the webpage.
>
> Why are we asking translators to translate the webpage if then they are
> disabled?
>
> We should either enable the translations or stop asking translators to
> translate.
>
> Cheers,
> Albert
More information about the kde-i18n-doc
mailing list