Re: [WebDNA] Foreign characters (2009)
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102332
interpreted = N
texte = Olin Lagon wrote:> What about creating a new field in your database that mirrors your live> content that contains NO accented characters?That's what I've been doing at it works fine although of course it=20increases the size of the databases considerably. The idea can also be=20expanded to deal with other kinds of close-match searches.The main problem back in 1998 was the lack of a standard extended=20character set. At that time "caf=E9" might have come across as "caf=FF,"=20"caf=EE" or whatever, depending on what OS/OS version/software the=20visitor's computer was running. This is no longer a major concern and=20that makes the problem much easier to solve.A wildcard search function would have made it even easier. No need for=20complicated conversion tables for the input string, just replace all=20potentially tricky charcaters with a * and do a wildcard enabled search=20through the simplified-charcters database field. (I can think of several=20other practical uses for wildcard searches as well. Would it be hard to=20persuade Donovan & co to include it in the next WebDNA upgrade?)Frank Nordberghttp://www.musicaviva.comhttp://stores.ebay.com/Nordbergs-Music-Store?refid=3Dstore
Associated Messages, from the most recent to the oldest:
Olin Lagon wrote:> What about creating a new field in your database that mirrors your live> content that contains NO accented characters?That's what I've been doing at it works fine although of course it=20increases the size of the databases considerably. The idea can also be=20expanded to deal with other kinds of close-match searches.The main problem back in 1998 was the lack of a standard extended=20character set. At that time "caf=E9" might have come across as "caf=FF,"=20"caf=EE" or whatever, depending on what OS/OS version/software the=20visitor's computer was running. This is no longer a major concern and=20that makes the problem much easier to solve.A wildcard search function would have made it even easier. No need for=20complicated conversion tables for the input string, just replace all=20potentially tricky charcaters with a * and do a wildcard enabled search=20through the simplified-charcters database field. (I can think of several=20other practical uses for wildcard searches as well. Would it be hard to=20persuade Donovan & co to include it in the next WebDNA upgrade?)Frank Nordberghttp://www.musicaviva.comhttp://stores.ebay.com/Nordbergs-Music-Store?refid=3Dstore
Frank Nordberg
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
eMailer replacement? (1998)
label?! (2005)
[WebDNA] configuring 5.1 with apache 2? (take 2) (2008)
graphics server, SSL, Netscape 4.0 (off topic) (1998)
all records returned. (1997)
Error Lob.db records error message not name (1997)
Emailer problem (1998)
PIXO support (1997)
Replace Statement (1997)
Problems with [Search] param - Mac Plugin b15 (1997)
WebCat & WebTen (1997)
WC Database Format (1997)
Accepting credit cards (1997)
Another question (1997)
emailer (1997)
Encrypted Databases (2000)
Problems getting parameters passed into email. (1997)
View order not right (1997)
Can't Update records (1997)
TPC Connect (1999)