You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by Christian Geisert <ch...@isu-gmbh.de> on 2002/03/12 00:02:30 UTC
[ANNOUNCEMENT] Fop 0.20.3 released
Doh, sorry for the previous mail (don't know what happened..)
Hi all,
just in case someone hasn't noticed yet ;-)
FOP 0.20.3 is finally available at http://xml.apache.org/dist/fop
for downloading.
The main reason for this release is the conformance to the XSL-FO
Version 1.0 W3C Recommendation. Other changes include:
- support for CMYK and embedded ICC profiles in jpeg images
- support for EPS images
- improved font encodings for native (Acrobat) fonts
- i18n improvments for AWT viewer
- support for letter-spacing
- Polish, Greek, and Hungarian hyphenation
- and of course a lot of bugfixes...
Changes from previous Release Candidate (rc2):
- added missing japanese resource for AWT viewer
- fixed Markers
- updated logkit from 1.0b4 to 1.0
Enjoy,
Christian
Re: [ANNOUNCEMENT] Fop 0.20.3 released
Posted by Christian Geisert <ch...@isu-gmbh.de>.
Raimund Kammering wrote:
> Hi,
>
> in the announcement for the fop 0.20.3 release there was a note about
> EPS images. I am not sure what this means:
>
> a.) Now you can also use EPS images in the FOP -> PDF process
> b.) FOP can now produce an EPS file as output
For the announcement I just copied some stuff from CHANGES:
(I really shouldn't write announcements that late..)
-Add support for EPS images in PostScript renderer and limited EPS
support in PDF Renderer (Tore Engvig)
I don't know what limited means here, maybe Tore can comment.
> A simple include by
> <fo:external-graphic src="myepsfile.eps"
> width="400px"
> scaling="uniform"
> display-align="center"/>
> (just the way as it is done with JPEG) dose not work. I got an error
> message like:
> --snip--
> [INFO]: [2]
> [ERROR]: Batik not in class path
> [ERROR]: Error while creating area : No ImageReader for this type of
> image (myepsfile.eps)
> --snip--
>
> What am I doing wrong (by the way batik IS definitely in my classpath)?
> Or is there no support for input of EPS images - meaning b.) was right?
Hmm, the error message with Batik seems to be wrong, I'll have a look
a this.
> Any comments and tips are very wellcome!
Maybe there is a epstosvg converter?
Or we could add support for PDF "graphics", I've succsessfully used
epstopdf and PDFTeX some time ago.
> Raimund
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: [ANNOUNCEMENT] Fop 0.20.3 released
Posted by Raimund Kammering <Ra...@desy.de>.
Hi,
in the announcement for the fop 0.20.3 release there was a note about
EPS images. I am not sure what this means:
a.) Now you can also use EPS images in the FOP -> PDF process
b.) FOP can now produce an EPS file as output
I guess and hope the first is meant?!
But if so I couldn't figure out how to include EPS images in my fo file.
A simple include by
<fo:external-graphic src="myepsfile.eps"
width="400px"
scaling="uniform"
display-align="center"/>
(just the way as it is done with JPEG) dose not work. I got an error
message like:
--snip--
[INFO]: [2]
[ERROR]: Batik not in class path
[ERROR]: Error while creating area : No ImageReader for this type of
image (myepsfile.eps)
--snip--
What am I doing wrong (by the way batik IS definitely in my classpath)?
Or is there no support for input of EPS images - meaning b.) was right?
Any comments and tips are very wellcome!
Raimund
--
DESY -MVP-
Notkestrasse 85
D-22603 Hamburg
Tel.: +49 40 8998 -4903
e-mail: Raimund.Kammering@desy.de
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: [ANNOUNCEMENT] Fop 0.20.3 released
Posted by Christian Geisert <ch...@isu-gmbh.de>.
David B. Bitton wrote:
> I notice the timestamp on the files is 3/4. Is that right, because that
> means I already have code made fresh daily.
Yeah, that correct. I've just been on holiday last week and had
no time to send the announcement until now.
> David B. Bitton
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: [ANNOUNCEMENT] Fop 0.20.3 released
Posted by "David B. Bitton" <da...@codenoevil.com>.
I notice the timestamp on the files is 3/4. Is that right, because that
means I already have code made fresh daily.
--
David B. Bitton
david@codenoevil.com
www.codenoevil.com
Diversa ab illis virtute valemus.
----- Original Message -----
From: "Christian Geisert" <ch...@isu-gmbh.de>
To: <fo...@xml.apache.org>; <fo...@xml.apache.org>
Sent: Monday, March 11, 2002 6:02 PM
Subject: [ANNOUNCEMENT] Fop 0.20.3 released
> Doh, sorry for the previous mail (don't know what happened..)
>
>
> Hi all,
>
> just in case someone hasn't noticed yet ;-)
>
>
> FOP 0.20.3 is finally available at http://xml.apache.org/dist/fop
> for downloading.
>
> The main reason for this release is the conformance to the XSL-FO
> Version 1.0 W3C Recommendation. Other changes include:
>
> - support for CMYK and embedded ICC profiles in jpeg images
> - support for EPS images
> - improved font encodings for native (Acrobat) fonts
> - i18n improvments for AWT viewer
> - support for letter-spacing
> - Polish, Greek, and Hungarian hyphenation
> - and of course a lot of bugfixes...
>
>
> Changes from previous Release Candidate (rc2):
> - added missing japanese resource for AWT viewer
> - fixed Markers
> - updated logkit from 1.0b4 to 1.0
>
>
> Enjoy,
> Christian
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> For additional commands, email: fop-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
RE: Omitting content length
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
This code looks like it's on the right sheet of music. :-) I only read the
message, though.
Use of this approach is subject to my final comment, which boils down to, be
aware of what your servlet container is doing for you already.
Transfer-codings are properties of the message and not of the message
payload - they are things that the HTTP layer does to ensure safe
transmission of the message - and strictly speaking (IMO) servlets proper
shouldn't have to deal with them. However, if your servlet container doesn't
do this for you then the servlet pretty much must.
But I would also still be cognizant of the possibility that if the servlet
container is not HTTP 1.1 compliant in this regard, that if your servlet is
doing chunked transfer-coding don't necessarily assume that the container
will cooperate, recognise what you're up to, and keep the connection open
for you. When I say "container" in this sense I mean the server as a whole -
the thing which handles both the servlet spec and the HTTP spec.
And if the browser on the other end is HTTP 1.0 then don't even bother. :-)
You need to detect that first.
Regards,
AHS
> -----Original Message-----
> From: Jeremias Maerki [mailto:jeremias.maerki@outline.ch]
> Sent: April 16, 2002 3:12 AM
> To: fop-user@xml.apache.org
> Subject: Re: Omitting content length
>
>
> There was a recent post on chunked transfer. I haven't checked it out,
> but it might help you.
>
> http://marc.theaimsgroup.com/?l=fop-dev&m=101791907122593&w=2
>
> Cheers,
> Jeremias Märki
>
> mailto:jeremias.maerki@outline.ch
>
> OUTLINE AG
> Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
> Tel. +41 41 317 2020 - Fax +41 41 317 2029
> Internet http://www.outline.ch
>
>
Re: Omitting content length
Posted by Jeremias Maerki <je...@outline.ch>.
There was a recent post on chunked transfer. I haven't checked it out,
but it might help you.
http://marc.theaimsgroup.com/?l=fop-dev&m=101791907122593&w=2
Cheers,
Jeremias Märki
mailto:jeremias.maerki@outline.ch
OUTLINE AG
Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
Tel. +41 41 317 2020 - Fax +41 41 317 2029
Internet http://www.outline.ch
RE: Omitting content length
Posted by Arved Sandstrom <Ar...@chebucto.ns.ca>.
Well, the alternative is chunked transfer-coding (which can be used on
either the request or response payloads). This is completely defined by HTTP
1.1, and _must_ be accepted in both directions by HTTP 1.1 compliant apps,
so if you send it to a recent IE browser it should know what to do with it.
I assume. :-)
In the context of servlet engines it doesn't make sense for a servlet to be
aware that a _request_ was transfer-coded, whether chunked or anything else.
The HTTP layer should handle this transparently. If it doesn't then it will
probably choke before your servlet ever gets a chance at it (this is what
should happen anyway).
Going in the other direction one can only that the servlet engine/HTTP
server combo will pick up on the fact that, at the instant that it must
commit the response, it doesn't have a content-length, and will therefore
switch over to chunked transfer coding, thereby keeping the connection open
_and_ allowing you not to worry about calculating an overall content-length.
I see from mailing lists that the Tomcat people were talking about chunked
transfer coding for Tomcat 3.2/3.3 a year or more ago - do they have it
properly implemented in 4.0 - I don't know. Worth checking out.
If all else fails I'd suggest that your servlet do all the work itself, but
my gut feeling is that if the servlet engine doesn't do chunked transfer
coding anyway, it's hardly going to properly react to the fact that your
servlet is doing it itself - it'll probably close the connection on you
anyway after committing the first buffer.
Hope that helps.
Regards,
AHS
> -----Original Message-----
> From: Brian O'Kelley [mailto:cokelley@alumni.princeton.edu]
> Sent: April 15, 2002 7:25 PM
> To: fop-user@xml.apache.org
> Subject: Omitting content length
>
>
> Ignore the question below - it works (if anyone needs SAX example, this
> is decent).
>
> It looks like what is happening is that I was writing this directly to a
> servlet's outputstream, so I never set the content length header. This
> made IE puke, although Lynx caught it ok. I've read through the threads
> about how IE handles content length header and requests the document
> twice.
>
> Is there any alternative to writing to a byte array to calculate the
> length before rewriting to the servlet's output stream? I'd like to
> avoid the memory consequences.
>
> Thanks,
> Brian
>
>
>
> -----Original Message-----
> From: Brian O'Kelley [mailto:cokelley@alumni.princeton.edu]
> Sent: Monday, April 15, 2002 5:28 PM
> To: fop-user@xml.apache.org
> Subject: FOP and SAX
>
>
> I'm trying to take an XML document, combine it with an XSL stylesheet,
> and spit it to PDF using SAX events, and I'm having trouble finding an
> example that works.
>
> Here's my code (using Fop 0.20.3):
>
> TransformerHandler tHandler = XSLTranslateFactory.
> getHandler("FopInput.xsl") ; // gets TransformerHandler
> from this file
> Driver fopDriver = new Driver() ;
> fopDriver.setRenderer(Driver.RENDER_PDF) ;
> fopDriver.setOutputStream(out) ;
> ContentHandler cHandler = driver.getContentHandler() ;
>
> XMLReader reader = XMLReaderFactory.createXMLReader() ;
> reader.setContentHandler(tHandler) ;
>
> reader.setProperty("http://xml.org/sax/properties/lexical-handler",
> tHandler) ;
> tHandler.setResult(new SAXResult(cHandler)) ;
> reader.parse(source) ;
>
> Any ideas?
>
> Thanks,
> Brian
>
>
Omitting content length
Posted by Brian O'Kelley <co...@alumni.princeton.edu>.
Ignore the question below - it works (if anyone needs SAX example, this
is decent).
It looks like what is happening is that I was writing this directly to a
servlet's outputstream, so I never set the content length header. This
made IE puke, although Lynx caught it ok. I've read through the threads
about how IE handles content length header and requests the document
twice.
Is there any alternative to writing to a byte array to calculate the
length before rewriting to the servlet's output stream? I'd like to
avoid the memory consequences.
Thanks,
Brian
-----Original Message-----
From: Brian O'Kelley [mailto:cokelley@alumni.princeton.edu]
Sent: Monday, April 15, 2002 5:28 PM
To: fop-user@xml.apache.org
Subject: FOP and SAX
I'm trying to take an XML document, combine it with an XSL stylesheet,
and spit it to PDF using SAX events, and I'm having trouble finding an
example that works.
Here's my code (using Fop 0.20.3):
TransformerHandler tHandler = XSLTranslateFactory.
getHandler("FopInput.xsl") ; // gets TransformerHandler
from this file
Driver fopDriver = new Driver() ;
fopDriver.setRenderer(Driver.RENDER_PDF) ;
fopDriver.setOutputStream(out) ;
ContentHandler cHandler = driver.getContentHandler() ;
XMLReader reader = XMLReaderFactory.createXMLReader() ;
reader.setContentHandler(tHandler) ;
reader.setProperty("http://xml.org/sax/properties/lexical-handler",
tHandler) ;
tHandler.setResult(new SAXResult(cHandler)) ;
reader.parse(source) ;
Any ideas?
Thanks,
Brian
FOP and SAX
Posted by Brian O'Kelley <co...@alumni.princeton.edu>.
I'm trying to take an XML document, combine it with an XSL stylesheet,
and spit it to PDF using SAX events, and I'm having trouble finding an
example that works.
Here's my code (using Fop 0.20.3):
TransformerHandler tHandler = XSLTranslateFactory.
getHandler("FopInput.xsl") ; // gets TransformerHandler
from this file
Driver fopDriver = new Driver() ;
fopDriver.setRenderer(Driver.RENDER_PDF) ;
fopDriver.setOutputStream(out) ;
ContentHandler cHandler = driver.getContentHandler() ;
XMLReader reader = XMLReaderFactory.createXMLReader() ;
reader.setContentHandler(tHandler) ;
reader.setProperty("http://xml.org/sax/properties/lexical-handler",
tHandler) ;
tHandler.setResult(new SAXResult(cHandler)) ;
reader.parse(source) ;
Any ideas?
Thanks,
Brian
Re: [FOP-USER] Re: [FOP-USER] [ANNOUNCEMENT] Fop 0.20.3 released
Posted by Trevor Jenkins <tr...@suneidesis.com>.
On Wed, 13 Mar 2002, Christian Geisert <ch...@isu-gmbh.de> wrote:
> Trevor Jenkins wrote:
>
> > Does this mean that I can now use the Norm Walsh XSLT stylesheets
> > "shrink-wrapped"?
>
> Yes, Docbook stylesheets (I assume you are talking about those)
> *should* work without changes but if you get the desired output is
> another question ;-)
Great ... provided that FOP implements the features properly and doesn't
baulk at the size/complexity of the document I'll get it to produce what
my customer wants. I suspect that the xref stuff will take some getting
right.
> Docbook compatibility is one of the things I would like to have a
> look at in the next time.
This document will test FOP's DocBook comatibility as the current source
file (an api manual) is over 1.5Mb, has some 300 refentry occurences, and
makes extensive use of DocBook structures with verbose markup. The final
version is projected to be over 3Mb, in addition to the refentry stuff
will contain a dozen or so chapters of tutorial material, and have
extensive examples added to each existing refentry. Indeed the final file
size would be much larger than that but for loads of entity declarations
for boiler-plate text in those refentry ocurrences. Being an api manual
there are hundreds of xref elements; perhaps 1,500 of them.
When I tried FOP 0.20.2 it took some 7 minutes elapsed time to report the
initial error with a 0.5Mb file size. Frustratingly that first error was
to report that certain features of Norman Walsh DocBook stylesheets were
not then supported. Actually the (elapsed) time isn't that important as
this will only be an ocassional re-generation. Might have be re-done every
6 months to a year but no more than that.
Regards, Trevor
British Sign Language is not inarticulate handwaving; it's a living language.
Support the campaign for formal recognition by the British government now!
Details at http://www.fdp.org.uk/ or http://www.bsl-march.co.uk/
--
<>< Re: deemed!
Re: [FOP-USER] [ANNOUNCEMENT] Fop 0.20.3 released
Posted by Christian Geisert <ch...@isu-gmbh.de>.
Trevor Jenkins wrote:
> Does this mean that I can now use the Norm Walsh XSLT stylesheets
> "shrink-wrapped"? I had problems doing this with 0.20.2 as previosuly
> reported to this list. If I can't use them shrink wrapped what must I do
> to use the latest versions of Norm's work?
Yes, Docbook stylesheets (I assume you are talking about those)
*should* work without changes but if you get the desired output is
another question ;-)
Docbook compatibility is one of the things I would like to have a
look at in the next time.
> Regards, Trevor
Christian
Re: [FOP-USER] [ANNOUNCEMENT] Fop 0.20.3 released
Posted by Trevor Jenkins <tr...@suneidesis.com>.
On Tue, 12 Mar 2002, Christian Geisert <ch...@isu-gmbh.de> wrote:
> FOP 0.20.3 is finally available at http://xml.apache.org/dist/fop
> for downloading.
>
> The main reason for this release is the conformance to the XSL-FO
> Version 1.0 W3C Recommendation.
Does this mean that I can now use the Norm Walsh XSLT stylesheets
"shrink-wrapped"? I had problems doing this with 0.20.2 as previosuly
reported to this list. If I can't use them shrink wrapped what must I do
to use the latest versions of Norm's work?
Regards, Trevor
British Sign Language is not inarticulate handwaving; it's a living language.
Support the campaign for formal recognition by the British government now!
Details at http://www.fdp.org.uk/ or http://www.bsl-march.co.uk/
--
<>< Re: deemed!