Olà, Le dim. 29 nov. 2020 à 23:46, andy pugh <[email protected]> a écrit :
> On Sun, 29 Nov 2020 at 21:50, J.M. Garcia <[email protected]> wrote: > > > Second, what is the benefit of this approach from the point of view of > pure > > translation work? I can't see any. > > I don't know enough about it, but I can see that a purpose-made > translation platform might make it easier to keep track of new changes > requiring translation, and to compare source language and translation > to determine the status of the translation of a particular document. This is exactly one of the main benefits of such tools, with complete integration with VCS (sources, translation files, pull/push/commits), change tracking at the string level, string reordering support, multiple source format support, translation helpers (translation QA tools, translation memory, machine translation), glossary management, rich desktop and web UI, integrated team translation and communication features. With all this packed in, I see this as an opportunity to give the project an infrastructure to build a translation team upon while creating a continuous translation pipeline and increasing project's code quality/structure by improving translation integration. About the external tool, like I said, I'd better be self hosted too. That's why I've spent many hours this WE looking at Crowdin alternatives and specifically Weblate. But again, these are just tools and all the data remain stored and managed in project's repository. Hope to send a message about the outcomes of the WE today or tomorrow... How did you work out what documents had been translated, and which > needed translation or updating when you did your (extensive) > translation work? Indeed, please share your experience and workflow! This is all knew to me and would greatly benefit from them 🙏 Have a good day folks _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
