Re: cvs commit: xml-fop/src/org/apache/fop/tools/anttasks Manifest.java
On 14 Dec 2001, [EMAIL PROTECTED] wrote: now uses built in ant manifest task (under jar) Thanks. I've added a testcase for Ant so that Ant's builds will continue to fail until we fix the problem, and you won't be bothered by GUMP mails any longer. To get the hostname, at least for Windows and Unix you can rely on environment variables, see http://marc.theaimsgroup.com/?l=ant-userm=100802855231701w=2 for a solution. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Problem in fo:inline background-color
Hello, I faced a problem on fo:inline background-color. I using fop0.20.2 to run fo:inline background-color and I found that is not background-color display in my PDF file. It there a way to solved this type of problem?? I hope someone can help me to solved this problem. thank you. lpkhoo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Problem in fo:inline background-color
Hi lpkhoo, background-color on fo:inline doesn't work. See bug 4510: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4510 --Phil. I faced a problem on fo:inline background-color. I using fop0.20.2 to run fo:inline background-color and I found that is not background-color display in my PDF file. It there a way to solved this type of problem?? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 5431] New: - space attributes don't work in FOP 0.20.2
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=5431. 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=5431 space attributes don't work in FOP 0.20.2 Summary: space attributes don't work in FOP 0.20.2 Product: Fop Version: all Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The space-after.optimum/space-before.optimum attributes no longer work as they did in the previous versions of FOP. Where they used to be able to be used on say a table-row element level, they no longer work, but have to be used on a block level instead, which is fine for short and simple stylesheets, but where complicated and dynamic stylesheets need to be used this is not always possible. AND, In all versions of FOP, FOP cannot handle large XML files(no bigger than 3MB with a small XSL file, and no more than say 1.8MB when used with a slightly bigger XSL file). It throws an out of memory exception, even when the memory usage parameter in FOP.BAT is set to the maximum on a PC with a LOT of ram. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [GUMP] Build Failure - FOP
On Fri, 14 Dec 2001, Keiron Liddle [EMAIL PROTECTED] wrote: Thanks, I have updated the build file to use the manifest under jar, works fine. Great! Looking at the hostname I think that it is better left out, it may cause computers to attempt to connect to the internet when resolving the hostname. As the original task would have done before. I guess my response to your commit message hasn't made it to fop-dev yet. As Diane pointed out, you can get the hostname from the environment (at least on Windows and Unix systems), see http://marc.theaimsgroup.com/?l=ant-userm=100802855231701w=2 for example. I don't know much about xslt apart from - it works. So you know more than me. What sort of things need to be done/added? Will it become a core task or optional? There is a built-in Ant task named style that has been built-in for a long time. It performs XSLT transformations, so it seems to be in the same area as xslt. I haven't looked at the code of FOP's task, but I assume that it must be doing something better than style does and therefore I would love to see style improved. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [GUMP] Build Failure - FOP
Stefan Bodewig wrote: I guess my response to your commit message hasn't made it to fop-dev yet. I've manually approved two more messages. Anyone on the fop-dev team want to volunteer to become moderator? My guess is that the current moderator has become backlogged for some reason. There is a built-in Ant task named style that has been built-in for a long time. It performs XSLT transformations, so it seems to be in the same area as xslt. I haven't looked at the code of FOP's task, but I assume that it must be doing something better than style does and therefore I would love to see style improved. Looking at both, I believe that fop could make use of the style tag. The primary difference between the two is that style was designed to support running multiple inputs through one stylesheet, xslt was designed to support sending one input. If fop were to use style for all of its fontfile.xsl transformations, it likely would see a noticable speedup in processing (and as this step takes a while, I'm sure that the speedup would be most welcome). There are a few secondary differences. xslt has a smart attribute which can be used to disable the check to see if the output is already up to date - this apparently is never used. It also has a mergefile attribute which will append the contents of the specified file to the target - again never used. Finally, there is a depends attribute which can declare other files which are referenced for the uptodate check. This can be done with the uptodate task. This is the only part that is slightly messy as it requires multiple targets to be created in order to achieve the same result. And since the style task doesn't have a smart flag, there only way to force the translation to be done is to delete the output. - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: [GUMP] Build Failure - FOP
On Fri, 14 Dec 2001, Sam Ruby [EMAIL PROTECTED] wrote: Stefan Bodewig wrote: I guess my response to your commit message hasn't made it to fop-dev yet. I've manually approved two more messages. Thanks, shouldn't be necessary any longer, I've subscribed to fop-dev shortly after sending my last post. xslt has a smart attribute which can be used to disable the check to see if the output is already up to date Corresponds to style's force attribute. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
FOP Javadoc
Is there a Javadoc for the FOP classes? Looked around in the distro and online and did find documentation, but was wondering if there was a nice standard Javadoc anywhere. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: FOP Javadoc
To clarify...I'm looking for javadoc on the 'org.apache.fop.apps' package as used by the provided servlet example. - Original Message - From: John M. Corro [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, December 14, 2001 7:52 AM Subject: FOP Javadoc Is there a Javadoc for the FOP classes? Looked around in the distro and online and did find documentation, but was wondering if there was a nice standard Javadoc anywhere. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: FOP Javadoc
At http://xml.apache.org/fop/dist/ in any file (just unzip it). Zdenek -Original Message- From: John M. Corro [mailto:[EMAIL PROTECTED]] Sent: Friday, December 14, 2001 4:56 PM To: [EMAIL PROTECTED] Subject: Re: FOP Javadoc To clarify...I'm looking for javadoc on the 'org.apache.fop.apps' package as used by the provided servlet example. - Original Message - From: John M. Corro [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, December 14, 2001 7:52 AM Subject: FOP Javadoc Is there a Javadoc for the FOP classes? Looked around in the distro and online and did find documentation, but was wondering if there was a nice standard Javadoc anywhere. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
DO NOT REPLY [Bug 4491] - PCL renderer not rendering tables correctly
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=4491. 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=4491 PCL renderer not rendering tables correctly [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2001-12-14 09:33 --- *** Bug 5430 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 5430] - pcl table rendering bug
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=5430. 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=5430 pcl table rendering bug [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Additional Comments From [EMAIL PROTECTED] 2001-12-14 09:33 --- I believe that this has been fixed. When the new release of FOP comes out (12/17/2001?) I will check again to confirm this. *** This bug has been marked as a duplicate of 4491 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Basic aspects (big fat list vs. live test documents)
On Friday 14 December 2001 10:05, Matthias Fischer wrote: However, you won't escape big maintenance so easily: Right - maintaining such a test suite is not light work. The advantage over pure documentation, however, is that both users and developers directly benefit from having strong test documents. So I think it would be easier to get the FOP community to work on building such a test suite (or organize/document existing tests) than finding someone to write and maintain documentation. -- -- Bertrand Delacrétaz, www.codeconsult.ch -- web technologies consultant - OO, Java, XML, C++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Fo inline truncates
Title: Fo inline truncates Hello - I am using the following code.. How can I prevent the fo:inline from truncating -? fo:table-cell fo:blockRequestor: fo:inline font-weight='normal' font-style='italic' wrap-option='wrap' #TAG_REQUEST# /fo:inline /fo:block /fo:table-cell Thanks Kunal Mittal Senior Consultant, i R i s e Bus: (510) 757-6145 eFax: (413) 460-5823 [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Basic aspects (big fat list vs. live test documents)
Hi all: Regarding the FO test suite. We at NIST in conjunction with the W3C Developed a test suite for FO. The site is: www.w3.org/Style/XSL/TestSuite/ We are also working on expanding that work to include ALL of the basic aspects of the language. We expect to have close to 5000 tests by next march. Any contributions, ideas, etc. will be appreciated. Thanks Carmelo Montanez - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
