<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"/> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"/>  <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> The Help Desk has a neat feature that when it shows doc.txt file, it scans them for ftp and http urls and e-mail addresses and displays them as links.  Unfortunately, the e-mail links don’t work correctly – they prepend ‘///’ on the front of the e-mail address.  Unfortunately, because of the way Outlook works – I’m sure it’s a feature – it isn’t easy (or possible?) to get rid of this in the address line in Outlook 2003.  I came across it when I was submitting my packages to PLaneT and tried to follow the link and it didn’t work.  (And I then klutzed up typing it and it took even longer.)<o:p></o:p> <o:p> </o:p> This bug has apparently been around for a while since Problem Report 6241 dated May 2, 2003 deals with it in Version 204 and it’s still open.  The PR is assigned to Robby Findler.<o:p></o:p> <o:p> </o:p> It turns out that the problem is in the way urls are parsed into an internal format and then turned back into strings.  There is no special parser for mailto: urls and for some reason the general url->string function for these generic urls adds the three slashes.<o:p></o:p> <o:p> </o:p> The following fix to the url->string function in the url-unit.ss file in the net collection corrects the problem, but needs to be verified.<o:p></o:p> <o:p> </o:p>       (define url->string<o:p></o:p>         (lambda (url)<o:p></o:p>           (let ((scheme (url-scheme url))<o:p></o:p>                 (user (url-user url))<o:p></o:p>                 (host (url-host url))<o:p></o:p>                 (port (url-port url))<o:p></o:p>                 (path (url-path url))<o:p></o:p>                 (query (url-query url))<o:p></o:p>                 (fragment (url-fragment url)))<o:p></o:p>             (cond<o:p></o:p>              ((and scheme (string=? scheme "file"))<o:p></o:p>               (string-append "file:" <o:p></o:p>                        (url->file-path url)<o:p></o:p>                              (or (and (not fragment) "")<o:p></o:p>                                  (string-append "#" fragment))))<o:p></o:p> ;;; added ---v<o:p></o:p>              ((and scheme (string=? scheme "mailto"))<o:p></o:p>               (string-append "mailto:"<o:p></o:p>                              (car path)))<o:p></o:p> ;;; ---------^<o:p></o:p>              (else<o:p></o:p>               (let ((sa string-append))<o:p></o:p>                 (sa (if scheme (sa scheme "://") "")<o:p></o:p>                     (if user (sa (uri-encode user) "@") "")<o:p></o:p>                     (if host host "")<o:p></o:p>                     (if port (sa ":" (number->string port)) "")<o:p></o:p>                                         ; There used to be a "/" here, but that causes an<o:p></o:p>                                         ; extra leading slash -- wonder why it ever worked!<o:p></o:p>                     (combine-path-strings path)<o:p></o:p>                     ;(if query (sa "?" (uri-encode query)) "")<o:p></o:p>                     (if (null? query) "" (sa "?"  (alist->form-urlencoded query)))<o:p></o:p>                     (if fragment (sa "#" (uri-encode fragment)) ""))))))))<o:p></o:p> <o:p> </o:p> This fixes the particular problem with mailto: urls in the help desk.  I can’t see that it would break anything else.<o:p></o:p> <o:p> </o:p> This fix is based on how the parser actually parses mailto: urls – with url-scheme = “mailto” and url-path = (“<the address>”).  One could debate that there should be code in the parser to handle mailto: urls, but there isn’t.<o:p></o:p> <o:p> </o:p> Doug<o:p></o:p> <o:p> </o:p> M. Douglas Williams, Ph.D.<o:p></o:p> Sr. Scientist<o:p></o:p> Science Applications International Corporation<o:p></o:p> 4B <st1:Street w:st="on"><st1:address w:st="on">Inverness Drive East</st1:address></st1:Street>, <st1:address w:st="on"><st1:Street w:st="on">Suite</st1:Street> 210</st1:address><o:p></o:p> <st1:place w:st="on"><st1:City w:st="on">Englewood</st1:City>, <st1:State w:st="on">CO</st1:State>  <st1:PostalCode w:st="on">80112</st1:PostalCode></st1:place><o:p></o:p> office: (303) 217-4421<o:p></o:p> cell: (303) 229-0315<o:p></o:p> <a href="mailto:m.douglas.williams@saic.com">m.douglas.williams@saic.com</a><o:p></o:p> <o:p> </o:p> </div> </body> </html>