From: Robin Roevens <robin.roevens@disroot.org>
To: development@lists.ipfire.org
Subject: Re: Call for small translation (for [PATCH 1/9] pakfire: Refactor dblist seperating UI and logic)
Date: Tue, 19 Apr 2022 21:14:19 +0200 [thread overview]
Message-ID: <aec75321968f37c900774e49d86b602bb9d70a01.camel@sicho.home> (raw)
In-Reply-To: <455D3150-2B8B-48C4-8C92-7220443E71FE@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3661 bytes --]
Hi All
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?
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:
En:
'traffic stat title' => 'Traffic',
'traffic stat in' => 'In',
'traffic stat out' => 'Out',
Nl:
'traffic stat title' => 'Verkeer',
'traffic stat in' => 'In',
'traffic stat out' => 'Uit',
Fr:
'traffic stat title' => 'Trafic',
'traffic stat in' => 'Entrée',
'traffic stat out' => 'Sortie',
De:
'traffic stat title' => 'Traffic',
'traffic stat in' => 'Ein',
'traffic stat out' => 'Aus',
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 ?) And for 'Traffic' I wondered
if that shouldn't be 'Verkehr'?
I'm quite certain about the french translation, but I'll check with
Stéphane anyway if there are maybe more appropriate words in this
context.
Unless it is decided here that we should not translate those things in
the header and footer of the WUI?
Regards
Robin
Michael Tremer schreef op ma 28-03-2022 om 15:03 [+0100]:
> Guys, what is happening here? Did you all forget you spoke German?
>
> Robin, please use these strings for German:
>
> 'core update' => ‘Core-Update',
> 'pak update' => ‘Paketupdate',
> 'release' => ‘Release',
> 'version' => 'Version',
>
> > On 28 Mar 2022, at 07:18, Robin Roevens <robin.roevens(a)disroot.org>
> > wrote:
> >
> > I received a French translation from Stéphane.
> > Any other translations? German?
> >
> > Regards
> > Robin
> >
> > Robin Roevens <robin.roevens(a)disroot.org> schreef op 23 maart 2022
> > 22:09:53 CET:
> > Hi All
> >
> > 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:
> >
> > 'core update' => 'Core-Update',
> > 'pak update' => 'Update',
> > 'release' => 'Release',
> > 'version' => 'Version',
> >
> > 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'}
> >
> > For example:
> > Core-Update -- 2.27-x86-64 -- Release: 163 -> 164
> >
> > and
> > $Lang::tr{'pak update'}: $pak -- $Lang::tr{'version'}:
> > $upgradelist{$pak}{'ProgVersion'} ->
> > $upgradelist{$pak}{'AvailableProgVersion'} -- $Lang::tr{'release'}:
> > $upgradelist{$pak}{'Release'} ->
> > $upgradelist{$pak}{'AvailableRelease'}
> >
> > For example:
> > Update: zabbix-agentd -- Version: 4.2.6 -> 5.0.21 -- Release: 4 ->
> > 5
> >
> > 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.
> >
> > I already have translations for Dutch.
> >
> > Many thanks
> >
> > Robin
> >
> > --
> > Dit bericht is gescanned op virussen en andere gevaarlijke
> > inhoud door MailScanner en lijkt schoon te zijn.
> >
> >
> > --
> > Dit bericht is gescanned op virussen en andere gevaarlijke
> > inhoud door MailScanner en lijkt schoon te zijn.
>
>
--
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.
next prev parent reply other threads:[~2022-04-19 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AB791BDC-08B2-4757-A7B5-81715ABFBCD7@sicho.home>
2022-03-28 14:03 ` Michael Tremer
2022-04-19 19:14 ` Robin Roevens [this message]
2022-04-20 11:17 ` Leo Hofmann
2022-04-20 21:19 ` Robin Roevens
2022-06-23 21:01 ` Robin Roevens
2022-06-29 22:31 ` Robin Roevens
2022-07-06 10:04 ` Michael Tremer
[not found] <626C7C30-DA39-4CBD-A8BF-6AD76F1068D4@sicho.home>
2022-07-07 11:38 ` Michael Tremer
[not found] <9EB2EA84-CCA9-481A-B11E-5375A721119D@gmail.com>
2022-07-02 15:48 ` Stefan Schantl
2022-03-23 21:09 Robin Roevens
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=aec75321968f37c900774e49d86b602bb9d70a01.camel@sicho.home \
--to=robin.roevens@disroot.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