From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/9] pakfire: Refactor dblist seperating UI and logic
Date: Wed, 23 Mar 2022 20:49:32 +0000 [thread overview]
Message-ID: <D1C65FD3-B24D-42B7-BF6D-3CA013AE8B6F@ipfire.org> (raw)
In-Reply-To: <a96eb14da6466f29199cd3fa1d6775328e8acdb7.camel@sicho.home>
[-- Attachment #1: Type: text/plain, Size: 1896 bytes --]
Hello,
> On 23 Mar 2022, at 19:18, Robin Roevens <robin.roevens(a)disroot.org> wrote:
>
> Hi Michael
>
> Robin Roevens schreef op di 22-03-2022 om 13:39 [+0100]:
>>>> diff --git a/html/cgi-bin/pakfire.cgi b/html/cgi-bin/pakfire.cgi
>>>> index 65c67fb90..30a23128b 100644
>>>> --- a/html/cgi-bin/pakfire.cgi
>>>> +++ b/html/cgi-bin/pakfire.cgi
>>>> @@ -370,7 +370,17 @@ print <<END;
>>>> <select name="UPDPAKS"
>>>> class="pflist" size="5" disabled>
>>>> END
>>>>
>>>> - &Pakfire::dblist("upgrade", "forweb");
>>>> + my %coredb = &Pakfire::coredbinfo();
>>>> + if (defined $coredb{'AvailableRelease'}) {
>>>> + print "<option value=\"core\">Core-Update --
>>>> $coredb{'CoreVersion'} -- Release: $coredb{'Release'} ->
>>>> $coredb{'AvailableRelease'}</option>\n";
>>>> + }
>>>
>>> The strings “Core-Update” (without the dash) and “Release” should
>>> be
>>> translated so that they make sense in other languages. You can do
>>> that with $Lang::tr (I am sure you know).
>> Agreed, I don't think it was originally in this place as this came
>> out
>> of the previous dblist function. But you are right, I will use
>> Lang::tr
>>
>
> I looked in the translation files, and currently there doesn't seem to
> be a translation string for "Core Update" and "Release". Should I just
> add it (to English and Dutch, I can)? Or did I overlook it ?
Yes, please just add the strings that you will need.
There are plenty of people who are native Germans here. Please get one of them to contribute the German strings. I don’t know who else we have on this list, but of course other languages are welcome too :)
>
> Regards
>
> Robin
>
> --
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door MailScanner en lijkt schoon te zijn.
>
next prev parent reply other threads:[~2022-03-23 20:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 22:56 [PATCH 0/9] pakfire: remove dup. code + seperate ui/logic Robin Roevens
2022-03-09 22:56 ` [PATCH 1/9] pakfire: Refactor dblist seperating UI and logic Robin Roevens
2022-03-21 16:18 ` Michael Tremer
2022-03-22 12:39 ` Robin Roevens
2022-03-23 19:18 ` Robin Roevens
2022-03-23 20:49 ` Michael Tremer [this message]
2022-03-09 22:56 ` [PATCH 2/9] pakfire: Replace duplicate code with dblist functioncall Robin Roevens
2022-03-21 16:20 ` Michael Tremer
2022-03-09 22:56 ` [PATCH 3/9] pakfire: Replace dbgetlist duplicate code Robin Roevens
2022-03-21 16:21 ` Michael Tremer
2022-03-09 22:56 ` [PATCH 4/9] pakfire: Replace coreupdate_available " Robin Roevens
2022-03-21 16:21 ` Michael Tremer
2022-03-22 12:42 ` Robin Roevens
2022-03-23 21:50 ` Robin Roevens
2022-03-09 22:56 ` [PATCH 5/9] pakfire: Optimize upgradecore function Robin Roevens
2022-03-21 16:24 ` Michael Tremer
2022-03-22 12:58 ` Robin Roevens
2022-03-22 15:16 ` Michael Tremer
2022-03-09 22:56 ` [PATCH 6/9] pakfire: Add list upgrade functionality Robin Roevens
2022-03-21 16:33 ` Michael Tremer
2022-03-22 12:59 ` Robin Roevens
2022-03-09 22:56 ` [PATCH 7/9] pakfire: Refactor status function separating UI and logic Robin Roevens
2022-03-21 16:28 ` Michael Tremer
2022-03-23 19:56 ` Robin Roevens
2022-03-23 20:48 ` Michael Tremer
2022-03-09 22:56 ` [PATCH 8/9] pakfire: Add getmetadata function Robin Roevens
2022-03-21 16:32 ` Michael Tremer
2022-03-22 13:28 ` Robin Roevens
2022-03-23 11:28 ` Michael Tremer
2022-03-09 22:56 ` [PATCH 9/9] pakfire: Redesign update output and workflow Robin Roevens
2022-03-21 16:36 ` Michael Tremer
2022-03-22 18:32 ` Robin Roevens
2022-03-23 10:30 ` Michael Tremer
2022-03-09 23:46 ` [PATCH 0/9] pakfire: remove dup. code + seperate ui/logic Tom Rymes
2022-03-09 23:56 ` Paul Simmons
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=D1C65FD3-B24D-42B7-BF6D-3CA013AE8B6F@ipfire.org \
--to=michael.tremer@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