public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Full translation of the "es.pl" file
Date: Wed, 02 Nov 2022 20:16:16 +0100	[thread overview]
Message-ID: <c27b22bd-287f-d46d-cd95-dba2fa8fa633@ipfire.org> (raw)
In-Reply-To: <F6D2BD61-FD1F-4D3F-AFC7-7E611089DB12@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]

Hi Michael,

In the past I have created the patch for Roberto for Spanish language 
translations. I am willing to do the same for these ones when I am able 
to get around to it. Probably next week.

Regards,

Adolf.

On 02/11/2022 18:44, Michael Tremer wrote:
> 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>

-- 
Sent from my laptop


  reply	other threads:[~2022-11-02 19:16 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 [this message]
2022-11-03  8:45   ` contacto
2022-11-05 10:13     ` Robin Roevens
2022-11-08 17:28       ` Michael Tremer

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=c27b22bd-287f-d46d-cd95-dba2fa8fa633@ipfire.org \
    --to=adolf.belka@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