Hi
I don't know much about PCL, but I know this: PCL laser printers usually
build a whole page in memory and then print it to paper. They normally
have a decent amount of memory. Especially older ink jet printers like
yours only have a small buffer, so the page has to be delivered in bands
(I
Sorry,
but after calling command from your example
xsl:variable name=locfo:page-number-citation ref-id=@id//xsl:variable
is variable loc empty. Could't you why? I tried fop 0.20.1.
My tested version:
!-- conditional adding even page --
xsl:template name=addEvenPage
xsl:param
Interesting how might I go about testing this? Could I change the
renderer and how would I do it? Could I test this by re-arranging PCL code
in the document I produce?
I render an XML stream into a PCL document, then I send it to the printer in
a separate step. How could I 'band' this?
Hi
Thx for responding. I do not use Cocoon at all. I use
Fop 0.18 with Xalan 1.2.2 and i have a template
mechanism to generate server side code(instead of
using JSP). My template takes in the XML file
dynamically built and xsl file to generate the Fo and
render the PDF from there. The same thing
I've had a quick look at the HP website. Your DJ 400 is a PCL 3 printer.
Art Welch said the PCL renderer produces PCL5, so this might actually be
the real problem.
Concerning my comment about banding, unfortunately, I haven't found any
information at the HP website.
On Thu, 13 Sep 2001 08:44:55
I think that everything that has been said is correct. However, I think that
banding would only come into play for graphic elements. It has been a very
long time since I last coded for an old DeskJet (or any DeskJet for that
matter - the last ones being the original DeskJet and the DeskJet Plus).
Hi all,
I would like to render xml input that contains arabic characters into pdf.
1. where can I find arabic fonts?
2. how can I add this font taking in consideration that xsl:fo has the
capability to specify text which is written right to left, top
to bottom?
with regards
Very interesting and helpful information. My understanding was that the
renderer would render the page as it is laid out in the XSL file, and since
the header is near the top (with text and graphics) I find it odd that it is
rendered and appears at the bottom of the page.
The text itself looks
I tried to run FOP-0.20 on tomcat 3.2.3. I replaced the jaxp.jar from
Tomcat/lib with the latest version. I placed the xerces-1.2.3.jar and
xalan-2.0.0.jar at he beginning of the Tomcat CLASSPATH(because tomcat uses
SAXParser 1 and FOP users SAXParser 2). When I run the servlet, the tomcat
Another thought... I am not sure if it has been suggested before, but
perhaps it may be better (easier) to just have a stylesheet generate plain
text and not use FOP at all. We have done this for some of our more simple
reports (that do not need to look pretty). This has the added benefit of
--- Liliana Selea [EMAIL PROTECTED] wrote:
I tried to run FOP-0.20 on tomcat 3.2.3. I replaced the jaxp.jar from
Tomcat/lib with the latest version. I placed the xerces-1.2.3.jar and
xalan-2.0.0.jar at he beginning of the Tomcat CLASSPATH(because tomcat uses
SAXParser 1 and FOP users
Hrm...plain text might be ok if we could have a small image and some
variable size text - any idea of I could use extensions for this?
-Original Message-
From: Art Welch [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 13, 2001 12:58 PM
To: '[EMAIL PROTECTED]'
Subject: RE: PCL
If you are using Xalan, it would be fairly simple to add an extension
function to spit out hard coded PCL3 commands to print a small bitmap (IIRC
just RLE of the pixels to print with some escape sequences) when called
(could even be more sophisticated and generate the PCL dynamically). Also
could
Thank you very much. I put xerces-1.2.3.jar, xalan-2.0.0.jar at the
beginning of tomcat classpath and deleted the jaxp.jar, parser.jar from
tomcat\lib directory and I put all FOP jars in lib directory under my web
application. I changed the worker to point to the right parser too.
Thanks
That works, but makes it tough if you change your Tomcat config files (which
uses the parser included with Tomcat to update the appropriate xml).
jw
-Original Message-
From: Liliana Selea [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 13, 2001 2:22 PM
To: [EMAIL PROTECTED]
Hi,
In CVS we have org.apache.fop.apps.Driver implementing the
org.apache.avalon.framework.logger.Loggable interface.
Is there a good reason we are dragging Avalon into our core code base?
Maybe someone should extend the Driver class with AvalonDriver so that us
Hi Steven,
I hate to tell you this, but 0.14 is a REALLY OLD version of FOP and no
one here is probably going to be able to help you. The best thing would
be for you to update your FOP distribution (http://xml.apache.org/fop)
and get the latest 0.20.1 version. The command line has changed but
Hi Corinna and welcome back,
Your idea sounds quite good to me. Speaking as a committer, I'm sure I
could spare a few minutes every now and then to commit the bugtest
files. Actually I've got rather a bunch of files lying about already
with names like bug1234.fo :-)
Since you've been absent for
FOP needs at all levels the ability to log errors and messages. System.out
is fine for CLI applications, but not for most embedded applications or
servers. We could have used Log4J instead, but the rest of Apache XML is
using LogKit and it suited our needs.
Avalon is the place where common
You are correct that it is theoretically possible to make FOP faster and
lighter without using any extra libraries like Avalon. If we made our own
custom XML parser optimized for FO, that would also be true, but we still
use Xalan and Xerces. We just don't have the resources or interest in
At our company we have have found a solution to the logging dilemma and
think FOP should do the same.
At this point there seems to be several ways to log errors within a Java
application:
1. JDK 1.4's new Logging API's
2. Log4J
3. Log Kit
4. Avalon's Loggable interface
5. Some new JDK
I tried to insert a jpg that was 800 width by 1035 height. Here is the
xsl-fo tag I'm using to do it:
fo:block
fo:external-graphic
xsl:attribute name =src
file:xsl:value-of select=location/
There was a discussion of this topic on the Avalon mailing list. Also,
there was a proposal of a revised Loggable interface. The current
Loggable interface is somewhat hardcoded to LogKit. The proposal would
basically solve the problem like Trunk would, except that this solution
is well
23 matches
Mail list logo
