From: <ben...@ug...> - 2007-01-29 23:38:33
|
Hi, the documentation section on gramps-project with manual was outdated: http://gramps-project.org/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=7&MMN_position=15:2 I linked to the new place where the manual can be found. I would delete the legacy section with the old manual, tar files and pdf files, and delete those on the server to. Is there a reason not to do this? Does somebody use these old manuals? Of course, new manual is only in english, so we loose the french version. However, for the other languages, a manual online has never be offered, so why treat french differently? Other options? Benny ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Alex R. <sh...@gr...> - 2007-01-30 00:09:00
|
On Tue, 2007-01-30 at 00:38 +0100, ben...@ug... wrote: > I would delete the legacy section with the old manual, tar files and pdf = files, > and delete those on the server to. Is there a reason not to do this? Does > somebody use these old manuals? >=20 > Of course, new manual is only in english, so we loose the french version. > However, for the other languages, a manual online has never be offered, s= o why > treat french differently? >=20 > Other options? Sure. We can regenerate manuals for the languages that have manual translations. For those we could post HTML and pdf just like it is used to be. It would be French, Dutch, Norwegian, and Slovak at this point. Alex --=20 Alexander Roitman http://www.gramps-project.org |
From: <ben...@ug...> - 2007-01-30 09:08:01
|
Quoting Alex Roitman <sh...@gr...>: >> Other options? > > Sure. We can regenerate manuals for the languages that have > manual translations. For those we could post HTML and pdf > just like it is used to be. It would be French, Dutch, > Norwegian, and Slovak at this point. > > Alex Ok, somebody must generate this who has access to the website to ftp it. You probably did this before Alex. Could you on devel wiki quickly list the steps needed to make the different files we upload? (so html, pdf in a4 and letter?). It would save me a lot of trial and error. I could then do this, and should in the future I have no time, somebody else can easily take over following the wiki. Benny ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: <ben...@ug...> - 2007-01-31 09:43:37
|
Hi, I did not succeed yet in converting the docbook manuals to html and pdf to publish on the website. Many deprecated programs, convoluted manuals, ... The internet can be a real jungle to find information sometimes. It appears I will have to read: http://sagehill.net/docbookxsl/index.html, so for pdf: http://sagehill.net/docbookxsl/PrintOutput.html and for html: http://sagehill.net/docbookxsl/HtmlOutput.html Should somebody have experience with these tools and be able to give the correct/best options, please let me know before I finished reading this and did numerous tests. Benny Quoting ben...@ug...: > Quoting Alex Roitman <sh...@gr...>: > > >>> Other options? >> >> Sure. We can regenerate manuals for the languages that have >> manual translations. For those we could post HTML and pdf >> just like it is used to be. It would be French, Dutch, >> Norwegian, and Slovak at this point. >> >> Alex > > Ok, somebody must generate this who has access to the website to ftp it. > You probably did this before Alex. Could you on devel wiki quickly list the > steps needed to make the different files we upload? (so html, pdf in a4 and > letter?). It would save me a lot of trial and error. > > I could then do this, and should in the future I have no time, somebody > else can > easily take over following the wiki. > > Benny > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Alexandre P. <ale...@gm...> - 2007-01-31 09:52:49
|
On 1/31/07, benny.malengier wrote: > I did not succeed yet in converting the docbook manuals to html and pdf to > publish on the website. Many deprecated programs, convoluted manuals, ... The > internet can be a real jungle to find information sometimes. > > It appears I will have to read: http://sagehill.net/docbookxsl/index.html, so > for pdf: http://sagehill.net/docbookxsl/PrintOutput.html and for html: > http://sagehill.net/docbookxsl/HtmlOutput.html > > Should somebody have experience with these tools and be able to give the > correct/best options, please let me know before I finished reading this > and did > numerous tests. 1. I'm doing my best to understand why we are discussing moving to some moinmoin wiki that doesn't even support inline graphics, when we have mediawiki and a working mediawiki2docbook bridge thanks to Dominic Mazzoni of Audacity team :) 2. 'xsltproc -o index.html /usr/share/xml/docbook/stylesheet/nwalsh/1.71.1/html/chunk.xsl manual.xml' should work for you. Alexandre |
From: <ben...@ug...> - 2007-01-31 10:28:45
|
Quoting Alexandre Prokoudine <ale...@gm...>: > > 1. I'm doing my best to understand why we are discussing moving to > some moinmoin wiki that doesn't even support inline graphics, when we > have mediawiki and a working mediawiki2docbook bridge thanks to > Dominic Mazzoni of Audacity team :) Alexandre, the problem is not so much the export of wiki to docbook. And anyway, this is possible today from within a moinmoin wiki (see eg openoffice, http://www.ooowiki.de/Writer2LaTeX, select action render as docbook, open the source if it opens in the browser, save the source as test.xml, and call up yelp test.xml, this looks just fine, yes the pictures are not present, but if you look in the xml, the imagedata tag is there, so having the correct directories would make this work with image) Anyway, the problem is import into wiki, so the present manual must not be rewritten. I also don't find good information on the web about this mediawiki2docbook, do you have some pointers? > > 2. 'xsltproc -o index.html > /usr/share/xml/docbook/stylesheet/nwalsh/1.71.1/html/chunk.xsl > manual.xml' should work for you. thanks, I'll do this. I'll also try Jerome's command. Benny ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: <rom...@ya...> - 2007-01-31 10:52:24
|
> thanks, I'll do this. I'll also try Jerome's command. I didn't try with last header http://www.w3.org/TR/2006/REC-xsl11-20061205/ or last libraries http://ftp.gnome.org/pub/GNOME/sources/libxslt/1.1/ ben...@ug... a écrit : > Quoting Alexandre Prokoudine <ale...@gm...>: > >> 1. I'm doing my best to understand why we are discussing moving to >> some moinmoin wiki that doesn't even support inline graphics, when we >> have mediawiki and a working mediawiki2docbook bridge thanks to >> Dominic Mazzoni of Audacity team :) > > Alexandre, the problem is not so much the export of wiki to docbook. > And anyway, > this is possible today from within a moinmoin wiki (see eg openoffice, > http://www.ooowiki.de/Writer2LaTeX, select action render as docbook, open the > source if it opens in the browser, save the source as test.xml, and call up > yelp test.xml, this looks just fine, yes the pictures are not present, but if > you look in the xml, the imagedata tag is there, so having the correct > directories would make this work with image) > > Anyway, the problem is import into wiki, so the present manual must not be > rewritten. > > I also don't find good information on the web about this mediawiki2docbook, do > you have some pointers? > >> 2. 'xsltproc -o index.html >> /usr/share/xml/docbook/stylesheet/nwalsh/1.71.1/html/chunk.xsl >> manual.xml' should work for you. > > thanks, I'll do this. I'll also try Jerome's command. > > Benny > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > ___________________________________________________________________________ Yahoo! Mail rvente le mail ! Duvrez le nouveau Yahoo! Mail et son interface rlutionnaire. http://fr.mail.yahoo.com |
From: <ben...@ug...> - 2007-02-01 23:23:16
|
Hi, I updated the manuals on the website, see http://gramps-project.org/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=7&MMN_position=15:2 I documented how these documents are obtained, and made a python script that does all the work, see http://developers.gramps-project.org/tiki-index.php?page=ManualGeneration What I noted: 1/Many of the pictures come out all bad in the pdf, as the pdf does not appear to do scaling of the png's. I notice the english text is very descent. I suggest French, Dutch and SLovak translator have a look, and clean up their screenshots so they have a good resolution for html and pdf, without becoming too large. I suggest one of you or Alex/Don who made english manual, makes a wiki entry to document how screenshots are best taken so they are uniform over the translations. Perhaps Don, you should say max size/resolution for figures? 2/Slovak pdf is full of # instead of certain accents. I have no real time nor incentive to investigate if this can be resolved. Perhaps the slovak translator can have a look? Html looks fine. 3/Norwegian is not included as it is all still in english :-) 4/English is now kept double on the website: once for the F1 key in GRAMPS (which I suppose supports versions of the manual??) and once due to what I did above. I suppose my english manual is at the moment the most current one. 5/This is 27.2 Mb, and uploading takes for ages from Europe (sometimes 10bit/s!!). I do therefore not intend to do this often. I suggest the translators notify me if much has changed. Benny ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: <rom...@ya...> - 2007-02-01 23:48:55
|
Benny, >> 1/Many of the pictures come out all bad in the pdf, as the pdf does not appear >> to do scaling of the png's. I notice the english text is very descent. I >> suggest French, Dutch and SLovak translator have a look, and clean up their >> screenshots so they have a good resolution for html and pdf, without becoming >> too large. I suggest one of you or Alex/Don who made english manual, makes a >> wiki entry to document how screenshots are best taken so they are uniform over >> the translations. >> Perhaps Don, you should say max size/resolution for figures? Already exist !!! http://developers.gramps-project.org/tiki-index.php?page=TranslatingDocs > It is nice if the translated manual has figures showing the translated version of GRAMPS. > > * If you can provide figures on your own this is great. Stick them under help/xx/figures (xx is your language code). Bear in mind that screenshots have to be *indexed PNGs, not more than 510 pixels wide*, in order to satisfy the GNOME Documentation Style Guide, see http://developer.gnome.org/documents/style-guide/c3728.html for the details. > * If it's too much trouble for you, just let know and somebody else will do it for you. Fortunately, one does not have to speak the language to make screenshots :-) But sometimes, this could be a nightmare ... I cannot generate nice width:500px figures with my distribution/desktop !!! http://bugs.gramps-project.org/view.php?id=522 ben...@ug... a écrit : > Hi, > > I updated the manuals on the website, see > http://gramps-project.org/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=7&MMN_position=15:2 > > I documented how these documents are obtained, and made a python script that > does all the work, see > http://developers.gramps-project.org/tiki-index.php?page=ManualGeneration > > What I noted: > > 1/Many of the pictures come out all bad in the pdf, as the pdf does not appear > to do scaling of the png's. I notice the english text is very descent. I > suggest French, Dutch and SLovak translator have a look, and clean up their > screenshots so they have a good resolution for html and pdf, without becoming > too large. I suggest one of you or Alex/Don who made english manual, makes a > wiki entry to document how screenshots are best taken so they are uniform over > the translations. > Perhaps Don, you should say max size/resolution for figures? > > 2/Slovak pdf is full of # instead of certain accents. I have no real time nor > incentive to investigate if this can be resolved. Perhaps the slovak > translator > can have a look? Html looks fine. > > 3/Norwegian is not included as it is all still in english :-) > > 4/English is now kept double on the website: once for the F1 key in GRAMPS > (which I suppose supports versions of the manual??) and once due to what I did > above. I suppose my english manual is at the moment the most current one. > > 5/This is 27.2 Mb, and uploading takes for ages from Europe (sometimes > 10bit/s!!). I do therefore not intend to do this often. I suggest the > translators notify me if much has changed. > > Benny ___________________________________________________________________________ Yahoo! Mail rvente le mail ! Duvrez le nouveau Yahoo! Mail et son interface rlutionnaire. http://fr.mail.yahoo.com |
From: Alex R. <sh...@gr...> - 2007-02-02 00:02:11
|
On Fri, 2007-02-02 at 00:53 +0100, J=C3=A9r=C3=B4me wrote: > Already exist !!! > http://developers.gramps-project.org/tiki-index.php?page=3DTranslatingDoc= s I just updated that page: we're now fully switched to the po-way and this is now reflected in the wiki. > But sometimes, this could be a nightmare ... > I cannot generate nice width:500px figures with my distribution/desktop=20 > !!! http://bugs.gramps-project.org/view.php?id=3D522 Well, you have to. Either scale it down or cut out a portion. There's no way around this. Nobody said this should be easy :-) Alex --=20 Alexander Roitman http://www.gramps-project.org |
From: <rom...@ya...> - 2007-02-02 00:26:35
|
> Well, you have to. Either scale it down or cut out a portion. :-D > There's no way around this. Nobody said this should be easy :-) I force dialog width (gconf) but after clicking I should remake it :( or/and sometimes I must remove text on tool bar !!! http://gramps-project.org/grampsmanuals/gramps-manual-fr/figures/family.png Otherwise, scale/resize after making a screenshot may "pixellized" figures :( => I will not be able to join specification ... Alex Roitman a écrit : > On Fri, 2007-02-02 at 00:53 +0100, Jérôme wrote: >> Already exist !!! >> http://developers.gramps-project.org/tiki-index.php?page=TranslatingDocs > > I just updated that page: we're now fully switched to the po-way > and this is now reflected in the wiki. > >> But sometimes, this could be a nightmare ... >> I cannot generate nice width:500px figures with my distribution/desktop >> !!! http://bugs.gramps-project.org/view.php?id=522 > > Well, you have to. Either scale it down or cut out a portion. > There's no way around this. Nobody said this should be easy :-) > > Alex > -- Jérôme Rapinat ___________________________________________________________________________ Yahoo! Mail rvente le mail ! Duvrez le nouveau Yahoo! Mail et son interface rlutionnaire. http://fr.mail.yahoo.com |
From: Don A. <don...@co...> - 2007-02-02 00:32:51
|
I just use GIMP to screen capture a window, then scale it appropriately. Don On Thu, 2007-02-01 at 16:01 -0800, Alex Roitman wrote: > On Fri, 2007-02-02 at 00:53 +0100, J=C3=A9r=C3=B4me wrote: > > But sometimes, this could be a nightmare ... > > I cannot generate nice width:500px figures with my distribution/desktop= =20 > > !!! http://bugs.gramps-project.org/view.php?id=3D522 >=20 > Well, you have to. Either scale it down or cut out a portion. > There's no way around this. Nobody said this should be easy :-) >=20 > Alex >=20 > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job ea= sier. > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim= o > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ Gramps-devel mailing list= Gra...@li... https://lists.sourceforge.net/lists/lis= tinfo/gramps-devel |
From: Alex R. <sh...@gr...> - 2007-02-02 00:03:48
|
On Fri, 2007-02-02 at 00:22 +0100, ben...@ug... wrote: > I updated the manuals on the website, see > http://gramps-project.org/index.php?module=3Dpagemaster&PAGE_user_op=3Dvi= ew_page&PAGE_id=3D7&MMN_position=3D15:2 Cool! Should we move these to where the gramps help looks if the local manual cannot be shown? I would think so. > 4/English is now kept double on the website: once for the F1 key in GRAMP= S > (which I suppose supports versions of the manual??) and once due to what = I did > above. I suppose my english manual is at the moment the most current one. I think we should use your manual as the manual :-) There's no point to keep the second version that is obsolete and not translated. Alex --=20 Alexander Roitman http://www.gramps-project.org |
From: Alexandre P. <ale...@gm...> - 2007-02-02 12:54:11
|
On 1/31/07, benny.malengier wrote: > Alexandre, the problem is not so much the export of wiki to docbook. > And anyway, > this is possible today from within a moinmoin wiki (see eg openoffice, > http://www.ooowiki.de/Writer2LaTeX, select action render as docbook, open the > source if it opens in the browser, save the source as test.xml, and call up > yelp test.xml, this looks just fine, yes the pictures are not present, but if > you look in the xml, the imagedata tag is there, so having the correct > directories would make this work with image) > > Anyway, the problem is import into wiki, so the present manual must not be > rewritten. > > I also don't find good information on the web about this mediawiki2docbook, do > you have some pointers? I'll talk to Dominic about details :) My mistake was that I didn't follow the list closely last couple of months and I thought you knew about this work. As for downscaling screenshots, I looked at the Figure 2.8 you mentioned and it looks like it was scaled using linear interpolation and not sharpened. There are several ways to make downscaled image look better. 1. Filter -> Enhance -> Unsharp mask (play with values to find which one is best) 2. Filter -> Enhance -> Sharpen (use value of 25-35) You can also use Dilate filter before sharpening. That will improve quality too. I wouldn't recommend tracing for screenshots. Alexandre |
From: <ben...@ug...> - 2007-02-02 13:21:48
|
Hi again, I looked at media.png in english version and in dutch version. Both look the same in GIMP, have same size and almost same resolution. Yet in english version the picture is nice in pdf, and in dutch version it is stretched and looks therefore ugly. Hence, the error is not in the screenshots, but in the pdf generation. I suggest the translators follow the instructions on http://developers.gramps-project.org/tiki-index.php?page=ManualGeneration and make themselves a pdf and try some things, investigate the output on specific error messages (you see a lot of those!). Some things I can think of: 1/some figures are missing: for figures you do not have a screenshot for, use the english version! It is better that users see in yelp, html, pdf an english example than no example, and perhaps it creates issues in pdf generation 2/in english, all png's are bit depth 24bbp, and color RGB, whereas in dutch, some figures are 32bbp and color RGB/alpha, eg first-open.png, perhaps the pdf creator has problems with that? 3/google for this issue with the fop program, perhaps see if another xsl solves the issue. There are a lot of options to find the cause of this, but they take some work. Eg you could make a figures and figures-nl dir, copy in figures all english figures, and one by one use the dutch figures, hunting down where the bug in pdf creation occurs. Benny ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: <rom...@ya...> - 2007-01-31 09:54:11
|
> Should somebody have experience with these tools and be able to give the > correct/best options, please let me know before I finished reading this and did numerous tests. Try xsltproc parser http://bugs.gramps-project.org/view.php?id=504 Also, I modify basic.py (a template coming with libxsl package) for parsing xml/xsl with a (basic) python module ... ben...@ug... a écrit : > Hi, > > I did not succeed yet in converting the docbook manuals to html and pdf to > publish on the website. Many deprecated programs, convoluted manuals, ... The > internet can be a real jungle to find information sometimes. > > It appears I will have to read: http://sagehill.net/docbookxsl/index.html, so > for pdf: http://sagehill.net/docbookxsl/PrintOutput.html and for html: > http://sagehill.net/docbookxsl/HtmlOutput.html > > Should somebody have experience with these tools and be able to give the > correct/best options, please let me know before I finished reading this > and did > numerous tests. > > Benny > > Quoting ben...@ug...: > >> Quoting Alex Roitman <sh...@gr...>: >> >> >>>> Other options? >>> Sure. We can regenerate manuals for the languages that have >>> manual translations. For those we could post HTML and pdf >>> just like it is used to be. It would be French, Dutch, >>> Norwegian, and Slovak at this point. >>> >>> Alex >> Ok, somebody must generate this who has access to the website to ftp it. >> You probably did this before Alex. Could you on devel wiki quickly list the >> steps needed to make the different files we upload? (so html, pdf in a4 and >> letter?). It would save me a lot of trial and error. >> >> I could then do this, and should in the future I have no time, somebody >> else can >> easily take over following the wiki. >> >> Benny >> >> >> ---------------------------------------------------------------- >> This message was sent using IMP, the Internet Messaging Program. >> >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share your >> opinions on IT & business topics through brief surveys - and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Gramps-devel mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel >> > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > -- Jérôme Rapinat ___________________________________________________________________________ Yahoo! Mail rvente le mail ! Duvrez le nouveau Yahoo! Mail et son interface rlutionnaire. http://fr.mail.yahoo.com |
From: <ben...@ug...> - 2007-02-02 07:54:23
|
Yes Jerome, I do not understand what gconf is needed for. I take screenshots with GIMP or ksnapshot, and scale it in GIMP. If you figure out an easy way/what settings are exactly right for inclusion= in the manual, or you can make an imagemagick script that does it automaticall= y, share it :-) Benny Quoting Don Allingham <don...@co...>: > I just use GIMP to screen capture a window, then scale it appropriately. > > Don > > On Thu, 2007-02-01 at 16:01 -0800, Alex Roitman wrote: >> On Fri, 2007-02-02 at 00:53 +0100, J=C3=A9r=C3=B4me wrote: >> > But sometimes, this could be a nightmare ... >> > I cannot generate nice width:500px figures with my distribution/deskto= p >> > !!! http://bugs.gramps-project.org/view.php?id=3D522 >> >> Well, you have to. Either scale it down or cut out a portion. >> There's no way around this. Nobody said this should be easy :-) >> >> Alex >> >> ------------------------------------------------------------------------= - >> Using Tomcat but need to do more? Need to support web services, security= ? >> Get stuff done quickly with pre-integrated technology to make your >> job easier. >> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geroni= mo >> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 >> _______________________________________________ Gramps-devel mailing >> list Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-devel > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: <rom...@ya...> - 2007-02-02 10:16:29
|
> I do not understand what gconf is needed for. GRAMPS have gconf options for dialog size. Do not need to scale/resize with 500px dialog ;) > If you figure out an easy way/what settings are exactly right for inclusion in the manual, or you can make an imagemagick script that does it automatically, share it :-) Scale bitmaps will evaluate a rate of pixels :( I should take screenshots, save as SVG or EPS, scale and save into indexed png ... Seems thats GIMP and imagemagick may use SVG, I will try !!! ben...@ug... a écrit : > Yes Jerome, > > I do not understand what gconf is needed for. > I take screenshots with GIMP or ksnapshot, and scale it in GIMP. > > If you figure out an easy way/what settings are exactly right for > inclusion in > the manual, or you can make an imagemagick script that does it > automatically, > share it :-) > > Benny > > Quoting Don Allingham <don...@co...>: > >> I just use GIMP to screen capture a window, then scale it appropriately. >> >> Don >> >> On Thu, 2007-02-01 at 16:01 -0800, Alex Roitman wrote: >>> On Fri, 2007-02-02 at 00:53 +0100, Jérôme wrote: >>> > But sometimes, this could be a nightmare ... >>> > I cannot generate nice width:500px figures with my >>> distribution/desktop >>> > !!! http://bugs.gramps-project.org/view.php?id=522 >>> >>> Well, you have to. Either scale it down or cut out a portion. >>> There's no way around this. Nobody said this should be easy :-) >>> >>> Alex ___________________________________________________________________________ Yahoo! Mail rvente le mail ! Duvrez le nouveau Yahoo! Mail et son interface rlutionnaire. http://fr.mail.yahoo.com |
From: <rom...@ya...> - 2007-02-02 11:15:57
|
Benny, > If you figure out an easy way/what settings are exactly right for inclusion in the manual, or you can make an imagemagick script that does it automatically, share it :-) maybe I am too lazy to learn and too obstinate for scaling screenshots :( I will keep in mind : chain SVG->png ... I find something (need Zenity, Inkscape) http://yeknan.free.fr/blog/fichiers/nautilus-actions/svg2png.schemas http://yeknan.free.fr/blog/fichiers/nautilus-actions/svg2png but with the last news nobody can make captures into vectorial :-D :( Maybe I will make a Autotrace/Potrace script, scale/resize, then associate with svg2png to have my final screenshots ... Jérôme a écrit : >> I do not understand what gconf is needed for. > > GRAMPS have gconf options for dialog size. Do not need to scale/resize > with 500px dialog ;) > >> If you figure out an easy way/what settings are exactly right for >> inclusion in the manual, or you can make an imagemagick script that >> does it automatically, share it :-) > > Scale bitmaps will evaluate a rate of pixels :( > > I should take screenshots, save as SVG or EPS, scale and save into > indexed png ... > Seems thats GIMP and imagemagick may use SVG, I will try !!! > > > > ben...@ug... a écrit : >> Yes Jerome, >> >> I do not understand what gconf is needed for. >> I take screenshots with GIMP or ksnapshot, and scale it in GIMP. >> >> If you figure out an easy way/what settings are exactly right for >> inclusion in >> the manual, or you can make an imagemagick script that does it >> automatically, >> share it :-) >> >> Benny >> >> Quoting Don Allingham <don...@co...>: >> >>> I just use GIMP to screen capture a window, then scale it appropriately. >>> >>> Don >>> >>> On Thu, 2007-02-01 at 16:01 -0800, Alex Roitman wrote: >>>> On Fri, 2007-02-02 at 00:53 +0100, Jérôme wrote: >>>> > But sometimes, this could be a nightmare ... >>>> > I cannot generate nice width:500px figures with my >>>> distribution/desktop >>>> > !!! http://bugs.gramps-project.org/view.php?id=522 >>>> >>>> Well, you have to. Either scale it down or cut out a portion. >>>> There's no way around this. Nobody said this should be easy :-) >>>> >>>> Alex > > > > > > ___________________________________________________________________________ > Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son > interface r�volutionnaire. > http://fr.mail.yahoo.com > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier. > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > > ------------------------------------------------------------------------ > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel -- Jérôme Rapinat ___________________________________________________________________________ Yahoo! Mail rvente le mail ! Duvrez le nouveau Yahoo! Mail et son interface rlutionnaire. http://fr.mail.yahoo.com |
From: <rom...@ya...> - 2007-02-02 14:52:47
|
Benny, > If you figure out an easy way/what settings are exactly right for inclusion in the manual, or you can make an imagemagick script that does it automatically, share it :-) sed 's/format="PNG"/scale="500px" format="PNG"/' ./gramps.xml > scaled.xml Now all figures will be validated by GNOME-doc spec (less than 510px), maybe it will be more easy to generate A4 pdf but with this screenshots, GRAMPS looks like an old X program :( OK I -> [] (pack up and go) Seriously, we cannot swith under pdf (vectorial) without loss. > and make themselves a pdf and try some things, investigate the output on specific error messages (you see a lot of those!) Do you need A4 letter pdf ? > perhaps see if another xsl solves the issue. I don't know FOP, maybe in this case, OpenOffice might produce better pdf ? Using one HTML file into OpenOffice. ben...@ug... a écrit : > Yes Jerome, > > I do not understand what gconf is needed for. > I take screenshots with GIMP or ksnapshot, and scale it in GIMP. > > If you figure out an easy way/what settings are exactly right for > inclusion in > the manual, or you can make an imagemagick script that does it > automatically, > share it :-) > > Benny > > Quoting Don Allingham <don...@co...>: > >> I just use GIMP to screen capture a window, then scale it appropriately. >> >> Don >> >> On Thu, 2007-02-01 at 16:01 -0800, Alex Roitman wrote: >>> On Fri, 2007-02-02 at 00:53 +0100, Jérôme wrote: >>> > But sometimes, this could be a nightmare ... >>> > I cannot generate nice width:500px figures with my >>> distribution/desktop >>> > !!! http://bugs.gramps-project.org/view.php?id=522 >>> >>> Well, you have to. Either scale it down or cut out a portion. >>> There's no way around this. Nobody said this should be easy :-) >>> >>> Alex ___________________________________________________________________________ Yahoo! Mail rvente le mail ! Duvrez le nouveau Yahoo! Mail et son interface rlutionnaire. http://fr.mail.yahoo.com |
From: Alex R. <sh...@gr...> - 2007-02-02 16:31:12
|
Benny, On Fri, 2007-02-02 at 08:54 +0100, ben...@ug... wrote: > If you figure out an easy way/what settings are exactly right for inclusi= on in > the manual, Indexed PNG, not wider than 510 pixels. In my experience, the best thing is to first rescale, than convert to indexed: Image->Mode->Indexed in GIMP and then select None for color dithering (bottom menu) Alex --=20 Alexander Roitman http://www.gramps-project.org |
From: Eero T. <ee...@us...> - 2007-02-02 20:26:47
|
Hi, On Friday 02 February 2007 18:30, Alex Roitman wrote: > > If you figure out an easy way/what settings are exactly right for > > inclusion in the manual, > > Indexed PNG, not wider than 510 pixels. > In my experience, the best thing is to first rescale, > than convert to indexed: > Image->Mode->Indexed in GIMP > and then select None for color dithering (bottom menu) I find it easiest to use ImageMagick tools: import -colors 256 -depth 8 shot.png And then click onto the window of which contents I want screenshot from. If you want also the window border, add option: -frame Note that this takes snapshot of a rectangular area occupied by the window borders, so with shaped windows it gets also some pixels from the background. In this case it's best to take snapshots with a single color background (you could have one virtual desktop for that purpose ;-)). If you want the shot at certain size, add as a first option something like: -resize '500x400' This will set the width to 500 and the height will be something that keeps the original image ratio. If I want to force the size to be exactly what I gave, I add '!' after the height: -resize '500x400!' If you want to add a border around the image, you could add as last options something like: -bordercolor gray -border 4x4 This is will increase the image size, not overwrite the image content. ImageMagick provides also options for image operations like sharpening, de-speckling etc. (see "man convert" for more info). - Eero "UI tools are so slow and inconvenient" |
From: <rom...@ya...> - 2007-02-03 09:31:01
|
> 2/in english, all png's are bit depth 24bbp, and color RGB, whereas in dutch, > some figures are 32bbp and color RGB/alpha, eg first-open.png, perhaps the pdf > creator has problems with that? And seems to me that english figures have better resolutions : 129-99ppp/dpi (mix between most "home" printers and screen) Most Dutch, French figures have 72ppp/dpi resolution (=do not allow nice print, but good enough for displaying on screen) Changing screenshots resolution on GIMP preferences : (View->get resolution) Otherwise, indexed reduce number of colors: 255 (without alpha) = a size optimization nl (48 files : 2.3Mo) en (57 files : 2.5Mo) fr (56 files : 1005.3Ko) > In my experience, the best thing is to first rescale, > than convert to indexed: > Image->Mode->Indexed in GIMP > and then select None for color dithering (bottom menu) must be the last step ... I must take new screenshots :( Print or screen optimization ? ben...@ug... a écrit : > Hi again, > > I looked at media.png in english version and in dutch version. Both look the > same in GIMP, have same size and almost same resolution. > > Yet in english version the picture is nice in pdf, and in dutch version it is > stretched and looks therefore ugly. > > Hence, the error is not in the screenshots, but in the pdf generation. > I suggest the translators follow the instructions on > http://developers.gramps-project.org/tiki-index.php?page=ManualGeneration and > make themselves a pdf and try some things, investigate the output on specific > error messages (you see a lot of those!). > > Some things I can think of: > 1/some figures are missing: for figures you do not have a screenshot for, use > the english version! It is better that users see in yelp, html, pdf an english > example than no example, and perhaps it creates issues in pdf generation > 2/in english, all png's are bit depth 24bbp, and color RGB, whereas in dutch, > some figures are 32bbp and color RGB/alpha, eg first-open.png, perhaps the pdf > creator has problems with that? > 3/google for this issue with the fop program, perhaps see if another > xsl solves > the issue. > > There are a lot of options to find the cause of this, but they take some work. > Eg you could make a figures and figures-nl dir, copy in figures all english > figures, and one by one use the dutch figures, hunting down where the bug in > pdf creation occurs. > > Benny ___________________________________________________________________________ Yahoo! Mail rvente le mail ! Duvrez le nouveau Yahoo! Mail et son interface rlutionnaire. http://fr.mail.yahoo.com |
From: <ben...@ug...> - 2007-02-03 09:58:28
|
Yes, this is the solution Jerome! The english pictures are double the resolution of french and dutch pictures= . If you go on the pictures in gimp, and open the info window (menu view) you see eg on first-open.png: dutch: dim 640x408, print size 9.27 x 5.9 inches, res: 69 x 69 dpi english: dim 640x409, print size 4.96 x 3.2 inches, res: 129x 126dp For the pdf manual, the print size is used, no scaling is applied apparentl= y. So, all screenshots in french, dutch should be made so that print size in g= imp info view shows a reasonable size. Note that slovak manual looks ok with 75dpi, eg first-open.png there has dim 500x300, print size 6.6 x 4 inches, res: 75 x 75 dpi A4 (210 =C3=97 297 mm or 8.3 =C3=97 11.7 inches So, please, redo the screenshots, and aim for a print size of 5 inches wide, if you want the pdf manual to have good pictures. Benny Quoting J=C3=A9r=C3=B4me <rom...@ya...>: >> 2/in english, all png's are bit depth 24bbp, and color RGB, whereas >> in dutch, >> some figures are 32bbp and color RGB/alpha, eg first-open.png, >> perhaps the pdf >> creator has problems with that? > > And seems to me that english figures have better resolutions : > 129-99ppp/dpi (mix between most "home" printers and screen) > Most Dutch, French figures have 72ppp/dpi resolution (=3Ddo not allow > nice print, but good enough for displaying on screen) > Changing screenshots resolution on GIMP preferences : > (View->get resolution) > > Otherwise, indexed reduce number of colors: > 255 (without alpha) =3D a size optimization > nl (48 files : 2.3Mo) > en (57 files : 2.5Mo) > fr (56 files : 1005.3Ko) > >> In my experience, the best thing is to first rescale, >> than convert to indexed: >> Image->Mode->Indexed in GIMP >> and then select None for color dithering (bottom menu) > > must be the last step ... I must take new screenshots :( > > Print or screen optimization ? > > > > > ben...@ug... a =C3=A9crit : >> Hi again, >> >> I looked at media.png in english version and in dutch version. Both look= the >> same in GIMP, have same size and almost same resolution. >> >> Yet in english version the picture is nice in pdf, and in dutch >> version it is >> stretched and looks therefore ugly. >> >> Hence, the error is not in the screenshots, but in the pdf generation. >> I suggest the translators follow the instructions on >> http://developers.gramps-project.org/tiki-index.php?page=3DManualGenerat= ion >> and >> make themselves a pdf and try some things, investigate the output on >> specific >> error messages (you see a lot of those!). >> >> Some things I can think of: >> 1/some figures are missing: for figures you do not have a screenshot >> for, use >> the english version! It is better that users see in yelp, html, pdf >> an english >> example than no example, and perhaps it creates issues in pdf generation >> 2/in english, all png's are bit depth 24bbp, and color RGB, whereas >> in dutch, >> some figures are 32bbp and color RGB/alpha, eg first-open.png, >> perhaps the pdf >> creator has problems with that? >> 3/google for this issue with the fop program, perhaps see if another >> xsl solves >> the issue. >> >> There are a lot of options to find the cause of this, but they take >> some work. >> Eg you could make a figures and figures-nl dir, copy in figures all engl= ish >> figures, and one by one use the dutch figures, hunting down where the bu= g in >> pdf creation occurs. >> >> Benny > > > > > > _________________________________________________________________________= __ > Yahoo! Mail r=EF=BF=BDnvente le mail ! D=EF=BF=BDouvrez le nouveau Yahoo!= Mail et > son interface r=EF=BF=BDolutionnaire. > http://fr.mail.yahoo.com > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: <ben...@ug...> - 2007-02-03 21:45:22
|
To close this thread, I have updated http://developers.gramps-project.org/tiki-index.php?page=3DTranslatingDocs = with a command to create the screenshot: import -quality 100 -trim -delay 200 -resize 500 -density 100x100 -frame -channel RGB -depth 8 screenshot.png On my system that works fine, you might need to tweak some things on differ= ent systems. If Jerome and Erik give me notification the screenshots are rescal= ed to a resolution that is ok with pdf manual, I'll recreate them and upload t= o g-p.org. Benny Quoting ben...@ug...: > Yes, this is the solution Jerome! > > The english pictures are double the resolution of french and dutch pictur= es. > > If you go on the pictures in gimp, and open the info window (menu view) > you see > eg on first-open.png: > dutch: dim 640x408, print size 9.27 x 5.9 inches, res: 69 x 69 dpi > english: dim 640x409, print size 4.96 x 3.2 inches, res: 129x 126dp > > For the pdf manual, the print size is used, no scaling is applied apparen= tly. > So, all screenshots in french, dutch should be made so that print > size in gimp > info view shows a reasonable size. > > Note that slovak manual looks ok with 75dpi, eg first-open.png there has > dim 500x300, print size 6.6 x 4 inches, res: 75 x 75 dpi > > A4 (210 =C3=97 297 mm or 8.3 =C3=97 11.7 inches > So, please, redo the screenshots, and aim for a print size of 5 inches > wide, if > you want the pdf manual to have good pictures. > > > Benny > > > > Quoting J=C3=A9r=C3=B4me <rom...@ya...>: > >>> 2/in english, all png's are bit depth 24bbp, and color RGB, whereas >>> in dutch, >>> some figures are 32bbp and color RGB/alpha, eg first-open.png, >>> perhaps the pdf >>> creator has problems with that? >> >> And seems to me that english figures have better resolutions : >> 129-99ppp/dpi (mix between most "home" printers and screen) >> Most Dutch, French figures have 72ppp/dpi resolution (=3Ddo not allow >> nice print, but good enough for displaying on screen) >> Changing screenshots resolution on GIMP preferences : >> (View->get resolution) >> >> Otherwise, indexed reduce number of colors: >> 255 (without alpha) =3D a size optimization >> nl (48 files : 2.3Mo) >> en (57 files : 2.5Mo) >> fr (56 files : 1005.3Ko) >> >>> In my experience, the best thing is to first rescale, >>> than convert to indexed: >>> Image->Mode->Indexed in GIMP >>> and then select None for color dithering (bottom menu) >> >> must be the last step ... I must take new screenshots :( >> >> Print or screen optimization ? >> >> >> >> >> ben...@ug... a =C3=A9crit : >>> Hi again, >>> >>> I looked at media.png in english version and in dutch version. Both >>> look the >>> same in GIMP, have same size and almost same resolution. >>> >>> Yet in english version the picture is nice in pdf, and in dutch >>> version it is >>> stretched and looks therefore ugly. >>> >>> Hence, the error is not in the screenshots, but in the pdf generation. >>> I suggest the translators follow the instructions on >>> http://developers.gramps-project.org/tiki-index.php?page=3DManualGenera= tion >>> and >>> make themselves a pdf and try some things, investigate the output on >>> specific >>> error messages (you see a lot of those!). >>> >>> Some things I can think of: >>> 1/some figures are missing: for figures you do not have a screenshot >>> for, use >>> the english version! It is better that users see in yelp, html, pdf >>> an english >>> example than no example, and perhaps it creates issues in pdf generatio= n >>> 2/in english, all png's are bit depth 24bbp, and color RGB, whereas >>> in dutch, >>> some figures are 32bbp and color RGB/alpha, eg first-open.png, >>> perhaps the pdf >>> creator has problems with that? >>> 3/google for this issue with the fop program, perhaps see if another >>> xsl solves >>> the issue. >>> >>> There are a lot of options to find the cause of this, but they take >>> some work. >>> Eg you could make a figures and figures-nl dir, copy in figures all eng= lish >>> figures, and one by one use the dutch figures, hunting down where >>> the bug in >>> pdf creation occurs. >>> >>> Benny >> >> >> >> >> >> ________________________________________________________________________= ___ >> Yahoo! Mail r=EF=BF=BDnvente le mail ! D=EF=BF=BDouvrez le nouveau Yahoo= ! Mail et >> son interface r=EF=BF=BDolutionnaire. >> http://fr.mail.yahoo.com >> > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your > job easier. > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim= o > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |