Matthew Holloway wrote:
Andrew Cunningham wrote:
LOL, i enjoyed the wording.
Considering the document character set of HTML4 is Unicode, if it
can't be displayed in UTF-8 in a browser, then it can't be displayed
using entitiies or NCRs either ;)
Generally I agree, although one good thing about entities (including
NCRs of course) is that it'll typically come up as a "?" when it's
unknown rather than mangled as ’. So it'll break more gracefully.
a slight correction: NCRs by definition are always know. the question
mark could inticate a number of different problems, not limited to, but
including lack of appropriate fonts available (although thats more
likely to be a missing/.notdef glyph rather than a question mark) or the
character has been mangled by a script or module on a web site's back
end, etc.
while seeing something like "’" instead is a completely different
story, i.e. either the http header or the meta element in the web page
are indicating the wrong encoding, or in some cases no encoding is
declared. NCRs are defined in terms of the Document Character Set for
HTML, and are thus independant of the character encoding used to display
individual pages. But using the most appropraite character encoding for
the document is the best approach.
Each is an example of very different problems or issues with a web page,
and shouldn't be lumped in together.
But as I indicated in a previous email:
"Use of NCRs and other entities should be rare occurances for language
challenged environments"
The reality is that some tools are very poor at handling Unicode, and
NCRs are at times a necessary evil.
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************
