Using Memsource

Start here, Lena Nørgaard Madsen (Unlicensed)

Related pages

Table of contents

 

 

If a file cannot be processed in MemSource, price estimation is not possible and the workflow is stuck.

Frequently asked questions

 

The files are uploaded but the text contains segments looking like codes and is not suitable for the translator to view:

This is an indication of upload processing containing incorrect settings. First open the original file to understand what type it is, what kind of raw text looks like and what is not being imported or uploaded correctly into MemSource. These informations provide baseline for which approach of solution is best. Then try to understand what kind of "noise" is in the document, is it HTML tags or other form of tags?

 

 

MemSource simply fails to upload the file and throws me a red exclamation mark.

 

Hover over the exclamation mark and read the error message. Usually write "memsource + error_message_here" in Google can lead to some information.   If no solution is found, create a ticket with the error message and the MemSource link together with the platform PO link.

 

---

ServiceDesk ticket format

 

Platform PO: xxxxx 

(With link): https://.....

 

MemSource Project Link: https://....

 

Problem description:

The text in the file does not look correct: file segments looks wrong, examples .......   or please see screenshot: ....

 

 

 

---

General file knowledge

 

Upload settings

How to use the MemSource upload settings:

When a file is uploaded, MemSource will take the file extension and decide which setting box to trigger. E.g. "translation.docx" will automatically trigger the setting box for Docx.

Some times the files should be enforced to a specific setting box, for instance the ".xml" extension will auto trigger the XML setting box, however since this type of files could be bilingual, there is a need to use a separate setting box - namely the "Bilingual XML".

 

To enforce a file type, scroll to the bottom and find "File type" setting box and choose the desired file type instead of the default "Auto-Detect" option.

 

Process HTML

HTML formatting can appear in various file types, such as excel, xml or even txt.

In these cases if the HTML tags are not processed, the translation job will have segments filled with HTML tags. The way to identify HTML tags is the bracket system that it uses:

Usually when you see a tag enclosed by brackets such as <sometag>, it's HTML tags.

MemSource can handle these tags by checking "Process HTML" in different file type settingboxes. Whenever this is selected, the HTML setting box also activates for this file. In the HTML setting box, choosing "Preserve Whitespace" will help ensuring the text layout in the delivery output file.

 

 

Process "Convert to MemSource tags"

In some cases we receive code files that contains translatable text, see below for example.

...

codified_variable = "some text that needs translation"

...

The left side of the equation mark is a variable in the code which should not be translated. The only thing that needs translation is the right side of the equation. In this case we can handle the files as txt format and use Regex codes to target structured texts like this.

 

SOMETHING ABOUT REGEX...

 

Viewing content in files

Some files require applications installed to view the content, such as Microsoft word files or powerpoint files. 

Other file types are text based, in which case they can be opened with Text Editor or a more advanced app such as Sublime Text. 

It is important to view the content to understand and identify what needs to be translated, essentially the text segment is the source of the word count which is used for price estimation and quoting. If the file is incorrectly uploaded, the wordcount and price will be faulty and would lead to several issues in the workflow.

 

 

---

Document type and instructions

For each document type, the official MemSource instruction and tips can be viewed:

 

Overall file handling can roughly be divided into two categories:

Monolingual file handling

The translated target text replaces the original text in the document, resulting in a monolingual output file for delivery.

Monolingual File handling

Generic text format, these files can usually be opened without issues and the text to be translated can be identified.  https://wiki.memsource.com/wiki/MS_Word

 

Same as docx, usually no additional change required. https://wiki.memsource.com/wiki/MS_PowerPoint

 

In most cases the required action would be to select the columns that should be translated. This can also be done by hiding unnecessary columns when reviewing the file directly in Excel. https://wiki.memsource.com/wiki/MS_Excel   However if HTML tags are visible after uploading the file, then the option for "Process HTML code" should be checked.  Whenever a "Process HTML" checkbox is enabled, the rules within HTML collapsible setting box is also used during the processing of this file. In this case remember to check "Preserve Whitespace" in the HTML setting box. https://wiki.memsource.com/wiki/HTML

 

https://help.memsource.com/hc/en-us/articles/360001502271 InDesign files   https://wiki.memsource.com/wiki/Adobe_FrameMaker FrameMaker files

 

https://help.memsource.com/hc/en-us/articles/360001501131 write lots and lots here

 

https://wiki.memsource.com/wiki/CSV ....

 

https://wiki.memsource.com/wiki/JSON

 

https://wiki.memsource.com/wiki/Zip_Files

 

 

Bilingual / Multilingual file handling

In these cases, the client wish to have the translated text in a specific place (e.g. a new column in excel). This means the original source text is not changed and the output file is a bilingual / multilingual file that contains segments in all relevant languages.

 

Bilingual Excel

 

Bilingual XML

 

Xliff

 

...

---

Procedure overview

 

1. First to understand and describe the issue. The more detailed description will largely enhance the speed of finding a solution.
   1. Review xxxx for opening certain files
2. Ask experienced LA regarding the issue described in step #1. This could help on finding the quickest fix as well as enhance communications to unify different solutions.
3. Review the Wiki articles, use the search function to quickly look up keywords. 
4. Create a service desk ticket to request assistance. In the ticket include the description of the issue, platform PO link and MemSource link.
5. In cases of resources not able to immediately respond to the ticket (workload / holidays), the ticket content will be send as email to MemSource support. This is why the description in #1 is important, if the description is insufficient then the first few exchanges of email will turn into understanding the issue rather than finding solution to the issue.

---

 

 

 

Other info

When analysing XML and CSV files and pretty much any other format (.po, wordpress xliff, html, excel etc ) that has the option to "Convert to Memsource Tags" you can use the following regex expressions to tag the string that you want.

Important: Always double check if the tags were applied as intended.

Special file settings in Memsource

Wordpress XML files

For Wordpress XML files please follow the instructions provided by Memsource here:

https://help.memsource.com/hc/en-us/articles/115003484332-Importing-Wordpress-XML

Depending on the case you might need to add other regex codes, besides the ones recommended on the Memsource dedicated page.

Very often: 

\[[^\]]+\] - for [variable]

\{[^\}]+\} - for {variable}

or \[[^\]]+\]|\{[^\}]+\} for [variable] and {variable}

 

Wordpress xliff files

1. Set file type to Wordpress Xliff
2. Go to the HTML subfilter and try this \{[^\}]+\}|\[[^\]]+\] in the "Convert to Memsource tags" to transform {varialbele} and [variable] in to Memsource Tags

 

More examples can be found here: https://help.memsource.com/hc/en-us/articles/115003930072-Regexp