Re: [Gimp-docs] Gimp-docs Digest, Vol 71, Issue 7
On Tue, Apr 13, 2010 at 07:43:55AM +0200, jhardlin wrote: > In Damned Lies, you can not send translation directly to the git > repository. Your work must be controlled by other translators and > approved by the language maintainer. ... and this is currently not possible? Why? Because we're not part of the GNOME i18n teams? As I understood Damned Lies: There are teams which coordinate the translation for each GNOME package. I guess the gimp user manual forms an exception here. Please correct me if I'm wrong. > GIMP-HELP is an exception, due to its history. Here, translators are not > many, are highly motivated and prefer to have a complete control > themselves on their work. Managing git, and using Ulf's improvements, is > a challenge for them. Well then I wonder, how can we make it easier and not a challenge ... Cheers, -- Roman Joost www: http://www.romanofski.de email: romanof...@gimp.org signature.asc Description: Digital signature ___ 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 7
> >> We migrated from xml to po files to make translator's work easier... > Is that a statement, an answer or is there more to say? :) ... and we didn't get the wanted result. >> 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? In Damned Lies, you can not send translation directly to the git repository. Your work must be controlled by other translators and approved by the language maintainer. GIMP-HELP is an exception, due to its history. Here, translators are not many, are highly motivated and prefer to have a complete control themselves on their work. Managing git, and using Ulf's improvements, is a challenge for them. Julien ___ 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 7
On Sun, Apr 11, 2010 at 09:22:21PM +0200, jhardlin wrote: > me too :-) . What tripped me up in the beginning was git. Wrapping my > > head around it (with all the good help and manuals) took me some time, > > and every time I had git problem, my enthusiasm cooled down a little. > > Many a times I just backed up my changed files, deleted the local > > folder and downloaded the repository from scratch. All the while I > > wasn't translating. > > We migrated from xml to po files to make translator's work easier... Is that a statement, an answer or is there more to say? :) > 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 www: http://www.romanofski.de email: romanof...@gimp.org signature.asc Description: Digital signature ___ 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 7
Hi, I did use Cygwin and felt difficulty on conflict of file names too. It may be a case insensitivity problem caused by the Windows file system. When I Noticed it on using GIT, I made one more clone repository at another directory. Though it is a fresh tree, an warning message was appear soon. The rebase command doesn't work with an error message. With the stash command, saving can be done successfully, but loading process stops with a reason that the tree is dirty, so this command is also unusable. After back to FreeBSD system, I tried to remove one of two images and it was easy. Then I created a GIT patch on this commit, and went to apply this diff on the Cygwin's tree. Unfortunately, this patch file is not applicable on Windows file system. Therefore, there is no solution of it for Cygwin users. I can remove the older file if you need, and I hope this issue is cleared, but perhaps it may cause another unexpected problem on Cygwin. 2010/4/11 Vitaly Lomov : >...snip... > The last thing that did it for me was some .gif > image that was originally saved as .GIF then somehow became .gif. Git > treated them differently and couldn't commit my changes because one > file wasn't there, but the file was there with just a different letter > case. I am on windows, where case doesn't matter. Deleting or renaming > the files just made matters worse. So, take-away point should be > consistent case (i.e. all small) for committed files. My guess is the > image was created in Paint, which saves the file with capital case > extension. -=-=-=-=-= SimaMoto,RyōTa http://code.google.com/p/gimp-doc-ja/ ___ 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 7
me too :-) . What tripped me up in the beginning was git. Wrapping my > head around it (with all the good help and manuals) took me some time, > and every time I had git problem, my enthusiasm cooled down a little. > Many a times I just backed up my changed files, deleted the local > folder and downloaded the repository from scratch. All the while I > wasn't translating. We migrated from xml to po files to make translator's work easier... 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. Only doc creators need git. Julien ___ 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 7
On Sun, Apr 11, 2010 at 09:02:37AM +0100, Vitaly Lomov wrote: > me too :-) . What tripped me up in the beginning was git. Wrapping my > head around it (with all the good help and manuals) took me some time, > and every time I had git problem, my enthusiasm cooled down a little. > Many a times I just backed up my changed files, deleted the local > folder and downloaded the repository from scratch. All the while I > wasn't translating. The last thing that did it for me was some .gif > image that was originally saved as .GIF then somehow became .gif. Git > treated them differently and couldn't commit my changes because one > file wasn't there, but the file was there with just a different letter > case. I am on windows, where case doesn't matter. Deleting or renaming > the files just made matters worse. So, take-away point should be > consistent case (i.e. all small) for committed files. My guess is the > image was created in Paint, which saves the file with capital case > extension. > I think move to po was a great idea. But I found editor functionality > lacking. Tried poedit and lokalize, decided to use lokalize, which has > good translation memory management, but crashes if you sneeze at it. > If I spend any of little free time researching other editors, I am not > translating. On the contributor page recommended software section > would be great. how much time wasted using Windows ... sorry I couldn't resist! ;-) 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... -- Marco Ciampa ++ | Linux User #78271 | | FSFE fellow #364 | ++ ___ 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 7
> Date: Sat, 10 Apr 2010 12:25:14 +1000 > From: Roman Joost > Subject: [Gimp-docs] Most annoying thing > To: GIMP Docs > Message-ID: <20100410022514.gb18...@bromeco.de> > Content-Type: text/plain; charset="utf-8" > > Now two years later: What is now the most annoying thing? > > The most annoying thing for me is, that I can't spend as much time on the > project as I would like to spend. I haven't made any contributions to > the manual for a while, also due to the fact that I'm just lost in the > current editing process. The wiki is down and doesn't seem to return > anymore. Maybe a better space to invite potential contributors would be > to open a space on the GNOME wiki me too :-) . What tripped me up in the beginning was git. Wrapping my head around it (with all the good help and manuals) took me some time, and every time I had git problem, my enthusiasm cooled down a little. Many a times I just backed up my changed files, deleted the local folder and downloaded the repository from scratch. All the while I wasn't translating. The last thing that did it for me was some .gif image that was originally saved as .GIF then somehow became .gif. Git treated them differently and couldn't commit my changes because one file wasn't there, but the file was there with just a different letter case. I am on windows, where case doesn't matter. Deleting or renaming the files just made matters worse. So, take-away point should be consistent case (i.e. all small) for committed files. My guess is the image was created in Paint, which saves the file with capital case extension. I think move to po was a great idea. But I found editor functionality lacking. Tried poedit and lokalize, decided to use lokalize, which has good translation memory management, but crashes if you sneeze at it. If I spend any of little free time researching other editors, I am not translating. On the contributor page recommended software section would be great. ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
