Hello Ben,
On Thursday, March 28, 2002, at 02:50:22 PM -0700, you wrote
the following in regards to "Mailto:s and TB!'s RTV":
> "For resiliency, programs interpreting URI should treat upper case
> letters as equivalent to lower case in scheme names (e.g., allow
Hello Dwight,
On Thursday, March 28, 2002, at 02:55:14 PM -0700, you wrote
the following in regards to "Mailto:s and TB!'s RTV":
> I agree with that. Even if upper case doesn't comply, it should work.
> But meanwhile, it just seemed reasonable to make the link work b
Hello Dwight,
On Thursday, March 28, 2002, at 02:08:45 PM -0700, you wrote
the following in regards to "Mailto:s and TB!'s RTV":
> Why? It if works lower everywhere, and is broken capped somewhere, why
> not just change. Lots less trouble than muddling thru a pile of rfcs,
Thursday, March 28, 2002, 4:38:15 PM, you wrote:
NA> Correct, and before I change my Mailto heading I want to be sure that the
NA> problem isn't just faulty Mailto handling by TB, and in fact the RFC calls
NA> for all lowercase letters. I'll start searching and see if I can locate
NA> the appl
On Thursday, March 28, 2002, 4:47:55 PM, Nick Andriash wrote:
> then it really should be resolved. No?
I agree with that. Even if upper case doesn't comply, it should work.
But meanwhile, it just seemed reasonable to make the link work before
TB! gets around to fixing the bugs.
--
Dwight A. C
On Thursday, March 28, 2002, 3:38:15 PM, Nick Andriash wrote:
>> It's a difference in how TB!'s "Fixed width viewer" and it's "Rich
>> Text Viewer" handles mailto:s with either an upper case or lower
>> case "M" in "mailto:";.
> Correct
This problem also exists for http: links. In the editor, h
On Thursday, March 28, 2002, 3:38:15 PM, Nick Andriash wrote:
> before I change my Mailto heading I want to be sure that the
> problem isn't just faulty Mailto handling by TB, and in fact the RFC
> calls for all lowercase letters
Why? It if works lower everywhere, and is broken capped somewhere
Hello Melissa,
On Thursday, March 28, 2002, at 01:30:37 PM -0700, you wrote
the following in regards to "Mailto:s and TB!'s RTV":
> It's a difference in how TB!'s "Fixed width viewer" and it's "Rich Text
> Viewer" handles mailto:s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday, March 28, 2002, at 12:17:06 PM PST, Nick Andriash wrote:
> Using the Fixed-Width Viewer I am having no problems with MailTo's,
> nor have I with any other Mailer I used that I can think of. There
> might be something in the RFC's that ad
Hello Dierk,
On Thursday, March 28, 2002, at 12:39:56 AM -0700, you wrote
the following in regards to "Mailto:s and TB!'s RTV":
>> I don't see many mailto:s starting with upper case "M"s, so I'm not
>> sure if this "problem" is just with
Hello Melissa!
On Thursday, March 28, 2002 at 4:54:18 AM you wrote:
> I don't see many mailto:s starting with upper case "M"s, so I'm not
> sure if this "problem" is just with TB!'s RTV or if mailto:s are only
> supposed to be lower case.
AFAIK, the latter.
--
Dierk Haasis
http://www.Write4
It was foretold that on 28-3-2002 @ 19:54:18 GMT-0800 (which was 4:54
where I live) Melissa Reese wrote and spread these wise comments on
"Mailto:s and TB!'s RTV":
MR> Just in case this is a typical problem for RTV's, you (lukie_be) might
MR> consider changing your mai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To "Lukie_be" and others...
I just wanted to mention a curious thing here - having to do with
TB!'s new RTV (Rich Text Viewer) and maito: URLs...
> Pgp key:
> Mailto:[EMAIL PROTECTED]?...
If the mailto begins with an upper case letter (Mailto:), th
13 matches
Mail list logo
