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 4jWC1X6G9Mz2xnL for ; Fri, 20 Nov 2026 10:56:00 +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 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "YR1" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4jWC1T2ltZz2xLm for ; Fri, 20 Nov 2026 10:55:57 +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 4jWC1R6CRZz4cf for ; Fri, 20 Nov 2026 10:55:55 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1795172156; 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; bh=EhO98S5Q6Ta7M9kp1GNk/UCKlrgjaFTV67swEnCT28E=; b=tvpQp2cG9DTuJn5PkI11PP/Vt4HztIZ+g5rldeBO9Uk16wX+xKyIPkBkMerjVrlxyJsTLt Sw7b8TvdySSVscCg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1795172156; 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; bh=EhO98S5Q6Ta7M9kp1GNk/UCKlrgjaFTV67swEnCT28E=; b=gFwqNdTKZlkUeRm8etz3gPI0vt0LgcIXiIyLXFG66qP1/vKRJ18mOTHfMDs0eH+qgghQ+M DBWFIlbMjBpUAcfZqx9JcvF3j+itS6+03/nPzy7ryzeShc56wU/wBzUIJBimVxMS7Byjep FGGVf8RIsTDbfSUEWGhIzNJQDB9T+HTbXkQ3vn2Sy9p7Le6cMytDl2XCZkUTY3AmFo4NLe 6mf1cLiu5YDi8TcHuSf6N3tUdgEkcyiROvr1Qw6haPhxLZvRryHCIaqGjD72UCI03qKMeo 428LG22vXb/VaC8urTa7tG2MgK+t8kKfNSQct8/gBFohl72Q349mMQPhmUYZZg== Message-ID: Date: Fri, 20 Nov 2026 11:55:48 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 From: Matthias Fischer Subject: How to handle the new translation method on a live system? To: "IPFire: Development-List" Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi all, I have some questions how to handle the way IPFire (since Core 206) deals with translations on a live system. Until Core 206 I could follow the procedure as described in the wiki: => https://www.ipfire.org/docs/devel/ipfire-2-x/translate Now everything has changed - the wiki is outdated. ;-) 'addon-langs' is gone, 'langs' is gone and 'update-lang-cache' has been deleted. Ok, no problem, but what now? E.g., I find a typo and want to correct it. Now. Without starting one of my 'Devels' and compiling the whole thing all over again. How do I do this? All I can find - on an installed system(!) - are binary language files under '/usr/share/locale/[LANGUAGE]/LC_MESSAGES/...' which are impossible to edit. Until Core 205 I could edit the appropriate language file, run 'update-lang-file' and was done. How can I do this with Core 206? I searched but wasn't successful. Could 'someone' please give me a hint? Best Matthias