According to Lachlan Andrew: > On Wed, 11 Sep 2002 05:06, you wrote: > > > The other problem is the format of "kurl"s, which use a > > > single '/' after the ':'. > > > > The proper fix would be in htcommon/URL.cc, where it > > handles parsing of URLs. I think it has to deal with > > exceptions like this on a case by case basis. > > Thanks for that. I was thinking of having a list of known > services, specifying the number of leading slashes, with > default entries: > mailto, news : 0 > http, ftp, most others : 2-or-more > > When there are two-or-more slashes, the user and port will > be parsed as currently. Otherwise, it will all be treated > as "path". > > When an external transport mechanism is specified as, say, > 'https' it will be added with "two slashes". However, if > it is specified as, say, "man:" or "help:/" or "https://"; > (with a colon), then the number of slashes can be specified > explicitly. That will avoid hard-coding the KDE stuff into > htDig:// > > Does that sound feasible?
That sounds like a great idea to me. Would you be willing to implement it? If you can provide patches, I can make sure they make it into the CVS tree. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- In remembrance www.osdn.com/911/ _______________________________________________ htdig-dev mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/htdig-dev
