Our servers dont seem to be displaying all pound signs correctly.
I think this is because of ASCII pound signs verses UTF-8 or iso-8859-1.
My client is using an old version of MS Frontpage.
They are however displaying properly on other servers.
Is there a "one line hack" in 'httpd.conf' that will solve this.
Many thanks in advance,
Aaron
i ended up converting =A3 signs to £ throughout html & db data....
i'm sure there's a better way but it worked...
On Jun 26, 12:10 pm, "dj.brainst...@gmail.com"
> i ended up converting =A3 signs to £ throughout html & db data....
> i'm sure there's a better way but it worked...
yeah basically your client must save in utf if the data is then served
in utf, most clients wont know how, so dont force a particular charset
when serving their files, and then the ball in firmly in their court
to set the appropriate meta tag in the html. However that tag isnt
looked at with xhtml and IE parses the document "intelligently" anyway
to find its own opinion as to what the encoding should be.
Personally I set the server up to do utf8 where I control the clients
software, and then set their software to encode to utf - on sites
where there are multiple languages this is normal proactise I guess,
or else as you say you end up with htmlentities all over the place, or
documents each with their own encoding, and to me it makes sense to
set things up once, and just ask that they "do it that way" php has
conversion function which can blast through a whole lod of docs
quickly.
check out mb_convert_encoding and if you ever have exisitng docs that
your client would like altered, just chuck them through that, and its
done.
>check out mb_convert_encoding and if you ever have exisitng docs that
>your client would like altered, just chuck them through that, and its done.
Is iconv and mbstring relevant ?
Aaron
On Jun 26, 4:39 pm, "Aaron Gray"
> >check out mb_convert_encoding and if you ever have exisitng docs that
> >your client would like altered, just chuck them through that, and its done.
>
> Is iconv and mbstring relevant ?
>
> Aaron
yeah I guess so, you could also have a php auto_prepended script which
converted the encodings that were not utf8 but I guess that would not
be too transparent for some people who would find they had less
control than they wanted.
I would recommend not setting the default character set to utf if your
users are not encoding in that char set:
(from the manual)
"AddDefaultCharset utf-8
AddDefaultCharset should only be used when all of the text resources
to which it applies are known to be in that character encoding and it
is too inconvenient to label their charset individually."
so mentioning php was just in case you were still dealing with your
client and needed a fix for some documents if they had agreed to go
utf8 in future