Lightening the load: leveraging multiple resources at once
Translation memories (TMs), term bases (TBs), LiveDocs – these resources are truly the lifeblood of localization teams. Every day, memoQ users access, create, exchange, import, archive and/or delete hundreds, even thousands, of these resources. Keeping track of them all can be tricky. Now, thanks to the latest enhancements, those resources can be batched to make life a little easier.
With memoQ 9.4, you can:
- Add/remove multiple LiveDocs corpora in projects.
- Provide “Can delete resources in batch” permission to user groups in the Server Administrator (desktop and browser).
- Delete (and optionally export) multiple TMs, TBs and LiveDocs corpora.
- Export multiple TMs, TBs and LiveDocs corpora in batches.
- Import multiple TM files.
- “Select All” via a new context menu option.
Hustle, not hassle: improvements to MT plugins
Enterprises and language service providers are increasingly relying on machine translation (MT), especially for large projects. That’s why memoQ is always looking for ways to improve the performance and reliability of MT plugins.
Here are some of the enhancements in memoQ 9.4:
Microsoft MT plugin. Segment exclusion is now possible.
Intento MT plugin. Not only have issues with translating tagged documents been fixed, but glitches with Smart Routing have also been eliminated. Plus, this plugin now supports of HTTP proxies for those users with specific security requirements or network restrictions.
Integrating private MT plugins has been made much easier.
Tilde. A small but important update has been made in code handling, mostly related to Norwegian.
No more “zombies” – Resource Console gets a revamp
Maintaining and keeping track of resources can be exhausting. Is that translation memory (TM) still in use? Has that term base (TB) been modified recently? Which ones are “zombies”, no longer used and just taking up valuable server space?
Questions like these are now a thing of the past, thanks to a revamped Resource Console. Everything’s cleaner, crisper, smarter.
New filter fields, new sorting options and new columns for displaying metadata mean you always have an overview of your resources.
New assignment workflow with memoQWeb
Your project deadline just got changed. Again.
But fear not – with memoQ 9.4, you’re prepared for the unexpected. You can now select multiple documents on the Translations page in memoQWeb and change the assignees, deadlines and statuses all in one go. Easy.
Content Connector: integration is everything
Content Connector is all about integration. What is more, it can be customizable integration. The list of what can be integrated is almost endless: Content Management Systems (CMS), Product Information Systems (PIMS), Component Content Management Systems (CCMS), Marketing Automatic Systems, among many, many others. With the proficient help of memoQ's Business Service Team, we can custom tailor integrations to your specific needs.
In memoQ 9.4, we are making changes to Content Connector in order to further enhance the work of memoQ's Business Service Team. These modifications aim to empower the team to provide our customers with the right solutions for their industry or team specific, unique requirements. The modified Content Connector will enable easier development and wider functionality for automated integrations with Content Management Systems.
To this end, the deployment of Content Connector connectors will be independent of the memoQ release cycle and its licensing protocols. What that means is the memoQ Business Services team will have a lot more options at its fingertips to help users looking for integrations.
With Protemos, integration is just one click away
We are excited to share the news that Protemos and memoQ are now integrated.
This is something that many users have requested and it will ensure the smooth transfer of projects between the two systems. Whereas users used to have to spend a lot of time and effort on manual copy-and-pasting, this new integration streamlines the whole process.
With one click, Protemos projects can be reproduced with the details about language pairs, deadlines, client info and files from memoQ. It works the other way, too, with users able to pull Protemos projects into memoQ simply and seamlessly.
What’s even more compelling about this integration is just how easy it is to use and to set up. It takes just a few minutes, and no special training is required.
Notable features worth mentioning: Trados Studio TM direct import and Grammar Check
Here are a couple of additional enhancements you’ll find in memoQ 9.4:
Grammar check: ignore once. Previously, this feature skipped an entire segment, not just a single instance of an error. This update is surely going to be a major help to anyone who needs to run grammar checker in memoQ.
Trados Studio TM direct import. SDLTM files can now be directly imported into memoQ TMs even outside packages, making life a little easier for users collaborating with partners who use SDL Trados.
As we strive to further develop memoQ for the specific needs of various industries, we would like to invite our users to partake in our Usage Data Collection, which we are expanding in memoQ 9.4.
With the full consent of users, and on an opt-in basis, of course, we will be able to collect demographic data. By doing this, we will be able to get a better handle on user needs and concerns and provide even more useful and relevant product updates.
Change logs
BUG-813: Adobe PDF filter: An error in the Aspose library causes out of memory exception when importing a document
BUG-3660: An incorrectly formatted currency code can make quotes on Customer Portal unreachable
BUG-3697: An issue related to the login process of Active Directory users may cause memoQ Server to not provide CAL licenses to such users for the false reason of unsuccessful login attempt
BUG-3443: Machine Translation: Amazon MT: Poor information on terminology import failures
BUG-3619: Machine Translation: DeepL MT: Pre-translation may not work for Japanese
BUG-3646: Machine Translation: Kantan MT: The plugin may not work because of unaligned communication of supported languages
BUG-3631: memoQ Server WS-API: If you add a segment to a translation memory using the WSTM API, you may find its contained tags appearing in different order in the result of a corresponding lookup operation
BUG-3424: memoQ Server WS-API: Online projects created in Plunet may disappear in memoQ in rare errors related to document delivery
BUG-3686: memoQWeb: The status of a Customer Portal customer may be different in the new and the legacy PM application
BUG-3684: memoQWeb: The telemetry opt-in dialog contains a typo
BUG-3682: memoQWeb: The translation of "Admin" button is incorrect in German
BUG-3452: memoQWeb: You cannot log in to memoQ using your Active Directory or Windows credentials
BUG-3532: memoQWeb: You may see undefined language pairs in discussions under rare circumstances
BUG-2497: Microsoft Word (DOC, DOCX) filter: You may be unable to export a document for said incorrectly paired inline tags, though QA check doesn't indicate any such issues
BUG-3297: Multilingual Delimited Text (CSV, XLSX) filter: A bug in the Aspose library results in the corruption of exported Excel XLSX workbooks
BUG-3745: Multilingual Delimited Text (CSV, XLSX) filter: The Unicode BOM marker may be changed in exported documents even if the option to keep the value found in the source document is turned on
BUG-3667: PHP filter: You may not be able to import documents containing comments inside arrays or text mixed with values in arrays as expected
BUG-3577: QTerm: If you click "Related topics" for a QTerm term in the legacy memoQWeb, you are taken to your project dashboard instead of the related discussion topic(s)
BUG-3522: QTerm: If you create or edit a filter, you cannot apply it straight, since results of the default filter are shown first
BUG-3696: QTerm: The icon of the "View/add/remove related entries" command may disappear
BUG-3548: Quotes are displayed instead of apostrophes in HTML QA reports with the "Check translation memory" option selected
BUG-3565: SDL Trados Document (SDLXLIFF) filter: Exporting a document may fail if a segment contains unpaired closing tags in a track change range
BUG-2727: SDL Trados Document (SDLXLIFF) filter: The status of a segment which was populated using machine translation may change to suggest it's a manual translation, instead of preserving the MT origin
BUG-3545: The "Custom" label is shown instead of the custom filter's real name on the "Document import options" dialog
BUG-3501: The "Store full path" translation memory option is not observed for Confirm and Update operations performed on memoQ servers
BUG-3677: The telemetry opt-in dialog contains a typo
BUG-3651: XLIFF filter: An error in state mapping logic might prevent you from successfully configuring xliff:doc filter configurations
BUG-2651: XLIFF filter: If you export a document right after importing it, you may receive warnings about empty trans-unit elements, and the exported document may become corrupted
BUG-3553: You can create projects from templates with duplicate target languages, rendering those projects unable to be opened
BUG-3661: You cannot add new target languages to online projects running on memoQ 9.0 or 9.3 servers using memoQ 9.4 clients
BUG-3525: You may be unable to edit a remote MT settings resource under rare circumstances
BUG-768: You may receive a false QA warning claiming for missing numbers when only the order of date parts is different
BUG-3643: You may receive an error when you try to export the results of a term extraction session to a termbase in a scenario where two memoQ Servers are connected and the vendor's child server only has a reference to a termbase instead of having a full copy of it
BUG-3596: You may receive an error when you try to perform term extraction in a scenario where two memoQ Servers are connected, and the vendor's child server only has a reference to a termbase instead of having a full copy of it
BUG-3589: You may spot negative values for database size in the Storage tab of Server Administrator
Improvements:
BUG-3290: Improvement: Damaged version histories of documents might have caused memoQ servers to become unresponsive or unreachable
BUG-3472: Improvement: Machine Translation: Microsoft MT: You can configure your service location (region) when configuring the plugin
BUG-3609: DeepL: memoQ returns MT match with Unicode decimal code
BUG-3588: Statistics: Cannot run statistics in an online project on server 9.3 with 9.4 client
BUG-3587: Deepl MT throws back unsupported language error although DeepL supports the language pair.
BUG-3570: Cannot synchronize offline TM nor creating an offline TM from an online TM when using 9.4 client on a 9.3 server.
BUG-3236: Custom code execution performed at export in API-generated projects may cause crash
BUG-3367: FindAndReplace utility: Running the FindAndReplace script causes the encoding of the processed files to change to UTF-8-BOM
BUG-886: Importing the same TMX file to a local and an online translation memory may result in different number of imported segments containing no text or containing only a single entity with identical source and translation
BUG-3164: Machine Translation: DeepL MT: You may not be able to connect to the MT provider using a TLS security protocol older than TLS 1.2
BUG-3300: memoQWeb: If you want to edit a term via the context menu of the term in WebTrans, you are redirected to your home page
BUG-3420: memoQWeb: The "Deliver to Customer Portal" command may be missing
BUG-3308: Microsoft Outlook (MSG) filter: An error in the Aspose code library may cause an error when you try to import an email message file
BUG-3120: Pre-translation may fail for specific segments in Korean to Russian projects
BUG-3481: QTerm: If you generate a PDF document from the glossary or the pretty print view of a termbase, you may be able unable to download the file if the name of the termbase contains characters with umlauts
BUG-3492: QTerm: You may be unable to open a termbase as an admin user if there is no permission granted for the admin user explicitly
BUG-2902: The message informing the user about the expected length of the server administrator's password contains an invalid condition on the maximum length
BUG-3267: Whitespaces may be displayed incorrectly when you view compared document versions with tracked changes
BUG-3183: YAML filter: "\n" characters may be exported as actual line breaks instead of "\n" strings
BUG-3471: You may not be able to configure project templates to use LiveDocs and TMs, as well as MT plugins in the course of pre-translation auto actions
Improvements:
BUG-3489: Improvement: If you reassign a document previously assigned with FirstAccept to a specific user, that user won't be invited for FirstAccept automatically
BUG-3256: Improvement: If you select multiple translation memories or termbases in a project, you can quickly add/remove all of them by clicking one of the Use/Remove checkboxes
BUG-2779: Improvement: memoQ Server Resources API: The Created, Creator, Modified and Modifier fields required for term creation are observed
BUG-2643: Improvement: memoQWeb: Manual changes to the document filter configurations of documents for which template-based filter configurations apply are observed
BUG-3255: Improvement: Supported languages for Google, DeepL and Amazon MT plugins can change dynamically
BUG-3259: Improvement: Use/Remove All checkbox added for adding/removing all translation memories or termbases to/from a project
BUG-3126: Improvement: User-specific unsigned private MT plugins can be deployed on memoQ server instances
BUG-3484: Improvement: You can add QTerm termbases to projects even if the set of languages are not exactly the same in the two
Initial 9.4 release was 9.4.7