<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Subject double-escaped in the message view</title> 
  <pubDate>Fri, 10 Apr 2026 17:52:44 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/8185</link> 
  <atom:link rel="self" type="application/rss+xml" title="Subject double-escaped in the message view" href="https://bugs.horde.org/ticket/8185/rss" /> 
  <description>Subject double-escaped in the message view</description> 
 
   
   
  <item> 
   <title>In the message view, the subject header is double-escaped (n</title> 
   <description>In the message view, the subject header is double-escaped (not the one used in the header, but the one below To: ). So instead of seeing:



Re: New Message -&gt; Attachment Button / Firefox 3



I see:



Re: New Message -&amp;gt; Attachment Button / Firefox 3





Given that this duplicates the header we might just remove it, too?</description> 
   <pubDate>Mon, 13 Apr 2009 21:41:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8185#t53637</link> 
  </item> 
   
  <item> 
   <title>Fixed (this was due to the URL linking code added several we</title> 
   <description>Fixed (this was due to the URL linking code added several weeks ago).



Also, it makes more sense to remove the duplicate subject info in the header - now that we link URLs in the subject, it makes more sense to display this with the other headers anyway.  I&#039;ve removed this duplicate subject info in both IMP and the pop-up DIMP display.</description> 
   <pubDate>Wed, 15 Apr 2009 05:42:00 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8185#t53657</link> 
  </item> 
   
  <item> 
   <title>Disagree - the subject line is relevant for scanning and now</title> 
   <description>Disagree - the subject line is relevant for scanning and now it&#039;s much harder to pick up at a glance. If that means dropping links from the subject I think it&#039;s more than a fair trade (yes, I asked for that one also I know).</description> 
   <pubDate>Wed, 15 Apr 2009 10:04:09 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8185#t53658</link> 
  </item> 
   
  <item> 
   <title>&gt; Disagree - the subject line is relevant for scanning and n</title> 
   <description>&gt; Disagree - the subject line is relevant for scanning and now it&#039;s 

&gt; much harder to pick up at a glance. If that means dropping links from 

&gt; the subject I think it&#039;s more than a fair trade (yes, I asked for 

&gt; that one also I know).



But subject display in the header looks awful.  And for long subjects, it is *very* difficult to read (and you can&#039;t truncate - there needs to be at least one place where the full subject is viewable).  The better solution is to highlight/move the Subject header display - not to display the subject in the header.</description> 
   <pubDate>Thu, 16 Apr 2009 20:05:56 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8185#t53673</link> 
  </item> 
   
  <item> 
   <title>&gt; But subject display in the header looks awful.  And for lo</title> 
   <description>&gt; But subject display in the header looks awful.  And for long 

&gt; subjects, it is *very* difficult to read (and you can&#039;t truncate - 

&gt; there needs to be at least one place where the full subject is 

&gt; viewable).  The better solution is to highlight/move the Subject 

&gt; header display - not to display the subject in the header.



Think about preview in the list page. Having even a fragment of the subject (which will often be the whole subject anyway) in the header is really important imo. I have no problem with having the subject fragment in the header and then the full one later, but then imo we should truncate the one in the header (which I used to do, and someone reverted).</description> 
   <pubDate>Fri, 17 Apr 2009 04:41:56 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8185#t53735</link> 
  </item> 
   
  <item> 
   <title>&gt; I have no problem with having the subject 

&gt; fragment in </title> 
   <description>&gt; I have no problem with having the subject 

&gt; fragment in the header and then the full one later, but then imo we 

&gt; should truncate the one in the header (which I used to do, and 

&gt; someone reverted).



I can live with this.  Reverted initial commit and re-added truncation in header (at 100 chars).</description> 
   <pubDate>Tue, 19 May 2009 15:01:00 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8185#t54252</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git for this ticket:

Bug #8185: F</title> 
   <description>Changes have been made in Git for this ticket:

Bug #8185: Fix double encoding of subjects.

http://git.horde.org/diff.php/imp/lib/UI/Message.php?rt=horde-git&amp;r1=bbdb7ec0f76401f339f207c0b376cb68014af47b&amp;r2=48d0a5284f91e28c4e7f3cfc8f3cee7b1b119ae9</description> 
   <pubDate>Wed, 13 Jan 2010 00:01:40 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8185#t57551</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git for this ticket:

Ticket #8185</title> 
   <description>Changes have been made in Git for this ticket:

Ticket #8185: Revert &quot;Don&#039;t show subject in page header.&quot;
This reverts commit ed1e359c809354bee6175215a63a10402ae22c68.
Truncate subject text in header also.

http://git.horde.org/diff.php/imp/message.php?rt=horde-git&amp;r1=a253d734b1b1fc2b8b9376ddddeb5fdb7fd86e7e&amp;r2=35ad9c6b347a412d110a8eac57564b7be9f94e6e</description> 
   <pubDate>Wed, 13 Jan 2010 00:02:37 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8185#t57566</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
