Tweet Button using shift_jis character encoding

JuN_RestificaR · 2011-07-15T00:02:22.000Z

Hi…

 Please help me.. I have a problem regarding the japanese encoding and im

using tweet button. Using shift_jis the tweet function doesnt work and
I tried to use utf-8 and it works well. The problem is our japanese data
was generated by shift_jis method…

chanian · 2011-07-15T02:58:24.000Z

Hi @junwarlord1, we have seen this problem reported before and it is a known issue that we are working on fixing as soon as possible. I will update this thread when the issue has been fixed!

chanian · 2011-07-19T22:27:54.000Z

We have pushed a fix that addresses this specific SHIFT_JS encoding issues on our end. Please let us know if you continue to have problems!

Thanks again for reporting this issue.

sidorvm · 2011-08-24T06:24:00.000Z

I still have problems with displaying tweet button on pages in Shift_JIS encoding.
Below is tweet button code.

royston_olivera · 2012-02-23T17:14:16.000Z

has this been fixed? or any genius have a work around for this? I cannot change the charset of the page

chanian · 2012-02-23T17:52:07.000Z

This appears to be a new bug on our end, we should be sending back UTF-8 char-encoding. I’ll work to get a fix in asap, and update this thread once it is out. Check back tomorrow!

royston_olivera · 2012-04-24T18:26:00.000Z

@chanian Is this fixed? lately we are seeing that the tweet button isn’t rendering on pages that are having content-type as shift_jis. It doesn’t happen in all browsers. We could reproduce it on FF7 on MAC.

Even the firebug console displays a error in widget.js

Screenshot: http://letsshare.comxa.com/tt_error.png

chanian · 2012-04-26T18:34:26.000Z

hmmm, looks like this issue came up again.
I’ll create an issue ticket for you to watch, and escalate it.

thanks for your patience, and sorry about this!

chanian · 2012-04-26T20:41:22.000Z

And the ticket to watch: https://dev.twitter.com/issues/332

royston_olivera · 2012-04-26T23:28:09.000Z

Thanks @chanian

endform · 2012-06-20T18:41:54.000Z

Hey guys. We released a fix for this issue last night. Thanks for your patience!

niall · 2016-02-06T23:01:51.167Z