Project managers can now create the following reports in memoQweb via the Reports tab:
A new Scope column on the Reports tab helps project managers quickly assess whether a report meets their needs. The column shows the number of files included in each report, and selecting a cell reveals a detailed list of all documents, making it easy to evaluate the report’s relevance and suitability.
Project managers can now download one or more reports directly from memoQ. Clicking the Download button opens a dialog to choose the report format (HTML or CSV), making it easy to include in purchase orders.
Project managers can now preview reports immediately after creating them, making it easy to check their usefulness before downloading or sharing.
memoQ server administrators can now set weighted word counts (WWCs) directly on the web, ensuring project managers see accurate WWCs when generating analysis reports for their projects.
Import filters are now available in memoQweb, allowing you to import, clone, rename, update descriptions, and delete filter configurations. Support for creating and editing filter settings will be introduced in future releases.
The Find & Replace panel in memoQ editor now goes beyond text. You can search in tags, comments, and context IDs, and use regex in all kinds of searches and the replace function in text. This upgrade delivers powerful precision for language engineers, project managers, translators, and enterprises.
memoQ 12.1 introduces a new tracked changes panel in memoQ editor, offering advanced navigation and the ability to accept or reject changes individually or in bulk. This gives linguists clearer control in projects where documenting edits is essential.
memoQ 12.1 introduces a status bar in memoQ editor, giving linguists role-based progress tracking and detailed segment information, while PMs and administrators see team averages. The update also adds Context ID display, providing valuable metadata for gaming and localization workflows.
memoQ 12.1 adds Join and Split commands to the Segment menu, allowing linguists to fix incorrect segmentation directly in memoQ editor. These tools help maintain translation memory integrity and ensure segments reflect the correct sentence structure before translation.
memoQ 12.1 introduces a more powerful filtering experience in memoQ editor. You can use regular expressions, combine or clear previous filters, choose what to filter (text, tags, comments, context IDs), apply preset or custom criteria, and even filter by changes or specific tag types.
memoQ AGT now skips all “forbidden terms” from your term base or Qterm, keeping translations accurate and compliant.
Public cloud users can now use the new Calculate now button in Server Administrator → Storage to get an immediate, accurate view of their storage usage without waiting for the next daily backup.
memoQ now aligns its Latin American Spanish language codes with DeepL’s new ES-419 code, ensuring smooth integration and accurate language matching when using DeepL for translation.
Project managers can now include memoQ’s automation framework, AGT, in template-based automated actions. When configured, translation with AGT runs automatically at key project lifecycle events.
With AGT integrated into automated actions, project managers can create fully automated pre-translation workflows that combine the strengths of TM, AGT, and MT for optimal results.
memoQ 12.0 improves AGT’s tag handling across all formats (from everyday files to complex structured DITA content used in CMS, CCMS, or any other systems) ensuring that formatting is preserved and translations remain accurate.
These updates build on the tag handling introduced in 11.6, further enhancing accuracy and ensuring more precise translations when AGT works with TM matches.
The browser-based memoQ editor now gives linguists and project managers more flexibility, speed, and control, with many improvements coming from user feedback, including requests submitted via the memoQ Users’ Ideas Portal.
For more details on these technical changes, please visit our Pressroom announcement.
memoQ 11.5 brings major improvements to the memoQ editor, our new web-based translation application for linguists working with organization licenses.
DeepL speeds up pre-translation for larger volumes, helping you move through big projects more efficiently.
Project managers can now export all project files in multiple formats directly from the Projects list:
Spelling can now be selected as a separate QA category in ICR configurations, offering more detailed quality assurance settings.

In this release, we are excited to introduce memoQ editor, our new web translation interface designed for linguists working with a license provided by an organization. memoQ editor is set to gradually replace webtrans as new features are added in each new release.
To explore memoQ editor’s features, benefits, and future developments in more detail, check out our in-depth blog post.
The Inverted Color Scheme introduced in memoQ 11.2 has received major updates. For a detailed overview, check out our blog post.
memoQ 10.2 (LTS) retires on January 31, 2025
Support for memoQ 10.2 (LTS) will end on January 31, 2025. The new LTS version, memoQ 11.2, will be supported until at least January 31, 2026. Users of memoQ 10.2 are advised to upgrade as soon as possible to ensure a smooth transition.
memoQ AGT can now be configured as an online resource, enabling the central management of the API key. Linguistic teams can access the same MT settings, with the AGT API key configured by a PM. This streamlined approach enhances security and simplifies project management, ensuring a more efficient workflow.
memoQ AGT now supports online projects. Previously, memoQ AGT could only be used in local projects or in checked-out online projects. Translations can be initiated directly in WebPM, eliminating the need to check out the project manually. Project managers can now use AGT for pre-translation before handing projects over to linguists for post-editing.
Atikamekw, Babine-Witsuwit’en, Blackfoot, Dene, Dogrib, Innu, Michif, Mohawk, Plautdietsch, Stoney, Apache (Western), Hopi, Lakota
In-Country Review Tool Improvements
Delete memoQ Term Base Entry with One Click
Efficient Email Cleanup
LQA reports via API
TM Creation
Until now, the In-country Review tool had certain limitations that prevented project managers from adding ICR users in certain workflows and assignment types. To address this, we implemented several fundamental changes to ICR in memoQ 11.0.
ICR users can now be assigned both to reviewer 1 and reviewer 2 roles in an assignment, not just one or the other ICR users can now be assigned using Advanced Assignment types such as FirstAccept, GroupSourcing, distribute documents, and even auto-assign ICR configurations are no longer assignment-specific but are managed via the ICR configurations page in memoQweb/Resources. Instead specifying all settings when assigning an ICR user, project managers can now select an ICR configuration from those available on the server to speed up work.
While ICR configurations can only be managed in memoQweb, they can now be used in the desktop client to provide an end-to-end project management workflow for desktop-only customers Project managers can now assign multiple documents to the same ICR user in one go and select the desired ICR configuration for the role the user is assigned to
Project managers can change the ICR configurations (reviewer 1, reviewer 2, or both) of multiple document assignments in one go.
Due to their reusability, the new ICR configurations no longer include project-specific resources (e.g. a specific TB), but metadata (e.g. Rank 1 TB only) instead.
Old ICR configurations will continue to work in their respective assignments even in memoQ 11.0, as they are automatically migrated during the memoQ TMS update; they will be listed with unique names under ICR configurations ICR configurations appear in project templates to support automation ICR configurations appear in WS API calls to support integration with BMS systems.
TAUS provides both generic and custom models for AIQE (Artificial Intelligence-based Quality Estimate). From now on, users can access their custom models trained by TAUS in memoQ. Using custom models can increase the accuracy of AIQE.
Markdown is a lightweight markup language with plain text formatting syntax. It’s designed to be easy to write and read and it can be converted into HTML for web pages. Markdown is widely used for documentation pages as well as blogging and collaborative software.
The new Markdown filter, available as of memoQ 11.0, supports the core functionality of the Markdown file format, with more features to be added in later memoQ releases.
The Hunspell spellchecker and its built-in dictionaries required updating. Therefore, Hunspell has been updated from 1.3.2 to 1.7.2, and we automated future Hunspell updates in memoQ TMS.
Previously, in the desktop client, the status bar in the translation editor only showed project/document % values for any confirmation. For example, for a user with R1 status, a 100% TR confirmed document was displayed as 100%.
We are now addressing this issue to display role-based progress info, and not only the % value but also the actual numbers (e.g. 20/200 (10%)) by segment/word/character count, as selected by the user. In addition, memoQ now shows the total number of rows in the document as well as the number of locked rows to provide a complete list, thereby clearly communicating the user’s actual progress in the specific role while working on the document. Both document and project progress are displayed.
Users now have the option to choose Chinese or Chinese (Taiwan) language when installing the memoQ desktop app.
LQA reports (statistics & error lists) are now available through the API.
We introduced a UX improvement to clearly communicate project/document progress in both the desktop client and memoQweb. Users can immediately see progress in the specific roles without having to hover over the respective progress bars.
The fragment assembly option will be unchecked by default from now on in both memoQweb and the desktop client during pretranslation.
A new update of the TexTra MT plugin is available in memoQ.
A diverse array of Indigenous languages is spoken in Canada. We’ve added four of them into memoQ: Inuktitut, Cree, Ojibwe, and Mi’kmaq. In addition to the Latin script versions, we included the syllabic versions for the Inuktitut, Cree, and Ojibwe languages.
memoQ AGT now supports changing or clarifying the expected tone of translation. Languages differ in how formality is handled. Some have no differentiation, while others have many levels of formality. As a result, the source language might reflect your intended target language tone.
The formality setting helps you match precisely your expected formality level, and thanks to using LLM and MT technology, memoQ AGT is especially adept at following your instructions concerning the tone of the target text.
When it comes to memoQ AGT, instant domain adaptation provides unmatched quality to your machine-translated texts. memoQ AGT works with the latest domain data generated by a linguistic operation. For example, it utilizes premium quality translations verified in memoQ to provide the machine translation results.
Occasionally linguistic data (term bases, translation memories, and LiveDocs) are not in sync. One may be more up-to-date than the other, and sometimes, they may even contradict each other.
Furthermore, LLMs tend to respect the weight of data. If a term appears in both a TB hit and a TM hit, it is the TM hit that eventually affects the outcome. From now on, we are providing a way to control which source of information will take priority when memoQ AGT works with a translation. You can rank TB hits higher than TM or LiveDocs hits through TB prioritization.
Amazon now supports changing the expected tone of translation. Some languages have varying levels of formality, so, the source language might not match the exact tone you intended to use in your target language. The formality setting helps you match precisely your expected level of formality for Amazon MT translations.
In addition to improving machine translation performance during pre-translation, we have also made Chinese (Taiwan) available as a UI language in the desktop app, memoQweb, Customer Portal, and the ICR tool.
Previously, users could only rely on the browser’s built-in spell checker, if properly configured. Now, the In-country review (ICR) tool includes a ‘Check spelling and get suggestions’ toggle on the toolbar. With this option enabled by default, the ICR tool highlights spelling errors on the translation grid with a curly underline. Hovering over this underline provides correction suggestions and allows users to ‘Skip all’ occurrences of that word in the document if needed. This spellcheck feature uses the Hunspell service configured for memoQWeb in the Server Administrator.
When users utilize the filter option in the app, not only are the relevant rows filtered, but the searched-for text is now also highlighted in each row for better focus.
We’ve added a ‘Jump to row’ button on the toolbar, allowing the reviewer to directly enter the row number they want to navigate to. This eliminates the need for manual scrolling to find a specific row. Additionally, a dedicated keyboard shortcut allows you to refocus on the currently active target segment from anywhere in the app.
These enhancements are particularly beneficial for users with accessibility issues, as visually scrolling and refocusing can be more challenging regardless as to if they use a screen reader software.
We began with a user idea, namely the need for a view where users don’t have to switch between the three tabs (Terms/Comments/Issues) to access all relevant information for a specific row. As a result:
To achieve a cleaner appearance, only the comment/issue of the selected card is highlighted in the active edit box.
Adding comments to a selected piece of text is now facilitated by displaying an ‘Add comment’ tooltip above.
To enhance accessibility, tooltips and ARIA labels are added to tab header items, comment cards, and issue cards.
So far, the TM+ feature has not been the default choice for creating a new Translation Memory (TM) or executing a TM batch import. From memoQ 10.5 on, the TM+ checkbox will be pre-selected as the default option for both these use cases within the user interface. This enhancement ensures that new TMs will automatically be created as TM+, unless the user opts to uncheck the checkbox on the UI. We believe this adjustment will streamline and optimize your workflow for an improved user experience.
For those highly concerned about security and data privacy, working with MT no longer entails being exposed to travel-sensitive data on the public internet. Azure & Microsoft MT provide access to MT service via private network and now memoQ MS MT plugin can work with it. Users having access to the custom endpoints of MS MT now can configure it in the MT plugin and can work with it just as smoothly as with the general MS MT service.
From memoQ 10.5 on, users can track the actual source of MT translations coming from Intento. This allows users to analyze their actual MT use including which engine had been used through Intento.
LiveDocs features on memoQweb have been improved. From memoQ 10.5 on, you can create and delete LiveDocs on memoQweb as a project manager. In addition, you can also edit LiveDocs properties. The new functionality is available on the Resources tab in the project view, as well as under Resources
When clicking on a link in a document preview, memoQ will now open Microsoft Edge as the default browser instead of Internet Explorer.
The commands Split and Join are visible in the context menu and also in the memoQ ribbon’s Alignment tab for better visibility. This is to make sure that the context menu and the memoQ ribbon have the same items relevant to the LiveDocs Alignment screen:
memoQ AGT is an AI-based translation automation technology that unifies the benefits of machine translation and translation memories. It provides instant domain adaptation so that the translation results are tailored to the customer’s existing language resources (translation memories, terminology, term bases, aligned documents).
This is one of the most important features of AIQE. Thanks to the auto-confirm function, you can simplify and automate your translation workflow and skip unnecessary steps when using machine translation in memoQ. This is similar to how translations are handled through TMs since AIQE provides quality attributes similar to the match rate of the TM.
Implementing the AIQE into the auto-confirm functions of the pre-translate function enables fully automated translations with MT & TM translations having the quality assured.
Until now, the matches during the pre-translation of a document could come from translation memories, LiveDocs, or a selected machine translation engine.
But how to select the right MT engine for your document/project/client? From now on, AIQE can choose the best translation from different engines on the fly during pre-translation. You can run a pre-translation with multiple engines and let AIQE pick the best translation segment-by-segment.
Previously, when working with AIQE within memoQ, match rates of machine translation had only been displayed in the translation results.
With the AIQE improvements in memoQ 10.4, match rates will also be displayed on the translation grid itself. The match rate reflects the accuracy of the translation according to AIQE, and it is shown in parentheses, indicating that the match comes from a machine translation engine.
The match rate will also show up in the .XLIFF file associated with the project. This enables the user to see which MT engines the matches come from, and which one performed better in the given document. This feature is especially useful when evaluating machine translation engines.
The memoQ server backup tool’s performance has been further improved. So far, files and databases could only be backed up separately. From memoQ 10.4 on, you can run your database backup parallel to the file backup.
The project manager can now use the Quality Assurance section of the “Configure in-country review” dialog so that they can enable and configure QA check (i.e., display issues) for the ICR user in the ICR tool, and also prevent the ICR user from delivering the document if it contains errors. With this new functionality, the PM can also define QA categories in which issues are shown to the ICR user.
In addition to the Terms and Comments tabs on the sidebar of the ICR tool, the Issues tab is now visible to the in-country reviewer, displaying warnings and errors and allowing the user to focus on specific issues and correct them in the corresponding row on the translation grid.
Issues are also communicated at the end of each row of the grid, always showing the most severe issue category found in the row. So, if you have warnings and errors in a row, only the error icon is displayed
Using the filter (funnel) icon on the toolbar, the ICR user can filter the document’s rows, allowing them to filter for rows containing the search phrase:
The preview of the translation document can be displayed or hidden using the preview icon in the document header. The preview and the translation grid are in sync, so clicking in a row on the translation grid will frame the same content in the preview and vice versa.
Project managers using the desktop client now have an “In-Country Review (ICR)” context menu for ICR assignments to access the following 3 options:
Extend the {affected_documents} section with placeholders for the number and target language of the affected documents in the E-mail template “Document assigned to subvendor group” and “Project distributed with subvendor group assignments.”
The function has become significantly faster with TM+ (compared to classic translation memories).
Because of the discontinuation of the TransPDF service, it is not supported by memoQ as a PDF import option anymore.
Multilingual XML filter now supports XPath 2.0 when configuring import rules.
This feature is connected to the WPML filter. From now on, you can configure what is interpreted as a short code with a regular expression.
A new IDP is added as a supported provider for SSO. Indeed, we are open to any IDPs working with OIDC, but the template allows for quicker implementation as of memoQ 10.4.
Besides the Excel filter, you can now use in-place translation when using the Multilingual XML filter.
We have added additional filter configuration options to cascade these filters: XLIFF 1, XLIFF 2, Multilingual Delimited Text filter, Multilingual XML filter.
We are constantly improving and adding new functionality to memoQweb so that project participants can collaborate more effectively online and project managers can take advantage of a full project management workflow. As a next step, we are adding LiveDocs to the available resources for online projects. Project managers can now add or remove LiveDocs corpora that are available on the server to and from the associated projects. Look out for more functionality to come in future releases!
Based on our users’ feedback and suggestions, memoQ project managers and server administrators are now allowed to rename projects on memoQweb.
With the new Guess translation function, concordance can be used to find the translation of a word or expression that’s not included in your term bases. From memoQ 10.3 on, this feature is also available in TM+ as well as classic translation memories.
Storing user roles for TM entries or importing/converting TM entries with user roles has become possible in TM+.
When a user changes an existing TM entry, that existing entry will be overwritten, along with its user role. In the case of a TMX import or TM+ conversion, if there are multiple versions of translations for the same source segment modified by different user roles, then memoQ picks the entry that has the “most valuable” user role.
The ICR tool in memoQ 10.3 will feature the following:
From memoQ 10.3 on, you will have a distinct import option when uploading reference files into LiveDocs rather than needing to check the Import as binary option in the import filter. We have also added a Description field for all LiveDocs documents (including reference files) to make it easier for PMs to communicate the value of each corpus document to linguists without writing a lengthy explanatory email.
Moreover, reference files of any source language can be uploaded to a LiveDocs corpus in a project, thereby allowing a greater variety of reference files (e.g., a Swedish IKEA catalog can now be uploaded to an English-German project). All reference files in a project are available to all project participants, regardless of the document languages and the users’ assignments, thereby allowing for more diversity of reference files.
These improvements were designed while working on the In-country review tool, but they are also available to all users working with LiveDocs documents.
The scope of the backup has become more versatile to reduce disk space, optimize speed, and enhance performance. Users can now freely configure the backup scope by choosing which files to back up and, if your enterprise data warehouse is handling a memoQ database, decide whether the database needs to be backed up. This helps optimize performance and ensures that memoQ is fully aligned with your organization’s data management policies.
Finally, the code has been separated from the Deployment Tool. This eliminates the potential failure of the backup if the Deployment Tool is left running on the server when a scheduled backup is due.
Google’s machine learning infrastructure is changing. The custom models of Google’s machine learning platform (AutoML) have a new shape and form. The former models have become obsolete (called Legacy models), and the new models are now called Native models.
We have upgraded the plugin to enable you to work with the custom models of the renewed AutoML service. The renewed plugin now includes both Legacy and Native models.
For enhanced security, users can now use the Google Advanced MT plugin with their own PEM certificate to encrypt the translation data traveling between memoQ and Google.
Edit distance reports are used to show you how much work has been done by translators and reviewers, and how good your supporting technologies (TMs and MT) are. When generating the edit distance report, memoQ computes the amount of editing required to transform the source text into the target text. Edit distance reports are now available in WebPM.
We renewed the MT plugins’ data communication between the memoQ server and the memoQ desktop client to make it faster and more reliable.
Taking a data-driven approach to localization is crucial for businesses who want to optimize their processes and drive a higher ROI. We can get you one step closer to that exact goal via Business Analytics, memoQ’s unparalleled analytics solution for memoQ TMS customers. With Business Analytics, you can build and visualize advanced and highly customizable reports for your localization projects. Understanding how much work has been done in a project and how much work has been saved with memoQ TMS has never been so easy.
When a term base is used by multiple translators in a project, users can add new terms to the term base from the memoQ translation editor. These new terminology items, though, will need to be approved or rejected by a terminologist before they are finalized in the term base. So far, this feature had only been available in memoQ term bases. From memoQ 10.2 on, moderation is also possible in Qterm term bases. To create a moderated term base, simply check the Moderated term base check box. The functionality of moderated Qterm term bases is the same as memoQ term bases, including late disclosure. When the Late disclosure option is enabled, the newly added entries only appear to the other translators after terminologist approval. If the option is disabled, everyone can see the new terms even before moderation takes place. Keep in mind, the terminologist may later decide to reject the term, at which point it disappears from the term base and is no longer visible under the Translation results.
Thanks to the new function, moderated memoQ term bases can also be converted into Qterm term bases.
As a memoQ server administrator or project manager, you can add reverse language TMs to project templates so that they automatically are present in every project you create with the template. When configuring a template, you can select the Include reverse TMs check box, which means that reverse language TMs with the required metadata will also be included in the project.
When working with local projects, you can lock segments (meaning once a segment is locked, you cannot edit or change it further), or have memoQ automatically lock segments based on selected criteria, such as Confirmed by Reviewer 2, etc. With memoQ 10.2, locking and unlocking segments is also possible in online projects, in the desktop version, or in WS-API. This update further facilitates the transition between local and online projects.
Embedded files, such as an Excel file embedded into a PPTX or ZIP files, appear as separate documents in memoQ. In automatic workflows, embedded documents will be handled together with the main document (e.g., they will only be given review status once all embedded documents have been translated).
Light resources (such as filter configurations), which can be abundant if you work with multiple clients and projects, can now be deleted in bulk.
If a segment in another tool’s XLIFF happens to be over the limit that memoQ can handle (4 000 characters), it is no longer omitted during import, but split into smaller chunks and imported with the rest of the segments.
When working with Packages in memoQ TMS, TM+s are no longer converted into classic TMs when exporting, but they keep their TM+ status and can be reimported as such. This way, they can be handled in the same way by all project participants and show up identically in your statistics.
As a project manager, you can now add the placeholder {deadline} in the Project distributed with subvendor group assignments email template so that you can notify subvendors about the deadline.
memoQ’s font substitution settings enable the use of a different font in the translated document—from memoQ 10.2 on, font substitution can also handle changes from one script to another (e.g., from Latin characters to Japanese ones).
Some translations are not only reviewed by linguists but also by subject matter experts typically living in the specific target language market. To further facilitate the life of in-country reviewers, we introduce memoQ’s in-country review tool. With a link, provided by the project manager and/or the memoQ server, in-country reviewers can start reviewing the assigned translation in a browser, without the need for having memoQ installed on their computers or use other options such as WebTrans, which is primarily designed for linguists.
In memoQ 10.1, they can comment on any given part of the translation, see comments made by other project participants, download reference files, find words and expressions, and more. Further features and improvements are expected in the upcoming memoQ releases.
With the introduction of the new online in-country review tool, project managers can benefit from this development just as much as in-country reviewers. Project managers can set what ICRs can see and do, customize their experience by selecting reference files, term bases, and non-translatables from the resources already added to the project, and include a message with instructions, among other features.
They can overall enjoy more sophisticated user management and project setup. Further features and improvements are expected in the upcoming memoQ releases.
With AIQE, language service providers and enterprises can effectively address the risks associated with the unreliable quality of machine translation. memoQ can be integrated with a myriad of machine translation engines and to make sure that our users can exploit them more effectively, we introduce AIQE, artificial intelligence-based quality estimate, available via integrations with TAUS and ModelFront.
In memoQ 10.1, AIQE offers proper guidance on the quality of machine-translated content, enabling language service providers and enterprises to benefit more from machine translation technology while saving costs and time. Through continuous developments, AIQE will eventually be able to provide quality-secured, fully automated localization workflows, enhanced user efficiency via lowering the risks of MT usage, a quick comparison of the effectiveness of various MT engines, and less time spent on post-editing.
Translation management systems should help each and every translator thrive. Therefore, we want to make memoQ available for anyone who needs it, including visually impaired translators. With memoQ 10.1, we are rolling out Accessibility Mode in WebTrans to do just that.
When you switch the Accessibility Mode button to ON, text input fields are superimposed over the translation grid cells with their content included, thus making it possible to read and edit the segments as you go using a screen reading software such as JAWS. Inline tags and formatting tags are displayed in these text input fields as raw text; this allows screen reading software to read aloud these tags and enables the user to separate tags from text.
Currently, DeepL’s glossary function is only available for a limited language list that does not contain language subvariants. This introduced limitations for our users when working with subvariants.
In 10.1, we are introducing a tweak that helps override this problem by having memoQ only forward the major language to the DeepL terminology request. In the meantime, we keep the sublanguage for the translation request (as DeepL handles the sublanguages during the translation).
TM+ is memoQ’s new-generation translation memory engine that works better in a server environment. It offers all major TM features, and memoQ supported languages. It can handle translation memories with more than 10 million segments, and scales well with more CPU cores. Its TMX import performance is much faster than the classic TM engine’s, and it is less sensitive to anti-virus program activity. TM+ is also more stable than the classic TM, as its architecture prevents corruption by design.
Edit distance is a widely used measurement of the translator’s work, especially with machine translation post-editing becoming a more and more widely used method of translation. An edit distance report can be created on completed documents, and after its thorough evaluation, it can provide information on the expected effort for upcoming projects.
Enterprises and LSPs sometimes use Phrase as their primary TMS, so freelancers are prone to encounter with its file format more frequently. By using the new Phrase XLIFF import filter, you can easily work in memoQ on projects where Phrase is your client’s TMS of choice.
9.14.6
February 8, 2023
Improvements:
Improvement: A clearer message will inform you if you want to create a CMS project or a CC-connected project from a project template with package workflow enabled, which is not supported
Improvement: Content Connector: The list of deleted documents is only downloaded on demand to improve the performance and the experience of opening CC-connected projects
Improvement: Date filters on the Projects dashboard (such as Deadline and Created on) supports spaces in dates (such as “01. 03. 2023”) even if the strict standard defines the date format without spaces
Improvement: Machine Translation: Google Cloud Translation Advanced plugin: memoQ remembers the glossary you select and will select it by default the next time
Improvement: WPML WordPress XLIFF (XLIFF) filter: All legitimate XLIFF elements such as or are supported
Improvement: You can tell memoQ to perform concordance search always in the source language, always in the target language, or in the language belonging to the segment in which you invoked the function
Improvement: Amazon MT plugin can also connect to the ap-southeast-2 data center located in Sydney, Australia
Bugfixes:
BUG-11356: A caching issue may cause memoQ to think a remote TM does not belong to the project when you try to import an update package to an online project on a memoQ TMS connected to another memoQ TMS instance
BUG-11331: Ampersands (&) are not displayed in TM entry meta fields in the TM Editor
BUG-11420: An error in the LQA model editor dialog could make you think memoQ does not apply your changes to the LQA settings
BUG-11294: Deployment: If you upgrade to or install memoQ TMS 9.14.4, endpoints for the memoqwebnextapi and customerportalapi APIs are not set
BUG-11362: Deployment: No certificates are displayed in the parent server’s “Registered child certificates” window within Deployment Tool
BUG-10805: HTML filter: Preview may get stuck at the “Loading” phase for documents containing < iframe > elements
BUG-11259: If you delete a language from a termbase and then export it to CSV or Excel format, the deleted language may appear in the exported file, later causing import error
BUG-11235: Inserting a curly quote (’) may cause deletion of the subsequent word in the target segment
BUG-11196: Machine Translation: Microsoft MT: The engine returns Portuguese (Brazil) matches instead of Portuguese (Portugal)
BUG-11183: Machine Translation: Microsoft MT: The list of supported languages before the pre-translation is read wrongly for an issue during checking access tokens
BUG-11222: memoQ backup wizard: Backup fails for non-existing resources with misleading error message
BUG-10971: memoQ Server WS-API: You may receive an error about an invalid XML file when trying to import a Microsoft Office document containing characters treated invalid in XML files
BUG-9942: memoQ skips term consistency check between source and target if a term appears more than once in the source segment
BUG-11365: memoQ TMS: If you reverted memoQ 9.14.4 to a previous version and want to upgrade it again to 9.14.4, you may receive an error reading “There is already an object named ‘ListServerProjectTBsWithFilterName’ in the database”
BUG-11228: memoQ XLIFF (MQXLIFF, MQXLZ) filter: An error in handling empty change tracked sections in target segments may prevent memoQ to import MQXLZ documents processed in SDL Trados Studio to fail with an error reading “No change tracked nesting is allowed except deletion in insertion”
BUG-10942: memoQ XLIFF (MQXLIFF, MQXLZ) filter: If you use an MQXLZ file to update a document imported with a filter or filter chain producing a document where split and join operations are not allowed, and some segments were still joined or split by someone, some segments affected in splitting may be skipped
BUG-11380: memoQWeb: An error in constructing a path may prevent you from opening a translation document in WebTrans
BUG-11332: memoQWeb: If memoQWeb is configured to close sessions after some idle time instead of keeping them alive and the option to close idle documents to limit resource usage is turned on, users may not be able to access projects on memoQWeb after some idle time passed
BUG-11395: memoQWeb: If you confirm a segment which could be a better match for the next segment you jump to than before confirmation, memoQ doesn’t wait for the previous confirmation to complete and inserts the previously highest match that is no longer highest
BUG-11301: memoQWeb: Localization: If you switch the PM interface to Chinese or Japanese, the names of project archive files may be displayed wrongly
BUG-11328: memoQWeb: No log entry is created when a translation document cannot be loaded in WebTrans
BUG-11374: memoQWeb: The Pre-translate button becomes disabled if you select and configure an MT settings for pre-translation
BUG-11375: memoQWeb: You may not be able to configure the default TM match if you have a TM settings attached to the project with no filters of either the strict or soft type defined
BUG-11248: memoQWeb: You may not be able to open a document in WebTrans if the configured MT plugin returns an error
BUG-11268: Merging terms in a termbase may cause deletion of existing terms under special circumstances
BUG-10930: Microsoft PowerPoint (PPT, PPTX) filter: You may receive an error if you want to import sections from a PowerPoint document containing new type of comments
BUG-11114: Microsoft Word (DOC, DOCX) filter: You may be unable to export a document (and archive projects containing such documents) if you imported the document using a cascading filter configuration which includes a Regex tagger filter, and the document contains emojis
BUG-11242: Multilingual Delimited Text (CSV, XLSX) filter: You may receive a System.ArgumentOutOfRangeException error when trying to import a Microsoft Excel document if you are importing multiple documents simultaneously
BUG-11251: QTerm: In the scenario of connected memoQ TMS instances, you may receive a termbase lookup error when you use a filter received from the parent (customer’s) TMS instance
BUG-11273: QTerm: The Replace metadata feature may sometimes miss updating some metadata
BUG-10768: SDL Trados Document (SDLXLIFF) filter: SDL Trados Studio may not recognize some SDLXLIFF documents processed in memoQ for an error in managing unexpected tags in segments
BUG-11240: The Replace All button of the Advanced Find and Replace dialog is enabled even if you specify a scope not including fields (Target text and, depending on your settings, Source text) supporting replacement
BUG-11357: Trying to insert a TM match patched (improved) by memoQ using the CTRL+number hotkey may cause an error under specific circumstances
BUG-11311: WPML WordPress XLIFF (XLIFF) filter: Files containing elements in CDATA blocks can not be imported
BUG-10994: WPML WordPress XLIFF (XLIFF) filter: You can not export documents containing CDATA elements with unclosed embedded HTML tags
BUG-9675: WPML WordPress XLIFF (XLIFF) filter: You may not be able to import documents containing legitimate XLIFF elements such as or
BUG-10984: XLIFF filter: An error in the logic of source language detection for multiple files may prevent importing multiple documents in template-based projects in some circumstances if the source language cannot be determined for each file
BUG-11215: You may not be able to launch memoQ desktop client on a Terminal Server for a deployment error
9.14.4
December 7, 2022
Improvements
Improvement: Added missing error message when memoQWeb fails to load the list of projects
Improvement: The fragment assembly and “Populate number-only segments” feature recognizes numbers in superscript and subscript positions
Improvement: You can govern how you want automatic jump to work after confirming a segment
Improvement: Amazon MT plugin can also connect to the ap-southeast-2 data center located in Sydney, Australia
Bugfixes:
BUG-11071: Adobe FrameMaker (MIF2) filter: Values of marker tag attributes are not imported
BUG-10781: An “Inline tag not allowed in this context” error message may appear and it may block you from restoring an archived project if it contains XML documents with illegal whitespace characters
BUG-10785: Document history incorrectly shows the “Only unambiguous TM or corpus matches data” option was turned on when an auto-action performed pre-translation
BUG-11179: If you clear the filter in the translation grid by pressing Ctrl+Shift+F, you are taken to the first segment instead of remaining on the selected one
BUG-10724: If you filter for projects with all documents delivered, the list of projects becomes empty
BUG-3564: If you perform a Replace all operation in the TM editor and try to save the TM, it goes corrupt
BUG-10935: LiveDocs structural alignment fails for the rest of the document if a context ID does not have a match, even though there are matching IDs for every other string pairs
BUG-10788: Localization: A word got trimmed in the German version of the “Add new length information rule” dialog box accessible from the Length tab of the “Edit QA settings” dialog
BUG-11106: Localization: Error in the Chinese translation of the word Final menu label in the Track Changes drop-down menu of the Tracking tab group
BUG-10846: Localization: The German translation of the “Find different numbers, too” checkbox of the Concordance window is incorrect
BUG-11183: Machine Translation: Microsoft MT: The list of supported languages before the pre-translation is read wrongly for an issue during checking access tokens
BUG-11162: Machine Translation: Systran MT: Not all supported languages may be listed for a profile
BUG-10641: Machine Translation: Tilde MT: You may receive an error when you try to configure the Tilde MT plugin in online MT settings resource
BUG-11223: memoQ backup wizard: You can’t perform backup until you open the Smart Quotes dialog once
BUG-11109: memoQ may hang up for a longer time if you try to edit an online document filter configuration with reference files specified, and the reference files do not exist anymore
BUG-11117: memoQWeb: Penalties defined in the attached TM settings are applied when the filter conditions are not met (instead of being applied when met)
BUG-11178: Microsoft PowerPoint (PPT, PPTX) filter: If a document has been imported with a pre-9.12 memoQ and you attempt to export it in memoQ 9.12 or later, a compatibility issue due to an improvement in handling alternative texts of images may prevent you from exporting the document
BUG-10890: Microsoft PowerPoint (PPT, PPTX) filter: If a document has been imported with a pre-9.12 memoQ and you attempt to export it in memoQ 9.12 or later, a compatibility issue due to an improvement in handling alternative texts of images may prevent you from exporting the document with an exception of MemoQ.DocConverters.OpenXML.SchemataCreator.InputNotValidException
BUG-11114: Microsoft Word (DOC, DOCX) filter: You may be unable to export a document (and archive projects containing such documents) if you imported the document using a cascading filter configuration which includes a Regex tagger filter, and the document contains emojis
BUG-11197: Microsoft Word (DOC, DOCX) filter: You may be unable to export a document for claimed tag pairing error under rare circumstances if the document contains hidden text
BUG-11091: Multilingual Delimited Text (CSV, XLSX) filter: You may get an “Index was out of range. Must be non-negative and less than the size of the collection.” error if you try to import Microsoft Office Excel files with unexpected newline characters present in an XML file within the XLSX package
BUG-11103: Star Transit Project (PPF, PXF) filter: You may fail to export packages containing documents with unsupported custom language codes
BUG-10076: Star Transit Project (PPF, PXF) filter: You may not be able to import documents from Transit projects with Thai as the target language
BUG-10983: The “Users can request password reset” checkbox of the “Configuration and logging” tab of the “Server administrator” console gets ticked off after you close and re-open the dialog
BUG-5132: The Files page of the Online PM window the Archived project page of the main Dashboard do not convert the UTC creation dates to the local timezone of the current memoQ desktop client
BUG-10297: The Sign in button of the SSO OIDC login page has duplicated text
BUG-10915: Wrong characters may be highlighted among the results of a Japanese Concordance search because of an error in recalculating highlight positions for segments with tags
BUG-10821: You may receive a false QA error claiming for the absence of non-translatable words if they are written using a different alphabet and are not surrounded by spaces
BUG-11207: You may receive an error if you try to perform QA on a view for an error in how memoQ tries to identify the assignment role of the current user for a segment in an effort to determine the enabled state of the change tracking feature
Initial 9.14.4 release was 9.14.6
9.9.10.
November 9, 2021
Bugfixes:
BUG-9725: A superfluous scrollbar may appear in the Sort dropdown above the translation grid, even though all items are visible
BUG-9820: Hunspell dictionaries for Norwegian do not appear in Server Administrator
BUG-9684: If a user is not member of the Project Managers group, but is set as project manager in a specific project, the user is not able to assign documents within that project to project members
BUG-9378: If you are trying to find something in a document by invoking the Find and replace window, memoQ may run out of memory under rare circumstances
BUG-9774: If you export a termbase from memoQ with Spanish (Latin America) in MultiTerm format, SDL MultiTerm may not see terms in this language
BUG-9806: If you try to enter a non-breaking space into the filter bar on top of the translation grid, it gets inserted in the target segment
BUG-9720: Improvement: Some database queries on project and document data for alert generation have been optimized to avoid timeouts
BUG-9776: Localization: There’s a typo in the Japanese translation of the “Merge Selection” button’s tooltip
BUG-9811: Machine Translation: Kantan MT: The plugin may not work in the English to Chinese (Singapore) language pair
BUG-4433: memoQ Server does not recognize Hunspell dictionaries for Norwegian
BUG-9754: Microsoft PowerPoint (PPT, PPTX) filter: Some characters may change to Wingdings in preview and in the exported documents
BUG-9470: Microsoft PowerPoint (PPT, PPTX) filter: Some characters may change to Wingdings in preview and in the exported documents for PPTM files
BUG-9767: Multilingual Delimited Text (CSV, XLSX) filter: If you import an Excel document using a cascading filter composed of a Multilingual Delimited Text filter and a Regex tagger filter, the exported document may lose some of the inline (in-cell) formattings
BUG-2470: PDF Preview tool: An error in an external component may cause specific PDF files to fail to be opened
BUG-9734: QTerm: Clicking on the Related entries link takes you to the login page
BUG-9809: QTerm: You may receive an error when you try to add a term to a termbase with custom date fields
BUG-9716: Restoring a project archive may fail for an error importing a bilingual document from the archived project
BUG-9775: Some fields of the Activation wizard may not be visible on specific screens or with specific display settings
BUG-9731: Some keyboard shortcuts, like CTRL+C and CTRL+E do not work in the Concordance window
BUG-9737: The Add term command’s shortcut, CTRL+E does not work in the Concordance window
BUG-9804: The copy command’s shortcut, CTRL+C does not work in the Concordance window
BUG-9467: XLIFF2 filter: Document export may fail if some tu elements have different number of source and target rows
BUG-9755: You may not be able to restore a project archive for an error in handling dates
BUG-9410: You may not be able to restore a project archive for an error in handling special date values
BUG-9846: You may receive an out of memory export when you try to export a document and font substitution was applied previously
9.9.9
October 5, 2021
REST API Security improvement:
The admin user has no longer access to the Resources API in order to strenghten security. For integrations to keep working, please switch to a user that is member of the Resource lookup via API/plugins group on the target memoQ Server.
Improvements:
Improvement: memoQWeb: Track changes are also displayed on tags, and support is added for nested changes within tags
Improvement: The Toggle case button of the Add/Change/Delete term dialog is moved to the far right
Improvement: The tooltip to warn you to make sure your tracked changes reflect those in the source side will only be shown once per document when you turn track changes on
Bugfixes:
BUG-9445: Adobe InDesign (IDML, INDD) filter: You may be unable to import certain documents for an error related to compressing empty folders within the IDML package
BUG-9520: Adobe Photoshop (PSD) filter: You may be unable to import documents containing certain special characters for an unescaping and decoding issue
BUG-5084: Changing shortcut for the Add new term command doesn’t have any effect in the Concordance window
BUG-9557: Deployment Tool: There’s a typo in a message box
BUG-9673: Duplicate hotkey in the Advanced find and replace dialog
BUG-3579: If you add a note containing a URL to a term’s definition, and if you select the term on the Translation results pane, and if the URL contains a URI element starting with a capital letter (e.g. /Foo), then the link ends at the slash
BUG-9601: Machine Translation: Google Cloud Translation Advanced plugin: You may receive a warning about an unsupported language when adding a valid language
BUG-9624: Machine Translation: MT SDK: Fixed HTML entity conversions
BUG-9610: Machine Translation: Tilde MT: You may receive a false warning about a network error or an improper source string if the MT produces a translation with extra space within a tag
BUG-9594: memoQWeb: Ctrl+NUMBER keyboard shortcuts for inserting translation results have no effect in specific workflow statuses
BUG-5074: memoQWeb: If you copy or select text from a segment with tracked changes to perform some operation like paste or concordance search, deleted text is also copied or selected
BUG-9513: memoQWeb: If you import a document with WPML WordPress XLIFF (XLIFF) filter, you may receive an img/alt tag error whereas memoQ desktop shows no error
BUG-9628: memoQWeb: If you open a document from the new UI, you may be unable to change the unit to measure your progress
BUG-9621: memoQWeb: If you perform a find and replace operation with track changes on, replacements are not marked as changes
BUG-9418: memoQWeb: You cannot select the “External files” radio button when delivering documents to Customer Portal
BUG-2897: Microsoft Excel (XLS, XLSX) + Multilingual Delimited Text (CSV, XLSX) filters: Unicode characters stored as text in an Excel file (cell) are not escaped and unescaped correctly
BUG-9531: Microsoft Visio (VSD, VSDX) filter: You may fail to import documents under rare circumstances involving formatted lists
BUG-9550: Multilingual Delimited Text (CSV, XLSX) filter: Adjacent
tags are merged into one
BUG-4826: Multilingual Delimited Text (CSV, XLSX) filter: Adjacent line breaks appear as one in the Preview pane
BUG-9480: Multilingual Delimited Text (CSV, XLSX) filter: You may have issues exporting documents containing formulas
BUG-9486: QTerm: You may be unable to save conditions for multi-value pick list fields
BUG-9638: SDL Trados Document (SDLXLIFF) filter: You may not be able to import a document into SDL Trados Studio if it contains cascaded locked translation units
BUG-9504: The progress indicator of a project displays incorrect (lower) values if all of the segments in a document within that project are locked
BUG-5056: The status bar may become empty if you open a memoQ document by clicking a hyperlink that is intended to check out a project and open a specific document
BUG-9455: TM hits for segments consisting of a # character and a number show up as 100% matches instead of 101% matches as they used to
BUG-4458: Translators may be able to change QTerm filters in their local copies of online projects
BUG-9499: XLIFF 2 (XLIFF) filter: Some segments may not be exported under rare conditions
BUG-9457: XLIFF filter: memoQ does not save your settings specified in the Tags section of the General tab of the Document import settings dialog
BUG-9553: XLIFF filter: You cannot import documents containing sub elements
BUG-9611: You cannot change whether to use TM-driven segmentation and machine translation or not when pre-translating a view, and you are stick to the settings you used the last time you performed pre-translation on a document
BUG-9454: You may be unable to change filter and configuration settings at document import with certain regional settings applied in Windows
BUG-9379: You may be unable to export documents with unaccepted or unrejected tracked changes present in tag values
BUG-5135: You may not be able to delete a subvendor user on a memoQ server for an error in removing them from projects
BUG-9479: You may receive a timeout error if you try to launch a project with a large number of documents and role assignments
BUG-9651: You may receive an error if you try to launch a project with a large number of documents and role assignments
BUG-9627: You may receive an error if you try to perform the Clear translations command in a document with a regex text filter applied
Initial 9.9.9 release was 9.9.10.