• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 578
  • Last Modified:

Recode to utf-8 or convert to entity form?

We are in the process of changing the encoding of our site to UTF-8 however we found out that its not just changing the charset to UTF-8 but also changing the characters themselves. I have posted separate questions on this but this question is to ask which is best to do? Is it encoding the pages in UTF-8 Compliant characters meaning not everything are in entity form or covert all non-ASCII characters to entity form?

(1) What will be the problems for each choice?
(2) Which is more readable?
(3) Which has the most compatibility?
(4) We are working wih Dreamweaver, which will have the same result as when working or entering characters in Dreamweaver because we would like to do the maintenance once.
  • 2
2 Solutions

iconv for windows can bulk convert files to utf.

Once the files are converted, change all the webpage meta tags from 8859 to utf-8.

Simple as that I'm afraid.
Hmm.  Just what I was going to post.  Also see

openaccount1Author Commented:
Ok, This is actually more of a poll. I was asking if its better to Recode to utf-8 or convert to entity form? For the solution on recoding please add the solution to: http://www.experts-exchange.com/Programming/Languages/Visual_Basic/VB_Script/Q_25476071.html

Also note that I am not a programmer so I may need something that is ready to use. Another thing is that we may have our html pages not consistently in ISO 8859-1 so we need something that can determine what type of encoding a file really is... e.g. it may be a mixed of ISO-8859-1 or Latin 1 or ASCII.
openaccount1Author Commented:
found our solution. Thanks.

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now