Hi all, Just a few notes on the topic from a translator's perspective:
I do have some experience with “direct” translating without a web tool, for example, in GitHub, in a text editor, or even in an Excel spreadsheet. However, the software I translated in this way always contained tens or hundreds of strings at most, definitely not over twenty thousand. To keep the high quality of translation, it is always necessary to monitor the consistency of the translations of individual strings, because inaccurate or inconsistent translations can often be misleading and thus complicate the work of librarians. Web interfaces usually offer various useful tools, such as tools for cooperation, search options, or suggestions based on previous translations, translations to other languages, translations of other projects, etc. Although the individual tools vary, there are always at least one or two things of this kind available. Without these tools, I find it difficult to see how to maintain the quality and consistency of translations in a project as large as Evergreen. Furthermore, I started “directly” translating that software only after I had already translated Evergreen in the Launchpad interface and had a basic understanding of how translations work and what the translation workflow looks like. To be honest, I can't imagine learning to translate any software without the support of web interface tools. That's why I entirely agree with Galen that direct editing of translations would be a major barrier (especially for new translators). Not to mention that there is always a greater susceptibility to typos and unwanted errors without some kind of interface with special translation tools. Regards, Eva po 3. 11. 2025 v 16:28 odesílatel Galen Charlton via Evergreen-dev < [email protected]> napsal: > Hi, > > My gut feeling is yes, we do need a web interface, with Git-only just > being a fallback. While the translation files on both the Angular and > non-Angular sides are both ultimately human-readable and human editable, > directly editing them would be a barrier and even the simplest of web-based > translation tools offer functionality for keeping track of the state of a > translation. > > Regards, > > Galen > > On Mon, Nov 3, 2025 at 9:43 AM Jason Stephenson <[email protected]> > wrote: > >> Do we need a web interface for translations? I know several projects that >> update translations in the code repository. They have translations >> directories. >> >> We can manage access by allowing translators to commit to those >> directories. >> >> That said, I have no idea how this works with the Angular translations if >> at all. >> >> Also, we may lose some translators because of the extra hurdles of using >> a text editor and git. >> >> So, maybe not the best idea but possibly a last resort. >> >> On Tue, Oct 28, 2025 at 1:51 PM Galen Charlton via Evergreen-dev < >> [email protected]> wrote: >> >>> Hi, >>> >>> In the course of trying to set up a translation series in Launchpad for >>> rel_3_16, I discovered a problem: it no longer appears to be possible. >>> >>> Specifically, Canonical has announced that they are phasing out hosting >>> Bazaar repositories. [1] >>> >>> By itself, that wouldn't be a problem for Evergreen, as we never used >>> Bazaar directly to manage Evergreen's code. However, Launchpad's >>> translation infrastructure currently does rely on receiving strings from a >>> bzr branch (which is synced to Evergreen's Git repo) and pushing >>> translation exports to a different bzr branch (which Evergreen's build >>> process draws from). >>> >>> However, as of June [2], I can't find any indication of when Launchpad >>> will be transitioning its translation import/exports to deal with Git repos >>> directly. And when I tried today, Launchpad would not let me set up bzr >>> branches even as just a temporary measure. >>> >>> I've asked in the Discourse thread whether there's an updated timeframe, >>> but if Launchpad doesn't resolve this soon (and their announcement states >>> that they are planning to drop *all *Bazaar repos in December), this >>> may force our hand regarding moving to a different translation platform. >>> >>> (I think we'll be OK for the 3.16-beta, as the machinery for managing >>> translations in the main series still seems to be working, and that will be >>> good enough for the beta. However, that will of course start diverging away >>> from rel_3_16.) >>> >>> There's POEditor, of course, though I have some reservations about >>> whether they will host Evergreen for free in the long run. Has anybody >>> looked at other options? Weblate struck my eye - it's libre and was adopted >>> by the Koha project last year. >>> >>> [1] https://blog.launchpad.net/general/phasing-out-bazaar-code-hosting >>> [2] >>> https://discourse.ubuntu.com/t/phasing-out-bazaar-code-hosting/62189/11 >>> >>> Regards, >>> >>> Galen >>> -- >>> Galen Charlton >>> Implementation and IT Manager >>> Equinox Open Library Initiative >>> [email protected] >>> https://www.equinoxOLI.org >>> phone: 877-OPEN-ILS (673-6457) >>> direct: 770-709-5581 >>> <http://evergreen-ils.org> >>> _______________________________________________ >>> Evergreen-dev mailing list -- [email protected] >>> To unsubscribe send an email to >>> [email protected] >>> >> >> >> -- >> >> Jason Stephenson (he/him) >> ILS Manager, C/W MARS, Inc. >> >> ------------------------------ >> >> [image: icon] [email protected] | [image: icon]www.cwmars.org >> >> [image: icon] 508-755-3323 x 418 >> > > > -- > Galen Charlton > Implementation and IT Manager > Equinox Open Library Initiative > [email protected] > https://www.equinoxOLI.org > phone: 877-OPEN-ILS (673-6457) > direct: 770-709-5581 > <http://evergreen-ils.org> > _______________________________________________ > Evergreen-dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ Evergreen-dev mailing list -- [email protected] To unsubscribe send an email to [email protected]
