Re: Re: creole suggested changes to handle encodings

Hans Lellelid wrote:
> Because no one has needed/asked for it yet. :)  We do have encoding
> transformations in Propel (using iconv).  I definitely wouldn't want to
> make iconv a requirement for Creole, but in your diffs it did look like
> it would only be used if the 'encoding' param were set in the DSN.

The problem of dealing with encodings will become more and more common
with the use of unicode/utf-8 as web standard and with the increasing
number of Indian, Chinese and Japanese surfers :-)

>  I
> don't know about setting the output_encoding in non-BC Creole, however.
>  It seems messy for Creole to be discovering page encodings, so perhaps
> it would have to be part of the DSN (...which also seems wrong). 

Why not ? can be copied from the real version with an on-the-fly
conf->changeValue().

> I'll
> discuss w/ Creole developers to think about how to implement this in our
> version.

Ok, good.
-- 
Jean-Christophe Michel
_______________________________________________
dev mailing list
dev-PnctHDZWAvB/Cz2I37pSEPZ4XP/[email protected]
http://lists.binarycloud.com/mailman/listinfo/dev