subject of message not shown in threaded and list views

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

subject of message not shown in threaded and list views

Graham Perrin
This post was updated on .
Neither the expanded nor collapsed view of <http://n2.nabble.com/-tp3636586p3636708.html> shows the subject that I entered for that post:

alternative location of screen shot of the mailman options for the address @n2.nabble.com for chandler-users f1653123

I have cleared the cache of Safari 4.0.3 (6531.9), and reloaded the page, and edited (but not saved) the message to reaffirm that the title was entered.

Postscript: screen shots at <http://www.wuala.com/grahamperrin/public/2009/09/13/b
Reply | Threaded
Open this post in threaded view
|

Classic view seems to be OK

Graham Perrin
<http://n2.nabble.com/-tp3636586p3636708.html> does present the subject.

Threaded and list views remain bugged.
Reply | Threaded
Open this post in threaded view
|

Re: Classic view seems to be OK

Hugo <Nabble>
This bug is very interesting. The subject isn't displayed because it ends with the subject of the parent message. See:

...
   [screen shot of the mailman options for the address @n2.nabble.com for chandler-users f1653123]
      [alternative location of screen shot of the mailman options for the address @n2.nabble.com for chandler-users f1653123]

The two bold parts are equal. When this case happens, Nabble assumes the second subject is pretty much the same as the parent one, plus some other irrelevant characters. The most common case is:

[Subject]
   [Re: Subject]
       [Re: Re: Subject]

So we don't show subjects that end with the parent subject. I know that your case is a little bit different, but we must keep this algorithm generic enough to handle most languages. For example, "Re:" is "Res:" in portuguese. So we can't parse the sentence and try to discover if the chars are relevant or not. if you want that subject to show up, please change something at the end that will make it different from the parent subject.
Reply | Threaded
Open this post in threaded view
|

subject lines of replies

Graham Perrin
Hugo <Nabble> wrote
This bug is very interesting. The subject isn't displayed because it ends with the subject of the parent message.
Thanks. With the explanation, I'm happy to treat this as resolved.

Or would you like to do anything further on this, at a (much) later date?

"Re:" is "Res:" in portuguese. So we can't parse the sentence and try to discover if …
Understood. Around the same time that I read <http://tools.ietf.org/html/draft-koch-subject-tags-considered-00> (one of the IETF documents that prompted my post re: Subject prefixes, tags, in square brackets) I raced through some of the documents about
Re:

My list <http://www.diigo.com/list/grahamperrin/etiquette?v=p> includes a reference to <http://tools.ietf.org/html/rfc5322> and it's probably that draft RFC 5322 that I recall.

Now: ignoring the fact that some of those documents are drafts and/or expired: recently I often cut the 'Re: ' from subject lines of replies. Nabble web UI behaves perfectly in this situation and happily, no complaints from SMTP recipients. I take the latter as a sign that:

* increasingly, people use mail readers that are properly designed to thread without total reliance on the subject line

— I assume that Google Mail still falls short in this area (that their drop of the 'Beta' tag has not made it more compliant).

Personally, I'm never shy of using a subject line that's specific, or long. A good subject line greatly increases the chances of things being rediscovered, and quickly understood, months or years after posting.

Looking ahead, wondering …

OT from Nabble, I wonder whether things like Google Wave will:

* increase subject line laziness
* make people less tolerant/understanding of good subject lines
* etc..
Reply | Threaded
Open this post in threaded view
|

Re: subject lines of replies

Hugo <Nabble>
Graham Perrin wrote
Thanks. With the explanation, I'm happy to treat this as resolved.

Or would you like to do anything further on this, at a (much) later date?
I don't think we have anything else to do. You can treat it as resolved.