On Sun, 23 Feb 2003 11:06 pm, Anthony Baxter wrote:
> > Richard 
Jones wrote
> >
> > On Sun, 23 Feb 2003 12:22 pm, John P. 
Rouillard
> > wrote:
> > > I'm not interested in that. I don't 
think the
> > > complexity of multipart emails with full html
> > > 
is needed. Just turn issue12 into
> > > http://.../issue12 and let 
the native URL
> > > recognition in the user's MUA handle it.
> 
>
> > Yeah, but then we're screwing with the formatting
> > of the 
message.
>
> Seems like going down the path to screwing with
> 
messages is going to cause pain. Can I suggest an
> alternative? 
Instead of replacing the
> text inline, put the entries at the end 
of the
> paragraph

Sounds like a good idea to me. John, please 
enter a feature request :)
    Richard

Done. Also it would be noce 
to have msg23 and other hyperlinked as well. For my 2 cents it would be 
enough
to put them at the end of the messages before
the chages to 
issue fields under a header like:

---------- referenced tracker 
objects
msg12: http://...
issue8: http://
----------
messages: 
3
nosy: admin
priority: high
status: open
title: Sunday 
Test

Logged In: YES 
user_id=29957

It's probably worth making a decision whether to put 
references in for quoted text as well - I'd tend to say
'no', as you'll end up with multiple references. Or you
make the "reference text" be of a form that you can 
pick up when parsing the message - if it's there already,
don't re-reference it. Note also that you probably only
want to do the reference thing for the first occurance of
each link.

Logged In: YES 
user_id=6405

There's two approaches to take: 
 
1. We insert the links between paras. This means we parse the 
message to figure where the para boudaries are. We can also figure 
quoted bits and ignore them, or 
2. We append links. No parsing is required UNLESS we want to ignore 
quoted bits. 
 
My vote is for approach #2.