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.
Tony Hoyle wrote: > Drew F. Sousa wrote: >> Hello, >> >> I'm not positive this is a result of the upgrade 2.0.14 to 2.0.34 but >> this issue appears to have started after the upgrade. It is possible it >> is just coincidental that we've upgraded recently. >> >> It appears that CVS converts UTF-16 to UTF-8 on check out. Converting >> XML in UTF-16 to UTF-8 makes our file invalid since it keeps <?xml >> version="1.0" encoding="utf-16"?> in the header. >> >> Any pointers for me? Thanks in advance. >> > Set -ku on the file so that it knows you want a unicode file on the > output. > > Tony 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. Olaf