Bug 2880 - Incorrect rendering on non-ASCII machines
Summary: Incorrect rendering on non-ASCII machines
Status: CLOSED DUPLICATE of bug 2532
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: pdf (show other bugs)
Version: all
Hardware: Other other
: P3 major
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-07-30 02:14 UTC by Julio
Modified: 2012-04-01 13:49 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Julio 2001-07-30 02:14:16 UTC 
I'm using OS/390 and IBM JDK1.3.0
When i use FOP in order to render PDF, the PDF headers are created in EBCDIC, 
and the PDF "streams" are written in binary, so the genereated pdf file is 
unreadable in a ASCII or EBCDIC machine.

I suppose you're using methods like writeBytes or writeChars or something like 
that. In EBCDIC machines the results are different when writen bytes or chars 
to a file.
Comment 1 Julio 2001-07-31 03:40:40 UTC 
I've been working on source files. I've found a possible soultion. The error is 
caused by the use of getBytes() in String translations. I've susbstituted 
getBytes() by getBytes("ISO-8859-1"), so the render of PDF files runs in my 
EBCDIC (S390) machine and in my ASCII (windows) machine.
I think the PDFDocument class should include a "setEncoding(String enc)" and 
a "getEncoding()" methods.
Comment 2 J.Pietschmann 2002-05-06 13:33:40 UTC 
One of the problems is that PDF is in part a binary format because of
embedded images (in particular compressed images).

*** This bug has been marked as a duplicate of 2532 ***
Comment 3 Glenn Adams 2012-04-01 13:49:02 UTC 
batch transition to closed remaining pre-FOP1.0 resolved bugs