of the different components
> >> - If I am not sure where a translation is supposed to reside in, I would
> >> have to hunt it down in many files instead of one
> >> - It also increases the probability of duplication which already exists
> in
> >> these monolithic
cation which already exists in
>> these monolithic UI files without breaking them down. I think this would
>> only get worse with smaller and smaller files and reusing labels becomes
>> less efficient.
>>
>> My 2 cents
>>
>> Taher Alkhateeb
>>
>> -
cient.
>
> My 2 cents
>
> Taher Alkhateeb
>
> - Original Message -
>
> From: "Adrian Crum"
> To: dev@ofbiz.apache.org
> Sent: Friday, 3 October, 2014 2:44:52 PM
> Subject: Re: Growing size of UI*Label.xml files
>
> The label files can be spli
get worse with smaller and smaller files and reusing labels becomes less
efficient.
My 2 cents
Taher Alkhateeb
- Original Message -
From: "Adrian Crum"
To: dev@ofbiz.apache.org
Sent: Friday, 3 October, 2014 2:44:52 PM
Subject: Re: Growing size of UI*Label.xml files
Looking at the tool(s) behind http://translate.apache.org, being pootle and
the translation toolkit I see that it supports both. Though the xml file is
in the XLIFF format, which is different to ours.
For more info see:
https://en.wikipedia.org/wiki/Pootle
https://en.wikipedia.org/wiki/Translate_T
The label files can be split out to separate languages, but the new
files will need to be in the original Java *.properties or *.xml formats.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 10/3/2014 12:21 PM, Pierre Smits wrote:
Maybe it is just me, but it seems that the UI*Label
Maybe it is just me, but it seems that the UI*Labels.xml files in the
configuration are becoming more cumbersome to manage and that it takes more
and more time to process in OFBiz with each commit iteration.
Currently all translations in each individual component is handled through
distinct files
