[BlueOnyx:15082] Re: YUM updates for 5106R/5107R/5108R

Hisao SHIBUYA shibuya at alpha.or.jp
Fri Apr 4 00:45:34 -05 2014


Hi Michael,

>> But, as you know with original codes, Japanese use entered through GUI
>> stored into CODB using EUC-JP. So I changed to UTF-8 when I released
>> at major version up.
> 
> Yeah, I had seen your 5200R code where you made that transition. But I
> might have missed the part where you changed the CODB-submit from EUC-JP
> to UTF-8.

Understood, but it’s not your fault, it is difficult to understand Japanese
encoding.



> As it is at the moment Japanese text such as this ...
> 
> 私は休暇中だ。後で私に連絡してください。
> 
> ... gets stored by CODB as this:
> 
> get 169 . Email
> [...]
> 102 DATA vacationMsg =
> "\347\247\201\343\201\257\344\274\221\346\232\207\344\270\255\343\201\240\343\200\202\345\276\214\343\201\247\347\247\201\343\201\253\351\200\243\347\265\241\343\201\227\343\201\246\343\201\217\343\201\240\343\201\225\343\201\204\343\200\202"
> [...]
> 
> I'm not even sure what charset that might relate to.

I checked on my BlueQuartz 5200R, the result as same as you tested.
And, this file is written in UTF-8.
The result of vavationMsg looks like corrupted, cceclient doesn’t support multibyte
to display, because of why.

Please install nkf you want to know the encoding, if you want.
[root at bq2 245]# cat Email.vacationMsg 
私は休暇中だ。後で私に連絡してください。

[root at bq2 245]# nkf --guess Email.vacationMsg 
UTF-8


>> If you are OK, I’ll check it out and take care of this with you.
> 
> That would be much appreciated, Hisao.
> 
> During this last update I took the approach of editing
> /usr/sausalito/ui/libPhp/I18n.php.
> 
> The functions get(), getHml(), getJs() (and the related interpolate
> functions) now convert all locales into UTF-8. Regardless of the
> encoding they were in before.
> 
> There is also a new function called I18n::Utf8Encode() that can be used
> to turn strings into UTF-8.

Thank you, I’ll check your change set.
Now, I set up BlueOnyx 5108R using ISO and I’ll add some user with Japanese
before update to latest.
I’ve read and look the images from Eiji’s email, I can imagine a few reasons
and points for this corruption.


> However, I did not change how data is stored in CODB. Which might
> contribute to the problem.

I agree with you.
We shouldn’t change data on the same platform.

Thanks,
Hisao





More information about the Blueonyx mailing list