Thank you Adrian. Now this is clear.
> This question should be asked on the users list.
>
> The properties file used for translating an entity's values is specified in
> the entity definition, not in the screen.
>
> -Adrian
>
>
> On 10/18/2012 4:39 PM, Martin Kaiser wrote:
>>
>> Hi all,
>>
>> I have a problem with i18n: I have extended the "AgreementType" Entity
>> by simply adding some new Agreement Types:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <entity-engine-xml>
>> <AgreementType agreementTypeId="ABC_AGREEMENT"
>> description="Agreement" hasTable="N" parentTypeId=""/>
>> <AgreementType agreementTypeId="AGRMNT_PRTNR" description="Partner
>> Agreement" hasTable="N" parentTypeId="ABC_AGREEMENT"/>
>> <AgreementType agreementTypeId="AGRMNT_SPPRTR"
>> description="Supporter
>> Agreement" hasTable="N" parentTypeId="ABC_AGREEMENT"/>
>> <AgreementType agreementTypeId="AGRMNT_SPNSR" description="Sponsor
>> Agreement" hasTable="N" parentTypeId="ABC_AGREEMENT"/>
>> <AgreementType agreementTypeId="AGRMNT_THR" description="Other
>> Agreement" hasTable="N" parentTypeId="ABC_AGREEMENT"/>
>> </entity-engine-xml>
>>
>> Now I want the descriptions to be translated by using the following
>> code in freemarker:
>>
>> <#list agreementTypes as agreementType>
>> <option
>> value="${agreementType.agreementTypeId}">${agreementType.get("description",locale)}</option>
>> </#list>
>>
>> If I now provide properties in "PartyEntityLabels.xml", the correct
>> translations are shown after rendering the page. However, if I put the
>> same properties in a separate map file "AgreementLabels.xml" in my
>> hotdeploy folder, and add this resource to to the map in the action
>> section, there is no longer any translation of the new values, but
>> only the previously contained agreement types are translated.
>>
>> How can I translate my own values without mixing my translations of my
>> own agreement types with those of ofbiz?
>>
>> Thank you.
>>
>> Best regards,
>> Martin
>
>
Locked
