Special characters get munged by TwitterFeed
My blog has this headline:
St. John's Morning Show Puts a Cap on Homelessness
...BUT...
TwitterFeed grabs it and spits it back out as:
St. John & # 8 2 1 7 ; s Morning Show Puts a Cap on Homelessness
(I had to put spaces in between so it would come out okay.)
Yuck. It happens to other characters as well, like the double-quote.
Can this be made a priority for fixing.
St. John's Morning Show Puts a Cap on Homelessness
...BUT...
TwitterFeed grabs it and spits it back out as:
St. John & # 8 2 1 7 ; s Morning Show Puts a Cap on Homelessness
(I had to put spaces in between so it would come out okay.)
Yuck. It happens to other characters as well, like the double-quote.
Can this be made a priority for fixing.
10
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The best solution from the company
-
For some reason getsatisfaction has lost a whole lot of this thread. There was a very long discussion, and in the end the upshot was that twitterfeed correctly posts entities like "& # 8 2 1 7 ;" (again, spaces are only there so the web browser doesn't turn it into a quote here), but that some clients don't render the entities correctly. This issue typically affected desktop clients like thwirl (not sure if that's fixed now), while the texts render correctly via the web.
The company says
this solves the problem
-
Inappropriate?Could you let me know the URL of your feed that contains examples of these and I'll look into it. I've done quite a lot of work around trying to make sure posts get encoded correctly (e.g. around double-byte issues), so it's a bit of a tricky area to make changes.
Yours is certainly a special case - special characters and quotes shouldn't (and usually don't) cause a problem, so it may be related to the original encoding of your feed. As I said, let me know the URL of the feed that shows these issues, and I'll see what I can do. -
Inappropriate?I'm having the same problems with single quotes and ellipsis (...) I use these pretty frequently in my blog, so this is a bit disappointing. I just signed up for twitterfeed yesterday and the first few posts were all jumbled.
I’m disappointed
-
This is happening on both of my websites, I just discovered... the same symbols are garbled when twitterfeed pulls them:
http://www.comicmix.com/rss/
http://www.mindpollution.org/feed/atom/ -
Inappropriate?Disappointing that this was reported 7 months ago and still not corrected.
I’m disappointed
-
Inappropriate?For some reason getsatisfaction has lost a whole lot of this thread. There was a very long discussion, and in the end the upshot was that twitterfeed correctly posts entities like "& # 8 2 1 7 ;" (again, spaces are only there so the web browser doesn't turn it into a quote here), but that some clients don't render the entities correctly. This issue typically affected desktop clients like thwirl (not sure if that's fixed now), while the texts render correctly via the web.
The company says
this solves the problem
-
I'm seeing it in the web-based version (on both Safari and Firefox): http://twitter.com/mnindy/statuses/93... -
Hi Paul, this was related to a problem with encodings at twitter's end, caused by some recent changes they did. It was fixed about 12 hours ago, as far as I can see - you can confirm it in your mnindy feed which contains so-called rich quotes which now render ok again, but for a while the entities themselves were printed. -
Thanks so much, Mario. It appears to be fixed. -
Inappropriate?ah, you're right, it's right on the web but not in twitterific, where i saw it.
-
Inappropriate?Mario, can you look at my feed and see if you can help?
http://www.williamsfortexas.com/artic...
Thanks. -
Could you elaborate on what the problem is? -
Inappropriate?I see the dev has replied that it's an issue with client software, just updating to say that I see this issue on Twitterific.
I’m bummed
-
Inappropriate?I think that the problem could be solved on TwitterFeed's side if they added code to convert the "& # 8 2 1 7 ;" in the RSS feed to the corresponding UTF8 apostrophe character, before sending it to Twitter. If TwitterFeed won't do this, somebody could build some kind of converter that sits in between.
I’m eagerly waiting for a fix.
-
Inappropriate?I too have this problem of the ' getting translated into misc characters. From the Twitter web client it looks fine, but when I look at my posts on Tweetie and on TweetDeck the ' get translated into ’ I use Twitterfeed from my wordpress blog, and my twitter account is /GeorgeONeill. Any suggestions on the fix would be appreciated. Perhaps it is not a Twitterfeed issue? Thanks.
-
Inappropriate?Interesting, in my above post the garbled characters were actually translated into an ' automatically. Let me separate the characters with a space so they will stay: & # 8 2 1 7 ;
-
Inappropriate?There's an explanation (if not necessarily a solution) in this thread here: http://getsatisfaction.com/twitterfee...
-
Inappropriate?We're posting via twitters web interface - twitterfeed - faccebook page. Swedish special characters such as "ÅÄÖ" is shown like Ã¥! etc. Is there a solution to this?
I’m frustrated
-
Yes, we're aware of this, we haven't yet found a way to post HTML entities or non-english characters via the Facebook Stream.publish API. We're not alone in this, lots of other developers seem to have the same issue, so not sure right now where the problem lies, but will continue to pursue this. -
Swe special characters are working now! -
Excellent, thanks for the update, we did make a couple of changes to how we post to facebook, so I'm glad it's working better!
Loading Profile...



EMPLOYEE

