D
Dick Watson
I'm trying to send a path to a file, of the form of
<\\ourserver\ourpath\meeting #1 agenda.pdf> in al OL03 message. Since I sign
by default, OL03 insists on ignoring my preference for RTF and using HTML
instead.
In RTF, just sending the text <\\ourserver\ourpath\meeting #1 agenda.pdf>
works fine and can be opened from an OL03 client.
In HTML, OL03 converts this to a hyperlink
href="file://\\ourserver\ourpath\meeting #1 agenda.pdf". But when you try to
open this hyperlink from OL03, it terminates the link it tries to open at the
#, thus making the act of sending the link worse than useless. So I've tried
all manner of ways to get the # sent as %23 (legal URL encoding for an
embedded #, last I looked) or similar and nothing I've tried works.
Is there a way to send an embedded # in a URL via OL03 such that OL03 will
also be able to open the link or should I just abandon signed email
completely so I can use RTF instead of Outlook mutant HTML?
<\\ourserver\ourpath\meeting #1 agenda.pdf> in al OL03 message. Since I sign
by default, OL03 insists on ignoring my preference for RTF and using HTML
instead.
In RTF, just sending the text <\\ourserver\ourpath\meeting #1 agenda.pdf>
works fine and can be opened from an OL03 client.
In HTML, OL03 converts this to a hyperlink
href="file://\\ourserver\ourpath\meeting #1 agenda.pdf". But when you try to
open this hyperlink from OL03, it terminates the link it tries to open at the
#, thus making the act of sending the link worse than useless. So I've tried
all manner of ways to get the # sent as %23 (legal URL encoding for an
embedded #, last I looked) or similar and nothing I've tried works.
Is there a way to send an embedded # in a URL via OL03 such that OL03 will
also be able to open the link or should I just abandon signed email
completely so I can use RTF instead of Outlook mutant HTML?