Re: [WebDNA] Foreign characters (2009)
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102312
interpreted = N
texte = Dan Strong wrote:> [url][/url]?That won't work since "e" and "=E9" will still be different=20chracters/chracter strings after [url].There are two ways to solve this.The best solution is probably to treat all tricky characters as=20wildcards. Problem is, I'm not sure if it's possible to do wildcard=20searches with WebDNA.The other solution is to use a table of all the tricky characters and=20which ones they should be replaced with. This wasn't really an option=20back in '98 with all the different ascii extensions in use at that time.=20But today all modern computers use Unicode which make this solution much=20easier to apply.Of course, ideally this character conversion feature sould be built in=20to WebDNA. Definitely something to add to the wish list for the next=20upgrade. In the meantime it shouldn't be that difficult to script.I may have been the one who brought up the issue in 1998. The=20quick-and-dirty solution I ended up with was to store two different=20versions of each relevant text block in the databases, one for diplay=20and another one with a simplified chracter set for searches. Then I=20added a note to the search forms telling visitors to use the simplified=20chracters. Not a good solution but at that time it was the best I could=20come up with. With Unicode it should be possible to use a better solution=.Frank Nordberghttp://www.musicaviva.comhttp://stores.ebay.com/Nordbergs-Music-Store?refid=3Dstore
Associated Messages, from the most recent to the oldest:
Dan Strong wrote:>
[url][/url]?That won't work since "e" and "=E9" will still be different=20chracters/chracter strings after
[url].There are two ways to solve this.The best solution is probably to treat all tricky characters as=20wildcards. Problem is, I'm not sure if it's possible to do wildcard=20searches with WebDNA.The other solution is to use a table of all the tricky characters and=20which ones they should be replaced with. This wasn't really an option=20back in '98 with all the different ascii extensions in use at that time.=20But today all modern computers use Unicode which make this solution much=20easier to apply.Of course, ideally this character conversion feature sould be built in=20to WebDNA. Definitely something to add to the wish list for the next=20upgrade. In the meantime it shouldn't be that difficult to script.I may have been the one who brought up the issue in 1998. The=20quick-and-dirty solution I ended up with was to store two different=20versions of each relevant text block in the databases, one for diplay=20and another one with a simplified chracter set for searches. Then I=20added a note to the search forms telling visitors to use the simplified=20chracters. Not a good solution but at that time it was the best I could=20come up with. With Unicode it should be possible to use a better solution=.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:
Shopping cart problem (2003)
2.0 Info (1997)
Running _every_ page through WebCat-error.html (1997)
OT: Log Files (2003)
# fields limited? (1997)
template includes encrypted template (1999)
Transferring [cart] to Database (1997)
RePost: NAT and the CART (1999)
RequiredFields template (1997)
Re:What file? (1997)
Bug Report, maybe (1997)
HELP WITH DATES (1997)
Math Bug (1999)
[WebDNA] doesn't "&max=1" work in a [delete] context? (2009)
Where's Cart Created ? (1997)
WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997)
unsubscribe (2000)
WebCatalog and directory indexing (1998)
custom freight charges (2001)
Formvariable won't update (1999)