[Evergreen-dev] [Evergreen-general] Untranslated column headers in the staff client - how to proceed?

[Linda Jansová]

Hi,

Just a quick update - using Blake's bugsquash2 test server, I have found 
out that the column headers which were shown as untranslated in the fall 
are still untranslated now (I have added this update as a comment to the 
bug: https://bugs.launchpad.net/evergreen/+bug/2042915).

Linda

On 2/22/24 20:18, Linda Jansová wrote:
> Dear Galen,
>
> Thank you very much!
>
> We haven't attempted changing the $locale variable in <!--#include 
> virtual="/opac/locale/${locale}/fm_IDL.dtd"--> as - if I understand it 
> correctly - it would not be useful anyway because we would also need 
> English (at least in its role of a fallback language).
>
> The IDL2js in our 3.12 test installation seems to contain the Czech 
> words (although one has to ask the web browser to automatically fix 
> the encoding but I suppose this has nothing to do with how the file is 
> actually used within Evergreen)...
>
> Linda
>
> On 2/22/24 15:46, Galen Charlton wrote:
>> Hi,
>>
>> All of this said, upon more examination, it does look like that there 
>> may also be a bug or two with how the Angular app build is attempting 
>> to specify that the IDL should be fetched in a non-default locale. 
>> I'll continue to look at this.
>>
>> One way to check to see if your Evergreen server has the translated 
>> IDL set up correctly is to try this URL:
>>
>> https://EVERGREEN/IDL2js?au&locale=cs-CZ 
>> <https://EVERGREEN/IDL2js?au&locale=cs-CZ>
>>
>> If you see Czech labels, that means that the installation of the 
>> entityized fm_IDL.xml and the relevant DTD files is working.
>>
>> Regards,
>>
>> Galen
>>
>> On Thu, Feb 22, 2024 at 9:06 AM Galen Charlton <gmc at equinoxoli.org> 
>> wrote:
>>
>>     Hi,
>>
>>     On Thu, Feb 22, 2024 at 1:24 AM Linda Jansová via Evergreen-dev
>>     <evergreen-dev at list.evergreen-ils.org> wrote:
>>     > In our installations we use both English and Czech, so I
>>     suppose the replacement for
>>     > the single-language site wouldn't be the right option for us as
>>     these would
>>     > actually count as two languages rather than one (?).
>>
>>     Yes, in your case you'd want to use the entity version of
>>     fm_IDL.xml as is and bring over the en-US DTD in addition to the
>>     cs-CZ one. (And actually, the en-US DTD should be put in place
>>     anyway as a fallback for cases where the browser isn't detecting
>>     or passing along the desired locale for whatever reason).
>>
>>     Please don't hesitate to ask if you run into any problems getting
>>     this set up on your installation.
>>
>>     Regards,
>>
>>     Galen
>>     --
>>     Galen Charlton
>>     Implementation and IT Manager
>>     Equinox Open Library Initiative
>>     gmc at equinoxOLI.org
>>     https://www.equinoxOLI.org <https://www.equinoxOLI.org>
>>     phone: 877-OPEN-ILS (673-6457)
>>     direct: 770-709-5581
>>
>>
>>
>> -- 
>> Galen Charlton
>> Implementation and IT Manager
>> Equinox Open Library Initiative
>> gmc at equinoxOLI.org
>> https://www.equinoxOLI.org <https://www.equinoxOLI.org>
>> phone: 877-OPEN-ILS (673-6457)
>> direct: 770-709-5581
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-dev/attachments/20240321/8e681cc8/attachment.htm>