Internationalizing seed data

[Victor Hernandez-2]

Hi everybody,

I have a little concern about OFBiz internationalization because my native
language is not English, and I saw there are a good advance about that but I
still continue seeing many UI's which still are in English due that entity
data is not translated, that is entirely comprehensible but I believe that
having the user perspective in mind may be we have to consider the
translation at least of seed data.

For that I believe that a similar approach such as the used for the
*.properties files in the OFBiz code can be useful just appending the
language suffix to each XML instance documents containing seed data, for
instance the file "/applications/accounting/ofbiz-component.xml" contains a
line like this:

<entity-resource type="data" reader-name="seed" loader="main"
location="data/AccountingTypeData.xml" />

And the "/applications/accounting/data/AccountingTypeData.xml" file contains
ENGLISH data to be imported at system setup time, but we can to use a
localized version instead if exist like
"/applications/accounting/data/AccountingTypeData_es.xml".

What you think about? What substantial code changes implies?

Cheers

- Victor Hugo Hernández Posadas

[Si Chen-2]

Victor,

Seed data can be internationalized: see the section on  
"Internationalizing data types" here:
http://www.opensourcestrategies.com/ofbiz/internationalizing_ofbiz.php

There's a link to an example as well.

On Nov 16, 2006, at 11:15 AM, Victor Hernandez wrote:

> Hi everybody,
>
> I have a little concern about OFBiz internationalization because my  
> native
> language is not English, and I saw there are a good advance about  
> that but I
> still continue seeing many UI's which still are in English due that  
> entity
> data is not translated, that is entirely comprehensible but I  
> believe that
> having the user perspective in mind may be we have to consider the
> translation at least of seed data.
>
> For that I believe that a similar approach such as the used for the
> *.properties files in the OFBiz code can be useful just appending the
> language suffix to each XML instance documents containing seed  
> data, for
> instance the file "/applications/accounting/ofbiz-component.xml"  
> contains a
> line like this:
>
> <entity-resource type="data" reader-name="seed" loader="main"
> location="data/AccountingTypeData.xml" />
>
> And the "/applications/accounting/data/AccountingTypeData.xml" file  
> contains
> ENGLISH data to be imported at system setup time, but we can to use a
> localized version instead if exist like
> "/applications/accounting/data/AccountingTypeData_es.xml".
>
> What you think about? What substantial code changes implies?
>
> Cheers
>
> - Victor Hugo Hernández Posadas

Best Regards,

Si
[hidden email]

[Danny Gaethofs-2]

Can it be user (login) dependent ?

> -----Original Message-----
> From: [hidden email]
> Sent: Fri, 17 Nov 2006 12:45:42 -0800
> To: [hidden email]
> Subject: Re: Internationalizing seed data
>
> Victor,
>
> Seed data can be internationalized: see the section on
> "Internationalizing data types" here:
> http://www.opensourcestrategies.com/ofbiz/internationalizing_ofbiz.php
>
> There's a link to an example as well.
>
> On Nov 16, 2006, at 11:15 AM, Victor Hernandez wrote:
>
>> Hi everybody,
>>
>> I have a little concern about OFBiz internationalization because my
>> native
>> language is not English, and I saw there are a good advance about
>> that but I
>> still continue seeing many UI's which still are in English due that
>> entity
>> data is not translated, that is entirely comprehensible but I
>> believe that
>> having the user perspective in mind may be we have to consider the
>> translation at least of seed data.
>>
>> For that I believe that a similar approach such as the used for the
>> *.properties files in the OFBiz code can be useful just appending the
>> language suffix to each XML instance documents containing seed
>> data, for
>> instance the file "/applications/accounting/ofbiz-component.xml"
>> contains a
>> line like this:
>>
>> <entity-resource type="data" reader-name="seed" loader="main"
>> location="data/AccountingTypeData.xml" />
>>
>> And the "/applications/accounting/data/AccountingTypeData.xml" file
>> contains
>> ENGLISH data to be imported at system setup time, but we can to use a
>> localized version instead if exist like
>> "/applications/accounting/data/AccountingTypeData_es.xml".
>>
>> What you think about? What substantial code changes implies?
>>
>> Cheers
>>
>> - Victor Hugo Hernández Posadas
>
> Best Regards,
>
> Si
> [hidden email]

____________________________________________________________
FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family!
Visit http://www.inbox.com/photosharing to find out more!

[Victor Hernandez-2]

Great!! I didn't saw :-), Thanks Si Chen, I continue enrolling myself

From: Si Chen <[hidden email]>
To: [hidden email]
Date: Fri, 17 Nov 2006 12:45:42 -0800
Subject: Re: Internationalizing seed data
Victor,

Seed data can be internationalized: see the section on
"Internationalizing data types" here:
http://www.opensourcestrategies.com/ofbiz/internationalizing_ofbiz.php

There's a link to an example as well.

On Nov 16, 2006, at 11:15 AM, Victor Hernandez wrote:

> Hi everybody,
>
> I have a little concern about OFBiz internationalization because my
> native
> language is not English, and I saw there are a good advance about
> that but I
> still continue seeing many UI's which still are in English due that
> entity
> data is not translated, that is entirely comprehensible but I
> believe that
> having the user perspective in mind may be we have to consider the
> translation at least of seed data.
>
> For that I believe that a similar approach such as the used for the
> *.properties files in the OFBiz code can be useful just appending the
> language suffix to each XML instance documents containing seed
> data, for
> instance the file "/applications/accounting/ofbiz-component.xml"
> contains a
> line like this:
>
> <entity-resource type="data" reader-name="seed" loader="main"
> location="data/AccountingTypeData.xml" />
>
> And the "/applications/accounting/data/AccountingTypeData.xml" file
> contains
> ENGLISH data to be imported at system setup time, but we can to use a
> localized version instead if exist like
> "/applications/accounting/data/AccountingTypeData_es.xml".
>
> What you think about? What substantial code changes implies?
>
> Cheers
>
> - Victor Hugo Hernández Posadas

Best Regards,

Si
[hidden email]