{{support}} Adding TheWikipediaLibrary Card Platform TranslateWiki

Fragment of a discussion from Support
Jump to navigation Jump to search

Very belated update: I've reworked the way we're setting the available languages so that Django is checking for the translation directories on startup. We restart the app every time we pull from the repo, so that should make for a nice automated workflow for adding new translations. Django doesn't support all of the languages listed at https://github.com/wikimedia/language-data (although we're definitely in the triple digits), so I added code to use the intersection of Django and wikimedia language codes and the autonyms from the wikimedia language data instead of English language names. I've significantly updated our database configuration so that the content that lives in the db can be localized across the entire intersection of languages without the app falling over from db column and index limitations.

Jsn.sherman (talk)14:03, 2 July 2018

What does happen when Django doesn't support a language? Do we need to add a blacklist/whitelist on our side?

The rest sounds good. Should we start checking about enabling this project on translatewiki.net?

Nike (talk)11:12, 3 July 2018

On its own, Django was falling over dead (500) when it encountered an unknown language code. I've configured our app to just ignore unknown languages. We should probably do a whitelist so that volunteers don't work on translations that aren't provided to users. That data structure currently lives as a python dict, so I could have the platform provide it as a JSON, CSV, or something similar. Other than ironing this detail out, I think we're about ready to go.

Jsn.sherman (talk)17:33, 3 July 2018
 

Looks like our actual supported language count is 83. I was doing quick glances before and was apparently including keys and values in the count. Here's the json whitelist which is computed from the live site. https://wikipedialibrary.wmflabs.org/i18n-whitelist

Jsn.sherman (talk)15:49, 10 July 2018