Re: EBCDIC os390
Hi Jason, I think this solution will work. Hope this will make it at the end to the official package. But, are you sure the encoding has to be or may be dynamic ? AFAIK pdf is a binary format. The content can be divided in two parts, the tags and the data. The tags are always binary the same. No character higher than 0x7f is used in the tags. So every ASCII encoding like US-ASCII or ISO-5589-1 will work perfect. Letting somebody set the encoding to a non-ASCII locale will kill the pdf-file. How encoding is handled in the data part I don't know. Markus [EMAIL PROTECTED] wrote: I now have FOP working on our OS/390. My solution was to add a class called PDFConstants that only held a static string variable for the encoding type. All places in the code where there was a str.getBytes(); I replaced with try { str.getBytes(PDFConstants.Encoding); } catch ( UnsupportedEncodingException ue ) { str.getBytes(); } If there is a better way, please holler. If this is an ok way to fix it, how do post the patches? (never done this before on a public project like this ) Thanks, Jason -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED]] Sent: Friday, March 01, 2002 3:16 AM To: [EMAIL PROTECTED] Subject: Re: 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. 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:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] begin:vcard n:Bernhardt;Markus tel;cell:0171-5770462 tel;fax:089-420903-20 tel;home:089-6378949 tel;work:089-420903-14 x-mozilla-html:FALSE url:www.swsgmbh.de org:Software Service Wulf Schupp GmbH;Spieljoch adr:;;Spieljochstr. 34;München;;81825;Germany version:2.1 email;internet:[EMAIL PROTECTED] title:Entwicklungsleiter note;quoted-printable:[dF]Quisam=0D=0Awww.discordian-Front.de=0D=0AHail Eris !!!=0D=0AHappy Frag !!! fn:Markus Bernhardt end:vcard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: EBCDIC os390
I now have FOP working on our OS/390. My solution was to add a class called PDFConstants that only held a static string variable for the encoding type. All places in the code where there was a str.getBytes(); I replaced with try { str.getBytes(PDFConstants.Encoding); } catch ( UnsupportedEncodingException ue ) { str.getBytes(); } If there is a better way, please holler. If this is an ok way to fix it, how do post the patches? (never done this before on a public project like this ) Thanks, Jason -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED]] Sent: Friday, March 01, 2002 3:16 AM To: [EMAIL PROTECTED] Subject: Re: 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. 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:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: EBCDIC os390
Anyone have any documents on how the software works already to help me speed up where to look and what to patch? What it looks like to me, is that there are some compressed streams inside the entire pdf stream. So, a conversion at the final output won't work; appears to convert the non-compressed parts ok though. Thanks, Jason -Original Message- From: Jeremias Maerki [mailto:[EMAIL PROTECTED]] Sent: Friday, March 01, 2002 3:16 AM To: [EMAIL PROTECTED] Subject: Re: 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. 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:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: 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. 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:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]