Hi Mike, many thanks for the idea. This would certainly be possible solution for the issue. However, to be honest, I am no sure I can really imagine, how this would look like in practice.(especially how much extra work would that means).
I am quite aware it won´t be possible to solve the issue for 3.0 release. However, it is necessary check and unify inconsistent translation in any case,so I will go on with this and I expect I will probably identify some more potentially conflicting terms. I suppose I should be ready with the checking within two weeks at the latest. It might probably be helpful if I put all problematic terms together and make a list of places in the code, where there might be a need to either change the English term, or provide cascading locale helpers. May be the list will show, how many of such terms there will be eventually, and what the most appropriate solution would be. If I should estimate, I would say that conflicting terms may not be more than 10-15 in general. I would like to add, that we really very much appreciate the efforts the community is making to solve the issue of staff client localization. Czech Evergreen libraries really look forward to being also able to take advantage of the new excellent features and opportunities offered by the web client. We have been excited about some progress that has been made recently. However, we are also aware it will be a long run yet, and we will do as much as we can, to help with this process And we still hope we will be able to start training the library staff for the localized web client around the beginning of the next year ;-) Eva . --- Mgr. Eva Cerniňáková cer...@jabok.cz Tel. +420 211 222 409 Knihovna Jabok http:/knihovna.jabok.cz Tel. +420 211 222 410 Jabok - Vyšší odborná škola sociálně pedagogická a teologická Salmovská 8, 120 00 Praha 2 2017-09-26 19:33 GMT+02:00 Mike Rylander <mrylan...@gmail.com>: > Hi Eva, > > One option to solve these conflicts would be to (down the road, not > for 3.0) provide cascading locale helpers that could be up to page > specific with regard to loading PO files, and would fall back to less > specific ones if the helper was not found. This would follow the Dojo > pattern, but be handled entirely in the mod_perl code (so no new 404s > for the user). > > -- > Mike Rylander > | President > | Equinox Open Library Initiative > | phone: 1-877-OPEN-ILS (673-6457) > | email: mi...@equinoxinitiative.org > | web: http://equinoxinitiative.org > > > On Mon, Sep 25, 2017 at 2:19 PM, Cerninakova Eva <cer...@jabok.cz> wrote: > > Hi all > > > > We have done some testing in the effort to move forward the localization > of > > the Web Client (by the way, I´d like to thank Ben Shum for the amazing > work > > he is doing for this). During the tests it became necessary to merge > several > > PO files into one. For testing, we used the Czech localization. > > > > It turned out, after merging the PO files, that in some cases in various > > templates the same term was translated in different ways. Regardless of > > whether the different translation made a sense or it was just a mistake, > if > > the translations differs, the term remains untranslated in the Web Staff > > Client interface. > > > > However, the issue concerns not only the translators. > > > > As I was checking the translation strings trying to unify them, I have > come > > across strings, where the English term is problematic for the > translation. > > Those stings are either English homonyms (which at least in the case of > the > > Czech language must be translated two different ways) or inconsistently > used > > English term. Just for completeness: I am in the middle of the effort > and I > > expect there will be more of such terms in time. > > > > I have opened the bug for this (see > > https://bugs.launchpad.net/evergreen/+bug/1719375) and listed the > > problematic terms I encountered so far. Probably in the cases listed in > the > > bug, English expression will need to be alter. I have made some > > suggestions for the solutions or for new possible terms in the bug. > However, > > they definitely needs to be revised because I'm not a native speaker > (and I > > might have also missed an important context). > > > > I am quite sure the problem of inconsistent translations - including > > problem of translations of English homonyms - will apply not only to > Czech > > translation and localization but also to translations into other > languages > > (and it will be probably needed to consider, what to do in such cases.) > > > > Eva > > > > > > > > > > > > > > > > --- > > Mgr. Eva Cerniňáková > > cer...@jabok.cz > > Tel. +420 211 222 409 > > > > Knihovna Jabok > > http:/knihovna.jabok.cz > > Tel. +420 211 222 410 > > Jabok - Vyšší odborná škola sociálně pedagogická a teologická > > Salmovská 8, 120 00 Praha 2 > > >