Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
This is an issue haunted me for a long time, and after trying Studio 2014 it seems no conspicuous solutions yet. Let me explain the term "asymmetric" here, there are a bunch of files, and a part of which require a little different target language translation, e.g. A.doc, B.doc, and C.doc require en-US->zh-CN language pair, but B.doc and C.doc only require en-US->de-DE language pair, now it is so called "asymmetric". For a long time the turnaround solution is to create a project including all the files, and after the project creation swith to the different target languages in the Files view to delete the unnecessary files. The disadvantage is obvious if the quantity of required target languages goes up, either tended to delete by mistake or waste a considerable time of unnecessary files analysis. I wonder if the adding project files dialog during the project creation could be smarter, for example, adding files for each language respectively. How is this idea? Hopefully the dev team could consider it.
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
To report site rules violations or get help, contact a site moderator:
Kilgray's memoQ is the world's fastest developing integrated localization & translation environment rendering you more productive and efficient.
With our advanced file filters, unlimited language and advanced file support, memoQ translator pro has been designed for translators and reviewers who work on their own, with other translators or in team-based translation projects.
Guarantee a unified, consistent and high-quality translation with terminology software by the industry leaders.
SDL MultiTerm 2019 allows translators to create one central location to store and manage multilingual terminology, and with SDL MultiTerm Extract 2019 you can automatically create term lists from your existing documentation to save time.