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.
I just updated to 2014. I have a multilingual TermBase. I think that at some point, my TB may have been corrupted, because when I add the TermBase to a translation project, and I am using Spanish as the source language, in the "Languages" window at the bottom of the screen, the TermBase language shows as "Latin" (rather than Spanish).
This also happened in 2011, but all I needed to do was to correct that tab and make it "Spanish" instead of Latin.
However, ever since beginning to work with 2014, whether I correct the language from Latin to Spanish or not, when I add terms directly to the TermBase through the editor view in Studio 2014, the Spanish term is added under Latin. I know I can cut that term and paste it to the Spanish entry, but this takes a lot of time and slows things down considerably.
Anyone ever have a similar experience or know how to fix this?
Thanks in advance!
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:
WordFinder is the leading dictionary service that gives you the words you want anywhere, anytime.
Access 260+ dictionaries from the world's leading dictionary publishers in virtually any device.
Find the right word anywhere, anytime - online or offline.
Translation Office 3000 is an advanced accounting tool for freelance translators and small agencies. TO3000 easily and seamlessly integrates with the business life of professional freelance translators.