Tickets :: [#12409] Charset issue with paged twitter content

Summary	Charset issue with paged twitter content
Queue	Horde Base
Queue Version	Git master
Type	Bug
State	Resolved
Priority	1. Low
Owners	mrubinsk (at) horde (dot) org
Requester	jan (at) horde (dot) org
Created	06/25/2013 (4396 days ago)
Due
Updated	06/27/2013 (4394 days ago)
Assigned
Resolved	06/27/2013 (4394 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

06/27/2013 09:45:08 PM	Michael Rubinsky	Comment #3 State ⇒ Resolved	Reply to this comment
Not sure why you were only seeing this when fetching more content - the original content and the additional content all come through the same code. Anyway, this should be fixed now (at least if fixed the few test tweets I made in German).

06/27/2013 09:43:57 PM	Git Commit	Comment #2	Reply to this comment
Changes have been made in Git (master): commit 87629f9962a326502b37aec5f545fee6c5dcb4f9 Author: Michael J Rubinsky <mrubinsk@horde.org> Date: Thu Jun 27 17:42:57 2013 -0400 Be kind to multibyte text. ~~Bug: 12409~~ horde/services/twitter/index.php \| 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-) http://git.horde.org/horde-git/-/commit/87629f9962a326502b37aec5f545fee6c5dcb4f9

06/25/2013 07:45:31 PM	Jan Schneider	Comment #1 Priority ⇒ 1. Low Patch ⇒ No Milestone ⇒ Assigned to Michael Rubinsky Queue ⇒ Horde Base Summary ⇒ Charset issue with paged twitter content Type ⇒ Bug State ⇒ Assigned	Reply to this comment
If fetching more content into the twitter block, sometimes the charset of the returned content is messed up, i.e. double utf-8 encoded. This can be seen with German translation for example, which contains umlauts in the timeline text.