Warning: Invalid argument supplied for foreach() in /home/wasaty/www/blog/wp-content/plugins/xili-language/xili-language.php on line 3562

Warning: Cannot modify header information - headers already sent by (output started at /home/wasaty/www/blog/wp-content/plugins/xili-language/xili-language.php:3562) in /home/wasaty/www/blog/wp-includes/feed-rss2.php on line 8
Wąsaty tłumacz http://wasaty.pl/blog O tłumaczeniach przy fajce i kawie Thu, 15 Nov 2018 11:09:31 +0000 en-US hourly 1 https://wordpress.org/?v=5.0.4 Memsource files in memoQ http://wasaty.pl/blog/2018/01/30/memsource-files-in-memoq/ http://wasaty.pl/blog/2018/01/30/memsource-files-in-memoq/#comments Tue, 30 Jan 2018 21:16:57 +0000 http://wasaty.pl/blog/?p=905

Continue reading]]> When it comes to online CAT-tools I personally consider Memsource as one of the better ones – it’s reasonably fast, offers decent functionality and usability. It’s even better with local (but not offline) client, which can undock some windows, so you can have concordance and TM matches on screen at the same time. Still, it’s not the same as memoQ when it comes to comfort and features, so whenever possible, I process Memsource files in memoQ – that is, if PM allows to download .mxliff files for work with local tool.

To do so I’m running pre-translation with relatively low threshold, download project files and open them in memoQ with another copy in Memsource for concordance and TB checks. After translation I open the files in memsource editor and use upload functionality to synchronize files with the server.
Unfortunately, the XLIFF format is a bit loose when it comes to how certain features should be implemented, so things like match rate and translation status are not imported by default and need some tinkering. I have created a template that can be used to import Memsource files in a bit more comfortable way.

There is a substantial edit concerning the template:

Originally .mxliff files were modified only before importing into memoQ, and I left cleaning up extra content to memsource editor. Now when you export finished translation, extra bits added for memoQ’s compatibility will be removed.


  1. Segments confirmed in memoQ will show as confirmed in Memsource. Of course you should still update the Memsource TM.
  2. Content of “Alt-trans” imported by default to memoQ from Memsource as comment will be ignored now. I was asked by multiple users to disable this. If you want alternative translations from Memsource, you can enable them in memoQ filter filter options.
  3. I removed my export path rules from template settings – this was causing problems for some users. Still, it’s a good idea to edit export path rules so memoQ will overwrite original files and you won’t have to manually re-name files exported from memoQ (to remove defalut “_iso” target language addition).

Original post content (still valid):

The template work by performing automated actions: the files are edited with regex-based Find and Replace rules to insert additional attributes for match rate and segment states (regex rules are included in .xml configuration files). Subsequently customixed XLIFF filter is used, configured to recognize the introduced attributes and regex-based tagging is run to convert Memsource tags into memoQ tags.

To use the template you need to follow instructions below for import and setup. When everything is configured correctly, you can create project from template and work with Memsource files more comfortably. But always remember to back up your files in case something goes wrong. Also while the conversions and template were tested by two people without any issues (at the time of publication), I can’t predict every possible case and setup, so you are doing this at your own risk – if something goes wrong, I may tray to help, but I won’t be held responsible.

Before you start: the template will work only with memoQ 8.x and 7.8, not older. However, executable file “FindAndReplace.exe” is only installed with memoQ version 8.1 and newer. If you have older version, you need to download it separately (see below).

Template Memsource does the following:

  • match rate will be visible in memoQ
  • locked status will be kept (segments locked in memsource will be locked in memoQ)
  • “translated” status will be kept
  • segments populated with machine translation will have “MT” status in memoQ
  • memsource tags will be converted into memoQ tags


1. memoQ version 8.1 and newer: none
2. memoQ version 7.8: download and unzip executable FindAndReplace (alternatively download and install newest memoQ version, you can still use 7.8, but FindAndReplace will be installed in the default path).


  1. Download this file: memsource_updated.zip
  2. Unzip the content (remember where you unzipped it).
  3. Start memoQ, open Resource console.
  4. Select Filter configurations.
  5. Select Import new and import:  ChainedConverter#memsource-tagged.mqres
  6. Select Project templates.
  7. Select Import new > Memsource.mqres
    The template contains hard-coded path for configuration file: C:\memoQ\FindAndReplace\memsource.xml. If you don’t want to edit the template, create this folder and put “memsource.xml” in this path. Alternatively edit the template:
    Select Resource console > Templates > memsource with states > Edit > Automated actions > Script before import and edit path in Command line arguments field, then click Update.
    You can now create template project and import Memsource files.

Project creation

  1. From the main memoQ screen select New Project.
    Create new project from template dialog will be displayed.
  2. Add documents or Add folder structure, then click Next.
  3. Select Memsource from Project-template drop-down select languages and fill metadata fields.memoQ will import files applying filter settings. Tagging mechanism will create empty (single) tags for numbers enclosed in curly brackets ( {1} ), opening (left) tags for any content starting with left curly bracket and closed by “greater than” sign (e.g. {1> or {i> ) and closing (right) tags for any content starting with “less than” sign closed by right curly bracket (e.g. <1} or <i} ). However, it is unlikely but possible that incorrect content will be tagged. In such case please contact me.

Please note that the project won’t have any TMs or TBs and only default resources will be attached, so you need to add TM and other resources manually using relevant Project home cards (Translation memoriesTerm bases, etc.).

PRO tip: File extension “mxliff” is not recognized by memoQ, so when you are adding files to an existing memoQ project, you need to “Show all“. But when you create a project based on this template you can skip “Add files” step (just don’t add any files in the step 2 above) and when the template-based project is created, simply drag and drop mxliff files into “Translations” memoQ window. Files will be recognized and correct filter will be applied automatically.


If instead of importing files into project Document import options dialog is displayed with red exclamation mark to the left of the file name, it means filter configuration is not properly installed or recognized. Repeat steps 3-5 of the Instalation section and try again.

If that doesn’t help, or when importing filter you’ll get a message “A filter configuration with the same name already exists in this location“, you can try the following steps:

  1. Open Resource console and go to Filter configurations section.
  2. Click memsource-tagged filter and select Properties command.
  3. Rename the filter, e.g. to memsource-tagged2.
  4. Still in the Resource console go to Project templates section.
  5. Select Memsource and click Edit.
  6. Click SettingsLanguage-independent resources.
  7. In the Filter configuration section select new name entered in step 3 (e.g. “memsource-tagged2”) from the Filter configuration drop-down.
  8. Click OK and create new template-based project.

If the above procedure also fails, you can try contacting me, but before you do, please make sure all your paths and file names are correct and you followed all the steps described here.

To update already installed template you need to:

  1. Use Resouce console to delete existing filter configuration and project template and install updated version
  2. Use Resouce console to rename existing filter configuration and project template and install updated version
  3. Import updated filter configuration with new name, import updated project template with new name and modify it to include updated filter configuration name.

Please note: the templates reference FindAndReplace.exe file, which should be available at C:\Program Files (x86)\Kilgray\FindReplace Tool folder (for memoQ 8.1 and up). If you have non-standard memoQ installation path, you need to edit exe configuration in template settings (see below). If you have memoQ version older than 8.1, you need to download the file separately and edit the path in template settings:

  1. Select Resource console > Templates > memsource with states > Edit > Automated actions > Script before import > Select findandreplace.exe and click Delete.
  2. Click Add files…, browse to and select FindAndReplace.exe.
  3. Click Update.

Template can be further customized with your default languages, TMs, light resources etc.

Additional help for templates with find and replace scripts can be found here: https://help.memoq.com/8-3/en/index.html?edit-template-find-and-replace.html
Template configuration file (actual find and replace commands) is commented and you can customize it any way you like.

]]> http://wasaty.pl/blog/2018/01/30/memsource-files-in-memoq/feed/ 14
Terminology mining from Eur-Lex corpora http://wasaty.pl/blog/2016/10/29/terminology-mining-from-eur-lex-corpora/ http://wasaty.pl/blog/2016/10/29/terminology-mining-from-eur-lex-corpora/#respond Sat, 29 Oct 2016 15:29:11 +0000 http://wasaty.pl/blog/?p=898

Continue reading]]> euThe conference #TranslatingEurope Forum 2016 was held on October 27-28 in Brussels. Besides presentations, the conference included two sessions of mini-workshops: the idea was to present some practical aspect of translation in small group – three people at a time. The workshops included my submission on terminology mining. I realized from the start that participants won’t be able to remember anything from 15-minute session with three different software tools, I have prepared handouts with some background information I had no time to introduce and description of all steps presented in the procedure. Since the workshop was quite popular (all groups were far larger than 3), I’m publishing somewhat extended version of the handout, which is available here:  Terminology_mining.pdf.

You can use the text freely, but if you use it for any derivative work, please credit the author.

]]> http://wasaty.pl/blog/2016/10/29/terminology-mining-from-eur-lex-corpora/feed/ 0
Tłumaczenia kart charakterystyk – przydatne materiały http://wasaty.pl/blog/2016/03/13/tlumaczenia-kart-charakterystyk-przydatne-materialy/ http://wasaty.pl/blog/2016/03/13/tlumaczenia-kart-charakterystyk-przydatne-materialy/#respond Sun, 13 Mar 2016 08:33:15 +0000 http://wasaty.pl/blog/?p=889

Continue reading]]> MSDSZamieszczone tu materiały stanowią uzupełnienie mojej prezentacji na Konferencji Tłumaczy z dnia 13 marca 2015 r. i w dużej części stanowią przywołanie materiałów zamieszczanych na blogu już wcześniej. Dla zainteresowanych dostępna jest też prezentacja w formacie PowerPoint z pełnym tekstem wykładu.

  • Serwis Eur-lex: akty prawne Unii Europejskiej. W pisać słowa kluczowe w polu wyszukiwania lub wpisać rok i numer szukanego dokumentu (np. 1907/2006).
  • Agencja ECHA: poradniki dotyczące sporządzania dokumentów związanych z kartami charakterystyk i przykładowe dokumenty. Część dostępna tylko po angielsku, część również w innych językach, również po polsku.
  • Baza terminologii ECHA: ponad tysiąc trzysta terminów z legislacji dotyczących chemikaliów, z definicjami i źródłami. Możliwość pobrania całości lub wybranych działów i języków.
  • Baza terminologii IATE: Interactive Terminology for Europe, terminologia Unii Europejskiej z całego zakresu dziedzin, również związanych z REACH i CLP.
  • Linguee: serwis oferujący wyszukiwanie w korpusach wielojęzycznych. Dzięki dużej bazie dopasowanych dokumentów świetne miejsce wyjścia do wyszukiwania terminologii/tłumaczeń dokumentów unijnych – ale zawsze należy sprawdzać, skąd pochodzi znalezione tłumaczenie.
  • Glosariusz akronimów: opracowany i utrzymywany przeze mnie glosariusz akronimów spotykanych w kartach charakterystyk. Korzystanie na własną odpowiedzialność.
  • Zestawienie zwrotów H i P: w artykule dostępne łącza do zestawienia wszystkich zwrotów w oryginalnej postaci dla wszystkich oficjalnych języków UE oraz rozbudowane zestawienie dla pary angielski-polski.
  • Zestawienie zwrotów R i S: formalnie nieaktualne, w tłumaczeniach będą występować jeszcze przez wiele lat.
  • Zestawienie nazw ONZ substancji niebezpiecznych z ustaw ADR/ADN/RID, z roku 2015: arkusz pobrany w listopadzie 2015 r. ze stron Ministerstwa Infrastruktury i Rozwoju, Departament Transportu Drogowego. Korzystanie na własną odpowiedzialność.

Tutaj dostępna jest prezentacja na temat tłumaczeń chemicznych, którą przedstawiłem na konferencji.

]]> http://wasaty.pl/blog/2016/03/13/tlumaczenia-kart-charakterystyk-przydatne-materialy/feed/ 0
Crash course in regular expressions http://wasaty.pl/blog/2016/03/10/crash-course-in-regular-expressions/ http://wasaty.pl/blog/2016/03/10/crash-course-in-regular-expressions/#comments Thu, 10 Mar 2016 16:49:10 +0000 http://wasaty.pl/blog/?p=892 regexI was invited to write a guest post on regular expressions in FrameMaker at Adobe blog platform. While it is written with FrameMaker in mind, I think the text can help anyone grasp basics of regex for any applications, including translation tools like memoQ or Trados Studio.

http://wasaty.pl/blog/2016/03/10/crash-course-in-regular-expressions/feed/ 1
memoQ auto-translatables for numbers http://wasaty.pl/blog/2015/11/15/memoq-auto-translatables-for-numbers/ http://wasaty.pl/blog/2015/11/15/memoq-auto-translatables-for-numbers/#comments Sun, 15 Nov 2015 12:24:23 +0000 http://wasaty.pl/blog/?p=875

Continue reading]]> new_memoQmemoQ is an excellent CAT/TEnT tool which offers plenty of advanced productivity features out of the box, but with little tinkering can be made even more useful. One of the advanced memoQ features is Auto-translatables: using regular expressions you can define how certain source text should be modified in target language. The rules can be quite advanced, e.g. for date format conversion from English “Monday, January 3rd, 2106” to Polish “Poniedziałek, 3 stycznia 2016 r.”. One of the most frequent uses for auto-translatables is the conversion of numeric strings according to target language rules. It used to be the most basic auto-translatable application – it’s not needed so much now, since memoQ offers automatic, out-of-box number format conversion: if your source segment contains numbers formatted according to source language rules,  just press Ctrl and from the displayed list select value formatted according to target language rules. The thing is, source format not always follows the rules (defined in Microsoft libraries used by memoQ).

Sometimes it’s still more convenient to use auto-translatables for format conversion. memoQ comes with some rules defined for the following target languages: English, French, German, Hungarian and Swiss, so in theory with some basic regular expressions (regexp for short) knowledge you should be able to modify them if they don’t work exactly as needed. Unfortunately, the rules shipped with memoQ have two drawbacks:

  • they are “one size fits all” with regard to source number format, so some trade-offs were necessary. And there are specific cases where they fail,
  • they are quite messy, not easy to interpret and modify.

Since the subject of auto-translatable rules for numbers is regularly raised on memoQ mailing list, I decided to share the simple, but rather robust rules created for for English to Polish format conversion that are easy do customize according to any source/target language combination. There is also a second, more complex set of En-Pl rules that I actually use in my daily work.

If you want to modify the rules, I strongly suggest to edit them using a text editor before importing into memoQ. Unfortunately the built-in memoQ editor for auto-translation rules is not very convenient, because due to its fixed size, you can see only small part of longer expressions, plus rules are re-ordered every time you change one of them. I suggest using Notepad++ for editing, but any text editor will do. If you do use Notepad++, after opening the file click Language menu and select XML – this will make editing much easier, because editor will show elements with different colors (see screenshot below). The rules are numbered, but you won’t see the numbers (or comments) once you import the file into memoQ.

Auto-translatable rules for numbers format conversion opened as .mqres file in Notepad++ with XML syntax clolring

Auto-translatable rules for numbers format conversion opened as .mqres file in Notepad++ with XML syntax clolring

First some background information:

The file is designed to convert English numbers into Polish formats – that means comma (,) as thousands separator and period (.) as decimal separator for source and (non-breaking)space ( ) as thousands separator and comma (,) as decimal separator for target. Several examples:






12 345




12 345,67


English financial documents sometimes use space instead of comma for thousands separator. The rules won’t work in such case, they would require modification (see near the end of post). To explain how this work, I’ll describe the rule number 2 (screenshot above).

<replaceRule>$1 $2</replaceRule>

Match rule:

  1. (?&lt;!\d,|\d\.|\d) – this part says: do not match, if before the numbers there is a digit (\d) followed by comma (,) or (I) number followed by period (\.) or number. The “&lt;” is actually way of encoding “<”, and that’s what you will see once you import the rules into memoQ.
  2. ([-–]?\d{1,3}),(\d{3}) – this part says: match if one, two or three digits (\d{1,3}, first numbered group), comma (,), and exactly three digits (\d{3}, second numbered group). Optionally there can be a dash or minus sign at the beginning ([-–]?), if present, it will be part of the first group.
  3. (?!,\d|\.\d|\d) – this part says: do not match, if after the point 2. there is a comma and digit (,\d) or period and digit (\.\d) or digit (\d).

This will match: 1,234 or 12,345 or 123,456

Replace rule:

  1. $1 $2 – this means get the write of the first group (point 2. above), then non-breaking space, then content of the second group (point. 2 above).

The conversion result: 1 234 or 12 345 or 123 456

As you can see, the actual number matching is done by rule in point 2, so what are points 1 and 3 for (blue text)? They are called “assertions” and they are there to limit matching to only the group you want. Let’s examine what would happen, if we’d write two following rules to match thousands in two ranges:

([-–]?\d{1,3}),(\d{3}) for numbers xxx,xxx

([-–]?\d{1,3}),(\d{3}),(\d{3}) for numbers xxx,xxx,xxx

Let’s use them on actual segment with numbers:

auto-trans rule

As you can see, the second rule matches as it should, but the first one matches too, because the rule matches also to a part of longer number. And that’s why I have used the assertions – to limit matching. And to exclude matching of longer numbers, one must exclude combination of the symbols appearing in the numbers formatting with numbers. That’s why in the “before” part I have excluded “\d,” (digit followed by comma), “\d\.” (digit followed by period) and “\d” (just number), and in the “after” part the same in reverse order: “,\d” (comma followed by digit), “\.\d” (period followed by digit) and “\d” (just digit).

So the important thing to remember is that if you want to modify the rules to different system, you need to replace current thousands separator and decimal symbol in both matching and assertions parts.

Before we proceed to actual modifications, one more important explanation:

Source (matchRule) and target (replaceRule) are interpreted differently when it comes to symbols. In regular expressions period (.) has a special meaning (“any character”), so if we want to match exactly period, we need to use (\.). However on the replacement side everything except “$number” is treated literally, so if you want to use period, just write a period. Similarly, while “\s” means “space” in the matching part, to get a space on the replacement side just type a space. Or paste non-breaking space from any program (e.g. Word or memoQ translation editor).

Now I will show you how to modify the rules for different source/target combination using Swiss as the source language format: apostrophe () as thousands separator, period (.) as decimal separator and Norwegian as target format: period (.) as thousands separator, comma (,) as decimal separator. Examples:













Of course start by downloading the file, then open it in text editor.

Let’s try to modify rule number 2:

<replaceRule>$1 $2</replaceRule>

We need to replace comma (,) with apostrophe () in the source part:


And replace space with period in the target part:


That’s it. I have replaced comma with an apostrophe, but I didn’t touch the period, because it’s also used in this source system, just in a different role. To cover everything, let’s try the rule number 6, with both number grouping symbol and decimal separator:

<replaceRule>$1 $2,$3</replaceRule>

We need to change it to:


This kind of changes needs to be done for every rule in the document, both for source (matchRule) and target (replaceRule). I advise not to use “Find and replace” for rules editing (especially not “replace all”), because it’s easy to mess up something by mistake.

And since there are two types of apostrophes (straight and curly: and ), to make the rules more foolproof you may want to create two sets of auto-translatables – one for each kind and use both in  your projects (if you prefer to keep regexes simple). Or you may try to use one set of rules making it a bit more complex:


Now there are separate conditions in assertions and alternative matching condition for separator: (?:’|’ ). The use of “?:” makes this group non-numbered, so this not affects target groups.

And one last example for space as thousands separator instead of comma:


Once you finish your edits, save the file (it has to be plain text with .mqres extension and UTF-8 encoding and simply import to memoQ (Resource console > Auto-translatables > Import). If memoQ complains:

  • during import – it means that XML structure is broken. Make sure all the <> parts are intact and that for every opening tag (<whatever>) there is exactly one closing tag of the same type (</whatever>),
  • when adding rules to project – it means there is some error in the regular expressions part. When you click “More” button on the error notification dialog memoQ will show first offending line. Make sure all brackets, parentheses and curly brackets are paired and the syntax is correct.

I also encourage you to check the auto-translatable set I use for numbers conversion – there are additional rules for matching telephone numbers (rules 11 and 12), proper recognition and conversion of percentage values (15, 16) and temperatures (°C and °F, 13 and 14). Plus rules for special case of numbers between 1,000 and 9,999, where thousands separator is not used in Polish (so 1000 and 9999 respectively).

* * *

An additional note regarding ease of rules editing. memoQ offers excellent mechanism of #lists# and in theory it should be easy to create rule set where all you have to do to modify rules according to your source rules would be to change content of #thousands_separator# and #decimal_place# lists. I tried, that was my original idea behind this post. Unfortunately it’s not possible, because you can’t use lists in assertions (well, you can, but the results are not what one would expect).


]]> http://wasaty.pl/blog/2015/11/15/memoq-auto-translatables-for-numbers/feed/ 2
Importing Studio TM and TB into memoQ http://wasaty.pl/blog/2015/11/07/importing-studio-tm-and-tb-into-memoq/ http://wasaty.pl/blog/2015/11/07/importing-studio-tm-and-tb-into-memoq/#comments Sat, 07 Nov 2015 15:13:34 +0000 http://wasaty.pl/blog/?p=872

Continue reading]]> new_memoQmemoQ is great tool with many interoperability features, including easy SDLXLIFF file import/export, ability to import Studio packages and generating Studio return packages. And while packages are imported with translation memories and term bases, strangely the ability to import stand-alone Studio TMs (SDLTM) and TBs (SDLTB) is nowhere to be found in the UI. And this can be a seroius problem if a client sends you SDLXLIFF and SDLTM files instead of proper package (happens often enough). And while there is a solution to this problem, I’m offering a relatively simple alternative.

Since memoQ can import both TM and TB native formats as parts of Studio package, all we need is to add the files we need into a proper Studio package and import it into memoQ. Using a simple package as a starting point I’ve created a bogus Studio package you can use to import the files you need. Here’s how:

  1. Download this file.
  2. Unpack its content to an empty folder (e.g. “Package”)
  3. Go to TM folder.
  4. Copy the TM file you need to import (e.g. “My_Studio_TM”) into this folder (optional: you can delete “Example_TM.sdltm” file)
  5.  Browse one level up, to folder “Package”.
  6. Go to Termbases folder.
  7. Copy the TB file you need to import (e.g. “My_Studio_TB”) into this folder (optional: you can delete “Example_TB.sdltb” file).
  8. Browse one level up, to folder “Package”.
  9. Open “Import_wrapper.sdlproj” with text editor (right click the file, select “Open with” and choose Notepad or any other text editor).
    Optionally you can rename the file, adding extention .txt, which will help with file editing.
  10. Find string “Example_TM.sdltm” and replace it with the name of the TM you want to import (e.g. “My_Studio_TM.sdltm”).
  11. Find string “Example_TB.sdltb” and replace it with the name of the TB you want to import (e.g. “My_Studio_TB.sdltb”).
  12. Find string “Example TB” and replace it with the name of your TB (e.g. “My Studio TB”).
  13. Replace all occurrences of string “en-GB” with the code for your source language (e.g. “de-DE” for German-Germany).
  14. Replace all ocurrences of string “pl-PL” with the code for your target language (e.g. “fr-FR” for French-France).
  15. If you do import term base, remember to replace index languages (English, Polish) with your source and target languages.
  16. Save edited “Import_wrapper.sdlproj” file. If you changed the extension in step 8, remember to re-name it back to .sdlproj.
  17. Create a ZIP archive of the folder (e.g. “Package”) content.
  18. Rename the archive by changing .zip extension into .sdlppx
  19. Import content to memoQ with “Import package” command. memoQ will notify you during import that there are no files to translate, but TM and/or TB will be imported and can be used in different memoQ projects.

Please note that since Import_wrapper.sdlppx file does not contain any files for translation, it can’t be imported into Studio. And if you have problems with changing file extensions, please see here.

]]> http://wasaty.pl/blog/2015/11/07/importing-studio-tm-and-tb-into-memoq/feed/ 2
Angielsko-polski glosariusz zwrotów H i P http://wasaty.pl/blog/2015/10/27/angielsko-polski-glosariusz-zwrotow-h-i-p/ http://wasaty.pl/blog/2015/10/27/angielsko-polski-glosariusz-zwrotow-h-i-p/#comments Tue, 27 Oct 2015 18:55:57 +0000 http://wasaty.pl/blog/?p=868 MSDSJak dobrze wie (albo powinien wiedzieć) każdy, kto ma styczność z tłumaczeniem kart charakterystyki (Safety Data Sheets, SDS), mogą one zawierać zwroty określające zagrożenia (Hazard, H-phrases) i zwroty określające środki ostrożności (Precautions, P-phrases). Treść tych zwrotów została opublikowana w rozporządzeniu Parlamentu Europejskiego i Rady (WE) nr 1272/2008 (CLP). Dokument ten był wielokrotnie korygowany kolejnymi rozporządzeniami, które modyfikowały również treść zwrotów H i P. W czerwcu tego roku został opublikowany tekst ujednolicony rozporządzenia, dostępny w serwisie Eur-Lex. Ponieważ w tekście dokumentu zamieszczone są zwroty H i P we wszystkich językach Unii, prosta obróbka umożliwiła mi stworzenie zestawienia wszystkich zwrotów we wszystkich językach w formie pozwalającej na łatwe zaimportowanie ich do bazy terminologii dowolnego programu CAT.

Jednak było to dla mnie tylko punktem wyjścia do stworzenia bardziej rozbudowanej bazy terminologii w parze EN-PL. Wszystkie zwroty, które składają się z wydzielonych części, znajdują się w bazie w całości oraz w postaci odrębnych terminów dla każdego fragmentu. Np. zwrot EUH 202, który składa się z czterech zdań (Cyjanoakrylany. Niebezpieczeństwo. Skleja skórę i powieki w ciągu kilku sekund. Chronić przed dziećmi.) znajduje się w bazie jako pełny zwrot, ale też osobnymi pozycjami są wszystkie zdania składowe, ponieważ segmentacja tekstu źródłowego zazwyczaj spowoduje ich rozbicie (czyli razem 5 pozycji). Podobnie dwa wpisy zajmuje zwrot H351 (Podejrzewa się, że powoduje raka <podać drogę narażenia, jeżeli definitywnie udowodniono, że inna droga narażenia nie powoduje zagrożenia>) – raz w całości, raz bez części w nawiasach trójkątnych. Osobnymi wpisami są też elementy rozdzielane ukośnikami, np. części składowe P260 (pył/dym/gaz itp.), natomiast nie dotyczy to pozycji z dwukropkami. Każdy wpis jest oznaczony identyfikatorem zwrotu, a zwroty, które nie pochodzą z rozporządzenia 1272/2008 zostały odpowiednio opisane. W niektórych wypadkach wpisałem też alternatywy dla pisowni GB/US lub inne wersje alternatywne, w wersji uproszczonej (patrz niżej) oddzielone symbolem „|”.

Ale uwaga – istnieją zwroty H i P, które nie zostały zamieszczone w rozporządzeniu 1272/2008 i trudno znaleźć ich oficjalne tłumaczenie. Zwroty H zostały przetłumaczone w dokumencie ECHA, tłumaczenia brakujących zwrotów P dostępne są w bazie terminologii IATE. Aby łatwiej je znaleźć w przyszłości, umieszczam te tłumaczenia poniżej, wraz z moją propozycją polskiego tekstu zwrotów określających zagrożenie z nowozelandzkich przepisów GHS – czasami spotyka się je w tłumaczeniach.

Baza dostępna jest w formie pliku Excel wyeksportowanego z programu memoQ, z wydzielonymi w niektórych przypadkach rdzeniami słów (matching: custom). Można ją w tej postaci zaimportować do memoQ bez żadnych problemów. Dla osób używających innych CATów dostępna jest też wersja uproszczona, również w formacie Excela, zawierająca tylko tekst EN, PL i identyfikatory (uwaga na P280/P282 – w pierwszym „Use” jest raz tłumaczone jako „stosować”, w drugim „nosić”).


ID EN PL Źródło
H227 Combustible liquid Ciecz zapalna. ECHA*
H303 Harmful if swallowed or if inhaled Działa szkodliwie po połknięciu lub w następstwie wdychania ECHA* / H290+H302
H305 May be harmful if swallowed and enters airways. Może działać szkodliwie po połknięciu i dostaniu się przez drogi oddechowe. ECHA* / H290+H302+H304
H313 May be harmful in contact with skin. Może działać szkodliwie w kontakcie ze skórą. ECHA* / H290+H302+H312
H316 Causes mild skin irritation. Działa łagodnie drażniąco na skórę. ECHA* / patrz H315
H320 Causes eye irritation. Działa drażniąco na oczy. ECHA* / patrz H319
H333 May be harmful if inhaled. Może działać szkodliwie w następstwie wdychania. H290+H332
H401 Toxic to aquatic life. Działa toksycznie na organizmy wodne. ECHA* / patrz H400, H410
H402 Harmful to aquatic life. Działa szkodliwie na organizmy wodne. ECHA* / H302+H400
Nowozelandzie GHS
H421 Very toxic to the soil environment. Działa bardzo toksycznie w glebie. Na podstawie H400 i H410
H422 Toxic to the soil environment. Działa toksycznie w glebie. Na podstawie H400 i H410
H423 Harmful to the soil environment. Działa szkodliwie w glebie. Na podstawie H400 i H410
H431 Very toxic to terrestrial vertebrates. Działa bardzo toksycznie na kręgowce ziemne. Na podstawie H400 i H410
H432 Toxic to terrestrial vertebrates. Działa toksycznie na kręgowe ziemne. Na podstawie H400 i H410
H433 Harmful to terrestrial vertebrates Działa szkodliwie na kręgowce ziemne. Na podstawie H400 i H410
H441 Very toxic to terrestrial invertebrates. Działa bardzo toksycznie na bezkręgowce ziemne. Na podstawie H400 i H410
H442 Toxic to terrestrial invertebrates. Działa toksycznie na bezkręgowce ziemne. Na podstawie H400 i H410
H443 Harmful to terrestrial invertebrates. Działa szkodliwie na bezkręgowce ziemne. Na podstawie H400 i H410
P281 Use personal protective equipment as required. Stosować wymagane środki ochrony indywidualnej. IATE
P307 IF exposed W PRZYPADKU narażenia IATE
P309 IF exposed or if you feel unwell W PRZYPADKU narażenia lub złego samopoczucia IATE
P322 Specific measures (see … on this label) Środki szczególne (patrz … na etykiecie) IATE
P341 If breathing is difficult, remove victim to fresh air and keep at rest in a position comfortable for breathing. W przypadku trudności z oddychaniem, wyprowadzić lub wynieść poszkodowanego na świeże powietrze i zapewnić warunki do odpoczynku w pozycji umożliwiającej swobodne oddychanie. IATE

* ECHA: http://echa.europa.eu/documents/10162/13653/dsm_12_cl_pl.pdf

Jeśli będziesz korzystać z glosariusza i uznasz go za przydatny, na następnej konferencji możesz postawić mi piwo (lub kawę).

http://wasaty.pl/blog/2015/10/27/angielsko-polski-glosariusz-zwrotow-h-i-p/feed/ 2
Amended H and P phrases http://wasaty.pl/blog/2015/10/23/amended-h-and-p-phrases/ http://wasaty.pl/blog/2015/10/23/amended-h-and-p-phrases/#comments Fri, 23 Oct 2015 18:36:39 +0000 http://wasaty.pl/blog/?p=865

Continue reading]]> MSDSLast December I’ve created and published here a spreadsheet with H and P phrases plus S and R statements from CLP regulations.  Time goes by and the EU regulations get updated. On July 1st a unified text of EC Regulation 1272/2008 (CLP) was published, which includes all amendments introduced by regulations: 790/2009/EC, 286/2011/EU, 618/2012/EU, 487/2013/EU, 517/2013/EU, 758/2013/EU, 944/2013/EU 605/2014/EU, 1297/2014/EU and Corrigendums OJ L 016 and OJ L 138. I have created a new spreadsheet with H and P phrases, but without R and S statements fom CHIP regulation, since they are not valid anymore as of June 1st, 2015.

The document is available as Excel file or tab-delimited text file (CSV).

* * *

Dislclaimer: While I have prepared the file with due diligence by extracting text from regulation published by Eur-Lex service, if you are using the file, you are responsible for validation of it’s contents.

]]> http://wasaty.pl/blog/2015/10/23/amended-h-and-p-phrases/feed/ 2
Zmiany w kartach charakterystyki (MSDS) http://wasaty.pl/blog/2015/07/19/zmiany-w-kartach-charakterystyki-msds/ http://wasaty.pl/blog/2015/07/19/zmiany-w-kartach-charakterystyki-msds/#respond Sun, 19 Jul 2015 09:22:58 +0000 http://wasaty.pl/blog/?p=862

Continue reading]]> MSDSWiększość substancji chemicznych i mieszanin wprowadzanych do obrotu na terenie Unii Europejskiej musi oferować kartę charakterystyki – (Material) Safety Data Sheet – MSDS. Tłumaczenie tych dokumentów wykonuje się z użyciem ściśle regulowanego języka, czerpanego wprost z rozporządzeń unijnych opisujących treść karty charakterystyki.

Młyny unijne mielą wolno, ale nieustannie. W maju tego roku zostało opublikowane rozporządzenie 2015/830, formalnie zmieniające rozporządzenie 1907/2006, w praktyce 453/2010, czyli dokument zawierający opis karty charakterystyki.
Zmian w samej karcie nie ma wiele, ale jest kilka istotnych, np. w sekcji 1 i 8 oraz w punkcie 7.2. Z istotniejszych zmian “luzem”:

  • Chemical name: “nazwa chemiczna” -> “nazwa rodzajowa”,
  • Personal protection: “środki kontroli indywidualnej” -> “środki ochrony indywidualnej”
  • Carcinogenicity: “rakotwórczość” -> “działanie rakotwórcze”
  • Repeated exposure: “narażenie powtarzane” -> “narażenie wielokrotne”.

IMO tłumaczenie jest generalnie trochę lepsze, ale znowu niespójne wewnętrznie. O ile OEL to “wartość narażenia zawodowego”, to WEL “najwyższe dopuszczalne stężenie w środowisku pracy”

Pełny tekst w wersji dwujęzycznej dostępny w serwisie Eur-Lex.

]]> http://wasaty.pl/blog/2015/07/19/zmiany-w-kartach-charakterystyki-msds/feed/ 0
memoQ 2015 project filtering http://wasaty.pl/blog/2015/05/23/memoq-2015-project-filtering/ http://wasaty.pl/blog/2015/05/23/memoq-2015-project-filtering/#comments Sat, 23 May 2015 18:28:37 +0000 http://wasaty.pl/blog/?p=843

Continue reading]]> new_memoQOn Friday, May 22nd, during the memoQfest conference in Budapest, Kilgray officially released memoQ 2015. One of its new features is redesigned Dashboard view – the screen you see when you start the application. And although it looks better than in previous versions, initially I was disappointed with the new filtering feature. But after playing with it a bit, I’m sold: it’s much better than before (with one exception).

If you haven’t seen memoQ 2015, dashboard now looks differently for translators and project managers.

Dashboard for "translator pro" license owners, with news feed.

Dashboard for “translator pro” license owners, with news feed.

Dashboard for "project manager" license owners, without news feed.

Dashboard for “project manager” license owners, without news feed.

As you can see, now you can see the standard project metadata set (Project, Client, Domain and Subject). You can also use “two column” view in both view versions.

Two rows view for PMs.

Two rows view for PMs.

Additionally in “translators pro” version users can use panel for even simpler project creation by dragging and dropping files. But that’s not what this post is about. Regardless of your license and selected view, you have access to filter bar. In the previous versions of memoQ filter bar was available only after checking “Project manager view” check box on the main screen, and it offered the following view:

Standard project/recources filtering options

Standard project/resources filtering options

By typing in the text field you could instantly (on the fly) filter by project name and/or description, drop-downs can be used for filtering by field values. Of course this works only if you do happen to use metadata in any consistent way (and if you don’t you should).

Now the drop-downs are gone and the filter does not work on the fly – you have to press Enter if you are typing in a keyword from project name or description. Which definitely is a step back. On the other hand, you can use the text field to filter for metadata in a way that’s even more convenient than the drop-downs. Just start typing the name of the category you want to filter by, e.g. “domain”, and memoQ will suggest you the rest. Just press Enter to insert category name.


Then start typing, and the software will display list of possible values starting with that letter. Press Enter again and you are done. Filtering is applied instantly.


I find this solution very elegant and convenient. Still, I’d love to see the return of “on the fly” filtering, although I’ll understand if that’s not possible. BTW, you can also filter all projects, active projects and recent projects (accessed within last 30 days).

* * *

During the last memoQfest session Istvan Lengyel, CEO of Kilgray said that the company is going to focus now more on smoothing out the rough edges in the software. And that’s very good. One area of such “roughness” concerns inconsistencies in the software. The new filtering system is available for projects, but all the rest of resources (TMs, TBs, corpora etc.) are filtered using the old method. I’d love to see the new system implemented in all those other places too, which would also lead to much better utilization of limited space in the software dialogs.

]]> http://wasaty.pl/blog/2015/05/23/memoq-2015-project-filtering/feed/ 1