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 4jWLMs04Zlz32dV for ; Fri, 20 Nov 2026 16:27:21 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (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 4jWLMn4B2kz2yJG for ; Fri, 20 Nov 2026 16:27:17 +0000 (UTC) Received: from michael.haj.ipfire.org (michael.haj.ipfire.org [172.28.1.242]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "michael.haj.ipfire.org", Issuer "YE1" (not verified)) by mail01.ipfire.org (Postfix) with ESMTPS id 4jWLMn0nYdzLg for ; Fri, 20 Nov 2026 16:27:17 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1795192037; 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=xw7OlCnrPp83D1xjL7UgS+7bIk1yaQqeWYvPJfgU4dE=; b=Z1ppTyoZCTCqPFCvvyH7DN1oQyo4L8qHxZBYEs+r88KMH0JqJTZhwgswUDsh18EMOoxsWG 6QyuIKormJfMWoDQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1795192037; 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=xw7OlCnrPp83D1xjL7UgS+7bIk1yaQqeWYvPJfgU4dE=; b=EfT0KZx9RtU4DXtzDziDZB2vYTF+HPZNpq7+r/NmxiFgSB26J7017wN1mw7sloF3ahUYsg RgnZvY4DsF4Nc79x800BFqYAvt2kIzWC9UVW1o/WdDF6UpAqBhO5cWUNZZrpBCANn7xx0q o4tSl+5nVfFtdlZ654p3Gp3lBVZzx7HA7ThIwV8VpH/DARMuQ0Q+vOkyUJ4ySZoLSXE0Vh IVxOIvbRhnWK+cGNuJ5qd0nZlOlYn8v0TaN06dWBFeU/xUu+ncYRbTRcMqeMqaF2WlQ8kz 6lvDVjrV6BhYSixOEjdPHPZcFkVFeDgx/gth606Md40hjMzKLpFntkFBslXSkg== Received: by michael.haj.ipfire.org (Postfix, from userid 0) id 4jWLMm6NGhzTq0T; Fri, 20 Nov 2026 16:27:16 +0000 (UTC) From: Michael Tremer To: development@lists.ipfire.org Subject: Re: How to handle the new translation method on a live system? In-Reply-To: References: Date: Fri, 20 Nov 2026 16:27:16 +0000 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Message-Id: <4jWLMm6NGhzTq0T@michael.haj.ipfire.org> Hi Matthias, 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. 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. Best, Michael