public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Translating IPFire with Weblate
Date: Mon, 26 Aug 2019 14:41:11 +0100	[thread overview]
Message-ID: <D05B3AA8-BF09-4DA7-9D91-E2A5F7742897@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]

Hello boys and girls,

I would like to pre-announce that I have installed a new translation system.

This is a problem that has been bothering me for quite a while because people in many places around the world are using IPFire and they should be able to use it in a language that is most easy for them. However, of course nobody of us can translate to all those languages ourselves. So we need the help from our community!

Editing files is boring, but everyone likes a great webUI.

In the past we have been using Transifex which was very nice, but has gone proprietary.

Then I tried Pootle, but that was a bit of a pain to run and I think I never set it up all the way, because it just was too buggy.

And since we are busy reinstalling all the things, it was a good time to review everything again.

This time, I tried Weblate: https://translate.ipfire.org/

This is a Django app and has builtin support for Git. Importing the repositories was quick and easy. I have not idea how to programmatically get it back into the repositories again because I do not want to give that application permissions to push into our repositories. So if anyone has some free time and write a script to download the PO files I would appreciate that very much :)

Apart from that, it would be nice for you guys to log in, test this - I did not spend too much time on that yet. And if it is all alright, I want to announce it to our community.

Best,
-Michael

                 reply	other threads:[~2019-08-26 13:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D05B3AA8-BF09-4DA7-9D91-E2A5F7742897@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox