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 bu...@apache.org on 2001/07/30 11:14:17 UTC
[Bug 2880] New: - Incorrect rendering on non-ASCII machines
PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT
ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW
AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE
DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL
BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2880
*** shadow/2880 Mon Jul 30 02:14:16 2001
--- shadow/2880.tmp.20872 Mon Jul 30 02:14:16 2001
***************
*** 0 ****
--- 1,24 ----
+ +============================================================================+
+ | Incorrect rendering on non-ASCII machines |
+ +----------------------------------------------------------------------------+
+ | Bug #: 2880 Product: Fop |
+ | Status: NEW Version: all |
+ | Resolution: Platform: Other |
+ | Severity: Major OS/Version: Other |
+ | Priority: Other Component: pdf renderer |
+ +----------------------------------------------------------------------------+
+ | Assigned To: fop-dev@xml.apache.org |
+ | Reported By: jfvilas@caixagalicia.es |
+ | CC list: Cc: |
+ +----------------------------------------------------------------------------+
+ | URL: |
+ +============================================================================+
+ | DESCRIPTION |
+ 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org