Re: [tlug] OT-Japanese in PHP

[Mark Sargent <powderkeg@example.com>]

Erin D. Hughes via info@example.com wrote:

> Mark Sargent wrote:
>
>> Erin D. Hughes via info@example.com wrote:
>>
>>> David E wrote:
>>>
>>>> From: Mark Sargent <powderkeg@example.com> on Date: Wed, 25 
>>>> May 2005 17:31:49 +0900
>>>>
>>>>
>>>>> Erin D. Hughes via info@example.com wrote:
>>>>>
>>>>>
>>>>>> Mark Sargent wrote:
>>>>>>
>>>>>>
>>>>>>> Hi All,
>>>>>>> output_handler = mb_output_handler
>>>>>>> mbstring.language = Japanese
>>>>>>> mbstring.internal_encoding = UTF-8
>>>>>>> mbstring.http_input = auto
>>>>>>> mbstring.http_output = SJIS
>>>>>>> mbstring.encoding_translation = On
>>>>>>> mbstring.detect_order = auto
>>>>>>> mbstring.substitute_character = none
>>>>>>> mbstring.internal_encoding = EUC-JP
>>>>>>>
>>>>>>> Now, I think I still haven't got the page that requires J, 
>>>>>>> displayed right, yet. Full code is below. Can anyone see any 
>>>>>>> mistakes..? Cheers.
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>> You haven't given any details on what seems wrong with the output.
>>>> This is kind of obvious, but have you made sure the text in the
>>>> database is in the sme encoding as you have mbstring.internal_encoding
>>>> set to? (You have it set twice, to different values in your config
>>>> above - I assume the last one set gets used, but safer to just make up
>>>> your mind, don't you think?)
>>>>
>>>> Dave
>>>>
>>> Dave I agree that is another valid point.
>>>
>>> I think he should first rule out the other problems though
>>>
>>> A. Make a test page with some Japanese text in HTML and test. IS 
>>> that OK? If yes go to B
>>>
>>> B. Make a test page in PHP with the same text and test. IS that OK? 
>>> If yes go to C.
>>>
>>> C. Make a test PHP page that pulls data from the DB. And in 3 
>>> separate lines with each line (data in the db encoded differently IE 
>>> UTF-8, Shift-jis and EUC) and see what comes out right.
>>>
>>> Also it is important to check the co-location in your DB if your 
>>> using MYSQL 4.XXXXXXXXXX there are very specific settings that I 
>>> have had a lot of trouble with my self in the past..... But that is 
>>> another issue I am sure.
>>>
>>> E./
>>>
>>>
>> Test A:
>> Hondaは、スポーティで安心感のある走りに加え、上質な内外装、高い安全性 
>> 能により好評を得ているアコードシリーズ（アコード／アコードワゴン）を 
>> 改良 し、本日より全国のホンダクリオ店から発売する。
>>
>> 　アコードでは、充実した装備の24TLにエアロパーツや17インチアルミホ 
>> イール、スポーツサスペンションを装備した「スポーツパッケージ」を、ア 
>> コードワゴンでは、2.0Lエンジンを搭載したベーシックなタイプ「20A」を、 
>> それぞれ新 たに設定。お客様の幅広い要望に応えられるタイプ設定とした。
>> 　また今回、アコード20A、20ELのFF車と、アコードワゴン20A、24EのFF車は 
>> 「平成17年排出ガス基準75％低減レベル（★★★★低排出ガス車）」認定を新た 
>> に取得し、高い環境性能を実現するとともにグリーン税制の適用対象を拡大 
>> した。
>>
>>
>> Result Test A(Comes out as coded in UTF-8)
>> Honda縺ｯ縲√せ繝昴・繝・ぅ縺ｧ螳牙ｿ・─縺ｮ縺ゅｋ襍ｰ繧翫↓蜉 縺医∽ｸ願ｳｪ縺ｪ 
>> 蜀・､冶｣・・ｫ倥＞螳牙・諤ｧ閭ｽ縺ｫ繧医ｊ螂ｽ隧輔ｒ蠕励※縺・ｋ繧｢繧ｳ繝ｼ繝 
>> 峨す繝ｪ繝ｼ繧ｺ・医い繧ｳ繝ｼ繝会ｼ上い繧ｳ繝ｼ繝峨Ρ繧ｴ繝ｳ・峨ｒ謾ｹ濶ｯ縺励∵ 
>> 悽譌･繧医ｊ蜈ｨ蝗ｽ縺ｮ繝帙Φ繝繧ｯ繝ｪ繧ｪ蠎励°繧臥匱螢ｲ縺吶ｋ縲・縲繧｢繧ｳ 
>> 繝ｼ繝峨〒縺ｯ縲∝・螳溘＠縺溯｣・ｙ縺ｮ24TL縺ｫ繧ｨ繧｢繝ｭ繝代・繝・ｄ17繧､ 
>> 繝ｳ繝√い繝ｫ繝溘・繧､繝ｼ繝ｫ縲√せ繝昴・繝・し繧ｹ繝壹Φ繧ｷ繝ｧ繝ｳ繧定｣・ｙ 
>> 縺励◆縲後せ繝昴・繝・ヱ繝・こ繝ｼ繧ｸ縲阪ｒ縲√い繧ｳ繝ｼ繝峨Ρ繧ｴ繝ｳ縺ｧ縺ｯ 
>> 縲・.0L繧ｨ繝ｳ繧ｸ繝ｳ繧呈政霈峨＠縺溘・繝ｼ繧ｷ繝・け縺ｪ繧ｿ繧､繝励・0A縲 
>> 阪ｒ縲√◎繧後◇繧梧眠縺溘↓險ｭ螳壹ゅ♀螳｢讒倥・蟷・ｺ・＞隕∵悍縺ｫ蠢懊∴繧峨 
>> ｌ繧九ち繧､繝苓ｨｭ螳壹→ 縺励◆縲・縲縺ｾ縺滉ｻ雁屓縲√い繧ｳ繝ｼ繝・0A縲・ 
>> 0EL縺ｮFF霆翫→縲√い繧ｳ繝ｼ繝峨 Ρ繧ｴ繝ｳ20A縲・4E縺ｮFF霆翫・縲悟ｹｳ謌・7蟷 
>> ｴ謗貞・繧ｬ繧ｹ蝓ｺ貅・5・・ｽ取ｸ帙Ξ 繝吶Ν・遺・笘・・笘・ｽ取賜蜃ｺ繧ｬ繧ｹ 
>> 霆奇ｼ峨崎ｪ榊ｮ壹ｒ譁ｰ縺溘↓蜿門ｾ励＠縲・ｫ倥＞迺ｰ蠅・ｧ閭ｽ繧貞ｮ溽樟縺吶ｋ 
>> 縺ｨ縺ｨ繧ゅ↓繧ｰ繝ｪ繝ｼ繝ｳ遞主宛縺ｮ驕ｩ 逕ｨ蟇ｾ雎｡繧呈僑螟ｧ縺励◆縲・
>>
>> Now, I realized, after an email from Dave E that I had 
>> internal.encoding as UTF-8 although the database encoding is SJIS. I 
>> just wasn't fully understanding what all the settings were doing. 
>> I've now changed the internal to SJIS, double checked that the page 
>> is set for SJIS also, but, the page only displays if I either change 
>> it in the browser to UTF-8 or set the page to that(Test A page, that 
>> is). I've added below my settings. The original page, that displays 
>> the database content, which is set to Shift_JIS also still doesn't 
>> display, at all. Thoughts..? Cheers.
>>
>> EDIT: I went and copied the data from the database into the Test A 
>> page and it also would only display correctly if I set it to UTF-8 in 
>> the browser. So, this narrows it down to, that the code is being 
>> coded to UTF-8. I don't understand this, as I've set all settings to 
>> SJIS. Obviously I'm missing something very fundamental, which I'm 
>> sure will pointed out to me, real quick. Cheers, again.
>>
>> Mark Sargent.
>>
>>
>> mbstring.detect_order auto
>>
>> mbstring.encoding_translation On
>>
>> mbstring.func_overload 0
>>
>> mbstring.http_input Auto
>>
>> mbstring.http_output SJIS
>>
>> mbstring.internal_encoding SJIS
>>
>> mbstring.language Japanese
>>
>> mbstring.substitute_character no value
>>
>
> OK I got you Mark so again can I ask if you commented out the line 
> that says AddDefaultCharset UTF-8
>
> Change it too
> #AddDefaultCharset UTF-8
>
> That will ALWAYS make all your pages display as UTF-8 as you just 
> stated is happening.
>
Hi All,

Erin, I would, if it existed. I even tried adding AddDefaultCharset  
Shift_jis..perhaps it is wrong.? Cheers.

Mark Sargent.


#
AddDefaultCharset Shift_JIS
AddCharset ISO-8859-1  .iso8859-1  .latin1
AddCharset ISO-8859-2  .iso8859-2  .latin2 .cen
AddCharset ISO-8859-3  .iso8859-3  .latin3
AddCharset ISO-8859-4  .iso8859-4  .latin4
AddCharset ISO-8859-5  .iso8859-5  .latin5 .cyr .iso-ru
AddCharset ISO-8859-6  .iso8859-6  .latin6 .arb
AddCharset ISO-8859-7  .iso8859-7  .latin7 .grk
AddCharset ISO-8859-8  .iso8859-8  .latin8 .heb
AddCharset ISO-8859-9  .iso8859-9  .latin9 .trk
AddCharset ISO-2022-JP .iso2022-jp .jis
AddCharset ISO-2022-KR .iso2022-kr .kis
AddCharset ISO-2022-CN .iso2022-cn .cis
AddCharset Big5        .Big5       .big5
# For russian, more than one charset is used (depends on client, mostly):
AddCharset WINDOWS-1251 .cp-1251   .win-1251
AddCharset CP866       .cp866
AddCharset KOI8-r      .koi8-r .koi8-ru
AddCharset KOI8-ru     .koi8-uk .ua
AddCharset ISO-10646-UCS-2 .ucs2
AddCharset ISO-10646-UCS-4 .ucs4
AddCharset UTF-8       .utf8