Advertisement

06.28.2008 at 01:10PM PDT, ID: 23524270
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
9.3

Encoding problems with UTF-8 compared to iso-8859-1 when working with ASP/VBscript and SQL Server

Asked by Alfahane in Web Languages/Standards, MS SQL Server, Microsoft IIS Web Server

Tags:

I'm have an own webshop system in iso-8859-1 and it works great for english and swedish. But I plan to extend the support to include other european characters so my thought is that the best thing is to "convert" the system into utf-8 and get support for any future language requirements.

I've read however that utf-8 can be problematic and I've even seen it being called "overkill". But my generall opinion is that if you do something then try to avoid limitations if possible.

My experience/knowledge of utf-8 is simply that the characters consists of more bits per character, all documents must be utf-8-encoded and that the input must be in in utf-8 aswell. I don't know what problems the database might cause. I've always used nvarchar, ntext etc in the database to support non english characters (mainly 3 swedish characters that does not exists in english) and I've always thought that that was enough.

There are a lot of discussions on the net about the usage of utf-8 but most of them seem to be the result of frustration rather than objectivity. (It took me a while to realize that one single include file in ASP that is not in UTF-8 will corrupt the encoding in the output and I think there are a lot of people like me) Therefore, I prefer to ask you guys =)

So, what are the common problems when going from iso-8859-1 to utf-8. Are there general problems with using utf-8 even if all the programming is correct? And of course: Is utf-8 the best choice?

I'm working in classic ASP / VBScript and SQL ServerStart Free Trial
[+][-]06.28.2008 at 11:36PM PDT, ID: 21893136

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Web Languages/Standards, MS SQL Server, Microsoft IIS Web Server
Tags: ASP VBscript
Sign Up Now!
Solution Provided By: coldboy
Participating Experts: 1
Solution Grade: A
 
 
[+][-]06.28.2008 at 11:42PM PDT, ID: 21893154

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628