[ expat-Bugs-1796740 ] wrong bug description (and fix) for #1690883

Bugs item #1796740, was opened at 2007-09-17 19:52
Message generated for change (Comment added) made by kwaclaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1796740&group_id=10127

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
>Group: Not a Bug
>Status: Closed
>Resolution: Rejected
Priority: 5
Private: No
Submitted By: flow67 (flow67)
Assigned to: Karl Waclawek (kwaclaw)
Summary: wrong bug description (and fix) for #1690883

Initial Comment:
Changes file for release 2.0.1 incorrectly reports 

- Fixed bug #1690883: Expat failed on EBCDIC systems as it assumed some character constants to be ASCII encoded.

Unfortunately bug 1690883 is not related to EBCDIC encoding (as we've just found out on our z/OS system) but , according to the bug database , 

[ 1690883 ] Expat rejects xml: prefix with "unbound prefix" error

2.0.1 is still not working on EBCDIC systems (initial <? is not recognised if coded in EBCDIC) 

Thanks 
 

----------------------------------------------------------------------

>Comment By: Karl Waclawek (kwaclaw)
Date: 2009-01-18 18:55

Message:
I did not notice at first that your issue is actually with Expat not
parsing documents encoded in EBCDIC. The original issue was with Expat not
properly building on EBCDIC systems, and this was fixed.

Parsing EBCDIC encoded documents has never been a goal for Expat, as it is
not required by the standard. However, we have a standalone patch (#987903)
which you might be able to adapt to your needs.

Closing this issue.

----------------------------------------------------------------------

Comment By: Karl Waclawek (kwaclaw)
Date: 2007-09-18 09:46

Message:
Logged In: YES 
user_id=290026
Originator: NO

The original fix was contributed by Scott Klement, and it certainly was a
valid fix for Expat, even if it doesn't fix your issue. However if fixed
the issue for Scott. Since we don't have access to an EBCDIC platform, we
cannot really address this issue from our side, we will have to rely on
contributors like Scott. Would yu please contact him (just click on the
link by his name on the original bug report) and maybe you two could figure
it out together.

Thanks,

Karl

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=1796740&group_id=10127