christian bindeballe wrote:
[...]
That's right. My mistake. I merely "deducted" the encoding from some
characters used inside the text of the feeds as for example &8221; which
are clearly non-Latin-1 characters. Since both feeds have ISO-8859-1 in
their response headers it means that these feeds are either malformatted
or malencoded.
Don't mix characterset and character encoding.
"&8221" is decimal notation of unicode character U+201D.
"iso-8859-1" or "utf-8" are just character encodings.
Encoding and formatting of both your sources is ok, but selection of
"iso-8859-1" is a poor choice regarding readability.
[...]
Do you mean I should register the serializer used with both the
parameter "charset" and the element <encoding> corresponding (having the
same value)?
The first one goes into HTTP response header and is needed by any
browser to recognize the character encoding of the following content.
You may run your own test by just omitting it and checking HTTP response
header of your output.
The second one is telling the serializer which character encoding to use
for the output.
[...]
I used both xml and html (to see, if there is any difference in the
output, but there is none). In the Userdocs it says that you shouldnt't
And after serializing, are you still having "&8221" in the output or is
it converted to "double-upper-nine" quotation mark?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
