Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

text display in Mac browsers

0 views
Skip to first unread message

Scott

unread,
Oct 30, 2003, 12:18:35 AM10/30/03
to
Both MSIE 5 and Safari seem to have difficulty displaying certain
characters. E.g., "cliché" (accent over the last "e") is displayed as
"clich&#233"
None of the text encoding settings seem to change this.

Is this type of thing a result of improper page setup, or a browser
problem?

--
to respond, change "spamless.invalid" with "optonline.net"
please mail OT responses only

Keith Whaley

unread,
Oct 30, 2003, 10:20:36 AM10/30/03
to
The accented "e" displays a diacritical mark. It's one of the high or
'extended' ASCII 8-bit text characters.
Regular text, with 7-bit ASCII characters numbered below no. 128 are
regular alphabet, numeric and other punctuation characters.
Anything more exotic than that are "high ASCII" or 8-bit characters,
such as your é and many browsers won't support them.

Oddly enough, some low ASCII characters are not displayed correctly in
some web sites text, such as an apostrophe, which is ASCII number 39!
Go figure...
I'm guessing that those sites cannot display 8-bit characters...for some reason.

keith whaley

renlog

unread,
Oct 30, 2003, 10:22:47 AM10/30/03
to
In article <heimdall-B4C21A...@news4.srv.hcvlny.cv.net>,
Scott <heim...@spamless.invalid> wrote:

> Both MSIE 5 and Safari seem to have difficulty displaying certain
> characters. E.g., "cliché" (accent over the last "e") is displayed as
> "clich&#233"
> None of the text encoding settings seem to change this.
>
> Is this type of thing a result of improper page setup, or a browser
> problem?

I don't have that problem with any browser, except (and rarely) on
certain pages and that's always because the proper html entity was not
used to create the accented letter.
Now, if that happens every time (try going to several French sites to
verify that) I don't know what to tell you, except that it's not the
browser's problem.

René

Scott

unread,
Oct 30, 2003, 11:22:53 AM10/30/03
to
In article <renlog-E2162C....@news04.east.earthlink.net>,
renlog <ren...@pipeline.com> wrote:

> I don't have that problem with any browser, except (and rarely) on
> certain pages and that's always because the proper html entity was not
> used to create the accented letter.
> Now, if that happens every time (try going to several French sites to
> verify that) I don't know what to tell you, except that it's not the
> browser's problem.


Try here:
<http://dir.salon.com/ent/movies/feature/2001/10/23/mulholland_drive_anal
ysis/index.html?pn=3>

Scroll down; near the bottom, look at the bold text that begins
Fine: "So it was all just a dream."
How does "cliché" appear for you?

Tom Harrington

unread,
Oct 30, 2003, 12:06:23 PM10/30/03
to
In article <heimdall-B4C21A...@news4.srv.hcvlny.cv.net>,
Scott <heim...@spamless.invalid> wrote:

> Both MSIE 5 and Safari seem to have difficulty displaying certain
> characters. E.g., "cliché" (accent over the last "e") is displayed as
> "clich&#233"
> None of the text encoding settings seem to change this.
>
> Is this type of thing a result of improper page setup, or a browser
> problem?

Must be the page, because in some quick testing it seems that not only
does Safari correctly render "&#233;" as an accented 'e', it's also
forgiving enough to render even some mis-formatted codes as the accented
'e' as well. What site(s) are you seeing this problem on?

--
Tom "Tom" Harrington
Macaroni, Automated System Maintenance for Mac OS X.
Version 1.4: Best cleanup yet, gets files other tools miss.
See http://www.atomicbird.com/

Eric Albert

unread,
Oct 30, 2003, 12:45:59 PM10/30/03
to
In article <heimdall-44DC99...@news4.srv.hcvlny.cv.net>,
Scott <heim...@spamless.invalid> wrote:

> In article <renlog-E2162C....@news04.east.earthlink.net>,
> renlog <ren...@pipeline.com> wrote:
>
> > I don't have that problem with any browser, except (and rarely) on
> > certain pages and that's always because the proper html entity was not
> > used to create the accented letter.
> > Now, if that happens every time (try going to several French sites to
> > verify that) I don't know what to tell you, except that it's not the
> > browser's problem.
>
>
> Try here:
> <http://dir.salon.com/ent/movies/feature/2001/10/23/mulholland_drive_anal
> ysis/index.html?pn=3>
>
> Scroll down; near the bottom, look at the bold text that begins
> Fine: "So it was all just a dream."
> How does "cliché" appear for you?

It appears as &#233, but that's correct. Here's the HTML:
&amp;#233;
It should be this:
&#233;

-Eric

--
Eric Albert ejal...@stanford.edu
http://rescomp.stanford.edu/~ejalbert/

renlog

unread,
Oct 30, 2003, 9:47:46 PM10/30/03
to
In article <3FA12C37...@dslextreme.com>,
Keith Whaley <kei...@dslextreme.com> wrote:

> The accented "e" displays a diacritical mark. It's one of the high or
> 'extended' ASCII 8-bit text characters.
> Regular text, with 7-bit ASCII characters numbered below no. 128 are
> regular alphabet, numeric and other punctuation characters.
> Anything more exotic than that are "high ASCII" or 8-bit characters,
> such as your é and many browsers won't support them.

How many browsers would that be?
So far as I can see, Safari, Explorer, Camino and Omniweb support them
very nicely (at least in French; can't speak for other languages).

Scott

unread,
Oct 31, 2003, 9:58:29 AM10/31/03
to
In article <afaber-BA1E14....@reader2.panix.com>,
Alice Faber <afa...@panix.com> wrote:

> Improperly coded? The page source has "clich&amp;#233" which indeed does
> display as "clich&#233"; from what Tom Harrington posted upthread, the
> coding should be "clich&#233;". It's not Safari's fault if Salon
> miscoded their page.


Looks like those aren't the only errors; I used the "Report Error" link
on the page, and it's coded as

mailto:tech...@salon.com/

(extraneous slash)

Matt Broughton

unread,
Oct 31, 2003, 10:30:31 AM10/31/03
to
In article
<heimdall-65F440...@news4-ge1.srv.hcvlny.cv.net>,
Scott <heim...@spamless.invalid> wrote:

> In article <afaber-BA1E14....@reader2.panix.com>,
> Alice Faber <afa...@panix.com> wrote:
>
> > Improperly coded? The page source has "clich&amp;#233" which indeed does
> > display as "clich&#233"; from what Tom Harrington posted upthread, the
> > coding should be "clich&#233;". It's not Safari's fault if Salon
> > miscoded their page.
>
>
> Looks like those aren't the only errors; I used the "Report Error" link
> on the page, and it's coded as
>
> mailto:tech...@salon.com/
>
> (extraneous slash)

Yes, there appear to be several errors. It's a bit hard to pinpoint
exactly what errors there are as the page does not specify a DOCTYPE.
That being the case, perhaps it is meant to be HTML 4.01 Transitional?
If so, you can see what the w3c.org validator has to say:
<http://validator.w3.org/check?uri=http%3A%2F%2Fdir.salon.com%2Fent%2Fmov
ies%2Ffeature%2F2001%2F10%2F23%2Fmulholland_drive_analysis%2Findex.html%3
Fpn%3D3&charset=%28detect+automatically%29&doctype=HTML+4.01+Transitional
>

--
Matt Broughton
Only relatives are absolute.

Scott

unread,
Oct 31, 2003, 10:40:20 AM10/31/03
to
In article <walterwego-DF6DE...@corp.supernews.com>,
Matt Broughton <walte...@macosx.com> wrote:

... and the "report error" mailto: address bounces.

0 new messages