ðÒÉ×ÅÔ!
Jean-Christian Imbeault wrote:
> Worry and worry a lot ...
I already do :( The most terrorizing thing is that desolating "There are
no user contributed notes for this page." that appears almost on every
function in the online manual.
And the fact that there is no pointer for people in
Alberto Serra wrote:
>
> I'll be extending an existing content-repository
> to add chinese text management in the winter so I'll better start to
> worry about it.
Worry and worry a lot ...
> As for your problem, I am afraid you would better turn to a japanese
> programmers' mailing list.
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
ðÒÉ×ÅÔ!
> Jean-Christian Imbeault wrote:
>> My page is always in the same charset, the problem is that the user
>> input might not be ...
Okay, I went thru a bit of docs on the japanese multibyte problem and
got some surface understanding of the problem. Yes, since char
dimensions are going to
ðÒÉ×ÅÔ!
Jean-Christian Imbeault wrote:
> Impossible, though it would be nice. Postgres can only accept one
> charset for it's input not multiple.
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.
>> *c
Thanks for the ideas Alberto but what I relly want is to understand how
to use the mbstring library, not how to implement a new solution.
mbstring is supposed to do everything I want, I guess I am just not
quite understanding how to use it yet.
Also in regard to some things you said,
> Now, l
ðÒÉ×ÅÔ!
As for deciding what your user language/charset requests are (in terms
of his/her browser settings) you might use this function
// this function remains unchanged. It returns an array
// 0 : negotiated charset
// 1 : negotiated lancode
function negotiated_langset()
ðÒÉ×ÅÔ!
Jean-Christian Imbeault wrote:
> Warning: PostgreSQL query failed: ERROR: Invalid EUC_JP character
> sequence found (0x8140) in /www/htdocs/test.php on line 31
>
> So I assumed that I should first convert user input into EUC-JP.
Now, let's make sure we have a clear background:
1)
8 matches
Mail list logo
