Re: Accentuated and non-English letters

This WebDNA talk-list message is from

2002

It keeps the original formatting. numero = 44964
interpreted = N
texte = >Here's a problem that's been bothering me for a while:>>As most of you probably know, ascii was invented by a couple of >second class yankee computer would-be-experts late one night over >the sixth round of beer at their local strip joint. Over the years >various people have attempted to sort out the mess those guys made - >usually ending up making matters even worse :-(>>Does anybody know of a simple and - above all - reliable way to use >letters like �, �, � etc. etc. in WebCat searches?Not exactly, but I have a solution that will work 100% of the time in all your searches:You can use convertchars to convert all those high ASCII characters to standard keyboard characters -- so none of the letters like �, �, � etc. are allowed to be stored in your db's. Then do the exact same conversions to the values your visitors enter into their search forms -- so your searches *also* use only the standard 26-letter character set. Then your search values will *always* match your db values.Yes, this will mean that when you display your db values on the web page, letters like �, �, � etc. will not appear, instead they will be replaced by their convertchars equivalents. But if this is a minor issue to you, then my solution will work just fine in terms of fixing all your search problems which are related to unusual characters.I use a similar technique when allowing people to enter phone numbers into my forms. Since they never seem to be able to type their phone numbers in exactly the same way twice, I just let them type their phone numbers in any format they feel like typing them. Then I remove all characters except the numeric digits before applying the resulting values to my search, append, replace and delete contexts. Yes, the phone numbers lose whatever formatting the visitor happened to give them in my web forms, but that's a minor inconvenience considering the fact that my searches always work on my phone number fields now ...:)Sincerely,Kenneth Grome---------------------------------------------------WebDNA Professional Training and Development Center175 J. Llorente Street +63 (32) 255-6921Cebu City, Cebu 6000 kengrome@webdna.netPhilippines http://www.webdna.net----------------------------------------------------------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: Accentuated and non-English letters (Tom Duke 2002)
Re: Accentuated and non-English letters (Kenneth Grome 2002)
Re: Accentuated and non-English letters (Frank Nordberg 2002)
Re: Accentuated and non-English letters (Nitai @ ComputerOil 2002)
Re: Accentuated and non-English letters (John Peacock 2002)
Accentuated and non-English letters (Frank Nordberg 2002)

>Here's a problem that's been bothering me for a while:>>As most of you probably know, ascii was invented by a couple of >second class yankee computer would-be-experts late one night over >the sixth round of beer at their local strip joint. Over the years >various people have attempted to sort out the mess those guys made - >usually ending up making matters even worse :-(>>Does anybody know of a simple and - above all - reliable way to use >letters like �, �, � etc. etc. in WebCat searches?Not exactly, but I have a solution that will work 100% of the time in all your searches:You can use convertchars to convert all those high ASCII characters to standard keyboard characters -- so none of the letters like �, �, � etc. are allowed to be stored in your db's. Then do the exact same conversions to the values your visitors enter into their search forms -- so your searches *also* use only the standard 26-letter character set. Then your search values will *always* match your db values.Yes, this will mean that when you display your db values on the web page, letters like �, �, � etc. will not appear, instead they will be replaced by their convertchars equivalents. But if this is a minor issue to you, then my solution will work just fine in terms of fixing all your search problems which are related to unusual characters.I use a similar technique when allowing people to enter phone numbers into my forms. Since they never seem to be able to type their phone numbers in exactly the same way twice, I just let them type their phone numbers in any format they feel like typing them. Then I remove all characters except the numeric digits before applying the resulting values to my search, append, replace and delete contexts. Yes, the phone numbers lose whatever formatting the visitor happened to give them in my web forms, but that's a minor inconvenience considering the fact that my searches always work on my phone number fields now ...:)Sincerely,Kenneth Grome---------------------------------------------------WebDNA Professional Training and Development Center175 J. Llorente Street +63 (32) 255-6921Cebu City, Cebu 6000 kengrome@webdna.netPhilippines http://www.webdna.net----------------------------------------------------------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Kenneth Grome

DOWNLOAD WEBDNA NOW!

Re: Accentuated and non-English letters

2002

Top Articles:

Related Readings: