Loading Profile...
Conversion of characters to HTML entities is ruining tweet display
I understand that part of the 140-character limit is figuring out what counts as a "character" (given HTML entities, alternate character encodings, etc.), but please please please don't resort to the dreaded truncation+ellipsis. This is ruining my tweets, and (today in particular, which has been quote-heavy on my Follow list) many others as well. Worse, it's often pushing important attribution out of the view, or (even worser) mangling the links by truncating to a partial URL.
To aid in comprehension, here is an example from a recent tweet of mine. First, the way it looks on the detail page (correct):
Then, the way it looks on the index pages (and in Twitterific, et al):
However you have to solve this, *please* stop the tweet truncation! I love Twitter too much to have it be so poopy in this regard.
To aid in comprehension, here is an example from a recent tweet of mine. First, the way it looks on the detail page (correct):
Then, the way it looks on the index pages (and in Twitterific, et al):
However you have to solve this, *please* stop the tweet truncation! I love Twitter too much to have it be so poopy in this regard.
I’m perturbed
11
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.
-
Inappropriate?I agree. I hate the truncation. It's screwing up my snurls and tinyurls.
I’m frustrated
-
Inappropriate?This is a real issue. < is one character not 4 (<). If i write 138 chars and the last one is a < or >, then twitter will see it is over 140 chars. Also if you type & lt ; (without the spaces) in twitter it converts them to the encoded chars. what in the world?
I’m unhappy
-
Inappropriate?I don't get it. You already have a 140 char limit. Why the hell would you add a truncate(msg, 140something) to the view when you already know the length of msg will be =<140>s not like some accidental 141 char message would crash the entire list view layout.
I’m angry
-
Inappropriate?Hating the truncation. A character should be a character should be a character, the way it was before the recent "upgrade." This is a step backward, not forward.
I’m frustrated
-
Inappropriate?This ruins a lot of my tweets. You should store the message as it is in the database, independent of how you're intending to present it (HTML, API, whatever).
Agh! I really hope that this gets fixed soon...
I’m frustrated
