Marck- Monday, February 24, 2003, 7:30:00 AM, you wrote:
MDP> You are quite right. That doesn't work at all. Why not use the link MDP> to explain the RFC to the webmaster? ;-) <grin> One point for Marck. But that *does* get us back on track. Here's what I (currently) think about this: Yes, the RFC does quite explicitly state that whitespace characters can end the field and this is a malformed url and therefore there's nothing really wrong with the way The Bat! is behaving here. But... OE *does* pick up the whole string, or so I've been told, not wanting to venture close enough to that beast to try it for myself. There's nothing technically hard about grabbing the whole thing - Windows does it quite easily. Right-click on the Feedback link, copy it to the clipboard, and paste it into your favorite text editor - there's the whole subject line, copied from the link, spaces and all. Grabbing the whole subject line from the link is also not a violation of the RFC - whitespace *can* end the tag, and technically you're supposed to translate the spaces to %20s and it's considered bad form if you don't, but I don't see a problem with TB working the way people expect it to instead of minimally conforming to the RFC. If the next version of TB were modified to act on the whole link instead of just the strict-interpretation subset I don't think it would break any existing behavior. And now I'm quite confused about the double-quotes in the registry thing. I thought this was just the thing it was supposed to fix up. Do you have a url for one where it does make a difference? -Mark Wieder Using The Bat! v1.63 Beta/4 on Windows 2000 5.0 Build 2195 Service Pack 2 -- ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
