Rule 0: If your data-entry form has syntax requirements, indicate them on the 
form. That includes requiring or prohibiting punctuation.

As for uppercasing the local part of an e-mail address, that is the sin for 
which there is no forgiveness.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


________________________________________
From: IBM Mainframe Discussion List <[email protected]> on behalf of 
Paul Gilmartin <[email protected]>
Sent: Wednesday, September 30, 2020 12:01 PM
To: [email protected]
Subject: Re: blanks at the end of Unix file names - was LMINIT cannot handle 
concatenation with more than 16 data sets?

On Wed, 30 Sep 2020 15:44:14 +0000, Seymour J Metz <[email protected]> wrote:

>Applications should diagnose but not "correct" user errors, and should use 
>comoon system services to do so, where they exist. OS developers should 
>provide services for validation. Neither application developers nor OS 
>developers should attempt to validate externally defined data unless they 
>*REALLY* know what the rules are: that means hands off of names and e-mail 
>addresses if you don't know in detail what is permitted in every culture and 
>in the relevant RFCs.
+1

Many (most) web forms reject my RFC-822 valid email address:
    Paul Gilmartin <PaulGBoulder@********.tld>
when I copy-and-paste it from my email header.

And they force the local-part to monocase, violating the RFC.

And my phone, copied from my Contacts entry:
    ‭(720) 382-xxxx
They accept only digits.  Some add insult to injury by then reformatting
it as I had tried to enter it.

And credit card numbers with groups of 4 digits.

-- gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to