From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Call for small translation (for [PATCH 1/9] pakfire: Refactor
 dblist seperating UI and logic)
Date: Thu, 07 Jul 2022 13:38:46 +0200
Message-ID: <F66FEBC9-9C8D-4D8D-8BFD-8F35531C0C6E@ipfire.org>
In-Reply-To: <626C7C30-DA39-4CBD-A8BF-6AD76F1068D4@sicho.home>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4477004405466086667=="
List-Id: <development.lists.ipfire.org>

--===============4477004405466086667==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Enjoy your holiday!

> On 6 Jul 2022, at 23:00, Robin Roevens <robin.roevens(a)disroot.org> wrote:
>=20
> Hi
>=20
> I'm afraid I will now have to leave you guys hanging for a few weeks as I l=
eft home for a vacation and I don't have access to my sources at the moment.
> But I should be able to process the pakfire patches by the end of July.
>=20
> Regards
> Robin
>=20
> Michael Tremer <michael.tremer(a)ipfire.org> schreef op 6 juli 2022 12:04:5=
0 CEST:
> Hello Robin,
>=20
> On 29 Jun 2022, at 23:31, Robin Roevens <robin.roevens(a)disroot.org> wrote:
>=20
> Hi again all
>=20
> I was noticed today that patch for which I required some opinion and
> small german translation (see below) would solve=20
> https://bugzilla.ipfire.org/show_bug.cgi?id=3D12868
>=20
> But I'm still waiting for confirmation of you guys about this last
> small (translation) issue..
>=20
> As (I think) I have cornered all remarks Michael had about that patch-
> set (https://patchwork.ipfire.org/project/ipfire/list/?series=3D2650) in
> a reworked patch-set sitting here, ready for submission (already for
> more than 3 months).=20
>=20
> I do understand that there are busy periods and things with higher
> priorities.. and that I need patience, certainly with some of the
> bigger sets I submitted up until now, but, especially in this case, I
> don't think it should take 3 months+ just to know if I should translate
> "traffic" now that I'm on it and if so, what the translation should
> be? This is a bit demotivating for me..
>=20
> I agree and I can only apologise.
>=20
> Email chains sometimes get very long and I always try to set some time asid=
e for it to work through them. It is a lot easier to just type a few lines as=
 a response to a very short email.
>=20
> I am very much interested in your work and I am trying to support you as mu=
ch as I can. I hope others will be able to contribute, too, and together we w=
ill get this over the line.
>=20
> I believe that the delays are indeed making it at lot harder because I feel=
 like I have to invest more time to figure out where we left off.
> =20
> For now I only know the opinion of Leo, so please, contribute to the
> discussion so that a decision can be made and that I can finally submit
> the reworked version of the patch-set which then can hopefully be
> implemented soon and as a bonus, even solve bug 12868.
>=20
> That sounds good to me. Thank you!
>=20
> -Michael
>=20
> Regards
>=20
> Robin
>=20
> Robin Roevens schreef op do 23-06-2022 om 23:01 [+0200]:
> Hi all
>=20
> I was forgotten about this a bit due to personal matters happening
> here
> and no further replies from you guys.
>=20
> So should I reword "Traffic" on de page headers to "Internet" as Leo
> suggested below, or rather to "RED Traffic" as I suggested, assuming
> a
> user could also use the  red interface for some other untrusted
> network, not being the internet specifically.
>=20
> And in case it should become "RED Traffic". How should I translate
> this
> in german? Would that be "ROTER Traffic" or should I rather translate
> it to "ROTER Verkehr" ? Or ?
>=20
> Dutch would be "ROOD Verkeer" and French "Trafic ROUGE"
>=20
> Regards
> Robin
>=20
> Robin Roevens schreef op wo 20-04-2022 om 23:19 [+0200]:
> Hi
>=20
> Leo Hofmann schreef op wo 20-04-2022 om 13:17 [+0200]:
> Hi Robin,
>=20
> Am 19.04.2022 um 21:14 schrieb Robin Roevens:
> Hi All
>=20
> After implementing and testing the translation discussed below,
> I
> noticed that in every page footer of the WUI there is also a
> mention of
> "Core Update XXX", which I assume should then also be
> translated
> with
> below 'core update' translation string?
>=20
> This footer is generated in
> html/themes/ipfire/include/functions.pl;
> And there I found also the "Traffic: In: XXX bit/s Out: XXX
> bit/s"
> header is generated, so I took the opportunity to also
> translate
> that
> string:
>=20
> En:
> 'traffic stat title' =3D> 'Traffic',
> 'traffic stat in' =3D> 'In',
> 'traffic stat out' =3D> 'Out',
>   Nl:
> 'traffic stat title' =3D> 'Verkeer',
> 'traffic stat in' =3D> 'In',
> 'traffic stat out' =3D> 'Uit',
>=20
> Fr:
> 'traffic stat title' =3D> 'Trafic',
> 'traffic stat in' =3D> 'Entr=C3=A9e',
> 'traffic stat out' =3D> 'Sortie',
>=20
> De:
> 'traffic stat title' =3D> 'Traffic',
> 'traffic stat in' =3D> 'Ein',
> 'traffic stat out' =3D> 'Aus',
>=20
> Could anyone confirm the german translation for this ? (I'm
> mainly
> doubting 'Ein' as it translates to "one" for me, so I'm not
> sure
> if
> it
> translates to 'in' also in this context ?)
> In the traffic graphs we use "Eingehender Verkehr" and
> "Ausgehender
> Verkehr". So in my opinion, "Ein" would be a suitable short form.
> And for 'Traffic' I wondered
> if that shouldn't be 'Verkehr'?
>=20
> AFAIK, this only represents traffic on RED and not the total
> firewall
> load.
> Maybe we should change it to "Internet", "WAN traffic" or
> something
> similar?
> Maybe we should name it "RED Traffic" then?  That should cover any
> special purpose/config a user gave to the RED interface.
>=20
> Robin
>=20
>=20
> Regards
> Leo
>=20
> I'm quite certain about the french translation, but I'll check
> with
> St=C3=A9phane anyway if there are maybe more appropriate words in
> this
> context.
>=20
> Unless it is decided here that we should not translate those
> things
> in
> the header and footer of the WUI?
>=20
> Regards
>=20
> Robin
>=20
> Michael Tremer schreef op ma 28-03-2022 om 15:03 [+0100]:
> Guys, what is happening here? Did you all forget you spoke
> German?
>=20
> Robin, please use these strings for German:
>=20
> 'core update' =3D> =E2=80=98Core-Update',
> 'pak update' =3D> =E2=80=98Paketupdate',
> 'release' =3D> =E2=80=98Release',
> 'version' =3D> 'Version',
>=20
> On 28 Mar 2022, at 07:18, Robin
> Roevens<robin.roevens(a)disroot.org>
> wrote:
>=20
> I received a French translation from St=C3=A9phane.
> Any other translations? German?
>=20
> Regards
> Robin
>=20
> Robin Roevens<robin.roevens(a)disroot.org>  schreef op 23
> maart
> 2022
> 22:09:53 CET:
> Hi All
>=20
> For the changes in "[PATCH 1/9] pakfire: Refactor dblist
> seperating
> UI
> and logic", Michael pointed out that we should take
> advantage
> of
> the
> code change to translate a few extra strings:
>=20
> 'core update' =3D> 'Core-Update',
> 'pak update' =3D> 'Update',
> 'release' =3D> 'Release',
> 'version' =3D> 'Version',
>=20
> As used on pakfire.cgi listing the available updates:
> $Lang::tr{'core update'} -- $pakfire_status{'CoreVersion'}
> --
> $Lang::tr{'release'}: $pakfire_status{'Release'} ->
> $pakfire_status{'AvailableRelease'}
>=20
> For example:
> Core-Update -- 2.27-x86-64 -- Release: 163 -> 164
>=20
> and
> $Lang::tr{'pak update'}: $pak -- $Lang::tr{'version'}:
> $upgradelist{$pak}{'ProgVersion'} ->
> $upgradelist{$pak}{'AvailableProgVersion'} --
> $Lang::tr{'release'}:
> $upgradelist{$pak}{'Release'} ->
> $upgradelist{$pak}{'AvailableRelease'}
>=20
> For example:
> Update: zabbix-agentd -- Version: 4.2.6 -> 5.0.21 --
> Release:
> 4
> ->
> 5
>=20
> Could anyone on this list capable of translating these 4
> strings in
> any
> other language please reply with translations, so that I
> can
> immediately integrate them in the patch.
>=20
> I already have translations for Dutch.
>=20
> Many thanks
>=20
> Robin
>=20
> --=20
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door MailScanner en lijkt schoon te zijn.
>=20
>=20
> --=20
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door MailScanner en lijkt schoon te zijn.
>=20
>=20
>=20
>=20
> --=20
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door MailScanner en lijkt schoon te zijn.
>=20
>=20
>=20
> --=20
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door MailScanner en lijkt schoon te zijn.
>=20
>=20
> --=20
> Dit bericht is gescanned op virussen en andere gevaarlijke=20
> inhoud door MailScanner en lijkt schoon te zijn.


--===============4477004405466086667==--