# data[].attributes.body
14.06.2020
I prepared a CV template that may be attached with the application when applying for a job in a translation office. It is in Polish, I deleted my personal data, but they can be easily put in, along with a photo. Details such as education or language pairs info can be changed, of course.
Remember to always sign your CV after printing it out!

# data[].attributes.headline
Translation bureaoux - recruitment requirements and procedures

# data[].attributes.subject
Translation bureaoux - recruitment requirements and procedures

# data[].attributes.body
12.06.2020
A presentation made by me as a CAT tools class assignment; may be useful in the future when applying for a job and preparing to meet different bureaux's expectations

# data[].attributes.headline
OmegaT - downloadable dictionaries online

# data[].attributes.subject
OmegaT - downloadable dictionaries online

# data[].attributes.body
12.06.2020
http://download.huzheng.org/dict.org/

# data[].attributes.body
12.06.2020
Some useful tips and tricks for quick online treasure-hunting

# data[].attributes.attachment_link.readable_text
What are Google search operators?

Google search operators are special characters and commands (sometimes called "advanced operators") that extend the capabilities of regular text searches. Search operators can be useful for everything from content research to technical SEO audits.

How do I use search operators?

You can enter search operators directly into the Google search box, just as you would a text search:

Except in special cases (such as the "in" operator), Google will return standard organic results.

Google search operators cheat sheet

You can find all of the major organic search operators below, broken up into three categories: "Basic", "Advanced", and "Unreliable". Basic search operators are operators that modify standard text searches.

Advanced search operators are special commands that modify searches and may require additional parameters (such as a domain name). Advanced operators are typically used to narrow searches and drill deeper into results.

Unreliable operators have either been found to produce inconsistent results or have been deprecated altogether. The "link:" operator was officially deprecated in early 2017. It appears that "inanchor:" operators are still in use, but return very narrow and sometimes unreliable results. Use link-based operators only for initial research.

Note that, for all of the "allin...:" operators, Google will try to apply the operator to every term following it. Combining "allin...:" operators with any other operators will almost never produce the desired results.

Search Operator Tips & Tricks

Having all of the pieces is only the first step in building a puzzle. The real power of search operators comes from combining them.

1. Chain together operator combos

You can chain together almost any combination of text searches, basic operators, and advanced operators:

"nikola tesla" intitle:"top 5..10 facts" -site:youtube.com inurl:2015

This search returns any pages that mention "Nikola Tesla" (exact-match), have the phrase "Top (X) facts" in the title, where X ranges from 5 to 10, are not on YouTube.com, and have "2015" somewhere in the URL.

2. Hunt down plagiarized content

Trying to find out if your content is unique or if someone is plagiarizing you? Use a unique phrase from your text, put it in quotes (exact-match) after an "intext:" operator, and exclude your own site with "-site:"...

intext:"they were frolicking in our entrails" -site:moz.com

Similarly, you can use "intitle:" with a long, exact-match phrase to find duplicate copies of your content.

3. Audit your HTTP->HTTPS transition

Switching a site from HTTP to HTTPS can be challenging. Double-check your progress by seeing how many of each type of page Google has indexed. Use the "site:" operator on your root domain and then exclude HTTPS pages with "-inurl:"...

site:moz.com -inurl:https

This will help you track down any stragglers or find pages that might not have been re-crawled by Google.

These are just a few examples of a nearly infinite set of combinations. Looking for more examples? You're in luck! We've created a mega-list of 67 examples to catapult you toward site operator mastery.

# data[].attributes.attachment_link.description
Google search operators are special characters and commands (sometimes called "advanced operators") that extend the capabilities of regular text searches. Search operators can be useful for everything from content research to technical SEO audits. How do I use search operators?

# data[].attributes.body
10.06.2020

1. Copy your dictionary files

2. go to the project Dictionaries folder (Drive:C -> Users -> Your account -> AppData -> Roaming -> OmegaT -> spelling)

3. paste your dictionary files

4. change their names into, e.g. 'pl' if they are Polish dictionaries (the name needs to match the abbreviation of the target language in OmegaT)

5. go back to OmegaT

6. Options -> Preferences -> Spellchecker

7. check 'Automatically check the spelling of text'

8. 'Browse' -> find the spelling folder where you pasted your dictionary files -> 'Open'

# data[].attributes.body
10.06.2020
To change/set up the user name:

1. Options -> Preferences -> Team

2. Change/Put in your name

3. Refresh by pressing f5

# data[].attributes.body
10.06.2020
If you want to use tabulators to navigate between the segments:

1. Options -> Preferences -> General

2. Tick "Use TAB to Advance"

# data[].attributes.body
10.06.2020

1. Tools -> Statistics

2. 'Copy All Data to Clipboard

or

1. Tools -> Match Statistics - this informs you about how many similarities there are between the segments in your translation/the current project and the TM

or

1. Tools -> Match Statistics per File - this gives you the same stats (match rates) for each file in the project and all files alltogether

# data[].attributes.body
10.06.2020
To quickly preview the TT:

1. CTRL + L

2. right-click

3. Open Target File

# data[].attributes.body
08.06.2020
You can confirm segments as the Translator, Reviewer 1 or Reviewer 2 (Revisor Proper).
In order to change your status, go to

1. Project Home

2. Settings

3. to the right from the User name, there is a 'Confirm using status' option with a box that lets you choose whar role you want to play at the given stage of the translation process.

When a bilingual file is exported, the "confirmation status" column informs you who confirmed which segments.

# data[].attributes.body
08.06.2020
It is possible to change QA settings. To do so:

1. Open a project

2. in Project Home, go to Settings

3. click the third icon from the left (with a little orange exclamation mark and green tick)

4. copy the default settings

5. 'Edit' the copy to your liking

# data[].attributes.body
08.06.2020
It is possible to change the way the source text is split into segments.

1. Open a project

2. in Project Home, go to Settings

3. click the second icon from the left (little scissors)

4. copy the default settings

5. 'Edit' the copy as you wish, e.g. you can change what signs the program should consider segment ends.

# data[].attributes.body
06.06.2020
YouAlign is a Software as a Service. You do not need to download the software, but you perform alignment online.
Over 100 file formats are supported.
Maximum file size for each file is 1 MB. For larger files you can use AlignFactory app, which has to be paid for.

1. go to youalign.com

2. create an account

3. when you log in, you are taken to the YouAlign interface

4. set the language pair

5. use the BROWSE buttons to upload your source and target texts

6. you can decide about segment filtering criteria (optional, rather useful)

7. hit ALIGN NOW

8. once the software processes the files, you can view the product and save it by clicking TXT FORMAT or LOGITERM (HTML) FORMAT button on the top of the table.

limitations:

file size limited (1 MB per file)

number of alignments per day limited (5 per day)

no Split, Join, Delete options that would allow you to manipulate the outcome of the alignment

# data[].attributes.body
06.06.2020
When you download the app from the web, it comes in a ZIP folder. Once you unzip it, you can launch the app by choosing either the .bat or .jar format file.
Before you start the alignment, make sure that your files are in the format supported by Bitext2tmx, i.e. the .txt format with the UTF-8 text encoding.

1. from the text menu select FILE -> OPEN

2. set the language pair (the choice of languages is far more limited than in standard CAT tools, national variations of languages are also unavailable)

3. use the BROWSE buttons to upload your source and target texts

4. hit OK

5. the program aligns segments with one another, but mistakes are very common, you need to play about with them, cut links and join segments manually

6. once all segments are aligned properly, go to FILE -> SAVE AS

All in all, this app is very limited in many aspects

it has very few options and features

a short language list without national variations

it only supports the .txt format

the quality of the alignment performed by the app is often rather poor, you need to play about with them, split segments, cut links and join segments manually

# data[].attributes.body
05.06.2020
OmegaT does not support .doc format - only .docx, so remember to save your files in .docx format before attempting to align them.

1. in OmegaT text menu go to TOOLS -> ALIGN FILES

2. set up the language pair

3. use the BROWSE buttons to upload the source and target files

4. hit OK

5. the program will process the files and a box with the segments aligned will appear

6. hit CONTINUE in the bottom right corner, then hit SAVE TMX

# data[].attributes.body
01.06.2020

RTF - Rich Text Format; most word processors are able to read and write some versions of this format

HTML - Hypertext Markup Language; the standard markup language for documents designed to be displayed in a web browser

XLIFF - XML Localization Interchange File Format; a common format for CAT tool exchange

XML - Extensible Markup Language; a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable

TMX - Translation Memory eXchange; an XML specification for the exchange of translation memory data between computer-aided translation and localization tools with little or no loss of critical data

DOC - a filename extension for word processing documents, most commonly in the proprietary Microsoft Word Binary File Format

DOCX - Office Open XML; a zipped, XML-based file format developed by Microsoft for representing spreadsheets, charts, presentations and word processing documents

# data[].attributes.body
30.05.2020

1. in the text menu go to DOCUMENTS -> EXPORT

2. it is recommended to choose the 'Export (Choose Path)'

3. a dialogue box opens up, in which you can decide where exactly you want to save the document

4. click OK

5. choose the folder you want to store your file in

6. label the document as TT

7. click OK

8. the document will ba saved and it will also open up automatically for you to view it.

You can also export your product as a bilingual file. You can choose between the MemoQ XLIFF format and Trados DOC/RTF format or a bilingual RTF table

# data[].attributes.body
30.05.2020
go to

1. general settings -> default resources -> 4th icon from the right

2. here you get settings for different languages, when you double-click on them, you get an alphabetical list of the resources, which are online dictionaries, encyclopedias or fora

3. you can select resurces by putting a tick into the little boxes to the left from the names of the resources

4. anytime you select a resource, it is automatically moved up to the top of the list

5. once you've selected all the resources you wanted, click OK and OK again

6. in the tab with the document you're currently translating, highlight the word or phrase you want to check in the resources

7. in the text menu go to REVIEW -> MEMOQ WEB SEARCH

8. the program will open up a box with tabs with all the resources you've selected and look up the word or phrase for you

9. from there you can further manipulate the search settings, select or deactivate resources

Adding a new resource to the list:

1. open the resource main page in your browser

2. look up any random word

3. copy the address

4. go back to MemoQ

5. access the web resources list

6. click 'Add new'

7. name the resource

8. paste the URL into the 'Search URL' box

9. replace the word that you've originally looked up on the website with two curvy braces: {} called 'place holders' - they will be always replaced by the program with a word we want to look up in the web resources.

10. hit OK

# data[].attributes.body
30.05.2020

1. in text menu, PREPARATION -> QUALITY ASSURANCE

2. you can either run QA for the whole project of just for the active document

3. a separate tab called 'Resolve errors and warnings' will open up, with a preview of the segment pair where an error occured and a describtion of the problem

4. you can ignore problems by ticking Ignore boxes on the left-hand side

5. graphic indicators on the very right stand for either warnings (lightning sign) or errors (exclamation mark)

# data[].attributes.body
30.05.2020
To produce a quote for a client or simply see how much works awaits you, you run statistics.

1. In text menu, choose DOCUMENTS -> STATISTICS

2. a box will appear, where you can choose your settings, e.g. you can run statistics for the whole project, only for the documents that are currently open, or for selected documents. You can also choose how you want the words to be counted - either according to MemoQ criteria or TRADOS 2007 criteria.

3. click 'Calculate' button

4. the statistics will be displayed below the settings box

5. you can export it by selecting 'Export' button, right below the 'Calculate' button - export into either HTML or CSV format

# data[].attributes.body
30.05.2020
this is the section where we can store documents, reference texts, anything that can be used in real time during the project work, e.g. for reference purposes. We can either put a text here that we want the computer to search through when we're looking for either examplary sentences or examples of language usage, or translations of terminology. We can treat all LiveDocs as large corpus that we can make use of.

# data[].attributes.body
30.05.2020
Alignment is usually performed within a project. What is important is that the project contains a translation memory, because texts that are aligned, segments are aligned, and when they are aligned by the program automatically, at the end of the day, what is produced is a translation memory., so in fact, the product of alignment is usually exported into an existing TM. Thus, to perform alignment you need to have a project up and running, with already existing TM that has been activated (the little tick on the left-hand side in TMs tab in Project Home).
go to

1. LiveDocs

2. create an empty corpus ('Create/Use New' in the top left corner in the text menu)

3. right-click in the empty white box below the corpora list

4. select 'Add alignment pair'

5. add source documents

6. add target documents

7. if you're adding more than one pair of documents, make sure that documents from each pair sit in the same line. If they are not, and they are not connected with a blue line, click 'Link documents'

8. click OK

9. double click on the product of the pre-alignment to open it

10. you will see that segments are connected with green lines, but it often happens that segments are not aligned entirely correctly.

11. Click 'Remove all Auto Links' - the lines will dissappear.

12. Now you need to create a backbone of the alignment to help the program align the segments properly.

13. click a segment on the left and the corresponding segment on the right.

1.  If they sit exatly opposite each other, click 'Create Synchro Link' button in the top left corner of the text menu.

2. If they are not exatly opposite each other, click 'Create Cross Link,' which can be found right beside the previous one.

14. Do this for every n-th pair in the document, depending on the lenght of the document. If it is relatively short, you can do it for every 10th segment pair.

15. Click 'Run Aligner' (or CTRL+SHIFT+R)

16. check if everything is correct

17. click 'Confirm all auto links'

18. select the ex-cross link paris and click 'Create synchro link'

19. once all links are confirmed, select EXPORT TO TM to export it to the existing project TM. The program already preselects the TM that is already active for the current project.

20. click OK

# data[].attributes.body
21.05.2020

1. VIEW -> 'On-the-fly spelling'

2. every word that is misspelled will be underlined with red colour

3. right-click on underlined words to see prompts for corrections

or

1. TRANSLATION -> 'Spelling/Grammar'

2. A box will appear, in which, after a bit of loading and processing, all errors that the program found will be displayed.

1. The box shows you the whole segment, in which an error occurs, with the error spelled out red. It also gives you the number of the segment and, sometimes, a sugestion on how to correct it.

2. You can either accept the suggestion by hitting 'Correct' or ignore the error by clicking 'Skip.'

# data[].attributes.body
21.05.2020
OPTIONS -> the last icon on the right is called MT SETTINGS
You can edit it
GoogleMT is available but you need to pay for it, or rather - it is available for free but only for a limited number of characters and once you exhaust it, you need to pay to get more

# data[].attributes.body
21.05.2020

to activate tag insertion: click F6 or TAG INSERION button in the QUICK ACCESS tab

to insert tags: click where you want to insert a tag , then

click 'Copy Next Tag Sequence' button

or, left click, which insert only one tag at a time

or, simply F9, which insert a whole sentence

remember to deactivate TAG INSERTION before moving on to a next operation

# data[].attributes.body
21.05.2020
go to

1. OPTIONS

2. From the left-hand menu select TERMINOLOGY PLUGINS

3. Only EuroTermBank plugin works for free. Check the 'Enable plugin' box to activate this plugin.

4. When you click 'Options' for the plugin, you can choose whether you want only exact matches to be displayed or any match above a treshold that you can set.

5. REMEMBER to check the box at the top that says: 'Perform terminology plugin lookups while working in the translation grid.' If you forget to do this, even if you enable the plugin, the results from the plugin will not work.

6. click APPLY

TLTR: there are 2 boxes that need to be checked for a plugin to work!!

# data[].attributes.body
21.05.2020
go to

1. OPTIONS

2. MISCALLANEOUS

3. the LANGUAGES tab

4. now you have to options

1. 'Show recently used languages' - this will automatically select the languages you use the most often. You can set the number of the languages to be regarded as preferred.

2. You can choose your preferred languages manually.

5. REMEMBER to check the top box that says 'Show preferred languages at the top of language lists' - otherwise the settings will be saved but yu will not see the languages where you need them.

# data[].attributes.body
21.05.2020
go to:

1. PREPARATION tab

2. select PRE-TRANSLATE

3. Under 'Lookup' you can select what matches you want, e.g. exact or good TM or corpus matches

4. You can also select what TMs will be searched through; usually it is already preselected by the program, which chooses the TM that has been activated for the current project

5. hit OK and the program will pre-translate the text for you

Remember that pre-translation is only the first step to producing a good traslation. The text still needs to be post-edited.
If you choose to run pre-translation after having already translated some segments, remember that whatwver you've translated will be changed in the pre-translation process. If you want some segments to remain intact, LOCK THEM by double-clicking on the red cross to the right from the segment pair!

# data[].attributes.body
17.05.2020
go to

1. OPTIONS (the main settings for the whole program)

2. the 4th icon from the left

3. the default settings are not meant to be edited, so you need to clone them by right-clicking on the 'Default' word in the 'Name' column and choosing 'Clone'

1. you can do it also by double-clicking the Default word - the program will ask you whether you want to clone it since this one cannot be edited

2. or, you can select the Default one and click 'Clone' on the bottom of the box

4. Once you have a copy of the default settings, right-click on it and choose 'Edit'

5. Now you can change e.g. the match tresholds.

# data[].attributes.body
17.05.2020
There are many ways to do this:

1. Highlight the word that you want to add a definition to in the source text segment.

2. Right-click on it.

3. Choose the 'Add Term' option

or

1. highlight the word

2. press CTRL+E

or

1. highlight the word

2. go to TRANSLATIONS tab

3. click "Add term'

either way, once you do it, a box will appear where you can set all the details about the term, i.e. defiition, gender, usage etc.
REMEMBER: when you add the term's equivalent, ALWAYS click the little green plus sign!! Otherwise it will not be added to your term base.

You can edit the term details at any point. To do so

1. select the term in the prompt pane

2. below, where all the details of the term are displayed, in the top right corner, click on the little pencil (when the cursor hovers over it, a pop-up says 'Edit term')

# data[].attributes.body
17.05.2020
The red X to the right from a segment means that the segment has not been confirmed yet. To confirm it, press CTRL + ENTER - the match rate field will turn green and the red X will turn into a green tick.
You lock segments by double-clicking on the green tick - it will turn into a padlock sign. You may unlock segments bu double-clicking on the little padlock. "Locked" means 'protected from any further changes.' If you now use the pre-translation option, the locked segments will remain intact.
It is possible to confirm many segment at once. To do so, click on the number of the first segment you want cofirmed, press SHIFT and use the down arrow to select as many segments as you need. You can now confirm them all by clicking the CONFIRM button under the QUICK ACCESS tab in the text menu. You can even choose to confirm as a translator or reviewer.
Under PREPARATION tab there is a LOCK/UNLOCK option and CHANGE SEGMENT STATUS option, which allows you to mark segments as 'not started/edited/pre-translated.'

# data[].attributes.body
16.05.2020

~65-95% - fuzzy match, segments are similar but not identical

100% - exact match, means that the segments are perfectly identical

101% - context match, means that not only the two segments are identical, but also the segments before or after them

# data[].attributes.body
16.05.2020
When you want to import a TM to your program, you first need to create an empty TM, which you do by going to:

1. PROJECT HOME

2. TRANSLATION MEMORIES

3. right-click on the list and choose "Create/Use New"

If you already have an empty TM, go to:

1. PROJECT HOME

2. TRANSLATION MEMORIES

3. right-click on the empty TM

4. choose "Import from TMX/CSV"

5. choose the TM from your disc

6. confirm

7. wait for the program to load and process everything

Your TM is ready.
When you add a TM to your resources, a new file is created, which gives you a summary of the import operation.

# data[].attributes.body
16.05.2020
When you open a translation pane, below the segments you have a preview of what the target text is going to look like (you need to choose the HTML preview option). On the right-hand side prompts are being displayed. The box displays prompts from the translation memory, but also the term base and your machine translation. Below there are details of the prompt selected, i.e. the subject it belongs to, defnition etc.

To insert prompt 1: press CTRL + 1

To manipulate many segments at the same time, click on the number of the first segment you want to change and press SHIFT, then use the down arrow to select as many segments as you need. You can now manipulate them as you want, e.g. confirm all of them immediately.

# data[].attributes.body
16.05.2020
The PROJECT HOME panel is only for the current project settings.
Here you can access SETTINGS, where there are many scroll-down options, e.g.

name and location - so that you can check where the project files can be found on your disc

languages

user and meta-information - here you can change the user name, deadline or the role the user plays when cofirming segments (e.g. translator, reviser etc.)

document versioning - where you can state whether you want the document version history recorded or not.

In PROJECT HOME you can also access TERM BASES and TRANSLATION MEMORIES tabs, in which you can check what TBs and TMs have been enabled and change it if necessary.
Under TRANSLATION you have the source text files that need to be translated - to start translating you either double-click a chosen file or right-click and choose "Open for Translation."

# data[].attributes.body
16.05.2020
It is recommended not to click on the main top NEW PROJECT button, because when you do that, you create a new project from a template, which is provided by Kilgray (the program provider).
You'd rather want to start a completely new project and decide yourself about all its settings. To do this

1. click the NEW PROJECT button below

2. a box will appear, where you can set the name of the new project, the language pair and a few more details like client, domain etc.

3. hit NEXT

4. import your source text by clicking IMPORT choosing the file you want from your disc

5. the program needs to process the file - at this moment it does several things:

converts the file into an XTLM file for preview purposes

converts it into an XLIFF file (the bilingual format, which on the left-hand side displays the text in the source language and the target text on the right-hand side)

6. once you have successfuly imported all the source text files, hit NEXT

7. now you can select all translation memories you want to use while translating

8. you can also create a new translation memory by clicking CREATE/USE NEW

9. set the details of your new TM and 'Confirm'

10. IMPORTANT: you need to tick the little box left from the name of the TM chosen - a little black tick, not the green one a bit to the right, which only means that a TM is available; the black tick means a TM has been enabled

11. once you have enabled all the TMs you wanted, hit NEXT

12. now you can select a term base or create a new one (to do so, repeat the same procedure as with the TMs) (you don't need to select the languages, they're already selected by default)

13. hit FINISH

14. the program needs to process all the files and data provided and opens a new project tab called PROJECT HOME, which is the main menu, i.e. the control panel for the whole project and project files.

The new project is ready!

# data[].attributes.body
16.05.2020
There are two tabs at the top left corner:

Project - here you work on your current project

memoQ - main program menu, in which you can e.g. consult your serial number or check for updates, or access Options, where you can change many general program settings, which are not for any particular project, but for the entire program.

You can also access the Options box by clicking on the little wheels button in the top left corner, right next to the Help button.

To navigate between the segments use up/down arrows or do it by left-clicking.

press CTRL for prompts

# data[].attributes.body
07.05.2020
ST formatting is preserved in OmegaT in the form of tags. Tag preservation is essential for the program to generate a TT formatted exactly like the ST.

To insert a tag

1. Place the cursor where the tag is missing

or

1. highlight the whole word (or phrase) that is supposed to be located between two (still missing) tags

2. hit CTRL + SPACE twice

3. click the tag you want inserted

Caution! - always check if unnecessary spaces have not been inserted with the tags - OmegaT often does that and the spaces need to be deleted manually!

# data[].attributes.body
07.05.2020

CTRL + S - saves the changes made in the project

CTRL + D - creates the TT file (which will appear in your 'target' folder, with the same name as the ST file, so change the name of the TT file immediately to avoid any confusion later)

Caution! Always open the TT after you're done (or so you think). Sometimes a word 'fuzzy' appears in square brackets. You need to open the project in OmegaT again and delete those inserted "[fuzzies]". Next, save the project once again, generate the TT and remember to change the name of the file once more!

# data[].attributes.body
07.05.2020
To make a note: activate the segment you want to make a note to, click on the Notes pane and write your note. Once you add a note, the segment will be highlighted in blue colour, provided you checked "Mark segments with notes" in VIEW.

PS.: There are other colours meant to inform you about other issues, so do not be afraid to explore the VIEW options and customize them to your liking!

# data[].attributes.body
07.05.2020
If you want the information about who modified a segment and at what time, to be displayed, go to: VIEW -> MODIFICATION INFO -> check "Display for all segmets" or "Display for current segment."

# data[].attributes.body
07.05.2020

1. Copy your dictionary files into the project Dictionaries folder (Drive:C -> Users -> Your account -> AppData -> Roaming -> OmegaT -> Dictionaries)

2. press F5 to reload the project. You should see the dictionary content in the Dictionary pane.

When you highlight a word in the source text, the Dictionary pane will display that word's definition, provided it features in the dictionary you uploaded.
However, the dictionary does not recognize words if they're not in their most basic form, i.e. it will recognize "work" but not "working" or "works." Highlighting only the root of the word does not help.

# data[].attributes.body
07.05.2020
In order to add an entry to your glossary, highlight the word you want to add, right-click and choose "Add Glossary Entry" OR, an even more simple way: press CTRL + SHIFT + G. You can add a target language equivalent and additional info like definition or how the term is used in a sentence.
The glossary file is in a simple .txt format and can be viewed in a simple NotePad. Once you add the first entry, a glossary is created and you can find it in the project Glossaries folder. You can also add new entries directly in the file. The source language word, the target language word, and the additional info need to be separated with single tabulators from one another.
In order to insert a prompt from the glossary press CTRL + SPACE - a box with prompts will appear (provided the glossary is not empty) - choose the prompt you like and click ENTER or double-click on the prompt.

# data[].attributes.body
07.05.2020

1. Important: if you want (and you probably do) to get MT prompts automatically, go to OPTIONS -> MACHINE TRANSLATION and tick both "Automatically Fetch Translations" and "MyMemory".

2. If you have a TM that could help you in your translation, you need to add it to a proper project folder in order to get prompts based on it:

1. Go to PROJECT -> ACCESS PROJECT CONTENTS -> TMS

2. Copy your TM into the project TMs folder

3. Press F5 to reload

4. You should be getting TM prompts now.

3. Key combinations for TM prompts manipulation:

CTRL +1 / +2 – choosing between fuzzy matches OR you can use UP/DOWN arrows

CTRL + R - replaces the content of a TT segment with a prompt from Translation Memory

CTRL + I - inserts a chosen prompt from Translation memory

You can also access the project TM folder by pressing CTRL + E, which opens up the box with the info about the location of all project folders. There you can see the location of your project TM folder (called 'tm'), so that you are able to trace the path and find the folder on your disc on your own. This, however, takes more time than the way described above, so I do not recommend this one.

# data[].attributes.body
06.05.2020
When you're finished with translating a segment and hit ENTER, a lot happens immediately and at the same time even though you do not neccesarily see it:

OmegaT adds the translated pair (source and target sentence/phrase) to your Translation Memory

inserts your translation into all identical TT segments

searches through the Translation Memory and the glossary for prompts for the next untranslated segment.

# data[].attributes.body
06.05.2020
If you cannot see the 'Dictionary,' 'Multiple Translations' etc. panes, go to: VIEW -> RESTORE MAIN WINDOW, and all the panes should appear.

# data[].attributes.body
06.05.2020
In order to check if you've translated all segments press CTRL + U. This key combination is supposed to take you to the next untranslated segment - if you press it and nothing happens, it means that all segments are translated.

# data[].attributes.body
06.05.2020
if you ever forget a shortcut key combination, check Edit or Go To options in the OmegaT text menu - the key combinations are to the right

# data[].attributes.body
06.05.2020

1. on the list of your installed programs, find OmegaT

2. right-click

3. 'Open file location'

4. find 'OmegaT.I4J. ini' file (if you cannot see it, go to View and check 'File name extensions')

5. right-click -> Edit

6. find the line that says "language:[pl]' (the brackets are not there, I used them here to show that it is an example and it can say 'it' or 'ru' etc. as well)

7. change the language to whatever you need, e.g. en

8. Save

9. Refresh OmegaT (f5)

# data[].attributes.body
06.05.2020

CTRL + M – inserts a Machine Translation prompt

CTRL + J – allows you to activate a chosen segment (after pressing the ctrl + J combination you need to press the letter assigned to that segment)

F5 - reloads OmegaT; the project files box opens up

CTRL + U – next untranslated segment (this is an easy way to check if the whole text has been translated - if the shortcut does not take you anywhere, it means there are no more untranslated segments)

CTRL + Shift + U – next translated segment

CTRL + N – next segment (doesn't matter whether it is translated or not)

CTRL + P – previous segment

CTRL + Shift + Q – next unique segment

CTRL + Shift + M – Source of Selected Match

CTRL + O – to open an already existing project

CTRL + S - saves the changes made in the project

CTRL + D - creates the TT file (which will appear in your 'target' folder, with the same name as the ST file, so change the name of the TT file immediately to avoid any confusion later)

CTRL + Q – quit

CTRL + Shift + G – creates a glossary entry

CTRL + K - search and replace

CTRL + UP/DOWN arrow – choose between prompts from the TM

CTRL + E - opens up the Edit (or Properties) window that allows you to edit properties such as source and target language - the one that you see when creating a new project

CTRL + L – opens up the project files box

CTRL + Z - undo

CTRL + Y - do again (what you've just undone)

CTRL + 1/ +2 – to choose between fuzzy matches OR use UP/DOWN arrows

CTRL + R - replaces the content of a TT segment with a prompt from Translation Memory

CTRL + I - inserts a chosen prompt from Translation memory

CTRL + Shift + W – closes the project

# data[].attributes.body
23.04.2020
It is possible to use machine translation with Memsource Translate or by setting up direct connections with Third-party MT engines. Memsource supports over 20 machine translation engines, e.g.

Amazon Translate

DeepL Pro

Google AutoML

Google Translate

Microsoft Custom Translator

Microsoft Translator / Microsoft Translator Hub

SDL BeGlobal

SDL Language Cloud

Yandex.

They can be customized to use your terms and learn from your inputs. You can even pick different machine translation providers for different language combinations.

# data[].attributes.body
21.04.2020
OmegaT has a limit of characters in a query that can be translated with the help of MT: 500 characters is the maximum per day.
It is good to know this before starting a new project and changing the default segmentation setting from sentence to paragraph level. I was not aware of the character limitation and used to prefer to see the ST in whole paragraphs, but now it turns out that if a paragaph is longer than 500 characters (which in reality is not that much), MT will not give you any prompts. This is very impractical and makes me very unhappy, but it seems like this cannot be helped (it can, but you need to pay for that).

# data[].attributes.body
20.04.2020
For some reason, when I downloaded my translation from the Cloud as a Word document, tags did not work as they should have. Instead of appearing as formating, they were just signs and numbers that I had to delete manually. I ended up doing the formating from scratch by myself.
So far I have not been able to find a solution to that and my only conslusion is that inserting tags in Memsource Cloud, automatically or manually, does not pay off, as we have to remove them later anyway... This is of course a highly pessimistic conclusion and I'll keep on looking for another way to go about it.

# data[].attributes.body
20.04.2020
When you press F8, Memsource automatically inserts the next tag in a row.
However, sometimes the source text is ill-formated or the word order in your translation is different than that in the ST (this happens very often), and thus you might at times want to tinker with tags, so that they are not inserted in the same order as in the ST.

To insert the exact tag you need:

1. highlight the portion of your translation that needs to be formated

2. from the text menu, choose "Edit"

3. expand the "Tags" edit options

4. there you have a few options to choose from:

"Insert Tag Number"

allows you to choose any of the tags available in the given document

"Insert Tag by Selection"

"Insert All Tags"

I do not recommend this one - it is very inexact and makes lots of mess, as it inserts tags wherever the machine thinks they should be and you have no control over it.

# data[].attributes.body
18.04.2020
VERY IMPORTANT
In order to calculate the price of a job:

1. open up the project the job is a part of

2. choose the job you're interested in

3. click "Analyse."

4. This opens up a window with a list of options, which you can choose as you wish.

5. On the bottom of the window you need to choose which text you want analysed - source or target. Once you're done with that,

6. click "Analyze" button, which will take you to a table with all the necessary statistics such as the number of characters, words, pages, segmets etc.

7. you can download it as an Excel file

8. the format looks messy at first, but you can deal with that in the following way:

1. pick the boxes with your statistics and highlight them as one entity

2. go to "Data"

3. click "Text to columns"

4. Change the settings so that your text is delimited by semicolons and tabulators

5. Done! Your statistics are now nicely divided into sections, clear and comprehensible.

# data[].attributes.body
15.04.2020
before you start translating, first you want to always check three little boxes in the top right corner - they should all be green! If any of those is red, it's a signal for you that you're missing some of the necessary translation resources, e.g. your TM might have not loaded correctly. If that is the case, fix it and check the little boxes again. Only if they are all green should you start translating!

# data[].attributes.body
15.04.2020
In Memosource, when working on a project, you can either select a TM you have already uploaded and worked with on the platform, or upload a new one. To do the latter, you need to click "Create New" and once a new page opens up, give your new TM a name and click "Import". Thus you will open a window like the one featured in the picture attached. Click "Browse" (in my case it says "Wybierz plik", which is in Polish, I'm not sure why since all other text and instructions on the website are in English). Next, choose the TM from your computer that you want to upload and you're good to go.
I especially appreciate the additional options Memsource offers below the "Browse" box. Non of them is checked by default, which is great, since you really don't want to remove tags by accident.. But when you do want them gone, Memsource makes it sooo easy for you!

# data[].attributes.body
10.04.2020
Having experimented with translating heavily tagged texts, I now understand the purpose of the default setting in OmegaT to paste the source text into the target text segment automatically. I believe that this setting is to make translation more convenient when we work on a heavily formated text - it is easier to retain the tags in the right place and undamaged by simply replacing the source text between them with our translations. If we change the setting, we have to be very careful as to what portions of the segment being translated belong between which tags - there is a high risk of misplacing something (or even completely deleting a tag!) and thus deforming the target text!

# data[].attributes.body
03.04.2020
What is very confusing to me is that the default setting in OmegaT is to duplicate the source text into the segment that is not translated yet. It is very disorienting for me to type over the source text. I discovered that you can change this setting in the following way:

0) Open the project you want to work on in OmegaT.

1) From the OmegaT text menu choose "Options", then "Editor..."

2) In the box that will open, you will see "Insert the source text" checked by default.

3) You want to check the option that says "Leave the segment empty".
Aaand... DONE! No more confusion and you can simply type in you translation :)