Re: Unusual characters in the db ...
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 42495
interpreted = N
texte = >>>Does anyone know why the ñ (lowercase n-tilde) character that people>>>type into my forms gets converted to Ò (uppercase O-acute) when it's>>>stored in a db -- and what can I do to prevent this problem?>>>>ñ in Mac Roman is Ò in ISO-8859-1. Make sure data is entered with>>the same character set as they're appended to the database. Search>>the archives, I've posted the code for this some times.>>>Hi Christer,>>The part of your instructions from the archives which are clear to me>suggest that we put these tags on every page:>>[SETMIMEHEADER name=Content-Type&value=text/html; charset=iso-8859-1]>[SETMIMEHEADER name=charset&value=iso-8859-1]>>Is this all there is to it? I mean, if this is all I do, will the ñ>characters my visitors type into their browsers get stored properly>in my webcat db's?No. It will be stored as Ò (assuming your server is a Mac server).>The reason I ask is because I have no idea what you're getting at>when you also say:>>Our policy is to store dbs as ISO-8859-1.The whole idea is to make sure all data is stored in the same character set. Otherwise you will have problems with searches.The SETMIMEHEADERs above forces all visitors' browsers to use ISO-8859-1 (also known as Western Roman), both for displaying and entering data.When you know what character set data is entered in you can make any choice you want. Store the data as is, convert it to Mac Roman, convert it to HTML, convert it to MIME - or what ever.If you need to sort results from databases alphabetically, you might probably want to convert the data to Mac Roman before storing it in your databases.>1- If I start using them now, what will 'break' that used to work>fine before I put them into all my webdna pages?Probably not.>2- isn't there certain times when you cannot use [setmimeheader] tags>-- such as on the same page than has [setcookie] or [redirect] or>[returnraw] tags in it? If anyone remembers please post your>response or email me privately, thanks.None of which I'm aware of.-- ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Ljusa Idéer AB S-211 37 Malmoe Fax +46 40 97 99 77 Sweden http://www.ljusaideer.se-------------------------------------------------------------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:
>>>Does anyone know why the ñ (lowercase n-tilde) character that people>>>type into my forms gets converted to Ò (uppercase O-acute) when it's>>>stored in a db -- and what can I do to prevent this problem?>>>>ñ in Mac Roman is Ò in ISO-8859-1. Make sure data is entered with>>the same character set as they're appended to the database. Search>>the archives, I've posted the code for this some times.>>>Hi Christer,>>The part of your instructions from the archives which are clear to me>suggest that we put these tags on every page:>>[SETMIMEHEADER name=Content-Type&value=text/html; charset=iso-8859-1]>[SETMIMEHEADER name=charset&value=iso-8859-1]>>Is this all there is to it? I mean, if this is all I do, will the ñ>characters my visitors type into their browsers get stored properly>in my webcat db's?No. It will be stored as Ò (assuming your server is a Mac server).>The reason I ask is because I have no idea what you're getting at>when you also say:>>Our policy is to store dbs as ISO-8859-1.The whole idea is to make sure all data is stored in the same character set. Otherwise you will have problems with searches.The SETMIMEHEADERs above forces all visitors' browsers to use ISO-8859-1 (also known as Western Roman), both for displaying and entering data.When you know what character set data is entered in you can make any choice you want. Store the data as is, convert it to Mac Roman, convert it to HTML, convert it to MIME - or what ever.If you need to sort results from databases alphabetically, you might probably want to convert the data to Mac Roman before storing it in your databases.>1- If I start using them now, what will 'break' that used to work>fine before I put them into all my webdna pages?Probably not.>2- isn't there certain times when you cannot use [setmimeheader] tags>-- such as on the same page than has [setcookie] or [redirect] or>[returnraw] tags in it? If anyone remembers please post your>response or email me privately, thanks.None of which I'm aware of.-- ************************************************************* Christer Olsson Stora Nygatan 21 Phone +46 40 791 50 Ljusa Idéer AB S-211 37 Malmoe Fax +46 40 97 99 77 Sweden http://www.ljusaideer.se-------------------------------------------------------------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/
Christer Olsson
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:
Looking for host (1999)
Problem with empty form-variables in [search] (1998)
Trouble with formula.db (1997)
WebCatalog can't find database (1997)
OK, here goes... (1997)
OFF-TOPIC: Free webdna.net email addresses ... (2003)
More on the email templates (1997)
Re2: Calculating multiple shipping... (1997)
Various Problems (1997)
Robert Minor duplicate mail (1997)
[shipCost] math formula? (1997)
Help name our technology! (1997)
Interfacing WebMerchant to www.fedex.com (1997)
WebCatalog for guestbook ? (1997)
Me know logical no need (2002)
Bug Report, maybe (1997)
Replace context problem ... (1997)
RE: Error: template (1997)
Ok here is a question? (1997)
Mac app. that converts e-mails (2000)