<div dir="ltr"><div>Hi Galen,<div><br></div><div>I don't think I can add more to the Evergreen translation tool considerations at this point:</div><div><br></div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div>Although I have quite positive experiences with Transifex, which I used for Zotero translation, Transifex is a proprietary tool and therefore, in my opinion, not very suitable for the Evergreen project. </div></div><div><div><br></div></div><div><div>The second tool I had in mind was Poedit. But that's only a translation editor.</div></div><div><div><br></div></div><div><div>While working on my dissertation, I dealt with the Koha Translation Project, which uses Pootle. In terms of translations, Pootle seems usable to me. However, I am not fully capable of evaluating him, because I did not actively use this tool for translations.</div></div></blockquote><div><br></div><div>Regards</div><div>Eva</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">pá 5. 5. 2023 v 16:31 odesílatel Galen Charlton <<a href="mailto:gmc@equinoxoli.org">gmc@equinoxoli.org</a>> napsal:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi Eva,</div><div><br></div><div>Thank you for your feedback - as one of the people who is actively doing translation work at the moment, it is very important.</div><div><br></div><div>You mentioned that you have experience with four tools. Would any of the other ones you use be worth considering for Evergreen, in your opinion?<br></div><div><br></div><div>Regards,</div><div><br></div><div>Galen<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 4, 2023 at 11:31 AM Cerninakova Eva <<a href="mailto:cernin@jabok.cz" target="_blank">cernin@jabok.cz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">
<div>Hi, <br></div><div><br></div><div>I can hardly contribute to the
discussion regarding developer questions
that<span lang="en"><span><span> Galen outlined in his previous email</span></span></span>. Just a few very practical notes on the topic
of translation tools from a translator's point of view (maybe they can
be a little helpful in future decision-making).</div><div><br></div>
I personally take quite a pragmatic approach to the translation tool: I
have experience with translations using four different tools (as well
as direct string translations in a text editor). In each of them, there
is something that does not suit me at all and something I really like. And <span>it's clear (at least from a translator point of view), that choosing a translation tool will always be a compromise</span>.
<br><ul><li>If I compare Launchpad and POEditor, I must say, <span>POEditor's interface is much nicer and “airier”, and it also works better on mobile devices.</span>
</li><li>In Launchpad, I miss the ability to search all strings at once,
which is a very useful and important option that helps to keep the
consistency of translations. In POEditor, such ability is available.</li><li>In
Launchpad, it is also NOT possible to skip strings that are not new
when browsing untranslated strings (I sometimes leave some strings
untranslated until I get to know them in more detail in the
documentation and/or I find out how Evergreen uses those strings in
practice). In POEditor, it is possible to mark batches of strings by
tag. Tagging related to<span> Evergreen version is extremely helpful for translators </span><span>as it allows them to select only a specific
batch of strings, e.g, only strings for the newest Evergreen version (thank you
very much for tagging strings 🙂).</span></li><li>In
POEditor, I lack the option to copy the English string into the
translation
field. The ability to copy the original string to the
translation field by just clicking the button is widely used in Launchpad.
This is especially important in cases where the string includes
variables, syntax, etc. Of course, it is possible to manually copy the
English string in the POEditor, but this may result in parts of the
text, spaces or lines that dont´t belong to the translation, or, conversely,
tha are missing in the translated string. This creates errors in the
translations, which must then be searched for and corrected.</li><li>In
POEditor, I also really miss the translation suggestions based on
previous translations (memory based suggestions) that are available in
Launchpad. The translator may not always realize that a similar string
was translated e.g. two years ago and can translate it differently. This
then contributes to the inconsistency of translations in the Evergreen interface, and thus to a possible confusion for users.</li></ul><div></div><div>So from my point of view, to sum it up:</div><div></div><div><br></div><div>
POEditor: <br></div><ul><li>Missing “Translation memory suggestions” </li><li>Missing function for copying the original string to the translation field</li></ul><div></div><div>Launchpad: <br></div><ul><li>Missing <span>option to search all strings at once</span></li><li>
<span>Missing option to mark a batch of strings specific to a particular version of Evergreen</span></li></ul><div><span></span></div><div><br></div><div>I hope that my comments will be at least somewhat helpful. <br></div><div><br></div><div><br></div><div><span>Eva<br></span></div><div><span><br></span></div><div><br></div>
</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">čt 4. 5. 2023 v 16:59 odesílatel Galen Charlton via Evergreen-dev <<a href="mailto:evergreen-dev@list.evergreen-ils.org" target="_blank">evergreen-dev@list.evergreen-ils.org</a>> napsal:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div>Hi,</div><div><br></div><div>Some further updates:</div><div><br></div><div>- I've sorted out the issue with importing strings from Evegreen's master/main branch. As of now, there are more strings available to translation, particularly for bootstrap-opac</div>- The naming of the action translation export branches is now more systematic:</div><div dir="ltr"><br></div><div dir="ltr">bzr branch lp:~evergreen-bugs/evergreen/translation-export-main</div><div dir="ltr">bzr branch lp:~evergreen-bugs/evergreen/translation-export-3.10</div><div dir="ltr">bzr branch lp:~evergreen-bugs/evergreen/translation-export-3.9</div><div dir="ltr"><br></div><div>- I've updated the current release instructions on the wiki <<a href="https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:evergreen:2.8" target="_blank">https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:evergreen:2.8</a>> to refer to the current translation branches<br></div><div><br></div><div>One thing to note: if you're intending to work with
translation-export-main today, you'll need to wait for Launchpad's daily automated translation export.<br></div><div><br></div><div>Regards,</div><div><br></div><div>Galen<br></div><div><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 4, 2023 at 9:48 AM Galen Charlton <<a href="mailto:gmc@equinoxoli.org" target="_blank">gmc@equinoxoli.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>Following up on discussions regarding internalization and localization (I18N/L10N0 at the Evergreen Conference, here are some updates:</div><div><br></div><div>- Blake Graham-Henderson has volunteered to assume responsibility for technical maintenance of the I18N infrastructure, including LP translations and POEditor.</div><div>- I have caught up with setting up translation series in Launchpad for every Evergreen release stream. The translation series for 3.11 can be set up once rel_3_11 is branched off as part of preparing the 3.11 beta release.</div><div>- This morning I discovered that imports from Git for Launchpad's master/main translation series have been failing since April 2022. I am recreating the setup required to import new strings for that translation series; the upshot is that later today or tomorrow there will be a slew of new strings showing up to translate.</div><div>- Some procedural changes discussed during the conference include:</div><div><br></div><div>* Automating string export to Launchpad, either periodically or upon a push to Git</div><div>* Similarly, automating string export to POEditr</div><div><br></div><div>- There was also some discussion about the tools used for translation, along the lines of:</div><div><br></div><div>* Can we consolidate down to one tool for all strings, rather than using both Launchpad and POEditor?</div><div>* Is there a preferred tool? Launchpad isn't set up to handle the translation formats used by the Evergreen Angular client, but POEditor could handle both the Angular strings and the non-Angular ones.</div><div>* Is there another tool that would be even better for people doing the translations?</div><div>* Noting that if we decide to move to GitHub or the like, that GitHub does _not_ provide a built-in translation tool the way that Launchpad does.</div><div><br></div><div>Feedback very much invited.<br></div><div><br></div>Regards,<div><br></div><div>Galen<br><span>-- </span><br><div dir="ltr"><div dir="ltr">Galen Charlton<br>Implementation and IT Manager<br>Equinox Open Library Initiative<br><a href="mailto:gmc@equinoxOLI.org" target="_blank">gmc@equinoxOLI.org</a><br><a href="https://www.equinoxOLI.org" target="_blank">https://www.equinoxOLI.org</a> <br>phone: 877-OPEN-ILS (673-6457)<br>direct: 770-709-5581<br><a href="http://evergreen-ils.org" target="_blank"></a></div></div></div></div>
</blockquote></div><br clear="all"><br><span>-- </span><br><div dir="ltr"><div dir="ltr">Galen Charlton<br>Implementation and IT Manager<br>Equinox Open Library Initiative<br><a href="mailto:gmc@equinoxOLI.org" target="_blank">gmc@equinoxOLI.org</a><br><a href="https://www.equinoxOLI.org" target="_blank">https://www.equinoxOLI.org</a> <br>phone: 877-OPEN-ILS (673-6457)<br>direct: 770-709-5581<br><a href="http://evergreen-ils.org" target="_blank"></a></div></div></div>
_______________________________________________<br>
Evergreen-dev mailing list<br>
<a href="mailto:Evergreen-dev@list.evergreen-ils.org" target="_blank">Evergreen-dev@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev</a><br>
</blockquote></div>
</blockquote></div><br clear="all"><br><span>-- </span><br><div dir="ltr"><div dir="ltr">Galen Charlton<br>Implementation and IT Manager<br>Equinox Open Library Initiative<br><a href="mailto:gmc@equinoxOLI.org" target="_blank">gmc@equinoxOLI.org</a><br><a href="https://www.equinoxOLI.org" target="_blank">https://www.equinoxOLI.org</a> <br>phone: 877-OPEN-ILS (673-6457)<br>direct: 770-709-5581<br><a href="http://evergreen-ils.org" target="_blank"></a></div></div>
</blockquote></div>