Re: [Gimp-docs] Gimp-docs Digest, Vol 71, Issue 8
Message: 2 Date: Sun, 11 Apr 2010 18:58:02 +0200 From: Marco Ciampa ciam...@libero.it Subject: Re: [Gimp-docs] Gimp-docs Digest, Vol 71, Issue 7 To: gimp-docs@lists.XCF.Berkeley.EDU Message-ID: 20100411165802.ga...@ciampix-lap2 Content-Type: text/plain; charset=us-ascii how much time wasted using Windows ... sorry I couldn't resist! ;-) I hate that too, but between jumping through Win hoops and not contributing I chose contributing. I had a dual boot before I joined GIMP, so my next move next week I will try to set it up again. on the contributor pages is it written that Linux is the dev OS of choice? There are plenty of translation tools po-aware on that OS... I am sure there are. Linux leads in this area, imo. ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] Gimp-docs Digest, Vol 71, Issue 9
Normally, a translator doesn't use git. He downloads po files from DamnedLies http://l10n.gnome.org. He translates them and checks them with gettext commands and then sends them to his language GNOME maintainer. Well put. I remember there was some effort spend for the user manual and it's also listed. What does translators keep from following that way? Cheers, Roman Joost Well, I thought DamnedLies was just that - statistics. I didn't know about that workflow. Anyway, gettext commands will not check for xml syntax correctness, and we have (had?) some embedded xml in po strings. I am not complaining, part of the reason for me to join was to learn new things. I adopted docbook in my company for user manual, for example. I just didn't expect the learning curve for git would be steeper than svn. ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
