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=20 chracters/chracter strings after [url]. There are two ways to solve this. The best solution is probably to treat all tricky characters as=20 wildcards. Problem is, I'm not sure if it's possible to do wildcard=20 searches with WebDNA. The other solution is to use a table of all the tricky characters and=20 which ones they should be replaced with. This wasn't really an option=20 back in '98 with all the different ascii extensions in use at that time.=20 But today all modern computers use Unicode which make this solution much=20 easier to apply. Of course, ideally this character conversion feature sould be built in=20 to WebDNA. Definitely something to add to the wish list for the next=20 upgrade. 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=20 quick-and-dirty solution I ended up with was to store two different=20 versions of each relevant text block in the databases, one for diplay=20 and another one with a simplified chracter set for searches. Then I=20 added a note to the search forms telling visitors to use the simplified=20 chracters. Not a good solution but at that time it was the best I could=20 come up with. With Unicode it should be possible to use a better solution= . Frank Nordberg http://www.musicaviva.com http://stores.ebay.com/Nordbergs-Music-Store?refid=3Dstore Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Foreign characters (2009) (Frank Nordberg 2009)
  2. Re: [WebDNA] Foreign characters (2009) (Patrick McCormick 2009)
  3. RE: [WebDNA] Foreign characters (2009) ("Olin Lagon" 2009)
  4. Re: [WebDNA] Foreign characters (2009) (christophe.billiottet@webdna.us 2009)
  5. Re: [WebDNA] Foreign characters (2009) (Donovan Brooke 2009)
  6. Re: [WebDNA] Foreign characters (2009) (=?ISO-8859-1?Q?Cristi=E1n_Tapia?= 2009)
  7. Re: [WebDNA] Foreign characters (2009) (Frank Nordberg 2009)
  8. Re: [WebDNA] Foreign characters (2009) (Donovan Brooke 2009)
  9. Re: [WebDNA] Foreign characters (2009) (Patrick McCormick 2009)
  10. Re: [WebDNA] Foreign characters (2009) (Donovan Brooke 2009)
  11. Re: [WebDNA] Foreign characters (2009) (christophe.billiottet@webdna.us 2009)
  12. Re: [WebDNA] Foreign characters (2009) ("Dan Strong" 2009)
  13. Re: [WebDNA] Foreign characters (2009) (Donovan Brooke 2009)
  14. Re: [WebDNA] Foreign characters (2009) (Tom Duke 2009)
  15. Re: [WebDNA] Foreign characters (2009) ("Dan Strong" 2009)
  16. [WebDNA] Foreign characters (2009) (=?ISO-8859-1?Q?Cristi=E1n_Tapia?= 2009)
Dan Strong wrote: > [url][/url]? That won't work since "e" and "=E9" will still be different=20 chracters/chracter strings after [url]. There are two ways to solve this. The best solution is probably to treat all tricky characters as=20 wildcards. Problem is, I'm not sure if it's possible to do wildcard=20 searches with WebDNA. The other solution is to use a table of all the tricky characters and=20 which ones they should be replaced with. This wasn't really an option=20 back in '98 with all the different ascii extensions in use at that time.=20 But today all modern computers use Unicode which make this solution much=20 easier to apply. Of course, ideally this character conversion feature sould be built in=20 to WebDNA. Definitely something to add to the wish list for the next=20 upgrade. 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=20 quick-and-dirty solution I ended up with was to store two different=20 versions of each relevant text block in the databases, one for diplay=20 and another one with a simplified chracter set for searches. Then I=20 added a note to the search forms telling visitors to use the simplified=20 chracters. Not a good solution but at that time it was the best I could=20 come up with. With Unicode it should be possible to use a better solution= . Frank Nordberg http://www.musicaviva.com http://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:

Setting up WebCatalog with Retail Pro data (1996) [WebDNA] [OT] the "Work in progress" thread. (2009) Truncated value after space - refresh my memory.... (1997) Plugin or CGI or both (1997) listfiles, moving files (1998) hard carriage returns and sendmail (1998) Nesting format tags (1997) WebCat 3.04-3.07 plug-in dying on server.... (2000) OT: Typhoon (1998) Personal Web Server (1998) Break out of a loop? (2000) [OT] Deploying XRAID (2003) Delete context run amok (2005) Locking up with WebCatalog... (1997) Install Webcatalog under NT4.0 and Microsoft IIS 2.0 (1997) best way to store prefs (1998) Rendering out a page (1997) Credit card types (1997) Click-through/Referral tracking solution needed (2000) Database of Tax Rates? (1997)