38661 - Use sender's quote marks in reply

Status: NEW

(MailNews Core :: Backend, enhancement)

Description

[Karl Ove Hufthammer]

I prefer using | as quote marks, and have set this in the preferences. But, when a discussion is held (either in mail or news), use of several different quote marks can look strange (ugly!). Sometimes I manually change my quote marks to match the sender's (e.g. if he/she uses >, so do I).

It would be great if this could be automated in Mozilla, i.e. Mozilla should use the same quote marks as the sender does. This should of course be a pref ("Use sender's quote marks"?). If several different types of quote marks are used, Mozilla should use the last one (in '>>||:>> Hi!', Mozilla should use '>').

I've set the priority of this to 'enhancement'. Please don't mark it as WONTFIX, even if it won't get implemented for 5.0. Instead, mark it as M200 or something ... ;)

Comment 1

[lchiang]

mark helpwanted

Comment 2

[Karl Ove Hufthammer]

The latest test version of the Windows news reader XNews, available from <URL: 
http://xnews.3dnews.net/test/ > (you'll also need the normal XNews release from 
<URL: http://xnews.3dnews.net/ >) has a similar feature. It displays all quote 
marks a '>' (you can turn off/on this feature from the menu or via a keyboard 
shortcut). Example:

||> >: > asdasd dgdst ljt kjtkjtkt jdslkt jdst kdjt tdst  
||> >: > rtu iu bivbu cv erlkjlk b jfdskj fjgt drs ht t hdrthtslkjdstdt
||> >: > asdasd dgdst ljt kjtkjtkt jdslkt jdst kdjt tdst  
||> >: > rtu iu bivbu cv erlkjlk b jfdskj fjgt drs ht t hdrthtslkjdstdt

is by default displayed as:

>>>>>> asdasd dgdst ljt kjtkjtkt jdslkt jdst kdjt tdst  
>>>>>> rtu iu bivbu cv erlkjlk b jfdskj fjgt drs ht t hdrthtslkjdstdt
>>>>>> asdasd dgdst ljt kjtkjtkt jdslkt jdst kdjt tdst  
>>>>>> rtu iu bivbu cv erlkjlk b jfdskj fjgt drs ht t hdrthtslkjdstdt

When you reply (followup), the quote marks are still displayed as '>>>>>>' (if 
the 'Uniform Quoting' option is activated).

Comment 3

[Serge Gautherie (:sgautherie)]

Filter on "Nobody_NScomTLD_20080620"