From: Wes Groleau on
On 06-16-2010 10:13, krishnananda wrote:
> My Safari (4.0.5) defaults to "Western (ISO Latin 1)". There is no
> setting for either "automatic" or "US ASCII". It has no problem with
> either page rendering the "~".

That's because the page happens to be encoded in your browser's
default. If the page were in UTF-8 and failed to say so, you
would see two or more odd characters instead of ã

--
Wes Groleau

Miss Universe had “lots of fun” in Guantanamo
http://Ideas.Lang-Learn.us/russell?itemid=1537
From: krishnananda on
In article <hvb6k6$lsl$1(a)news.eternal-september.org>,
Wes Groleau <Groleau+news(a)FreeShell.org> wrote:

> On 06-16-2010 10:13, krishnananda wrote:
> > My Safari (4.0.5) defaults to "Western (ISO Latin 1)". There is no
> > setting for either "automatic" or "US ASCII". It has no problem with
> > either page rendering the "~".
>
> That's because the page happens to be encoded in your browser's
> default. If the page were in UTF-8 and failed to say so, you
> would see two or more odd characters instead of ã

Nope.

Set the default to UTF-8, no problem.
Set it to Simplified Chinese, no problem.
From: Wes Groleau on
On 06-16-2010 15:22, krishnananda wrote:
> Wes Groleau<Groleau+news(a)FreeShell.org> wrote:
>> On 06-16-2010 10:13, krishnananda wrote:
>>> My Safari (4.0.5) defaults to "Western (ISO Latin 1)". There is no
>>> setting for either "automatic" or "US ASCII". It has no problem with
>>> either page rendering the "~".
>>
>> That's because the page happens to be encoded in your browser's
>> default. If the page were in UTF-8 and failed to say so, you
>> would see two or more odd characters instead of ã
>
> Nope.
>
> Set the default to UTF-8, no problem.
> Set it to Simplified Chinese, no problem.

Then they must have fixed the page. When I checked it,
it failed to identify its encoding. Consequently I (with
default at UTF-8) saw something odd.

Your default is used when the page doesn't say.

When the author does things right, the browser uses the
encoding header to render the page, instead of its default.

--
Wes Groleau

Here's a short essay on our primitive sense of community
http://Ideas.Lang-Learn.us/barrett?itemid=1524
From: dorayme on
In article <4c18c9b1$0$31691$c3e8da3(a)news.astraweb.com>,
Warren Oates <warren.oates(a)gmail.com> wrote:

> In article <dorayme-B0B75A.09200315062010(a)news.albasani.net>,
> dorayme <dorayme(a)optusnet.com.au> wrote:
>
> > I would be interested to get feedback on if anyone on any *Mac
> > OS* sees different between the two URLs above on any *Mac
> > browser* (apart from that one has two illustrated instances).
>
> Well, you may just be lucky with the one that doesn't use the
> "entities." One should always use the entities for them furriner
> letters.

Yes, it is a safe enough policy as long as you can get a good
grip on what is inside the unfurry circle and what is not.

> See, here's the thing: with
>
> http://dorayme.netweaver.com.au/jojo.html
>
> if I (with Opera, say, but any browser will do) change the encoding from
> "automatic" to "US Ascii" then your text goes into the toilet. Opera
> displays the tilded character as upper-case A tilde, followed by the
> sterling (British pound) symbol. Changing the encoding on your other
> site has no effect; both lines display correctly.
>

On my Opera 10.53 on Tiger, I have not been able to duplicate
your experience with either the above URL or

<http://dorayme.netweaver.com.au/jojo2.html>

Yes, I set the browser to "US Ascii" and quit and restarted it
several times? But Opera is quite a strange and slow responding
browser on my Tiger machine, perhaps give it a week?

> Also, &atilde is identical to &#227 so all of god's browsers should be
> able to see it.

Well, anyway, it might well be the safest policy to use entities.
But I would still be interested in the feedback I mentioned but
that I could verify somehow.

Even IE5 for Mac set to anything at all, however bizarre seems to
be unaffected! Perhaps the settings on MacIE5 are like the
buttons on some pedestrian crossings, they don't actually do
anything? <g>

--
dorayme
From: Wes Groleau on
On 06-16-2010 19:36, dorayme quoted:
>> > Also,&atilde is identical to&#227 so all of god's browsers should be
>> > able to see it.

But don't forget we're based on DARWIN, and our parent's logo is a
_devil_ and some of us use an incantation of "chmod 666"

and added:
> Well, anyway, it might well be the safest policy to use entities.
> But I would still be interested in the feedback I mentioned but
> that I could verify somehow.

Again,
1. use whatever characters are easiest for _you_ to read
2. Save as UTF-8
3. If you are using an editor that's too stupid to add the encoding
header, add it manually

Do that, and the user of any browser less than ten years old
will see it correctly unless he makes a conscious effort to mess it up.

--
Wes Groleau

He that complies against his will is of the same opinion still.
-- Samuel Butler, 1612-1680