CAT-Tools/MemoQ/Wishlist

From Wikibooks, the open-content textbooks collection

Jump to: navigation, search

Contents

[edit] Actual wishes

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

[edit] General workflow

  • Editing the source: Since there are often mistakes in source texts, it would be convenient to be able to correct the source on the fly. Otherwise, wrong source text is enshrined in the memory. 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)
  • 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)
  • Copying projects: In most cases a new project is similar to an existing project: project manager, translator, source language, target language, client, etc. So copying a project makes sense. (Carsten)
  • 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)
  • Project dashboard to have an overview of running projects (T.Rox)
  • Notepad to add notes for each project (in most cases to collect and forward them to the client) (T.Rox)
  • 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 segements 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)
  • Jump to segment #xxx - a way to quickly jump to a specific segment; eg: ESC 666 Enter or Ctrl+Sth - open a dialog when one enters the segment number - entering the number - Enter will move to cursor to the target cell of segment 666. (tsca [re] 13:11, 19 January 2008 (UTC))
  • The settings for auto-propagation should be specific to a project (instead of applying generally, as it is now) // tsca [re] 14:00, 18 July 2008 (UTC)
  • Get a warning when the text in the current target cell is different from a 100 match (F. Vidal)
  • Comments function: could work more like the comments funciton in Word ie, possibility to highlight part of the segment (single word or phrase), click ctrl+M and the highlighted part will be inserted in the comment field or marked in the segement, thus identifying what part of the segment the comment refers to. (ditbal)
  • Comments function: possiblity to export all comments made to a document (or project) to a file that can be edited and eg, submitted to the client as queries. (ditbal)
  • 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 possiblity 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)
  • 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)

[edit] Term base

  • Remember selected languages when directly editing a term base
    Source language should always be selected. The second language should be remember from the last editing session. (Carsten)
  • Term base: terms show up even if they don't have a translation
    Scenario: The project manager defines new terms and releases them. During translation the terms show up as not yet translated. (Carsten)
  • Communication add-in for the translation manager
    As a translation manager it would be nice to have a communication window always open and always on top. Or put it into the task bar.
    If there several projects with documents into several languages, I would like to get an instant notification of a new chat entry or a forum thread. So can answer immediately. (Carsten)
  • Hide languages
    New projects: For us as a company, the source language never changes. The target languages are fixed. Only once in a while we will add a new target language. It would be nice if one could
    1. prefill the fields when creating a new project (e.g. saved settings from last project, so the French translator is already selected when creating a French project)
    2. Hide target languages you don't need; e.g., deselect languages in a global settings dialog so they don't show up when creating a new project, term base, etc. (See Workarounds section)
    These I consider nice to have features. (Carsten)
  • term base improvements
    1. A possibility to add extra columns
    2. A possibility to add pictures and to link pictures (pictures may exist in a media asset management system or on the web site of a company)
    3. An alignment function for importing word lists or adding a language
    4. Export functions
    a) Define the order of the columns (e.g. Subject > column 3, Domain > column 1, Note > column 2, etc.)
    b) 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.
    5. 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.
    6. 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)
    7. 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)
  • Related to this: an option 'Case sensitive term recognition'. Some won't use it, but for languages like German it is very useful (the Verb 'schrauben' is translated different from the noun 'Schrauben' (plural)). (Transit offers this, but it's implementation has severe bugs.) (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)
  • 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)
  • 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)
  • Saving the TB content to Word or PDF (or another format), to automate and speed up the creation of glossaries.(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)
  • Termmbase compatibility to the TBX standard format. It will be nice, if MemoQ were able to import and export files with the TBX [1]standard termbase exchange format. (Paul Bouvier)

[edit] GUI

  • It would be nice to have the number of words not started in the Project Status bar at the bottom of the screen. [Requested Nov 2007 by Karin Adamczyk]
  • Larger or adjustable font for the Translation Results area. [Requested Nov 2007 by Karin Adamczyk]
  • "Projects" button in "Project Manager" (under "Settings") which gives direct access to other projects (TilovdB)
  • Display file extensions (and maybe Windows-file-type-icons) in Project Manager (TilovdB)
  • View: All except locked rows (TilovdB)
  • View: Locked rows (TilovdB)
  • Option "Omit embedded codes" when retrieving fragments from "Translation Results" (TilovdB)
  • Elimination of duplicates (same target, same source) from termbases and translation memory (David Turner)
  • Reduce clutter in Translation Results window (numbers, number of fuzzy matches, etc. (David Turner)
  • Edit TUs directly in concordance window (T.Rox)
  • Add keyboard shortcuts for concordance window (for: Move hits up and down, insert selected) (T.Rox)
  • Move word(s) left/right keyboard shortcut as an editing workaround for MQ's lack of drag'n'drop (cut selection (word if insertion point), move left/right, paste, retain selection for next move). (David Turner, May 2008)
  • Being able to use MemoQ on two screens (Anette)
  • Make all the File Filter settings available via Tools > Options (Thomas V.)
  • Provide a GUI to edit the smart quote replacements (Thomas V.)

[edit] Import/Export

  • Import/Export of Transit files, I think (when autoassemble/ebmt is covered) that this will be the crucial feature for MemoQ, the 'killer application thing'. Never understood why Atril doesn't offer this, I believe it's because of old ties. (Hans List)
  • VBA-like macro language that allows us to communicate with the interace (pop-up dialogs etc.) and create our own goodies that we can share via this WIKI. My suggestion: Basic Script is Visual Basic for Application™ compatible language built on top of popular SAX Basic engine. The Basic Script comes with powerful editor (features syntax highlighting, tool tips), debugger, dialog editor, language reference help and other tools necessary for comfortable scripts development. Basic Script features more commands then native macro language and allows user to write more complex scripts: use OLE, DDE, create dialogs, use mathematical functions and much more. (Hans List)
  • Set the language of exported documents to the target language (instead of leaving the original source language setting). Currently 100% of the text in exported doc files is underlined in red. (tsca)

[edit] Others

  • 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)
  • "Copy placeable" feature from Wordfast - to be able to first mark, then copy digits/strings with digits from source to target with a shortcut (Grzegorz Harbaszewski)
  • Allow "unconfirming" all segments at one go (Grzegorz Harbaszewski)
  • Marking spelling mistakes as you type (am I asking too much?) (Grzegorz Harbaszewski)
  • Include spaces in character count (Grzegorz Harbaszewski)
  • Ability to edit and delete portions and matches directly in the Translation Results window (David Turner)
  • After running the "Resolve errors and warnings function", you are still taken to a blank "Resolve errors and warnings" window even if there are no errors to correct. It would be better to have a "No errors or warnings" message. (David Turner)
  • Enable "Add all" button in "Mark selected ranges" (XLS-Import) to select multiple tab sheets subsequently (TilovdB)
  • Improve speed of spell checker (TilovdB)
  • AutoAssemble and EBMT. (Hans List)
  • Formatting/adding/inserting of bold, italics and underlined is fine (great), but for a technical translator supscript and superscript are necessary too (a lot of m², m³, m-1 etc. in technical texts). (Hans List)
  • Automatic copy of statistics in project folder or at least a reminder/confirmation before closing the statistics' windows (T. Rox)
  • Find & Replace - adding option with ability to find a source string only in confirmed/edited segments (T. Rox)
  • Special characters This function is available in the most recent edition, see menu Edit → Insert symbol.
  • Working area - moving windows from inside MemoQ (like translator's grip, automatic translation results or translation preview) out of MemoQ (for example to another screen) - Grzegorz Kowalski
  • A shortcut key for Export Active Document (Anette)

[edit] Solved issues or workarounds

For any problem and workaround see also the page CAT-Tools/MemoQ/Tips and Tricks.

[edit] Solved issues

  • Unified view of all files in project as if they were one file (David Turner) - View feature in Version 2.2 does this job.
  • Alphabetical/natural sorting of unified view and individual files (source or target) (David Turner) - Version 2.2 does this job.
  • Filtering on a term or portion in unified view and individual files (in combination with sorting) (David Turner) - Version 2.2 does this job.
  • Row/segment selection/view according to status: duplicates only, fuzzy only, empty only, etc. in combination with sorting and filtering (David Turner) - Version 2.2 does this job.
  • Export filter to Trados(TM) uncleaned format (Pablo Bouvier) - Version 2.2 does this job.
  • Import filter to import Trados(TM)-TMs in txt format. (T.Rox) - can be resolved with PlusToyz, XBench or Olifant.
  • Add sublanguages for Dutch (TilovdB) - - Version 2.2 does this job (Belgium and Netherlands).

[edit] Workarounds

[edit] Allow keeping only the last translations for every segment.

  • DVX cannot perform this trick (neither can Transit, Trados does it, when re-importing an exporting TM). (Hans List)
  • See the solution Gábor Ugray provided under CAT-Tools/MemoQ/Tips and Tricks!

[edit] Auto correct as you type.

  • Current workaround is to use PhraseExpress, AutoHotkey or similar (Requested Nov 2007 by Karin Adamczyk)

[edit] Automatic insertion of exact/best matches from TM

  • Pretranslation should do the job (can be configured in different ways) (Grzegorz Harbaszewski)

[edit] Hide target languages you don't need

  • Edit the LangInfo.xml file and comment out or delete the languages you don't need. You can use Notepad or an XML editor, your choice. Note: Be sure to save a copy of your edited file in a safe place, because a program update will overwrite it.
    - The file is found here: C:\Documents and Settings\All Users\Application Data\MemoQ\LangInfo.xml
    Workaround by Gregory - confirmed by Gábor Ugray of Killgray on the MemoQ2 list: http://tech.groups.yahoo.com/group/MemoQ2/message/2009.

[edit] Shortcut: delete all codes in current translation segment

  • Current workaround is to use PhraseExpress, AutoHotkey, or similar (TilovdB)

[edit] Shortcut: delete entire contents in current translation segment

  • Current workaround is to use PhraseExpress, AutoHotkey, or similar (TilovdB)
Retrieved from "http://en.wikibooks.org/wiki/CAT-Tools/MemoQ/Wishlist"