![]() ![]() We know that some of our clients are using XTM just to generate XLIFF file. Is there any way I can translate this file in SDL but still get in back to my client in a format they can use with their new system? Or am I destined to copy and paste the night away? I translated a few segments in SDL and tried to upload it, but XMT does not like it. I was able to download the xliff file from the Cloud. I feel like Fred Flintstone at a typewriter. Not efficient I know, but the available TM is patchy, I have no term base or auto-propagation and using XMT alone is slow, slow, slow. Having read the instructions, the comments on various forums and having started (the first 50 segements) translating a lengthy (but relatively simple) piece of work, I have decided (rightly?) that the best thing for me to do is translate it using SDL Studio 2011 and copy and paste into each XMT Cloud segment. My client has opted to go with this system. Topic: Can I use SDL Studio to return xliff files to XTM Cloud - or am I bound to Ctrl C, Ctrl V? it can have the language suffix that Wordfast automatically put on the clean files). The name of the imported XLIFF is irrelevant (i.e. ![]() To import back your translated XLIFF in XTM, click on the blue arrow pointing upward and choose the import menu item. to generate the clean bilingual XLIFF file. when you are finished translating, choose Save target as. Once imported, WF will create a TXML and will handle the translation as usually done. If translating with Wordfast Pro, be sure to have copied all the sources to targets before doing so, otherwise the translation won't be imported back in XTM once done.Īlso, you will need to set custom filter to import an XLIFF in Wordfast (step by step instruction available on WF wikis). In your XTM inbox, click on the green arrow icon pointing downward and choose "Prepare bilingual XLIFF file and download it". In case of any problems, please write directly to XLIFF files can be generated from XTM project menu-> files tab-> XLIFF If translator did not change number of inline elements and target file will be correctly generated by other CAT tool, than XTM will not have any problems with uploading file back. Other problems are caused by modifying structure of xliff files while generating translated files in external CAT tools (additional spaces, tags). Usually when translators are having problems with uploading translated file back to XTM, their problems are caused by modified number of inline elements (To upload file back to XTM, number of inline elements must be always identical in source and target text). After that, translated file can be uploaded back to XTM (external tool have to maintain xliff format of the file) Such file can be than translated in any CAT tool which support xliff files or in any text editor. The only way of translating projects outside XTM is to create project in our system and generate xliff file. If you think that this trick is too difficult for you, I recommend using Virtaal which is free and very easy to use,Īnd it will enable you to open and translate XLIFF files directly, without preparation.Topic: What's the best CAT to work with XTM exported files? However, the above-mentioned trick can be useful for Note: Wordfast Pro does NOT officially support translation of XLIFF files. To learn more about generating *.properties file, please refer to the article about Translation of XML Files. Those *.properties files might need customization based on the structure of files. If you rather need to translate a source only "standard" XLF, you can use this (*.properties) file downloadable here. General conversion rules (*.properties) file valid for most bilingual "standard" XLF files can be downloaded here. XLF example file (generated by iLocalize) can be downloaded here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |