Hi Ron,
Your script should send a response header as follows:
Content-Type: text/html; charset=UTF-8
and in your HTML source you should have a matching meta-tag:
meta http-equiv=Content-Type content=text/html; charset=UTF-8 /
If you're using CA then the response header can be defined by:
Hi Mike
On Mon, 2008-09-08 at 09:23 +0100, Mike Tonks wrote:
You got me there. I'm using mysql with utf8 and this works fine for
me. I tend to agree with Peter that utf8 is the way to go.
I've tried to go the 'utf8' way
(1) httpd.conf:
PerlSetEnv PGCLIENTENCODING UTF8
(2) startup.pl:
Hi Ron,
Don't know if this will come through correctly via email - I'll mail
you direct with file as an attachment - but I ended up writing a
simple perl script to run from the command line to test my utf8 data
display and retrieval from the database. You will need to alter the
database calls to
Hi Mike
On Tue, 2008-09-09 at 11:18 +0100, Mike Tonks wrote:
Hi Ron,
Don't know if this will come through correctly via email - I'll mail
Yep, received. $many x $thanx;
In summary - I found I did not need encode or decode functions, but
did need to 'use utf8' and binmode utf8, and when
Hi Mike
Ok. Here's the output.
Don't know if this will come through correctly via email - I'll mail
[EMAIL PROTECTED]:~$ ./test_utf8.pl
Test phrases - display and concatenation
Benützername [UTF8 on, non-ASCII, 12 characters 13 bytes]
Se déconnecter [UTF8 on, non-ASCII, 14 characters 15
You got me there. I'm using mysql with utf8 and this works fine for
me. I tend to agree with Peter that utf8 is the way to go.
475 | info | CGIApp: CÔTE D'IVOIRE. Encoding: UTF8 off, ASCII, 3
characters 3 bytes | 2008-09-08 09:27:03.887059
3 chars? WTF?
The code is:
$self - log($_ -
Ron Savage wrote on 9/5/08 7:51 PM:
Hi Folks
Here is the set up (details below):
o An fcgid scripts calls...
o A module based on CGI::Application::Dispatch, which calls...
o My module, which reads country names from Postgres and displays them
This works, so Ivory Coast is displayed as
I don't have a full explanation, but the second character looks like a
wrongly encoded double-byte utf8 issue, i.e. utf8 character (double
byte) being displayed as two characters. Do you see 'wide character
in print anywhere?
This can happen when you concatenate two string together if the uft8
Hi Mike
On Sun, 2008-09-07 at 09:33 +0100, Mike Tonks wrote:
I don't have a full explanation, but the second character looks like a
wrongly encoded double-byte utf8 issue, i.e. utf8 character (double
byte) being displayed as two characters. Do you see 'wide character
in print anywhere?
Hi Peter
On Sat, 2008-09-06 at 20:49 -0500, Peter Karman wrote:
Ron Savage wrote on 9/5/08 7:51 PM:
Hi Folks
Here is the set up (details below):
o An fcgid scripts calls...
o A module based on CGI::Application::Dispatch, which calls...
o My module, which reads country names from
Hi Folks
Here is the set up (details below):
o An fcgid scripts calls...
o A module based on CGI::Application::Dispatch, which calls...
o My module, which reads country names from Postgres and displays them
This works, so Ivory Coast is displayed as 'CÔte D'ivoire' (ignoring the
upper-case O
11 matches
Mail list logo