Hello Robin,
On 29 Jun 2022, at 23:31, Robin Roevens <robin.roevens@disroot.org> wrote:
Hi again all
I was noticed today that patch for which I required some opinion and
small german translation (see below) would solve
https://bugzilla.ipfire.org/show_bug.cgi?id=12868
But I'm still waiting for confirmation of you guys about this last
small (translation) issue..
As (I think) I have cornered all remarks Michael had about that patch-
set (https://patchwork.ipfire.org/project/ipfire/list/?series=2650) in
a reworked patch-set sitting here, ready for submission (already for
more than 3 months).
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..
I agree and I can only apologise.
Email chains sometimes get very long and I always try to set some time aside 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.
I am very much interested in your work and I am trying to support you as much as I can. I hope others will be able to contribute, too, and together we will get this over the line.
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.
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.
That sounds good to me. Thank you!
-Michael
Regards
Robin
Robin Roevens schreef op do 23-06-2022 om 23:01 [+0200]:
Hi all
I was forgotten about this a bit due to personal matters happening
here
and no further replies from you guys.
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.
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 ?
Dutch would be "ROOD Verkeer" and French "Trafic ROUGE"
Regards
Robin
Robin Roevens schreef op wo 20-04-2022 om 23:19 [+0200]:
Hi
Leo Hofmann schreef op wo 20-04-2022 om 13:17 [+0200]:
Hi Robin,
Am 19.04.2022 um 21:14 schrieb Robin Roevens:
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 ?)
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'?
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.
Robin
Regards
Leo
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@disroot.org>
wrote:
I received a French translation from Stéphane.
Any other translations? German?
Regards
Robin
Robin Roevens<robin.roevens@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.
--
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.