25 Apr
2018
25 Apr
'18
10:47 a.m.
On 24 Apr 2018, at 15:44, Clément Aubin
<aubincleme(a)gmail.com> wrote:
On 04/23/2018 12:18 PM, Adel Atallah wrote:
- You said "Weblate is able to run scripts after pulling changes from the git
repository and before committing changes.”. I don’t understand this sentence. You mean to
sync files that are located in our Git repos to weblate (git —> weblate)? When you say
“committing changes” you mean loading changes from git and inside weblate?
- You said "XML files with properties as content will be treated the same way as
above”. I couldn’t find what you meant by “same way as above”. Certainly you’ll need to
generate some properties file out of the XML file, no?
- Globally I find what you describe very complex and a bit hackish. Especially the part
about having some “.translation” directory which I assume you’ll want to commit in our git
repos?
- Isn’t it possible to add some new file format inside weblate instead so that it
understands properties inside XML files, etc.?
- Another idea: using weblate’s REST APIs to push/pull from weblate, using github web
hooks to perform conversions:
— when a change is pushed to a translation file in github, run a script to import it
inside weblate using weblate’s REST API
— when a change is done inside weblate and a PR is sent to our repos by weblate, run a
script to convert the content to the proper format and modify the PR accordingly
Even that sounds complex IMO. Being able to teach weblate about our format would seem the
simplest. If we could do this we could even send weblate a PR to support our format
natively.
You also need to handle deprecated keys, ability to rename/move a key and all its
translations, etc.
Thanks
-Vincent
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/
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/WeblateasXWikistranslationp…
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*
adel.atallah(a)xwiki.com <corina.luong(a)xwiki.com>
tel: +33 (0)6 12 96 35 06
Thanks,
Clément