[Evergreen-dev] Updates on translations
Cerninakova Eva
cernin at jabok.cz
Mon May 8 02:31:00 EDT 2023
Hi Galen,
I don't think I can add more to the Evergreen translation tool
considerations at this point:
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.
The second tool I had in mind was Poedit. But that's only a
translation editor.
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.
Regards
Eva
pá 5. 5. 2023 v 16:31 odesílatel Galen Charlton <gmc at equinoxoli.org> napsal:
> Hi Eva,
>
> Thank you for your feedback - as one of the people who is actively doing
> translation work at the moment, it is very important.
>
> 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?
>
> Regards,
>
> Galen
>
> On Thu, May 4, 2023 at 11:31 AM Cerninakova Eva <cernin at jabok.cz> wrote:
>
>> Hi,
>>
>> I can hardly contribute to the discussion regarding developer questions
>> that Galen outlined in his previous email. 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).
>>
>> 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 it's
>> clear (at least from a translator point of view), that choosing a
>> translation tool will always be a compromise.
>>
>> - If I compare Launchpad and POEditor, I must say, POEditor's
>> interface is much nicer and “airier”, and it also works better on mobile
>> devices.
>> - 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.
>> - 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 Evergreen version is extremely helpful for translators 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
>> 🙂).
>> - 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.
>> - 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.
>>
>> So from my point of view, to sum it up:
>>
>> POEditor:
>>
>> - Missing “Translation memory suggestions”
>> - Missing function for copying the original string to the translation
>> field
>>
>> Launchpad:
>>
>> - Missing option to search all strings at once
>> - Missing option to mark a batch of strings specific to a particular
>> version of Evergreen
>>
>>
>> I hope that my comments will be at least somewhat helpful.
>>
>>
>> Eva
>>
>>
>>
>> čt 4. 5. 2023 v 16:59 odesílatel Galen Charlton via Evergreen-dev <
>> evergreen-dev at list.evergreen-ils.org> napsal:
>>
>>> Hi,
>>>
>>> Some further updates:
>>>
>>> - 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
>>> - The naming of the action translation export branches is now more
>>> systematic:
>>>
>>> bzr branch lp:~evergreen-bugs/evergreen/translation-export-main
>>> bzr branch lp:~evergreen-bugs/evergreen/translation-export-3.10
>>> bzr branch lp:~evergreen-bugs/evergreen/translation-export-3.9
>>>
>>> - I've updated the current release instructions on the wiki <
>>> https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:evergreen:2.8>
>>> to refer to the current translation branches
>>>
>>> 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.
>>>
>>> Regards,
>>>
>>> Galen
>>>
>>> On Thu, May 4, 2023 at 9:48 AM Galen Charlton <gmc at equinoxoli.org>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Following up on discussions regarding internalization and localization
>>>> (I18N/L10N0 at the Evergreen Conference, here are some updates:
>>>>
>>>> - Blake Graham-Henderson has volunteered to assume responsibility for
>>>> technical maintenance of the I18N infrastructure, including LP translations
>>>> and POEditor.
>>>> - 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.
>>>> - 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.
>>>> - Some procedural changes discussed during the conference include:
>>>>
>>>> * Automating string export to Launchpad, either periodically or upon a
>>>> push to Git
>>>> * Similarly, automating string export to POEditr
>>>>
>>>> - There was also some discussion about the tools used for translation,
>>>> along the lines of:
>>>>
>>>> * Can we consolidate down to one tool for all strings, rather than
>>>> using both Launchpad and POEditor?
>>>> * 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.
>>>> * Is there another tool that would be even better for people doing the
>>>> translations?
>>>> * 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.
>>>>
>>>> Feedback very much invited.
>>>>
>>>> Regards,
>>>>
>>>> Galen
>>>> --
>>>> Galen Charlton
>>>> Implementation and IT Manager
>>>> Equinox Open Library Initiative
>>>> gmc at equinoxOLI.org
>>>> https://www.equinoxOLI.org
>>>> phone: 877-OPEN-ILS (673-6457)
>>>> direct: 770-709-5581
>>>> <http://evergreen-ils.org>
>>>>
>>>
>>>
>>> --
>>> Galen Charlton
>>> Implementation and IT Manager
>>> Equinox Open Library Initiative
>>> gmc at equinoxOLI.org
>>> https://www.equinoxOLI.org
>>> phone: 877-OPEN-ILS (673-6457)
>>> direct: 770-709-5581
>>> <http://evergreen-ils.org>
>>> _______________________________________________
>>> Evergreen-dev mailing list
>>> Evergreen-dev at list.evergreen-ils.org
>>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-dev
>>>
>>
>
> --
> Galen Charlton
> Implementation and IT Manager
> Equinox Open Library Initiative
> gmc at equinoxOLI.org
> https://www.equinoxOLI.org
> phone: 877-OPEN-ILS (673-6457)
> direct: 770-709-5581
> <http://evergreen-ils.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-dev/attachments/20230508/cb422aa7/attachment.htm>
More information about the Evergreen-dev
mailing list