# CAT-Tools/MemoQ/Wishlist
## Actual wishes

For any problem and workaround see also the page CAT-Tools/MemoQ/Tips and Tricks. Please choose the appropriate section to add a wish.

### General workflow

* It would also be good if tags could be deleted at the translator's discretion. As the software now stands, the translator is not given full credit as an intelligent participant. If it really is not possible to delete unwanted tags, it would be nice if they were hidden in the source text as soon as Alt + F8 is pressed. Then the translator can focus on what matters and not be bothered by what doesn't. (Rod Walters)
* Server Administrator, Server projects: Would it be possible to add a status feature here? E.g. in the form of colours that can be given to projects by right-clicking them in the overview pane (for example like the categorize feature in Microsoft Outlook). This would help in the workflow. You could give a project which has been translated but is pending feedback and possible changes from the client the colour red, and then change it to green once the project was completely finanlised. Green would then indicate that project was ready for updating/sending segments to a final/proofread TM. I suspect the possibility to categorize projects according to five different colours would be sufficient. No need to define categories/statuses for each colour; in that way people can use the colours to fit their specific workflow. (ditbal)
* Reset format: a command (and shortcut) to reset a format of segments (bold/italic/underlined)

### Propagation

* Confirm without propagation: a command (and shortcut) to confirm a segment without propagation (if propagation is enabled)
* The settings for auto-propagation should be specific to a project (instead of applying generally, as it is now) // tsca 14:00, 18 July 2008 (UTC)
* Conditional propagation: prompt user if subsequent segment is translated differently, empty, confirmed (like Trados Studio)
* Propagation for comments: an option to propagate comments for repetitions so that a comment would be visible in all identical segments which were propagated

### Statistics

* Include name of analyzed file in Overview/Reports after performing statistics on single file from Translations
* Show statistics history in Statistics window - an option to view previous statistics reports in Statistics window
* Weighted word count - done in current version of memoQ
* Automatic copy of statistics in project folder or at least a reminder/confirmation before closing the statistics' windows (T. Rox)
* [Automatic] saving intermediate reports - an option to measure hourly productivity by comparing different reports
* Analysis percentages with decimal places - rounding everything down makes the percentages useless for character/word counts
* Productivity measurement - a tool to measure how many words are translated/proofread per hour.
* Translating time - similar to editing time (for each user role)
* Options for setting up Editing time - inactive mouse, overlaid screen etc.
* Customize columns in Statistics report - ability to rearrange and exclude columns (and add calculated columns)
* Word count calculation in background - linguist has to wait for a long time while memoQ is counting statistics

### Project management

* Create project template from existing project or several projects (combining resources from them)
* Assign role of translator/reviewer to the whole folder in the structure view
* Remember which folders were collapsed in structure view when re-opening project
* Assign the whole folder in structure view
* Structure view by different attributes: show Structure view not only for folders by also for dates, file formats, translators etc.
* Different profiles for translation and proofreading: an option to switch between proofreading and translating profile
* Automatically open the last project: an option to open automatically the last project
* Grouping and labeling documents in Project Home: an option to label and group document (creating folder structure) for batch tasks and filtering
* Prioritizing of documents: an option to mark different priorities for processing
* A quick way to open original: an option to open original document quickly; the translator often needs to look at the original to see the actual format in the native application since html preview is not perfect for certain files. Now the easiest way, if you are not sure about file path, is to go to "Translations," select document, click "details" panel, copy the import path, go to file explorer, and paste it; which is not very practical.
* Hide/unhide TM/TB/project: an option to hide TM/TB/project having possibility to restore its visibility in resources
* Profiles for creating projects: In general there are too many clicks necessary for creating a new server project. In a profile you could determine the source language, target languages, translator(s), project manager(s), etc. In a "normal" company the source language never changes, so why it has to be selected with every new project. There should also be a checkbox in order to use the file name as the project name, or it would be even better if the project name were defined through variables (project manager initials, date, running number, etc.). (Carsten) - memoQ 2014 has templates for projects
* Password protection for the memoQ application: There should be a native way to password-protect memoQ with options such as simple password protection against children or novice users, and even advanced encryption of confidential projects.

### Navigation

* Bookmarks in order to quickly mark entries (e.g. in order to return quickly to the last edited segment after scrolling up and down in the text) (TilovdB)
* Insert "Rich" Bookmarks in Translation file when several people do several tasks on the same document and on the same PC, allowing later review/proofreading of specific parts. Each BookMark could include information like : Who, did What (translation, proofreading, etc...), on Which part (X segments from A to B, representing Y source words), When, for How Long . This information could also be used later for project accounting purposes (on a larger project, who contributed in how many % to reach the goal) (MartinB)
* Being able to click on hyperlinks to webpages and be sent to the page directly instead of having to highlight the link and copy it into the browser (Anette)
* Go to original segment from translation results: an option to go to the original segment within the same project from translation results (e. g. a translator notices some errors in translation results and need to go to the original segment to correct it). Such feature exists in SDL Passolo.
* Clickable repetition icon: clicking on the repetition icon in the document view allows to filter other repetitions of this segment in the document/project (e.g. show them in view pane).
* Jump to view: an option that is opposite to "jump to" option in view (to go from document to view)
* Easily maximize memoQ from taskbar memoQ is often stuck in the taskbar and refuses to be maximized; even alt+tab is useless. Sometimes the only option is to use Task Manager's "Bring to front." (Noticed in several Windows versions, such as Vista, 7, and 10)

### Communication/Comments

* Communication add-in
** Email notification when somebody posts a message in the forum. Subscribe option for new messages. New posts will be sent to the user's email address which is stored in the user profile on the MemoQ server.
** Possibility to delete messages (Carsten)
* Comments function: possibility to export all comments made to a document (or project) to a file that can be edited and e.g., submitted to the client as queries. (ditbal)
* Notepad to add notes for each project (in most cases to collect and forward them to the client) (T.Rox)
* Status for comment: an option to set a status for comment (accepted, rejected, replied and user-defined lists with different statuses). An option for filter comments by its status
* Tree-like structure for comments
* Show comments in QA results
* A flag for files with comments - a mark for files with comments to see in the file list which files have comments inside (without opening them)
* Extra column for comments - a "comment view" - an option to see comments in a separate column
* Navigation panel in Active comments tab - an option to go to the next/previous commented segments
* Filter comments in Active comments tab - an option to filter comments by different attributes (user, date, category etc).
* Change font size in Active comments tab
* Filter comments by its category (error, warning, information, other)
* Comments for the whole folder in structure view
* Show number of comments in the status bar
* Add comments to multiple segments at once

### Quality assurance
#### General QA

* Different number of sentences in source and target": could help in detecting of partially translated segments
* Several tabs "Resolve errors and warnings": currently each new QA closes the previous tab
* Check for unchanged fuzzy matches
* Log for all QA checks and spellchecks: logging of date&time for all checks (to see that the file was checked after the last change)
* Skipping segments which are identical to source in QA: an option to skip segments which are identical to source during QA (except notice "identical to source")
* Differences between translated segment and TM entry: an option to see a differences between translated segment and TM entry. It is very useful when proofreading in memoQ translations which were made externally in other CAT. Some segments in TM could have "approved status" and they should not be changed in translation. This feature would help to track such "illegal" changes
* Check web-addresses: an option to check web-addresses (and recognize them as non-translatable)
* Check ™, ®, ©, *, >, <, ≥, ±, +: an option to check whether both source and target have these characters
* Check acronyms: an option to check acronyms (and recognize them as non-translatable)
* Save sort order in QA results: memoQ always resets a sort order by table column in QA results when you change anything.
* Identification of duplicated punctuation marks: double colon, double semicolon etc.
* Check words before sign ® and TM: ensure that trademarks are not translated
* Recognize chemical formulas
* Detection of imperial measures: imperial measures are usually converted into metrical system so imperial measures in translation should generate a warning.

#### Reduction of false errors in QA

* Source and target ends with different punctuation - exclude quotes and brackets from this check as it is always a false error

#### Spellchecking

* Group identical spelling errors in QA report: an option to process all identical spelling errors together (skip etc).
* Spellcheck in background: spellcheck takes quite a lot of time but confirmed segments could spellchecked in background to create an instant report.
* Spellcheck all CAPS: an option to check spelling of words which are in all caps (frequency of spelling errors in all CAPS words is rather high).
* Skip the whole segment: an option to skip not only one word but the whole segment during spellchecking. E. g. "Skip segment" button in spellchecker window.
* Skip identical to source segments: an option not to check spelling in segments which are identical to source. Such segments are usually left in a source language and do not need to be checked.
* QA report for spellcheck: right-click menu with options similar to spellchecker window in QA results table
* Improve speed of spell checker (TilovdB)
* Spellcheck TM: even if spellcheck is enabled for QA, memoQ now does not check spelling in TM
* Instant creation of spellcheck report: if spellcheck is done in background, spellcheck QA report could be created immediately
* Consider glossary terms as spellchecked: an option to skip TB entries during spellcheck considering them correct
* Automatically add TB entries to spellchecker dictionary:

#### AutoCorrect

* Make end of target segment punctuation equal to source: replace end punctuation mark in the target with the one from source segment
* Autocapitalization for segments starting with tag: autocapitalization currently does not work if a segment starts with tag
* Do not reapply autocapitalization if user undoes autocapitalization by Ctrl+Z
* Smart rules for autocapitalization: do not apply after colon, semicolon or some other punctuation marks
* Autocorrection of multiple spaces
* Autodeletion of spaces at the end of the segment
* Autocorrection of space to non-breaking space in special cases (between number and unit etc)

### Filter/Sort/View
#### View

* Renaming of views: an option to rename views rather then create them a new - this feature will be in the next version of memoQ
* Defining the order of documents when gluing them together: an option to select an order of documents in a view composed of several documents (drag-n-drop would be fine).
* Creating view from selected segments: an option to create view from segments selected in work area via right-click menu
* Refresh view status: an option to refresh status of views (it is currently possible to refresh files only)
* Create view from view: an option to create a view from other views rather than documents
* Creating view from filtered segments: an option to create view from segments filtered in work area via right-click menu (or button on filter panel)
* Creating view by dragging file onto tab "Views"

#### Filter/Sort

* Filter segments with Patch Match (fuzzy match repair): they should be checked more careful
* Filter segments "containing numbers": show segments which include at least 1 number to check numbers throughout the text - this can be done by enabling regex and filtering for \d
* Filter "number only" segments and "excluding number only" segments: it is more comfortable to translate without number only segments
* Reapply the last filter: an option to reapply the last filter
* Templates and history for filters: an option to save templates and history for filters to use them by single click
* Filtering segments by formatting: an option to filter segments by present of formatting (contain bold/italics)
* Filtering segments by script: an option to filter segments by script (Latin, Arabic, etc.)
* Filtering segments where target is identical to source: an option to filter segments where target is identical to source (it would be a good complement for QA which could find such segments)
* Filtering documents by its status in Project Home: an option to filter documents by different status and properties (extension, degree of completeness, translated, proofed, size, name)
* Inverting filter: an option to invert filter (to see hidden by filter segments and hide visible segments)
* Filter all respective repetitions in the project (or file) by clicking on the repetition icon of segment
* Filter/sort segments in view by file name: memoQ 2013 now shows file names in views; it would be useful to filter/sort segments in view by file name
* Ask to restore filter when reopening file: an option to restore filter if file was closed when filter was used

### Resources
#### Translation memory/Corpora

* Block annoying matches from Muses: an option to block some undesirable matches from Muses (when memoQ offers the same wrong matches for predictive typing, I have to reject them again and again. What is about blocking some of them?)
* Forbidden segments: an option to mark segments in TM as forbidden (similar to forbidden terms). It allows to leave such segments in TM for tracking purposes but excludes them from pretranslation.
* Select TMs for pretranslation: an option to select TM for pretranslation in Pretranslate window (now I have to change TMs for the whole project)
* Number and punctuation differences should be distinguished in pretranslation: This can be very useful if the translator is pressed for time, and the document has many matches with minor punctuation differences, such as extra spaces. Unfortunately, the "good match" option in Pretranslate makes no distinction between number and punctuation differences, which is crucial; while the translator should reasonably be able to automatically confirm 99% matches with only minor punctuation differences, 99% matches with number differences must be revised one by one to check whether memoQ has replaced numbers correctly. A simple checkbox such as "Ignore minor punctuation differences" next to the "exact match" radio button in Pretranslate dialog should solve this problem.
* More options for TM-driven segmentation: such as an option to join a fourth and even a fifth segment (which can help in malformed documents with too many misplaced line breaks), and an option to perform only joining or only splitting for more control over segmentation
* Subsegment confirming mode: when importing an Excel sheet on a cell-by-cell basis using the option "import linebreaks as inline tags," and we have the memoQ segment "Paragraph1 <br> Paragraph2," it is useful to be able to confirm three translation units at once with the confirm shortcut depending on the <br> tag location: (1) the whole memoQ segment, (2) Pargraph1 subsegment, and (3) Paragraph2 subsegment. These should result in more future matches, and better fragment assembly.
* Fixing the never stopping loading circle in corner of results pane noticed in memoQ 2015 7.8.52; it is very annoying for someone used to seeing it stop/disappear at scan completion in earlier versions.
* Save segments with tracked changes in TM: show tracked changes in TM results to facilitate consistent editing
* Show differences between translation in TM and document in compare control: to facilitate consistent editing of similar segments
* Ranking of TMs like TBs: an option to rank TMs like TBs in memoQ 2013 R2
* Penalizing all TMs except primary one: an option to add penalties to all TMs except primary one (it is easier than add penalties for each TM separately)
* Transferring context information between TM: moving context data between TM to get 101% matches.
* Colour-coding to distinguish between exact and fuzzy matches in the Translation Results window and in the translation grid after e.g. pretranslation. (Grzegorz Harbaszewski)
* Merging 2 or more TMs: an option to merge 2 or more TMs with one command taking into account meta-data (without import/export by mean of tmx)
* Locked segments in TM: an option to protect some segments from editing in TM.
* Show penalties in meta-information area: an option to show TM's penalties in meta-information area.
* Plug-in for using Trados TMs directly: an option to connect to Trados TMs.
* Select several TMX for import - it is not possible to select more than 1 TMX-file to import into TM
* Highlight segment attributes in Meta-information box - highlight segment attributes that match the current project (it will help promptly recognize TM segments created in the current project or which are very similar to current project). Ideally it should be customizable to highlight segments made within particular time/date range etc.
* TM maintenance - automatically delete number-only segments from TM
* Show which TBs and TMs are associated to projects: When moving or deleting a TB or TM it would be convenient to know in which projects the TB or TM is used. (Carsten)
* Elimination of duplicates (same target, same source) from termbases and translation memory (David Turner) - current memoQ version can identify duplicates but can not clean them automatically
* Marking matches that require only deletion of contiguous text: Sometimes a match ranked down the list is actually better than matches ranked higher because it has contiguous "blue" text and is more accurate; such matches (with contiguous "blue" text) should be marked clearly, e.g. with a "+" next to the match rate, when they are not the first on the list.
* Revert patch matches: button/short cut/right click menu to revert patch matches and get "normal" TM matches

#### Muses/Predictive Typing/Autopick

* Block some words from Muses in Predictive typing: some incorrect variants are rather annoying when you have to delete them again and again.
* Turn off Predictive typing when typing in the middle of word: if you need to correct a spelling error in the middle of word, predictive typing tries to insert the whole word. Such behavior is confusing.
* Time delay for predictive typing: an option to set up a delay for displaying prompts
* Exclude from predictive typing words which are already typed in the segment
* Use content of active document/project for predictive typing: it is strange that memoQ does not offer words from segments translated above.
* Turn off predictive typing when the word is mostly typed: predictive typing is not required for short words or when 1-3 letters are left
* Predictive typing for numbers + units: it is logical to offer not only number but number + % sign (or localized units - mg, m, kg etc)
* Turn off case-sensitive predictive typing: predictive typing currently does not work if you start typing word with capital letter which is entered into the glossary uncapitalized - case sensitivity option for predictive typing has been added in a recent update
* Predictive typing for Machine Translation suggestions: it would be great if Predictive Typing could suggest full sentences, phrases, and words from various MT resources. Of course, the user could switch on/off the function.
* Train Muse in background: this task could be done in background
* Predictive typing for proper names: an incredibly useful feature, which would prevent translators from making spelling mistakes in proper names. Of course it wouldn't be faultless, but could be triggered by words starting with capital letters in a sentence.
* Predictive typing/autopick for number ranges, formulas etc: it is more handy to insert ranges (or other group of numbers) rather than individual numbers
* Show resources used to create Muses in their properties

#### Term base

* A possibility to add extra columns
** Define the order of the columns (e.g. Subject > column 3, Domain > column 1, Note > column 2, etc.)
** Save the export setting so the user doesn't have to select, deselect, order, select TXT or CVS, or whatever setting the next time she exports.
* Easy access to the term base for terminologists. In our case, terminologists are marketing people and developers. Neither of them is interested in foreign languages, translation memories, alignment functions, translation projects, etc. They just want to
** enter and/or release terms in the source language
** look up and/or export terms of any language.
* Web based access to the terms (read-only would be sufficient for our needs). At the moment we use the Typo3 extension sg_dictionary which is enough. See http://www.rohloff.de/de/info/woerterbuch/english/index.html for an implementation at Rohloff (sorry, our dictionary access is password protected). (Carsten)
* Ignore accents (e.g. recognize "categorie" for TB entry "catégorie" and "habitaciones" for "habitación" (Torsten)
* A thing DéjàVu never offered, as an alternative for fuzzy term recognition: morphological reduction/recognition (language specific). First language to start with, (of course ;-)): German - So: Dictionary has 'Baum', in the text 'Baumes' (Genitiv), Baumes is recognized as Baum+es. (Transit offers this.) (Hans List)
* MemoQ now stores it's dictionaries in a text file (we've discussed this), should be moved to a MySQL or MS Jet. DéjàVu users speak of big mama when they talk about terminology databases of 100 000 entries or more. They all use large databases that should work fast. (Hans List)
* Context sensitive terminology recognition. Some kind of 3 dimensional terminology database. Example: If computer and Apple are in one segment, do not translate Apple (or: translate it with Apple). If Apple and Tree are in one segment, translate it with 'green fruit growing on a tree'. I know subject codes can help, but my suggestion is nicer. (Hans List)
* Selecting TB entries to be exported. Instead of exporting the complete TB content, there could be a functionality to specify selected entries to be exported, for instance, all entries where the subject is "Finances" or "Project management". Such a functionality could also be helpful to quickly create a glossary intended for clients. A termbase is mainly intended to assist translators, but all terms would not be useful in a glossary. If I can mark some entries as "Glossary" and extract these specific entries, the creation and update process of client glossaries would be greatly enhanced. (Ariane)
* Ability to add new fields, as for instance "Source" (F. Vidal)
* Possibility of viewing and changing all termbases during translation. Right-click on term in results pane and change destination of term. Edit term in termbase and see a list of all termbases to choose from. (Anette)
* It would also be very useful to be able to filter on things such as "case sensitivity" and "prefix matching" and "domain" ... so that we can fix things like double entries in our term bases, and edit/maintain them... That is, filtering on columns in the actual window that opens when we click on "edit" a term base, like in a spreadsheet, rather than having to use the confusing: Term Base -> Filter -> Filter and sorting interface, which I find rather unintuitive. (wordbook.nl)
* Preferred terms: an option to mark a term as preferred. It could have a special icon in translation results. A preferred term could hide all other variants.
* Join 2 terms entries via right click menu in translation results: currently it is not possible.
* Being able to move a term from one termbase to another termbase in one click (Anette)
* Add terms to TB from concordance window
* Open TB for editing with double click - it does not work
* arabterm.org plugin - English, French, German, Arabic
* Show all variants of terms from TB when mouse is over highlighted term: currently only 1 variant is shown.
* Ignore a list of stop words: They could be present in a term base converted from a full dictionary that has such words that the user cannot easily locate and delete. This could be an extension of the similar function used when extracting terms.
* Indicating the source of term translation in the translation grid. The translator should be able to set an abbreviation for each termbase, which can be displayed next to the term translation in the tooltip. This way the translator will not have to waste time by clicking in the translation result pane to view the source of the term translation.
* Distinct colors for different TMs. Suppose that there are two TMs available in a given translation project. While TM1 is only advisory, the terminology of TM2 has to be observed. In the source part of the translation grid, (sequences of) words belonging to TM2 are highlighted in red, (sequences of) words belonging to TM1 are highlighted in blue. This would ensure that translators do not overlook any important, fixed translation. Additionally translators would save time (cf. previous wish "no time wasted with looking for the source of the term translation"). (MIPS-CAT)
* Exclude some terms from predictive typing - check-box "Exclude from predictive typing" on tab "Usage" of term editing window (some terms are for reference only and should not be inserted into translation)

#### Web search

* Option to use mobile user agent: an option to use a mobile user agent, similar to the function of the "User Agent Switcher" add-on for Firefox; this enables loading light versions of many websites, i.e. faster and more efficient web search.
* Option to load only one xpath: an option to easily define one xpath for loading, which removes distracting elements from webpages, and makes web search more stable. Defining the xpath should be easy, as in popular web scraping software.
* Adding arabterm.org technical dictionary: English, French, German, Arabic
* Adding Librairie du Liban Publishers dictionaries: several premium dictionaries are offered for free, involving the languages Arabic, English, French, German, and Spanish. The pairs with most results are English <-> Arabic, and French <-> Arabic. The URL is http://www.ldlp-dictionary.com.

#### Machine translation

* Ability to set up MT correction rules: an option to set up simple and complex rules for the correction of MT results. This feature can be very useful when the source is repetitive, which may lead to repetitions of the same error in the MT results. e.g., a simple rule such as "always replace bishop with ceilings" can greatly improve the English MT result of an Arabic construction document since the Arabic word "أسقف" can mean either "ceilings" or "bishop." For complex rules, regex could be used.

### GUI
#### Full support of high resolution displays (4K, 2160p, 3840 x 2160)

* Fix of current bugs with UI: Find & Replace, edit of comments, reports etc. A lot of UI elements are not usable now.
* UI is extremely slow on 4K displays: working with memoQ on 4K display is not comfortable

#### Translation memories panel

* Customization of columns shown for TM properties : configure the number of shown columns for TM properties (project, client, domain etc). Now they are shown below for selected TM only.

#### Meta-data area

* Hide/show meta information: to configure which meta-data are to be shown (moving of separation bar is not flexible enough)