Jamie, Glad to be of some use. I'm an ardent anti-spammer and it was an initiative to thwart harvesters. I use mixed in an effort to confuse parsing aglos employed by poorly coded harvesters. However, any programmer worth his salt will simply run a recursive loop and trap for either ...
Be warned, though: this can play merry hell with screen readers and other accessible text software unless they're properly setup to interpret these coded feeds. There is no real difference between the two formats; both are happily interpreted and rendered by contemporary browsers (even Lynx -- which is a bonus), although one is an internationally recognised standards format (ISO). There is no 'secure' format because if a browser can display it, a programmer can read it. But it'll keep the kids at bay :o) Cheers, Mike Pepper Accessible Web Developer (with shares in Anadin) www.seowebsitepromotion.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jaime W Sent: 03 June 2004 22:04 To: [EMAIL PROTECTED] Subject: RE: [WSG] Anti-spam mailto encoders using Character Entity Evasion Mike you are a gem! This tool generates codes that validates in XHTML 1.0 DTD Strict! Is helpful and great for lazy people like me lol. Tested it and it works great. Thank you thank you very much! By the way what is the differences between ISO and Hex Conversion? Which is more secure? I choose the default which is ISO Conversion. Best Wishes, Jaime ....... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Pepper Sent: Friday, 4 June 2004 3:17 AM To: [EMAIL PROTECTED] Subject: RE: [WSG] Anti-spam mailto encoders using Character Entity Evasion Jaime, Just use http://www.seowebsitepromotion.com/obfuscate_email.asp. Might prove useful and does it all for you, including complete mail-to strings. Mike Pepper Accessible Web Developer (with a headache because he's been on the system way too long) http://www.seowebsitepromotion.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jaime W Sent: 03 June 2004 19:35 To: [EMAIL PROTECTED] Subject: [WSG] Anti-spam mailto encoders using Character Entity Evasion Ermm another question List fellows. Hope you guys don't mind...4th question for the past 2 weeks. I am trying to use Character Entity Evasion for mailto encoding instead of JavaScript. At times it validates and at times it doesn't. Why? I have no idea. Example of Character Entity encoded email: Decode: [EMAIL PROTECTED] Encode: test@testing. com Those characters is making my xhtml 1.0 strict validation unhappy. May I know what alternatives do the rest of you use besides using JavaScript for encoding your e-mail? Contact Forms and '@ image method' or replacing '@' with 'at' method aside please. Thank you! Best Wishes, Jaime ....... ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ***************************************************** ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ***************************************************** ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ***************************************************** ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************
