Re: 0.20.5rc3 (was Re: PDF Encryption: Clarification)
Forgive my ignorance, but can someone explain the argument for limiting the number of Release Candidates? If testing needs to be done, why not create snapshots that could be used for testing more widely. Since I don't currently use hyphenation, I don't want to wait for the hyphenation patterns to continue testing bug fixes for problems that are causing me to continue using 0.20.4 as my primary FOP, but I'd like to continue testing 0.20.5x. I really like the speed bump (40% is suh-weet!) I get when running 0.20.5rc 0.20.5rc2, but some of the bugs are showstoppers for me (especially 17472 15936). Perhaps it is just that I don't understand why we would want to limit the number of release candidates? Another potential problem, is that I'm having problems figuring out how to use our CVS system. Is there an FAQ somewhere? As for 0.20.5rc3, I'd like to see another Release Candidate ASAP (why wait for two weeks--other than the hope that more hyphenation patterns will be released). I figure if we put a new RC on the download page, people will use it and report any new bugs they find. ;-p Respectfully, Web Maestro Clay Christian Geisert wrote: Yes, another RC makes sense but I'm a bit unsure about the timeframe because I'd like 0.20.5rc3 to be the last RC before releasing 0.20.5 (i.e at best no changes after rc3) but there is still the issue with the hyphenation patterns which will probably take some to be solved as we we shouldn't use LPPL stuff (did I understand this right?) So what about rc3 in two weeks and then really stop with the maintenance branch? -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18624] New: - Problem with: multiple page-sequence(s)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18624. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18624 Problem with: multiple page-sequence(s) Summary: Problem with: multiple page-sequence(s) Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When I try examples with multiple page sequences, I get an error: [ERROR] master-reference '' for fo:page-sequence matches no simple-page-master or page-sequence-master. This is demonstrated by running: giro.fo advanced example. I have tried other examples from books and get the same result. I haven't found any other documentation stating this is a known problem, or a work around. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: DO NOT REPLY [Bug 18624] New: - Problem with: multiple page-sequence(s)
This is a FAQ: http://xml.apache.org/fop/faq.html#no_page_master 2.1. I get the error: [ERROR]: 'master-reference' for 'fo:page-sequence'matches no 'simple-page-master' or 'page-sequence-master'^ FOP was changed to be in accordance with the latest standard (see XSL standard).The page master for a fo:page-sequence is now refereced by the master-reference attribute. Replace the master-name attributes of your fo:page-sequence elements by master-reference attributes. You have to do this also for fo:single-page-master-reference, fo:repeatable-page-master-reference and fo:conditional-page-master-reference elements in you page master definitions. [EMAIL PROTECTED] wrote: DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18624. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18624 Problem with: multiple page-sequence(s) Summary: Problem with: multiple page-sequence(s) Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When I try examples with multiple page sequences, I get an error: [ERROR] master-reference '' for fo:page-sequence matches no simple-page-master or page-sequence-master. This is demonstrated by running: giro.fo advanced example. I have tried other examples from books and get the same result. I haven't found any other documentation stating this is a known problem, or a work around. -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/resources/stylesheets compliance2html.xsl
vmote 2003/04/02 12:33:00 Modified:src/documentation/resources/stylesheets compliance2html.xsl Log: Create links to the standard. Revision ChangesPath 1.3 +69 -10 xml-fop/src/documentation/resources/stylesheets/compliance2html.xsl Index: compliance2html.xsl === RCS file: /home/cvs/xml-fop/src/documentation/resources/stylesheets/compliance2html.xsl,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- compliance2html.xsl 30 Mar 2003 23:52:26 - 1.2 +++ compliance2html.xsl 2 Apr 2003 20:33:00 - 1.3 @@ -33,33 +33,61 @@ /xsl:template xsl:template match=body - table class=title summary= -tr -td valign=middle - h1xsl:value-of select=/compliance/head/title//h1 + table class=title summary= +tr +td valign=middle + h1xsl:value-of select=/compliance/head/title//h1 /td td nowrap=nowrap width=40 align=center a class=dida href=compliance.pdfimg alt=PDF src=skin/images/pdfdoc.gif border=0/br/PDF/a -/td - /tr +/td + /tr /table xsl:apply-templates select=standard/ /xsl:template xsl:template match=standard - h2xsl:value-of select=@name//h2 + h2 +a + xsl:attribute name=target +xsl:value-of select=@baseURL/ + /xsl:attribute + xsl:attribute name=href +xsl:value-of select=@baseURL/ + /xsl:attribute + xsl:value-of select=@name/ +/a + /h2 xsl:apply-templates select=explanatory/ xsl:apply-templates select=level-1/ /xsl:template xsl:template match=level-1 - h3xsl:value-of select=@name//h3 + h3 +xsl:value-of select=@name/ +xsl:if test=@citation + xsl:text (/xsl:text + a +xsl:attribute name=target + xsl:apply-templates select=../@baseURL/ +/xsl:attribute +xsl:attribute name=href + xsl:apply-templates select=../@baseURL//xsl:apply-templates select=@extURL/ +/xsl:attribute +xsl:value-of select=@citation/ + /a + xsl:text)/xsl:text +/xsl:if + /h3 xsl:apply-templates select=explanatory/ table border=1 tr th rowspan=2 pxsl:value-of select=@compliance-item-desc//p /th +th align=center rowspan=2 + Citation +/th th align=center colspan=3 Support /th @@ -92,8 +120,21 @@ xsl:template match=level-2 tr -td colspan=5 class=category +td colspan=6 class=category xsl:value-of select=@name/ +xsl:if test=@citation + xsl:text (/xsl:text + a +xsl:attribute name=target + xsl:apply-templates select=../../@baseURL/ +/xsl:attribute +xsl:attribute name=href + xsl:apply-templates select=../../@baseURL//xsl:apply-templates select=@extURL/ +/xsl:attribute +xsl:value-of select=@citation/ + /a + xsl:text)/xsl:text +/xsl:if /td /tr xsl:apply-templates select=level-3/ @@ -103,6 +144,24 @@ tr td xsl:value-of select=@name/ +/td +td align=center + xsl:choose +xsl:when test=@citation + a +xsl:attribute name=target + xsl:apply-templates select=../../../@baseURL/ +/xsl:attribute +xsl:attribute name=href + xsl:apply-templates select=../../../@baseURL//xsl:apply-templates select=@extURL/ +/xsl:attribute +xsl:value-of select=@citation/ + /a +/xsl:when +xsl:otherwise + xsl:text./xsl:text +/xsl:otherwise + /xsl:choose /td td align=center xsl:attribute name=class - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: xml-fop/src/documentation/content/xdocs compliance.xml
vmote 2003/04/02 12:34:03 Modified:src/documentation/content/xdocs compliance.xml Log: Add more link data. Revision ChangesPath 1.6 +104 -104 xml-fop/src/documentation/content/xdocs/compliance.xml Index: compliance.xml === RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/compliance.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- compliance.xml9 Dec 2002 17:26:10 - 1.5 +++ compliance.xml2 Apr 2003 20:34:03 - 1.6 @@ -7,7 +7,7 @@ titleFOP 0.20.4 Standards Compliance/title /head body -standard name=W3C XSL-FO 1.0 Standard baseURL=http://www.w3.org/TR/xsl/; compliance-level-1-desc=Basic compliance-level-2-desc=Extended compliance-level-3-desc=Complete +standard name=W3C XSL-FO 1.0 Standard baseURL=http://www.w3.org/TR/xsl; compliance-level-1-desc=Basic compliance-level-2-desc=Extended compliance-level-3-desc=Complete explanatory pFOP's goal is to be compliant with the W3C XSL-FO 1.0 standard. There are three levels of compliance specified in the standard: basic, extended, and complete. In the tables below, blue indicates support at the specified level of compliance, and red indicates a lack of support./p /explanatory @@ -69,7 +69,7 @@ level-3 name=table-body citation=§6.7.8 extURL=slice6.html#fo_table-body compliance-level=1 comply=yes/ level-3 name=table-row citation=§6.7.9 extURL=slice6.html#fo_table-row compliance-level=1 comply=yes/ level-3 name=table-cell citation=§6.7.10 extURL=slice6.html#fo_table-cell compliance-level=1 comply=yes -commentmust contain block-level FOs (cannot contain straight character data/comment +commentmust contain block-level FOs (cannot contain straight character data)/comment /level-3 /level-2 level-2 name=List Formatting Objects citation=§6.8 extURL=slice6.html#section-N17076-Formatting-Objects-for-Lists @@ -99,147 +99,147 @@ level-3 name=retrieve-marker citation=§6.11.4 extURL=slice6.html#fo_retrieve-marker compliance-level=2 comply=yes/ /level-2 /level-1 - level-1 name=XSL-FO Property Support compliance-item-desc=Property Name + level-1 name=XSL-FO Property Support citation=§7 extURL=slice7.html#pr-section compliance-item-desc=Property Name explanatory pThe following is a summary of FOP's current support for the standard XSL-FO properties. Please note that a number of properties and categories of properties are not supported because they do not apply to documents in visual formats./p /explanatory -level-2 name=Common Accessibility Properties - level-3 name=source-document compliance-level=1 comply=na/ - level-3 name=role compliance-level=1 comply=na/ -/level-2 -level-2 name=Common Absolute Position Properties - level-3 name=absolute-position compliance-level=3 comply=no/ - level-3 name=top compliance-level=2 comply=yes/ - level-3 name=right compliance-level=2 comply=yes/ - level-3 name=bottom compliance-level=2 comply=yes/ - level-3 name=left compliance-level=2 comply=yes/ -/level-2 -level-2 name=Common Aural Properties - level-3 name=azimuth compliance-level=1 comply=na/ - level-3 name=cue-after compliance-level=1 comply=na/ - level-3 name=cue-before compliance-level=1 comply=na/ - level-3 name=elevation compliance-level=1 comply=na/ - level-3 name=pause-after compliance-level=1 comply=na/ - level-3 name=pause-before compliance-level=1 comply=na/ - level-3 name=pitch compliance-level=1 comply=na/ - level-3 name=pitch-range compliance-level=1 comply=na/ - level-3 name=play-during compliance-level=1 comply=na/ - level-3 name=richness compliance-level=1 comply=na/ - level-3 name=speak compliance-level=1 comply=na/ - level-3 name=speak-header compliance-level=1 comply=na/ - level-3 name=speak-numeral compliance-level=1 comply=na/ - level-3 name=speak-punctuation compliance-level=1 comply=na/ - level-3 name=speech-rate compliance-level=1 comply=na/ - level-3 name=stress compliance-level=1 comply=na/ - level-3 name=voice-family compliance-level=1 comply=na/ - level-3 name=volume compliance-level=1 comply=na/ -/level-2 -level-2 name=Common Border, Padding, and Background Properties - level-3 name=background-attachment compliance-level=2 comply=no/ - level-3 name=background-color compliance-level=1 comply=yes/ - level-3 name=background-image compliance-level=2
DO NOT REPLY [Bug 18629] New: - when blocks are nested, the whole contents of the parent block is repeated several times
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18629. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18629 when blocks are nested, the whole contents of the parent block is repeated several times Summary: when blocks are nested, the whole contents of the parent block is repeated several times Product: Fop Version: 0.20.5 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I use empty fo:block / nested inside other blocks for line breaks. With previous versions of FOP, it worked fine, but with version 0.20.5-rc2, the contents of the whole block gets repeated on every line. For example: fo:block font-family=Helvetica fo:block Line 1 fo:block/ Line 2 fo:block/ Line 3 /fo:block /fo:block In previous FOP versions, this was rendered as Line 1 Line 2 Line 3 However, in 0.25-rc2, it is rendered as Line 1 Line 2 Line 3 Line 1 Line 2 Line 3 Line 1 Line 2 Line 3 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18629] - when blocks are nested, the whole contents of the parent block is repeated several times
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18629. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18629 when blocks are nested, the whole contents of the parent block is repeated several times --- Additional Comments From [EMAIL PROTECTED] 2003-04-02 22:22 --- Created an attachment (id=5610) example FO to reproduce the bug - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18629] - when blocks are nested, the whole contents of the parent block is repeated several times
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18629. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18629 when blocks are nested, the whole contents of the parent block is repeated several times --- Additional Comments From [EMAIL PROTECTED] 2003-04-02 22:23 --- Created an attachment (id=5611) example of output with FOP 0.25rc2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18629] - when blocks are nested, the whole contents of the parent block is repeated several times
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18629. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18629 when blocks are nested, the whole contents of the parent block is repeated several times [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2003-04-02 22:27 --- *** This bug has been marked as a duplicate of 17472 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17472] - Images appear twice in PDF output
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17472. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17472 Images appear twice in PDF output [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-04-02 22:27 --- *** Bug 18629 has been marked as a duplicate of this bug. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 18624] - Example giro.fo contains invalid properties
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18624. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18624 Example giro.fo contains invalid properties [EMAIL PROTECTED] changed: What|Removed |Added Summary|Problem with: multiple page-|Example giro.fo contains |sequence(s) |invalid properties --- Additional Comments From [EMAIL PROTECTED] 2003-04-03 06:37 --- See FAQ: http://xml.apache.org/fop/faq.html#no_page_master The problem is that the example wasn't completely updated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: 0.20.5rc3 (was Re: PDF Encryption: Clarification)
+1 for a 0.20.5rc3 ASAP (as Clay Leeds suggests). 0.20.5rc2 is bugged and I believe Jörg is tired of marking new bug reports as duplicates. :-) +1 for really (!) going to bugfixing-only mode in the maintenance branch. +1 for 0.20.5 being the last release from the maintenance branch. But being realistic, -0 on new bugfix release(s) if needed. Bugfixing only!!! 0.20.5a, 0.20.5b..., no 0.20.6. +1 for somebody providing funds so I can stay unemployed a little longer and invest more time in the redesign. I've got to get some money coming in again in about three months from now. The sooner the better. +1 for FOP enthusiasts start helping with the redesign. +1 for banning all lawyers to a small isolated pacific island. No seriously, I have one test case of grant submission running for over two weeks now. I haven't gotten any confirmation on that, yet. Ok, I was also shoving that before me, but I'm going to check on the status today. I promise. Once, I get the first through, I'll start the others. On 02.04.2003 16:22:11 Christian Geisert wrote: J.Pietschmann wrote: [..] Because hyphenation license updates seem to be slow, what about doing an rc3 in 10-15 days? We'll get rid of this duplicated text problem which poeple complain about much too often and get also a more thourough test of the encryption stuff. Yes, another RC makes sense but I'm a bit unsure about the timeframe because I'd like 0.20.5rc3 to be the last RC before releasing 0.20.5 (i.e at best no changes after rc3) but there is still the issue with the hyphenation patterns which will probably take some to be solved as we we shouldn't use LPPL stuff (did I understand this right?) So what about rc3 in two weeks and then really stop with the maintenance branch? Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
