XUL Parsing Error if DTD is not saved as UTF-8




13 years ago
13 years ago


(Reporter: aponso, Assigned: Blake Ross)


Firefox Tracking Flags

(Not tracked)




13 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/ jpeg;q=0, gif; q=0

An XML Parsing error occurs when I load a XUL file with a corresponding DTD, 
and the DTD has international characters, like below:

<?xml version="1.0" encoding="ISO-8859-1"?>
<!ENTITY dtd_bug_msg1 "There is a bug here!!">
<!ENTITY dtd_bug_msg2 "Tem um bug que é o cão chupando manga!!">

Firefox is ignoring the encoding declaration. Only functions if the DTD file is 
saved as UTF-8 encoding by the text editor.

Reproducible: Always

Steps to Reproduce:
1.Create a XUL file as below

<?xml version="1.0" encoding="ISO-8859-1"?>
<?xml-stylesheet href="chrome://global/skin" type="text/css"?>

<!DOCTYPE dialog SYSTEM "bug_dtd_encoding.dtd">

<dialog id="dtd_bug_test"
	title="DTD Bug Test Dialog"
	<vbox flex="1">

2. Create the corresponding DTD, save as DOS/ASCII (not UTF-8):

<?xml version="1.0" encoding="ISO-8859-1"?>
<!ENTITY dtd_bug_msg1 "There is a bug here!!">
<!ENTITY dtd_bug_msg2 "Tem um bug que é o cão chupando manga!!">

3. Run the xul file

Actual Results:  
XML Parsing Error: error in processing external entity reference:

<!DOCTYPE dialog SYSTEM "bug_dtd_encoding.dtd">

Expected Results:  
Followed the xml encoding declaration, accepting the international characters 
in DTD.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.