I have some problem on .aspx utf-8 file format.

For example :

my OS is windows server 2003 R2 chinese version, my vs2005 is english version.

by default , default.aspx is saved as "Chinese Simplified (GB2312) - Codepage 936", I want to save my .aspx file into "utf-8".

so i use "Advanced Save Options" save my file into "Unicode (UTF-8 without signature ) - Codepage 65001".

The strange things happened.

I have some chinese characters in my .aspx file, when i re-open the .aspx file, i cannot see the real chinese characters.

Is it a vs2005 bug or how can i resolve the problem?

BTW, if .aspx file is saved into "Unicode (UTF-8 with signature ) - Codepage 65001", there is no problem.

I've jumped this thread some way, but I share with you my experiences about "UTF 8 with signature" vs. "UTF-8 without signature":

I recommend visit this site for unicode infomation. For a faq about utf-8 I recommend this.

A small excerpt from the faq (bold text is by me):

--- 

Q: Can a UTF-8 data stream contain the BOM character (in UTF-8 form)? If yes, then can I still assume the remaining UTF-8 bytes are in big-endian order?

A: Yes, UTF-8 can contain a BOM. However, it makes no difference as to the endianness of the byte stream. UTF-8 always has the same byte order. An initial BOM is only used as a signature ? an indication that an otherwise unmarked text file is in UTF-8. Note that some recipients of UTF-8 encoded data do not expect a BOM. Where UTF-8 is used transparently in 8-bit environments, the use of a BOM will interfere with any protocol or file format that expects specific ASCII characters at the beginning, such as the use of "#!" of at the beginning of Unix shell scripts.

---

In the past some times I got strange characters on the top of my plain html pages (UTF-8 with signature): that was the signature which was displayed by the browser! (The answer for this is the bold text ) For aspx pages I've never seen that, so it is probably safe to go with UTF-8 with signature.