public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: How to handle the new translation method on a live system?
Date: Fri, 20 Nov 2026 17:18:19 +0100	[thread overview]
Message-ID: <ae011333-0145-49eb-8da3-ad3c09a90f37@ipfire.org> (raw)
In-Reply-To: <4jWKzk20n5zTq0T@michael.haj.ipfire.org>

On 20.11.2026 17:09, Michael Tremer wrote:
> Hi Matthias,

Hi Michael,

> You are right, the wiki page was outdated. I have rewritten it for the Weblate-based workflow that we have used since Core 206:
> 
>   https://www.ipfire.org/docs/devel/ipfire-2-x/translate
> 
> In short: translations are now done at https://translate.ipfire.org. Typos in a translation are fixed there, and Weblate sends the changes to this list for review. They then ship with a following Core Update. The old way of editing a language file on the installed system and running `update-lang-cache` no longer exists, since the translations are compiled into the binary catalogs you found under /usr/share/locale. The page also explains how to change an English source text, which goes through a patch to this list.

Ok, I read about that (new) way. So I really do need my 'Devels' for
that. No problem...

> I did not cover a quick way to test a change on a live system without a rebuild. If someone has a good approach for that, please add it to the thread and I will put it on the page.

Thanks for clarification! I wasn't sure if I overlooked something. If I
find a suitable way, I'll post it.

Best
Matthias



  parent reply	other threads:[~2026-11-20 16:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20 10:55 Matthias Fischer
     [not found] ` <4jWKzk20n5zTq0T@michael.haj.ipfire.org>
2026-11-20 16:18   ` Matthias Fischer [this message]
2026-11-20 16:27 ` Michael Tremer

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=ae011333-0145-49eb-8da3-ad3c09a90f37@ipfire.org \
    --to=matthias.fischer@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