Tickets :: [#8941] DIMP message display not formatted

6.0.0-alpha14

6/30/25

Summary	DIMP message display not formatted
Queue	IMP
Queue Version	Git master
Type	Bug
State	Not A Bug
Priority	2. Medium
Owners
Requester	jonathan (at) findyourfans (dot) com
Created	03/30/2010 (5571 days ago)
Due
Updated	04/01/2010 (5569 days ago)
Assigned	03/30/2010 (5571 days ago)
Resolved	03/31/2010 (5570 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

04/01/2010 05:20:36 AM	jonathan (at) findyourfans (dot) com	Comment #11	Reply to this comment
What component exactly are you referring to? I am using Apache httpd Your system locales. OK, thanks. I didin't realize Horde or IMP (or PHP) relied on system locales, especially since I hadn't had trouble with UTF-8 output before. I also hadn't realized that I didn't have any UTF-8 locales installed. As soon as I installed en_US.utf8, I didn't get the encoding warning from IMP any more.

03/31/2010 08:09:12 AM	Jan Schneider	Comment #10	Reply to this comment
What component exactly are you referring to? I am using Apache httpd Your system locales.

03/31/2010 08:08:18 AM	Jan Schneider	State ⇒ Not A Bug

03/31/2010 03:38:04 AM	jonathan (at) findyourfans (dot) com	Comment #9	Reply to this comment
Well, to begin with, you absolutely can NOT use DIMP on a non-UTF-8 browser. So the real ticket should be denying you access totally to dimp on that browser. Wherever the message encoding issues are coming from, I doubt they have much to do with the formatting problems I've described, since the latter resulted from missing HTML markup, not encoding or decoding errors. However, to muddy things even more, I can no longer reproduce the formatting problem. For a couple of days, I could consistently reproduce the problem in DIMP mode only, but now both regular and dynamic views seem to be displaying messages correctly. I'm starting to suspect this is the result of a cache inconsistency, but that's really just a wild guess.

03/31/2010 03:32:53 AM	jonathan (at) findyourfans (dot) com	Comment #8	Reply to this comment
This message probably comes from the server not supporting UTF-8, rather than the browser. You still should fix this, because Horde 4 will require UTF-8 support for both browser and server. What component exactly are you referring to? I am using Apache httpd 2.2.9 and have been serving UTF-8 documents for years. Do you mean there has to be UTF-8 support in PHP? I am using mod_php 5.2.6; is there something else I need? I've never had any trouble related to a lack of UTF-8 support before in many other PHP web applications. When displaying some messages, IMP puts "This message was written in a character set (UTF-8) other than your own." in a box above the message. I can view those exact same messages (served from the same IMAP server on the same host) using Roundcube (running on the exact same instance of Apache and PHP) with no issues at all and Firefox reports the encoding of the document is UTF-8.

03/31/2010 03:06:37 AM	jonathan (at) findyourfans (dot) com	Comment #7	Reply to this comment
Well, to begin with, you absolutely can NOT use DIMP on a non-UTF-8 browser. So the real ticket should be denying you access totally to dimp on that browser. I'm pretty sure that Firefox 3.6.3pre and Google Chrome 5.0.342.7 beta can handle UTF-8. I have been wondering what IMP means by "This message was written in a character set (UTF-8) other than your own."

03/30/2010 09:34:52 PM	Jan Schneider	Comment #6	Reply to this comment
This message probably comes from the server not supporting UTF-8, rather than the browser. You still should fix this, because Horde 4 will require UTF-8 support for both browser and server.

03/30/2010 07:51:33 PM	Michael Slusarz	Comment #5	Reply to this comment
Well, to begin with, you absolutely can NOT use DIMP on a non-UTF-8 browser. So the real ticket should be denying you access totally to dimp on that browser.

03/30/2010 07:30:28 PM	jonathan (at) findyourfans (dot) com	Comment #4 New Attachment: imp.png	Reply to this comment
Definitely don't see this. For comparison, here's the same message in normal IMP mode.

03/30/2010 07:27:30 PM	jonathan (at) findyourfans (dot) com	Comment #3 New Attachment: dimp.png	Reply to this comment
Definitely don't see this. Here's what I'm seeing.

03/30/2010 06:26:25 PM	Michael Slusarz	Comment #2 State ⇒ Feedback	Reply to this comment
Definitely don't see this.

03/30/2010 08:32:22 AM	jonathan (at) findyourfans (dot) com	Comment #1 Priority ⇒ 2. Medium State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Queue ⇒ IMP Summary ⇒ DIMP message display not formatted Type ⇒ Bug	Reply to this comment
When viewing normal plain text messages in the DIMP mode, there are no line breaks, so the text all runs together and is very difficult to read. In the traditional IMP mode, the message body text is displayed inside a '<div class="fixed leftAlign">' and newlines are converted to '<br>' but neither is true in DIMP mode.