From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4ZLFvJ4gwlz333S for ; Sun, 23 Mar 2025 12:32:44 +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) client-signature RSA-PSS (4096 bits)) (Client CN "mail01.haj.ipfire.org", Issuer "R10" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4ZLFvF0P7qz32vy for ; Sun, 23 Mar 2025 12:32:41 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4ZLFvC6jTDz5Yc; Sun, 23 Mar 2025 12:32:39 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1742733160; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=NS+092PJCRCGPD3QAPh+rGyQfcQawnWI1UAPjhANprM=; b=N2xUOCn/Z97rgzqCAd3fr/EsKWr313EsDdsQsNUtmjjd9YqGSAKsQN4B4brVHi40EWRbtv bezh0ETeRKIV5EBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1742733160; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=NS+092PJCRCGPD3QAPh+rGyQfcQawnWI1UAPjhANprM=; b=Drf8z2wt1iYw3DcdlyxM009X28VuaRRiT7si+O2lT2TARbs0iWf4MjrvyJdOKqoC2b9TNQ Kj2z7yjBH8dT/B0cTan3xhk79qFjnRhXe86y2tr+K1YjGJ1H2OzI0Yixl/jv3GB1sRYbK8 iXISbD2QQLTXhHrad1VgxwaqA91yjl1uTMbCmfIkuGSwN63gAVJNdt5Zl0Dkl+AzsRFKW+ 3sNgP3q7j9VajXWzKAYRT2IOgHjlkS6em3V+fsbaxhi8M3PP1ZGIrW89Go52frhe+vnLXB B0ypYXSq3XU17Fynsr5lno39e/TElcXR/Uc7SxtIc2S7h5HT7CO4prZDO1XEiw== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: Upcoming pakfire.cgi changes. From: Michael Tremer In-Reply-To: Date: Sun, 23 Mar 2025 12:32:39 +0000 Cc: development@lists.ipfire.org Content-Transfer-Encoding: quoted-printable Message-Id: <40F9151E-D5E6-4186-9BEE-6EE7F002770A@ipfire.org> References: To: Stephen Cuka Hello, Thanks for taking this conversation to here. Let=E2=80=99s also keep it = here... > On 23 Mar 2025, at 10:48, Stephen Cuka wrote: >=20 > Hello, >=20 > In reference to the community post: >=20 > https://community.ipfire.org/t/core-192-unexpected-upgrade/13760 >=20 > I'm going to be submitting a set of patches for changes to pakfire.cgi = to fix some problems, do some cleanup, and hopefully improve the overall = consistency and appearance of the page. >=20 > I wanted to give advance notice of this so that when the patches start = coming through you'll be aware of what I'm up to. *Received* > Below is the list of changes that I'm planning to make. >=20 > Let me know of questions, comments or concerns. >=20 > Regards, >=20 > Stephen >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > pakfire.cgi patches >=20 >=20 > 1. Add new translation 'pakfire upgrade' to replace 'upgrade'. The = 'upgrade' tr is only used in pakfire.cgi and this will move the tr into = the pakfire translation block. >=20 > 2. Add new translation 'pakfire install' to replace 'install'. The = 'install' tr is only used in pakfire.cgi and this will move the tr into = the pakfire translation block. >=20 > 3. Add translation 'pakfire updates' to en.pl and it.pl. It already = exists in the other languages. The 'available updates' tr used in = pakfire.cgi will be changed to 'pakfire updates' which will be in the = pakfire translation block. >=20 > 4. Add translation 'pakfire refresh list'. pakfire.cgi currently = uses 'calamaris refresh list'. >=20 > 5. Add translations 'pakfire resolvedeps wait', 'pakfire dependencies = found' and 'pakfire no dependencies found' to use on install and remove = confirmation pages. >=20 > 6. Add new translations 'pakfire confirm updates' and 'pakfire = updating' for new upgrade confirmation page. >=20 > 7. Update pakfire.cgi to use 'pakfire upgrade', 'pakfire install', = 'pakfire updates' and 'pakfire refresh list' instead of 'upgrade', = 'install', 'available updates' and 'calamaris refresh list'. The translation issues seem to be a much bigger problem than I thought. > 8. Update pakfire.cgi to convert icons to buttons on the main and = confirmation pages. Disable Install, Remove and Upgrade buttons if = nothing to do. Hmm, I think this could become a bit confusing, because even though = there might not be anything to do right now, a greyed-out button will = let the user know where to go whenever there is something to do. I am also concerned about potential layout breakages if there are so = many changes. The entire web UI is incredibly based on tables and = removing a cell somewhere might either mess up the layout or you will = need to add a lot of code for simple things. I would rather look at = investing this time to replace the web UI as a whole. > 9. Update pakfire.cgi to add confirmation page for upgrades. The = confirmation page will do a 'pakfire update' to ensure that the local = pakfire database is current and then display updates to be made and = request confirmation. The box title will be 'pakfire upgrade'. Agreed. > 10. Update pakfire.cgi to change box titles for install and remove = confirmation pages from 'request' to 'pakfire install' and 'remove'. >=20 > 11. Update pakfire.cgi to change 'abort' on confirmation screens to = 'cancel'. >=20 > 12. Update pakfire.cgi install and remove confirmation pages. Display = 'pakfire resolve wait' while 'pakfire resolvedeps' is running. Only = display 'Need to install...' lines from 'pakfire resolvedeps' output. = Remove spaces between resolvedeps output lines to tighten up the output. = Display "Dependancies found:' before list of dependancies or 'No = dependancies found.' if none found. The 'Checking >=20 > 13. Update pakfire.cgi to change 'uninstall' to 'remove' on = confirmation page. The main page uses 'remove' for the minus sign, but = the confirmation page uses 'uninstall'. I never know which one would be the best term. SuSE is even using = =E2=80=9Cerase=E2=80=9D. I think remove makes the most sense and is also = visually different from =E2=80=9Cinstall=E2=80=9D - unlike = =E2=80=9Cuninstall=E2=80=9D. > 14. Update pakfire.cgi to adjust some spacing and alignment. >=20 > 15. Add missing translations for the cases where the translations are = English=3D>English instead of English=3D>Language. Yeah, this is a difficult topic. In many languages there are native = words for things, but everyone is using the English term as it is much = easier and to the point. So in German you would still use =E2=80=9CUpdates= =E2=80=9D although there is a word like =E2=80=9CAktualisierungen=E2=80=9D= . So be careful with Google translate :) > 16. Clean up > Delete 'upgrade' tr. It is now unused. > Delete 'available updates' tr. It is now unused. > Delete 'abort' tr. It is now unused. > Delete 'request' tr. It is now unused. > Delete 'uninstall' tr. It is now unused. > Delete 'pakfire possible dependancy' tr. It is now unused. > Delete 'pakfire core update auto' tr. It is not used. > Delete 'pakfire health check' tr. It is not used. > Delete 'pakfire update daily' tr. It is not used. Agreed. You know about =E2=80=9C./make.sh lang=E2=80=9D? > Note on translations: >=20 > I am doing translations with multiple web based translation utilities. = Where the results don't match between the utilities, I look for other = similar translations in the applicable *language*.pl file and pick the = one that seems to be most in context or consistent. I think this is a good start. We have people on the team who can help = with German, Dutch, maybe a bit of French. There are some Italian people = on the forum which can help. For the rest, I would consider those = translations abandoned and I think it is fine to just do nothing here = and the software will automatically put the English version which at = least is correct. > Where titles and button text have multiple words. I capitalize the = words. For example 'Available updates:' becomes 'Available Updates:' = and 'Liste aktualisieren' becomes 'Liste Aktualisieren'. Yes, I like the words being capitalised in English. It looks a bit wrong = to me in German, because only nouns are capitalised. Not sure how people = feel about other languages. Best, -Michael >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 >=20 >=20 >=20 >=20 >=20