From: 5p9 <5p9@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Guardian 2.0 Testversion 011
Date: Fri, 29 May 2015 01:40:22 +0200 [thread overview]
Message-ID: <5567A766.6070807@ipfire.org> (raw)
In-Reply-To: <5567A4A5.2090500@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 2140 bytes --]
Hi Fischer,
thx for help! :)
> I think this is normal - and happened before - since the Guardian
> 2.0-language strings seem to be not fully implemented in the language
> files shipped with the new Core update.
i think this, too.
> I think you could either reinstall - which could lend to strings missing
> in other places so I would NOT recommend this - or simply copy the
> attached files
Okay thx for this answer. I'll test and report it.
> This gives me the chance to repeat my proposal/feature request from here:
>
https://forum.ipfire.org/viewtopic.php?f=4&t=13524&p=84922&sid=3a921f770f3b4ce8e21a734f5c9af6f4#p84922
I know, I can remember me. Does that in a bugreport or wishlist?
Great job to "Core-Update90" IPFire-Team! GEOIPBlock rockt :D
5p9
Am 29.05.2015 um 01:28 schrieb Matthias Fischer:
> On 29.05.2015 00:32, 5p9 wrote:
>> Hi(a)all,
>
> Hi!
>
>> i have a question. My Fire has became the final Core-Update 90 (stable)
>> and guardian 2 have now display-lang-bugs in the cgi.
>
> I think this is normal - and happened before - since the Guardian
> 2.0-language strings seem to be not fully implemented in the language
> files shipped with the new Core update.
>
>> Must i wait to a newest Version of guardian 2 or can i do the steps he
>> told us?
>
> I think you could either reinstall - which could lend to strings missing
> in other places so I would NOT recommend this - or simply copy the
> attached files to '/var/ipfire/addon-lang' and update the language cache
> starting "/usr/local/bin/update-lang-cache" from console. I hope I
> didn't miss a string. For me its looking good, no missing strings after
> updating.
>
> This gives me the chance to repeat my proposal/feature request from here:
> https://forum.ipfire.org/viewtopic.php?f=4&t=13524&p=84922&sid=3a921f770f3b4ce8e21a734f5c9af6f4#p84922
>
>
> Using the '/var/ipfire/addon-lang'-directory for those addons would make
> things perhaps a bit easier.
>
> Jm2C - Regards
> Matthias
>
> P.S.: Besides - update to Core 90 went ok by now, no probems detected.
> Good job - thanks! ;-)
next prev parent reply other threads:[~2015-05-28 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5551C5AC.6030909@ipfire.org>
2015-05-12 19:19 ` Stefan Schantl
2015-05-14 9:15 ` 5p9
2015-05-28 22:32 ` 5p9
2015-05-28 23:28 ` Matthias Fischer
2015-05-28 23:40 ` 5p9 [this message]
[not found] <1425131435.2685.24.camel@ipfire.org>
2015-05-10 8:08 ` Stefan Schantl
[not found] <934634537.3431881425296755846.JavaMail.root@ip-10-41-150-66.ec2.internal>
2015-03-05 18:37 ` Stefan Schantl
2015-03-02 19:51 Matthias Fischer
2015-03-02 20:20 ` Stefan Schantl
2015-03-02 20:43 ` Matthias Fischer
2015-03-02 20:59 ` Matthias Fischer
[not found] <DUB120-W2840AF412EFCF1DA7249F69C100@phx.gbl>
2015-03-02 18:35 ` Stefan Schantl
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=5567A766.6070807@ipfire.org \
--to=5p9@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