Re: [VOTE] Finn Bock for Committer
Glen Mazza wrote: Therefore, I'm happy to nominate Finn Bock for committer +1 J.Pietschmann
Re: [VOTE] Finn Bock for Committer
J.Pietschmann wrote: Glen Mazza wrote: Therefore, I'm happy to nominate Finn Bock for committer +1 +1 -- Oleg Tkachenko http://www.tkachenko.com/blog Multiconn Technologies, Israel
DO NOT REPLY [Bug 25732] - [PATCH] Supress leading spaces after a line-break.
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=25732. 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=25732 [PATCH] Supress leading spaces after a line-break. --- Additional Comments From [EMAIL PROTECTED] 2003-12-24 12:30 --- The use of 'first' is to indicate that space suppression should only happen at the very first flow object in a block. But Simon and Glen's comments have made me realize that that is probably wrong. Space suppression should occur for each flow object until a bp is added. So the test vecInlineBreaks.size() == iPrevLineEnd is enough and the badly named 'first' vrbl can be removed. Unfortunately this triggers a different bug where setting space suppression on a InlineStackingLM cause space suppression to occurs for each of the LM's children. I'll take a look at that problem, and until I come up with something, this patch should be suspended.
DO NOT REPLY [Bug 25743] New: - Spaces are suppressed between words for first fo:inline after line-break
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=25743. 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=25743 Spaces are suppressed between words for first fo:inline after line-break Summary: Spaces are suppressed between words for first fo:inline after line-break Product: Fop Version: 1.0dev Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: page-master/layout AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] If a fragment like this: fo:inline background-color=bluefo:inlinefoo/fo:inlinefo:inline bar/fo:inline/fo:inline is the first flow object after a linebreak, then the space before ' bar' is incorrectly suppressed.
DO NOT REPLY [Bug 25743] - Spaces are suppressed between words for first fo:inline after line-break
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=25743. 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=25743 Spaces are suppressed between words for first fo:inline after line-break --- Additional Comments From [EMAIL PROTECTED] 2003-12-24 12:36 --- Created an attachment (id=9695) A test .fo that illustrate the problem.
DO NOT REPLY [Bug 25732] - [PATCH] Supress leading spaces after a line-break.
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=25732. 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=25732 [PATCH] Supress leading spaces after a line-break. --- Additional Comments From [EMAIL PROTECTED] 2003-12-24 13:52 --- A new patch, that doesn't introduce new vrbls but uses the existing test for a new line. The patch also ensure that a child InlineStackingLM always uses the parent LM value for SUPPRESS_LEADING_SPACES. As it were, the parent value was only used when the InlineStackingLM started a new area. This patch also fixes bug 25743. Thank you Simon and Glen for your help. regards, finn
DO NOT REPLY [Bug 25732] - [PATCH] Supress leading spaces after a line-break.
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=25732. 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=25732 [PATCH] Supress leading spaces after a line-break. --- Additional Comments From [EMAIL PROTECTED] 2003-12-24 13:53 --- Created an attachment (id=9696) A new unified patch against HEAD that overrides the previous patch.
DO NOT REPLY [Bug 25732] - [PATCH] Supress leading spaces after a line-break.
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=25732. 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=25732 [PATCH] Supress leading spaces after a line-break. --- Additional Comments From [EMAIL PROTECTED] 2003-12-24 13:54 --- Created an attachment (id=9697) A slightly diffrent test that also checks for the bug in 25743.
Trying to use the NIST test suite.
Hi, I was looking for xsl-fo test suites on the net and found http://www.w3.org/Style/XSL/TestSuite/ but for some reason all the test in the NIST zip file uses master-name instead of master-reference on the fo:page-sequence's. fo:page-sequence master-name=test-page-master Is there some kind of background story of this? To me, it seems like the tests are plain wrong here. regards, finn
RE: Trying to use the NIST test suite.
-Original Message- From: Finn Bock [mailto:[EMAIL PROTECTED] Hi, I was looking for xsl-fo test suites on the net and found http://www.w3.org/Style/XSL/TestSuite/ but for some reason all the test in the NIST zip file uses master-name instead of master-reference on the fo:page-sequence's. fo:page-sequence master-name=test-page-master Hi, Apparently this was admitted by earlier versions of the spec. Older versions of FOP still supported this, but the latest version throws an error... See also : http://xml.apache.org/fop/faq.html#no-page-master Is there some kind of background story of this? To me, it seems like the tests are plain wrong here. So they are indeed dead-wrong. Cheers, Andreas
Re: Trying to use the NIST test suite.
I was looking for xsl-fo test suites on the net and found http://www.w3.org/Style/XSL/TestSuite/ but for some reason all the test in the NIST zip file uses master-name instead of master-reference on the fo:page-sequence's. fo:page-sequence master-name=test-page-master [Andreas L. Delmelle] Apparently this was admitted by earlier versions of the spec. Older versions of FOP still supported this, but the latest version throws an error... See also : http://xml.apache.org/fop/faq.html#no-page-master Thank you for the link, that was exactly what I was looking for. regards, finn
RE: [VOTE] Finn Bock for Committer
-Original Message- From: Bertrand Delacretaz [mailto:[EMAIL PROTECTED] Seems like no one has voted on this yet? Must be this Christmas thing... Indeed, it's holidays... I almost felt compelled to add my own (invalid) +1, just to have _some_ answer ;) Happy Holidays ( to everyone who cares ) ! Cheers, Andreas
Re: Trying to use the NIST test suite.
On Wednesday 24 December 2003 15:39, Andreas L. Delmelle wrote: -Original Message- From: Finn Bock [mailto:[EMAIL PROTECTED] Hi, I was looking for xsl-fo test suites on the net and found http://www.w3.org/Style/XSL/TestSuite/ but for some reason all the test in the NIST zip file uses master-name instead of master-reference on the fo:page-sequence's. fo:page-sequence master-name=test-page-master Hi, Apparently this was admitted by earlier versions of the spec. Older versions of FOP still supported this, but the latest version throws an error... Hi, wouldn't it be reasonable to also accept the obsolete 'master-name' and to just print out a corresponding warning message instead of throwing an error? AFAIK, the attribute has only been renamed to 'master-reference', but its meaning and usage remained identically the same. Regards, Bernd
Re: Trying to use the NIST test suite.
On Dec 24, 2003, at 8:55 AM, Bernd Brandstetter wrote: On Wednesday 24 December 2003 15:39, Andreas L. Delmelle wrote: Apparently this was admitted by earlier versions of the spec. Older versions of FOP still supported this, but the latest version throws an error... wouldn't it be reasonable to also accept the obsolete 'master-name' and to just print out a corresponding warning message instead of throwing an error? AFAIK, the attribute has only been renamed to 'master-reference', but its meaning and usage remained identically the same. Regards, Bernd +1 (if non-votes count! ;-) ) In fact, I would love to see this considered a bugfix for the 0.20.5 maintenance release, as I believe it would help people upgrade from 0.20.4 (or lower) to 0.20.5 and higher. Backward-compatibility is always a nice thing--especially if it's as easy as this appears to be.
Re: Trying to use the NIST test suite.
HI all: I developed the NIST test suite. I will look into this issue Friday morning. Regrettably I can't dot this minute. I was under the impression that the stated problem was solved years ago. I will post something soon after Christmas. Carmelo At 03:29 PM 12/24/2003 +0100, you wrote: Hi, I was looking for xsl-fo test suites on the net and found http://www.w3.org/Style/XSL/TestSuite/ but for some reason all the test in the NIST zip file uses master-name instead of master-reference on the fo:page-sequence's. fo:page-sequence master-name=test-page-master Is there some kind of background story of this? To me, it seems like the tests are plain wrong here. regards, finn
Merry Christmas/Frohe Weihnachten!
Yes, thankfully Bertrand came to the rescue for us here! Merry Christmas and Happy New Year everyone! I'll be back to FOP this weekend. Regards, Glen --- Andreas L. Delmelle [EMAIL PROTECTED] wrote: -Original Message- From: Bertrand Delacretaz [mailto:[EMAIL PROTECTED] Seems like no one has voted on this yet? Must be this Christmas thing... Indeed, it's holidays... I almost felt compelled to add my own (invalid) +1, just to have _some_ answer ;) Happy Holidays ( to everyone who cares ) ! Cheers, Andreas __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
RE: Trying to use the NIST test suite.
-Original Message- From: Clay Leeds [mailto:[EMAIL PROTECTED] On Dec 24, 2003, at 8:55 AM, Bernd Brandstetter wrote: wouldn't it be reasonable to also accept the obsolete 'master-name' and to just print out a corresponding warning message instead of throwing an error? AFAIK, the attribute has only been renamed to 'master-reference', but its meaning and usage remained identically the same. +1 (if non-votes count! ;-) ) In fact, I would love to see this considered a bugfix for the 0.20.5 maintenance release, as I believe it would help people upgrade from 0.20.4 (or lower) to 0.20.5 and higher. Backward-compatibility is always a nice thing--especially if it's as easy as this appears to be. Yes, perhaps some solution comparable to deprecation in Java. As ( and if ) the spec evolves further, this would become a necessity anyway. ( Problem would appear if, in the future 'master-name' would be defined in a whole different way... XSL-FO doesn't provide a 'version' attribute yet, like XSLT does ) Then again, it seems hard to believe this topic has not presented itself before, and maybe it wasn't so easy after all. Since one of the primary goals of FOP is compliance with the spec, and if the spec no longer considers this property name to be valid --what's more important? Backward compatibility or compliance with (the most current version of) the spec? The latter seems preferrable as it discourages the use of properties that are undefined by the spec, while the first allows people to ignore it. If at some time they decide (for some mysterious reason) to use XEP instead of FOP, they'll receive an error anyway. Just a thought. Cheers, Andreas
