What is the best way to convert a memoQ TM to SDL?

Hi Folks,

I am new to SDL Studio. Have done all my work in memoQ so far. Now need to convert my memoQ TMs to .sdltm and am looking for the best way of doing it. Exporting from memoQ to TMX and then importing/upgrading TMX in Studio 2017 results in huge losses/multiple errors (20-40% of the units seem to be lost in the process).

If there a work-around? E.g. some way of trimming a large TMX file to a simple two-column BL table outside CAT tools (I don't care about formatting or any metadata in my TMs, just need bare units) and then importing this table into .sdltm without any loss?

Thanks in advance for any suggestions or pointers to the relevant resources.

Yuri

 

Parents Reply Children
  • Paul and others, 

    Yes, and all the error reports in ‘_error.tmx’ looks like this: 

    <!--Error: TagAnchorNotOpen-->

        <tu creationdate="20110508T110453Z" creationid="Balashov" changedate="20110509T153156Z" changeid="Balashov">

          <prop type="x-OriginalFormat">Unknown</prop>

          <tuv xml:lang="en-US">

            <seg><bpt i="1" type="1" x="1" /><bpt i="2" type="2" x="2" />What is the proposed optional "translational research"?<ept i="1" /><ept i="2" /></seg>

          </tuv>

          <tuv xml:lang="ru-RU">

            <seg><bpt i="1" type="1" x="1" /><bpt i="2" type="2" x="2" />В чём заключаются предполагаемые необязательные «сопутствующие исследования» ("translational research")?<ept i="1" /><ept i="2" /></seg>

          </tuv>

        </tu>

    I looked back at the original memoQ TM and I think I have an idea of what may be creating these problems: the double formatting in these memoQ TM entries, such as bold+italic and bold+underline (please see the screenshot).

    Does this sound right?

    If so could you suggest a good way of getting rid of ALL the formatting tags in a memoQ-generated TMX? Deleting the external tags turned out to be easy: just a single click in the memoQ TM viewer. But the internal tags for bold/italic/underline are invisible there. I’m still playing with Olifant; and my learning curve there is slow. But perhaps there is another way, e.g. doing it manually in Notepad or Notepad++?

    Thanks again!

    Yuri

     

  • Hi Yuri,

    I had exactly same problem when importing several tmx generated by Transit in an .sdltm. For evey TM I converted, I kept the non-valid segments (which you obtain in General import options -> Export invalid translation units), and edited it in Notepad++ with a macro I created myself. This macro simply looks for the elements <bpt...> <ept...> that Studio doesn't like and delete them. Then you save the file and re-import it in Studio TM.

    As an example (depending on the tags you have to delete): the macro looks for &lt;ept(.*?)/&gt; and replace to nothing "" - regular expression activated.

    Hope this helps,

    Almudena
  • This seems that the original source file loaded to MemoQ was actually invalid - the tags are overlapping (bpt1 opened, then bpt2 opened, then bpt1 closed and then bpt2 closed... which is clearly incorrect).

    So Studio is correctly rejecting such mess...

    Since such tagging is completely irrelevant (these would be normally - if placed correctly, i.e. not overlapping - taken outside of the segment), you can simply delete them from the segments and then import the fixed TMX to Studio TM.