In <[EMAIL PROTECTED]">mid:[EMAIL PROTECTED]>, Dierk Haasis [DH] wrote:'
DH> So, TB should "send" mailto links correctly coded and "accept" (in DH> other mails) them wrong? DH> First, I am not sure what that means in this context. DH> Second, how the hell should TB know what part after a mailto: DH> belongs to the link and what is the next normal text? DH> PGP keys available: DH> mailto:[EMAIL PROTECTED]?Subject=SendMyPGPkeys for DH> secure and private conversation per e-mail with me. I think there's some confusion as well. One with what the user sees vs the actual source. This has come up before and in all instances, we're able to show that the actual message source or the web pages source have the hex codes for the spaces. It's just that the interpreter leaves out the space in the output. You ask the question. How is TB! to know when the mail-to link ends??? You can't compare an incorrectly formatted mailto link embedded in text to an incorrectly formatted url or other link put in a browsers address field. The browser can safely assume that all characters entered in the address field, makes up the URL. So if there's a space, it will automatically insert the %20 characters. Unless you develop a system where URL's are entered in a special field, there's no room for accepting incorrect formatting and assuming characters mean something else. -- Allie C Martin \ TB! v1.62/Beta16 & WinXP Pro (SP1) List Moderator / PGP Key - http://pub-key.ac-martin.com ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
