Weblate and i18next json files

Fri, 29 Apr 2016 00:00:00 +0000

There’s a bug report on github about JSON format breaks i18next files due to automatic restructuring. Actually it flattens your i18next JSON file and makes it unusable for further usage.

So after starting with a JSON file like:

{
"navbar": {
"reward": "Rewards",
"about": "About"
}
}

you end up with a committed file which was transformed into this:

{
"navbar.reward": "Rewards",
"navbar.about": "About"
}

Use Weblate PRE_COMMIT_SCRIPTS

Weblate offers script hooks before or after a repository action happens. I’m using one of those hooks to execute a short Python script which reformats JSON again to be usable in i18next translation tools again. The script below is also available on Github:

GitLab as OAuth provider for Weblate

Thu, 28 Apr 2016 00:00:00 +0000

Weblate is built on Django and you can use a lot of authentication plugins. After my contribution to django-allauth and the backporting work of glensc and omab to django-social-auth it’s very easy to integrate [GitLab]’s authentication provider with Weblate

GitLab

All you have to do on GitLab is configuration through webinterface. Go to https://gitlab.com/profile/applications and register a new application.

Name: Weblate
Redirect URI: `https://weblate.yourdomain.tld/accounts/complete/GitLab/``

After registering your new application you’ll get your Application Key and Secret. You’ll need this later for configuration

Weblate on widerin

Weblate and i18next json files

Use Weblate PRE_COMMIT_SCRIPTS

GitLab as OAuth provider for Weblate

GitLab