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

[Stephanie Leary]

Hi, all. I want to revisit the issue of missing translations that Linda
brought up on Jan. 2. If I understand correctly, the main problem is that
we have strings in the IDL that are not being imported into POEditor.

This is the procedure the 3.12 release team used:
https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:evergreen:how_to_build

As you can see, there are several steps related to translations.

The POEditor instructions are here:
https://wiki.evergreen-ils.org/doku.php?id=poeditor

Are we missing some steps?


Stephanie Leary
Front End Developer
Equinox Open Library Initiative
stephanie.leary at equinoxOLI.org
https://www.equinoxOLI.org
phone: 877-OPEN-ILS (673-6457)


On Tue, Jan 2, 2024 at 12:23 AM Linda Jansová via Evergreen-general <
evergreen-general at list.evergreen-ils.org> wrote:

> Dear all,
>
> We have begun working with the 3.12 version which is - when it comes to
> correctly displaying Czech - significantly better than the previous
> version - of course a big thank you goes out to everyone who has helped
> along the way :-)!
>
> One of the so far unresolved issues we would like to start working on
> now are the column headers. These often remain untranslated as we have
> reported here:
>
> https://bugs.launchpad.net/evergreen/+bug/2042915
>
> There is also a spreadsheet with a couple of examples:
>
>
> https://docs.google.com/spreadsheets/d/13_AwTRNLobGIgA6bFqw0pC3tWXq8D8i13CshCbOb1u4/edit?usp=sharing
>
> It seems that if the string (and, consequently, its translation) is not
> present in POEditor and can only be found on Launchpad and in fm_IDL.xml
> and in translation files in GIT, the staff client interface shows the
> English string instead of the Czech one.
>
> So I was just wondering how we could proceed, e.g. should we try to
> compile a comprehensive list of all missing translations from the column
> headers? And if so, which other pieces of information would be useful to
> add, e.g., would a spreadsheet like the one mentioned above be a good
> starting point?
>
> In some cases when the string is not very unique (actually, it is a
> rather common situation to come across widely used strings; the unique
> ones appear less frequently), the GIT links might not be very useful as
> the string would be found in many more places (and, consequently, files)
> than just say in a single column header.
>
> Perhaps trying to locate relevant ".component.html" files with missing
> i18n-label attributes (using
>
> https://git.evergreen-ils.org/?p=Evergreen.git&a=search&h=HEAD&st=grep&s=+%3Ceg-grid-column
> or a similar approach) would be a better choice? (But maybe this
> wouldn't work in practice as the example strings from the spreadsheet
> currently indicate no occurrences in the .component.html files.)
>
> Or would there be an entirely different way to tackle it?
>
> Thank you very much for sharing your views!
>
> Linda
>
> _______________________________________________
> Evergreen-general mailing list
> Evergreen-general at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-dev/attachments/20240221/cf023ad2/attachment.htm>