From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: 'resolv' => 'Resolv-Retry', = Obsolete?
Date: Sat, 04 Feb 2017 18:34:48 +0100 [thread overview]
Message-ID: <67a4669e-1a9b-a040-3e23-b616fe70012f@ipfire.org> (raw)
In-Reply-To: <9dca0521-c4de-dcdb-902d-40190ed20729@web.de>
[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]
Hi Timmothy,
I'm a ~bit puzzled, to say the least.
Is this right or is someone kidding me?
Unused translation strings:
de.pl: 669
en.pl: 775
es.pl: 620
fr.pl: 630
it.pl: 697
nl.pl: 693
pl.pl: 620
ru.pl: 621
tr.pl: 705
For a start:
Why not delete these unused entries!?
I'm not so good in bash-programming, but how about something like this:
UNUSED_STRINGS=(
'[STRING_FROM_LANGUAGE_ISSUES_XY]'
'[NEXT_STRING...]'
'[NEXT_STRING...]'
.
.
.
for i in ${UNUSED_STRINGS[@]}; do
[SOME_SED_AND_GREP_COMMANDS{i}_TO_DELETE_UNUSED_ENTRIES_LINE_BY_LINE_FROM_XY.PL_FILES_ONE_BY_ONE]
.
.
.
I'd do it "one by one" but this is a bit too much for a hand job... ;-))
Ideas and programming examples are welcome!
Best,
Matthias
On 04.02.2017 17:32, IT Superhack wrote:
> Hello Matthias,
>
> as far as I am aware, there are a lot of unused translated
> strings (and of untranslated used) which seem to be listed in
> doc/language_issues.[language]
>
> Example:
> http://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=doc/language_issues.en;h=f2b6eb7b4aa68fde7a0d14594b5bd96d842fba85;hb=f2b6eb7b4aa68fde7a0d14594b5bd96d842fba85
>
> It seems like some strings are obsolete and can be safely
> deleted - but I don't know for sure.
>
> Thanks for caring about #10972 and #11271.
>
> Best regards,
> Timmothy Wilson
>
> Matthias Fischer:
>> Hi,
>>
>> ...speaking about typos: ;-)
>>
>> Can anybody tell me for what is the translation...
>>
>> 'resolv' => 'Resolv-Retry'
>>
>> ...good for?
>>
>> I can't find an appropriate "Lang::tr"-translation command. Is this
>> string obsolete?
>>
>> Best,
>> Matthias
>>
>
>
next prev parent reply other threads:[~2017-02-04 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 16:19 Matthias Fischer
2017-02-04 16:32 ` IT Superhack
2017-02-04 17:34 ` Matthias Fischer [this message]
[not found] <bd4c095b-9fea-9f36-9f78-d9246eacbb21@ipfire.org>
2017-02-06 15:26 ` ummeegge
2017-02-06 18:29 ` Matthias Fischer
[not found] <0436f51f-7ffc-cccf-d3c5-87c66b4c4741@ipfire.org>
2017-02-07 9:52 ` ummeegge
2017-02-07 18:19 ` Matthias Fischer
2017-02-08 4:18 ` ummeegge
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=67a4669e-1a9b-a040-3e23-b616fe70012f@ipfire.org \
--to=matthias.fischer@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