We don't have current plans to fix this issue. The problem isn't around
utf-8, but rather around non-space separated languages. Our language
processing experts described the effort required, and it's a pretty large
project, and may be computationally impractical in the current streaming
architecture. There is a workaround, albeit a generally impractical one:
take the firehose and perform the language parsing on your end.
On Mon, Jun 28, 2010 at 1:34 AM, sjoonk <sjo...@gmail.com> wrote:
> I know current Twitter Streaming API do not support utf-8 track
> As an CJK engineer, I hope this feature will implemented so soon.
> Does anybody know when will be supported this feature in Twitter
> Streaming API??