![]() #Xliff editor mac 2016 proThere are, of course, sometimes inherent differences in efficiency to be found between working environments - the current column grid paradigm used by Trados Studio, memoQ, WordFast Pro and others is probably some 20 to 30% more efficient than the over/under arrangement for translation in the confused bilingual view of WordFast Classic or Trados Workbench and probably OmegaT as well. I've found that unfortunately many translators have a very poor understanding of ergonomics and efficiency, and most do not realize how much switching between various CAT tools can slow down one's output, particularly for small jobs. However, I generally think it's good to avoid switching translation tools to accommodate particular file types where there is an alternative to work in one's usual environment. Then SDL Trados Studio will identify the languages in the XLIFF file correctly and open the file without warnings or errors. In my case, that would mean setting the memoQ project to DE-DE and EN-US rather than just DE and EN for the source and target languages. Another way to deal with this if you are aware that Studio will be involved is to use sublanguages in the environment that generates your XLIFF file.But still, it worked, and the content could be edited or fed to a TM. In the case of my XLIFF file, generic German and English were set, so when I changed the defaults in Studio to DE-DE and EN-US, the file opened, but I was warned that the language abbreviation in the XLIFF file was not "fully qualified" (a common German obsession). ![]() Set the source and target languages in Studio to something in the same language group as the source and target language of the XLIFF file.There are two ways to deal with this problem if you need to import an XLIFF file from another source into Trados Studio: The source language in the XLIFF file I attempted to open was German. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |