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.
Since Studio 2009 can't handle International or Latin American Spanish (I was told the languages will be re-mapped but I don't know if that will fix the problem), I'm using the TM fields to determine the proper sub-languages for each project. So I want to do a similar thing with my termbases and use the definitions to set the corresponding sub-language.
I just don't know how to do this. I have a Multiterm 7 termbase in English to Spanish (Spain) and Spanish (Latin America), and I want to create an Multiterm 8 termbase and import all the terms as one language, English to Spanish rather than English to Spanish (Spain) or (Latin America).
So basically I want to change Spanish (Spain) and Spanish (Latin America) to Spanish. Is this possible?
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:
Modern desktop project management for freelance translators
BaccS makes it easy for translators to manage their projects, schedule tasks, create invoices, and view highly customizable reports. User-friendly, ProZ.com integration, community-driven development – a few reasons BaccS is trusted by translators!
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.