Re: svn commit: r1342781 - in /xmlgraphics/fop/trunk: src/documentation/content/xdocs/bugs.xml src/documentation/content/xdocs/faq.xml status.xml
Great, thanks. I made the changes to the CMS and ported the other changes in the same time. There seems to be a bug in the Markdown converter, that doesn’t properly handle nested lists. It’s strange because the previewer in the web editor displays them properly. I cannot imagine that 2 different converters are used for the preview and the actual HTML generation. I’ll try and investigate what’s going on. Vincent On 20/11/12 14:40, Glenn Adams wrote: > ok, i can accept > > On Tue, Nov 20, 2012 at 3:52 AM, Vincent Hennebert > wrote: > >> Ok, so what about the attached diff? >> >> Thanks, >> Vincent >> >> On 10/10/12 00:50, Glenn Adams wrote: >>> As long as you don't remove the MUST/SHOULD language about providing an >>> input FO file, then I don't mind you taking another editing pass. If you >>> want to change the MUST/SHOULD language, then please propose a >> replacement >>> for discussion here. >>> >>> On Tue, Oct 9, 2012 at 11:10 PM, Vincent Hennebert >> wrote: >>> (Going through old unread commit messages...) I’d like to soften a bit the rather martial tone introduced in those changes. If I were a new user looking into submitting a bug and reading this page, I think I would refrain from doing so for fear of the police forces breaking into my home in the middle of the night and pointing a gun to my head because I dared not to follow the process... :-) Any objections? Thanks, Vincent On 25/05/12 20:10, gadams wrote: > Author: gadams > Date: Fri May 25 19:10:28 2012 > New Revision: 1342781 > > URL: http://svn.apache.org/viewvc?rev=1342781&view=rev > Log: > Update FAQ and New Bug documentation. > > Modified: > xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml > xmlgraphics/fop/trunk/src/documentation/content/xdocs/faq.xml > xmlgraphics/fop/trunk/status.xml > > Modified: >> xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml > URL: >> http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml?rev=1342781&r1=1342780&r2=1342781&view=diff > >> == > --- xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml (original) > +++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml Fri May 25 19:10:28 2012 > @@ -45,21 +45,66 @@ an email as changes are made to the issu > > >Unreported Issues (Reporting New Issues) > - User reports of bugs and requests for enhancements are extremely > -important parts of FOP development, and we appreciate the time you >> take to help > -us track these issues down. > + > +User reports of bugs and requests for enhancements are >> extremely > +important parts of FOP development, and we appreciate the time you take to help > +us track these issues down. > + > > -To help us ensure that the bug database is as useful as it should be, please > -use the Getting Help checklist to determine whether a bug report should be entered. > -Review the http://issues.apache.org/bugzilla/page.cgi?id=bug-writing.html";>Apache Bug Writing Guidelines before submitting your report. > -Enter a new issue report at http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The FOP issue database (Bugzilla). > -You will be asked to login to an existing Bugzilla account or to >> create a new > -one. > -When entering the bug report, please make your description complete >> and concise. > -If appropriate, attach a minimal fo file to your report which demonstrates the > -problem. > -After submission, a copy of your bug report will be automatically > -sent to the FOP developer discussion list. > + > + To help us ensure that the bug database is as useful as it should be, please > + use the Getting Help checklist to determine whether a bug report should be entered. > + > + > + Review the http://issues.apache.org/bugzilla/page.cgi?id=bug-writing.html";>Apache >> Bug > + Writing Guidelines before submitting your report. > + > + > + Enter a new issue report at http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The > + FOP issue database (Bugzilla). You will be asked to login to an existing Bugzilla account or to > + create a new one. When entering the bug report, please make your description complete and concise. > + If the issue involves a specific input or output file, then you MUST include the > + following information in the bug repo
Re: svn commit: r1342781 - in /xmlgraphics/fop/trunk: src/documentation/content/xdocs/bugs.xml src/documentation/content/xdocs/faq.xml status.xml
Ok, so what about the attached diff? Thanks, Vincent On 10/10/12 00:50, Glenn Adams wrote: > As long as you don't remove the MUST/SHOULD language about providing an > input FO file, then I don't mind you taking another editing pass. If you > want to change the MUST/SHOULD language, then please propose a replacement > for discussion here. > > On Tue, Oct 9, 2012 at 11:10 PM, Vincent Hennebert > wrote: > >> (Going through old unread commit messages...) >> >> I’d like to soften a bit the rather martial tone introduced in those >> changes. If I were a new user looking into submitting a bug and reading >> this page, I think I would refrain from doing so for fear of the police >> forces breaking into my home in the middle of the night and pointing >> a gun to my head because I dared not to follow the process... :-) >> >> Any objections? >> >> Thanks, >> Vincent >> >> >> On 25/05/12 20:10, gadams wrote: >>> Author: gadams >>> Date: Fri May 25 19:10:28 2012 >>> New Revision: 1342781 >>> >>> URL: http://svn.apache.org/viewvc?rev=1342781&view=rev >>> Log: >>> Update FAQ and New Bug documentation. >>> >>> Modified: >>> xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml >>> xmlgraphics/fop/trunk/src/documentation/content/xdocs/faq.xml >>> xmlgraphics/fop/trunk/status.xml >>> >>> Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml >>> URL: >> http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml?rev=1342781&r1=1342780&r2=1342781&view=diff >>> >> == >>> --- xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml >> (original) >>> +++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml Fri >> May 25 19:10:28 2012 >>> @@ -45,21 +45,66 @@ an email as changes are made to the issu >>> >>> >>>Unreported Issues (Reporting New Issues) >>> - User reports of bugs and requests for enhancements are >> extremely >>> -important parts of FOP development, and we appreciate the time you take >> to help >>> -us track these issues down. >>> + >>> +User reports of bugs and requests for enhancements are extremely >>> +important parts of FOP development, and we appreciate the time >> you take to help >>> +us track these issues down. >>> + >>> >>> -To help us ensure that the bug database is as useful as it >> should be, please >>> -use the Getting Help checklist to >> determine whether a bug report should be entered. >>> -Review the http://issues.apache.org/bugzilla/page.cgi?id=bug-writing.html";>Apache >> Bug Writing Guidelines before submitting your report. >>> -Enter a new issue report at http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The FOP >> issue database (Bugzilla). >>> -You will be asked to login to an existing Bugzilla account or to create >> a new >>> -one. >>> -When entering the bug report, please make your description complete and >> concise. >>> -If appropriate, attach a minimal fo file to your report which >> demonstrates the >>> -problem. >>> -After submission, a copy of your bug report will be >> automatically >>> -sent to the FOP developer discussion list. >>> + >>> + To help us ensure that the bug database is as useful as it >> should be, please >>> + use the Getting Help >> checklist to determine whether a bug report should be entered. >>> + >>> + >>> + Review the http://issues.apache.org/bugzilla/page.cgi?id=bug-writing.html";>Apache Bug >>> + Writing Guidelines before submitting your report. >>> + >>> + >>> + Enter a new issue report at http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The >>> + FOP issue database (Bugzilla). You will be asked to >> login to an existing Bugzilla account or to >>> + create a new one. When entering the bug report, please make >> your description complete and concise. >>> + If the issue involves a specific input or output file, then >> you MUST include the >>> + following information in the bug report (preferably as one or >> more attachments): >>> + >>> + >>> + an input XSL-FO file (an input XML plus XSLT file is not >> acceptable, unless and only if the >>> + issue being reported is related to the built-in XSLT >> transform processing convenience function provided >>> + by FOP); this input SHOULD be >> maximally minimal, which means that it should >>> + contain nothing more than the minimum needed to >> demonstrate the problem; if you do not take the effort >>> + to provide a maximally minimal input FO file, then you >> will be subsequently asked to do so before the >>> + bug is processed; >>> + >>> + >>> + a resulting output file
Re: svn commit: r1342781 - in /xmlgraphics/fop/trunk: src/documentation/content/xdocs/bugs.xml src/documentation/content/xdocs/faq.xml status.xml
As long as you don't remove the MUST/SHOULD language about providing an input FO file, then I don't mind you taking another editing pass. If you want to change the MUST/SHOULD language, then please propose a replacement for discussion here. On Tue, Oct 9, 2012 at 11:10 PM, Vincent Hennebert wrote: > (Going through old unread commit messages...) > > I’d like to soften a bit the rather martial tone introduced in those > changes. If I were a new user looking into submitting a bug and reading > this page, I think I would refrain from doing so for fear of the police > forces breaking into my home in the middle of the night and pointing > a gun to my head because I dared not to follow the process... :-) > > Any objections? > > Thanks, > Vincent > > > On 25/05/12 20:10, gadams wrote: > > Author: gadams > > Date: Fri May 25 19:10:28 2012 > > New Revision: 1342781 > > > > URL: http://svn.apache.org/viewvc?rev=1342781&view=rev > > Log: > > Update FAQ and New Bug documentation. > > > > Modified: > > xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml > > xmlgraphics/fop/trunk/src/documentation/content/xdocs/faq.xml > > xmlgraphics/fop/trunk/status.xml > > > > Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml > > URL: > http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml?rev=1342781&r1=1342780&r2=1342781&view=diff > > > == > > --- xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml > (original) > > +++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml Fri > May 25 19:10:28 2012 > > @@ -45,21 +45,66 @@ an email as changes are made to the issu > > > > > >Unreported Issues (Reporting New Issues) > > - User reports of bugs and requests for enhancements are > extremely > > -important parts of FOP development, and we appreciate the time you take > to help > > -us track these issues down. > > + > > +User reports of bugs and requests for enhancements are extremely > > +important parts of FOP development, and we appreciate the time > you take to help > > +us track these issues down. > > + > > > > -To help us ensure that the bug database is as useful as it > should be, please > > -use the Getting Help checklist to > determine whether a bug report should be entered. > > -Review the http://issues.apache.org/bugzilla/page.cgi?id=bug-writing.html";>Apache > Bug Writing Guidelines before submitting your report. > > -Enter a new issue report at http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The FOP > issue database (Bugzilla). > > -You will be asked to login to an existing Bugzilla account or to create > a new > > -one. > > -When entering the bug report, please make your description complete and > concise. > > -If appropriate, attach a minimal fo file to your report which > demonstrates the > > -problem. > > -After submission, a copy of your bug report will be > automatically > > -sent to the FOP developer discussion list. > > + > > + To help us ensure that the bug database is as useful as it > should be, please > > + use the Getting Help > checklist to determine whether a bug report should be entered. > > + > > + > > + Review the http://issues.apache.org/bugzilla/page.cgi?id=bug-writing.html";>Apache Bug > > + Writing Guidelines before submitting your report. > > + > > + > > + Enter a new issue report at http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The > > + FOP issue database (Bugzilla). You will be asked to > login to an existing Bugzilla account or to > > + create a new one. When entering the bug report, please make > your description complete and concise. > > + If the issue involves a specific input or output file, then > you MUST include the > > + following information in the bug report (preferably as one or > more attachments): > > + > > + > > + an input XSL-FO file (an input XML plus XSLT file is not > acceptable, unless and only if the > > + issue being reported is related to the built-in XSLT > transform processing convenience function provided > > + by FOP); this input SHOULD be > maximally minimal, which means that it should > > + contain nothing more than the minimum needed to > demonstrate the problem; if you do not take the effort > > + to provide a maximally minimal input FO file, then you > will be subsequently asked to do so before the > > + bug is processed; > > + > > + > > + a resulting output file, preferably in PDF format; if the > issue being reported involves a different output > > + format, then provide both a PDF output file an
Re: svn commit: r1342781 - in /xmlgraphics/fop/trunk: src/documentation/content/xdocs/bugs.xml src/documentation/content/xdocs/faq.xml status.xml
(Going through old unread commit messages...) I’d like to soften a bit the rather martial tone introduced in those changes. If I were a new user looking into submitting a bug and reading this page, I think I would refrain from doing so for fear of the police forces breaking into my home in the middle of the night and pointing a gun to my head because I dared not to follow the process... :-) Any objections? Thanks, Vincent On 25/05/12 20:10, gadams wrote: > Author: gadams > Date: Fri May 25 19:10:28 2012 > New Revision: 1342781 > > URL: http://svn.apache.org/viewvc?rev=1342781&view=rev > Log: > Update FAQ and New Bug documentation. > > Modified: > xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml > xmlgraphics/fop/trunk/src/documentation/content/xdocs/faq.xml > xmlgraphics/fop/trunk/status.xml > > Modified: xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml > URL: > http://svn.apache.org/viewvc/xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml?rev=1342781&r1=1342780&r2=1342781&view=diff > == > --- xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml (original) > +++ xmlgraphics/fop/trunk/src/documentation/content/xdocs/bugs.xml Fri May 25 > 19:10:28 2012 > @@ -45,21 +45,66 @@ an email as changes are made to the issu > > >Unreported Issues (Reporting New Issues) > - User reports of bugs and requests for enhancements are extremely > -important parts of FOP development, and we appreciate the time you take to > help > -us track these issues down. > + > +User reports of bugs and requests for enhancements are extremely > +important parts of FOP development, and we appreciate the time you > take to help > +us track these issues down. > + > > -To help us ensure that the bug database is as useful as it > should be, please > -use the Getting Help checklist to determine > whether a bug report should be entered. > -Review the href="http://issues.apache.org/bugzilla/page.cgi?id=bug-writing.html";>Apache > Bug Writing Guidelines before submitting your report. > -Enter a new issue report at href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The FOP > issue database (Bugzilla). > -You will be asked to login to an existing Bugzilla account or to create a new > -one. > -When entering the bug report, please make your description complete and > concise. > -If appropriate, attach a minimal fo file to your report which demonstrates > the > -problem. > -After submission, a copy of your bug report will be automatically > -sent to the FOP developer discussion list. > + > + To help us ensure that the bug database is as useful as it should > be, please > + use the Getting Help checklist to > determine whether a bug report should be entered. > + > + > + Review the href="http://issues.apache.org/bugzilla/page.cgi?id=bug-writing.html";>Apache > Bug > + Writing Guidelines before submitting your report. > + > + > + Enter a new issue report at href="http://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop";>The > + FOP issue database (Bugzilla). You will be asked to login > to an existing Bugzilla account or to > + create a new one. When entering the bug report, please make your > description complete and concise. > + If the issue involves a specific input or output file, then you > MUST include the > + following information in the bug report (preferably as one or more > attachments): > + > + > + an input XSL-FO file (an input XML plus XSLT file is not > acceptable, unless and only if the > + issue being reported is related to the built-in XSLT transform > processing convenience function provided > + by FOP); this input SHOULD be maximally > minimal, which means that it should > + contain nothing more than the minimum needed to demonstrate > the problem; if you do not take the effort > + to provide a maximally minimal input FO file, then you will be > subsequently asked to do so before the > + bug is processed; > + > + > + a resulting output file, preferably in PDF format; if the > issue being reported involves a different output > + format, then provide both a PDF output file and the output > file for the output format for which the report > + applies; > + > + > + a copy of the FOP configuration file you used (e.g., > fop.xconf); > + > + > + if FOP was invoked using the command line (or an equivalent), > then a dump of both the input > + command line and any console output (stderr or s
