Date:  Mon, 14 Jan 2008 12:07:28 +0100
From:  Jes Kasper Klittum <jes (at mark) enavn.com>
Subject:  [coba-e:11719] Re: Rationalizing BQ localization files?
To:  coba-e (at mark) bluequartz.org
Message-Id:  <478B4270.1040009 (at mark) enavn.com>
In-Reply-To:  <478745B3.1060704 (at mark) enavn.com>
References:  <478745B3.1060704 (at mark) enavn.com>
X-Mail-Count: 11719

Doesn't anyone have any comments about this? :)

Jes

Jes Kasper Klittum skrev:
> Hello blues,
> 
> I am almost done with the Danish translation of the current BQ. However, 
> I think the original strings should have a overhaul, as it seems to 
> contain a whole lot of repetitions. F.ex. the strings below, which I am 
> certain I have translated more than 20 times:
> 
> "Please enter a series of four numbers between 0 and 255 separated by 
> periods.  For example, 192.168.1.1 is a valid entry."
> 
> Why does this string appear so many times, instead of just existing once 
> and being then have the localization engine calling one specific string 
> instead of having 20 strings resulting in the same translation?
> 
> Also a lot of translations contain the same string with a small 
> variation, f.ex:
> 
> "Please enter a series of four numbers between 0 and 255 separated by 
> periods.  For example, 192.168.1.1 is a valid entry."
> 
> "Please enter a series of four numbers between 0 and 255 separated by 
> periods.  For example, 255.255.255.0 is a valid entry."
> 
> Why not also make the parts of this string, where the actual IP is, in 
> this example in to another string, like:
> 
> msgid="gateway_exmpl"
> msgstr=255.255.255.0"
> 
> msgid="ip_addr_exmpl"
> msgstr=192.168.1.1"
> 
> and then have the localization engine put in [[ip_addr_exmpl]] or 
> [[gateway_exmpl]] where applicable?
> 
> I am almost certain that the amount of strings to be translated cut be 
> cut down a very great deal if this was done - this might encourage some 
> more people to go through the trouble of doint the translation to 
> another language.
> 
> Please understand that I do not myself understand the inner workings of 
> the i18n, so please let me know if there is a specific limitation in 
> i18n that makes this neccessary.
> 

	
11719_2.x-vcard (attatchment)(tag is disabled)