Hi Yaron,
welcome back!
And thanks for exploring Crowdin.
What do you see as their advantages? I've taken a look at their website, and all I could find was a proprietary, hosted program, with free plans for open source projects on request :-(
They don't appear to be open source, as far as I could find.
This looks like it could be a quick-set-up option for interim solutions for small teams outside of the official Inkscape project, but if it's meant to be official, it would need to be open source.
Have you also had a look at other translation web interfaces recently? It's hard to stay up-to-date, we need more eyes :)
This is what I found out about Weblate:
I must admit that the first setup is pretty slow. Filling the database took 20 minutes for 6 languages out of 90, then I had to break off, it was getting too late, will try again another day, and maybe not with the full Inkscape repo, but with inkscape-docs.
They added a lot of control options and also translation memory and multiple machine translation options since I last had a look. The translation interface could be more straightforward (the menus - and especially getting back to where I came from - were confusing). The functionality seems to be just fine. It allows discussions, comments, screenshot uploads (you told me about that previously, but I couldn't take a look then). Will need to do some more testing when I get my Hackfest Laptop from Tuxedo (they are going to lend it to me for that time, and are a sponsor of Kielux).
Do you have any other systems to suggest for testing?
Maren
Am 25.07.2018 um 09:55 schrieb Yaron Shahrabani:
Hey there, I'm sorry I faded away, I got really hooked up at work.
Anyways, I've tried implementing Crowdin, less overhead, can be easily managed (as long as we have only a file or 2), returns back to repository, if there are scripts that manage your current Github repo (syncing etc.) I can probably use it to create my own setup and connect it to Crowdin, I've tried it before with Gitlab but it was too much code and the repository was closed.
We can play around with my repository and if it works we'll move it over to your repository, I can take ownership if needed, I'm already doing it for several different projects. YaronShahrabani
<DevOps - Hebrew translator>On Wed, Jul 25, 2018 at 4:02 AM Maren Hachmann <maren@...325... mailto:maren@...325...> wrote:
Am 23.07.2018 um 19:35 schrieb Bryce Harrington: > On Mon, Jul 23, 2018 at 06:17:34PM +0200, Firas Hanife wrote: >> Hello, >> >> I'm the current Italian translator for Inkscape. In the last years I worked >> alone on the translations, but now I have been contacted by some users that >> would like to contribute to the translation work. >> >> I created a fork on gitlab for Inkscape: >> https://gitlab.com/FirasH/inkscape >> >> and for Inkscape documentation: >> https://gitlab.com/FirasH/documentation >> >> but I don't know how to configure my fork to do the following: >> 1) keep it up to date with master and 0.92.x except for the translation >> files >> >> I added the original repo as mirrored, but as soon as I push a commit >> request I get an error due to mismatch between my fork and the original one >> (mirrored). > > Do your work on a branch off your forked version, and that should avoid > that I think. Setting it up as a mirror should work ok; I've done this > in other projects. > > However, I don't think this is a typical workflow that translators use, > so hopefully they can share some other approaches that might work better > for you. For code development, many people craft their branch off the > main Inkscape repo rather than off their own mirror; this tends to be > simpler to set up, and (I think?) easier to send merge requests from. > But again the translation team can probably give you more practical > advice for your particular need. Hi Firas, great that you found some support for helping with Italian (does it have to do with someone from the English Inkscape forums asking on the Italian Inkscape forums? I remember suggesting it, but haven't heard if there were any reactions.)! For German, we have an even more manual setup, see https://github.com/Ede123/inkscape-localization . The repository only contains our own po files and not much else - that's why it also requires a lot of manual work. I think one of the reasons for having it in a separate repo was that then we can discuss (in German) without annoying devs with it (they probably already get a headache from all my posts...). Some time ago, Yaron suggested using Weblate, but then we were in need of someone who would want to be responsible, and discussion subsided. As it's django-based, I was just playing around with it a bit this evening locally. It seems a bit slow, from their demo page (and locally, too), but I'll play with it a bit more. Maybe we can some day set up an instance of it on one of the virtual hosts on cloudscale, and have it automatically push translation changes to a branch on gitlab. Maren > Bryce > >> 2) keep the "names" of the people who contributed to my fork in the commits >> (that I will review, then create a merge request) >> >> Thanks in advance, >> Firas > >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> _______________________________________________ >> Inkscape-translator mailing list >> Inkscape-translator@lists.sourceforge.net <mailto:Inkscape-translator@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/inkscape-translator > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-translator mailing list > Inkscape-translator@lists.sourceforge.net <mailto:Inkscape-translator@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/inkscape-translator > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-translator mailing list Inkscape-translator@lists.sourceforge.net <mailto:Inkscape-translator@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/inkscape-translator