Re: French characters in variables
This WebDNA talk-list message is from 2001
It keeps the original formatting.
numero = 39706
interpreted = N
texte = Larry Trudelle wrote: > > Here's what I am trying to do in simple context: > > I have a search page which gives the user some pop-up lists. The lists are populated from a > DB file using standard web-cat search methods. The user selects a list option, then clicks a > submit button. > The Search values from the selected list are passed to a Results page with Command='search'. > This works perfectly when using the English version. > > The French version requires French DB values, which are just translations of the English DB. > The pop-up lists fo show the French text with the correct accents, > but when the values are passed to the Results page, the text is not the same as whe was sent. > Although some people have gotten things to work using extended ASCII characters, I think it is a mistake to store anything except low ASCII and HTML entities (è). Then the URLized text will be exactly the same as before, but will display properly. That is what the HTML entities are for, after all, which is to encode extended ASCII characters in a form that will display properly no matter what code-set you are using.You need to translate a user-supplied value with [convertchars] prior to using a [search] context. It just so happens that the browser you are using is correctly translating Ne pas déranger into Ne+pas+d%E9ranger but you cannot assume that will always be true (since it depends on the browser). If you have instead Ne pas déranger instead, that will always be translated the same way.John-- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747------------------------------------------------------------- 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:
Larry Trudelle wrote: > > Here's what I am trying to do in simple context: > > I have a search page which gives the user some pop-up lists. The lists are populated from a > DB file using standard web-cat search methods. The user selects a list option, then clicks a > submit button. > The Search values from the selected list are passed to a Results page with Command='search'. > This works perfectly when using the English version. > > The French version requires French DB values, which are just translations of the English DB. > The pop-up lists fo show the French text with the correct accents, > but when the values are passed to the Results page, the text is not the same as whe was sent. > Although some people have gotten things to work using extended ASCII characters, I think it is a mistake to store anything except low ASCII and HTML entities (è). Then the URLized text will be exactly the same as before, but will display properly. That is what the HTML entities are for, after all, which is to encode extended ASCII characters in a form that will display properly no matter what code-set you are using.You need to translate a user-supplied value with [convertchars] prior to using a [search] context. It just so happens that the browser you are using is correctly translating Ne pas déranger into Ne+pas+d%E9ranger but you cannot assume that will always be true (since it depends on the browser). If you have instead Ne pas déranger instead, that will always be translated the same way.John-- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747------------------------------------------------------------- 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/
John Peacock
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:
webcat 2.1 new cart fields - please explain more (1998)
WebCat2 several catalogs? (1997)
show all problem (1997)
Banner Ad example (Typhoon) and WebCatalog (1997)
_ in front of field name (1998)
Re:Email Problem (1997)
[WebDNA] How to get a screen size (2009)
Shownext and search context (2000)
TCP Connect (2000)
New Plug-in and Type 11 errors (1997)
Some Questions (1997)
Use of & in text areas follow-up (1998)
Template Not Found (1998)
[shownext] and sort (1998)
[showif] / [hideif] (1997)
OPEN MARKET PATENTS SOUND ECOMMERCE ALARM (1998)
The [shownext] limitations (2002)
Pgp&emailer (1997)
Blank orders after update to 5.1 (2003)
Summing fields (1997)