- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Wed, 13 Sep 2017 17:23:28 +0200
- To: "Steven Pemberton" <Steven.Pemberton@cwi.nl>, "C. M. Sperberg-McQueen" <cmsmcq@blackmesatech.com>, "Steven Pemberton" <steven.pemberton@cwi.nl>
- Cc: XForms <public-xformsusers@w3.org>
On Wed, 13 Sep 2017 12:18:07 +0200, Steven Pemberton <steven.pemberton@cwi.nl> wrote: >> To try to boil it down, the following number patterns are not >> supported by the regex given; whether they should be is in each case a >> policy question: >> >> a (+352) 999 99-99999 > Will fix >> b 999.999.9999 > Propose to disallow. >> c 0711/9999-999 > Propose to disallow. >> d 613 999-9999 (two blanks or one-em space after area code) > This seems to work. >> e +33 | 99 99 99 99 > Propose to disallow. >> f 800,999.9999 x349 > Propose to disallow. >> g (1) 905 999 9999 x99999 > Propose to disallow. >> h +420-2-9999-9999 > Will fix >> i EM6-9999 > Propose to disallow. >> j 1-800-WHA-KNOW > Propose to disallow. >> The following number patterns are supported (but use parentheses to >> enclose something other than an area code) >> >> z (1) 905 999 9999 > Already works >> y +44 (0) 9999 999999 > Already works So I have added all these examples to the test set, and fixed the regexp to correctly match the ones we want to be valid. Viewable, and playable-with, at the bottom of http://homepages.cwi.nl/~steven/forms/tests/email.xml Steven
Received on Wednesday, 13 September 2017 15:23:55 UTC