From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4jWL9g6dq0z3356 for ; Fri, 20 Nov 2026 16:18:31 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "mail01.haj.ipfire.org", Issuer "YR1" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4jWL9c3FNsz2yJG for ; Fri, 20 Nov 2026 16:18:28 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4jWL9b2W15z5M for ; Fri, 20 Nov 2026 16:18:27 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1795191507; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Bm7xZFgOYkrvFltDsADtxKAxOkEwXduL1sWuu8xR3pg=; b=g82xBrSeeZ4+6JokhFw8WNaXBEBRvRGuEF2uNQ07uj/oJCyOmCvXYWergxQKUbw4Ortgv8 6HBN0En0CGp4REAw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1795191507; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Bm7xZFgOYkrvFltDsADtxKAxOkEwXduL1sWuu8xR3pg=; b=S6m567NTShOIqCH8DkuCIHIq85mTbR+F8Ti3jkFHB2GF08ovAinF2MbOilNHpIxDq/QebG pWqF3lsZt8oXc+3paMribbp1ty0k/6v6jX8QMPyFBAMrArA3sPEWj3pn2IXvwYvO8iQpg5 wvTTzcuxCt2c2QhMSGfyzPd6bzjrPXV3KPe/n3ebusltS4RyUOUOjKBNx1Gn31O6bYg3yd EG0c6tjRAeUJHeGwUicCKyV8jFEWDl4GIQOSDYiHuH/iwHs03vP5v+6+nD+fIMrM2TFlWb XExcknkls1y25nzOZAeD/zwSFe1zlOE5ssJIRiwYdmISCPJWMO5GKwm6819oIw== Message-ID: Date: Fri, 20 Nov 2026 17:18:19 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: How to handle the new translation method on a live system? To: development@lists.ipfire.org References: <4jWKzk20n5zTq0T@michael.haj.ipfire.org> Content-Language: en-US From: Matthias Fischer In-Reply-To: <4jWKzk20n5zTq0T@michael.haj.ipfire.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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