Jean-Christian Imbeault wrote:
> David Emery wrote:
>
>>
>
>> There's more, and this is the biggie...
>>
>> '--enable-mbstring-enc-trans' should be '--enable-mbstr-enc-trans'
>
>
>
> That fixed most of my problems! Thanks!
>
> Now I just have a question concerning the use of "internal encodi
Jean-Christian Imbeault wrote:
> Yasuo Ohgaki wrote:
>
>>
>>> So what is the difference between mbstring.internal_encoding and
>>> mbstring.http_output?
>>
>>
>>
>> I suppose you've read the manual pages... I may really need to
>> add more description...
>
>
>
> Yes, I read them over and over
are they using at this time?
Thanks,
-jeff
-Original Message-
From: Jean-Christian Imbeault [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 11, 2002 1:48 PM
To: [EMAIL PROTECTED]
Subject: Re: [PHP-I18N] Re: mbstring: Japanese: encoding conversion not
Lew Mark-Andrews wrote:
>
Lew Mark-Andrews wrote:
>
> As I also have a deep interest in Japanese-related PHP matters, I'd like to
> say thanks guys for providing these insights and information. This is the
> most legitimate traffic this list has had in months!
This thread has been most informative! I tried many other v
Yasuo Ohgaki wrote:
>
>> So what is the difference between mbstring.internal_encoding and
>> mbstring.http_output?
>
>
> I suppose you've read the manual pages... I may really need to
> add more description...
Yes, I read them over and over :) Are you in charge of maintaning the
manual page
Jean-Christian Imbeault wrote:
> David Emery wrote:
>
>>
>> I found this...
>>
>> You have default_charset set to EUC-JP. It should be Shift_JIS. PHP
>> will set the outgoing headers to this value (that's what it's for)
>
>
>
> So what is the difference between mbstring.internal_encoding and
>I would have thought that ./configure should
>have complained that I had passed it an invalid flag ...
Apparently not. A couple of months ago the people from Sun who provide
unofficial upgrade packages for Cobalt Raq servers inadvertently compiled
PHP using "with" instead of "enable" for the mbst
Aha! Now I understand what's going on. Thanks for the lucid explanation
David!
I'll use EUC-JP for internal since that's what my pgsql wants its input
to be in and I'll spit out SJIS to browsers since most of them support
that automatically.
Yippee, I'm on my to being a PHP programmer ... eve
At 13:22 +0900 02.7.11, Jean-Christian Imbeault wrote:
>David Emery wrote:
>
>>
>
>>There's more, and this is the biggie...
>>
>>'--enable-mbstring-enc-trans' should be '--enable-mbstr-enc-trans'
>
>
>That fixed most of my problems! Thanks!
>
>Now I just have a question concerning the use of "inte
David Emery wrote:
>
> There's more, and this is the biggie...
>
> '--enable-mbstring-enc-trans' should be '--enable-mbstr-enc-trans'
That fixed most of my problems! Thanks!
Now I just have a question concerning the use of "internal encoding".
When I receive $test it is in EUC-JP (because I
David Emery wrote:
>
> I found this...
>
> You have default_charset set to EUC-JP. It should be Shift_JIS. PHP will
> set the outgoing headers to this value (that's what it's for)
So what is the difference between mbstring.internal_encoding and
mbstring.http_output?
Jc
--
PHP Internati
David Emery wrote:
>
> There's more, and this is the biggie...
>
> '--enable-mbstring-enc-trans' should be '--enable-mbstr-enc-trans'
>
> so the input encoding translation isn't actually compiled into your
> system.
That would explain a lot. I would have thought that ./configure should
hav
At 11:30 +0900 02.7.11, David Emery wrote:
>>
>>Unfortunately my server is behind a firewall (testing phase now). I'm
>>sending you the output as an html attachment (zipped because the plain
>>HTML is larger than 40k).
>
>I found this...
>
>You have default_charset set to EUC-JP. It should be Shi
At 10:38 +0900 02.7.11, Jean-Christian Imbeault wrote:
>I sent a reply to this thread last night only to find out this morning
>that messages over 4 bytes can't make it through. So here I go again :
>
>David Emery wrote:
>
>>
>> How about sending the entire output of phpinfo() (or putting it
I sent a reply to this thread last night only to find out this morning
that messages over 4 bytes can't make it through. So here I go again :
David Emery wrote:
>
> How about sending the entire output of phpinfo() (or putting it online
> somewhere I can see it)? I'll compare it to what c
Jean-Christian Imbeault wrote:
> I beleive that mbstring is working and it is my settings that are wrong
> *or* some environment variable (in either PHP, Apache, or my browsers).
>
> I am only asking for help in trying to identify and then fix the problem ^_^
So far, I cannot tell what's wrong. T
At 17:23 +0900 02.7.10, Jean-Christian Imbeault wrote:
>I totally agree that getting input conversion to work is the key to
>solving all my japanese related problems. The question now though is what
>is different from my system and yours?
>
>Any suggestions as to any other tests I can do to try
Yasuo Ohgaki wrote:
> mbstring is working well for me as well as many
> others.
I am not saying there is something wrong with mbstring.
> Automatic encoding detection is not perfect since
> one encoding is smilar to another.
> If things are setting up right, all you need to
> do is adding dum
mbstring is working well for me as well as many
others.
Automatic encoding detection is not perfect since
one encoding is smilar to another.
If things are setting up right, all you need to
do is adding dummy input. Add something like
in your form.
Then it may work as you want.
--
Yasuo Ohgaki
David Emery wrote:
>
> So it *doesn't* work on your system. Basically, if the input conversion
> doesn't happen then there is something wrong with your set-up. Maybe
> it's time to start over from scratch. Making sure you compile with both
> --enable-mbstring and --enable-mbstr-enc-trans migh
At 13:48 +0900 02.7.10, Jean-Christian Imbeault wrote:
>David Emery wrote:
>>so here's a really simple test that works as it should on my system. Try
>>it on yours and see if it's ok.
>
>
>It works, but there is one problem.
>
>When I enter some japanese into the form your program says:
>
>"The e
David Emery wrote:
>
> Something's fishy there.
Very.
> so here's a really simple test that works as it should
> on my system. Try it on yours and see if it's ok.
It works, but there is one problem.
When I enter some japanese into the form your program says:
"The encoding of variable tes
22 matches
Mail list logo
