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:
Developer Edition (4.5) (2004)
Solution to Back button (2000)
PIXO support (1997)
WebCat2 - [SendNews] (1997)
LOG IN LOG OUT (1997)
RAM crash (1998)
Unstable on my server (2000)
Performance: deafening silence (1999)
Rounding question (2002)
unable to launch acgi in WebCat (1997)
Summing fields (1997)
Using Plug-In while running 1.6.1 (1997)
problems with 2 tags (1997)
how to do [search] params on the fly? (2004)
[WebDNA] PayPal integration code examples? (2011)
Emailer (2000)
WCS Newbie question (1997)
More on [purchase] (1998)
Meet your competition (2000)
Re:no [search] with NT (1997)