Re: Unicode in Visual .NET 2003 and C#
- From: "MasterGaurav" <gaurav.vaish@xxxxxxxxx>
- Date: 13 Jun 2005 22:06:58 -0700
Unicode file will normall have a signature for little endian or big
endian:
FEFF or FFFE
These two bytes are the starting point. I recommend using signature so
that when the file is opened, the encoding is detected automatically.
"Without signature" means without these two extra bytes at the start.
It may create problems mainly because the encoding is not defined and
the editor / file-open must be instructed to consider it as unicode
(little-endian) file.
I recommend to always use the signature.
--
Cheers,
Gaurav Vaish
http://mastergaurav.blogspot.com
http://mastergaurav.org
---------------------
.
- References:
- [newbie] Unicode in Visual .NET 2003 and C#
- From: Kwan
- Re: Unicode in Visual .NET 2003 and C#
- From: MasterGaurav
- Re: Unicode in Visual .NET 2003 and C#
- From: swayze
- Re: Unicode in Visual .NET 2003 and C#
- From: Kwan
- Re: Unicode in Visual .NET 2003 and C#
- From: Kwan
- [newbie] Unicode in Visual .NET 2003 and C#
- Prev by Date: Re: ArrayList.AddRange Error
- Next by Date: Re: event delegate communication question
- Previous by thread: Re: Unicode in Visual .NET 2003 and C#
- Next by thread: Virtual RS232 port on USB
- Index(es):
Relevant Pages
|