Re: [Gimp-docs] some docs fixes
Dne 21.12.2010 15:51, Julien Hardelin napsal(a): > Hi Miroslav, > > Your patches have been pushed. thank you. i noticed it cost you one hour of work. > Good work! > Could you tell us how you modified msgid strings in po files? A command > line? A script? i did all the fixes with grep and sed, except the case of "the the" string where one "the" was at the end of one line and the other "the" was at the beginning of following line ... that i edited manually though it could be automated too, but it does not deserve the effort. editing everything manually would be very time consuming. still, it cost me over one hour just the last time to prepare the patches. also, for typo issues i used whole git repo, whereas for changes in words i used just src dir. the simple case looked like this: for file in `git grep -l " you you "`; do sed -i "s/ you you / you /g" $file; done the whole process was little bit more complicated as i wanted to be sure the result is exactly what i want, so it was like pre-scan, modify, check, commit. about the msgid, it should work imo as we changed the typos both in src and po files the same way, so after concatenating the msgid strings, the result should be still the same as in xml files. i'll prepare you more patches when i find some time, as there are more issues i found. > Julien miroslav ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Hi Miroslav, Your patches have been pushed. Good work! Could you tell us how you modified msgid strings in po files? A command line? A script? Julien ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Dne 21.12.2010 07:42, Julien Hardelin napsal(a): > Hi Miroslav, >> well, i have no idea what is the rule now, but imo making extra work for >> translation teams just because there was a typo in english version does >> not make sense to me :-) > You are right. > > But here what I get when applying patches: > > ~/gimp-help-2> git apply select_to_channel.patch > > ~/gimp-help-2> git apply access_to.patch > error: patch failed: po/es/toolbox.po:2754 > error: po/es/toolbox.po: patch does not apply > > ~/gimp-help-2> git apply magnify_to_zoom.patch > error: patch failed: po/es/toolbox.po:183 > error: po/es/toolbox.po: patch does not apply > > ~/gimp-help-2> git apply duplicate.patch > ~/git-patches/gimp-help-2> > > The es toolbox.po files has been updated after you made patches. > > The problem is that there are 1769 lines only in this file and that line > 183 looks perfectly normal. > > Do you have a solution? i will prepare you new patches, but it's a question whether the process will be short enough so no po changes/commits will break it :-) if i had direct access to repo, this would be much easier. > Julien miroslav ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Hi Marco, On Sat, Dec 18, 2010 at 02:10:12PM +0100, Marco Ciampa wrote: > On Sat, Dec 18, 2010 at 12:12:35PM +0100, Miroslav Šulc wrote: > > Dne 18.12.2010 08:22, Roman Joost napsal(a): > > http://en.wikipedia.org/wiki/Capitalization > http://jon.henshaw.me/rules-for-capitalization-in-a-title/ > Cheers for clarifying. I never bothered to look around actually. 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] some docs fixes
Hi Jan, On Sun, Dec 19, 2010 at 01:59:07AM +0100, Miroslav Šulc wrote: > > Hi Roman, > > > > Does the GIMP documentation project have a style guide such as the > > excellent GNOME Documentation Style Guide? > > http://library.gnome.org/devel/gdp-style-guide/2.32/index.html.en > > well, maybe gimp documentation team should use that guide instead of > creating its own :-) Yes. Afaik - we don't have one on our own, but use the guide lines from the GNOME documentation project like the one you've found. 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] some docs fixes
Hi Miroslav, > well, i have no idea what is the rule now, but imo making extra work for > translation teams just because there was a typo in english version does > not make sense to me :-) You are right. But here what I get when applying patches: ~/gimp-help-2> git apply select_to_channel.patch ~/gimp-help-2> git apply access_to.patch error: patch failed: po/es/toolbox.po:2754 error: po/es/toolbox.po: patch does not apply ~/gimp-help-2> git apply magnify_to_zoom.patch error: patch failed: po/es/toolbox.po:183 error: po/es/toolbox.po: patch does not apply ~/gimp-help-2> git apply duplicate.patch ~/git-patches/gimp-help-2> The es toolbox.po files has been updated after you made patches. The problem is that there are 1769 lines only in this file and that line 183 looks perfectly normal. Do you have a solution? Julien ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Dne 20.12.2010 16:27, Julien Hardelin napsal(a): > Oh sorry, I understand now what you want to do with your patch. I was > accustomed to have a #, fuzzy comment for one lettre changed. well, i have no idea what is the rule now, but imo making extra work for translation teams just because there was a typo in english version does not make sense to me :-) > I just resumed work after six monthes absence. I have lost familiarity > with gimp-help and I had gorgotten that there are two zoom.xml :-( > > But I get now into a problem: > > When I run > git-apply --check xxx.patch > I get the error "Command not found". > > Trying to resolve it... try "git apply", so instead '-' use space :-) > Julien miroslav ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Oh sorry, I understand now what you want to do with your patch. I was accustomed to have a #, fuzzy comment for one lettre changed. I just resumed work after six monthes absence. I have lost familiarity with gimp-help and I had gorgotten that there are two zoom.xml :-( But I get now into a problem: When I run git-apply --check xxx.patch I get the error "Command not found". Trying to resolve it... Julien ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Dne 20.12.2010 07:50, Julien Hardelin napsal(a): > Le 19/12/2010 17:34, Miroslav Šulc a écrit : > I'll apply only changes in source xml files. >>> cool, thanks. i have more patches on my disk, and planning to make a >>> patch for other stuff too, like the capitalization of titles (and >>> uncapitalization of image labels), tagging ui objects etc ... just need >>> to know what is supposed to be the right style for the docs as it is not >>> obvious to me yet. >>> > I have several English books and in all, title are capitalized. Image > legends are not capitalized, excepted when they they refer to a command. > Example: "The Save as Brush dialog, showing a sample brush". that is the same what i saw in the "GNOME Documentation Style Guide" that Jan Smith pointed to. imo that is the style guide that should be used for gimp documentation too, but i am not the one to say that, proly Róman is the right person to say that :-) >>> also, i agree with you that the fixes should probably be done only in >>> src dir, the translation teams will get them once they update their po >>> files as it affects also msgid items. i have no idea how much it will >>> break their work as the msgid values will be new and will not match what >>> comes from the main xml files. from this point of view patching also >>> msgid lines would be better, but it's a question whether some inner po >>> logic will not be broken by that. > Modifying msgid strings manually is nonsense. > A normal workflow is: > - git pull --rebase > This will update, in your repo, src/*.xml files and synchronize po files > if another translator made changes in them. > > - make pot-xx > This updates pot files according to changes in xml files. > > - make po-xx > This updates your po files: msgid strings are updated and marked with a > "#, fuzzy" comment. yes, i understand the workflow, i just did not want to create too much work for nothing for the translation teams as they will get every text that contains typos marked as fuzzy. and if they do not follow, they will wonder why their text is fuzzy and will waste time on checking the translation. it make no sense to me to mark their work fuzzy when "the the" is replaced with "the" etc. so you are sure you wanna go the fuzzy way? >>> up to that, the changes are just in english language, so it affects >>> either the untranslated texts or the msgid lines, not their translations. >> just as thinking about it, please let me know what way you wanna apply >> the patches. if you wanna change just src files, i can adjust the >> patches. i used mostly grep and sed for these patches so they were fast >> to create, but there were also cases with one line ending with "the" and >> following line beginning with "the" so some changes were not that trivial. > Patches are applied to the src/*.xml files. >> also, as these issues occur both in gimp-help-2-6-0 and in master, in my >> opinion they should go first to branch gimp-help-2-6-0 and then should >> be merged to master (and after that master should be searched for any >> ommitted cases), but i noticed there is quite a lot (exactly 9) unmerged >> changes between gimp-help-2-6-0 and master so i am not sure you port >> everything from 2.6 branch to master. up to that, some changes, though >> not merged from the branch, are in the master anyway, which confuses me >> even more :-) > Don't worry about gimp-help-2.6.0. > We work on master only. Our boss, Roman, periodically makes a new > release of this help (which is always behind the master...) he makes releases of the gimp-help-2.6.0 branch? i proly did not understand this correctly, as according to Ulf, this branch should be obsolete now, but it reappeared in repo again. >> after this, i can adjust the patches and prepare the rest of patches (i >> have total 10, just 6 are at bugzilla atm) and i will know how to >> prepare the rest. > Please send patches directly to me, so that I am not obliged to retrieve > them from Bugzilla. ok. i have 12 patches now here and more will be coming. i just need your confirmation that you want the typo fixes do the "fuzzy" way (as described above in this mail) and then i will send them all your way in proper format. > Julien miroslav ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Dne 19.12.2010 21:25, Ulf-D. Ehlert napsal(a): > Miroslav Šulc (Thursday, 16. December 2010) >> well, as i think of it, the best way would be to create the patches >> on gimp-help-2-6-0 branch (to fix current documentation) and then >> merge them to master branch and update them to the changes in >> master branch (to have the fixes at the latest changes too), > I forgot: Ignore the gimp-help-2-6-0 branch, this is/was a temporary > branch and is no longer used. > I had renamed it to "obsolete/gimp-help-2-6-0", but somehow (voodoo?) > it came back... ah, now it makes sense, thx. anyway, some translators are still committing there it seems: http://git.gnome.org/browse/gimp-help-2/log/?h=gimp-help-2-6-0 > Ulf miroslav ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Dne 20.12.2010 08:00, Julien Hardelin napsal(a): > Le 19/12/2010 17:17, Miroslav Šulc a écrit : >> my git repo is up to date, what is not probably up to date is po files >> of some translations. just run this to see yourself: > If your repo is up-to-date, go to src/toolbox. You must find the > zoom.xml file. Open it in a text editor : you will see that there is no > "Magnify". there is really no Magnify in src/toolbox/zoom.xml file. it is in src/menus/view/zoom.xml. you can try this: $ git grep Magnify src/ src/menus/view/zoom.xml: can also use the Magnify tool src/toolbox/zoom.xml: 2009-04-04 j.h: review for v2.6. Magnify -> Zoom second is reference to changelog, so only first has to be fixed. and i see Magnify is still there, though the linkend is already fixed. >> git grep src/toolbox/tool-zoom.xml > This command shows reference to tool-zoom.xml in the old changelogs that > we no longer fill since we migrated to git from svn. well, not only changelogs, you probably did not scroll to the end of the output :-) on my laptop the output for a while contained only changelog entries, but after a while occurrences in po files were added. you can try this: git grep src/toolbox/tool-zoom.xml po/ you should see that it is referenced in po//toolbox.po files of es, fi, hr, ko, lt, nl, pl, sv and zh_CN. so these are not up to date with latest xml files. > Julien miroslav ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Miroslav Šulc (Thursday, 16. December 2010) > well, as i think of it, the best way would be to create the patches > on gimp-help-2-6-0 branch (to fix current documentation) and then > merge them to master branch and update them to the changes in > master branch (to have the fixes at the latest changes too), I forgot: Ignore the gimp-help-2-6-0 branch, this is/was a temporary branch and is no longer used. I had renamed it to "obsolete/gimp-help-2-6-0", but somehow (voodoo?) it came back... Ulf -- Gott ist der einzige Herr der Welt, der weniger zu sagen hat als seine Diener. -- Karlheinz Deschner signature.asc Description: This is a digitally signed message part. ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Le 19/12/2010 17:17, Miroslav Šulc a écrit : > my git repo is up to date, what is not probably up to date is po files > of some translations. just run this to see yourself: > If your repo is up-to-date, go to src/toolbox. You must find the zoom.xml file. Open it in a text editor : you will see that there is no "Magnify". > git grep src/toolbox/tool-zoom.xml > This command shows reference to tool-zoom.xml in the old changelogs that we no longer fill since we migrated to git from svn. Julien ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Le 19/12/2010 17:34, Miroslav Šulc a écrit : >>> >>> I'll apply only changes in source xml files. >> cool, thanks. i have more patches on my disk, and planning to make a >> patch for other stuff too, like the capitalization of titles (and >> uncapitalization of image labels), tagging ui objects etc ... just need >> to know what is supposed to be the right style for the docs as it is not >> obvious to me yet. >> I have several English books and in all, title are capitalized. Image legends are not capitalized, excepted when they they refer to a command. Example: "The Save as Brush dialog, showing a sample brush". >> also, i agree with you that the fixes should probably be done only in >> src dir, the translation teams will get them once they update their po >> files as it affects also msgid items. i have no idea how much it will >> break their work as the msgid values will be new and will not match what >> comes from the main xml files. from this point of view patching also >> msgid lines would be better, but it's a question whether some inner po >> logic will not be broken by that. >> Modifying msgid strings manually is nonsense. A normal workflow is: - git pull --rebase This will update, in your repo, src/*.xml files and synchronize po files if another translator made changes in them. - make pot-xx This updates pot files according to changes in xml files. - make po-xx This updates your po files: msgid strings are updated and marked with a "#, fuzzy" comment. >> up to that, the changes are just in english language, so it affects >> either the untranslated texts or the msgid lines, not their translations. > just as thinking about it, please let me know what way you wanna apply > the patches. if you wanna change just src files, i can adjust the > patches. i used mostly grep and sed for these patches so they were fast > to create, but there were also cases with one line ending with "the" and > following line beginning with "the" so some changes were not that trivial. > Patches are applied to the src/*.xml files. > also, as these issues occur both in gimp-help-2-6-0 and in master, in my > opinion they should go first to branch gimp-help-2-6-0 and then should > be merged to master (and after that master should be searched for any > ommitted cases), but i noticed there is quite a lot (exactly 9) unmerged > changes between gimp-help-2-6-0 and master so i am not sure you port > everything from 2.6 branch to master. up to that, some changes, though > not merged from the branch, are in the master anyway, which confuses me > even more :-) > Don't worry about gimp-help-2.6.0. We work on master only. Our boss, Roman, periodically makes a new release of this help (which is always behind the master...) > after this, i can adjust the patches and prepare the rest of patches (i > have total 10, just 6 are at bugzilla atm) and i will know how to > prepare the rest. Please send patches directly to me, so that I am not obliged to retrieve them from Bugzilla. Julien ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Dne 19.12.2010 17:10, Miroslav Šulc napsal(a): > Dne 19.12.2010 15:26, Julien Hardelin napsal(a): >>> i have 10 patches in my local git repo now fixing various problems, and >>> now even in the proper format. i just did not want to spam bugzilla more. >> Hi Miroslav, >> >> I'll take care of your patches in Bugzilla. >> >> In magnify_to_zoom.patch, there are changes in po of different >> languages. Usually, patches are only for source xml files. >> >> I am not sure translators will agree foreign changes in their work. >> >> I'll apply only changes in source xml files. > cool, thanks. i have more patches on my disk, and planning to make a > patch for other stuff too, like the capitalization of titles (and > uncapitalization of image labels), tagging ui objects etc ... just need > to know what is supposed to be the right style for the docs as it is not > obvious to me yet. > > also, i agree with you that the fixes should probably be done only in > src dir, the translation teams will get them once they update their po > files as it affects also msgid items. i have no idea how much it will > break their work as the msgid values will be new and will not match what > comes from the main xml files. from this point of view patching also > msgid lines would be better, but it's a question whether some inner po > logic will not be broken by that. > > up to that, the changes are just in english language, so it affects > either the untranslated texts or the msgid lines, not their translations. just as thinking about it, please let me know what way you wanna apply the patches. if you wanna change just src files, i can adjust the patches. i used mostly grep and sed for these patches so they were fast to create, but there were also cases with one line ending with "the" and following line beginning with "the" so some changes were not that trivial. also, as these issues occur both in gimp-help-2-6-0 and in master, in my opinion they should go first to branch gimp-help-2-6-0 and then should be merged to master (and after that master should be searched for any ommitted cases), but i noticed there is quite a lot (exactly 9) unmerged changes between gimp-help-2-6-0 and master so i am not sure you port everything from 2.6 branch to master. up to that, some changes, though not merged from the branch, are in the master anyway, which confuses me even more :-) after this, i can adjust the patches and prepare the rest of patches (i have total 10, just 6 are at bugzilla atm) and i will know how to prepare the rest. >> Your new look at GIMP Help is precious. >> >> All the best, >> >> Julien miroslav ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Dne 19.12.2010 15:57, Julien Hardelin napsal(a): > Hi again, > > In magnify_to_zoom patch: > > #: src/toolbox/tool-zoom.xml:50(para) > msgid "" > -"The Magnify Tool is used to change the zoom level of your working > image. If " > +"The Zoom Tool is used to change the zoom level of your working image. If " > > src/toolbox/tool-zoom.xml doesn't exist. We presently have > src/toolbox/zoom.xml where no "Magnify" is present. > > Which version of gimp-help-2 are you working on? > > You must do > git clone git://git.gnome.org/gimp-help-2 > > In the gimp-help-2 directory you get, you run > ./autogen.sh --without-gimp ALL_LINGUAS="cz en" > make html-en > to get the up-to-date English html. my git repo is up to date, what is not probably up to date is po files of some translations. just run this to see yourself: git grep src/toolbox/tool-zoom.xml doing that on master and on gimp-help-2-6-0 gives roughly the same results (i did not diff the results to see whether there are some differences). > Julien miroslav ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Dne 19.12.2010 15:26, Julien Hardelin napsal(a): >> i have 10 patches in my local git repo now fixing various problems, and >> now even in the proper format. i just did not want to spam bugzilla more. > Hi Miroslav, > > I'll take care of your patches in Bugzilla. > > In magnify_to_zoom.patch, there are changes in po of different > languages. Usually, patches are only for source xml files. > > I am not sure translators will agree foreign changes in their work. > > I'll apply only changes in source xml files. cool, thanks. i have more patches on my disk, and planning to make a patch for other stuff too, like the capitalization of titles (and uncapitalization of image labels), tagging ui objects etc ... just need to know what is supposed to be the right style for the docs as it is not obvious to me yet. also, i agree with you that the fixes should probably be done only in src dir, the translation teams will get them once they update their po files as it affects also msgid items. i have no idea how much it will break their work as the msgid values will be new and will not match what comes from the main xml files. from this point of view patching also msgid lines would be better, but it's a question whether some inner po logic will not be broken by that. up to that, the changes are just in english language, so it affects either the untranslated texts or the msgid lines, not their translations. > Your new look at GIMP Help is precious. > > All the best, > > Julien miroslav ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Hi again, In magnify_to_zoom patch: #: src/toolbox/tool-zoom.xml:50(para) msgid "" -"The Magnify Tool is used to change the zoom level of your working image. If " +"The Zoom Tool is used to change the zoom level of your working image. If " src/toolbox/tool-zoom.xml doesn't exist. We presently have src/toolbox/zoom.xml where no "Magnify" is present. Which version of gimp-help-2 are you working on? You must do git clone git://git.gnome.org/gimp-help-2 In the gimp-help-2 directory you get, you run ./autogen.sh --without-gimp ALL_LINGUAS="cz en" make html-en to get the up-to-date English html. Julien ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
> i have 10 patches in my local git repo now fixing various problems, and > now even in the proper format. i just did not want to spam bugzilla more. Hi Miroslav, I'll take care of your patches in Bugzilla. In magnify_to_zoom.patch, there are changes in po of different languages. Usually, patches are only for source xml files. I am not sure translators will agree foreign changes in their work. I'll apply only changes in source xml files. Your new look at GIMP Help is precious. All the best, Julien ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Dne 18.12.2010 20:49, Jan Smith napsal(a): > > > Date: Sat, 18 Dec 2010 17:22:41 +1000 > From: Roman Joost mailto:romanof...@gimp.org>> > Subject: Re: [Gimp-docs] some docs fixes > To: "Ulf-D. Ehlert" mailto:ud...@web.de>> > Cc: gimp-docs@lists.xcf.berkeley.edu > <mailto:gimp-docs@lists.xcf.berkeley.edu> > Message-ID: <20101218072241.gj29...@ned> > Content-Type: text/plain; charset="utf-8" > > Hi Ulf, > > On Wed, Dec 15, 2010 at 09:14:57PM +0100, Ulf-D. Ehlert wrote: > > BTW: What do the official rules say? > As far as I know: Starting with uppercase, continuing with lowercase - > as usual. Although I have to admit, that I'm not 100% sure about that. > The English native speakers I've talked to weren't that sure either. > Perhaps it's about consistancy ... > > Cheers, > -- > Roman Joost > > > Hi Roman, > > Does the GIMP documentation project have a style guide such as the > excellent GNOME Documentation Style Guide? > http://library.gnome.org/devel/gdp-style-guide/2.32/index.html.en > > Cheers, > > Jan Smith well, maybe gimp documentation team should use that guide instead of creating its own :-) miroslav ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
> > > Date: Sat, 18 Dec 2010 17:22:41 +1000 > From: Roman Joost > Subject: Re: [Gimp-docs] some docs fixes > To: "Ulf-D. Ehlert" > Cc: gimp-docs@lists.xcf.berkeley.edu > Message-ID: <20101218072241.gj29...@ned> > Content-Type: text/plain; charset="utf-8" > > Hi Ulf, > > On Wed, Dec 15, 2010 at 09:14:57PM +0100, Ulf-D. Ehlert wrote: > > BTW: What do the official rules say? > As far as I know: Starting with uppercase, continuing with lowercase - > as usual. Although I have to admit, that I'm not 100% sure about that. > The English native speakers I've talked to weren't that sure either. > Perhaps it's about consistancy ... > > Cheers, > -- > Roman Joost > Hi Roman, Does the GIMP documentation project have a style guide such as the excellent GNOME Documentation Style Guide? http://library.gnome.org/devel/gdp-style-guide/2.32/index.html.en Cheers, Jan Smith > ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Dne 18.12.2010 14:10, Marco Ciampa napsal(a): > On Sat, Dec 18, 2010 at 12:12:35PM +0100, Miroslav Šulc wrote: >> Dne 18.12.2010 08:22, Roman Joost napsal(a): >>> Hi Ulf, >>> >>> On Wed, Dec 15, 2010 at 09:14:57PM +0100, Ulf-D. Ehlert wrote: BTW: What do the official rules say? >>> As far as I know: Starting with uppercase, continuing with lowercase - >>> as usual. Although I have to admit, that I'm not 100% sure about that. >>> The English native speakers I've talked to weren't that sure either. >>> Perhaps it's about consistancy ... >> i have here some english written books and i think all of them use >> capitalization of headings ... but searching on net, people claim that >> it depends on the purpose of the heading and the depth of it. when >> looking at netbeans documentation, they use capitalization in headings >> too. so it looks like capitalization is the preffered style, at least >> where i looked. anyway, i think it's up to the docs team to specify this >> rule for english documentation, and once done, i can adjust the >> documentation to the rules when i find some time. >>> Cheers, >> miroslav > http://en.wikipedia.org/wiki/Capitalization > http://jon.henshaw.me/rules-for-capitalization-in-a-title/ > > Please note that, as the main (and almost only) author of the italian > translation of the GIMP manual, I've always removed it (if found is an > error) as in italian is considered a bad habit and is not used at all > (pick any italian newspaper at random to see..). well, i am talking only about english version of the documentation, for example in czech (my language) we capitalize only first word in titles, which is proly the same as in italian. miroslav ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
On Sat, Dec 18, 2010 at 12:12:35PM +0100, Miroslav Šulc wrote: > Dne 18.12.2010 08:22, Roman Joost napsal(a): > > Hi Ulf, > > > > On Wed, Dec 15, 2010 at 09:14:57PM +0100, Ulf-D. Ehlert wrote: > >> BTW: What do the official rules say? > > As far as I know: Starting with uppercase, continuing with lowercase - > > as usual. Although I have to admit, that I'm not 100% sure about that. > > The English native speakers I've talked to weren't that sure either. > > Perhaps it's about consistancy ... > i have here some english written books and i think all of them use > capitalization of headings ... but searching on net, people claim that > it depends on the purpose of the heading and the depth of it. when > looking at netbeans documentation, they use capitalization in headings > too. so it looks like capitalization is the preffered style, at least > where i looked. anyway, i think it's up to the docs team to specify this > rule for english documentation, and once done, i can adjust the > documentation to the rules when i find some time. > > Cheers, > miroslav http://en.wikipedia.org/wiki/Capitalization http://jon.henshaw.me/rules-for-capitalization-in-a-title/ Please note that, as the main (and almost only) author of the italian translation of the GIMP manual, I've always removed it (if found is an error) as in italian is considered a bad habit and is not used at all (pick any italian newspaper at random to see..). -- 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] some docs fixes
Dne 18.12.2010 08:22, Roman Joost napsal(a): > Hi Ulf, > > On Wed, Dec 15, 2010 at 09:14:57PM +0100, Ulf-D. Ehlert wrote: >> BTW: What do the official rules say? > As far as I know: Starting with uppercase, continuing with lowercase - > as usual. Although I have to admit, that I'm not 100% sure about that. > The English native speakers I've talked to weren't that sure either. > Perhaps it's about consistancy ... i have here some english written books and i think all of them use capitalization of headings ... but searching on net, people claim that it depends on the purpose of the heading and the depth of it. when looking at netbeans documentation, they use capitalization in headings too. so it looks like capitalization is the preffered style, at least where i looked. anyway, i think it's up to the docs team to specify this rule for english documentation, and once done, i can adjust the documentation to the rules when i find some time. > Cheers, miroslav ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Hi Ulf, On Wed, Dec 15, 2010 at 09:14:57PM +0100, Ulf-D. Ehlert wrote: > BTW: What do the official rules say? As far as I know: Starting with uppercase, continuing with lowercase - as usual. Although I have to admit, that I'm not 100% sure about that. The English native speakers I've talked to weren't that sure either. Perhaps it's about consistancy ... 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] some docs fixes
Dne 16.12.2010 20:13, Ulf-D. Ehlert napsal(a): > Miroslav Šulc (Wednesday, 15. December 2010) >> i have 10 patches in my local git repo now fixing various problems, >> and now even in the proper format. i just did not want to spam >> bugzilla more. > Bugreports and bugfixes are obviously not spam. If you report bugs via > bugzilla you make sure that we don't forget them. :-) well, i hope you will not regret what you wrote :-P anyway, it's little bit discouraging to see no reaction for the bugs at bugzilla but i guess the docs team is busy with other things (like real life, christmas, end of year related work etc). it's understandable as this is just volunteer work, i just like to see things moving forward :-) 3) there are some inconsistencies in capitalization of chapter titles. > [...] >>> I'm not sure, too. It seems that most documentors prefer >>> capitalization... >>> >>> BTW: What do the official rules say? >> nothing as far as i can remember. but generally, chapter topic in >> english should use capitalization except words like "the", "of" >> etc. at least that is what i was taught at school long time ago. >> about image titles, i am not sure whether they should be >> considered as titles (so capitalized) or just as labels without >> capitalization. > If I remember correctly I had learned the same rule at school (also > long time ago), but meanwhile I think it depends on the weather, on > the day of the week, or on some random number... yes, it looks that way when reading the documentation, each part was written under different circumstances :-P in my opinion, all titles should be capitalized, but label of images should not. i know this is just style issue, it does not affect the quality of the content, but the documentation would definitely look more professional with these things fixed. in fact the documentation is really cool, but things like duplicated words and these style issues are little bit distracting (to me). >> well, i do not have account on git.gnome.org yet. and they say i >> should create one only if somebody tells me it's a good idea to do >> so :-) >> >> also, i spent some time today on reading how git works exactly so >> as i wrote above, i have the patches in the format-patch format >> now too. i just don't know what to do with them, did not want to >> create extra spam on bugzilla. > Using bugzilla and creating patches with "git format-patch" is a good > way to start. well, as i think of it, the best way would be to create the patches on gimp-help-2-6-0 branch (to fix current documentation) and then merge them to master branch and update them to the changes in master branch (to have the fixes at the latest changes too), but that would produce even more work (now i have 10 patches and it's sure not final number) and (afaik) i cannot do patches for merges so someone from the docs team would have to spend his/her time on this. also, i noticed that some changes in gimp-help-2-6-0 branch were not merged into master branch which might complicate the merge little bit. at least 'git log remotes/origin/master..remotes/origin/gimp-help-2-6-0' shows some commits. though when looking at it more deeply, it seems some changes from release reported as not merged are in master anyway, so maybe they were done as different commits (which is not in my opinion correct, they should be merged from the instead, this way it creates little mess with the merges). anyway, in my opinion my fixes should go both to gimp-help-2-6-0 and to master, which means i should redo the patches for gimp-help-2-6-0 and then someone with push rights should merge the commits to master (so the list of unmerged commits from branch to master does not grow) and master should be then scanned for the issues and fixed too in case some things that the patches fix would be still left there (due to changes in master). what is your opinion? and if you'd agree with this approach, how will we do that? looks like it will take some time when several people working on it. i just don't like wasting time, whether it is my time or time of somebody else :-) i was not able to make sample points > [...] >>> It works: Ctrl-click on a ruler, hold the mouse button pressed, >>> and move the pointer to the image. >> well, just tried with latest 2.7 and does not work, neither with >> mouse (that even does not catch click, weird) nor with stylus. in >> fact i am not even able to put guide on ruler that way. i must >> have something wrong in setup then. > But your mouse works, so that you can, for example, create selections > using the mouse? well, to be exact, i have laptop with synaptics touchpad and wacom tablet. as tablet gestures work weird in linux (they are not usable), i have touch features of table disabled, but still, there is some issue with loading synaptics driver for my touchpad as since i plugged the tablet, some advanced features of the touchpad (like scrolling) do not work and i did not have time to fix this yet.
Re: [Gimp-docs] some docs fixes
Miroslav Šulc (Wednesday, 15. December 2010) > i have 10 patches in my local git repo now fixing various problems, > and now even in the proper format. i just did not want to spam > bugzilla more. Bugreports and bugfixes are obviously not spam. If you report bugs via bugzilla you make sure that we don't forget them. :-) > >> 3) there are some inconsistencies in capitalization of chapter > >> titles. [...] > > I'm not sure, too. It seems that most documentors prefer > > capitalization... > > > > BTW: What do the official rules say? > > nothing as far as i can remember. but generally, chapter topic in > english should use capitalization except words like "the", "of" > etc. at least that is what i was taught at school long time ago. > about image titles, i am not sure whether they should be > considered as titles (so capitalized) or just as labels without > capitalization. If I remember correctly I had learned the same rule at school (also long time ago), but meanwhile I think it depends on the weather, on the day of the week, or on some random number... > well, i do not have account on git.gnome.org yet. and they say i > should create one only if somebody tells me it's a good idea to do > so :-) > > also, i spent some time today on reading how git works exactly so > as i wrote above, i have the patches in the format-patch format > now too. i just don't know what to do with them, did not want to > create extra spam on bugzilla. Using bugzilla and creating patches with "git format-patch" is a good way to start. > >> i was not able to make sample points [...] > > It works: Ctrl-click on a ruler, hold the mouse button pressed, > > and move the pointer to the image. > > well, just tried with latest 2.7 and does not work, neither with > mouse (that even does not catch click, weird) nor with stylus. in > fact i am not even able to put guide on ruler that way. i must > have something wrong in setup then. But your mouse works, so that you can, for example, create selections using the mouse? Bye, Ulf -- Sie vernichten Getreide - und sammeln Brot für die Welt. -- Karlheinz Deschner signature.asc Description: This is a digitally signed message part. ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
hi, thanks for response, i was already giving up :-) Dne 15.12.2010 21:14, Ulf-D. Ehlert napsal(a): > Hi Miroslav, > > Miroslav �ulc (Wednesday, 15. December 2010) >> i am reading gimp documentation to learn gimp as i am complete >> newbie with gimp. as i am skilled with coding, i also decided to >> create some patches that fix issues in the documentation like >> wording etc. as i am newbie, i do not fix any content. i already >> put 5 patches on bugzilla and have one tiny on disk yet and did >> not finish reading the documentation yet. > Yes, thank you very much. :-) I just had no time (or was too lazy?) to > apply them. i have 10 patches in my local git repo now fixing various problems, and now even in the proper format. i just did not want to spam bugzilla more. >> there are three questions that i have: >> >> 1) as i did not follow gimp documentation project at all, i am not >> sure if it is the right time to create these patches, > It's always the right time. ;-) cool :-) >> i have no >> idea whether there is an undergoing work elsewhere on preparing >> documentation for 2.8 release so my patches might not apply >> cleanly after these would be pushed into the main repo or maybe >> it's somewhere else already fixed. >> >> 2) should i also make patches that "move" documentation toward 2.8 >> release, like changes in shortcuts etc? > No, not necessary. We did not start changing docs for v2.8. well, i guess i can make them then and when the time comes, i can just send them the right way. i just do not want do duplicate someone elses work. time is precious :-) >> 3) there are some inconsistencies in capitalization of chapter >> titles. i am really not sure whether i will find some time and >> will to fix this, but if i find it, what are the rules? i noticed >> some titles do not use capitalization of following words, but on >> the other hand, titles of images are sometimes capitalized. > I'm not sure, too. It seems that most documentors prefer > capitalization... > > BTW: What do the official rules say? nothing as far as i can remember. but generally, chapter topic in english should use capitalization except words like "the", "of" etc. at least that is what i was taught at school long time ago. about image titles, i am not sure whether they should be considered as titles (so capitalized) or just as labels without capitalization. >> also, if that would be preferable for you, i am skilled enough to >> do direct commits to the git repository, though my main scm that i >> use for my daily work is mercurial (which is pretty similar to >> git). but i suppose my help would be very limited as i am not >> skilled with gimp yet and i do not plan to read the documentation >> indefinetly :-) though i could probably help with extending the >> documentation while learning using gimp, but it's just hobby for >> me and it depends on my limited free time. anyway, i have no >> problem with putting patches on bugzilla, just that i might save >> you some time by direct commits. > So you have an account for git.gnome.org? > Then I think it's ok if you commit (push) your patches. If you are not > sure about your changes, use bugzilla (best way is to create patches > with "git format-patch", but simple patches are also fine). well, i do not have account on git.gnome.org yet. and they say i should create one only if somebody tells me it's a good idea to do so :-) also, i spent some time today on reading how git works exactly so as i wrote above, i have the patches in the format-patch format now too. i just don't know what to do with them, did not want to create extra spam on bugzilla. >> also, i have one issue with understanding of documentation, the >> section about sample points. i was not able to make sample points >> work neither in gimp 2.6 nor 2.7 though i think i did it right >> (ctrl+click on ruler). anyone knows whether the documentation is >> correct and the feature does not work in gimp or there is some >> other way to make it work? > It works: Ctrl-click on a ruler, hold the mouse button pressed, and > move the pointer to the image. well, just tried with latest 2.7 and does not work, neither with mouse (that even does not catch click, weird) nor with stylus. in fact i am not even able to put guide on ruler that way. i must have something wrong in setup then. > Thank for your help, > > bye, > Ulf miroslav ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
Re: [Gimp-docs] some docs fixes
Hi Miroslav, Miroslav �ulc (Wednesday, 15. December 2010) > i am reading gimp documentation to learn gimp as i am complete > newbie with gimp. as i am skilled with coding, i also decided to > create some patches that fix issues in the documentation like > wording etc. as i am newbie, i do not fix any content. i already > put 5 patches on bugzilla and have one tiny on disk yet and did > not finish reading the documentation yet. Yes, thank you very much. :-) I just had no time (or was too lazy?) to apply them. > there are three questions that i have: > > 1) as i did not follow gimp documentation project at all, i am not > sure if it is the right time to create these patches, It's always the right time. ;-) > i have no > idea whether there is an undergoing work elsewhere on preparing > documentation for 2.8 release so my patches might not apply > cleanly after these would be pushed into the main repo or maybe > it's somewhere else already fixed. > > 2) should i also make patches that "move" documentation toward 2.8 > release, like changes in shortcuts etc? No, not necessary. We did not start changing docs for v2.8. > 3) there are some inconsistencies in capitalization of chapter > titles. i am really not sure whether i will find some time and > will to fix this, but if i find it, what are the rules? i noticed > some titles do not use capitalization of following words, but on > the other hand, titles of images are sometimes capitalized. I'm not sure, too. It seems that most documentors prefer capitalization... BTW: What do the official rules say? > also, if that would be preferable for you, i am skilled enough to > do direct commits to the git repository, though my main scm that i > use for my daily work is mercurial (which is pretty similar to > git). but i suppose my help would be very limited as i am not > skilled with gimp yet and i do not plan to read the documentation > indefinetly :-) though i could probably help with extending the > documentation while learning using gimp, but it's just hobby for > me and it depends on my limited free time. anyway, i have no > problem with putting patches on bugzilla, just that i might save > you some time by direct commits. So you have an account for git.gnome.org? Then I think it's ok if you commit (push) your patches. If you are not sure about your changes, use bugzilla (best way is to create patches with "git format-patch", but simple patches are also fine). > also, i have one issue with understanding of documentation, the > section about sample points. i was not able to make sample points > work neither in gimp 2.6 nor 2.7 though i think i did it right > (ctrl+click on ruler). anyone knows whether the documentation is > correct and the feature does not work in gimp or there is some > other way to make it work? It works: Ctrl-click on a ruler, hold the mouse button pressed, and move the pointer to the image. Thank for your help, bye, Ulf -- Kein größeres Verbrechen als Gleichgültigkeit. Gleichgültigsein heißt unablässig morden. -- Karlheinz Deschner signature.asc Description: This is a digitally signed message part. ___ Gimp-docs mailing list Gimp-docs@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-docs
