Frederik Holljen wrote: > I need some extra information to be able to vote.. > > On Friday 27 July 2007 15:53, Alexandru Stanoi wrote: >> 1. Which regexp to use for email validation? >> >> a. >> http://cvs.php.net/viewvc.cgi/pear/HTML_QuickForm/QuickForm/Rule/Email.php? >> revision=1.4&view=markup b. >> http://iamcal.com/publish/articles/php/parsing_email/ >> c. http://code.iamcal.com/php/rfc822/full_regexp.txt >> d. http://ex-parrot.com/~pdw/Mail-RFC822-Address.html >> e. http://www.tienhuis.nl/files/email_verify_source.php >> f. This one (please specify): _________________ >> g. Write our own one > I don't have time for an in depth look at all of these :) Can you tell me the > difference?
All the regexp here are bad, in that they don't have the same results for the same addresses. Most correct one seems to be b because it follows RFC822 to the letter. >> 2. Do we need to support conversion to Puny code >> (http://en.wikipedia.org/wiki/Puny_code)? >> >> a. NO WAY! >> b. No >> c. Not now >> d. Yes >> e. YES WAY! > What do we gain/lose? Can we implement this support later? This was discussed already (see the whole thread). In my opinion we don't gain too much and also I think we don't need it. But some other people think we need it. >> 3. If the answer to question 2 was one of c, d or e, then where to put >> the unicodeToPunyCode convert function (and the reverse function)? >> >> a. Mail >> b. Url >> c. Base >> d. UserInput >> e. a Tiein (please specify): _______________ >> f. I can tell you where to put it! > What exactly will that method do? We need to know that in order to decide > where it should go. It should convert an URL from Unicode to PunyCode. See the discussion in the thread. Some people wanted it in Mail, some others in Url and some others even in Base. > Cheers, > Frederik -- Alexandru Stanoi eZ Components System Developer eZ Systems | http://ez.no -- Components mailing list Components@lists.ez.no http://lists.ez.no/mailman/listinfo/components
