Tickets :: [#8811] Test unicode in Horde Twitter client/block

6.0.0-beta1

11/8/25

Summary	Test unicode in Horde Twitter client/block
Queue	Horde Base
Queue Version	Git master
Type	Bug
State	Resolved
Priority	1. Low
Owners	Horde Developers (at)
Requester	chuck (at) horde (dot) org
Created	01/02/2010 (5789 days ago)
Due
Updated	01/04/2010 (5787 days ago)
Assigned
Resolved	01/04/2010 (5787 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

01/04/2010 07:54:58 PM	Chuck Hagenbuch	State ⇒ Resolved

01/04/2010 06:24:04 PM	Michael Rubinsky	Comment #5 State ⇒ Not A Bug	Reply to this comment
The display issues I was having is evidently due to the fact that the font I was using doesn't contain the character. So, move along, nothing to see here... ;)

01/04/2010 05:48:05 PM	Jan Schneider	Comment #4	Reply to this comment
Looks perfectly fine in the timeline here.

01/02/2010 04:24:22 AM	Michael Rubinsky	Comment #3	Reply to this comment
..and this looks like it's due to running the tweet through Horde_Text_Filter_Text2html. Can't find the culprit though. Even making sure that we pass the correct charset as a parameter seems to still break the encoding.

01/02/2010 04:00:16 AM	Michael Rubinsky	Comment #2	Reply to this comment
The links work correctly, but the on-screen display shows the little unicode glyph/box instead of the character.

01/02/2010 01:22:45 AM	Chuck Hagenbuch	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Test unicode in Horde Twitter client/block Queue ⇒ Horde Base Assigned to Horde Developers Milestone ⇒ Patch ⇒ No State ⇒ Assigned	Reply to this comment
See the parenthetical here: http://daringfireball.net/linked/2009/11/27/df-twitter I'd do this but my portal is broken right now.