From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Full translation of the "es.pl" file
Date: Tue, 08 Nov 2022 17:28:12 +0000 [thread overview]
Message-ID: <E65A1730-03D7-4E4C-A8C4-645D81428728@ipfire.org> (raw)
In-Reply-To: <6a3046ef9a5ab17564df11bc84982e8be34c9f66.camel@sicho.home>
[-- Attachment #1: Type: text/plain, Size: 4415 bytes --]
Hello,
> On 5 Nov 2022, at 10:13, Robin Roevens <robin.roevens(a)disroot.org> wrote:
>
> Hi
>
> During my work in services.cgi, I also noticed "Addon" not being
> translated. But I didn't correct that (should have though :-).
>
> So I was quickly looking at that now, but I would need the singular
> "Addon" (at least in latest services.cgi, not sure about earlier
> versions, didn't check) and that one is not defined in en.pl, only the
> plural "Addons" is defined there .. but in de.pl and fr.pl a singular
> "Addon" is actually defined:
>
> de.pl:
> 'addon' => 'Add-Ons',
> 'addons' => 'Add-Ons',
>
> fr.pl:
> 'addon' => 'Module additionnel',
> 'addons' => 'Modules additionnels',
>
> For the german translation, it seems to me that the singular 'addon' is
> actually 'translated' to plural ? Should I correct this to 'Add-On' ?
> French looks correct to me.
>
> And I will then add singular 'addon' to English and Dutch.
>
> So please let me know about the German translation?
Not sure whether it is too late for this, but in German, I would say historically it would have been “Addon”, but “Add-on” probably is a better choice because it is consistent and more and more English words have made it into the language.
-Michael
> Then I will submit a patch correcting this and translating 'addon' in
> services.cgi.
> Then Roberto (and/or Adolf) can concentrate on only the Spanish
> translation.
>
> Regards
> Robin
>
> contacto(a)northsecure.es schreef op do 03-11-2022 om 09:45 [+0100]:
>> Hi Michael.
>>
>> The reason for modifying the "services.cgi" is because in that line
>> there is no variable that changes the word "Addons" to "Complementos"
>> and to follow a single criterion and always call the complements
>> "Complementos", I modified this so that reflect the change. I think
>> it's well done, feel free to correct it if it's not. (As I already
>> mentioned, I don't know how to program).
>>
>> There are expressions that are perhaps very "Spanished", since
>> Firewall, I have put "Cortafuegos" and I don't know which is the
>> best. There is another one that I have chosen to leave in English,
>> since for example "Host", it is better in English since in Spanish,
>> "Huésped" (Guest) is less understandable.
>>
>> If you want me to translate anything related to IPFire 3 (or anything
>> else), send me things to translate.
>>
>> BR.
>>
>> Roberto.
>>
>> -----Mensaje original-----
>> De: Michael Tremer <michael.tremer(a)ipfire.org>
>> Enviado el: miércoles, 2 de noviembre de 2022 18:45
>> Para: contacto(a)northsecure.es
>> CC: development(a)lists.ipfire.org
>> Asunto: Re: Full translation of the "es.pl" file
>>
>> Hello Roberto,
>>
>> Thanks for your email.
>>
>> Is there any chance that you have ever worked with Git? We normally
>> submit changes here using patch files which are text-based and easier
>> to review and merge into the development tree.
>>
>> It would also be great if you could configure your client to send
>> plain text emails.
>>
>> I am very interested in updating the Spanish translation. Thank you
>> for working on that. We don’t have anyone on the team who speaks
>> Spanish.
>>
>> Why is the change needed in the services.cgi?
>>
>> -Michael
>>
>>> On 27 Oct 2022, at 18:30, <contacto(a)northsecure.es>
>>> <contacto(a)northsecure.es> wrote:
>>>
>>> Hello everyone. I don't know if I can contribute something (I'm
>>> null in programming) but at least I can translate texts into
>>> Spanish. You can send me any text you want me to translate. I have
>>> always seen that the translation of the IPFire in Spanish was
>>> halfway and I have translated it completely. I have used the file
>>> that was already there and merging it with the "en.pl" (adding what
>>> was missing) I have generated a complete one. The only thing, in
>>> the "services.cgi" file, you have to make the following
>>> modification in line 141: &Header::openbox('100%', 'left',
>>> "$Lang::tr{addons} - $Lang::tr{services}");
>>> P.D.: I hope it's alright now. Thanks Michael for the effort to
>>> solve the problem of sending the mail.
>>> Saludos. Roberto Peña González
>>> <es.zip>
>>
>>
>
> --
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door MailScanner en lijkt schoon te zijn.
>
prev parent reply other threads:[~2022-11-08 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000c01d8ea29$bf926230$3eb72690$@northsecure.es>
2022-11-02 17:44 ` Michael Tremer
2022-11-02 19:16 ` Adolf Belka
2022-11-03 8:45 ` contacto
2022-11-05 10:13 ` Robin Roevens
2022-11-08 17:28 ` Michael Tremer [this message]
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=E65A1730-03D7-4E4C-A8C4-645D81428728@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