Re: mod_plsql / dad / character set problem

In article <1153127944.699625_at_proxy.dienste.wien.at>, Laurenz Albe says...
> Sybrand Bakker <postbus_at_sybrandb.demon.nl> wrote:
> >>> On Fri, 23 Jun 2006 17:22:49 +0100, Jeremy <jeremy0505_at_gmail.com>
> >>> wrote:
> >>>
> >>>>So we feel as though we are caught between a rock and a hard place -
> >>>>cananyone suggest a setting taht might support all our needs (sure I
> >>>>haven't defined ALL out needs! - of course I mean something that
> >>>>supports western european accented characters as well as the Euro
> >>>>symbol)?
> >
> > I assume (but I admit I didn't verify it) utf8 supports the euro.
> > On the other hand, WE8ISO8859P15 can not be converted to WE8MSWIN1252
> > and vice versa, so what I was trying to say: if you convert your
> > database to an utf characterset, allegedly a superset of normal 8-bit
> > charactersets, any 8-bit client should convert correctly.
>
> Sybrand, this time your advice, which is usually well grounded and valuable,
> shows that you indeed did not verify the information you gave:
>
> - First, UTF-8 (AL32UTF8 in Oracle) will support all possible characters,
> including the Euro, so your first advice to convert to this character set
> is clearly a good solution.
>
> - Second, Windoes 1252 contains all printable characters of ISO 8859-15,
> so it should never be a problem to convert characters from WE8ISO8859P15
> to WE8MSWIN1252.
>
> - Third, unless your strings contain any of the dreaded Windows characters
> (like UNICODE 0x2014, the em dash, or UNICODE 0x201c, left double quotation
> mark), conversion from WE8MSWIN1252 to WE8ISO8859P15 will also work.
>
> A question for the original poster:
> What is the character set you are currently using?
>

Database is WE8ISO8859.

The DAD is defined as UTF8.

-- 

jeremy