Hi folks,
Felipe's mails remembered me on a huge point on my personal agenda for translations of Geany: Kind of a webinterface where translations can be done in a collaborative way without huge fuzzying around with git master etc. We had this under discussion quiet a lot during the last 10 years but nothing really happend -- my bad at least at some points ;)
So I like to ask: Is somebody of you having any experience with using, administration, installation of any collaborative tool for translation work?
What we currently have ----------------------
Translations are stored inside git within folder /po. This will most likely not change, as this is kind of a pre-set value. However, translations are generated by using tools like poedit oder Geany based on GNU gettext and the geany[-plugins].pot-file inside po-directory. This catalog is currently inside git master only update regularly in front of an release. Also we do have scripts running for http://i18n.geany.org and http://i18n.geany.org/plugins providing updated po files based on a daily run -- but these are not synched to git. In past we had trying to make some usage of launchpad of Ubuntu, but at least I had the feeling it's not working very well.
What I hope we will have at some point --------------------------------------
I pretty much looking for a webinterface, where I can update in a fast and easy way translations. E.g. I see a typo (currently I'm doing it on github editor but this might not work for everybody). Also I would like to have access to some kind of a dictionary/translations catalog enabling use same phrases around geany and geany-plugins as well as use common translations, so the user is feeling "at home" somd kine of.
So anyone able to give input here?
Cheers, Frank
Hi Frank,
about the technical part I'm a zero, but have a little experience with Transifex and it's really easy for translators. Pootle is also nice, and Weblate. These are all easy to use from my point of view.
Just my two cents, Pedro.
On 04-06-2015 17:39, Frank Lanitz wrote:
Hi folks,
Felipe's mails remembered me on a huge point on my personal agenda for translations of Geany: Kind of a webinterface where translations can be done in a collaborative way without huge fuzzying around with git master etc. We had this under discussion quiet a lot during the last 10 years but nothing really happend -- my bad at least at some points ;)
So I like to ask: Is somebody of you having any experience with using, administration, installation of any collaborative tool for translation work?
What we currently have
Translations are stored inside git within folder /po. This will most likely not change, as this is kind of a pre-set value. However, translations are generated by using tools like poedit oder Geany based on GNU gettext and the geany[-plugins].pot-file inside po-directory. This catalog is currently inside git master only update regularly in front of an release. Also we do have scripts running for http://i18n.geany.org and http://i18n.geany.org/plugins providing updated po files based on a daily run -- but these are not synched to git. In past we had trying to make some usage of launchpad of Ubuntu, but at least I had the feeling it's not working very well.
What I hope we will have at some point
I pretty much looking for a webinterface, where I can update in a fast and easy way translations. E.g. I see a typo (currently I'm doing it on github editor but this might not work for everybody). Also I would like to have access to some kind of a dictionary/translations catalog enabling use same phrases around geany and geany-plugins as well as use common translations, so the user is feeling "at home" somd kine of.
So anyone able to give input here?
Cheers, Frank
I18n mailing list I18n@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/i18n
Hi,
I've also heard good things about Transifex when working on XFCE stuff.
The only "bad" part I observed there is the commit logs get jammed with generic, auto-generated commits/messages, hiding all the code changes. I don't know if this would be the case for Geany as it probably has more code-related changes and less translation changes than the project I have experienced this with.
Cheers, Matthew Brush
On 2015-06-04 09:39 AM, Frank Lanitz wrote:
Hi folks,
Felipe's mails remembered me on a huge point on my personal agenda for translations of Geany: Kind of a webinterface where translations can be done in a collaborative way without huge fuzzying around with git master etc. We had this under discussion quiet a lot during the last 10 years but nothing really happend -- my bad at least at some points ;)
So I like to ask: Is somebody of you having any experience with using, administration, installation of any collaborative tool for translation work?
What we currently have
Translations are stored inside git within folder /po. This will most likely not change, as this is kind of a pre-set value. However, translations are generated by using tools like poedit oder Geany based on GNU gettext and the geany[-plugins].pot-file inside po-directory. This catalog is currently inside git master only update regularly in front of an release. Also we do have scripts running for http://i18n.geany.org and http://i18n.geany.org/plugins providing updated po files based on a daily run -- but these are not synched to git. In past we had trying to make some usage of launchpad of Ubuntu, but at least I had the feeling it's not working very well.
What I hope we will have at some point
I pretty much looking for a webinterface, where I can update in a fast and easy way translations. E.g. I see a typo (currently I'm doing it on github editor but this might not work for everybody). Also I would like to have access to some kind of a dictionary/translations catalog enabling use same phrases around geany and geany-plugins as well as use common translations, so the user is feeling "at home" somd kine of.
So anyone able to give input here?
Cheers, Frank
I18n mailing list I18n@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/i18n
Le 05/06/2015 02:12, Matthew Brush a écrit :
Hi,
I've also heard good things about Transifex when working on XFCE stuff.
The only "bad" part I observed there is the commit logs get jammed with generic, auto-generated commits/messages, hiding all the code changes. I don't know if this would be the case for Geany as it probably has more code-related changes and less translation changes than the project I have experienced this with.
BTW, I'd rather see such an automated system perform PRs than direct committing. Basically I don't really trust automated systems to commit to a repository [1] :)
Though, indeed having a system simplifying the translator's work is probably great.
Cheers, Colomban
[1] what if the thing has a security issue that leads for anyone to be able to commit anything? or things like that? I know we trust Git and GitHub here, but they seem more trustworthy security-wise than a translation webapp :)
On 05/06/15 14:05, Colomban Wendling wrote:
Le 05/06/2015 02:12, Matthew Brush a écrit :
Hi,
I've also heard good things about Transifex when working on XFCE stuff.
The only "bad" part I observed there is the commit logs get jammed with generic, auto-generated commits/messages, hiding all the code changes. I don't know if this would be the case for Geany as it probably has more code-related changes and less translation changes than the project I have experienced this with.
BTW, I'd rather see such an automated system perform PRs than direct committing. Basically I don't really trust automated systems to commit to a repository [1] :)
Though, indeed having a system simplifying the translator's work is probably great.
Full ACK. As Matthew mentioned, the Xfce project is using Transifex for years and as far as I know, without bigger problems. I'm pretty much sure such a system would help the Geany project as well as it will be much easier for translators to contribute.
[1] what if the thing has a security issue that leads for anyone to be able to commit anything? or things like that? I know we trust Git and GitHub here, but they seem more trustworthy security-wise than a translation webapp :)
Very good point. A quick internet search didn't reveal much about Transifex being able to create pull requests, though. But Transifex seems to be able to work with branches. Maybe we could set up a i18n branch to which Transifex pushes directly and Frank or whoever else wants to, merges or cherry-picks from this branch to master on demand. The reverse merge from master to the i18n branch can be automated, probably. I have no idea if this could work reliably in production, so far it's just an idea :).
Regards, Enrico
Am 05.06.2015 um 16:37 schrieb Enrico Tröger:
Very good point. A quick internet search didn't reveal much about Transifex being able to create pull requests, though. But Transifex seems to be able to work with branches. Maybe we could set up a i18n branch to which Transifex pushes directly and Frank or whoever else wants to, merges or cherry-picks from this branch to master on demand. The reverse merge from master to the i18n branch can be automated, probably. I have no idea if this could work reliably in production, so far it's just an idea :).
Yep, could solve that issue. Working in a special branch/repo and then sqash + merge. Or even a simple a merge --no-ff would at least prevent git from putting commits on top of master.
Cheers, Frank