Loading Profile...
Ping.fm encoding problem?
There seems to be a UTF-8 character encoding problem. I updated my status with
is watching 'seven pounds'
and twitter got the status right but fb and plurk got
is watching 'seven pounds'.
So the question is: is ping.fm overencoding or plurk and fb underencoding?
Some links:
http://twitter.com/artemr
http://www.plurk.com/ArtemR
is watching 'seven pounds'
and twitter got the status right but fb and plurk got
is watching 'seven pounds'.
So the question is: is ping.fm overencoding or plurk and fb underencoding?
Some links:
http://twitter.com/artemr
http://www.plurk.com/ArtemR
I’m confused
2
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.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I think, I'm having a similar problem. On the recent posts page, http://ping.fm/recent/, it shows:
http://ping.fm/p/ePuvP - Und hier ging der ganze M�ll hin.
Note the broken ü in Müll (or M�ll).
But on the post page http://ping.fm/p/ePuvP, it looks well.
I’m confused
1 Comment
Add a comment
This solves the problem
-
Umlaute (ie. äöü) and other UTF-8 charcters (eg. „ or “) are also broken when ping.fm updates the LinkedIn status.
As you can see on http://twitter.com/alexs77/status/110..., I wrote:
hat Karten für „Sieben Leben“ gekauft. Sah in der Werbung nett aus. Mal schauen, wie es in echt ist.
At LinkedIn, this reads:
Alexander hat Karten f�r �Sieben Leben� gekauft. Sah in der Werbung nett aus. Mal schauen, wie es in echt ist
Es you can see, the ü in "für" (or f�r) is broken and the charachters before and after „Sieben Leben“ are broken. -
Inappropriate?I *DO* have this problem.
http://twitter.com/alexs77/status/108...
It reads: =?utf-8?Q?Fl=C3=B6ten
It should read: "Flöten".
I send this from my Nokia 6300 as an MMS email.
I’m unhappy about that limitation
-
Inappropriate?Alex, our problems are of completely different nature, but sure, add it along.1 Comment Add a comment
This solves the problem
-
Hm, yes, I think you're right - these might be different encoding problems.
But the common thing is, that they are encoding problems :) -
Inappropriate?Yes, the keyword is the same :) but the problem is fundamentally different:
- in my case, content is potentially encoded an extra time into an html entity
- in your case, encoding is messed up altogether
-
1 Comment Add a comment
This solves the problem
-
Web, mail and/or IM (from Gmail, in this case).
-
Inappropriate?I post from the web and through IM.
-
Inappropriate?Posting in Finnish via SMS, ä's and ö's were dropped from my status somewhere along the way to both FB and Identi.ca.
EMPLOYEE
