Only include translations which are completed

The website project on Weblate is very small and doesn't contain too many strings (compared to say, the Android client or the website documentation). Therefore, lets use this as the threshold for whether a translation gets included or not.

In a meeting with @eighthave we mentioned that given the size of the weblate project, we should include translations at 100% and exclude others.

Now it occurs to me that when we go and add a new string, this will immediately exclude all translations because they will no longer be at 100%. However I think this will not be a problem because the workflow will be as follows:

• Someone adds some new text to the fdroid-website project.
• Weblate pulls this repo, resulting in all translations dropping to < 100%.
• There is an arbitrary time period before a human manually pulls translations back from Weblate. During this time, translators are able to add the new string in order to bump back to 100%.
• The website will only get deployed when a human manually tags a release.

Perhaps one nice-to-have would be a script which the potential-website-tag-and-releaser could run, which tells them:

$ ./tools/tag-release.sh

Since last release, we've dropped support for the following 12 languages:
 * Spanish
 * French
 * German
 ...
Is it still okay to tag a release without these languages? [y/N]

added bazaar localization labels

I thought there was a jekyll config item to enable languages. That would be ideal, because we can then just pull in all translations from Weblate, and then run a script to see which are ready, which generates the list for the jekyll config. Otherwise, if we have to keep incomplete translations out of fdroid-website git for releases, then we'll have to merge Weblate into master, then for each release, make a release branch which purges the incomplete translation files in the release branch only.

In the past, I've experimented with this in the client. It is relatively straighforward to ask Weblate for these stats:

$ curl https://hosted.weblate.org/exports/stats/f-droid/website/\?format\=csv
name,code,total,translated,translated_percent,total_words,translated_words,failing,failing_percent,fuzzy,fuzzy_percent,url_translate,url,last_change,last_author
Asturian,ast,21,20,95.2,67,66,0,0.0,1,4.7,https://hosted.weblate.org/projects/f-droid/website/ast/,https://hosted.weblate.org/engage/f-droid/ast/,2017-06-19 15:02:35+00:00,Xuacu Saturio
Chinese (Simplified),zh_Hans,21,21,100.0,67,67,0,0.0,0,0.0,https://hosted.weblate.org/projects/f-droid/website/zh_Hans/,https://hosted.weblate.org/engage/f-droid/zh_Hans/,2017-06-23 14:14:19+00:00,sima
Chinese (Traditional),zh_Hant,21,21,100.0,67,67,0,0.0,0,0.0,https://hosted.weblate.org/projects/f-droid/website/zh_Hant/,https://hosted.weblate.org/engage/f-droid/zh_Hant/,2017-06-22 04:39:22+00:00,ezjerry liao
English,en,21,21,100.0,67,67,0,0.0,0,0.0,https://hosted.weblate.org/projects/f-droid/website/en/,https://hosted.weblate.org/engage/f-droid/en/,,
French,fr,21,21,100.0,67,67,0,0.0,0,0.0,https://hosted.weblate.org/projects/f-droid/website/fr/,https://hosted.weblate.org/engage/f-droid/fr/,2017-06-16 19:50:33+00:00,Jean-Baptiste
German,de,21,21,100.0,67,67,0,0.0,0,0.0,https://hosted.weblate.org/projects/f-droid/website/de/,https://hosted.weblate.org/engage/f-droid/de/,2017-06-26 13:07:04+00:00,Roman Leo
Persian,fa,21,0,0.0,67,0,0,0.0,0,0.0,https://hosted.weblate.org/projects/f-droid/website/fa/,https://hosted.weblate.org/engage/f-droid/fa/,,
Portuguese (Brazil),pt_BR,21,21,100.0,67,67,0,0.0,0,0.0,https://hosted.weblate.org/projects/f-droid/website/pt_BR/,https://hosted.weblate.org/engage/f-droid/pt_BR/,2017-06-24 20:25:14+00:00,José Victor
Romanian,ro,21,0,0.0,67,0,0,0.0,0,0.0,https://hosted.weblate.org/projects/f-droid/website/ro/,https://hosted.weblate.org/engage/f-droid/ro/,,
Sardinian,sc,21,21,100.0,67,67,0,0.0,0,0.0,https://hosted.weblate.org/projects/f-droid/website/sc/,https://hosted.weblate.org/engage/f-droid/sc/,2017-06-19 14:43:55+00:00,Ajeje Brazorf
Spanish,es,21,21,100.0,67,67,0,0.0,0,0.0,https://hosted.weblate.org/projects/f-droid/website/es/,https://hosted.weblate.org/engage/f-droid/es/,2017-06-21 22:09:12+00:00,José Rodrigo Baires Quezada
Spanish (Argentina),es_AR,21,21,100.0,67,67,0,0.0,0,0.0,https://hosted.weblate.org/projects/f-droid/website/es_AR/,https://hosted.weblate.org/engage/f-droid/es_AR/,2017-06-19 02:40:23+00:00,Macofe
Tibetan,bo,21,0,0.0,67,0,0,0.0,0,0.0,https://hosted.weblate.org/projects/f-droid/website/bo/,https://hosted.weblate.org/engage/f-droid/bo/,,
Turkish,tr,21,21,100.0,67,67,0,0.0,0,0.0,https://hosted.weblate.org/projects/f-droid/website/tr/,https://hosted.weblate.org/engage/f-droid/tr/,2017-06-18 20:12:16+00:00,monolifed

And then do the following to pull out those with 100%:

$ curl --silent https://hosted.weblate.org/exports/stats/f-droid/website/\?format\=csv | tail -n +2 | awk -F ',' '{ if ($5 == "100.0") print $2 }'
zh_Hans
zh_Hant
en
fr
de
pt_BR
sc
es
es_AR
tr

@eighthave:

I thought there was a jekyll config item to enable languages.

That is correct, and what I intended. I've renamed the issue to clarify.

Since we're already building the biggest jekyll site ever, we need to make sure it doesn't get massive. I think we need to restrict the number of languages the site supports, at least until we get it running smoothly. So I think the requirements for adding a language to the website should be:

• https://hosted.weblate.org/projects/f-droid/website/ 100% translated
• 100% of the contents of the main pages (About, Contribute, etc)
• at least 10 apps 100% translated

Otherwise, we'll have thousands of "packages" pages with only little bits of that language sprinkled around an otherwise English site.

I am happy with 100% translated + 100% of the contents of the main pages. Not too keen on the 10 apps translated, because most of the package page will be in their language, as will all of the chrome around it. For reference, here is a screenshot of the play store in Czech, where I've highlighted the equivalent parts which would be English on out site:

This is also no different than the client is (and always has been): An app store where all of the chrome is translated, but the metadata about apps is not. Finally, a bar of 10 apps translated will still result in a lot of English on the page, because we have side bars highlighting apps, which will inevitably contain English metadata anyway (and be shown on every page the user views). Even the size isn't too bad, with a total of 29MiB for each language when built with the f-droid.org repo:

$ du --hc --max-depth=1 _site
29M	_site/fr
29M	_site/tr
29M	_site/sc
29M	_site/es
29M	_site/es_AR
29M	_site/zh_Hans
29M	_site/en
29M	_site/zh_Hant
29M	_site/de
260M	_site
260M	total

And a build time which increases by about 10-15 seconds for each language (and which can be reduced during development by only enabling a few languages).

mentioned in merge request !86 (merged)

One key part of the idea of the requirement that I proposed is for translators to demonstrate a commitment to working on the site and keeping the translation current. Half translated chrome is almost always worse than just English. In my experience with crowdsourced translations over the past 6 years, I've seen a lot of "drive by" contributions, were someone translates to a new language, then no one touches it for years and it bitrots.

changed milestone to %launch-localized

So we have 8 languages to launch with now 26d7f9e13f8ebbdb4be775e14c8ad1834805f967, we can see about adding more once this is deployed. !125 (merged)

closed

closed