{"id":554,"date":"2011-06-05T10:46:27","date_gmt":"2011-06-05T09:46:27","guid":{"rendered":"http:\/\/wasaty.pl\/blog\/?p=554"},"modified":"2011-10-23T15:37:49","modified_gmt":"2011-10-23T14:37:49","slug":"memoq-automation-auto-translatables","status":"publish","type":"post","link":"https:\/\/wasaty.pl\/blog\/2011\/06\/05\/memoq-automation-auto-translatables\/","title":{"rendered":"MemoQ automation – auto-translatables"},"content":{"rendered":"
Tweet<\/a><\/div>\n

\"\"MemoQ is a fast, easy to use and very powerful CAT tool. However, in the default configuration it does have two features I don’t like: the QA module often gives warnings concerning numbers (“invalid number format in source\/target prevents strict matching”), and the software does not allow to copy numerical values from source segments by keyboard shortcuts, like in Trados. Both these problems can be addressed by simple operations: turning on the auto-translateables and modifying the QA rules.<\/p>\n

Let’s start with turning on “automatic” insertion of numbers. The feature works by detecting numerical values in the source text, and if they are in a proper format of given language, offering the same numerical value formatted for target language on the translation results pane. Why the format change? Because different languages use different formatting rules for numbers. For example “10,189.53<\/strong>” in English should be written as “10 189,53<\/strong>” in Polish. <\/strong> The modified values can be inserted exactly the same way as other elements from the translation results pane, e.g. by double clicking or entering Ctrl-hit number<\/strong> from the list.<\/p>\n

The procedure of enabling this function will look differently if we want to turn on auto-translatables for current project (and only for this one), or in case we would like to turn them for all new projects.<\/p>\n

Let’s start with enabling automatic number “translation” for current project<\/strong> — say to check, how this works.<\/p>\n

    \n
  1. Open\/create a project.<\/li>\n
  2. In the Settings<\/strong> panel of the current project click Auto-translation rules<\/strong>. The list of available national standards will be displayed.<\/li>\n
  3. Choose your target language (in case of Polish one can use Hungarian instead). The name of active rule set is displayed with bold font, exactly as for other resources. Below you can see the example of the numerical values recognized by default auto-translation rules.\n

    \"\"<\/a>

    Example of numerical values recognized by default auto-translation rules. The numbers separated by hyphens are recognized individually.<\/p><\/div><\/li>\n<\/ol>\n

    This will definitely simplify the translation of texts with lots of numbers, especially if they are in “standard” format. On the other hand, this will not help much if the text we are dealing with contains a lot of non-standard numbers, e.g. catalog numbers where numbers are grouped with letters, numbers separated by hyphens or references to sub-points of some documentation or legal texts. As you can see above, not all of them will be recognized.<\/p>\n

    Fortunately, auto-translation rules can be easily defined using regular expressions. To make my life easier, I’ve defined myself the group of four rules for recognizing non-standard numbers:<\/p>\n

      \n
    1. Letters and numbers combined (e.g. catalog numbers). Example: N665, Alpha9beta<\/li>\n
    2. Combined text and numbers separated by hyphen (unlimited number groups, e.g. catalog numbers, regulations). Example: IEC60001-11-1, CAP1283-34<\/li>\n
    3. Groups of numbers separated by at least two dots (e.g. software version numbers, sub-subparagraph numbers, legal texts). Example: 654.123.456, 84.12.79.1<\/li>\n
    4. Groups of numbers separated by at least two hyphens (e.g. catalog numbers). Example:6-234-957, 543-21-8<\/li>\n
    5. ADDED<\/strong>: Rules for recognizing email addresses and URLs (http and ftp). If you need to localize the URLs, just remove the rules starting with “http”.<\/li>\n<\/ol>\n

      To use my rules you have to download this file<\/strong><\/a> and in auto-translation settings (see point 2) use Import new<\/strong> command and select the downloaded file (Non-standard numbers.mqres<\/strong>). Then select it for the current project. Examples of recognized number groups are shown on the picture below.<\/p>\n

      \"\"<\/a>

      Numbers groups recognized by \u201eNon-standard numbers\u201d rule set.<\/p><\/div>\n

      The numbers with one dot are not recognized to avoid a conflict with standard rules, and groups with only one hyphen are not recognized because they usually (but not always) have to be treated separately in Polish (ie. 45-69 should be formatted as 45 \u2013 69). If we activate both rules groups (standard for target language and my non-standard numbers), the result for my example file will look like this:<\/p>\n

      \"\"<\/a>

      Active rules "Numbers-PolishGroup" and "Non-standard numbers".<\/p><\/div>\n

      If the auto-translation rules are meeting your expectations, you can activate them for all newly created projects<\/strong>. To do so:<\/p>\n

        \n
      1. In the Tools<\/strong> menu select Options<\/strong>. The Default resources<\/strong> is the first active card.<\/li>\n
      2. From the list on the Default resources<\/strong> pane click Auto-translation rules<\/strong>. Select rules, you want to activate for new projects. In my case this is Numbers-PolishGroup<\/strong> and (optional) Non-standard numbers<\/strong>.<\/li>\n
      3. Click OK<\/strong>.<\/li>\n<\/ol>\n

        It is worth knowing that auto-translatables can be used for many other things besides numbers. For example, if there are HTML tags in the Word or Excel file, we can detect them in the source segments and insert them by keyboard shortcut. In this case you have to use rules editor: enter “(\\<.+?\\>)” in the Auto-translation rules<\/strong> and “$1” in the Replace order rules<\/strong> field. Similar rules can be created e.g. for consistently marked text strings which are not to be translated. Auto-translation rules can be used also for automatic unit conversion – this subject is described in the memoQ help file.<\/p>\n

        Now, the use of auto-translation rules can simplify our job, but there are still “non-standard number format” alerts we have to deal with. How to remove them\/reduce their number?<\/p>\n

        For the current project<\/strong>:<\/p>\n

          \n
        1. In the project Settings<\/strong> panel select QA settings<\/strong>. Since the default settings cannot be modified, you have to clone them using Clone\/use new<\/strong> command in the lower right part of the window. Enter the meaningful name, e.g. Default-corrected numbers<\/strong>.<\/li>\n
        2. Select new QA rules and click Edit<\/strong> command.<\/li>\n
        3. In the Edit QA settings<\/strong> window select Check auto-translatables<\/strong> option.
          \n          \"\"
          \n<\/a><\/li>\n
        4. Click the Numbers<\/strong> tab of the Edit QA settings<\/strong> window.<\/li>\n
        5. Deselect<\/strong> all checking options<\/del>. EDIT: Deselect all checkmarks except the one for Verify that numbers are matched on the target side<\/strong> (leave that one checked, see Denis Hay comment below post).
          \n          \"\"<\/a><\/li>\n<\/ol>\n

          With these settings memoQ will no longer verify the source\/target numbers using internal rules over which we don’t have any control, but<\/strong> auto-translatables verification won’t let us miss any incorrect number in the target text. Depending on the type of text and target language rules, we can drastically reduce or even eliminate the “unknown format” warnings. Some will still be there, though – if there will be e.g. “point 6.8” or “version 12.1”, we’ll still have warnings there (at least for Polish, where the dot should be changed to comma).<\/p>\n

          To apply the above change in QA settings to all new projects:<\/strong><\/p>\n

            \n
          1. From the Tools<\/strong> menu select Options<\/strong>. The Default resources<\/strong> is the first active card.<\/li>\n
          2. From the list on the Default resources<\/strong> pane click QA settings.<\/strong><\/li>\n
          3. Select modified QA settings (e.g. Default-corrected numbers<\/strong>).<\/li>\n
          4. Click OK<\/strong>.<\/li>\n<\/ol>\n

            The modified rules will be active as defaults for all new memoQ projects.<\/p>\n

            EDIT:<\/strong><\/p>\n

            Added rules for recognizing email addresses and URLs (http and ftp). If you need to localize the URLs, just remove the rules starting with “http”.<\/p>\n

             <\/p>\n","protected":false},"excerpt":{"rendered":"

            Tweet MemoQ is a fast, easy to use and very powerful CAT tool. However, in the default configuration it does have two features I don’t like: the QA module often gives warnings concerning numbers (“invalid number format in source\/target prevents strict matching”), and the software does not allow to copy numerical values from source segments … <\/p>\n

            Continue reading<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,6],"tags":[9,11,20,24,25],"class_list":["post-554","post","type-post","status-publish","format-standard","hentry","category-narzedzia","category-wskazowki","tag-cat","tag-english","tag-memoq","tag-porady","tag-qa","item-wrap"],"_links":{"self":[{"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/posts\/554","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/comments?post=554"}],"version-history":[{"count":8,"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/posts\/554\/revisions"}],"predecessor-version":[{"id":564,"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/posts\/554\/revisions\/564"}],"wp:attachment":[{"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/media?parent=554"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/categories?post=554"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wasaty.pl\/blog\/wp-json\/wp\/v2\/tags?post=554"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}