[cvsnt] Re: UTF conversion issues after upgrade to 2.0.34

Tony Hoyle tmh at nodomain.org
Tue Apr 6 08:14:04 BST 2004


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


Olaf Groeger wrote:

> 
> But be aware that this must be UTF-16 BE including BOM (0xff 0xfe). All
> other UTF-16 (LE and/or no BOM) will be silently damaged.
> 
LE isn't common on intel systems (in fact it's basically unheard of).  The 
file is still a perfectly valid Unicode file - the BOM is part of the 
standard, precisely to avoid the problems distinguishing between LE and BE.

If you want the exact file use binary mode... you lose merging though.

Tony



More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook