HELP! Again. I seem to have some padding I can't get rid of and a PHP problem.

Neredbojias wrote:

eregi("[A-Z]+");

include a-z or not?

I think it does. But that's just me thinking :-)

Me, too.

See Ben's reply :-)

And thanks for uploading the nice pics.

Only one! the rest is NOT mine - not taking responsibility for those
<g>

--
Els http://locusmeus.com/

Ben C wrote:

On 2008-03-27, Els <els.aNOSPAM (AT) tiscali (DOT) nl> wrote:

Sounds like the safest bet would be to use A-z ?

That's a good idea, although I don't have total confidence that it's
either AaBbCc... or ABC...abc... and not some other other strange order
in some locales.

Locale is irrelvant. It's just ASCII. You can find the order in any
ASCII chart. There are many around the web.

--
Berg

Blinky the Shark wrote:

Els wrote:

Toby A Inkster wrote:

Els wrote:

Which special chars are between Z and a then? Noob here - I just
thought it would either go AaBbCc.. or ABC...XYZabc...xyz ?

There are six characters between 'Z' and 'a': [\]^_`

Thanks - I had no idea.. :-)

http://www.asciitable.com/

Shows I'm not a real geek - that's the first time I ever saw an ASCII
table. (not counting the ones I wrote myself by starting at ALT-128 so
I had a list for the occasional é and ç back when I was a typist...)

--
Els http://locusmeus.com/

Els wrote:

Toby A Inkster wrote:

Els wrote:

Which special chars are between Z and a then? Noob here - I just
thought it would either go AaBbCc.. or ABC...XYZabc...xyz ?

There are six characters between 'Z' and 'a': [\]^_`

Thanks - I had no idea.. :-)

http://www.asciitable.com/

--
Blinky
Killing all posts from Google Groups
The Usenet Improvement Project: http://improve-usenet.org
Blinky: http://blinkynet.net

Blinky the Shark wrote:

Els wrote:

Shows I'm not a real geek

snip

You can be. Just stick with us.

Been doing that for ehm... [counting on fingers..] 5 years already -
didn't help much yet! :-)

Okay - I didn't count on my fingers, I had to look it up in Google
groups, and the oldest post I can find of myself in this group, was in
August 2003. Funny thing though, Jukka is in that thread too, and he
is so friendly and helpful! I'm almost tempted to read back the last 5
years of alt.html posts to see what went wrong ;-)

--
Els http://locusmeus.com/

Neredbojias wrote:

Okay, I've scoured the php manual and apparently the following insert if
designated as caseless:

[A-Z]

will indeed include a-z. In some foreign languages that have umlauts and
other gazinckisses, such letters may be also included.

Okay, good to know.

And thanks for uploading the nice pics.

Only one! the rest is NOT mine - not taking responsibility for those

Really? I wonder who uploaded the foggy sun and vale one? Anyway, there
was quite a rush last night, and it was interesting.

You should have captured IP addresses - then compare them to IP
addresses in the group's posts ;-)

(PS: Did you see Blinky's behemoth killer shark?)

Yup, I did :-)

--
Els http://locusmeus.com/

Els wrote:

Blinky the Shark wrote:

Els wrote:

Toby A Inkster wrote:

Els wrote:

Which special chars are between Z and a then? Noob here - I just
thought it would either go AaBbCc.. or ABC...XYZabc...xyz ?

There are six characters between 'Z' and 'a': [\]^_`

Thanks - I had no idea.. :-)

http://www.asciitable.com/

Shows I'm not a real geek

<snip>

You can be. Just stick with us.


--
Blinky
Killing all posts from Google Groups
The Usenet Improvement Project: http://improve-usenet.org
Blinky: http://blinkynet.net

..oO(Els)

I'm no PHP wizard, nor do I know much about regexp, but for those who
are, this is the part in the script that seems to check the email
address:

// Check the email address enmtered matches the standard email address
format
if (!eregi("^[A-Z0-9._%-]+@[A-Z0-9._%-]+\.[A-Z]{2,6}$", $email)) {
echo "<p>It appears you entered an invalid email address</p><p><a
href='javascript: history.go(-1)'>Click here to go back</a>.</p>";
}

Just two notes:

1) Using such checks should be done carefully. A proper RFC-compliant
address check _cannot_ be done with such a simple regex. Almost every
regex I saw will still allow many invalid addresses and reject valid
ones. The RFC 822 is a quite complex beast.

Mail::RFC822::Address: regexp-based address validation
http://www.ex-parrot.com/~pdw/Mail-RFC822-Address.html

PHP : Parsing Email Adresses in PHP
http://www.iamcal.com/publish/articl...parsing_email/

The second one seems to work quite well, but still is not fully RFC-
compliant (but should be enough in most cases, though).

2) The ereg_* functions are dead and will be removed in PHP6. The preg_*
(PCRE) functions are the way to go and much more powerful and efficient.

Micha

Michael Fesser wrote:

if (!eregi("^[A-Z0-9._%-]+@[A-Z0-9._%-]+\.[A-Z]{2,6}$", $email)) {

Just two notes:

1) Using such checks should be done carefully. A proper RFC-compliant
address check _cannot_ be done with such a simple regex. Almost every
regex I saw will still allow many invalid addresses and reject valid
ones. The RFC 822 is a quite complex beast.

Mail::RFC822::Address: regexp-based address validation
http://www.ex-parrot.com/~pdw/Mail-RFC822-Address.html

PHP : Parsing Email Adresses in PHP
http://www.iamcal.com/publish/articl...parsing_email/

I think I like this one better than the Perl one.. easier to see if I
made a typo <g>

The second one seems to work quite well, but still is not fully RFC-
compliant (but should be enough in most cases, though).

2) The ereg_* functions are dead and will be removed in PHP6. The preg_*
(PCRE) functions are the way to go and much more powerful and efficient.

Thanks for the heads up :-)

--
Els http://locusmeus.com/

On 2008-03-27, Bergamot <bergamot (AT) visi (DOT) com> wrote:

Ben C wrote:
On 2008-03-27, Els <els.aNOSPAM (AT) tiscali (DOT) nl> wrote:

Sounds like the safest bet would be to use A-z ?

That's a good idea, although I don't have total confidence that it's
either AaBbCc... or ABC...abc... and not some other other strange order
in some locales.

Locale is irrelvant. It's just ASCII. You can find the order in any
ASCII chart. There are many around the web.

I'm pretty sure the value of LC_COLLATE will affect whether [A-Z]
matches "b" or not (assuming case-sensitive, otherwise it will always
match "b") in many programs.

In the egrep manual:

Within a bracket expression, a range expression consists of two
characters separated by a hyphen. It matches any single character
that sorts between the two characters, inclusive, using the locale's
collating sequence and character set. For example, in the default C
locale, [a-d] is equivalent to [abcd]. Many locales sort characters
in dictionary order, and in these locales [a-d] is typically not
equivalent to [abcd]; it might be equivalent to [aBbCcDd], for
example. To obtain the traditional interpretation of bracket
expressions, you can use the C locale by setting the LC_ALL
environment variable to the value C.