You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Ja...@mail.state.ky.us on 2002/02/28 22:41:08 UTC
EBCDIC os390
I'll apologize upfront as I think my question is really for the users list
but,
I was unable to find how to subscribe to it.
I'm developing under Websphere 4.0 and have had success in using FOP .20
on my NT machines. I take that ear file and install it on our os390
Websphere
server and I get back garbage. If I convert the garbage from EBCDIC to ASCII
with a tool, it appears the uncompressed streams convert fine. The document
still does not work. How can I make FOP ensure that all of it's temporary
streams
use the proper encoding? The following snippet is how I'm using FOP.
ByteArrayOutputStream out = new ByteArrayOutputStream();
response.setContentType("application/pdf");
Driver driver = new Driver();
driver.setRenderer(Driver.RENDER_PDF);
driver.setOutputStream(out);
driver.render( foDoc );
byte[] content = out.toByteArray();
response.setContentLength(content.length);
response.getOutputStream().write(content);
response.getOutputStream().flush();
TIA, Jason
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: EBCDIC os390
Posted by Jeremias Maerki <je...@outline.ch>.
> I'll apologize upfront as I think my question is really for the users list
> but,
> I was unable to find how to subscribe to it.
No, I think you're in the right place.
> I'm developing under Websphere 4.0 and have had success in using FOP .20
> on my NT machines. I take that ear file and install it on our os390
> Websphere
> server and I get back garbage. If I convert the garbage from EBCDIC to ASCII
> with a tool, it appears the uncompressed streams convert fine. The document
> still does not work. How can I make FOP ensure that all of it's temporary
> streams
> use the proper encoding? The following snippet is how I'm using FOP.
Ben Fowler posted a similar mail two days ago.
http://marc.theaimsgroup.com/?l=fop-dev&m=101480100804070&w=2
You're in the same boat. I think it would be good if you one of you two
could really track down the problem, create a patch for it and post it
to the list for inclusion into FOP along with some documentation
(guidelines) what has to be done to ensure non-ascii-environment
compatibility in FOP for the future.
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
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org