[cvsnt] Re: UTF conversion issues after upgrade to 2.0.34
Tony Hoyle
tmh at nodomain.org
Mon Apr 5 22:04:30 BST 2004
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
More information about the cvsnt
mailing list