Hi

RH8.0 with 1.3.27 to FC3 2.0.52 upgrade.

2.0.52 I now notice that some pages which worked before now show ? for some
chars. (£ - ')
Browser (I.E6) encoding shows UTF-8 yet switching to western fixes the
pages.
what do i need to do to apache to get the ? showing the correct values.

Mark

On Tue, 29 Mar 2005, Mark D Smith wrote:

> X-Newsreader: Microsoft Outlook Express 6.00.2800.1437

Fix first your newsreader^W Outlook Express before you try
to manage web servers:

Tools > Options > Send
Mail Sending Format > Plain Text Settings > Message format MIME
News Sending Format > Plain Text Settings > Message format MIME
Encode text using: None

> RH8.0 with 1.3.27 to FC3 2.0.52 upgrade.
>
> 2.0.52 I now notice that some pages which worked before now show ? for some
> chars. (? - ')

Give URLs!

> Browser (I.E6) encoding shows UTF-8 yet switching to western fixes the
> pages.

Give URLs!

> what do i need to do to apache to get the ? showing the correct values.

You need to tell us the URLs.


And read
http://www.w3.org/International/O-HTTP-charset.html
http://ppewww.ph.gla.ac.uk/~flavell/...t/ns-burp.html

--
Top-posting.
What's the most irritating thing on Usenet?

"Andreas Prilop" <nhtcapri@rrzn-user.uni-hannover.de> wrote in message
news:Pine.GSO.4.44.0503291705350.12607-100000@s5b004...
> On Tue, 29 Mar 2005, Mark D Smith wrote:
>
> > X-Newsreader: Microsoft Outlook Express 6.00.2800.1437
>
> Fix first your newsreader^W Outlook Express before you try
> to manage web servers:
>
> Tools > Options > Send
> Mail Sending Format > Plain Text Settings > Message format MIME
> News Sending Format > Plain Text Settings > Message format MIME
> Encode text using: None
>
> > RH8.0 with 1.3.27 to FC3 2.0.52 upgrade.
> >
> > 2.0.52 I now notice that some pages which worked before now show ? for
some
> > chars. (? - ')
>
> Give URLs!
>
> > Browser (I.E6) encoding shows UTF-8 yet switching to western fixes the
> > pages.
>
> Give URLs!
>
> > what do i need to do to apache to get the ? showing the correct values.
>
> You need to tell us the URLs.
>
>
> And read
> http://www.w3.org/International/O-HTTP-charset.html
> http://ppewww.ph.gla.ac.uk/~flavell/...t/ns-burp.html
>
> --
> Top-posting.
> What's the most irritating thing on Usenet?
>

Hi

Not sure how OE got changed been posting for since w95 without complaint.

http://www.leasingworld.co.uk/html/advertising.php

1. should read - Displays not ? Displays & £15.00 not ?15.00
4. company?s should read company's

and a few others in there.

will follow up links tomorrow.

Mark

On Tue, 29 Mar 2005, Mark D Smith wrote:

[disrespectful fullquote, complete with sig, snipped]

> Not sure how OE got changed been posting for since w95 without
> complaint.

Probably because other participants were too polite to point out your
failings.

> http://www.leasingworld.co.uk/html/advertising.php
>
> 1. should read - Displays not ? Displays & £15.00 not ?15.00

You really aren't capable of posting unusual characters to usenet, as
Andreas already cautioned you. You'd do better to describe what
you're seeing.

> 4. company?s should read company's
>
> and a few others in there.

Your server says that you are sending utf-8 encoding:

Date: Tue, 29 Mar 2005 18:53:19 GMT
Server: Apache/2.0.52 (Fedora)
X-Powered-By: PHP/4.3.9
Content-Length: 1426
Connection: close
Content-Type: text/html; charset=UTF-8

On the evidence of your actual page, this seems unlikely. You'd
probably best get advice from your server admin about your server
settings.

On Tue, 29 Mar 2005, Mark D Smith wrote:

> Not sure how OE got changed been posting for since w95 without complaint.

You need to define an encoding ("charset") if you want to transmit
special, non-ASCII characters. This is the same problem as with
your web server!

> http://www.leasingworld.co.uk/html/advertising.php

Your server sends "charset=UTF-8" whereas you have an additional
ersatz <META charset=ISO-8859-1>:
http://validator.w3.org/check?uri=ww...dvertising.php

Delete the <META charset> line which has no use since your web server
sends already an encoding (charset). Set up your server correctly
http://www.w3.org/International/O-HTTP-charset.html
so that it sends "charset=ISO-8859-1". For example, write
AddCharset ISO-8859-1 php
into your .htaccess file.


Consider writing all special Latin-1 characters as entities such as &quid;
http://ppewww.ph.gla.ac.uk/~flavell/...t/checklist#s1
Then it doesn't matter whether the encoding is UTF-8 or ISO-8859-1.

--
Top-posting.
What's the most irritating thing on Usenet?