If your XLS or XLSX file is multilingual plain text, you can import it as several bilingual jobs to Memsource in one go.
To do this, map the corresponding target language columns in the File Import Settings. This will create separate jobs for each language pair, while in the background the file will remain as one. And when you download the completed file after translation, you will have a single Excel file containing all languages.
A few things to note about this process:
- Translating multiple sheets in Multilingual Excel is not supported. Only the first sheet can be used for import and export of translatable text.
- Excel files are converted to XML 2003 Spreadsheets when imported—most of the Excel formatting, graphs and images will be lost.
- Some files cannot be converted to multilingual files due to compatibility issues between various versions of Microsoft Excel.
File Import Settings:
1. First, be sure to select Multilingual MS Excel in the File Type field. (This is bottom of the File Import Settings page). If you fail to do this, the file will be imported as a regular Excel.
2. Then you can then open the Multilingual MS Excel section and select the following options:
- Use HTML subfilter: If your XLSX file contains any HTML tags, it can be imported with the HTML Subfilter option. In this case, it is possible to set additional settings in the HTML. (For example, a break tag (<br/>) would create a new segment.) Please note that paragraph tags (such as <p>) will create new segments even if Segment Multilingual XLS is unselected.
- Segment multilingual XLS: It is safer to have one cell as one segment, but you can choose to have text segmented by a general segmentation rule. (Please note that the above-mentioned HTML subfilter is an exception.)
Using Segment multilingual XLS on a file that contains target text may result in a different number of segments in the source and in the target.
- A warning will be displayed on the project page: "Document segmentation resulted in a different number of source and target segments in some paragraphs. Extra segments have been joined with previous segments using space characters except in non-space languages (e.g., JA, ZH, KO). Try importing without segmentation."
- A segment comment will be added to the job in the Memsource Editors: "Target is not segmented as expected!".
- Source (column): Here, you can use lowercase or capital letters (a or A). For more columns, enter letters separated by commas with no spaces (for example A,D,G).
- Target (column): There is one column for each target language. For more columns, enter letters separated by commas with no spaces (for example B,E,H).
- Import specific rows only: Enter rows to be imported (for example 1,4,7).
- Context key (column): Here, you can specify a context key that will be saved with the segment to the Translation Memory. This is available by going to File Import Settings, selecting TM Match Context and Optimization and ensuring that the Context Type is set to Segment key.
- Context note (column): It is possible to have more columns as a context note (B,C). The notes will be displayed on separate lines.
- Maximum length (column): This sets the maximum length of the translation. For more columns, enter letters separated by commas, with no spaces (for example I,J,K).
- Convert to Memsource tags: Use Regexp to convert non-translatable text into Memsource tags.
XLSX File example
Below, you'll see an Excel file with two context notes and maximum target length:
Jobs in Project
Multilingual jobs have a slightly different icon then general XLSX jobs so that they are easily distinguished from monolingual jobs.
If the file was imported as a multilingual file into several target languages, the Completed file will be always composed of all the target languages.
In-context Preview Limit
The In-context Preview in the Editor can only be generated for a maximum of 200 columns in the imported file. A file with more than 200 columns will have the following warning displayed in the project: "In-context preview was not generated." and the in-context preview will not be available in the Editor. This limit doesn't apply to the hidden columns—if the original file has more then 200 columns but they are "hidden", then the preview will be created.