please fix a probrem with encoding

6 views
Skip to first unread message

鈴木晋

unread,
Mar 17, 2011, 2:34:02 AM3/17/11
to person...@googlegroups.com
Hi,

We're running twitter bots which broadcast every post in PersonFinder by using API.
etc...

Now, we are facing a problem with encoding.
Some data are posted in SHIFT_JIS and these data are currently shown as such (also url encoded).
These are examples.



I don't know the exact reason why this happens, but I guess the main reason is mobile- phone posting.

We've already fixed this problem in our bots by using mb_convert_encoding (PHP),
but people still can't see the original page correctly.
Users would be confused if they move to these pages.

Refugees are only able to use mobile phones, not PC, 
so fixing this problem will help a lot of sheltering people! 
I hope someone will fix this problem.


SHIN Suzuki

山田友典

unread,
Mar 17, 2011, 10:44:15 AM3/17/11
to person...@googlegroups.com, Alice Bonhomme-Biais, 鈴木晋
Alice

This is critical problem for Japanese users of both post and search.

At resist phase, maybe the easiest way to fix is check the character
encoding used to submit and if necessary, convert the params into
utf-8 before stored in DB.
At response phase, since Japanese GARAKE(not smartphone) can NOT
handle any encode but shift-jis, convert data into shift-jis.


2011/3/17 鈴木晋 <shino...@gmail.com>:

> --
> You received this message because you are subscribed to the Google Groups
> "personfinder" group.
> To post to this group, send email to person...@googlegroups.com.
> To unsubscribe from this group, send email to
> personfinder...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/personfinder?hl=en.
>

--
-----------------------------------------------
山田 友典
tomonori...@gmail.com
-----------------------------------------------

Ka-Ping Yee

unread,
Mar 17, 2011, 6:07:03 PM3/17/11
to person...@googlegroups.com, 山田友典, Alice Bonhomme-Biais, 鈴木晋
Hi, thank you for reporting this.

We're aware of this problem and are working on it.


—Ka-Ping Yee
Google Crisis Response
Reply all
Reply to author
Forward
0 new messages