Professional Documents
Culture Documents
About Translation - Quick Tips - How To Translate A MemSource Project Using Memoq
About Translation - Quick Tips - How To Translate A MemSource Project Using Memoq
I will probably write more about MemSource in the future. For now a quick workaround if you find yourself
having to translate a project in MemSource but would much rather use memoQ instead - for instance,
because you find that MemSource lacks some feature you love in memoQ, or more simply because you
find that MemSource is slowing you down.
1. Log in to the MemSource cloud, accept your project, pretranslate it, and download it as a bilingual
.mxliff file (just as you would if you wanted to translate using the MemSource desktop editor).
IF YOU NEED MY PROFESSIONAL SERVICES,
2. Open your .mxliff file in the MemSource desktop editor. Join or split all segments that need to be PLEASE CONTACT ME USING THE FORM
joined or split (Important: do this in the MemSource editor - don't wait to do this operation in BELOW:
memoQ: you might end up with a translated file that doesn't load cleanly in MemSource). Save
your file. Name
3. Open memoQ. Create a new project, and add to it your .mxliff file. When adding your document
select "All files" (don't select "All supported files" or "XLIFF files": memoQ doesn't yet recognize
the .mxliff extension, but correctly handles .mxliff files once loaded). Email *
Message *
Send
Search
BLOG LIST
Lo Sciacqualingua
Puntualizzazioni linguistiche (3) - Due
Select "XLIFF filter"
parole, due, sull'avverbio "invece",
che si può scrivere in grafia analitica
5. At this point you'll have successfully imported your file in memoQ, but you'll see that all the
(in vece) e in grafia univerbata
MemSource tags are unprotected. You need to use memoQ's Regex Tagger to protect them. (invece), naturalmente non a caso. ...
6. First, identify all types of MemSource tags in your document. You can do that by simply filtering 18 hours ago
your source text searching for the character "{". Once you have identified your tags, clear your
filter (otherwise the Regex tagger won't work). Training for Translators
7. Go to the Preparation ribbon. Select Regex Tagger. In Tag current document you'll have to add Building relationships with potential
clients, versus just pitching your
the rules to correctly protect the MemSource tags. The rule for protecting the {b> (begin of bold
services - It’s a great time of the year
text) tag, for example, will be \{b>. A more efficient rule that works for {b>, {bu>, {i> and {u>
to do some marketing, when clients
would be \{[a-z]{1,2}>. Repeat, adding all the different types of tags you have in your document.
have returned from their summer
break but before things get really
crazy around the wint...
2 days ago
Terminologia etc.
Grazie e serafini, in inglese in coppia
(minima) - Una spiritosaggine che
offre diversi spunti linguistici ed
etimologici.
2 days ago
Multifarious
Can’t see the wood for the trees… -
Back in 2015 I wrote an article called
“Good bugs… bad bugs!” which was
all about the unintended positive side
effect as a result of computer
software not ...
3 weeks ago
Translation Tribulations
The Invisible Hand of Social Media -
We've probably all been there by now.
The evolution of social media
platforms has seen the "rise of the
machines", with artificial
(non-)intelligence ...
2 months ago
You can translate like you suggest, but that would cripple other translators on the team, because MTPE of Poor Quality Source Texts: Some
they won't get real time updates to translation memory. Practical Suggestions
To achieve the best MT results, you
Reply
should first correct the source text, when it
is a scanned hard copy or an automatic
Replies transcription of re...
BLOG ARCHIVE
What would be a rule for {1} and {1}? \{\d+\} is not working. ► 2021 (7)
Your regex formula should work... if you could send me a sample file I could take a ▼ 2016 (22)
look and see why it doesn't. ► September (1)
► July (2)
Birgitte
Reply 2 5 8 3 5 2 7
Replies THE TOOLKIT
Hi Birgitte,
If you look at the last screenshot above, you'll see that the closing tags are already
included in my example... but you are right, I didn't specifically indicate how to deal
with them: I said
"Repeat, adding all the different types of tags you have in your document."
so, if, following my example, the way to protect the opening tags is NO TO PEANUTS!
\{[a-z]{1,2}>. Join the No Peanuts! Movement
The corresponding way to protect the closing ones is
<[a-z]{1,2}\}.
Reply
Replies
Hi Lion9,
Have you checked whether the languages in your project are in fact different from the
languages in your xliff file?
Depending on the tool, even a slight difference may prevent your tool from working
with a file, if the languages pr sub-languages are different.
I had a similar experiences years ago when I tried to use an EN_US>ITA memory to
translate an EN_CN>ITA file.
If there is indeed a difference, you can solve the problem in various way one is to open
the xliff file in a text editor and search and replace the language codes.
Reply
Hi Riccardo! Thanks for this post. I have a similar issue with MemQ. And thanks for this post I
managed to solve it though I am not much familiar with Regex.
Now the issue is how to export memory files to the cloud server.
Reply
Hello Ricardo. Do you know a way to import other keys than language ones also? I have
something like this:
"
enemies.name.s3_dwarf_axe
CHANGED. Gender: Male
"
But it's never imported.
Thank you!
Reply
"
Thanks again!
Reply
Replies
Hi Elim,
That didn't import correctly in Blogger (I assume it's because it contains tags that
Blogger can't deal with).
If you could contact me via e-mail, and send me a copy of what material you can
share, I'll be happy to take a look. You can email me at the following address:
RSchiaffino {at} aliquantuminc.com
Reply
Replies
Reply
Unfortunately, comment spam has grown to the point that all comments need to be moderated. All
legitimate comments will be published as soon as possible.