Hi

And if I suggest to rethink completely the way the strings to translate are generated, I suppose you will eject me as troll ? :-)
Or maybe you will ask if I have 1 million $ to put on the table ?

A lot of english words can be nouns or verbs (in imperative form for ex.). In french and other languages, they need to have different translations, but that's not possible
And in PO we have a lot of pseudo-strings like '%s %s' or big xml snippets (from ilsdi), or CSS classes, etc. Sometime it is obvious it is not to translate, sometimes not...
Translating Koha seems quite hard compared to other projects where strings are stored in variables, or where only strings that need to be translated are in the PO.

Regards,
Mathieu

Galen Charlton a écrit :

Hi,

On Wed, Nov 20, 2013 at 4:34 AM, Paul Poulain <paul.poulain@biblibre.com> wrote:

How could we change one of the 2 "terms" to have different words, and
correct translations ?

For the English templates, I would suggest using "academic term" in the course reserves module.

Regards,

Galen
--

Galen Charlton

Manager of Implementation

Equinox Software, Inc. / The Open Source Experts

email: gmc@esilibrary.com

direct: +1 770-709-5581

cell: +1 404-984-4366

skype: gmcharlt

web: http://www.esilibrary.com/

Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

-- 
Mathieu Saby
Service d'Informatique Documentaire
Service Commun de la Documentation
Université Rennes 2
Téléphone : 02 99 14 12 65
Courriel : mathieu.saby@univ-rennes2.fr