|
|
Posted by Richard on 07/19/07 23:24
On Jul 19, 12:59 pm, "Jukka K. Korpela" <jkorp...@cs.tut.fi> wrote:
> Scripsit Richard:
>
> > In this case, do you think the author should have used something other
> > than UTF-8 because his page was pure ASCII,
>
> He could have used US-ASCII, ISO-8859-1, or even windows-1252. Now that
> support to UTF-8 in web browsers is rather universal, it doesn't matter much
> that you declare it even in cases where your data is really ASCII. On the
> other hand, declaring UTF-8 even if you really use ASCII used to help
> Netscape 4 into doing the right thing with entity references. But that's
> past winter's snow now. What remains is that people who read the source code
> get puzzled with the declaration of UTF-8.
>
> > save for the HTML entity?
>
> The entity reference doesn't make the data non-ASCII: it consists of ASCII
> characters that represent, by a special convention, a particular character.
>
> > Or do you think the author should have employed other
> > features supported by UTF-8?
>
> I'm not saying he _should_, just that it puzzles me why he didn't. (I can
> imagine some reasons, like editors that cannot handle real UTF-8.) If your
> authoring software supports UTF-8, wouldn't you want to see a real
> apostrophe instead of a cryptic reference like ’ when you read the
> source code?
>
> --
> Jukka K. Korpela ("Yucca")http://www.cs.tut.fi/~jkorpela/
Hey Yukka,
Thanks for your further comments. I feel a lot smarter today than I
did yesterday :-)
Best wishes,
Richard
[Back to original message]
|