From: Bernhard Bitsch <Bernhard.Bitsch@gmx.de>
To: development@lists.ipfire.org
Subject: Aw: Re: [PATCH] Fix hardcoded strings in pppsetup.cgi
Date: Tue, 02 Jun 2015 10:51:13 +0200 [thread overview]
Message-ID: <trinity-294547dc-41d4-427b-867e-7fbd5967fa1c-1433235073319@3capp-gmx-bs44> (raw)
In-Reply-To: <op.xzlcb2yucahio0@atl-uetersen.atlantisgmbh.local>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
> Gesendet: Dienstag, 02. Juni 2015 um 08:58 Uhr
> Von: Larsen <larsen007(a)web.de>
> An: "Bernhard Bitsch" <Bernhard.Bitsch(a)gmx.de>
> Cc: "development(a)lists.ipfire.org" <development(a)lists.ipfire.org>
> Betreff: Re: Aw: [PATCH] Fix hardcoded strings in pppsetup.cgi
>
> Hi Bernhard,
>
> so this means that "'pptp netconfig' => ''," should be missing completely
> instead of setting an empty string?
>
yes.
>
> Lars
>
>
> On Mon, 01 Jun 2015 23:57:08 +0200, Bernhard Bitsch
> <Bernhard.Bitsch(a)gmx.de> wrote:
>
> > Language files should contain translations only.
> > The process for building the language cache for the language <lang>
> > desired is
> > - read en.pl files ( the base definition )
> > - read <lang>.pl files ( replacing english terms )
> > --> all translated strings appear in <lang>, untranslated strings are in
> > english
> > --> to find untranslated strings, computed the complement of set of keys
> > in en.pl and set of keys in <lang>.pl
> >
> > Hope, I could clarify a bit.
> >
> > -Bernhard
> >
next prev parent reply other threads:[~2015-06-02 8:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1433079323.3370.92.camel@ipfire.org>
2015-06-01 20:59 ` Larsen
2015-06-01 21:57 ` Aw: " Bernhard Bitsch
2015-06-02 6:58 ` Larsen
2015-06-02 8:51 ` Bernhard Bitsch [this message]
2015-06-02 10:04 ` Aw: " Larsen
2015-06-02 19:49 ` Larsen
2015-06-02 20:01 ` Michael Tremer
2015-06-02 21:05 ` Larsen
2015-06-02 21:07 ` Larsen
2015-06-04 16:23 ` Michael Tremer
2015-06-04 20:52 ` Problem with whitespace in patches Larsen
2015-06-05 13:25 ` Michael Tremer
2015-06-05 13:29 ` Larsen
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=trinity-294547dc-41d4-427b-867e-7fbd5967fa1c-1433235073319@3capp-gmx-bs44 \
--to=bernhard.bitsch@gmx.de \
--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