This dialog is shown to select the exchange method to be used. Select an appropriate method and press OK. Possible methods are:
|Send original project file to translator||developer -> translator||Sisulizer||Send the original project file (.slp) as it is. This is the easiest and fastest way to send data to translator. However the translator will get the whole project including all existing languages and translations. Translator has to have Sisulizer installed or he or she has to install free Sisulizer Free Edition.|
|Send project to translator using Exchange Wizard||developer -> translator||Sisulizer||Use Exchange Wizard to create an exchange package. This takes some time but let you include only those languages and items that are needed. You can also include Sisulizer Free Edition setup to the exchange package.|
|Import translated project file||developer <- translator||Sisulizer||Use Exchange Wizard to import translations from the project file that the translator has sent. After import process developer's projects contains the same translations as the translator's project.|
|Export project and send exported file to translator||developer -> translator||Other||Use Export Wizard to export the project data to another file format such as Excel, Text or TMX file. Send the exported file to the translator. Use this if the translator does not use Sisulizer but some other translation tool.|
|Import translations from a file||developer <- translator||Other||Use Import Wizard to import translations from the translation file that the translator has sent. Use this if your translator does not use Sisulizer but some other translation tool.|
Note! It is highly recommended that Sisulizer is used as translation tool. It is several advantages over TMX, Excel and text files such as visual editors, validations, context sensitive import/export and so on.