Sorry for flooding the list, but I am reporting bugs as I found them.

I have a document that complies with a DTD I wrote myself. The document contains some entities, namely: æ and à, which are defined on the DTD as:

    <!ENTITY aelig   "&#230;" ><!-- small ae diphthong (ligature) -->
    <!ENTITY agrave  "&#224;" ><!-- small a, grave accent -->

For compatibility with quite old browsers and OSs, I had on the configuration files these directives:

  AxTranslateOutput On
  AxOutputCharset iso-8859-1

This worked ok with AxKit 1.5. On 1.6.1-CVS (downloaded a couple of hours ago or so) it's doing strange:

* the browser correctly detects a ISO-8859-1 encoding
* &aelig; shows up as æ
* &agrave; shows up correctly

If I force the browser to UTF-8, &aelig; shows up correctly and &agrave; is garbled.

If I comment out the two directives above:

* the browser detects a UTF-8 encoding
* again, &aelig; shows up as æ and &agrave; shows up correctly

Forcing the browser to ISO-8859-1 further garbles the output.

No problems are reported to the error log (with AxDebugLevel set to 1).

Am I wrong somewhere? Or is there a bug? Or should I update XML::LibXML from 1.51 to...?

Thanks for help and sorry for flooding :-(

Ciao
Marco

--
Marco Marongiu                         Email: [EMAIL PROTECTED]
CRS4 Research Center                   Phone: +39 070 9250 336
NCS Division                           Fax:   +39 070 9250 216
NSM Group                              WWW: http://bugs.unica.it:4444/



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to