I understand your concerns and I admit that all solutions I came across so far have their downsides. But are you actually suggesting that we should prefer a system that is complicated and impractical in order to keep "unwanted" translators away? That sounds just wrong to me.
At this point I should probably elaborate on my initial request: My intention was not to use any of those platforms for the sake of their existing "community" (I know myself that most translators you reach this way don't have a strong commitment towards a specific project), but to improve the localization process for those translators that are already actively translating Inkscape anyway (in the end we don't have to open translations for everyone regardless of the system/process that is used). That said I also do not insist on using a specific localization platform (the ones mentioned above were merely popular examples). In the end I'd already be happy with a code repository that contains all the latest translation files and where established translators can easily gain write access. This way we can at least submit our work as we go and always translate the latest version of a file, without the risk of producing multiple branches of the same file that need to be merged afterwards in a cumbersome process. Would something like this find your approval or do you have even better ideas on how to handle translations at least a little bit better than we currently do? Best Regards, Eduard Am 19.09.2015 um 03:53 schrieb Victor Westmann: > Unfortunately Alex is right. :( > > I took care of translating another open source project and I did an > effort to raise translations from 40% to 100%. I was super excited. > Until I contacted revisors team. No one answered me. From a team of > more than 10 reviewers and 100 translators. :( > > > > --Victor Westmann > > 2015-09-18 18:15 GMT-03:00 Alexandre Prokoudine > <[email protected] <mailto:[email protected]>>: > > On Fri, Sep 18, 2015 at 11:38 PM, Maren wrote: > > >>> I'm wondering for some time now why Inkscape does not use some > sort of > >> web-based translation platform (like Transifex or Crowdin, > maybe even > >> Launchpad's integrated localization capabilities)? > >> > >> Because they all suck. > > > > I think Martin is trying to establish a more integrated > solution, that is > > meant to be available for translating all Inkscape's resources. > > It will still take some work, so it's probably not yet time to > announce > > publicly... > > The question is whether there will be a way to track and review > changes made by completely arbitrary people who try to be helpful or > just feeling like messing with translation out of boredom, but have no > clue whatsoever about what they are doing. Another question is how > much time this review would consume. > > Alex > > > ------------------------------------------------------------------------------ > _______________________________________________ > Inkscape-translator mailing list > [email protected] > <mailto:[email protected]> > https://lists.sourceforge.net/lists/listinfo/inkscape-translator > > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Inkscape-translator mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/inkscape-translator ------------------------------------------------------------------------------ _______________________________________________ Inkscape-translator mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/inkscape-translator
