[Koha-translate] EN files that have french words

[LAURENT Henri-Damien]

Le 10/11/2010 16:03, Frédéric DEMIANS a écrit :
> 
>> I have check files to translate the 3.2
>> In same 'en' files there are French words.
>> So to translate all the files, I need two languages,
>> English and French
>>
>> The 'en' files with French words are:
>>
>> ../koha-tmpl/opac-tmpl/prog/en/xslt/UNIMARCslim2OPACDetail.xsl
>> ../koha-tmpl/opac-tmpl/prog/en/xslt/UNIMARCSlimUtils.xsl
>> ../koha-tmpl/opac-tmpl/prog/en/xslt/UNIMARCslim2OPACResults.xsl
>>
>> ../koha-tmpl/intranet-tmpl/prog/en/xslt/UNIMARCSlim2OAIDC.xsl
>> ../koha-tmpl/intranet-tmpl/prog/en/xslt/UNIMARCSlim2intranetDetail.xsl
>> ../koha-tmpl/intranet-tmpl/prog/en/xslt/UNIMARCSlimUtils.xsl
>>
>> The bug in bugzilla is:
>> http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5204
>>
>> Do I send a patch to use English instead of French ?
>> Attention that all translations already done need to change.
> 
> The issue comes from the fact that UNIMARC is massively used by French
> libraries. So UNIMARC XSL are in French from the beginning (with few
> words in English).
> 
> There are two options:
> 
>    1. UNIMARC XSL are translated in authoritative templates (en) from
>       French to English. And then, the standard translation process
>       applies. You will have, as you said, to re-translate text
>       extracted from en UNIMARC XSL and it won't be available before
>       next 3.2.x release.
>    2. UNIMARC XSL stays in French. And you translate from French to
>       Italian just those text coming from XSL UNIMARC files.
> 
> I incline to prefer option 2 :-) I'm not sure so many libraries outside
> France will use UNIMARC in English or any other language.
> 
> If 1 is preferred, I can translate French UNIMARC XSL into English and
> submit a patch.

Why not taking option 1 (which would be far cleaner), provided that time
is invested in order to make C4::XSLT to take the correct language path
for XSLT (which at the moment is not the case for many reasons which
would be too long to detail). Having also the ability to have one XSLT
for results at intranet and another one for opac could also be
interesting. But maybe this is not a problem for the community version.

-- 
Henri-Damien LAURENT