<?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>Fwd: string is translated</title> 
  <pubDate>Fri, 10 Apr 2026 16:47:27 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/5674</link> 
  <atom:link rel="self" type="application/rss+xml" title="Fwd: string is translated" href="https://bugs.horde.org/ticket/5674/rss" /> 
  <description>Fwd: string is translated</description> 
 
   
   
  <item> 
   <title>compose.php uses an i18n&#039;able variant of the &#039;Fwd:&#039; tag whic</title> 
   <description>compose.php uses an i18n&#039;able variant of the &#039;Fwd:&#039; tag which indicates a forwarded message:



| $header[&#039;subject&#039;] = _(&quot;Fwd:&quot;);



Although not explicitly stated in RFC850, this is similarly to the &#039;Re:&#039; tag which is expected as-is but not as an translated string.



E.g. &#039;compose.php&#039; expects the english tag to decide whether a new tag shall be added:



| foreach (array(&#039;fwd:&#039;, &#039;fw:&#039;, &#039;(fwd)&#039;, &#039;[fwd]&#039;) as $signal) {





Using internationalized strings there results into subjects like



|  &quot;Fwd: WG: Fwd: P.ep: VS: 





Hence, there should not be used _(&quot;Fwd:&quot;) but plain &quot;Fwd:&quot; and &#039;Fwd:&#039; should be moved out of the _(...) in 



| $header[&#039;subject&#039;] = sprintf(_(&quot;Fwd: %u Forwarded Messages&quot;), count($msglist));

</description> 
   <pubDate>Mon, 27 Aug 2007 10:45:03 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5674#t36394</link> 
  </item> 
   
  <item> 
   <title>You can&#039;t really compare Fwd: with Re: because you usually r</title> 
   <description>You can&#039;t really compare Fwd: with Re: because you usually reply to messages forth and back often, but you don&#039;t usually forward a message several times. This was discussed in the past and decided to translate Fwd: because it&#039;s not that common for non-English speakers as Re: is.

But we should add the translated version of Fwd: to that array you are referencing if this isn&#039;t the case in IMP 4.2 already.</description> 
   <pubDate>Mon, 27 Aug 2007 15:30:05 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5674#t36410</link> 
  </item> 
   
  <item> 
   <title>do you really add the 43 translations (as of 4.1.4) of &#039;fwd:</title> 
   <description>do you really add the 43 translations (as of 4.1.4) of &#039;fwd:&#039; to this array?



Or at least: add a configuration option so that user can decide whether he wants the translated version or the common &#039;fwd:&#039; only? Even Outlook has such an option...</description> 
   <pubDate>Mon, 27 Aug 2007 15:36:29 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5674#t36414</link> 
  </item> 
   
  <item> 
   <title>&gt; do you really add the 43 translations (as of 4.1.4) of &#039;fw</title> 
   <description>&gt; do you really add the 43 translations (as of 4.1.4) of &#039;fwd:&#039; to this array?



No, only the translation of the current language. It&#039;s really not a common case that people with different languages forward messages one by one.



&gt; Or at least: add a configuration option so that user can decide 

&gt; whether he wants the translated version or the common &#039;fwd:&#039; only? 

&gt; Even Outlook has such an option...



I don&#039;t think this is an issue large enough to justify a setting.</description> 
   <pubDate>Mon, 27 Aug 2007 17:09:31 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5674#t36417</link> 
  </item> 
   
  <item> 
   <title>&gt; No, only the translation of the current language. It&#039;s rea</title> 
   <description>&gt; No, only the translation of the current language. It&#039;s really not a common case that people with different . languages forward messages one by one.



It is very common that people use regular mail clients (which set untranslated &#039;Fwd:&#039; tags). IMP would make them to &#039;&lt;local translation&gt;: Fwd:&#039;.





&gt; I don&#039;t think this is an issue large enough to justify a setting.



What is the issue to translate &#039;Fwd:&#039;?  Translating it is very uncommon (and execpt IMP, I know only one major MUA which is doing it be default).</description> 
   <pubDate>Mon, 27 Aug 2007 17:52:00 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5674#t36418</link> 
  </item> 
   
  <item> 
   <title>&gt;&gt; do you really add the 43 translations (as of 4.1.4) of &#039;f</title> 
   <description>&gt;&gt; do you really add the 43 translations (as of 4.1.4) of &#039;fwd:&#039; to this array?

&gt;

&gt; No, only the translation of the current language. It&#039;s really not a 

&gt; common case that people with different languages forward messages one 

&gt; by one.



Agreed.  And even if you do receive that rare forward from someone who speaks a different language, it is not that big of a deal.  Especially given the alternative of having to do a potentially expensive comparison of a long list of strings every time you want to view a message.



&gt;&gt; Or at least: add a configuration option so that user can decide

&gt;&gt; whether he wants the translated version or the common &#039;fwd:&#039; only?

&gt;&gt; Even Outlook has such an option...

&gt;

&gt; I don&#039;t think this is an issue large enough to justify a setting.



Agreed.</description> 
   <pubDate>Tue, 28 Aug 2007 18:01:06 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5674#t36431</link> 
  </item> 
   
  <item> 
   <title>&gt; And even if you do receive that rare forward from someone </title> 
   <description>&gt; And even if you do receive that rare forward from someone who speaks a different language



it&#039;s not only different language; it can be a different MUA too. Horde/IMP is the only MUA which enforces translation of the &#039;Fwd:&#039; string.



&gt; Especially given the alternative of having to do a potentially expensive comparison of a long list of strings every time



Exactly. That&#039;s why, &#039;Fwd:&#039; should be handled like &#039;Re:&#039; and never be translated.</description> 
   <pubDate>Tue, 28 Aug 2007 19:00:23 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5674#t36438</link> 
  </item> 
   
  <item> 
   <title>I see your point, but it looks like none of your arguments c</title> 
   <description>I see your point, but it looks like none of your arguments convinced any of the developers.</description> 
   <pubDate>Mon, 01 Oct 2007 23:36:57 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5674#t37275</link> 
  </item> 
   
  <item> 
   <title>Well, I was following the conversation. If most other client</title> 
   <description>Well, I was following the conversation. If most other clients don&#039;t translate Fwd, I don&#039;t think we should either.</description> 
   <pubDate>Tue, 02 Oct 2007 02:15:33 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5674#t37312</link> 
  </item> 
   
  <item> 
   <title>Outlook does. But this is probably a really bad example, it </title> 
   <description>Outlook does. But this is probably a really bad example, it even translates Re:.</description> 
   <pubDate>Tue, 02 Oct 2007 10:54:36 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5674#t37329</link> 
  </item> 
   
  <item> 
   <title>Accordingly http://www.web-blog.net/comments/P135_0_1_0/ (on</title> 
   <description>Accordingly http://www.web-blog.net/comments/P135_0_1_0/ (only german, first google hit for &quot;outlook rfc 850&quot;), outlook can be configured to use correct subject tags (inclusive &#039;Fwd:&#039;).



There is no way in Horde to use international &#039;Fwd:&#039;.</description> 
   <pubDate>Tue, 02 Oct 2007 11:00:41 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5674#t37330</link> 
  </item> 
   
  <item> 
   <title>Done for IMP 4.2.</title> 
   <description>Done for IMP 4.2.</description> 
   <pubDate>Tue, 02 Oct 2007 17:38:27 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5674#t37355</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
