• State Verified Answer
  • Replies 10 replies
  • Answers 2 answers
  • Subscribers 434 subscribers
  • Views 8166 views
  • Users 0 members are here
Options
Related

How to import a bilingual Word document for translation

Michael Bauer

I have some clients whose preferred tool is MemSource but Studio doesn't like mxliff and to make matters worse, because I cannot re-assign locales in Studio (at the moment at least), I get the unsupported culture thing because MemSource seems to define it as "gd" but Studio expects gd-GB. Argh.

Anyway, their second preferred option is a "bilingual Word document" but that doesn't seem to sit well with Studio either. On the face of it, this "bilingual Word document" format seems to be a multi-column table with string IDs, a Source colum, a Target column, some column for tagging the translation status and a Comment column, plus some header stuff. But when I try to open this in Studio, it treats the whole document as if it was plain text i.e. if there are translated segments, it also treats them as Source strings.

Does Studio handle this format for translation (not talking bilingual review) and I'm doing something wrong or does it simply not handle this format?
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi ,

    Having the unsupported culture should not prevent you being able to translate the file. You should be able to do this adding *.mxliff to your wildcard identifier in the default Studio XLIFF. But using this plugin is probably a better solution as the tags are handled better:

    appstore.sdl.com/.../

    If you want to handle their bilingual word file then of course you will see that every bit of content in the file will be translatable. Studio has no idea what a memsource bilingual file is. You might be able to handle it if you copy the source to the target column, then hide everything in the file apart from the target. But this leaves you with two issues:

    1. You can't use partially translated memsource bilingual word files
    2. I have no idea how sensitive these files are to being manipulated in this way (Studio bilingual files probably wouldn't like it!)

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Reply
  • 0
    Hi ,

    Having the unsupported culture should not prevent you being able to translate the file. You should be able to do this adding *.mxliff to your wildcard identifier in the default Studio XLIFF. But using this plugin is probably a better solution as the tags are handled better:

    appstore.sdl.com/.../

    If you want to handle their bilingual word file then of course you will see that every bit of content in the file will be translatable. Studio has no idea what a memsource bilingual file is. You might be able to handle it if you copy the source to the target column, then hide everything in the file apart from the target. But this leaves you with two issues:

    1. You can't use partially translated memsource bilingual word files
    2. I have no idea how sensitive these files are to being manipulated in this way (Studio bilingual files probably wouldn't like it!)

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

Children