Replace curly to iso 8859

  • Thread starter Thread starter Kim Gjerstad
  • Start date Start date
K

Kim Gjerstad

I recently changed my web.config file to iso 8859-1 for the request
and response encoding.

This created another problem: my forms storing information with data
type varchar suddenly replace all Windows curly quotes into question
marks (?). This didn't not apply with ntext.

This said, I can't find anywhere on the web example code on how to at
least replace the curly quotes.

If you have a clue let me know.

Cheers,

Kim
 
Kim Gjerstad said:
I recently changed my web.config file to iso 8859-1 for the request
and response encoding.

This created another problem: my forms storing information with data
type varchar suddenly replace all Windows curly quotes into question
marks (?). This didn't not apply with ntext.

This said, I can't find anywhere on the web example code on how to at
least replace the curly quotes.

If you have a clue let me know.
Click to expand...

I don't believe ISO-8859-1 includes curly quotes. Any reason for using
8859-1 in particular? In general, I'd suggest using UTF-8.
 
I don't believe ISO-8859-1 includes curly quotes. Any reason for using
8859-1 in particular? In general, I'd suggest using UTF-8.
Click to expand...

That is correct and that's my problem. If I use UTF-8, passing special
characters (such as éàç, etc.) in the URL suddenly causes problems.
Yet, it is essential for the search on my site (http://www.monuc.org)
which actually opens the google search.

Many messages on the groups suggest to change from UTF-8 to 8859 for
foreign language sites. This works well, but the why does it work fine
for the ntext and not varchar? Mystery, mystery.

Cheers,

Kim
 
Kim Gjerstad said:
That is correct and that's my problem. If I use UTF-8, passing special
characters (such as éàç, etc.) in the URL suddenly causes problems.
Yet, it is essential for the search on my site (http://www.monuc.org)
which actually opens the google search.
Click to expand...

Ah, you didn't say it was passing the information on the URL.

Data being passed on a URL is fairly dodgy in terms of encodings,
unfortunately. Can you not make a POST request instead and pass the
data in the body?
Many messages on the groups suggest to change from UTF-8 to 8859 for
foreign language sites. This works well, but the why does it work fine
for the ntext and not varchar? Mystery, mystery.
Click to expand...

Check this, but I believe ntext is unicode and varchar isn't - use
nvarchar instead and you should be okay.
 
Back
Top