[jira] Closed: (XERCESJ-80) Reporting of externally specified encodings

[ji...@apache.org]

Message:

   The following issue has been closed.

   Resolver: Andy Clark
       Date: Fri, 23 Apr 2004 2:39 PM

This is an old issue and not relevent to the current implementation. If someone disagrees, then re-open the issue and provide a reason why this should be discussed further.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESJ-80

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESJ-80
    Summary: Reporting of externally specified encodings
       Type: Bug

     Status: Closed
 Resolution: WON'T FIX

    Project: Xerces2-J
 Components: 
             XNI
   Versions:
             2.0.0 [beta 2]

   Assignee: 
   Reporter: James Clark

    Created: Mon, 26 Nov 2001 3:05 AM
    Updated: Fri, 23 Apr 2004 2:39 PM
Environment: Operating System: Other
Platform: Other

Description:
XMLDocumentHandler reports encodings in two stages: firstly the
autodetected encoding is reported in startDocument or startEntity, and
secondly the encoding specified in the XML or text declaration is
reported in xmlDecl or textDecl.  It is not clear to me how these work
in the case where the encoding of an entity is specified not by
anything in the entity itself but by an external transport protocol
such as HTTP where the encoding can be specified by a charset
parameter in the MIME header (see 4.3.3 of the XML Rec). The infoset
defines the [character encoding scheme] of the document entity as "The
name of the character encoding scheme in which the document entity is
expressed". I don't see how I can compute this using XNI so that it
works regardless of whether the encoding was specified externally.
The encoding reported by the textDecl or xmlDecl methods presumably
refers to the encoding declared in the XML or text declaration which
may be wrong if the encoding was externally specified.  On the other
hand, when the encoding is not externally specified then the encoding
reported by textDecl or xmlDecl must be used. It seems to me that
startDocument and startEntity need an additional parameter saying
whether the encoding is externally specified; when it is the encoding
parameter would report the externally specified parameter rather than
the autodetected parameter.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org