> On 26 Apr 2018, at 10:21, Thomas Mortagne <[email protected]> wrote: > > From what I remember https://crowdin.com/ quota for OpenSource plan > was too low for XWiki.
I also prefer weblate which is more open source than crowdin (which I don’t know if you can install locally and it’s a business and they could change their “opensource” plans at any time so we'd need a way to install it locally). Thanks -Vincent > > On Wed, Apr 25, 2018 at 10:15 PM, Sergiu Dumitriu <[email protected]> wrote: >> On 04/24/2018 09:44 AM, Clément Aubin wrote: >>> On 04/23/2018 12:18 PM, Adel Atallah wrote: >>>> Hello everyone, >>> >>> Hi, >>> >>> AFAICS Weblate looks nice, but haven't we looked at other alternatives ? >>> >>> Here are some of them : >>> >>> * http://jabylon.org/ (uses Java, so it might be easier to integrate) >>> * http://zanata.org/ >>> * http://pootle.translatehouse.org/ >>> * https://pontoon.mozilla.org/ >> >> I've been quite happy with https://crowdin.com/ , which handles >> ApplicationResources.properties very well, but isn't ideal for the .xml >> translations. It's free for open source projects. >> >> The problem with the .xml files is that apart from the translatable >> content, which it handles well, it tries to commit the exact same XML >> markup as in the "source" file, which doesn't really work for XWiki. As >> a workaround, I just cat|sed the contents of the XML files and upload it >> as a non-github-tracked resource. The alternative is to >> rebase-interactive each pull request it creates to discard the commits >> that try to re-format the XML files, but that gets tedious after a while. >> >>> Also, I think that it has already been discussed, either on >>> https://xwiki.markmail.org/search/?q=weblate or on IRC, but being able >>> to use xwiki.org as an identity provider on our translation platform >>> would be neat, so it could be something to look for in the possible >>> solutions. >>> >>>> As you may already know, we have thought about replacing the l10n platform >>>> which is becoming too slow. Weblate seems to be a good replacement choice, >>>> as it will able contributors to have their name in the commits and it has >>>> every features needed to make translations. >>>> >>>> One problem is that XWiki doesn't use a standard method to process >>>> translation files. We can solve that by creating some scripts to convert >>>> XWiki translation files into one that Weblate can understand. >>>> >>>> A detailed solution can be found here : >>>> http://design.xwiki.org/xwiki/bin/view/Proposal/WeblateasXWikistranslationplatform >>> >>> We'll indeed need to convert our translation files to a more "standard" >>> format, but I fear that using Python might decrease the maintainability >>> of those scripts. >>> >>> WDYT ? >>> >>>> Feel free to discuss it by responding here or directly in the design page. >>>> >>>> Thanks, >>>> <http://www.xwiki.com/> *Adel Atallah* >>>> *Product developer intern* >>>> [email protected] <[email protected]> >>>> tel: +33 (0)6 12 96 35 06 >>>> >>> >>> Thanks, >>> Clément >>> >> >> >> -- >> Sergiu Dumitriu >> http://purl.org/net/sergiu > > > > -- > Thomas Mortagne
