I look after 7 pc's at work, all running Windows XP Pro, all with IE6 SP1.

I notice that IE6 fails to identify Unicode (UTF8) pages. As the number of
websites using this encoding increases, I have resorted to setting it
manually under View-Encoding.

Since all of the machines I know have this problem, I was suprised not to be
able to pick up any hits searching newsgroups. Do I happen to have the only
6 machines that exhibit the problem?

A sample website: www.dabs.com where every price shows has  before the £
sign, and "you're in home > product View" is mutated into "youâ?Tre in home
> product View"

If I am missing a setting please tell me...

Keith P.

This is what I got from the source code of the site.

<meta http-equiv="Content-Type" content="text/html; charset='iso-8859-1'" />


--

Henri Leboeuf
Web page: http://www.generation.net/~hleboeuf/index.htm


"Keith Pocock" <(E-Mail Removed)> wrote in message
news:md7ub.190402$(E-Mail Removed)...
>
> I look after 7 pc's at work, all running Windows XP Pro, all with IE6 SP1.
>
> I notice that IE6 fails to identify Unicode (UTF8) pages. As the number
of
> websites using this encoding increases, I have resorted to setting it
> manually under View-Encoding.
>
> Since all of the machines I know have this problem, I was suprised not to
be
> able to pick up any hits searching newsgroups. Do I happen to have the
only
> 6 machines that exhibit the problem?
>
> A sample website: www.dabs.com where every price shows has  before the £
> sign, and "you're in home > product View" is mutated into "youâ?Tre in
home
> > product View"
>
> If I am missing a setting please tell me...
>
> Keith P.
>
>

"H Leboeuf" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)
> This is what I got from the source code of the site.
>
> <meta http-equiv="Content-Type" content="text/html;
> charset='iso-8859-1'" />
>
> "Keith Pocock" <(E-Mail Removed)> wrote in message
> news:md7ub.190402$(E-Mail Removed)...
>>
>> I look after 7 pc's at work, all running Windows XP Pro, all with
>> IE6 SP1.
>>
>> I notice that IE6 fails to identify Unicode (UTF8) pages. As the
>> number of websites using this encoding increases, I have resorted to
>> setting it manually under View-Encoding.
>>
>> Since all of the machines I know have this problem, I was suprised
>> not to be able to pick up any hits searching newsgroups. Do I happen
>> to have the only 6 machines that exhibit the problem?
>>
>> A sample website: www.dabs.com where every price shows has  before
>> the £ sign, and "you're in home > product View" is mutated into
>> "youâ?Tre in
> home
>>> product View"
>>
>> If I am missing a setting please tell me...
>>
>> Keith P.

The HTML on that page is too complicated for me, but my IE6 SP1 chooses
UTF-8 and displays the page properly.
In Viiew | Encoding is AutoSelect checked?

--
Frank Saunders, MS-MVP, IE/OE
Please respond in Newsgroup. Do not send email
http://www.fjsmjs.com

When back to the site this morning and my View/Encoding was changed to UTF8
for that page.
Looking at the source code again I was unable to find any reference to UTF8
on the page.
How UTF8 is selected when viewed is beyond me also.

--

Henri Leboeuf
Web page: http://www.generation.net/~hleboeuf/index.htm




"Frank Saunders, MS-MVP" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "H Leboeuf" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)
> > This is what I got from the source code of the site.
> >
> > <meta http-equiv="Content-Type" content="text/html;
> > charset='iso-8859-1'" />
> >
> > "Keith Pocock" <(E-Mail Removed)> wrote in message
> > news:md7ub.190402$(E-Mail Removed)...
> >>
> >> I look after 7 pc's at work, all running Windows XP Pro, all with
> >> IE6 SP1.
> >>
> >> I notice that IE6 fails to identify Unicode (UTF8) pages. As the
> >> number of websites using this encoding increases, I have resorted to
> >> setting it manually under View-Encoding.
> >>
> >> Since all of the machines I know have this problem, I was suprised
> >> not to be able to pick up any hits searching newsgroups. Do I happen
> >> to have the only 6 machines that exhibit the problem?
> >>
> >> A sample website: www.dabs.com where every price shows has  before
> >> the £ sign, and "you're in home > product View" is mutated into
> >> "youâ?Tre in
> > home
> >>> product View"
> >>
> >> If I am missing a setting please tell me...
> >>
> >> Keith P.
>
> The HTML on that page is too complicated for me, but my IE6 SP1 chooses
> UTF-8 and displays the page properly.
> In Viiew | Encoding is AutoSelect checked?
>
> --
> Frank Saunders, MS-MVP, IE/OE
> Please respond in Newsgroup. Do not send email
> http://www.fjsmjs.com
>

> A sample website: www.dabs.com where every price shows
> has  before the £ sign, and "you're in home > product View"
> is mutated into "youâ?Tre in home > product View"

Has it been fixed?

No sign of either of those problems. In particular I suspect the text
is different because I can't see that item in the Home menu.
The closest that I have to "product View" would be Shop by Brand.
In any case all of the headings that I have seen display the apostrophe
in "you're in home" correctly. My View Encoding is always Auto-Select,
Unicode (UTF-8).

You may be interested in my suggestion to Andrew McDonald
in his similar discussion: IE chooses wrong page encoding


HTH

Robert Aldwinckle
---


"Keith Pocock" <(E-Mail Removed)> wrote in message
news:md7ub.190402$(E-Mail Removed)...
>
> I look after 7 pc's at work, all running Windows XP Pro, all with IE6 SP1.
>
> I notice that IE6 fails to identify Unicode (UTF8) pages. As the number of
> websites using this encoding increases, I have resorted to setting it
> manually under View-Encoding.
>
> Since all of the machines I know have this problem, I was suprised not to be
> able to pick up any hits searching newsgroups. Do I happen to have the only
> 6 machines that exhibit the problem?
>
> A sample website: www.dabs.com where every price shows has  before the £
> sign, and "you're in home > product View" is mutated into "youâ?Tre in home
> > product View"
>
> If I am missing a setting please tell me...
>
> Keith P.
>
>