We can use VSSConverter for migration of Visual Source Safe repositories and CQConverter for migration of ClearQuest work items to VSTS in globalization setups or in localization scenarios supported by Visual Studio Team System.

 

When we use VSS, CQ Converters in Globalization/Localization scenarios, we need to make sure to save the configuration xml files with correct encoding scheme.  Configuration xml files can be saved in different formats like utf-8, utf-16 (Unicode).

 

For example, consider the sample VSSConverter migration settings xml file below. This contains some extended characters on CHS OS (i.e.., DBCS) for VSS repository name, destination project name and migration report. If you are using notepad, when you save this settings file by File->Save, by default the encoding scheme is ANSI. If you save this settings file with this default option, you will get an error during migration.

 

 

So, if you are planning to use utf-8 encoding scheme as in this example, you have to explicitly choose the encoding schemes to utf-8 while saving the file as shown below:

 

If you want to save with Unicode encoding in the above example (See Unicode option above), make sure to change the encoding section of Migration configuration xml file from:

 

<?xml version="1.0" encoding="utf-8"?>

<SourceControlConverter>

<ConverterSpecificSetting>

 

To

<?xml version="1.0" encoding="unicode "?>

<SourceControlConverter>

<ConverterSpecificSetting>