Tickets :: [#5674] Fwd: string is translated

6.0.0-beta1

7/8/25

Summary	Fwd: string is translated
Queue	IMP
Queue Version	4.1.4
Type	Bug
State	Resolved
Priority	1. Low
Owners	chuck (at) horde (dot) org
Requester	ensc+horde (at) cvg (dot) de
Created	08/27/2007 (6525 days ago)
Due
Updated	10/02/2007 (6489 days ago)
Assigned	10/02/2007 (6489 days ago)
Resolved	10/02/2007 (6489 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

10/02/2007 05:38:27 PM	Chuck Hagenbuch	Comment #12 Assigned to Chuck Hagenbuch State ⇒ Resolved	Reply to this comment
Done for IMP 4.2.

10/02/2007 11:00:41 AM	ensc+horde (at) cvg (dot) de	Comment #11	Reply to this comment
Accordingly http://www.web-blog.net/comments/P135_0_1_0/ (only german, first google hit for "outlook rfc 850"), outlook can be configured to use correct subject tags (inclusive 'Fwd:'). There is no way in Horde to use international 'Fwd:'.

10/02/2007 10:54:36 AM	Jan Schneider	Comment #10	Reply to this comment
Outlook does. But this is probably a really bad example, it even translates Re:.

10/02/2007 02:15:33 AM	Chuck Hagenbuch	Comment #9 Summary ⇒ Fwd: string is translated State ⇒ Feedback	Reply to this comment
Well, I was following the conversation. If most other clients don't translate Fwd, I don't think we should either.

10/01/2007 11:36:57 PM	Jan Schneider	Comment #8 State ⇒ Not A Bug	Reply to this comment
I see your point, but it looks like none of your arguments convinced any of the developers.

08/28/2007 07:00:23 PM	ensc+horde (at) cvg (dot) de	Comment #7	Reply to this comment
And even if you do receive that rare forward from someone who speaks a different language it's not only different language; it can be a different MUA too. Horde/IMP is the only MUA which enforces translation of the 'Fwd:' string. Especially given the alternative of having to do a potentially expensive comparison of a long list of strings every time Exactly. That's why, 'Fwd:' should be handled like 'Re:' and never be translated.

08/28/2007 06:01:06 PM	Michael Slusarz	Comment #6	Reply to this comment
do you really add the 43 translations (as of 4.1.4) of 'fwd:' to this array? No, only the translation of the current language. It's really not a common case that people with different languages forward messages one 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. Or at least: add a configuration option so that user can decide whether he wants the translated version or the common 'fwd:' only? Even Outlook has such an option... I don't think this is an issue large enough to justify a setting. Agreed.

08/27/2007 05:52:00 PM	ensc+horde (at) cvg (dot) de	Comment #5	Reply to this comment
No, only the translation of the current language. It'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 'Fwd:' tags). IMP would make them to '<local translation>: Fwd:'. I don't think this is an issue large enough to justify a setting. What is the issue to translate 'Fwd:'? Translating it is very uncommon (and execpt IMP, I know only one major MUA which is doing it be default).

08/27/2007 05:09:31 PM	Jan Schneider	Comment #4	Reply to this comment
do you really add the 43 translations (as of 4.1.4) of 'fwd:' to this array? No, only the translation of the current language. It's really not a common case that people with different languages forward messages one by one. Or at least: add a configuration option so that user can decide whether he wants the translated version or the common 'fwd:' only? Even Outlook has such an option... I don't think this is an issue large enough to justify a setting.

08/27/2007 03:36:29 PM	ensc+horde (at) cvg (dot) de	Comment #3	Reply to this comment
do you really add the 43 translations (as of 4.1.4) of 'fwd:' to this array? Or at least: add a configuration option so that user can decide whether he wants the translated version or the common 'fwd:' only? Even Outlook has such an option...

08/27/2007 03:30:05 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
You can't really compare Fwd: with Re: because you usually reply to messages forth and back often, but you don't usually forward a message several times. This was discussed in the past and decided to translate Fwd: because it'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't the case in IMP 4.2 already.

08/27/2007 10:45:03 AM	ensc+horde (at) cvg (dot) de	Comment #1 Priority ⇒ 1. Low State ⇒ Unconfirmed Queue ⇒ IMP Summary ⇒ 'fwd:' string is translated Type ⇒ Bug	Reply to this comment
compose.php uses an i18n'able variant of the 'Fwd:' tag which indicates a forwarded message: \| $header['subject'] = _("Fwd:"); Although not explicitly stated in RFC850, this is similarly to the 'Re:' tag which is expected as-is but not as an translated string. E.g. 'compose.php' expects the english tag to decide whether a new tag shall be added: \| foreach (array('fwd:', 'fw:', '(fwd)', '[fwd]') as $signal) { Using internationalized strings there results into subjects like \| "Fwd: WG: Fwd: P.ep: VS: Hence, there should not be used _("Fwd:") but plain "Fwd:" and 'Fwd:' should be moved out of the _(...) in \| $header['subject'] = sprintf(_("Fwd: %u Forwarded Messages"), count($msglist));