Why there are mis-encoded characters in the cvs log file?
Posted by Alan Huang on 03 January 2012 02:50 PM

The logs are encoded as Unicode (UTF-8) in the cvs file. To read the logs properly, please open the file with any text editor or program which supports Unicode encoding, like OpenOffice.


Applied Models: All NAS series

(0 vote(s))
Not helpful

Comments (1)
09 June 2012 05:33 AM
I have found some information about this.Though it is posibsle at the time a script is saved to change the encoding to ascii it is tedious. Here is the process.1) Choose File\Save As2) Choose the name and folder to save the file then look really closely at the right edge of the Save button for a tiny arrow.3) Click that tiny Arrow and choose Save with Encoding 4) From the Drop list select the encoding you want (the default encoding is Unicode Codepage 1200 , which means UTF-16 ). I have been using US-ASCII Codepage 20127 .5) Hit OK and Save. Your files should now work just fine with Perforce, CVS, etc.There is not currently (or as far as I know planned) a way to change the default encoding for these files, but I have submitted a feedback to the SQL team and would request anyone affected by this issue to add their voice so M$ knows how important this is. Here is the URL of my feedback: