Don't know the answer to your question exactly but how about
transforming all user input into something like unicode/UTF-8 (or
UTF-16) and *then* putting it into the DB?
That way all the DB input has the same charset.
Jc
Alberto Serra wrote:
> ������!
>
> Jean-Christian Imbeault wrote:
>
>> Alberto Serra wrote:
>>
>>> I hope you mean one charset per language. Otherwise I can just cancel
>>> POstgres from my list of usable engines. But yes, it can't be just one.
>>
>>
>> I'm no pgsql expert but I think that yes, it will only accept input in
>> one charset. But for charsets that use only 8-bits I think you can
>> insert data that is in more than one charset.
>>
>> But for charsets that use more than 8-bits I think pgsql actually
>> checks that the input is in the charset the DB expects it to be in.
>
>
> Can anyone say something about this? It would mean that a content
> repository ported to Postgres would not be able to hold chinese, korean
> and japanese content at the same time. Quite a big minus, I'd say.
>
> Any chinese, korean or japanese programmers on this list? (I put the
> countries list in alphabetical order, no personal preferences implied).
>
> ����
> ��������
> ����
>
>
> @-_=}{=_-@-_=}{=_-@-_=}{=_-@-_=}{=_-@-_=}{=_-@-_=}{=_-@-_=}{=_-@
>
> LoRd, CaN yOu HeAr Me, LiKe I'm HeArInG yOu?
> lOrD i'M sHiNiNg...
> YoU kNoW I AlMoSt LoSt My MiNd, BuT nOw I'm HoMe AnD fReE
> tHe TeSt, YeS iT iS
> ThE tEsT, yEs It Is
> tHe TeSt, YeS iT iS
> ThE tEsT, yEs It Is.......
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
