diff --git a/_includes/omt-inst-verif-macos/index.html b/_includes/omt-inst-verif-macos/index.html index fe410cb3..b44a5a0f 100644 --- a/_includes/omt-inst-verif-macos/index.html +++ b/_includes/omt-inst-verif-macos/index.html @@ -2320,7 +2320,7 @@

Installation

  • Click on the button below to download OmegaT 5.7.2. This is a custom version prepared by cApStAn which includes several bug fixes and enhancements not available in other versions.

    -

    Download OmegaT 5.7.2

    +

    Download OmegaT 5.7.2

  • If you're using Safari, then the file will be unzipped automatically when the download ends.​ If you use another browser, double-click the file when the download ends to unzip it.

    diff --git a/_includes/omt-inst-verif/index.html b/_includes/omt-inst-verif/index.html index cb7769b1..c442b6c3 100644 --- a/_includes/omt-inst-verif/index.html +++ b/_includes/omt-inst-verif/index.html @@ -2288,7 +2288,7 @@

    ConfigurationRun OmegaT and go to Tools > Scripting to open your scripting console, In OmegaT 5.7.1, please open the scripting console. Check whethers you have a script called "Update Customisation Bundle (v572)":

    Warning

    -

    If you don't see the "v752" bit, then it's not the script we're looking for. See next step to fetch the script.

    +

    If you don't see the "v572" bit, then it's not the script we're looking for. See next step to fetch the script.

    If the script "Update Customisation Bundle (v572)" is there, please click on it to select it and press the Run button (at the bottom left) to run it. The script will run to update your config files and will quit OmegaT. After that, skip the next step and jump directly to the installation section.

    diff --git a/search/search_index.json b/search/search_index.json index 23501aac..3f60f255 100644 --- a/search/search_index.json +++ b/search/search_index.json @@ -1 +1 @@ -{"config": {"indexing": "full", "lang": ["en"], "min_search_length": 3, "prebuild_index": false, "separator": "[\\s\\-]+"}, "docs": [{"location": "", "text": "OmegaT guides \u00b6 Welcome to cApStAn's OmegaT guides. A guide for each task \u00b6 Translation Reconciliation Adaptation Verification Review Other stuff \u00b6 Videos Exercises Miscellanea", "title": "Contents"}, {"location": "#omegat-guides", "text": "Welcome to cApStAn's OmegaT guides.", "title": "OmegaT guides"}, {"location": "#a-guide-for-each-task", "text": "Translation Reconciliation Adaptation Verification Review", "title": "A guide for each task"}, {"location": "#other-stuff", "text": "Videos Exercises Miscellanea", "title": "Other stuff"}, {"location": "adaptation/", "tags": ["Adaptation"], "text": "a.md-footer__link--prev[aria-label^=\"Previous:\"], .md-nav__icon { display: none !important; } \ud83d\udc4b Welcome to the OmegaT adaptation guide! \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "Adaptation"}, {"location": "adaptation/#welcome-to-the-omegat-adaptation-guide", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "\ud83d\udc4b Welcome to the OmegaT adaptation guide!"}, {"location": "adaptation/accessing-the-project/", "text": "Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Accessing a project"}, {"location": "adaptation/accessing-the-project/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "adaptation/accessing-the-project/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "adaptation/accessing-the-project/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "adaptation/accessing-the-project/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "adaptation/accessing-the-project/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "adaptation/accessing-the-project/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "adaptation/creating-target-files/", "text": "Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "adaptation/creating-target-files/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "adaptation/creating-your-deliverable/", "text": "Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Creating your deliverable"}, {"location": "adaptation/creating-your-deliverable/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "adaptation/creating-your-deliverable/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "adaptation/creating-your-deliverable/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "adaptation/glossary/", "text": "Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Glossary"}, {"location": "adaptation/glossary/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "adaptation/glossary/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "adaptation/glossary/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "adaptation/install-and-setup/", "text": "Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "adaptation/install-and-setup/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "adaptation/matches/", "text": "Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "adaptation/matches/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "adaptation/navigation/", "text": "Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation"}, {"location": "adaptation/navigation/#navigation", "text": "", "title": "Navigation"}, {"location": "adaptation/navigation/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "adaptation/navigation/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "adaptation/navigation/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "adaptation/other-useful-features/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Other useful features"}, {"location": "adaptation/other-useful-features/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "adaptation/other-useful-features/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "adaptation/other-useful-features/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "adaptation/other-useful-features/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "adaptation/qa-checks/", "text": "QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "QA checks"}, {"location": "adaptation/qa-checks/#qa-checks", "text": "", "title": "QA checks"}, {"location": "adaptation/qa-checks/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "adaptation/qa-checks/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "adaptation/qa-checks/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "adaptation/repetitions/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Repetitions"}, {"location": "adaptation/repetitions/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "adaptation/repetitions/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "adaptation/repetitions/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "adaptation/repetitions/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "adaptation/shortcuts/", "text": "a.md-footer__link--next[aria-label^=\"Next:\"], .md-nav__icon { display: none !important; } OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "adaptation/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "adaptation/tags/", "text": "Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Tags"}, {"location": "adaptation/tags/#tags", "text": "", "title": "Tags"}, {"location": "adaptation/tags/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "adaptation/tags/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "adaptation/tags/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "editing/", "tags": ["Verification", "Proofreading", "Adaptation", "Review", "Revision", "Review"], "text": "a.md-footer__link--prev[aria-label^=\"Previous:\"], .md-nav__icon { display: none !important; } \ud83d\udc4b Welcome to the OmegaT verification guide! \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "Editing"}, {"location": "editing/#welcome-to-the-omegat-verification-guide", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "\ud83d\udc4b Welcome to the OmegaT verification guide!"}, {"location": "editing/accessing-the-project/", "text": "Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Accessing a project"}, {"location": "editing/accessing-the-project/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "editing/accessing-the-project/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "editing/accessing-the-project/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "editing/accessing-the-project/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "editing/accessing-the-project/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "editing/accessing-the-project/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "editing/creating-target-files/", "text": "Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "editing/creating-target-files/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "editing/creating-your-deliverable/", "text": "Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Creating your deliverable"}, {"location": "editing/creating-your-deliverable/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "editing/creating-your-deliverable/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "editing/creating-your-deliverable/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "editing/glossary/", "text": "Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Glossary"}, {"location": "editing/glossary/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "editing/glossary/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "editing/glossary/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "editing/install-and-setup/", "text": "Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "editing/install-and-setup/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "editing/matches/", "text": "Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "editing/matches/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "editing/navigation/", "text": "Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation"}, {"location": "editing/navigation/#navigation", "text": "", "title": "Navigation"}, {"location": "editing/navigation/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "editing/navigation/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "editing/navigation/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "editing/other-useful-features/", "text": "Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Other useful features"}, {"location": "editing/other-useful-features/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "editing/other-useful-features/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "editing/other-useful-features/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "editing/other-useful-features/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "editing/other-useful-features/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "editing/other-useful-features/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "editing/other-useful-features/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "editing/qa-checks/", "text": "QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "QA checks"}, {"location": "editing/qa-checks/#qa-checks", "text": "", "title": "QA checks"}, {"location": "editing/qa-checks/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "editing/qa-checks/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "editing/qa-checks/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "editing/repetitions/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Repetitions"}, {"location": "editing/repetitions/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "editing/repetitions/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "editing/repetitions/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "editing/repetitions/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "editing/shortcuts/", "text": "a.md-footer__link--next[aria-label^=\"Next:\"], .md-nav__icon { display: none !important; } OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "editing/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "editing/tags/", "text": "Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Tags"}, {"location": "editing/tags/#tags", "text": "", "title": "Tags"}, {"location": "editing/tags/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "editing/tags/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "editing/tags/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "exercises/", "text": "OmegaT exercises \u00b6 Getting started \u00b6 In order to do these exercises, you'll have to download an offline OmegaT project package. Get your project \u00b6 Download project package project_task_fr-ZZ_offline_omt.omt . Unpack that project from OmegaT: Project > Unpack project from OMT file... Relevant section in the OmegaT guide How to unpack an offline project .", "title": "Getting started"}, {"location": "exercises/#omegat-exercises", "text": "", "title": "OmegaT exercises"}, {"location": "exercises/#getting-started", "text": "In order to do these exercises, you'll have to download an offline OmegaT project package.", "title": "Getting started"}, {"location": "exercises/#get-your-project", "text": "Download project package project_task_fr-ZZ_offline_omt.omt . Unpack that project from OmegaT: Project > Unpack project from OMT file... Relevant section in the OmegaT guide How to unpack an offline project .", "title": "Get your project"}, {"location": "exercises/alt/", "text": "06. Alternative translations \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification In the previous section you saw that translations of repeated segments (or edits in those translations) auto-propagate to all instances of that repeated segment when you save them (or leave the segment). That is convenient in many cases, but not always. Sometimes you'll have to prevent auto-propagation. To do that, you must create an alternative translation . Exercise 06.1: create alternative translation \u00b6 Go to segment #16 in the project. Source text reads: Pretty good Notice that it is translated with an auto-propagated translation. Pretty good and Pretty bad in segments #16 and #17 in this context refer to \"level of English\" which is masculine in French. However, your translations (\"Plut\u00f4t bonNE\" and \"Plut\u00f4t mauvaisE\") refers to \"situation economique\", which is feminine. You want to modify the translation in segments #16 and #17 to make it masculine, so that it agrees with \"level\" in French. Follow these three simple but VERY IMPORTANT steps: Go to Edit > Create Alternative Translation . Tip: Also available if you right-click the segment. Modify the translation to make it masculine Just remove the last character if you don't know French Press Ctrl + S to register the translation Warning This is a very important and delicate function of OmegaT. It's easy to use it correctly if you grasp well the three steps above, but it's also easy to make a mess if you don't. Please make sure you really follow the three steps above to the letter. Did you follow the steps above? If you did, now you'll notice that: your alternative translation appears now in the Multiple Translations pane, below the default translation and followed by the filename and the segment ID. the Segment Properties pane for that segment says now \"Is alternative: TRUE\" the (default) translation of segment #13 hasn't changed Press Enter to move to segment #17 and do the same steps as above. Info If you want more practice on this, go to segment #62 (source text reads: Subject: ), which is also repeated a few times. The first occurrence refers to an email subject line, whereas the other occurrences refer to the topic or subject matter field of books in a library classification system, so each of those requires a different translation, i.e. \"Objet\" vs \"Sujet\".", "title": "06 - Alternative translations"}, {"location": "exercises/alt/#06-alternative-translations", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification In the previous section you saw that translations of repeated segments (or edits in those translations) auto-propagate to all instances of that repeated segment when you save them (or leave the segment). That is convenient in many cases, but not always. Sometimes you'll have to prevent auto-propagation. To do that, you must create an alternative translation .", "title": "06. Alternative translations"}, {"location": "exercises/alt/#exercise-061-create-alternative-translation", "text": "Go to segment #16 in the project. Source text reads: Pretty good Notice that it is translated with an auto-propagated translation. Pretty good and Pretty bad in segments #16 and #17 in this context refer to \"level of English\" which is masculine in French. However, your translations (\"Plut\u00f4t bonNE\" and \"Plut\u00f4t mauvaisE\") refers to \"situation economique\", which is feminine. You want to modify the translation in segments #16 and #17 to make it masculine, so that it agrees with \"level\" in French. Follow these three simple but VERY IMPORTANT steps: Go to Edit > Create Alternative Translation . Tip: Also available if you right-click the segment. Modify the translation to make it masculine Just remove the last character if you don't know French Press Ctrl + S to register the translation Warning This is a very important and delicate function of OmegaT. It's easy to use it correctly if you grasp well the three steps above, but it's also easy to make a mess if you don't. Please make sure you really follow the three steps above to the letter. Did you follow the steps above? If you did, now you'll notice that: your alternative translation appears now in the Multiple Translations pane, below the default translation and followed by the filename and the segment ID. the Segment Properties pane for that segment says now \"Is alternative: TRUE\" the (default) translation of segment #13 hasn't changed Press Enter to move to segment #17 and do the same steps as above. Info If you want more practice on this, go to segment #62 (source text reads: Subject: ), which is also repeated a few times. The first occurrence refers to an email subject line, whereas the other occurrences refer to the topic or subject matter field of books in a library classification system, so each of those requires a different translation, i.e. \"Objet\" vs \"Sujet\".", "title": "Exercise 06.1: create alternative translation"}, {"location": "exercises/aut/", "text": "07. Special characters \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification You may insert special characters in different ways: autotext shortcut, character table, etc. Exercise 07.1: use a known autotext shortcut \u00b6 You may use the autotext shortcut \\sub2 to insert a subscript number 2 (i.e. \u2082 ). Now you know! :) Tip The \"suB\" part in the shorcut \\sub2 stands for subindex or subscript. Go to segment #72 and read the source text. Target text reads Le dioxyde de carbone (CO2) se dissout dans l'eau de mer pour former de l'acide carbonique. Delete number 2 in \u201cCO2\u201d (and keep the cursor right after \"CO\"). A subscript number should be used instead of a regular digit. In that same position, type the autotext shortcut \\sub2 Notice how the auto-completer window opens showing the autotext entry. Press Enter to insert the special character \u2082 . The result should be: CO\u2082 In this exercise you have used an autotext shortcut that you knew already. In the following exercises you'll find out an autotext entry that you don't know. Exercise 07.2: find special character in the list of autotext entries \u00b6 In this exercise, you must insert the multiplication symbol but you don't know what autotext entry you can use. Go to segment #74 Source text reads: Thermal conductivity coefficient
    (W/m \u00d7 K) Open the list of available shortcuts here . Look for the autotext entry for the multiplication symbol. You can use either \\times or \\x (how lucky, this one is shorter!) Translate segment #74 as you like (don't forget the part in parentheses). To translate the part in parenthesis, type \\x (or \\times ) between W/m and K . Notice how the auto-completer opens when you typed the autotext shortcut. Press Enter to insert the caracter. Result should be: W/m \u00d7 K Incorrect translation: W/m x K Info You can find the list of autotext entries in OmegaT guides > Miscellanea > Autotext Exercise 07.3: insert special character from the character table \u00b6 Remember the auto-completer? You used it to insert tags. You'll use it again now to insert a special character. Go to segment #75 Target text reads: \u201cLa densit\u00e9 de population est de 62 personnes par km2 en 2023.\u201d Delete number 2 in \u201ckm2\u201d (and keep your cursor right after \u201ckm\u201d). Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cCharacter table\u201d. Spot the relevant character \u00b2 and double click on it to insert it. The result should be: km\u00b2 Tip You could have inserted character \u00b2 with shortcut \\sup2 (where \"suP\" stands for superscript or superindex or superordinate). Exercise 07.4: insert special quotation marks \u00b6 French uses special quotation marks, called angle quotes or \"chevrons\". You can use autotext to insert them. Go to segment #77. Look at the translation of segment #76 and notice how the angle quotes are used there. L'eau est \u00ab satur\u00e9e \u00bb si... Translate segment #77. You can use the exact match that appears in the Matches pane. Type autotext shortcut << before \"insatur\u00e9e\" to insert character \u00ab followed by a non-breaking space. Type autotext shortcut >> after \"insatur\u00e9e\" to insert character \u00ab preceded by a non-breaking space. Expected results: \u00ab insatur\u00e9e \u00bb Remember If there's a special character that you need which you can't find in the list of autotext entries or the character table, please let us know through the Helpdesk and we'll add it for you.", "title": "07 - Special characters"}, {"location": "exercises/aut/#07-special-characters", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification You may insert special characters in different ways: autotext shortcut, character table, etc.", "title": "07. Special characters"}, {"location": "exercises/aut/#exercise-071-use-a-known-autotext-shortcut", "text": "You may use the autotext shortcut \\sub2 to insert a subscript number 2 (i.e. \u2082 ). Now you know! :) Tip The \"suB\" part in the shorcut \\sub2 stands for subindex or subscript. Go to segment #72 and read the source text. Target text reads Le dioxyde de carbone (CO2) se dissout dans l'eau de mer pour former de l'acide carbonique. Delete number 2 in \u201cCO2\u201d (and keep the cursor right after \"CO\"). A subscript number should be used instead of a regular digit. In that same position, type the autotext shortcut \\sub2 Notice how the auto-completer window opens showing the autotext entry. Press Enter to insert the special character \u2082 . The result should be: CO\u2082 In this exercise you have used an autotext shortcut that you knew already. In the following exercises you'll find out an autotext entry that you don't know.", "title": "Exercise 07.1: use a known autotext shortcut"}, {"location": "exercises/aut/#exercise-072-find-special-character-in-the-list-of-autotext-entries", "text": "In this exercise, you must insert the multiplication symbol but you don't know what autotext entry you can use. Go to segment #74 Source text reads: Thermal conductivity coefficient
    (W/m \u00d7 K) Open the list of available shortcuts here . Look for the autotext entry for the multiplication symbol. You can use either \\times or \\x (how lucky, this one is shorter!) Translate segment #74 as you like (don't forget the part in parentheses). To translate the part in parenthesis, type \\x (or \\times ) between W/m and K . Notice how the auto-completer opens when you typed the autotext shortcut. Press Enter to insert the caracter. Result should be: W/m \u00d7 K Incorrect translation: W/m x K Info You can find the list of autotext entries in OmegaT guides > Miscellanea > Autotext", "title": "Exercise 07.2: find special character in the list of autotext entries"}, {"location": "exercises/aut/#exercise-073-insert-special-character-from-the-character-table", "text": "Remember the auto-completer? You used it to insert tags. You'll use it again now to insert a special character. Go to segment #75 Target text reads: \u201cLa densit\u00e9 de population est de 62 personnes par km2 en 2023.\u201d Delete number 2 in \u201ckm2\u201d (and keep your cursor right after \u201ckm\u201d). Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cCharacter table\u201d. Spot the relevant character \u00b2 and double click on it to insert it. The result should be: km\u00b2 Tip You could have inserted character \u00b2 with shortcut \\sup2 (where \"suP\" stands for superscript or superindex or superordinate).", "title": "Exercise 07.3: insert special character from the character table"}, {"location": "exercises/aut/#exercise-074-insert-special-quotation-marks", "text": "French uses special quotation marks, called angle quotes or \"chevrons\". You can use autotext to insert them. Go to segment #77. Look at the translation of segment #76 and notice how the angle quotes are used there. L'eau est \u00ab satur\u00e9e \u00bb si... Translate segment #77. You can use the exact match that appears in the Matches pane. Type autotext shortcut << before \"insatur\u00e9e\" to insert character \u00ab followed by a non-breaking space. Type autotext shortcut >> after \"insatur\u00e9e\" to insert character \u00ab preceded by a non-breaking space. Expected results: \u00ab insatur\u00e9e \u00bb Remember If there's a special character that you need which you can't find in the list of autotext entries or the character table, please let us know through the Helpdesk and we'll add it for you.", "title": "Exercise 07.4: insert special quotation marks"}, {"location": "exercises/fnd/", "text": "08. Search \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Exercise 08.1: search for a selected expression \u00b6 Try to find the translation of \"translator\" in the translation memories. Press Ctrl + J and enter 47 to go to segment #47. Select the word translator . Press Ctrl + F to open the Text Search dialog. Notice how the word \"translator\" is already filled in in the search box. Check option \"Translated\" so that you will only find translated segments. Check box \"TMs\" under \"Search in\" to search in the translations memories. Press the Search button. Expected result: traducteur Exercise 08.2: search for a segment identifier \u00b6 You might need to refer to a certain segment by its identifier (the segment ID or key). Press Ctrl + F to open the Text Search dialog unless it's already open. Check option: In comments Type 123abc in the search box, and press Search . Expected results: 01_qq/03_qq_paq.xml -- 22> Neither good nor bad # name = 123abc Info Here # name refers to the segment identifier. Exercise 08.3: search for some source text \u00b6 One instance of the repeated segment \"Rather satisfied\" was not translated consistenly. Press Ctrl + F to open the Text Search dialog. Check options: Exact search In source All matching segments Search in: Memory Do not check options: Search in: TMs Type Rather satisfied in the search box, and press Search . Expected results: 27> Plut\u00f4t satisfait 32> Assez satisfait 37> Plut\u00f4t satisfait Notice that here is one instance of the repeated segment \"Rather satisfied\" that was not translated consistenly. Can you see which translation is inconsistent?", "title": "08 - Search"}, {"location": "exercises/fnd/#08-search", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification", "title": "08. Search"}, {"location": "exercises/fnd/#exercise-081-search-for-a-selected-expression", "text": "Try to find the translation of \"translator\" in the translation memories. Press Ctrl + J and enter 47 to go to segment #47. Select the word translator . Press Ctrl + F to open the Text Search dialog. Notice how the word \"translator\" is already filled in in the search box. Check option \"Translated\" so that you will only find translated segments. Check box \"TMs\" under \"Search in\" to search in the translations memories. Press the Search button. Expected result: traducteur", "title": "Exercise 08.1: search for a selected expression"}, {"location": "exercises/fnd/#exercise-082-search-for-a-segment-identifier", "text": "You might need to refer to a certain segment by its identifier (the segment ID or key). Press Ctrl + F to open the Text Search dialog unless it's already open. Check option: In comments Type 123abc in the search box, and press Search . Expected results: 01_qq/03_qq_paq.xml -- 22> Neither good nor bad # name = 123abc Info Here # name refers to the segment identifier.", "title": "Exercise 08.2: search for a segment identifier"}, {"location": "exercises/fnd/#exercise-083-search-for-some-source-text", "text": "One instance of the repeated segment \"Rather satisfied\" was not translated consistenly. Press Ctrl + F to open the Text Search dialog. Check options: Exact search In source All matching segments Search in: Memory Do not check options: Search in: TMs Type Rather satisfied in the search box, and press Search . Expected results: 27> Plut\u00f4t satisfait 32> Assez satisfait 37> Plut\u00f4t satisfait Notice that here is one instance of the repeated segment \"Rather satisfied\" that was not translated consistenly. Can you see which translation is inconsistent?", "title": "Exercise 08.3: search for some source text"}, {"location": "exercises/mat/", "text": "02. Matches \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Exercise 02.1: translate from scratch \u00b6 Press Ctrl + J and enter 1 to go to segment #1. Source text reads Welcome to this survey! Translate segment #1. Suggested translation: Bienvenue \u00e0 cette enqu\u00e8te ! Press Enter to go to the next segment. Exercise 02.2: pretranslated and locked \u00b6 You're now in segment #2. Notice how this segment is pretranslated. Notice that it has an orange background. That means that this is an enforced translation. In other words, the translation is not editable. Make some edits to modify the translation. Press F5 to reload the project. Notice how your edits are now gone. Press Ctrl + U to go to the next untranslated segment. That should take you to segment #3. Exercise 02.3: insert match and update it \u00b6 You're now in segment #3. Notice that there's a fuzzy match you can use. Press Ctrl + I to insert it. Looking at the match in the Matches pane, notice the difference between the new source text and the source text in \"tracked changes\". Update the inserted translation so that it corresponds to the source text you're translating. Tip: Replace sanitaire with \u00e9conomique . Press Ctrl + U to go to the next untranslated segment. That should take you to segment #5. Exercise 02.4: insert match and update it \u00b6 Notice how pressing Ctrl + U has jumped over segment #4, which was already translated. You're in segment #5. There is a 50% match that you could use. Press Ctrl + I to insert it. Now update the translation so that it corresponds to the source text. Tip: delete Tr\u00e8s and change the case of the first letter. Expected result: Bon Press Ctrl + U to go to the next untranslated segment. That should take you to segment #6. Exercise 02.5: insert exact match \u00b6 You're in segment #6. Notice that there's an exact match which you can use as is. Your lucky day! Press Ctrl + I to insert it. There's nothing else to do this time :) Press Ctrl + U to go to the next untranslated segment. That should take you to segment #7. Exercise 02.6: select text and insert \u00b6 You're in segment #7. Notice that there are two 50% matches that you could use. See what is the part that can be used in the first match. Press Ctrl + 2 to select the second match. See what is the part that can be used in the second match. Press Ctrl + 1 to select the first match again. Alternate between Ctrl + 1 and Ctrl + 2 to highlight the differences in each match. With your mouse, select Tr\u00e8s in match #1. The translation of \"very\" in the first match is something you can use. Press Ctrl + I to insert your selection. With your mouse, select mauvais in match #2. You can also use the translation of \"bad\" in the second match. Press Ctrl + I to insert your selection. Expected result: tr\u00e8s mauvais Press Ctrl + U to go to the next untranslated segment. That should take you to segment #8. Exercise 02.7: select a match and insert it \u00b6 You're now in segment #8. Notice how the first match is not so convenient as the second match. Press Ctrl + 2 to select match #2. Press Ctrl + I to insert match #2. Exercise 02.8: pretranslated and editable \u00b6 You're still in segment #8. Notice how segments #9 and #10 are pretranslated. Notice that they have a pink background. That means that they can be edited. Press Ctrl + U to go to the next untranslated segment. Exercise 02.9: almost identical match \u00b6 You're in segment #11. Notice how pressing Ctrl + U has jumped over the two pretranslated segments. Source text reads Welcome to this survey. Notice how this segment is almost identical to the first segment you translated. The only difference is in the final punctuation. Press Ctrl + I to insert the match. Update the translation now. Replace the exclamation mark ! with a full stop . Press Ctrl + U to go to the next untranslated segment. That should take you to segment #12. Exercise 02.10: insert match and update it \u00b6 Ok, the last one if you have time :) You're now in segment #12. Notice that there's a fuzzy match you can use. Press Ctrl + I to insert it. Looking at the match in the Matches pane, notice the difference between the new source text and the source text in \"tracked changes\". Update the inserted translation so that it corresponds to the source text you're translating. Tip: Replace financi\u00e8re with \u00e9conomique Well done!", "title": "02 - Matches"}, {"location": "exercises/mat/#02-matches", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification", "title": "02. Matches"}, {"location": "exercises/mat/#exercise-021-translate-from-scratch", "text": "Press Ctrl + J and enter 1 to go to segment #1. Source text reads Welcome to this survey! Translate segment #1. Suggested translation: Bienvenue \u00e0 cette enqu\u00e8te ! Press Enter to go to the next segment.", "title": "Exercise 02.1: translate from scratch"}, {"location": "exercises/mat/#exercise-022-pretranslated-and-locked", "text": "You're now in segment #2. Notice how this segment is pretranslated. Notice that it has an orange background. That means that this is an enforced translation. In other words, the translation is not editable. Make some edits to modify the translation. Press F5 to reload the project. Notice how your edits are now gone. Press Ctrl + U to go to the next untranslated segment. That should take you to segment #3.", "title": "Exercise 02.2: pretranslated and locked"}, {"location": "exercises/mat/#exercise-023-insert-match-and-update-it", "text": "You're now in segment #3. Notice that there's a fuzzy match you can use. Press Ctrl + I to insert it. Looking at the match in the Matches pane, notice the difference between the new source text and the source text in \"tracked changes\". Update the inserted translation so that it corresponds to the source text you're translating. Tip: Replace sanitaire with \u00e9conomique . Press Ctrl + U to go to the next untranslated segment. That should take you to segment #5.", "title": "Exercise 02.3: insert match and update it"}, {"location": "exercises/mat/#exercise-024-insert-match-and-update-it", "text": "Notice how pressing Ctrl + U has jumped over segment #4, which was already translated. You're in segment #5. There is a 50% match that you could use. Press Ctrl + I to insert it. Now update the translation so that it corresponds to the source text. Tip: delete Tr\u00e8s and change the case of the first letter. Expected result: Bon Press Ctrl + U to go to the next untranslated segment. That should take you to segment #6.", "title": "Exercise 02.4: insert match and update it"}, {"location": "exercises/mat/#exercise-025-insert-exact-match", "text": "You're in segment #6. Notice that there's an exact match which you can use as is. Your lucky day! Press Ctrl + I to insert it. There's nothing else to do this time :) Press Ctrl + U to go to the next untranslated segment. That should take you to segment #7.", "title": "Exercise 02.5: insert exact match"}, {"location": "exercises/mat/#exercise-026-select-text-and-insert", "text": "You're in segment #7. Notice that there are two 50% matches that you could use. See what is the part that can be used in the first match. Press Ctrl + 2 to select the second match. See what is the part that can be used in the second match. Press Ctrl + 1 to select the first match again. Alternate between Ctrl + 1 and Ctrl + 2 to highlight the differences in each match. With your mouse, select Tr\u00e8s in match #1. The translation of \"very\" in the first match is something you can use. Press Ctrl + I to insert your selection. With your mouse, select mauvais in match #2. You can also use the translation of \"bad\" in the second match. Press Ctrl + I to insert your selection. Expected result: tr\u00e8s mauvais Press Ctrl + U to go to the next untranslated segment. That should take you to segment #8.", "title": "Exercise 02.6: select text and insert"}, {"location": "exercises/mat/#exercise-027-select-a-match-and-insert-it", "text": "You're now in segment #8. Notice how the first match is not so convenient as the second match. Press Ctrl + 2 to select match #2. Press Ctrl + I to insert match #2.", "title": "Exercise 02.7: select a match and insert it"}, {"location": "exercises/mat/#exercise-028-pretranslated-and-editable", "text": "You're still in segment #8. Notice how segments #9 and #10 are pretranslated. Notice that they have a pink background. That means that they can be edited. Press Ctrl + U to go to the next untranslated segment.", "title": "Exercise 02.8: pretranslated and editable"}, {"location": "exercises/mat/#exercise-029-almost-identical-match", "text": "You're in segment #11. Notice how pressing Ctrl + U has jumped over the two pretranslated segments. Source text reads Welcome to this survey. Notice how this segment is almost identical to the first segment you translated. The only difference is in the final punctuation. Press Ctrl + I to insert the match. Update the translation now. Replace the exclamation mark ! with a full stop . Press Ctrl + U to go to the next untranslated segment. That should take you to segment #12.", "title": "Exercise 02.9: almost identical match"}, {"location": "exercises/mat/#exercise-0210-insert-match-and-update-it", "text": "Ok, the last one if you have time :) You're now in segment #12. Notice that there's a fuzzy match you can use. Press Ctrl + I to insert it. Looking at the match in the Matches pane, notice the difference between the new source text and the source text in \"tracked changes\". Update the inserted translation so that it corresponds to the source text you're translating. Tip: Replace financi\u00e8re with \u00e9conomique Well done!", "title": "Exercise 02.10: insert match and update it"}, {"location": "exercises/nav/", "text": "01. Navigation \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Remember The active segment always has a green background. Exercise 01.1: moving through the project \u00b6 Press Ctrl + J and enter 1 to go to segment #1. Source text reads Welcome to this survey! Press Enter to move to the next segment. You are now in segment #2. Press Ctrl + U to move to the next untranslated segment. You are now in segment #3. Press Enter twice in a row to go forward 2 segments. You end up in segment #5. Press Ctrl + Enter twice in a row to go backwards 2 segments. You are now in segment #3. Press Ctrl + U once to go to the next untranslated segment. You end up in segment #5 again. Notice that you have jumped segment #4, which is already translated (in pink). Tip Press Ctrl + U when you're translating. Press Enter when you're reviewing a translation. Exercise 01.2: moving through the project a bit more \u00b6 Press Ctrl + J and enter number 25 to go to segment #25. Source text reads: Generally speaking, please tell me how satisfied you are with public transport where you live. Press Ctrl + U to jump to the next untranslated segment. You are now on segment #30. Press Enter to move the next segment. You are now on segment #31. Oops, you haven't translated segment #30. Press Ctrl + Enter to go back to it. You are now on segment #30 again. Scroll down until you see another untranslated segment in that file. Source text reads: Generally speaking, please tell me how satisfied you are with schools and other educational facilities where you live. Double click on that segment. You are now on segment #53. Press keyboard shortcut Ctrl + J and enter number 1 to go to segment number #1. Recap In this exercise you have practiced several ways to activate a segment: Enter opens the next segment Ctrl + Enter opens the previous segment Ctrl + U opens the next untranslated segment Ctrl + J (plus the segment numberj) opens a specific segment", "title": "01 - Navigation"}, {"location": "exercises/nav/#01-navigation", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Remember The active segment always has a green background.", "title": "01. Navigation"}, {"location": "exercises/nav/#exercise-011-moving-through-the-project", "text": "Press Ctrl + J and enter 1 to go to segment #1. Source text reads Welcome to this survey! Press Enter to move to the next segment. You are now in segment #2. Press Ctrl + U to move to the next untranslated segment. You are now in segment #3. Press Enter twice in a row to go forward 2 segments. You end up in segment #5. Press Ctrl + Enter twice in a row to go backwards 2 segments. You are now in segment #3. Press Ctrl + U once to go to the next untranslated segment. You end up in segment #5 again. Notice that you have jumped segment #4, which is already translated (in pink). Tip Press Ctrl + U when you're translating. Press Enter when you're reviewing a translation.", "title": "Exercise 01.1: moving through the project"}, {"location": "exercises/nav/#exercise-012-moving-through-the-project-a-bit-more", "text": "Press Ctrl + J and enter number 25 to go to segment #25. Source text reads: Generally speaking, please tell me how satisfied you are with public transport where you live. Press Ctrl + U to jump to the next untranslated segment. You are now on segment #30. Press Enter to move the next segment. You are now on segment #31. Oops, you haven't translated segment #30. Press Ctrl + Enter to go back to it. You are now on segment #30 again. Scroll down until you see another untranslated segment in that file. Source text reads: Generally speaking, please tell me how satisfied you are with schools and other educational facilities where you live. Double click on that segment. You are now on segment #53. Press keyboard shortcut Ctrl + J and enter number 1 to go to segment number #1. Recap In this exercise you have practiced several ways to activate a segment: Enter opens the next segment Ctrl + Enter opens the previous segment Ctrl + U opens the next untranslated segment Ctrl + J (plus the segment numberj) opens a specific segment", "title": "Exercise 01.2: moving through the project a bit more"}, {"location": "exercises/qac/", "text": "09. QA checks \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Exercise 09.1: check tag issues \u00b6 Open the QA checks dialog in Tools > Check for issues... . Uncheck all options except \"Tag Issues\" The \"Tag Issues\" check is mandatory, you cannot unselect it. Press \"OK\" Notice that there is (at least) an issue about \"Bad nesting\". Press the \"Jump to segment\" button. OmegaT will open the segment with the issue. You should be on segment #25 Look at the tags and notice what the issue is about. The order of tags is incorrect. Remove the two tags and insert them again. Expected result: De mani\u00e8re g\u00e9n\u00e9rale, dites-moi si \u00e0 quel point vous \u00eates satisfait avec les transports publics l\u00e0 o\u00f9 vous vivez. Press the \"Refresh\" button in the Issues dialog to confirm that the issue is gone. Tip If you're not sure how to fix a tag issue during a production task, please request support through the Helpdesk. Exercise 09.2: check completion \u00b6 Go to Tools > Statistics . Look at the Remaining row in the project statistics. Notice whether the project is fully translated. Tip If you see a number higher than zero in the Remaining row(s), that means that there are still some remaining untranslated segments. All segments should be translated before you can finalize your task. Tip Press Ctrl + U to go to the next untranslated segment.", "title": "09 - QA checks"}, {"location": "exercises/qac/#09-qa-checks", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification", "title": "09. QA checks"}, {"location": "exercises/qac/#exercise-091-check-tag-issues", "text": "Open the QA checks dialog in Tools > Check for issues... . Uncheck all options except \"Tag Issues\" The \"Tag Issues\" check is mandatory, you cannot unselect it. Press \"OK\" Notice that there is (at least) an issue about \"Bad nesting\". Press the \"Jump to segment\" button. OmegaT will open the segment with the issue. You should be on segment #25 Look at the tags and notice what the issue is about. The order of tags is incorrect. Remove the two tags and insert them again. Expected result: De mani\u00e8re g\u00e9n\u00e9rale, dites-moi si \u00e0 quel point vous \u00eates satisfait avec les transports publics l\u00e0 o\u00f9 vous vivez. Press the \"Refresh\" button in the Issues dialog to confirm that the issue is gone. Tip If you're not sure how to fix a tag issue during a production task, please request support through the Helpdesk.", "title": "Exercise 09.1: check tag issues"}, {"location": "exercises/qac/#exercise-092-check-completion", "text": "Go to Tools > Statistics . Look at the Remaining row in the project statistics. Notice whether the project is fully translated. Tip If you see a number higher than zero in the Remaining row(s), that means that there are still some remaining untranslated segments. All segments should be translated before you can finalize your task. Tip Press Ctrl + U to go to the next untranslated segment.", "title": "Exercise 09.2: check completion"}, {"location": "exercises/rec/", "text": "03. Reconciliation \u00b6 The relevant section in the guide... See the relevant section (about matches) in your guide: Reconciliation This section includes some bonus exercises specifically addressed to reconcilers. You may skip this section if you're not going to reconcile. Getting started \u00b6 Here's a UI preference that may be useful for you when you reconcile. In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 100 With that setting, the Matches pane will show you only the translations you need to reconcile. Please remember to restore the default value when you're not reconciling. Exercise 03.01: inserting one match \u00b6 Go to segment #55 and read it. Here comes a story for you. Source text reads Once upon a time there was a reconciler who worked in OmegaT. You have one exact match. Press Ctrl + I to insert it. Easy start. Now press Ctrl + U to move to the next unreconciled segment. Read segment #56. You have one exact match. Press Ctrl + I to translate the segment with that match. Still easy. Press Ctrl + U to move to the next unreconciled segment. Info You only see one match if \"translation 1\" and \"translation 2\" are identical. Exercise 03.02: selecting the match \u00b6 You're now on segment #57. Read segment #57. Notice that now you can see two matches because \"translation 1\" and \"translation 2\" are different now. You want to use the first translation (selected by default). Press Ctrl + I to insert match #1. Translation reads Parfois, l'une des deux traductions \u00e9tait bonne, et l'autre \u00e9tait mauvaise, donc le choix \u00e9tait clair. Press Ctrl + U to move to the next unreconciled segment. You're now on segment #58. 11. Read segment #58. 11. Here you want to use the second translation. Press Ctrl + 2 to select match #2. 12. Press Ctrl + I to insert it. Translation reads D'autres fois, la premi\u00e8re traduction \u00e9tait mauvaise, mais la seconde \u00e9tait bonne, donc le choix \u00e9tait \u00e9galement clair. Press Ctrl + U to move to the next unreconciled segment. Exersise 04.03: editing the inserted translation \u00b6 You're now on segment #59. Read segment #59. Press Ctrl + I to insert the exiting match. Edit the translation to make it a good translation. Tip: Remove the excessive SSs in parfoisSSs . Press Ctrl + U to move to the next unreconciled segment. Exercise 03.03: assembling fragments \u00b6 You are in segment #60. In match #1, select Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, Press Ctrl + I to insert the text you have selected. In match #2, select , mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. Press Ctrl + I to insert the text you have selected now. Expected result: Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. You have combined two parts of two translations to create one single reconciled version. Congrats! Finally \u00b6 Please remember to restore the default threshold to show matches: In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 50.", "title": "03 - Reconciliation"}, {"location": "exercises/rec/#03-reconciliation", "text": "The relevant section in the guide... See the relevant section (about matches) in your guide: Reconciliation This section includes some bonus exercises specifically addressed to reconcilers. You may skip this section if you're not going to reconcile.", "title": "03. Reconciliation"}, {"location": "exercises/rec/#getting-started", "text": "Here's a UI preference that may be useful for you when you reconcile. In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 100 With that setting, the Matches pane will show you only the translations you need to reconcile. Please remember to restore the default value when you're not reconciling.", "title": "Getting started"}, {"location": "exercises/rec/#exercise-0301-inserting-one-match", "text": "Go to segment #55 and read it. Here comes a story for you. Source text reads Once upon a time there was a reconciler who worked in OmegaT. You have one exact match. Press Ctrl + I to insert it. Easy start. Now press Ctrl + U to move to the next unreconciled segment. Read segment #56. You have one exact match. Press Ctrl + I to translate the segment with that match. Still easy. Press Ctrl + U to move to the next unreconciled segment. Info You only see one match if \"translation 1\" and \"translation 2\" are identical.", "title": "Exercise 03.01: inserting one match"}, {"location": "exercises/rec/#exercise-0302-selecting-the-match", "text": "You're now on segment #57. Read segment #57. Notice that now you can see two matches because \"translation 1\" and \"translation 2\" are different now. You want to use the first translation (selected by default). Press Ctrl + I to insert match #1. Translation reads Parfois, l'une des deux traductions \u00e9tait bonne, et l'autre \u00e9tait mauvaise, donc le choix \u00e9tait clair. Press Ctrl + U to move to the next unreconciled segment. You're now on segment #58. 11. Read segment #58. 11. Here you want to use the second translation. Press Ctrl + 2 to select match #2. 12. Press Ctrl + I to insert it. Translation reads D'autres fois, la premi\u00e8re traduction \u00e9tait mauvaise, mais la seconde \u00e9tait bonne, donc le choix \u00e9tait \u00e9galement clair. Press Ctrl + U to move to the next unreconciled segment.", "title": "Exercise 03.02: selecting the match"}, {"location": "exercises/rec/#exersise-0403-editing-the-inserted-translation", "text": "You're now on segment #59. Read segment #59. Press Ctrl + I to insert the exiting match. Edit the translation to make it a good translation. Tip: Remove the excessive SSs in parfoisSSs . Press Ctrl + U to move to the next unreconciled segment.", "title": "Exersise 04.03: editing the inserted translation"}, {"location": "exercises/rec/#exercise-0303-assembling-fragments", "text": "You are in segment #60. In match #1, select Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, Press Ctrl + I to insert the text you have selected. In match #2, select , mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. Press Ctrl + I to insert the text you have selected now. Expected result: Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. You have combined two parts of two translations to create one single reconciled version. Congrats!", "title": "Exercise 03.03: assembling fragments"}, {"location": "exercises/rec/#finally", "text": "Please remember to restore the default threshold to show matches: In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 50.", "title": "Finally"}, {"location": "exercises/rep/", "text": "05. Repetitions \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Exercise 05.1: recognize repeated segments \u00b6 Press Ctrl + J and enter 13 to go to segment #13. Source text reads: Pretty good Notice how the segment marker says that this segment is repeated three more times. . Look at the Segment Properties pane. It says \"Is duplicate: FIRST\" Right click on the segment. See how all the instances are listed and identified by their segment number. Select Segment 16 on the list to go to segment #16. Look at the Segment Properties pane for segment #16. It says \"Is duplicate: NEXT\" Right click on segment #16 to see instances listed again, go back to segment #13 again. Exercise 05.2: auto-propagate translations \u00b6 Go to segment #12. Translate segment #12. You can insert the match ( Ctrl + I ) and update it (replace financi\u00e8re with \u00e9conomique ) Notice how \"situation \u00e9conomique\" is grammatically feminine in French. Go to segment #13 and translate it. Suggested translation: Plut\u00f4t bonNE The -NE ending is the feminine suffix, because \"Good\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #13 to go to segment #14. Notice how the translation is auto-propagated to segment #16. Translate segment #14. Suggested translation: Plut\u00f4t mauvaisE The -E ending is the feminine suffix, because \"Bad\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #14 to confirm the translation of segment #14 and go to the next segment. Notice how the translation is auto-propagated to segment #17. Exercise 05.3: auto-propagate edits in translations \u00b6 Go to segment #16 in the project. You can see that it is translated with your auto-propagated translation. Modify the translation (append \"xx\") in segment #16 and press Ctrl + S to save the translation. Notice how the translation of segment #13 also changes. Do the same in segment #17 and see how changes auto-propagate to segment #14. Tip Shortcut Ctrl + S saves the translation. You can also save in Project > Save , but using the mouse takes longer ;)", "title": "05 - Repetitions"}, {"location": "exercises/rep/#05-repetitions", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification", "title": "05. Repetitions"}, {"location": "exercises/rep/#exercise-051-recognize-repeated-segments", "text": "Press Ctrl + J and enter 13 to go to segment #13. Source text reads: Pretty good Notice how the segment marker says that this segment is repeated three more times. . Look at the Segment Properties pane. It says \"Is duplicate: FIRST\" Right click on the segment. See how all the instances are listed and identified by their segment number. Select Segment 16 on the list to go to segment #16. Look at the Segment Properties pane for segment #16. It says \"Is duplicate: NEXT\" Right click on segment #16 to see instances listed again, go back to segment #13 again.", "title": "Exercise 05.1: recognize repeated segments"}, {"location": "exercises/rep/#exercise-052-auto-propagate-translations", "text": "Go to segment #12. Translate segment #12. You can insert the match ( Ctrl + I ) and update it (replace financi\u00e8re with \u00e9conomique ) Notice how \"situation \u00e9conomique\" is grammatically feminine in French. Go to segment #13 and translate it. Suggested translation: Plut\u00f4t bonNE The -NE ending is the feminine suffix, because \"Good\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #13 to go to segment #14. Notice how the translation is auto-propagated to segment #16. Translate segment #14. Suggested translation: Plut\u00f4t mauvaisE The -E ending is the feminine suffix, because \"Bad\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #14 to confirm the translation of segment #14 and go to the next segment. Notice how the translation is auto-propagated to segment #17.", "title": "Exercise 05.2: auto-propagate translations"}, {"location": "exercises/rep/#exercise-053-auto-propagate-edits-in-translations", "text": "Go to segment #16 in the project. You can see that it is translated with your auto-propagated translation. Modify the translation (append \"xx\") in segment #16 and press Ctrl + S to save the translation. Notice how the translation of segment #13 also changes. Do the same in segment #17 and see how changes auto-propagate to segment #14. Tip Shortcut Ctrl + S saves the translation. You can also save in Project > Save , but using the mouse takes longer ;)", "title": "Exercise 05.3: auto-propagate edits in translations"}, {"location": "exercises/tag/", "text": "04. Tags \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Exercise 04.1: insert paired tags \u00b6 Press Ctrl + J and enter 40 to go to segment #40, which is untranslated. Source text reads: Click Play to see it in action. Notice the two tags in the segment. With your mouse, hover over the two tags and notice how the two tags are paired . The first tag stands for and the second tag stands for . Translate segment #40. Suggested translation: Cliquez sur Jouer pour voir \u00e7a en action. Select the part of the translation that corresponds to \"Play\" Tip: you should select Jouer Press Ctrl + Space to open the auto-completer. Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cMissing tags\u201d section. The first option (i.e. | ) is selected by default. Press Enter to insert tag pair. Notice how the two paired tags are inserted around the selected text in the translation. Expected result: Cliquez sur Jouer pour le voir en action. Well done! Exercise 04.2: see what tags stand for \u00b6 Go to segment #41. Source text reads if sensor detects black Notice how the segment contains one standalone tag. Hover over the tag to see what the tag stands for. The tooltip should show {{ sensor_type }} Go to the next segment, #42. Notice how this segment has two standalone tags, not two paired tags! Check what the two tags stand for. The tooltips should show {{ object1 }} and {{ object2 }} Warning The difference between two standalone tags and two paired tags is very important. Exercise 04.3: insert standalone tags \u00b6 Go to segment #43. Notice that the tag is missing in the translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: right at the end of the translation Press Ctrl + Space to launch the auto-completer and insert the tag. Go to segment #44. Notice how the tag is also missing in this translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: click between tourner \u00e0 droite jusqu'\u00e0 ce que and le capteur d\u00e9tecte le noir Use the auto-completer to insert the missing tag. Exercise 04.4: insert standalone tag as you translate \u00b6 Go to segment #45. To translate the segment and insert the tag, proceed in this way: Translate \"repeat\" Suggested translation of the first part: r\u00e9p\u00e9ter Use the auto-completer to insert the missing tag Remember the shortcut to launch the auto-completer is Ctrl + Space . Translate \"times\" Suggested translation of the second part: fois You have inserted the tag as you made progress through the translation. Exercise 04.5: trigger the tag tooltip \u00b6 Press Ctrl + J and enter 48 to go to segment #48. Source text reads: The translator had to pay attention to formatting such as bold, italics, underline. Hover over the tags with your mouse to display a tooltip that shows the line code the tags stand for. Tip: the tooltip should display HTML tags , , etc. Exercise 04.6: insert more tags \u00b6 Still in segment #48, press Ctrl + I to insert the fuzzy match. Notice how most tags are missing in the translation. Select the part of the translation that corresponds to \u201cbold\u201d Tip: le gras Press Ctrl + Space to open the \"Missing tags\" section in the auto-completer. The first line (i.e. ) is selected by default. Press Enter to insert the tag pair that appears in the first line of the auto-completer. Notice how the tags have been inserted around the selected text Results should be le gras Do the same for the translation of \u201citalics\u201d Results should be l\u2019italique Notice how you cannot insert a tag pair around the translation of \u201cunderline\u201d because closing tag is already inserted. Place the mouse cursor in the position where you would like to insert the tag that is paired with . Use the auto-completer ( Ctrl + Space ) to insert tag . Results should be le soulignement Well done!", "title": "04 - Tags"}, {"location": "exercises/tag/#04-tags", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification", "title": "04. Tags"}, {"location": "exercises/tag/#exercise-041-insert-paired-tags", "text": "Press Ctrl + J and enter 40 to go to segment #40, which is untranslated. Source text reads: Click Play to see it in action. Notice the two tags in the segment. With your mouse, hover over the two tags and notice how the two tags are paired . The first tag stands for and the second tag stands for . Translate segment #40. Suggested translation: Cliquez sur Jouer pour voir \u00e7a en action. Select the part of the translation that corresponds to \"Play\" Tip: you should select Jouer Press Ctrl + Space to open the auto-completer. Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cMissing tags\u201d section. The first option (i.e. | ) is selected by default. Press Enter to insert tag pair. Notice how the two paired tags are inserted around the selected text in the translation. Expected result: Cliquez sur Jouer pour le voir en action. Well done!", "title": "Exercise 04.1: insert paired tags"}, {"location": "exercises/tag/#exercise-042-see-what-tags-stand-for", "text": "Go to segment #41. Source text reads if sensor detects black Notice how the segment contains one standalone tag. Hover over the tag to see what the tag stands for. The tooltip should show {{ sensor_type }} Go to the next segment, #42. Notice how this segment has two standalone tags, not two paired tags! Check what the two tags stand for. The tooltips should show {{ object1 }} and {{ object2 }} Warning The difference between two standalone tags and two paired tags is very important.", "title": "Exercise 04.2: see what tags stand for"}, {"location": "exercises/tag/#exercise-043-insert-standalone-tags", "text": "Go to segment #43. Notice that the tag is missing in the translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: right at the end of the translation Press Ctrl + Space to launch the auto-completer and insert the tag. Go to segment #44. Notice how the tag is also missing in this translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: click between tourner \u00e0 droite jusqu'\u00e0 ce que and le capteur d\u00e9tecte le noir Use the auto-completer to insert the missing tag.", "title": "Exercise 04.3: insert standalone tags"}, {"location": "exercises/tag/#exercise-044-insert-standalone-tag-as-you-translate", "text": "Go to segment #45. To translate the segment and insert the tag, proceed in this way: Translate \"repeat\" Suggested translation of the first part: r\u00e9p\u00e9ter Use the auto-completer to insert the missing tag Remember the shortcut to launch the auto-completer is Ctrl + Space . Translate \"times\" Suggested translation of the second part: fois You have inserted the tag as you made progress through the translation.", "title": "Exercise 04.4: insert standalone tag as you translate"}, {"location": "exercises/tag/#exercise-045-trigger-the-tag-tooltip", "text": "Press Ctrl + J and enter 48 to go to segment #48. Source text reads: The translator had to pay attention to formatting such as bold, italics, underline. Hover over the tags with your mouse to display a tooltip that shows the line code the tags stand for. Tip: the tooltip should display HTML tags , , etc.", "title": "Exercise 04.5: trigger the tag tooltip"}, {"location": "exercises/tag/#exercise-046-insert-more-tags", "text": "Still in segment #48, press Ctrl + I to insert the fuzzy match. Notice how most tags are missing in the translation. Select the part of the translation that corresponds to \u201cbold\u201d Tip: le gras Press Ctrl + Space to open the \"Missing tags\" section in the auto-completer. The first line (i.e. ) is selected by default. Press Enter to insert the tag pair that appears in the first line of the auto-completer. Notice how the tags have been inserted around the selected text Results should be le gras Do the same for the translation of \u201citalics\u201d Results should be l\u2019italique Notice how you cannot insert a tag pair around the translation of \u201cunderline\u201d because closing tag is already inserted. Place the mouse cursor in the position where you would like to insert the tag that is paired with . Use the auto-completer ( Ctrl + Space ) to insert tag . Results should be le soulignement Well done!", "title": "Exercise 04.6: insert more tags"}, {"location": "exercises/tgt/", "text": "10. Working with team projects \u00b6 Unlike in previous cycles, in this cycle you will work on an online team project hosted in a git repository. Download team project from git repository \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Details \u00b6 Here are the details of a team project you can download for training purposes. Warning This is not the project where you must work to produce your translation. URL of the git repository: https://github.com/capstanlqc/project_task_fr-ZZ_omt.git Username: pisa25npm Password: password (For security reasons, the password is provided in a separate page. Just click on the link above to open it.) Steps \u00b6 In OmegaT, go to Project > Download Team Project . Paste the URL of the git repository in the \"Repository URL\" field. Then click on the \"New Local Project Folder\" field. OmegaT will propose a location to clone the project in your machine, e.g. something like C:\\Users\\USER\\project_task_fr-ZZ_omt (where USER is your username). The name of the project is highlighted in yellow in the screenshot below: If the proposed path to the local project folder is fine, just press OK . All files in the project will be downloaded and the project will be open in OmegaT after a few seconds. Want to edit the local project folder? You may change or edit the path to the location where the project will be created, e.g. to create the project in a PISA folder: In any case, do not change the name of the project (highlighted in yellow below): Please check our File organization tips, they could help you keep your files and folders more organized. Warning The location where you create the team project should not be inside a folder sync'ed by Dropbox, OneDrive, Nextcloud, etc. (any sync'ing service in your machine). Commit target files \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification To commit target files (e.g. to update the preview): Go to Project > Commit Target Files .", "title": "10 - Team projects"}, {"location": "exercises/tgt/#10-working-with-team-projects", "text": "Unlike in previous cycles, in this cycle you will work on an online team project hosted in a git repository.", "title": "10. Working with team projects"}, {"location": "exercises/tgt/#download-team-project-from-git-repository", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification", "title": "Download team project from git repository"}, {"location": "exercises/tgt/#details", "text": "Here are the details of a team project you can download for training purposes. Warning This is not the project where you must work to produce your translation. URL of the git repository: https://github.com/capstanlqc/project_task_fr-ZZ_omt.git Username: pisa25npm Password: password (For security reasons, the password is provided in a separate page. Just click on the link above to open it.)", "title": "Details"}, {"location": "exercises/tgt/#steps", "text": "In OmegaT, go to Project > Download Team Project . Paste the URL of the git repository in the \"Repository URL\" field. Then click on the \"New Local Project Folder\" field. OmegaT will propose a location to clone the project in your machine, e.g. something like C:\\Users\\USER\\project_task_fr-ZZ_omt (where USER is your username). The name of the project is highlighted in yellow in the screenshot below: If the proposed path to the local project folder is fine, just press OK . All files in the project will be downloaded and the project will be open in OmegaT after a few seconds. Want to edit the local project folder? You may change or edit the path to the location where the project will be created, e.g. to create the project in a PISA folder: In any case, do not change the name of the project (highlighted in yellow below): Please check our File organization tips, they could help you keep your files and folders more organized. Warning The location where you create the team project should not be inside a folder sync'ed by Dropbox, OneDrive, Nextcloud, etc. (any sync'ing service in your machine).", "title": "Steps"}, {"location": "exercises/tgt/#commit-target-files", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification To commit target files (e.g. to update the preview): Go to Project > Commit Target Files .", "title": "Commit target files"}, {"location": "exercises_02/", "text": "OmegaT exercises - Getting started \u00b6 Getting your project \u00b6 For countries (NOT READY YET): \u00b6 Download project package project_task_fr-ZZ_offline_omt.omt . Unpack that project. Reminder How to unpack an offline project", "title": "OmegaT exercises - Getting started"}, {"location": "exercises_02/#omegat-exercises-getting-started", "text": "", "title": "OmegaT exercises - Getting started"}, {"location": "exercises_02/#getting-your-project", "text": "", "title": "Getting your project"}, {"location": "exercises_02/#for-countries-not-ready-yet", "text": "Download project package project_task_fr-ZZ_offline_omt.omt . Unpack that project. Reminder How to unpack an offline project", "title": "For countries (NOT READY YET):"}, {"location": "exercises_02/alt/", "text": "06. Alternative translations \u00b6 In the previous section you saw that translations of repeated segments (or edits in those translations) auto-propagate to all instances of that repeated segment when you save them (or leave the segment). That is convenient in many cases, but not always. Sometimes you'll have to prevent auto-propagation. To do that, you must create an alternative translation . Exercise 06.1: create alternative translation \u00b6 Go to segment #5 in the project. Source text reads: Good Notice that it is translated with an auto-propagated translation. Good and Bad in segments #5 and #6 in this context refer to \"level of English\" which is masculine in French. However, your translation (\"BonNE\" and \"MauvaisE\") refers to \"situation economique\" and therefore is feminine. You want to modify the translation in segments #16 and #17 to make it masculine, so that it agrees with \"level\" in French. Follow these three simple but VERY IMPORTANT steps: Go to Edit > Create Alternative Translation . Tip: Also available if you right-click the segment. Modify the translation to make it masculine Just remove the last character if you don't know French Press Ctrl + S to register the translation Warning This is a very important and delicate function of OmegaT. It's easy to use it correctly if you grasp well the three steps above, but it's also easy to make a mess if you don't. Please make sure you really follow the three steps above to the letter. Did you follow the steps above? If you did, now you'll notice that: your alternative translation appears now in the Multiple Translations pane, below the followed the default translation and followed by the filename and the segment ID. the Segment Properties pane for that segment says now \"Is alternative: TRUE\" the (default) translation of segment #2 hasn't changed Press Enter to move to segment #6 and do the same steps as above. Info If you want more practice, go to segment #29 (source text reads: Subject: ), which is also repeated a few times. The first occurrence refers to an email subject line, whereas the other occurrences refer to the topic or subject matter field of books in a library classification system, so each of those requires a different translation, i.e. \"Objet\" vs \"Sujet\".", "title": "06. Alternative translations"}, {"location": "exercises_02/alt/#06-alternative-translations", "text": "In the previous section you saw that translations of repeated segments (or edits in those translations) auto-propagate to all instances of that repeated segment when you save them (or leave the segment). That is convenient in many cases, but not always. Sometimes you'll have to prevent auto-propagation. To do that, you must create an alternative translation .", "title": "06. Alternative translations"}, {"location": "exercises_02/alt/#exercise-061-create-alternative-translation", "text": "Go to segment #5 in the project. Source text reads: Good Notice that it is translated with an auto-propagated translation. Good and Bad in segments #5 and #6 in this context refer to \"level of English\" which is masculine in French. However, your translation (\"BonNE\" and \"MauvaisE\") refers to \"situation economique\" and therefore is feminine. You want to modify the translation in segments #16 and #17 to make it masculine, so that it agrees with \"level\" in French. Follow these three simple but VERY IMPORTANT steps: Go to Edit > Create Alternative Translation . Tip: Also available if you right-click the segment. Modify the translation to make it masculine Just remove the last character if you don't know French Press Ctrl + S to register the translation Warning This is a very important and delicate function of OmegaT. It's easy to use it correctly if you grasp well the three steps above, but it's also easy to make a mess if you don't. Please make sure you really follow the three steps above to the letter. Did you follow the steps above? If you did, now you'll notice that: your alternative translation appears now in the Multiple Translations pane, below the followed the default translation and followed by the filename and the segment ID. the Segment Properties pane for that segment says now \"Is alternative: TRUE\" the (default) translation of segment #2 hasn't changed Press Enter to move to segment #6 and do the same steps as above. Info If you want more practice, go to segment #29 (source text reads: Subject: ), which is also repeated a few times. The first occurrence refers to an email subject line, whereas the other occurrences refer to the topic or subject matter field of books in a library classification system, so each of those requires a different translation, i.e. \"Objet\" vs \"Sujet\".", "title": "Exercise 06.1: create alternative translation"}, {"location": "exercises_02/aut/", "text": "06. Special characters \u00b6 \u2190TODO Add link to the section in the guide. You may insert special characters in different ways: autotext shortcut, character table, etc. Exercise 06.1: use a known autotext shortcut \u00b6 You may use the autotext shortcut \\sub2 to insert a subscript number 2 (i.e. \u2082 ). Now you know! :) Tip The \"suB\" part in the shorcut \\sub2 stands for subindex or subscript. \u2190TODO @quiz: what do you notice in segment #47 (@todo: complete) Go to segment #47 and read the source text. Target text reads Le dioxyde de carbone (CO2) se dissout dans l'eau de mer pour former de l'acide carbonique. Delete number 2 in \u201cCO2\u201d (and keep the cursor right after \"CO\"). A subscript number should be used instead of a regular digit. In that same position, type the autotext shortcut \\sub2 Notice how the auto-completer window opens showing the autotext entry. Press Enter to insert the special character \u2082 . The result should be: CO\u2082 In this exercise you have used an autotext shortcut that you knew already. In the following exercises you'll find out an autotext entry that you don't know. Exercise 06.2: find special character in the list of autotext entries \u00b6 In this exercise, you must insert the multiplication symbol but you don't know what autotext entry you can use. Go to segment #52 Source text reads: Thermal conductivity coefficient
    (W/m \u00d7 K) Open the list of available shortcuts here . Look for the autotext entry for the multiplication symbol. You can use either \\times or \\x (how lucky, this one is shorter!) Translate segment #52 as you like (don't forget the part in parentheses). To translate the part in parenthesis, type \\x (or \\times ) between W/m and K . Notice how the auto-completer opens when you typed the autotext shortcut. Press Enter to insert the caracter. Result should be: W/m \u00d7 K Incorrect translation: W/m x K Info You can find the list of autotext entries in OmegaT guides > Miscellanea > Autotext Exercise 06.3: insert special character from the character table \u00b6 Remember the auto-completer? You used it to insert tags. You'll use it again now to insert a special character. Go to segment #49 Target text reads: \u201cLa densit\u00e9 de population est de 62 personnes par km2 en 2023.\u201d Delete number 2 in \u201ckm2\u201d (and keep your cursor right after \u201ckm\u201d). Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cCharacter table\u201d. Spot the relevant character \u00b2 and double click on it to insert it. The result should be: km\u00b2 Tip You could have inserted character \u00b2 with shortcut \\sup2 (where \"suP\" stands for superscript or superindex or superordinate).", "title": "06. Special characters"}, {"location": "exercises_02/aut/#06-special-characters", "text": "\u2190TODO Add link to the section in the guide. You may insert special characters in different ways: autotext shortcut, character table, etc.", "title": "06. Special characters"}, {"location": "exercises_02/aut/#exercise-061-use-a-known-autotext-shortcut", "text": "You may use the autotext shortcut \\sub2 to insert a subscript number 2 (i.e. \u2082 ). Now you know! :) Tip The \"suB\" part in the shorcut \\sub2 stands for subindex or subscript. \u2190TODO @quiz: what do you notice in segment #47 (@todo: complete) Go to segment #47 and read the source text. Target text reads Le dioxyde de carbone (CO2) se dissout dans l'eau de mer pour former de l'acide carbonique. Delete number 2 in \u201cCO2\u201d (and keep the cursor right after \"CO\"). A subscript number should be used instead of a regular digit. In that same position, type the autotext shortcut \\sub2 Notice how the auto-completer window opens showing the autotext entry. Press Enter to insert the special character \u2082 . The result should be: CO\u2082 In this exercise you have used an autotext shortcut that you knew already. In the following exercises you'll find out an autotext entry that you don't know.", "title": "Exercise 06.1: use a known autotext shortcut"}, {"location": "exercises_02/aut/#exercise-062-find-special-character-in-the-list-of-autotext-entries", "text": "In this exercise, you must insert the multiplication symbol but you don't know what autotext entry you can use. Go to segment #52 Source text reads: Thermal conductivity coefficient
    (W/m \u00d7 K) Open the list of available shortcuts here . Look for the autotext entry for the multiplication symbol. You can use either \\times or \\x (how lucky, this one is shorter!) Translate segment #52 as you like (don't forget the part in parentheses). To translate the part in parenthesis, type \\x (or \\times ) between W/m and K . Notice how the auto-completer opens when you typed the autotext shortcut. Press Enter to insert the caracter. Result should be: W/m \u00d7 K Incorrect translation: W/m x K Info You can find the list of autotext entries in OmegaT guides > Miscellanea > Autotext", "title": "Exercise 06.2: find special character in the list of autotext entries"}, {"location": "exercises_02/aut/#exercise-063-insert-special-character-from-the-character-table", "text": "Remember the auto-completer? You used it to insert tags. You'll use it again now to insert a special character. Go to segment #49 Target text reads: \u201cLa densit\u00e9 de population est de 62 personnes par km2 en 2023.\u201d Delete number 2 in \u201ckm2\u201d (and keep your cursor right after \u201ckm\u201d). Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cCharacter table\u201d. Spot the relevant character \u00b2 and double click on it to insert it. The result should be: km\u00b2 Tip You could have inserted character \u00b2 with shortcut \\sup2 (where \"suP\" stands for superscript or superindex or superordinate).", "title": "Exercise 06.3: insert special character from the character table"}, {"location": "exercises_02/fnd/", "text": "07. Search: AM \u00b6 @\u0167odo: review Using the search function, try to find the following segments in the project: Notice that here is one instance of the repeated segment \"Rather unsatisfied\" that was not translated consistenly. @quiz: can you find it? Find the segment with \"How\" in a note. Try to find the translation of \"translator\" in the translation memories. Find \"Subject\", but only if it has a translation.", "title": "07. Search: AM"}, {"location": "exercises_02/fnd/#07-search-am", "text": "@\u0167odo: review Using the search function, try to find the following segments in the project: Notice that here is one instance of the repeated segment \"Rather unsatisfied\" that was not translated consistenly. @quiz: can you find it? Find the segment with \"How\" in a note. Try to find the translation of \"translator\" in the translation memories. Find \"Subject\", but only if it has a translation.", "title": "07. Search: AM"}, {"location": "exercises_02/mat/", "text": "02. Matches @WIP \u00b6 @todo: check whether tags + matches or matches + tags @todo: update numbers or remove them Exercise 02.1: translate from scratch \u00b6 Translate segment #1. Suggested translation: Bienvenue \u00e0 cette enqu\u00e8te. Press Ctrl + U to go to segment #2. Exercise 02.2: insert match and update it \u00b6 You're in segment #2. Notice that there's a fuzzy match you can use. Press Ctrl + I to insert it. Looking at the Matches pane, notice that there's a difference between the new source text and the source text in the match. Update the inserted translation so that it corresponds to the source text you're translating. Tip: Replace financiere with \u00e9conomique . Press Ctrl + U to go to segment #3. Exercise 02.3: insert exact match \u00b6 You're in segment #3. Notice that there's an exact match which you can use as is. Press Ctrl + I to insert it. There's nothing else to do this time :) Press Ctrl + U to go to segment #4. Exercise 02.4: insert match and update it \u00b6 You're in segment #4. Your previous translation is now a 50% match that you could use. Press Ctrl + I to insert the 50% match. Now update the translation so that it corresponds to the source text. Tip: delete bon , type mauvaise Expected result: Plut\u00f4t mauvaise Exercise 02.5: pretranslated and editable \u00b6 You're still in segment #4. Notice how segment #5 is pretranslated. Notice that it has a pink background. That means that it is editable, if necessary. Press Ctrl + U to go to segment #8. Exercise 02.6: almost identical match \u00b6 You're in segment #8. Source text reads Welcome to this survey! Notice how this segment is almost identical to the first segment you translated. The only difference is in the final punctuation. Press Ctrl + I to insert the match. Update the translation now. Replace final dot . with exclamation mark ! Exercise 02.7: pretranslated and locked \u00b6 You're still in segment #8. Notice how segments #9, #11 and a few others are pretranslated. Notice that they have an orange background. That means they are enforced translations, in other words: not editable. Modify the translation (just add a few characters) Press F5 to reload the project. Notice how your edits are now gone. Exercise 02.8: select match \u00b6 Press Ctrl + J and enter number 15 to go to segment #15. Notice that this segment is pretranslated. Go to segment #16. Source text reads Good Notice how the Matches pane presents two matches you could use. Press Ctrl + 2 to select the second match (match #2). Press Ctrl + I to insert the selected match (match #2). Delete plut\u00f4t and change the case. Expected result: Bon Note In this case both matches required the same amount of work to update them. The only reason why you have to select and insert match #2 is to make you practice ;) Exercise 02.9: insert selection \u00b6 Press Ctrl + U to go to segment #17. Select \"mauvaise\" in the fuzzy match Now press Ctrl + I to insert the selected text Update the match. Change case of m to M Expected result: Mauvais \u00e7 Exercise 02.10: \u00b6 Press Ctrl + U to go to segment #18. Press Ctrl + 2 , then press Ctrl + 3 , as many times as you want. Notice how match #2 and match #3 get seleted when you press the shortcuts above. Select one and insert it, then updated it. Here you're free to update the fuzzy match as you like. Expected resul: Tr\u00e8s mauvais Recap To recap, the available options are: Write Tr\u00e8s , then select mauvaise in match #2 and press Ctrl + I Press Ctrl + 2 , then Ctrl + I to insert match #2, then replace PLut\u00f4t with Tr\u00e8s Press Ctrl + 3 , then Ctrl + I to insert Mauvaise , then update it, then add Tr\u00e8s at the beginning Write Tr\u00e8s , then press Ctrl + 3 , then Ctrl + I to insert match #3, then update it. They are all valid approaches, any is fine as long as the result is correct.", "title": "02. Matches @WIP"}, {"location": "exercises_02/mat/#02-matches-wip", "text": "@todo: check whether tags + matches or matches + tags @todo: update numbers or remove them", "title": "02. Matches @WIP"}, {"location": "exercises_02/mat/#exercise-021-translate-from-scratch", "text": "Translate segment #1. Suggested translation: Bienvenue \u00e0 cette enqu\u00e8te. Press Ctrl + U to go to segment #2.", "title": "Exercise 02.1: translate from scratch"}, {"location": "exercises_02/mat/#exercise-022-insert-match-and-update-it", "text": "You're in segment #2. Notice that there's a fuzzy match you can use. Press Ctrl + I to insert it. Looking at the Matches pane, notice that there's a difference between the new source text and the source text in the match. Update the inserted translation so that it corresponds to the source text you're translating. Tip: Replace financiere with \u00e9conomique . Press Ctrl + U to go to segment #3.", "title": "Exercise 02.2: insert match and update it"}, {"location": "exercises_02/mat/#exercise-023-insert-exact-match", "text": "You're in segment #3. Notice that there's an exact match which you can use as is. Press Ctrl + I to insert it. There's nothing else to do this time :) Press Ctrl + U to go to segment #4.", "title": "Exercise 02.3: insert exact match"}, {"location": "exercises_02/mat/#exercise-024-insert-match-and-update-it", "text": "You're in segment #4. Your previous translation is now a 50% match that you could use. Press Ctrl + I to insert the 50% match. Now update the translation so that it corresponds to the source text. Tip: delete bon , type mauvaise Expected result: Plut\u00f4t mauvaise", "title": "Exercise 02.4: insert match and update it"}, {"location": "exercises_02/mat/#exercise-025-pretranslated-and-editable", "text": "You're still in segment #4. Notice how segment #5 is pretranslated. Notice that it has a pink background. That means that it is editable, if necessary. Press Ctrl + U to go to segment #8.", "title": "Exercise 02.5: pretranslated and editable"}, {"location": "exercises_02/mat/#exercise-026-almost-identical-match", "text": "You're in segment #8. Source text reads Welcome to this survey! Notice how this segment is almost identical to the first segment you translated. The only difference is in the final punctuation. Press Ctrl + I to insert the match. Update the translation now. Replace final dot . with exclamation mark !", "title": "Exercise 02.6: almost identical match"}, {"location": "exercises_02/mat/#exercise-027-pretranslated-and-locked", "text": "You're still in segment #8. Notice how segments #9, #11 and a few others are pretranslated. Notice that they have an orange background. That means they are enforced translations, in other words: not editable. Modify the translation (just add a few characters) Press F5 to reload the project. Notice how your edits are now gone.", "title": "Exercise 02.7: pretranslated and locked"}, {"location": "exercises_02/mat/#exercise-028-select-match", "text": "Press Ctrl + J and enter number 15 to go to segment #15. Notice that this segment is pretranslated. Go to segment #16. Source text reads Good Notice how the Matches pane presents two matches you could use. Press Ctrl + 2 to select the second match (match #2). Press Ctrl + I to insert the selected match (match #2). Delete plut\u00f4t and change the case. Expected result: Bon Note In this case both matches required the same amount of work to update them. The only reason why you have to select and insert match #2 is to make you practice ;)", "title": "Exercise 02.8: select match"}, {"location": "exercises_02/mat/#exercise-029-insert-selection", "text": "Press Ctrl + U to go to segment #17. Select \"mauvaise\" in the fuzzy match Now press Ctrl + I to insert the selected text Update the match. Change case of m to M Expected result: Mauvais \u00e7", "title": "Exercise 02.9: insert selection"}, {"location": "exercises_02/mat/#exercise-0210", "text": "Press Ctrl + U to go to segment #18. Press Ctrl + 2 , then press Ctrl + 3 , as many times as you want. Notice how match #2 and match #3 get seleted when you press the shortcuts above. Select one and insert it, then updated it. Here you're free to update the fuzzy match as you like. Expected resul: Tr\u00e8s mauvais Recap To recap, the available options are: Write Tr\u00e8s , then select mauvaise in match #2 and press Ctrl + I Press Ctrl + 2 , then Ctrl + I to insert match #2, then replace PLut\u00f4t with Tr\u00e8s Press Ctrl + 3 , then Ctrl + I to insert Mauvaise , then update it, then add Tr\u00e8s at the beginning Write Tr\u00e8s , then press Ctrl + 3 , then Ctrl + I to insert match #3, then update it. They are all valid approaches, any is fine as long as the result is correct.", "title": "Exercise 02.10:"}, {"location": "exercises_02/nav/", "text": "01. Navigation \u00b6 Exercise 01.1 \u00b6 Press Ctrl + J and enter 1 to go to segment #1. Source text reads Welcome to this survey. Press Enter to move to the next segment. You are now in segment #2. Press Ctrl + U to move to the next untranslated segment. You are now in segment #3. Press Enter three times in a row to go forward 3 segments. You end up in segment #6. Press Ctrl + Enter twice in a row to go backwards 2 segments. You are now in segment #4. Press Ctrl + U once to go to the next untranslated segment. You end up in segment #6 again. Notice that you have jumped segment #5, which is already translated (in pink). Tip when you tranlsate: ctrl+u when you review: enter Exercise 01.2 \u00b6 Press Ctrl + J and enter number 53 to go to segment #53. Source text reads: Generally speaking, please tell me how satisfied you are with public transport where you live . Press Ctrl + U to jump to the next untranslated segment. You are now on segment #58. Press Enter to move the next segment. You are now on segment #59. Oops, you haven't translated segment #58. Press Ctrl + Enter to go back to it. You are now on segment #58 again. Scroll down until you see another untranslated segment in that file. Source text reads: Generally speaking, please tell me how satisfied you are with schools and other educational facilities where you live. Double click on that segment. You are now on segment #63. Press keyboard shortcut Ctrl + J and enter number 1 to go to segment number #1. Recap In this exercise you have practiced several ways to activate a segment: Enter opens the next segment Ctrl + Enter opens the previous segment Ctrl + U opens the next untranslated segment Ctrl + J (plus the segment numberj) opens a specific segment \u2190TODO Check segment numbers after no more changes.", "title": "01. Navigation"}, {"location": "exercises_02/nav/#01-navigation", "text": "", "title": "01. Navigation"}, {"location": "exercises_02/nav/#exercise-011", "text": "Press Ctrl + J and enter 1 to go to segment #1. Source text reads Welcome to this survey. Press Enter to move to the next segment. You are now in segment #2. Press Ctrl + U to move to the next untranslated segment. You are now in segment #3. Press Enter three times in a row to go forward 3 segments. You end up in segment #6. Press Ctrl + Enter twice in a row to go backwards 2 segments. You are now in segment #4. Press Ctrl + U once to go to the next untranslated segment. You end up in segment #6 again. Notice that you have jumped segment #5, which is already translated (in pink). Tip when you tranlsate: ctrl+u when you review: enter", "title": "Exercise 01.1"}, {"location": "exercises_02/nav/#exercise-012", "text": "Press Ctrl + J and enter number 53 to go to segment #53. Source text reads: Generally speaking, please tell me how satisfied you are with public transport where you live . Press Ctrl + U to jump to the next untranslated segment. You are now on segment #58. Press Enter to move the next segment. You are now on segment #59. Oops, you haven't translated segment #58. Press Ctrl + Enter to go back to it. You are now on segment #58 again. Scroll down until you see another untranslated segment in that file. Source text reads: Generally speaking, please tell me how satisfied you are with schools and other educational facilities where you live. Double click on that segment. You are now on segment #63. Press keyboard shortcut Ctrl + J and enter number 1 to go to segment number #1. Recap In this exercise you have practiced several ways to activate a segment: Enter opens the next segment Ctrl + Enter opens the previous segment Ctrl + U opens the next untranslated segment Ctrl + J (plus the segment numberj) opens a specific segment \u2190TODO Check segment numbers after no more changes.", "title": "Exercise 01.2"}, {"location": "exercises_02/qac/", "text": "08. QA checks \u00b6 @todo: review There are two segments with tag errors, can you find them? On which segment is there a glossary error?", "title": "08. QA checks"}, {"location": "exercises_02/qac/#08-qa-checks", "text": "@todo: review There are two segments with tag errors, can you find them? On which segment is there a glossary error?", "title": "08. QA checks"}, {"location": "exercises_02/rec/", "text": "03. Reconciliation \u00b6 This section includes some bonus exercises specifically addressed to reconcilers. You may skip this section if you're not going to reconcile. Getting started \u00b6 Here's a UI preference that may be useful for you when you reconcile. In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 100 With that setting, the Matches pane will show you only the translations you need to reconcile. Please remember to restore the default value when you're not reconciling. Exercise 04.01: inserting one match \u00b6 Go to segment #62 and read it. Here comes a story for you. Source text reads Once upon a time there was a reconciler who worked in OmegaT. You have one exact match. Press Ctrl + I to insert it. Easy start. Now press Ctrl + U to move to the next unreconciled segment. Read segment #63. You have one exact match. Press Ctrl + I to translate the segment with that match. Still easy. Press Ctrl + U to move to the next unreconciled segment. Info You only see one match if \"translation 1\" and \"translation 2\" are identical. Exercise 04.02: selecting the match \u00b6 You're now on segment #64. Read segment #64. Notice that now you can see two matches because \"translation 1\" and \"translation 2\" are different now. You want to use the first translation (selected by default). Press Ctrl + I to insert match #1. Translation reads Parfois, l'une des deux traductions \u00e9tait bonne, et l'autre \u00e9tait mauvaise, donc le choix \u00e9tait clair. Press Ctrl + U to move to the next unreconciled segment. You're now on segment #65. 11. Read segment #65. 11. Here you want to use the second translation. Press Ctrl + 2 to select match #2. 12. Press Ctrl + I to insert it. Translation reads D'autres fois, la premi\u00e8re traduction \u00e9tait mauvaise, mais la seconde \u00e9tait bonne, donc le choix \u00e9tait \u00e9galement clair. Press Ctrl + U to move to the next unreconciled segment. Exersise 04.03: editing the inserted translation \u00b6 You're now on segment #66. Read segment #66. Press Ctrl + I to insert the exiting match. Edit the translation to make it a good translation. Tip: Remove the excessive SSs in parfoisSSs . Press Ctrl + U to move to the next unreconciled segment. Exercise 04.03: assembling fragments \u00b6 You are in segment #67. In match #1, select Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, Press Ctrl + I to insert the text you have selected. In match #2, select , mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. Press Ctrl + I to insert the text you have selected now. Expected result: Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. You have combined two parts of two translations to create one single reconciled version. Congrats! Finally \u00b6 Please remember to restore the default threshold to show matches: In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 50.", "title": "03. Reconciliation"}, {"location": "exercises_02/rec/#03-reconciliation", "text": "This section includes some bonus exercises specifically addressed to reconcilers. You may skip this section if you're not going to reconcile.", "title": "03. Reconciliation"}, {"location": "exercises_02/rec/#getting-started", "text": "Here's a UI preference that may be useful for you when you reconcile. In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 100 With that setting, the Matches pane will show you only the translations you need to reconcile. Please remember to restore the default value when you're not reconciling.", "title": "Getting started"}, {"location": "exercises_02/rec/#exercise-0401-inserting-one-match", "text": "Go to segment #62 and read it. Here comes a story for you. Source text reads Once upon a time there was a reconciler who worked in OmegaT. You have one exact match. Press Ctrl + I to insert it. Easy start. Now press Ctrl + U to move to the next unreconciled segment. Read segment #63. You have one exact match. Press Ctrl + I to translate the segment with that match. Still easy. Press Ctrl + U to move to the next unreconciled segment. Info You only see one match if \"translation 1\" and \"translation 2\" are identical.", "title": "Exercise 04.01: inserting one match"}, {"location": "exercises_02/rec/#exercise-0402-selecting-the-match", "text": "You're now on segment #64. Read segment #64. Notice that now you can see two matches because \"translation 1\" and \"translation 2\" are different now. You want to use the first translation (selected by default). Press Ctrl + I to insert match #1. Translation reads Parfois, l'une des deux traductions \u00e9tait bonne, et l'autre \u00e9tait mauvaise, donc le choix \u00e9tait clair. Press Ctrl + U to move to the next unreconciled segment. You're now on segment #65. 11. Read segment #65. 11. Here you want to use the second translation. Press Ctrl + 2 to select match #2. 12. Press Ctrl + I to insert it. Translation reads D'autres fois, la premi\u00e8re traduction \u00e9tait mauvaise, mais la seconde \u00e9tait bonne, donc le choix \u00e9tait \u00e9galement clair. Press Ctrl + U to move to the next unreconciled segment.", "title": "Exercise 04.02: selecting the match"}, {"location": "exercises_02/rec/#exersise-0403-editing-the-inserted-translation", "text": "You're now on segment #66. Read segment #66. Press Ctrl + I to insert the exiting match. Edit the translation to make it a good translation. Tip: Remove the excessive SSs in parfoisSSs . Press Ctrl + U to move to the next unreconciled segment.", "title": "Exersise 04.03: editing the inserted translation"}, {"location": "exercises_02/rec/#exercise-0403-assembling-fragments", "text": "You are in segment #67. In match #1, select Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, Press Ctrl + I to insert the text you have selected. In match #2, select , mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. Press Ctrl + I to insert the text you have selected now. Expected result: Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. You have combined two parts of two translations to create one single reconciled version. Congrats!", "title": "Exercise 04.03: assembling fragments"}, {"location": "exercises_02/rec/#finally", "text": "Please remember to restore the default threshold to show matches: In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 50.", "title": "Finally"}, {"location": "exercises_02/rep/", "text": "05 Repetitions \u00b6 Exercise 05.1: notice repeated segments \u00b6 Go to segment #3. Source text reads: Pretty good \u2190TODO @quiz: how many reps in total? Notice how the segment marker says that this segment is repeated three more times: . Look at the Segment Properties pane. It says \"Is duplicate: FIRST\" Right click on the segment. See how all the instances are listed and identified by their segment number. Select Segment 6 on the list to go to segment #6. Look at the Segment Properties pane for segment #6. It says \"Is duplicate: NEXT\" \u2190TODO @quiz: some question about FIRST and NEXT (feedback welcome) Right click on segment #6 to see instances listed again, go back to segment #3 again. Exercise 05.2: auto-propagate translations \u00b6 Translate segment #2. Suggested translation: \"BonNE\" -NE ending: feminine suffix, because \"Good\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #2 to go to segment #3. Notice how the translation is auto-propagated to segment #5. Translate segment #3. Suggested translation: \"MauvaisE\" -E ending: feminine suffix, because \"Bad\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #3 to confirm the translation of segment #3 and go to the next segment. Notice how the translation is auto-propagated to segment #6. Exercise 05.3: auto-propagate edits in translations \u00b6 Go to segment #5 in the project. You can see that it is translated with your auto-propagated translation. Modify the translation in segment #5 and press Ctrl + S to save the translation. Notice how the translation of segment #2 also changes. Tip Shortcut Ctrl + S saves the translation. You can also save in Project > Save , but it takes longer ;)", "title": "05 Repetitions"}, {"location": "exercises_02/rep/#05-repetitions", "text": "", "title": "05 Repetitions"}, {"location": "exercises_02/rep/#exercise-051-notice-repeated-segments", "text": "Go to segment #3. Source text reads: Pretty good \u2190TODO @quiz: how many reps in total? Notice how the segment marker says that this segment is repeated three more times: . Look at the Segment Properties pane. It says \"Is duplicate: FIRST\" Right click on the segment. See how all the instances are listed and identified by their segment number. Select Segment 6 on the list to go to segment #6. Look at the Segment Properties pane for segment #6. It says \"Is duplicate: NEXT\" \u2190TODO @quiz: some question about FIRST and NEXT (feedback welcome) Right click on segment #6 to see instances listed again, go back to segment #3 again.", "title": "Exercise 05.1: notice repeated segments"}, {"location": "exercises_02/rep/#exercise-052-auto-propagate-translations", "text": "Translate segment #2. Suggested translation: \"BonNE\" -NE ending: feminine suffix, because \"Good\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #2 to go to segment #3. Notice how the translation is auto-propagated to segment #5. Translate segment #3. Suggested translation: \"MauvaisE\" -E ending: feminine suffix, because \"Bad\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #3 to confirm the translation of segment #3 and go to the next segment. Notice how the translation is auto-propagated to segment #6.", "title": "Exercise 05.2: auto-propagate translations"}, {"location": "exercises_02/rep/#exercise-053-auto-propagate-edits-in-translations", "text": "Go to segment #5 in the project. You can see that it is translated with your auto-propagated translation. Modify the translation in segment #5 and press Ctrl + S to save the translation. Notice how the translation of segment #2 also changes. Tip Shortcut Ctrl + S saves the translation. You can also save in Project > Save , but it takes longer ;)", "title": "Exercise 05.3: auto-propagate edits in translations"}, {"location": "exercises_02/tag/", "text": "04. Tags \u00b6 Reminder Section in the guides about Tags . Exercise 04.1: insert tags \u00b6 Go to segment #10, which is untranslated. Source text reads: There are no right answers. Notice the two tags in the segment. @quiz: what do you think these are? How to we handle them: should we ignore them or reproduce them in the translation? @todo: move to quiz or remove Translate segment #10. Suggested translation: Il n\u2019y a pas de bonne r\u00e9ponse. Select the part of the translation that corresponds to \"right\" Tip: you should select bonne Press Ctrl + Space to open the auto-completer. Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cMissing tags\u201d section. The first option (i.e. | ) is selected by default. Press Enter to insert tag pair. Notice how the two paired tags are inserted around the selected text in the translation. Expected result: Il n\u2019y a pas de bonne r\u00e9ponse. Well done! Exercise 04.2: trigger the tag tooltip \u00b6 Press Ctrl + J and enter 55 to go to segment #55. Source text reads: The translator had to pay attention to formatting such as bold, italics, underline. Hover over the tags with your mouse to display a tooltip that shows the line code the tags stand for. Tip: the tooltip should display HTML tags , , etc. Exercise 04.3: see what standalone tags stand for \u00b6 Press Ctrl + J and enter 75 to go to segment #75. Source text reads if sensor detects black Notice how the segment contains one standalone tag. Hover over the tag to see what the tag stands for. The tooltip should show {{ sensor_type }} Go to the next segment, #76 Notice how this segment has two standalone tags, not two paired tags! Check what the two tags stand for. The tooltips should show {{ object1 }} and {{ object2 }} Warning The difference between two standalone tags and two paired tags is very important. Exercise 04.4: insert standalone tags \u00b6 Go to segment #77. Notice that the tag is missing in the translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: right at the end of the translation Press Ctrl + Space to launch the auto-completer and insert the tag. Go to segment #78. Notice how the tag is also missing in this translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: click between tourner \u00e0 droite jusqu'\u00e0 ce que and le capteur d\u00e9tecte le noir Use the auto-completer to insert the missing tag. Exercise 04.5: insert standalone tag as you translate \u00b6 Go to segment #79. To translate the segment and insert the tag, proceed in this way: Translate \"repeat\" Suggested translation of the first part: r\u00e9p\u00e9ter Use the auto-completer to insert the missing tag Remember the shortcut to launche the auto-completer is Ctrl + Space Translate \"times\" Suggested translation of the second part: fois You have inserted the tag as you made progress through the translation. Exercise 04.6: insert more tags \u00b6 Still in segment #39, notice how most tags are missing in the translation. Select the part of the translation that corresponds to \u201cbold\u201d Tip: le gras Press Ctrl + Space to open the \"Missing tags\" section in the auto-completer. The first line (i.e. ) is selected by default. Press Enter to insert that tag pair. Notice how the tags have been inserted around the selected text Results should be le gras Do the same for the translation of \u201citalics\u201d Tip: l\u2019italique Do the same for the translation of \u201cunderline\u201d Tip: le soulignement", "title": "04. Tags"}, {"location": "exercises_02/tag/#04-tags", "text": "Reminder Section in the guides about Tags .", "title": "04. Tags"}, {"location": "exercises_02/tag/#exercise-041-insert-tags", "text": "Go to segment #10, which is untranslated. Source text reads: There are no right answers. Notice the two tags in the segment. @quiz: what do you think these are? How to we handle them: should we ignore them or reproduce them in the translation? @todo: move to quiz or remove Translate segment #10. Suggested translation: Il n\u2019y a pas de bonne r\u00e9ponse. Select the part of the translation that corresponds to \"right\" Tip: you should select bonne Press Ctrl + Space to open the auto-completer. Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cMissing tags\u201d section. The first option (i.e. | ) is selected by default. Press Enter to insert tag pair. Notice how the two paired tags are inserted around the selected text in the translation. Expected result: Il n\u2019y a pas de bonne r\u00e9ponse. Well done!", "title": "Exercise 04.1: insert tags"}, {"location": "exercises_02/tag/#exercise-042-trigger-the-tag-tooltip", "text": "Press Ctrl + J and enter 55 to go to segment #55. Source text reads: The translator had to pay attention to formatting such as bold, italics, underline. Hover over the tags with your mouse to display a tooltip that shows the line code the tags stand for. Tip: the tooltip should display HTML tags , , etc.", "title": "Exercise 04.2: trigger the tag tooltip"}, {"location": "exercises_02/tag/#exercise-043-see-what-standalone-tags-stand-for", "text": "Press Ctrl + J and enter 75 to go to segment #75. Source text reads if sensor detects black Notice how the segment contains one standalone tag. Hover over the tag to see what the tag stands for. The tooltip should show {{ sensor_type }} Go to the next segment, #76 Notice how this segment has two standalone tags, not two paired tags! Check what the two tags stand for. The tooltips should show {{ object1 }} and {{ object2 }} Warning The difference between two standalone tags and two paired tags is very important.", "title": "Exercise 04.3: see what standalone tags stand for"}, {"location": "exercises_02/tag/#exercise-044-insert-standalone-tags", "text": "Go to segment #77. Notice that the tag is missing in the translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: right at the end of the translation Press Ctrl + Space to launch the auto-completer and insert the tag. Go to segment #78. Notice how the tag is also missing in this translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: click between tourner \u00e0 droite jusqu'\u00e0 ce que and le capteur d\u00e9tecte le noir Use the auto-completer to insert the missing tag.", "title": "Exercise 04.4: insert standalone tags"}, {"location": "exercises_02/tag/#exercise-045-insert-standalone-tag-as-you-translate", "text": "Go to segment #79. To translate the segment and insert the tag, proceed in this way: Translate \"repeat\" Suggested translation of the first part: r\u00e9p\u00e9ter Use the auto-completer to insert the missing tag Remember the shortcut to launche the auto-completer is Ctrl + Space Translate \"times\" Suggested translation of the second part: fois You have inserted the tag as you made progress through the translation.", "title": "Exercise 04.5: insert standalone tag as you translate"}, {"location": "exercises_02/tag/#exercise-046-insert-more-tags", "text": "Still in segment #39, notice how most tags are missing in the translation. Select the part of the translation that corresponds to \u201cbold\u201d Tip: le gras Press Ctrl + Space to open the \"Missing tags\" section in the auto-completer. The first line (i.e. ) is selected by default. Press Enter to insert that tag pair. Notice how the tags have been inserted around the selected text Results should be le gras Do the same for the translation of \u201citalics\u201d Tip: l\u2019italique Do the same for the translation of \u201cunderline\u201d Tip: le soulignement", "title": "Exercise 04.6: insert more tags"}, {"location": "exercises_02/tgt/", "text": "09. Download git project + commit target files + helpdesk \u00b6 NOTE FOR HELPERS This is a draft. Go to the C: drive in your computer and create a new folder called Work (or something else if you really dislike \"Work\" as a folder name). | If you don't have permissions to create a folder under C: , you can use another location such as C:\\Users\\USER\\ The path to this folder will be C:\\Work . This is where you will create your project. Copy this URL to your clipboard (select it and press Ctrl+C): https://github.com/capstanlqc-pisa/PISA_2025_fr-ZZ_Verification_OMT.git Open OmegaT, click on the Project menu, select \"Download Team Project\". Click inside the Repository URL field and press Ctrl+V to paste the URL you have copied. Click inside the New Local Project Folder field. OmegaT will propose a default path for you, if that path is not suitable you can edit it to have the project created in your preferred location Note We advise you to use an easy path to remember, such as a folder in your Documents folder Press OK, the project will be loaded after a few seconds.", "title": "09. Download git project + commit target files + helpdesk"}, {"location": "exercises_02/tgt/#09-download-git-project-commit-target-files-helpdesk", "text": "NOTE FOR HELPERS This is a draft. Go to the C: drive in your computer and create a new folder called Work (or something else if you really dislike \"Work\" as a folder name). | If you don't have permissions to create a folder under C: , you can use another location such as C:\\Users\\USER\\ The path to this folder will be C:\\Work . This is where you will create your project. Copy this URL to your clipboard (select it and press Ctrl+C): https://github.com/capstanlqc-pisa/PISA_2025_fr-ZZ_Verification_OMT.git Open OmegaT, click on the Project menu, select \"Download Team Project\". Click inside the Repository URL field and press Ctrl+V to paste the URL you have copied. Click inside the New Local Project Folder field. OmegaT will propose a default path for you, if that path is not suitable you can edit it to have the project created in your preferred location Note We advise you to use an easy path to remember, such as a folder in your Documents folder Press OK, the project will be loaded after a few seconds.", "title": "09. Download git project + commit target files + helpdesk"}, {"location": "misc/", "text": "Miscellanea \u00b6 This section contains some guides that are not specific for any role or task in particular, but that might be useful or interesting for anyone. Some guides are addressed only to people with specific responsibiilities: Bidirectionality (RTL) for RTL languages IT security for IT departments Autotext entries for productivity users", "title": "Miscellanea"}, {"location": "misc/#miscellanea", "text": "This section contains some guides that are not specific for any role or task in particular, but that might be useful or interesting for anyone. Some guides are addressed only to people with specific responsibiilities: Bidirectionality (RTL) for RTL languages IT security for IT departments Autotext entries for productivity users", "title": "Miscellanea"}, {"location": "misc/about/", "text": "About \u00b6 OmegaT \u00b6 team cApStAn \u00b6 bar cApStAn tech team \u00b6 baz", "title": "About"}, {"location": "misc/about/#about", "text": "", "title": "About"}, {"location": "misc/about/#omegat", "text": "team", "title": "OmegaT"}, {"location": "misc/about/#capstan", "text": "bar", "title": "cApStAn"}, {"location": "misc/about/#capstan-tech-team", "text": "baz", "title": "cApStAn tech team"}, {"location": "misc/autotext/", "text": "OmegaT autotext entries \u00b6 The Auto-Completer allows to insert a special character by typing a shortcut. The table below shows the list of shortcuts available in OmegaT. Shorcut Character Description \\lq \u201c upper left double quotation mark (U+201C) \\rq \u201d upper right double quotation mark (U+201D) \\lolq \u201e lower left (low-9) double quotation mark (U+201E) << \u00ab left-pointing double angle quotation mark (U+00AB) >> \u00bb right-pointing duoble angle quotation mark (U+00BB) \\laquo \u00ab left-pointing double angle quotation mark (U+00AB) \\raquo \u00bb right-pointing duoble angle quotation mark (U+00BB) \\rsquo \u2019 right single quotation mark (U+2019) \\apos \u2019 right single quotation mark (U+2019) \\lsquo \u2018 left single quotation mark (U+2018) \\x \u00d7 multiplication symbol / vector product \\times \u00d7 multiplication symbol \\nbsp non-breaking space \\tm \u2122 trademark symbol \\reg \u00ae registered (U+00AE) (tm) \u2122 trademark symbol \\sup0 \u2070 superscript 0 (U+2070) \\sup1 \u00b9 superscript 1 (U+00B9) \\sup2 \u00b2 superscript 2 (U+00B2) \\sup3 \u00b3 superscript 3 (U+00B3) \\sup4 \u2074 superscript 4 (U+2074) \\sup5 \u2075 superscript 5 (U+2075) \\sup6 \u2076 superscript 6 (U+2076) \\sup7 \u2077 superscript 7 (U+2077) \\sup8 \u2078 superscript 8 (U+2078) \\sup9 \u2079 superscript 9 (U+2079) \\supi \u2071 superscript i (U+2071) \\supn \u207f superscript n (U+207F) \\sup( \u207d superscript left parenthesis (U+207D) \\sup) \u207e superscript right parenthesis (U+207E) \\lrm \u200e LRM (U+200E) \\rlm \u200f RLM (U+200F) \\minus \u2013 n-dash (U+2013) \\ndash \u2013 n-dash (U+2013) \\mdash \u2014 m-dash (U+2014) \\pi \u03c0 mathematical pi letter \\thinspace \u2009 thin space \\ellipsis \u2026 horizontal ellipsis \\divided \u00f7 division \\middot \u00b7 interpunct/interpoint/middle dot/middot/centered dot (multiplication / scalar product) \\interpunct \u00b7 interpunct/interpoint/middle dot/middot/centered dot (multiplication / scalar product) \\bullet \u2219 bullet operator (U+2219) \\pm \u00b1 plus or minus \\le \u2264 less than or equal to \\ge \u2265 greater than or equal to \\ne \u2260 does not equal \\approx \u2248 approximately equal to \\emptyset \u2205 empty set \\sqrt \u221a square root (U+221A) \\deg \u00b0 degree \\infty \u221e infinity \\copyright \u00a9 copyright symbol \\smalle \u1d49 modifier letter small e (U+1D49) \\Omegat \u03a9 Greek capital letter omega / Ohm \\pound \u00a3 pound currency \\euro \u20ac euro currency \\cent \u00a2 cent (U+00A2) \\yen \u00a5 yen (U+00A5) \\ordf \u00aa feminine ordinal indicator (U+00AA) \\ordm \u00ba masculine ordinal indicator (U+00BA) \\shy \u00ad soft hyphen (U+00AD) \\micro \u00b5 micro (U+00B5) \\not \u00ac not sign (U+00AC) \\frac12 \u00bd vulgar fraction 1/2 / half \\frac13 \u2153 vulgar fraction 1/3 / third \\frac23 \u2154 vulgar fraction 2/3 \\frac14 \u00bc vulgar fraction 1/4 / quarter \\frac34 \u00be vulgar fraction 3/4 \\frac15 \u2155 vulgar fraction 1/5 / fifth \\frac25 \u2156 vulgar fraction 2/5 \\frac35 \u2157 vulgar fraction 3/5 \\frac45 \u2158 vulgar fraction 4/5 \\frac16 \u2159 vulgar fraction 1/6 \\frac56 \u215a vulgar fraction 5/6 \\frac17 \u2150 vulgar fraction 1/7 \\frac18 \u215b vulgar fraction 1/8 \\frac38 \u215c vulgar fraction 3/8 \\frac58 \u215d vulgar fraction 5/8 \\frac78 \u215e vulgar fraction 7/8 \\frac19 \u2151 vulgar fraction 1/9 \\frac110 \u2152 vulgar fraction 1/10 \\fracslash \u2044 fraction slash (E+2044\u209b) \\9 \u0669 nan \\8 \u0668 nan \\7 \u0667 nan \\6 \u0666 nan \\5 \u0665 nan \\4 \u0664 nan \\3 \u0663 nan \\2 \u0662 nan \\1 \u0661 nan \\0 \u0660 nan \\ar_percent \u2052 commercial minus sign (U+2052) \\nbhy \u2011 non-breaking hyphen \\ordrd \u02b3\u1d48 rd ordinal superscript \\ordnd \u207f\u1d48 nd ordinal superscript \\ordst \u02e2\u1d57 st ordinal superscript \\ordth \u1d57\u02b0 th ordinal superscript \\mathx \ud835\udc65 Mathematical italic small x \\orde \u1d49 superscript small e (for ordinals in French) \\supe \u1d49 superscript small e (for ordinals in French) \\ordde \u1d48\u1d49 superscript small de (for 2nd ordinal in French) \\supde \u1d48\u1d49 superscript small de (for 2nd ordinal in French) \\sup- \u207b superscript minus sign (U+207B) \\sup+ \u207a superscript plus sign (U+207A) \\sub0 \u2080 subscript 0 (U+2080) \\sub1 \u2081 subscript 1 (U+2081) \\sub2 \u2082 subscript 2 (U+2082) \\sub3 \u2083 subscript 3 (U+2083) \\sub4 \u2084 subscript 4 (U+2084) \\sub5 \u2085 subscript 5 (U+2085) \\sub6 \u2086 subscript 6 (U+2086) \\sub7 \u2087 subscript 7 (U+2087) \\sub8 \u2088 subscript 8 (U+2088) \\sub9 \u2089 subscript 9 (U+2089) \\subs \u209b subscript s (U+209B) The list above can also be checked in Options > Preferences > Auto-Completion > Autotext .", "title": "Autotext"}, {"location": "misc/autotext/#omegat-autotext-entries", "text": "The Auto-Completer allows to insert a special character by typing a shortcut. The table below shows the list of shortcuts available in OmegaT. Shorcut Character Description \\lq \u201c upper left double quotation mark (U+201C) \\rq \u201d upper right double quotation mark (U+201D) \\lolq \u201e lower left (low-9) double quotation mark (U+201E) << \u00ab left-pointing double angle quotation mark (U+00AB) >> \u00bb right-pointing duoble angle quotation mark (U+00BB) \\laquo \u00ab left-pointing double angle quotation mark (U+00AB) \\raquo \u00bb right-pointing duoble angle quotation mark (U+00BB) \\rsquo \u2019 right single quotation mark (U+2019) \\apos \u2019 right single quotation mark (U+2019) \\lsquo \u2018 left single quotation mark (U+2018) \\x \u00d7 multiplication symbol / vector product \\times \u00d7 multiplication symbol \\nbsp non-breaking space \\tm \u2122 trademark symbol \\reg \u00ae registered (U+00AE) (tm) \u2122 trademark symbol \\sup0 \u2070 superscript 0 (U+2070) \\sup1 \u00b9 superscript 1 (U+00B9) \\sup2 \u00b2 superscript 2 (U+00B2) \\sup3 \u00b3 superscript 3 (U+00B3) \\sup4 \u2074 superscript 4 (U+2074) \\sup5 \u2075 superscript 5 (U+2075) \\sup6 \u2076 superscript 6 (U+2076) \\sup7 \u2077 superscript 7 (U+2077) \\sup8 \u2078 superscript 8 (U+2078) \\sup9 \u2079 superscript 9 (U+2079) \\supi \u2071 superscript i (U+2071) \\supn \u207f superscript n (U+207F) \\sup( \u207d superscript left parenthesis (U+207D) \\sup) \u207e superscript right parenthesis (U+207E) \\lrm \u200e LRM (U+200E) \\rlm \u200f RLM (U+200F) \\minus \u2013 n-dash (U+2013) \\ndash \u2013 n-dash (U+2013) \\mdash \u2014 m-dash (U+2014) \\pi \u03c0 mathematical pi letter \\thinspace \u2009 thin space \\ellipsis \u2026 horizontal ellipsis \\divided \u00f7 division \\middot \u00b7 interpunct/interpoint/middle dot/middot/centered dot (multiplication / scalar product) \\interpunct \u00b7 interpunct/interpoint/middle dot/middot/centered dot (multiplication / scalar product) \\bullet \u2219 bullet operator (U+2219) \\pm \u00b1 plus or minus \\le \u2264 less than or equal to \\ge \u2265 greater than or equal to \\ne \u2260 does not equal \\approx \u2248 approximately equal to \\emptyset \u2205 empty set \\sqrt \u221a square root (U+221A) \\deg \u00b0 degree \\infty \u221e infinity \\copyright \u00a9 copyright symbol \\smalle \u1d49 modifier letter small e (U+1D49) \\Omegat \u03a9 Greek capital letter omega / Ohm \\pound \u00a3 pound currency \\euro \u20ac euro currency \\cent \u00a2 cent (U+00A2) \\yen \u00a5 yen (U+00A5) \\ordf \u00aa feminine ordinal indicator (U+00AA) \\ordm \u00ba masculine ordinal indicator (U+00BA) \\shy \u00ad soft hyphen (U+00AD) \\micro \u00b5 micro (U+00B5) \\not \u00ac not sign (U+00AC) \\frac12 \u00bd vulgar fraction 1/2 / half \\frac13 \u2153 vulgar fraction 1/3 / third \\frac23 \u2154 vulgar fraction 2/3 \\frac14 \u00bc vulgar fraction 1/4 / quarter \\frac34 \u00be vulgar fraction 3/4 \\frac15 \u2155 vulgar fraction 1/5 / fifth \\frac25 \u2156 vulgar fraction 2/5 \\frac35 \u2157 vulgar fraction 3/5 \\frac45 \u2158 vulgar fraction 4/5 \\frac16 \u2159 vulgar fraction 1/6 \\frac56 \u215a vulgar fraction 5/6 \\frac17 \u2150 vulgar fraction 1/7 \\frac18 \u215b vulgar fraction 1/8 \\frac38 \u215c vulgar fraction 3/8 \\frac58 \u215d vulgar fraction 5/8 \\frac78 \u215e vulgar fraction 7/8 \\frac19 \u2151 vulgar fraction 1/9 \\frac110 \u2152 vulgar fraction 1/10 \\fracslash \u2044 fraction slash (E+2044\u209b) \\9 \u0669 nan \\8 \u0668 nan \\7 \u0667 nan \\6 \u0666 nan \\5 \u0665 nan \\4 \u0664 nan \\3 \u0663 nan \\2 \u0662 nan \\1 \u0661 nan \\0 \u0660 nan \\ar_percent \u2052 commercial minus sign (U+2052) \\nbhy \u2011 non-breaking hyphen \\ordrd \u02b3\u1d48 rd ordinal superscript \\ordnd \u207f\u1d48 nd ordinal superscript \\ordst \u02e2\u1d57 st ordinal superscript \\ordth \u1d57\u02b0 th ordinal superscript \\mathx \ud835\udc65 Mathematical italic small x \\orde \u1d49 superscript small e (for ordinals in French) \\supe \u1d49 superscript small e (for ordinals in French) \\ordde \u1d48\u1d49 superscript small de (for 2nd ordinal in French) \\supde \u1d48\u1d49 superscript small de (for 2nd ordinal in French) \\sup- \u207b superscript minus sign (U+207B) \\sup+ \u207a superscript plus sign (U+207A) \\sub0 \u2080 subscript 0 (U+2080) \\sub1 \u2081 subscript 1 (U+2081) \\sub2 \u2082 subscript 2 (U+2082) \\sub3 \u2083 subscript 3 (U+2083) \\sub4 \u2084 subscript 4 (U+2084) \\sub5 \u2085 subscript 5 (U+2085) \\sub6 \u2086 subscript 6 (U+2086) \\sub7 \u2087 subscript 7 (U+2087) \\sub8 \u2088 subscript 8 (U+2088) \\sub9 \u2089 subscript 9 (U+2089) \\subs \u209b subscript s (U+209B) The list above can also be checked in Options > Preferences > Auto-Completion > Autotext .", "title": "OmegaT autotext entries"}, {"location": "misc/aux/", "text": "Auxiliary tools \u00b6 AutoHotKey (e.g. to insert no-break spaces) \u00b6 If you need to insert non-breaking spaces in your translation, you can use the autotext entry \\nbsp . However, if this is not convenient (e.g. because you need to insert no-break spaces veeeery often) you can use a AutoHotKey script on Windows. AutoHotKey is a standalone software and has nothing to do with OmegaT. The AutoHotKey script can be used to insert autotext (e.g. the no-break space in this case) in any other application in your system. Info AutoHotKey is a Windows-only application. If you're on Mac or Linux, you should find an alternative way to insert non-breaking spaces. Perhaps your operating system natively supports autotext without the need to install third-party apps. How to install the AutoHotKey script \u00b6 Follow these steps: Download and install AutoHotKey . Press Win+R on your keyboard, paste shell:startup and press OK. The startup folder opens up. Right-click the following link to the AHK script , select \u201cSave link as\u201d and save the nbsp.ahk script in your startup folder. In the startup folder, right-click the script file ( nbsp.ahk ) and choose Run script . This script will be run automatically the next time your machine starts. Info You're free to install AutoHotKey and use the AutoHotKey that we provide for your convenience using the steps above. However, we cannot provide support for AutoHotKey. You can find help in the AutoHotKey community. How to insert the no-break space: \u00b6 Click in the position in the text where you want to insert the non-breaking space. Press Ctrl + Shift + Space .", "title": "Auxiliary tools"}, {"location": "misc/aux/#auxiliary-tools", "text": "", "title": "Auxiliary tools"}, {"location": "misc/aux/#autohotkey-eg-to-insert-no-break-spaces", "text": "If you need to insert non-breaking spaces in your translation, you can use the autotext entry \\nbsp . However, if this is not convenient (e.g. because you need to insert no-break spaces veeeery often) you can use a AutoHotKey script on Windows. AutoHotKey is a standalone software and has nothing to do with OmegaT. The AutoHotKey script can be used to insert autotext (e.g. the no-break space in this case) in any other application in your system. Info AutoHotKey is a Windows-only application. If you're on Mac or Linux, you should find an alternative way to insert non-breaking spaces. Perhaps your operating system natively supports autotext without the need to install third-party apps.", "title": "AutoHotKey (e.g. to insert no-break spaces)"}, {"location": "misc/aux/#how-to-install-the-autohotkey-script", "text": "Follow these steps: Download and install AutoHotKey . Press Win+R on your keyboard, paste shell:startup and press OK. The startup folder opens up. Right-click the following link to the AHK script , select \u201cSave link as\u201d and save the nbsp.ahk script in your startup folder. In the startup folder, right-click the script file ( nbsp.ahk ) and choose Run script . This script will be run automatically the next time your machine starts. Info You're free to install AutoHotKey and use the AutoHotKey that we provide for your convenience using the steps above. However, we cannot provide support for AutoHotKey. You can find help in the AutoHotKey community.", "title": "How to install the AutoHotKey script"}, {"location": "misc/aux/#how-to-insert-the-no-break-space", "text": "Click in the position in the text where you want to insert the non-breaking space. Press Ctrl + Shift + Space .", "title": "How to insert the no-break space:"}, {"location": "misc/bidi/", "text": "Handling bidirectionality in OmegaT \u00b6 Text direction and text alignment \u00b6 By default, text direction in the translation editor is left to right (LTR) and text is aligned to the left. That applies to text in any language except languages written in a right-to-left (RTL) script, like Arabic, Hebrew, Syriac, etc., in which case the segment flows from right to left (RTL) and is aligned to the right. Global text direction and alignment of source and target segments is determined by the source and target languages, respectively, indicated in the project settings. Depending on the language, segments are aligned either to the left or to the right. On the other hand, while text direction at the segment level is determined by the project settings, text direction might change inside the segment depending on the script used. For example, English text in a LTR segment will flow left to right but a quotation in Arabic in that same segment will flow right to left. Since OmegaT users are only responsible for producing the translation, let\u2019s focus on what happens in target segments. Everything that follows applies to source segments too, with the difference that they are not directly editable in the translation editor in OmegaT. Bidirectionality mode \u00b6 The bidirectionality mode activates either when at least one of the two languages in the project uses a RTL script or when some text in a RTL is inserted. When the bidirectionality mode is activated, text direction is indicated by a flag on the top of the cursor. In the image below, notice how by default the cursor flag points left in a RTL segment but it may point left or right depending on the previous character: In text written in an LTR script, text flows from left to right, which means that the cursor flag points right and every character typed in LTR script always appears to the right of the previous one. That is always the case for the whole LTR segment unless it contains some fragment in an RTL script, in which case the rules for RTL text apply within that fragment. Strong and weak directionality \u00b6 In text written in an RTL script, text flows from right to left or left to right depending on the characters typed. Alphabetic characters have a RTL directionality: after each alphabetical character, the cursor flag points left, which means that if a new character is inserted, it will appear to the left of the cursor. On the other hand, numeric characters have a LTR directionality: after each number, the cursor flag points right, which means that if a new number is inserted, it will appear to the right of the cursor. Strings in LTR script will behave like numbers. Letters and numbers have a strong directionality, which means that they always flow in the same direction: letters in RTL script flow from right to left, letters in LTR flow from left to right, and numbers in any script always flow from left to right too. However, other characters like punctuation symbols do not have an intrinsic directionality of their own and will inherit the directionality of the segment (hence called of weak or neutral directionality): one same character (e.g. +, as in the image above) will flow right to left in a RTL segment, whereas it will flow left to right in a LTR segment. Orientation \u00b6 Some characters, such as quotation marks, are purely bidirectional and may also have a different orientation depending on the directionality of the segment. For example, the opening double angle quotation mark (Unicode U+00AB) points left when used in a LTR segment, but the same character points right when used in a RTL segment. In the image below, an autotext entry is used to insert that character in an LTR segment: In the image below, in turn, the same autotext entry is used to insert the same character in a LTR segment: The same thing would happen with any other double characters with neutral directionality, such as parenthesis, square brackets, curly brackets, etc. The opening character will point left or right depending on the directionality of the text stretch where it is inserted. Bidirectionality control characters \u00b6 Often the default behaviour described above is fine, but when you\u2019re mixing RTL text and LTR text or using special characters with weak directionality in RTL, you might need to use Unicode bidirectionality control characters (or bidi characters for short) to achieve the expected directionality. Bidi control characters can be found in the menu Edit > Insert Unicode Control Characters and may be used to: insert an invisible character with a certain strong directionality to force a specific position for a character with weak directionality create an embedding which works as a sort of protective environment within which text can flow in the opposite direction of the segment. These control characters are invisible, nothing is display or printed, but they change directionality. If you want to see where these characters are inserted, you can activate option View > Mark Bidirectional Algorithm Control Characters . Marks \u00b6 Let\u2019s see a few examples. Some expressions and brand names combine symbols with letters, e.g. Yahoo!, C++, C#, Hola!, Chips Ahoy!, etc. If you must write, say, \u201cC++\u201d in Arabic, you will notice that by default the + characters will appear to the left of the letter C: That is obviously incorrect. To force the correct position of the ++ characters, type C, then ++, then insert a left-to-right mark (or LRM for short) at the end. The ++ part will then be surrounded by two characters with strong LTR directionality (namely, the letter C and the LRM) and therefore will inherit the directionality of those characters and flow left to right instead of inheriting the directionality of the segment and flow right to left. See that in action in the following image: You might be tempted to type characters in reverse order: first ++, then C. Even though that might look good, that is logically wrong and could bring about issues when the text is further processed later or subjected to different uses. For example, if you type ++C in Arabic, even if it looks visually correct in the translation editor, it will not appear in search results when a user looks for \u201cC++\u201d in the Arabic document. Let alone the fact that often, if the expression is a bit complex, you\u2019ll struggle with trial and error until you obtain something that (only) looks as expected (although underneath it is wrong). Don\u2019t try to fake the looks. LRM and RLM (marks) characters are enough when you must change the directionality and position of one character only at the end or beginning of one homogeneous chunk of text. However, when the expression that must flow in the opposite direction contains several parts separated by spaces, or contains non-alphanumeric characters as well as alphanumeric characters, it\u2019s often better to use RTL or LTR embeddings. Embeddings \u00b6 The behaviour of embeddings is a bit different from that of marks. For starters, two characters must be inserted: one to start the embedding and another one to pop out of it. For example, to create a LTR embedding in an RTL segment, you would insert a left-to-right embedding (LRE) character, then the LTR text, then the pop directional formatting (PDF) character. Likewise, to create a RTL embedding in an LTR segment, you would insert a right-to-left embedding (RLE) character, then the RTL text, then the PDF character. Let\u2019s see an example. Equations, formulas and mathematical notation in general are expressions that must normally run left-to-right in bidirectional languages like Arabic or Hebrew, just like in English. Simply typing or copy-pasting an equation in Arabic will not produce the correct result, as can be seen in the image below: Instead, you should proceed in this way to create a LTR embedding: insert the LRE character, then type or insert the equation, finally insert the PDF character. See that in action: Notice how the red square rim appears around the LTR embedding right after inserting the PDF character, when the option Mark Bidirectional Algorithm Control Characters is activated in the View menu.", "title": "Bidirectionality"}, {"location": "misc/bidi/#handling-bidirectionality-in-omegat", "text": "", "title": "Handling bidirectionality in OmegaT"}, {"location": "misc/bidi/#text-direction-and-text-alignment", "text": "By default, text direction in the translation editor is left to right (LTR) and text is aligned to the left. That applies to text in any language except languages written in a right-to-left (RTL) script, like Arabic, Hebrew, Syriac, etc., in which case the segment flows from right to left (RTL) and is aligned to the right. Global text direction and alignment of source and target segments is determined by the source and target languages, respectively, indicated in the project settings. Depending on the language, segments are aligned either to the left or to the right. On the other hand, while text direction at the segment level is determined by the project settings, text direction might change inside the segment depending on the script used. For example, English text in a LTR segment will flow left to right but a quotation in Arabic in that same segment will flow right to left. Since OmegaT users are only responsible for producing the translation, let\u2019s focus on what happens in target segments. Everything that follows applies to source segments too, with the difference that they are not directly editable in the translation editor in OmegaT.", "title": "Text direction and text alignment"}, {"location": "misc/bidi/#bidirectionality-mode", "text": "The bidirectionality mode activates either when at least one of the two languages in the project uses a RTL script or when some text in a RTL is inserted. When the bidirectionality mode is activated, text direction is indicated by a flag on the top of the cursor. In the image below, notice how by default the cursor flag points left in a RTL segment but it may point left or right depending on the previous character: In text written in an LTR script, text flows from left to right, which means that the cursor flag points right and every character typed in LTR script always appears to the right of the previous one. That is always the case for the whole LTR segment unless it contains some fragment in an RTL script, in which case the rules for RTL text apply within that fragment.", "title": "Bidirectionality mode"}, {"location": "misc/bidi/#strong-and-weak-directionality", "text": "In text written in an RTL script, text flows from right to left or left to right depending on the characters typed. Alphabetic characters have a RTL directionality: after each alphabetical character, the cursor flag points left, which means that if a new character is inserted, it will appear to the left of the cursor. On the other hand, numeric characters have a LTR directionality: after each number, the cursor flag points right, which means that if a new number is inserted, it will appear to the right of the cursor. Strings in LTR script will behave like numbers. Letters and numbers have a strong directionality, which means that they always flow in the same direction: letters in RTL script flow from right to left, letters in LTR flow from left to right, and numbers in any script always flow from left to right too. However, other characters like punctuation symbols do not have an intrinsic directionality of their own and will inherit the directionality of the segment (hence called of weak or neutral directionality): one same character (e.g. +, as in the image above) will flow right to left in a RTL segment, whereas it will flow left to right in a LTR segment.", "title": "Strong and weak directionality"}, {"location": "misc/bidi/#orientation", "text": "Some characters, such as quotation marks, are purely bidirectional and may also have a different orientation depending on the directionality of the segment. For example, the opening double angle quotation mark (Unicode U+00AB) points left when used in a LTR segment, but the same character points right when used in a RTL segment. In the image below, an autotext entry is used to insert that character in an LTR segment: In the image below, in turn, the same autotext entry is used to insert the same character in a LTR segment: The same thing would happen with any other double characters with neutral directionality, such as parenthesis, square brackets, curly brackets, etc. The opening character will point left or right depending on the directionality of the text stretch where it is inserted.", "title": "Orientation"}, {"location": "misc/bidi/#bidirectionality-control-characters", "text": "Often the default behaviour described above is fine, but when you\u2019re mixing RTL text and LTR text or using special characters with weak directionality in RTL, you might need to use Unicode bidirectionality control characters (or bidi characters for short) to achieve the expected directionality. Bidi control characters can be found in the menu Edit > Insert Unicode Control Characters and may be used to: insert an invisible character with a certain strong directionality to force a specific position for a character with weak directionality create an embedding which works as a sort of protective environment within which text can flow in the opposite direction of the segment. These control characters are invisible, nothing is display or printed, but they change directionality. If you want to see where these characters are inserted, you can activate option View > Mark Bidirectional Algorithm Control Characters .", "title": "Bidirectionality control characters"}, {"location": "misc/bidi/#marks", "text": "Let\u2019s see a few examples. Some expressions and brand names combine symbols with letters, e.g. Yahoo!, C++, C#, Hola!, Chips Ahoy!, etc. If you must write, say, \u201cC++\u201d in Arabic, you will notice that by default the + characters will appear to the left of the letter C: That is obviously incorrect. To force the correct position of the ++ characters, type C, then ++, then insert a left-to-right mark (or LRM for short) at the end. The ++ part will then be surrounded by two characters with strong LTR directionality (namely, the letter C and the LRM) and therefore will inherit the directionality of those characters and flow left to right instead of inheriting the directionality of the segment and flow right to left. See that in action in the following image: You might be tempted to type characters in reverse order: first ++, then C. Even though that might look good, that is logically wrong and could bring about issues when the text is further processed later or subjected to different uses. For example, if you type ++C in Arabic, even if it looks visually correct in the translation editor, it will not appear in search results when a user looks for \u201cC++\u201d in the Arabic document. Let alone the fact that often, if the expression is a bit complex, you\u2019ll struggle with trial and error until you obtain something that (only) looks as expected (although underneath it is wrong). Don\u2019t try to fake the looks. LRM and RLM (marks) characters are enough when you must change the directionality and position of one character only at the end or beginning of one homogeneous chunk of text. However, when the expression that must flow in the opposite direction contains several parts separated by spaces, or contains non-alphanumeric characters as well as alphanumeric characters, it\u2019s often better to use RTL or LTR embeddings.", "title": "Marks"}, {"location": "misc/bidi/#embeddings", "text": "The behaviour of embeddings is a bit different from that of marks. For starters, two characters must be inserted: one to start the embedding and another one to pop out of it. For example, to create a LTR embedding in an RTL segment, you would insert a left-to-right embedding (LRE) character, then the LTR text, then the pop directional formatting (PDF) character. Likewise, to create a RTL embedding in an LTR segment, you would insert a right-to-left embedding (RLE) character, then the RTL text, then the PDF character. Let\u2019s see an example. Equations, formulas and mathematical notation in general are expressions that must normally run left-to-right in bidirectional languages like Arabic or Hebrew, just like in English. Simply typing or copy-pasting an equation in Arabic will not produce the correct result, as can be seen in the image below: Instead, you should proceed in this way to create a LTR embedding: insert the LRE character, then type or insert the equation, finally insert the PDF character. See that in action: Notice how the red square rim appears around the LTR embedding right after inserting the PDF character, when the option Mark Bidirectional Algorithm Control Characters is activated in the View menu.", "title": "Embeddings"}, {"location": "misc/faq/", "text": "FAQ \u00b6 Can I export the contents of the OmegaT project in Excel ? \u00b6 Yes. To export the contents of the OmegaT project in Excel, go to Tools > Write Project to Excel . To access the exported Excel, go to Project > Access Project Contents > Root . The Excel will be found in the script_output folder. Warning Please remember that the Excel file cannot be reimported in OmegaT. Any change you make in translations in that Excel export needs to be reflected in the OmegaT project. The size of text in the editor is too small or too big. \u00b6 To change the font size go to Options > Preferences > Font . Change the font size to one you find suitable. This has no impact on the actual font size in the target files, it only changes the display in OmegaT. How do I install the spellchecker files? \u00b6 A spelling checker is available in OmegaT and you must install the spellchecking dictionary for your language in order to use it. Follow these steps: Go to Options > Preferences > Spellchecker . Click on Install new dictionary , and a list of languages will appear. Select the appropriate language for your language version (e.g. es_AR - Spanish (Argentina) if your language is Spanish and your country is Argentina). Press the Install button. You can close the remaining pop up window. The spellchecker is now installed. Tip You can also watch the following video to see those steps in action: There is no spellchecker for my language. \u00b6 If you cannot find your language in the list when you go to Options > Preferences > Spellchecker. and then clicking on Install new dictionary , please contact the helpdesk and our team will try to find a spellchecking dictionary for you. Please note that spellchecking dictionaries might not be available for all languages. I don't have the Unpack project from OMT file item. \u00b6 If you do not see the Unpack project from OMT file option in the Project menu, please follow our OmegaT installation and setup guide (available from the Installation and setup section of these guides) and choose the third path (\"Version 5.7.1 of OmegaT is already installed in your machine\") to install the customization (again). If you still cannot see the Unpack project from OMT file option after doing that, please contact the Helpdesk. How can I correct a typo in a term in the glossary? \u00b6 Yes. Please follow these steps: Go to Project > Access Project contents > Glossaries to access your writeable glossary file. The Glossaries folder will open, which contains a file named glossary.txt . Open it in your plain text editor (e.g. Notepad): Correct any term that contains an error and Save the file. Warning Do not open the glossary file in Microsoft Word or any other similar word processor. Do we have access to the TMs from previous cycles? \u00b6 Yes. TMs (translation memories) from previous cycles should already be included in your project. You may see translations coming from them in the Matches pane, or you may find them by running a text search (see the relevant section in the guide, under Other useful features > Running concordance searches ). You may also access translations from all previous cycles of the project for your language in MemoryLn . Info If you don't see the expected translations in your OmegaT project and in MemoryLn, please contact the Helpdesk. Can I work in Trados or another CAT tool? \u00b6 The answer is no. OmegaT is specifically customized to edit the files you are working on. Such a customization is not possible in Trados or memoQ. Removing the files from the OmegaT project and translating them separately may damage the files and render them unusable for further use. How can I find translations searching by the target text? \u00b6 Proceed as follows: Press Ctrl + F on your keyboard. The search dialog opens. Type the text in the target language that you want to find. Check option \"In translation\" in the search dialog Press the Search button. I only see one 100% match when I am reconciling. \u00b6 If you matches are identical, only one of them will be displayed in the Matches pane to avoid space-consuming duplicates. If you only see one translation in the Matches pane during the reconciliation task, that means the two translators have proposed the exact same translation. Next to the 100% match you will also notice it is written \"+1 more\".", "title": "FAQ"}, {"location": "misc/faq/#faq", "text": "", "title": "FAQ"}, {"location": "misc/faq/#can-i-export-the-contents-of-the-omegat-project-in-excel", "text": "Yes. To export the contents of the OmegaT project in Excel, go to Tools > Write Project to Excel . To access the exported Excel, go to Project > Access Project Contents > Root . The Excel will be found in the script_output folder. Warning Please remember that the Excel file cannot be reimported in OmegaT. Any change you make in translations in that Excel export needs to be reflected in the OmegaT project.", "title": "Can I export the contents of the OmegaT project in Excel ?"}, {"location": "misc/faq/#the-size-of-text-in-the-editor-is-too-small-or-too-big", "text": "To change the font size go to Options > Preferences > Font . Change the font size to one you find suitable. This has no impact on the actual font size in the target files, it only changes the display in OmegaT.", "title": "The size of text in the editor is too small or too big."}, {"location": "misc/faq/#how-do-i-install-the-spellchecker-files", "text": "A spelling checker is available in OmegaT and you must install the spellchecking dictionary for your language in order to use it. Follow these steps: Go to Options > Preferences > Spellchecker . Click on Install new dictionary , and a list of languages will appear. Select the appropriate language for your language version (e.g. es_AR - Spanish (Argentina) if your language is Spanish and your country is Argentina). Press the Install button. You can close the remaining pop up window. The spellchecker is now installed. Tip You can also watch the following video to see those steps in action:", "title": "How do I install the spellchecker files?"}, {"location": "misc/faq/#there-is-no-spellchecker-for-my-language", "text": "If you cannot find your language in the list when you go to Options > Preferences > Spellchecker. and then clicking on Install new dictionary , please contact the helpdesk and our team will try to find a spellchecking dictionary for you. Please note that spellchecking dictionaries might not be available for all languages.", "title": "There is no spellchecker for my language."}, {"location": "misc/faq/#i-dont-have-the-unpack-project-from-omt-file-item", "text": "If you do not see the Unpack project from OMT file option in the Project menu, please follow our OmegaT installation and setup guide (available from the Installation and setup section of these guides) and choose the third path (\"Version 5.7.1 of OmegaT is already installed in your machine\") to install the customization (again). If you still cannot see the Unpack project from OMT file option after doing that, please contact the Helpdesk.", "title": "I don't have the Unpack project from OMT file item."}, {"location": "misc/faq/#how-can-i-correct-a-typo-in-a-term-in-the-glossary", "text": "Yes. Please follow these steps: Go to Project > Access Project contents > Glossaries to access your writeable glossary file. The Glossaries folder will open, which contains a file named glossary.txt . Open it in your plain text editor (e.g. Notepad): Correct any term that contains an error and Save the file. Warning Do not open the glossary file in Microsoft Word or any other similar word processor.", "title": "How can I correct a typo in a term in the glossary?"}, {"location": "misc/faq/#do-we-have-access-to-the-tms-from-previous-cycles", "text": "Yes. TMs (translation memories) from previous cycles should already be included in your project. You may see translations coming from them in the Matches pane, or you may find them by running a text search (see the relevant section in the guide, under Other useful features > Running concordance searches ). You may also access translations from all previous cycles of the project for your language in MemoryLn . Info If you don't see the expected translations in your OmegaT project and in MemoryLn, please contact the Helpdesk.", "title": "Do we have access to the TMs from previous cycles?"}, {"location": "misc/faq/#can-i-work-in-trados-or-another-cat-tool", "text": "The answer is no. OmegaT is specifically customized to edit the files you are working on. Such a customization is not possible in Trados or memoQ. Removing the files from the OmegaT project and translating them separately may damage the files and render them unusable for further use.", "title": "Can I work in Trados or another CAT tool?"}, {"location": "misc/faq/#how-can-i-find-translations-searching-by-the-target-text", "text": "Proceed as follows: Press Ctrl + F on your keyboard. The search dialog opens. Type the text in the target language that you want to find. Check option \"In translation\" in the search dialog Press the Search button.", "title": "How can I find translations searching by the target text?"}, {"location": "misc/faq/#i-only-see-one-100-match-when-i-am-reconciling", "text": "If you matches are identical, only one of them will be displayed in the Matches pane to avoid space-consuming duplicates. If you only see one translation in the Matches pane during the reconciliation task, that means the two translators have proposed the exact same translation. Next to the 100% match you will also notice it is written \"+1 more\".", "title": "I only see one 100% match when I am reconciling."}, {"location": "misc/fonts/", "text": "Fonts \u00b6 Installing suplemental fonts \u00b6 On Windows 10 \u00b6 If your language has special requirements (such as a double-byte writing system for some Asian languages, etc.), please follow these steps (where LANGUAGE would be your language): Go to Windows Settings > Apps > Optional Features > + Add a feature > LANGUAGE Suplemental Fonts . The install that package and then restart OmegaT. Recommended fonts in OmegaT \u00b6 Language Fonts Comment Korean UnDotum, Malgun Gothic Chinese NSimSun Source Han Sans or Source Han Serif (untested!) Amharic, Tigrinya Ebrima Thai Leelawadee UI Japanese Meiryo, NSimSun Khmer Khmer UI", "title": "Fonts"}, {"location": "misc/fonts/#fonts", "text": "", "title": "Fonts"}, {"location": "misc/fonts/#installing-suplemental-fonts", "text": "", "title": "Installing suplemental fonts"}, {"location": "misc/fonts/#recommended-fonts-in-omegat", "text": "Language Fonts Comment Korean UnDotum, Malgun Gothic Chinese NSimSun Source Han Sans or Source Han Serif (untested!) Amharic, Tigrinya Ebrima Thai Leelawadee UI Japanese Meiryo, NSimSun Khmer Khmer UI", "title": "Recommended fonts in OmegaT"}, {"location": "misc/security/", "text": "Security information \u00b6 OmegaT is the translation tool selected for the language tasks of various projects. cApStAn is responsible for customizing this tool so that it can interact optimally with the XLIFF files that will be prepared for those projects, and to streamline language tasks and reduce support requests. OmegaT will be installed from a designated installer that will be downloaded from the http://omegat.org website. The customization consists of editing or adding some settings files to the default installation and an executable developed by cApStAn will be provided to users to save them the effort of doing the customization manually. If you prefer to customize manually, that's also possible, just let us know. The purpose of the present document is to provide information relevant for IT departments who must ensure that any software installed in their organization does not pose any security threads. Updating Windows malware definitions \u00b6 Before downloading the installation files (OmegaT installer and customization utility), you should update Windows Defender's definitions. On the command prompt as administrator: Change directory to C:\\Program Files\\Windows Defender Run MpCmdRun.exe -removedefinitions -dynamicsignatures Run MpCmdRun.exe -SignatureUpdate Source: https://www.microsoft.com/en-us/wdsi/definitions Integrity verification <= UPDATE NEEDED \u00b6 You can check the integrity of the file to make sure that, after download, you have the same file that is available for download in the repository of OmegaT binaries. On Windows, you can compute the cryptographic hash values of a binary file with the File Checksum Integrity Verifier utility (check this for further information and download the utility). The correct hashes of the 64-bit installer (OmegaT_4.1.5_04_Beta_Windows_64.exe) are: SHA1: 9a7560368ca11255c4359c2ed225eb0bd7a7fbe0 MD5: 8c4dd481b715396979ba6ec5e2d1e9a8 The correct hashes of the 32-bit installer (OmegaT_4.1.5_04_Beta_Windows.exe) are: SHA1: 682e38f718ef8736ccb978f45dd13da75184648a MD5: 608417d270bc67f153d92e243abd1f96 These values are taken from the official OmegaT download page . If you obtain the same values, you can be certain that you have the same file as it\u2019s available for download and that it\u2019s safe to whitelist it. Java maintenance \u00b6 OmegaT is developed in Java and needs JRE to run. The OmegaT installers we recommend include the version of JRE that OmegaT needs, and that JRE would be uninstalled when OmegaT is uninstalled. However, in any case, as Java can be a security risk if it\u2019s not kept up to date, it\u2019s worth maintaining that version of JRE up to date after installed if necessary. Data leakage \u00b6 OmegaT can check for new versions, get MT results, get glossary matches from TaaS, download MediaWiki links and use them as source files, have remote files on HTTP, Git and SVN servers mapped locally, and then there's SVN/Git team project functionality. We're not using any of those functions in the translation of the PISA/PIAAC materials, which means we won't instruct users to configure or use them. However, it\u2019s always possible that the user unilaterally uses them. If this is a concern for the organization, OmegaT could be made to work in a complete offline manner, namely it could be started with a non-functional proxy, so it won't connect to internet at all (specifying a non-existing proxy server, e.g. 270.270, in the startup parameters in the OmegaT.l4J.ini file). In other words, it\u2019s up to the organization and their internal policy to decide how much access to the internet it must be allowed to OmegaT. Open source \u00b6 In case of any concerns about vulnerabilities in OmegaT against viruses or other malware, the source code is freely available and used to build software packages in several OS distributions. Any Java engineer can inspect the code and conduct any tests to assess its robustness and reliability. Endorsement by big organizations \u00b6 The European Commission has been promoting the use of open-source software namely within its [R&D programmes]. It is in this context that open source applications like OmegaT are being used in DGT (the European Commission\u2019s Directorate-General for Translation), alongside other commercial applications. DGT has been using OmegaT for prototyping since 2012, customizing it and extending it with some useful improvements. This information can be useful to endorse the usage of OmegaT. Source: http://ec.europa.eu/translation/portuguese/magazine/documents/folha54_ot_en.pdf OmegaT is also one of the Translator Partners of Microsoft. Please see https://www.microsoft.com/en-us/translator/business/partners/ DGT and Microsoft can attest the security of OmegaT.", "title": "IT security"}, {"location": "misc/security/#security-information", "text": "OmegaT is the translation tool selected for the language tasks of various projects. cApStAn is responsible for customizing this tool so that it can interact optimally with the XLIFF files that will be prepared for those projects, and to streamline language tasks and reduce support requests. OmegaT will be installed from a designated installer that will be downloaded from the http://omegat.org website. The customization consists of editing or adding some settings files to the default installation and an executable developed by cApStAn will be provided to users to save them the effort of doing the customization manually. If you prefer to customize manually, that's also possible, just let us know. The purpose of the present document is to provide information relevant for IT departments who must ensure that any software installed in their organization does not pose any security threads.", "title": "Security information"}, {"location": "misc/security/#updating-windows-malware-definitions", "text": "Before downloading the installation files (OmegaT installer and customization utility), you should update Windows Defender's definitions. On the command prompt as administrator: Change directory to C:\\Program Files\\Windows Defender Run MpCmdRun.exe -removedefinitions -dynamicsignatures Run MpCmdRun.exe -SignatureUpdate Source: https://www.microsoft.com/en-us/wdsi/definitions", "title": "Updating Windows malware definitions"}, {"location": "misc/security/#integrity-verification-update-needed", "text": "You can check the integrity of the file to make sure that, after download, you have the same file that is available for download in the repository of OmegaT binaries. On Windows, you can compute the cryptographic hash values of a binary file with the File Checksum Integrity Verifier utility (check this for further information and download the utility). The correct hashes of the 64-bit installer (OmegaT_4.1.5_04_Beta_Windows_64.exe) are: SHA1: 9a7560368ca11255c4359c2ed225eb0bd7a7fbe0 MD5: 8c4dd481b715396979ba6ec5e2d1e9a8 The correct hashes of the 32-bit installer (OmegaT_4.1.5_04_Beta_Windows.exe) are: SHA1: 682e38f718ef8736ccb978f45dd13da75184648a MD5: 608417d270bc67f153d92e243abd1f96 These values are taken from the official OmegaT download page . If you obtain the same values, you can be certain that you have the same file as it\u2019s available for download and that it\u2019s safe to whitelist it.", "title": "Integrity verification <= UPDATE NEEDED"}, {"location": "misc/security/#java-maintenance", "text": "OmegaT is developed in Java and needs JRE to run. The OmegaT installers we recommend include the version of JRE that OmegaT needs, and that JRE would be uninstalled when OmegaT is uninstalled. However, in any case, as Java can be a security risk if it\u2019s not kept up to date, it\u2019s worth maintaining that version of JRE up to date after installed if necessary.", "title": "Java maintenance"}, {"location": "misc/security/#data-leakage", "text": "OmegaT can check for new versions, get MT results, get glossary matches from TaaS, download MediaWiki links and use them as source files, have remote files on HTTP, Git and SVN servers mapped locally, and then there's SVN/Git team project functionality. We're not using any of those functions in the translation of the PISA/PIAAC materials, which means we won't instruct users to configure or use them. However, it\u2019s always possible that the user unilaterally uses them. If this is a concern for the organization, OmegaT could be made to work in a complete offline manner, namely it could be started with a non-functional proxy, so it won't connect to internet at all (specifying a non-existing proxy server, e.g. 270.270, in the startup parameters in the OmegaT.l4J.ini file). In other words, it\u2019s up to the organization and their internal policy to decide how much access to the internet it must be allowed to OmegaT.", "title": "Data leakage"}, {"location": "misc/security/#open-source", "text": "In case of any concerns about vulnerabilities in OmegaT against viruses or other malware, the source code is freely available and used to build software packages in several OS distributions. Any Java engineer can inspect the code and conduct any tests to assess its robustness and reliability.", "title": "Open source"}, {"location": "misc/security/#endorsement-by-big-organizations", "text": "The European Commission has been promoting the use of open-source software namely within its [R&D programmes]. It is in this context that open source applications like OmegaT are being used in DGT (the European Commission\u2019s Directorate-General for Translation), alongside other commercial applications. DGT has been using OmegaT for prototyping since 2012, customizing it and extending it with some useful improvements. This information can be useful to endorse the usage of OmegaT. Source: http://ec.europa.eu/translation/portuguese/magazine/documents/folha54_ot_en.pdf OmegaT is also one of the Translator Partners of Microsoft. Please see https://www.microsoft.com/en-us/translator/business/partners/ DGT and Microsoft can attest the security of OmegaT.", "title": "Endorsement by big organizations"}, {"location": "misc/shortcuts/", "text": "Keyboard shortcuts \u00b6 OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "misc/shortcuts/#keyboard-shortcuts", "text": "", "title": "Keyboard shortcuts"}, {"location": "misc/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "misc/tags/", "text": "Adaptation \u00b6 Adaptation Editing Proofreading \u00b6 Editing Review Reconciliation \u00b6 Reconciliation Review \u00b6 Editing Editing Review Revision \u00b6 Editing Review Translation \u00b6 Translation Verification \u00b6 Editing Verification", "title": "Tags"}, {"location": "misc/tags/#adaptation", "text": "Adaptation Editing", "title": "Adaptation"}, {"location": "misc/tags/#proofreading", "text": "Editing Review", "title": "Proofreading"}, {"location": "misc/tags/#reconciliation", "text": "Reconciliation", "title": "Reconciliation"}, {"location": "misc/tags/#review", "text": "Editing Editing Review", "title": "Review"}, {"location": "misc/tags/#revision", "text": "Editing Review", "title": "Revision"}, {"location": "misc/tags/#translation", "text": "Translation", "title": "Translation"}, {"location": "misc/tags/#verification", "text": "Editing Verification", "title": "Verification"}, {"location": "misc/tips/", "text": "Tips and tricks \u00b6 File organization \u00b6 File organization on your end is very important for the successful execution of your work. Here come some recommendations for a tidy organization. Designate a working folder for the project in your machine, and use that same location for all related tasks. We would suggest a location at a very high level in the folder structure in your computer, e.g. On Windows: C:\\Work\\CLIENT\\PROJECT or C:\\Users\\USER\\Work\\CLIENT\\PROJECT On Mac/Linux: /Users/USER/Work/CLIENT/PROJECT Inside the PROJECT 's working folder above, create the following folder structure (or something similar that fits your purposes): \u251c\u2500\u2500 00_Admin \u251c\u2500\u2500 01_Instructions \u251c\u2500\u2500 02_Tasks \u2514\u2500\u2500 03_Whatever Create your OmegaT project folders inside, say, C:\\Users\\Manolo\\Work\\cApStAn\\Globex\\02_Tasks . The final path to the OmegaT project folder should look like C:\\Users\\USER\\Work\\CLIENT\\PROJECT\\02_Tasks\\OMT-PROJ-DIR , where OMT-PROJ-DIR is (the name of) your local OmegaT project folder. How to copy-paste a URL \u00b6 Select the URL: To select the URL, click right before the first character of the URL and drag your mouse up to the end of the URL. Copy the URL: When the whole URL is highlighted (which means that it's selected), press Ctrl + C in your keyboard. Alternatively, you may right-click the highlighted text and select Copy in the contextual menu that will appear. When you copy text, it'll be stored in your clipboard. Paste the URL: Go to the location where you want to paste the URL and press Ctrl + V to insert it there.", "title": "Tips and tricks"}, {"location": "misc/tips/#tips-and-tricks", "text": "", "title": "Tips and tricks"}, {"location": "misc/tips/#file-organization", "text": "File organization on your end is very important for the successful execution of your work. Here come some recommendations for a tidy organization. Designate a working folder for the project in your machine, and use that same location for all related tasks. We would suggest a location at a very high level in the folder structure in your computer, e.g. On Windows: C:\\Work\\CLIENT\\PROJECT or C:\\Users\\USER\\Work\\CLIENT\\PROJECT On Mac/Linux: /Users/USER/Work/CLIENT/PROJECT Inside the PROJECT 's working folder above, create the following folder structure (or something similar that fits your purposes): \u251c\u2500\u2500 00_Admin \u251c\u2500\u2500 01_Instructions \u251c\u2500\u2500 02_Tasks \u2514\u2500\u2500 03_Whatever Create your OmegaT project folders inside, say, C:\\Users\\Manolo\\Work\\cApStAn\\Globex\\02_Tasks . The final path to the OmegaT project folder should look like C:\\Users\\USER\\Work\\CLIENT\\PROJECT\\02_Tasks\\OMT-PROJ-DIR , where OMT-PROJ-DIR is (the name of) your local OmegaT project folder.", "title": "File organization"}, {"location": "misc/tips/#how-to-copy-paste-a-url", "text": "Select the URL: To select the URL, click right before the first character of the URL and drag your mouse up to the end of the URL. Copy the URL: When the whole URL is highlighted (which means that it's selected), press Ctrl + C in your keyboard. Alternatively, you may right-click the highlighted text and select Copy in the contextual menu that will appear. When you copy text, it'll be stored in your clipboard. Paste the URL: Go to the location where you want to paste the URL and press Ctrl + V to insert it there.", "title": "How to copy-paste a URL"}, {"location": "misc/videos/", "text": "Training videos \u00b6 Accessing a project \u00b6 Change font size \u00b6 Spell checker \u00b6 Navigation through files \u00b6 Navigation through segments \u00b6 Autopropagation \u00b6 Alternative translations \u00b6 Searching in TM \u00b6 Using matches \u00b6 Handling tags \u00b6 QA checks: tags \u00b6 Packing for delivery \u00b6", "title": "Videos"}, {"location": "misc/videos/#training-videos", "text": "", "title": "Training videos"}, {"location": "misc/videos/#accessing-a-project", "text": "", "title": "Accessing a project"}, {"location": "misc/videos/#change-font-size", "text": "", "title": "Change font size"}, {"location": "misc/videos/#spell-checker", "text": "", "title": "Spell checker"}, {"location": "misc/videos/#navigation-through-files", "text": "", "title": "Navigation through files"}, {"location": "misc/videos/#navigation-through-segments", "text": "", "title": "Navigation through segments"}, {"location": "misc/videos/#autopropagation", "text": "", "title": "Autopropagation"}, {"location": "misc/videos/#alternative-translations", "text": "", "title": "Alternative translations"}, {"location": "misc/videos/#searching-in-tm", "text": "", "title": "Searching in TM"}, {"location": "misc/videos/#using-matches", "text": "", "title": "Using matches"}, {"location": "misc/videos/#handling-tags", "text": "", "title": "Handling tags"}, {"location": "misc/videos/#qa-checks-tags", "text": "", "title": "QA checks: tags"}, {"location": "misc/videos/#packing-for-delivery", "text": "", "title": "Packing for delivery"}, {"location": "reconciliation/", "tags": ["Reconciliation"], "text": "a.md-footer__link--prev[aria-label^=\"Previous:\"], .md-nav__icon { display: none !important; } \ud83d\udc4b Welcome to the OmegaT reconciliation guide! \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "Reconciliation"}, {"location": "reconciliation/#welcome-to-the-omegat-reconciliation-guide", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "\ud83d\udc4b Welcome to the OmegaT reconciliation guide!"}, {"location": "reconciliation/accessing-the-project/", "text": "Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Accessing a project"}, {"location": "reconciliation/accessing-the-project/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "reconciliation/accessing-the-project/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "reconciliation/accessing-the-project/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "reconciliation/accessing-the-project/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "reconciliation/accessing-the-project/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "reconciliation/accessing-the-project/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "reconciliation/creating-target-files/", "text": "Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "reconciliation/creating-target-files/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "reconciliation/creating-your-deliverable/", "text": "Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Creating your deliverable"}, {"location": "reconciliation/creating-your-deliverable/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "reconciliation/creating-your-deliverable/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "reconciliation/creating-your-deliverable/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "reconciliation/glossary/", "text": "Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Glossary"}, {"location": "reconciliation/glossary/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "reconciliation/glossary/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "reconciliation/glossary/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "reconciliation/install-and-setup/", "text": "Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "reconciliation/install-and-setup/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "reconciliation/matches/", "text": "Reconciling using matches \u00b6 During the reconciliation task, the translations from translator 1 and translator 2 are handled as matches and are displayed in the Matches pane. A reconciler's task in practice consists of one of these three options: Inserting one of the two matches (and then modify it if needed), OR Inserting part of one of the two matches and then inserting part of the other match, OR Translating the segment from scratch if none of the two matches is suitable. By default, the match from translator 1 is activated. It is the first one in the list and it is bolded . If you want to use the match from translator 2, double click on it to activate that one instead (the activated match will become bolded ). To insert the active match in full, press Ctrl + I on your keyboard. After inserting it, make any necessary changes so that it fits the segment you are reconciling. Alternatively, you can also insert only part of a match or combine several matches: Double-click the match you want to use to activate it Drag your mouse over the part of the match you wish to insert to select it Press Ctrl + I on your keyboard to insert it Select (part of) another match if appropriate or type the rest of the translation Remember It is important to make sure the final translation is harmonized as the two translators may use different terms and styles. To ensure this, make sure you preview the item prior to delivery and perform concordance searches on recurring instructions and terminology.", "title": "Matches"}, {"location": "reconciliation/matches/#reconciling-using-matches", "text": "During the reconciliation task, the translations from translator 1 and translator 2 are handled as matches and are displayed in the Matches pane. A reconciler's task in practice consists of one of these three options: Inserting one of the two matches (and then modify it if needed), OR Inserting part of one of the two matches and then inserting part of the other match, OR Translating the segment from scratch if none of the two matches is suitable. By default, the match from translator 1 is activated. It is the first one in the list and it is bolded . If you want to use the match from translator 2, double click on it to activate that one instead (the activated match will become bolded ). To insert the active match in full, press Ctrl + I on your keyboard. After inserting it, make any necessary changes so that it fits the segment you are reconciling. Alternatively, you can also insert only part of a match or combine several matches: Double-click the match you want to use to activate it Drag your mouse over the part of the match you wish to insert to select it Press Ctrl + I on your keyboard to insert it Select (part of) another match if appropriate or type the rest of the translation Remember It is important to make sure the final translation is harmonized as the two translators may use different terms and styles. To ensure this, make sure you preview the item prior to delivery and perform concordance searches on recurring instructions and terminology.", "title": "Reconciling using matches"}, {"location": "reconciliation/navigation/", "text": "Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation"}, {"location": "reconciliation/navigation/#navigation", "text": "", "title": "Navigation"}, {"location": "reconciliation/navigation/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "reconciliation/navigation/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "reconciliation/navigation/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "reconciliation/other-useful-features/", "text": "Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Other useful features"}, {"location": "reconciliation/other-useful-features/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "reconciliation/other-useful-features/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "reconciliation/other-useful-features/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "reconciliation/other-useful-features/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "reconciliation/other-useful-features/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "reconciliation/other-useful-features/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "reconciliation/other-useful-features/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "reconciliation/qa-checks/", "text": "QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "QA checks"}, {"location": "reconciliation/qa-checks/#qa-checks", "text": "", "title": "QA checks"}, {"location": "reconciliation/qa-checks/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "reconciliation/qa-checks/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "reconciliation/qa-checks/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "reconciliation/repetitions/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Repetitions"}, {"location": "reconciliation/repetitions/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "reconciliation/repetitions/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "reconciliation/repetitions/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "reconciliation/repetitions/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "reconciliation/shortcuts/", "text": "a.md-footer__link--next[aria-label^=\"Next:\"], .md-nav__icon { display: none !important; } OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "reconciliation/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "reconciliation/tags/", "text": "Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy : Fixing tag issues \u00b6 All tags you see in the source text should be present in the translation too and in the correct position. You must correct any errors that you may see when that's not the case. You may find two types of issue: A tag or tag pair is missing: in that case, the solution is simply to insert it . A tag is inserted but misplaced: the solution may be either to drag and drop single tags to the correct position, or simply to delete the tag (or tag pair) and insert it again correctly. Warning for RTL languages In right-to-left languages such as Arabic or Hebrew, moving tags will not work. Please delete the tag and insert it again if you work with any of these languages. Deleting tags \u00b6 If you have inserted a tag incorrectly and need to insert it again, double click on the tag to select it in full and press Backspace or Del on your keyboard to delete it first. Moving tags \u00b6 If you have inserted a tag in the wrong position and need to insert it somewhere else, you can simply drag and drop it. Alternatively, you can also delete it and insert it again.", "title": "Tags"}, {"location": "reconciliation/tags/#tags", "text": "", "title": "Tags"}, {"location": "reconciliation/tags/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "reconciliation/tags/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "reconciliation/tags/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "reconciliation/tags/#fixing-tag-issues", "text": "All tags you see in the source text should be present in the translation too and in the correct position. You must correct any errors that you may see when that's not the case. You may find two types of issue: A tag or tag pair is missing: in that case, the solution is simply to insert it . A tag is inserted but misplaced: the solution may be either to drag and drop single tags to the correct position, or simply to delete the tag (or tag pair) and insert it again correctly. Warning for RTL languages In right-to-left languages such as Arabic or Hebrew, moving tags will not work. Please delete the tag and insert it again if you work with any of these languages.", "title": "Fixing tag issues"}, {"location": "reconciliation/tags/#deleting-tags", "text": "If you have inserted a tag incorrectly and need to insert it again, double click on the tag to select it in full and press Backspace or Del on your keyboard to delete it first.", "title": "Deleting tags"}, {"location": "reconciliation/tags/#moving-tags", "text": "If you have inserted a tag in the wrong position and need to insert it somewhere else, you can simply drag and drop it. Alternatively, you can also delete it and insert it again.", "title": "Moving tags"}, {"location": "review/", "tags": ["Proofreading", "Revision", "Review"], "text": "a.md-footer__link--prev[aria-label^=\"Previous:\"], .md-nav__icon { display: none !important; } \ud83d\udc4b Welcome to the OmegaT proofreading guide! \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "Review"}, {"location": "review/#welcome-to-the-omegat-proofreading-guide", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "\ud83d\udc4b Welcome to the OmegaT proofreading guide!"}, {"location": "review/accessing-the-project/", "text": "Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Accessing a project"}, {"location": "review/accessing-the-project/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "review/accessing-the-project/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "review/accessing-the-project/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "review/accessing-the-project/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "review/accessing-the-project/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "review/accessing-the-project/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "review/creating-target-files/", "text": "Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "review/creating-target-files/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "review/creating-your-deliverable/", "text": "Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Creating your deliverable"}, {"location": "review/creating-your-deliverable/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "review/creating-your-deliverable/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "review/creating-your-deliverable/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "review/glossary/", "text": "Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Glossary"}, {"location": "review/glossary/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "review/glossary/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "review/glossary/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "review/install-and-setup/", "text": "Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "review/install-and-setup/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "review/matches/", "text": "Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "review/matches/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "review/navigation/", "text": "Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation"}, {"location": "review/navigation/#navigation", "text": "", "title": "Navigation"}, {"location": "review/navigation/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "review/navigation/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "review/navigation/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "review/other-useful-features/", "text": "Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Other useful features"}, {"location": "review/other-useful-features/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "review/other-useful-features/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "review/other-useful-features/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "review/other-useful-features/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "review/other-useful-features/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "review/other-useful-features/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "review/other-useful-features/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "review/qa-checks/", "text": "QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "QA checks"}, {"location": "review/qa-checks/#qa-checks", "text": "", "title": "QA checks"}, {"location": "review/qa-checks/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "review/qa-checks/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "review/qa-checks/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "review/repetitions/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Repetitions"}, {"location": "review/repetitions/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "review/repetitions/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "review/repetitions/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "review/repetitions/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "review/shortcuts/", "text": "a.md-footer__link--next[aria-label^=\"Next:\"], .md-nav__icon { display: none !important; } OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "review/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "review/tags/", "text": "Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Tags"}, {"location": "review/tags/#tags", "text": "", "title": "Tags"}, {"location": "review/tags/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "review/tags/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "review/tags/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "sp-guides/", "text": "Hello world \u00b6", "title": "Hello world"}, {"location": "sp-guides/#hello-world", "text": "", "title": "Hello world"}, {"location": "sp-guides/tec-cb-ome-adp/", "text": "Adaptation \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to enable you to perform your task. Quick walkthrough \u00b6 Download the package for adaptation and the Excel document from the portal Import the OMT package in OmegaT as described in the section The OmegaT project for adaptation will open: If you're borrowing another translation, all segments will probably appear translated in the Editor pane (the main pane of OmegaT, which contains the source text and the translation). If you are adapting from a base version (your target version is a variation of the source version), you might find it useful to automatically insert the source text in every segment . You can distinguish trend segments from non-trend segments thanks to a color coding: trend segments appear highlighted in orange. For more information about navigation between segments, please refer to the section of this user guide. If you adapt any recurring term or recurring instructions in a file, please make sure that the adaptation is done consistently. You can perform a concordance search on a specific term or phrase and OmegaT will display all segments containing it. You can go through the results to make sure that everything has been adapted consistently. For more information about concordance searches, please check the section Concordance search Installation and setup \u00b6 To install OmegaT on a computer running on Windows, please consult the . Accessing the package \u00b6 Accessing the package for the first time \u00b6 The following steps need to be performed only once per OmegaT package : when you access each package for the first time: Download the from the portal Store the in a location you will remember on your computer. Import the in OmegaT: Open OmegaT Go to Project>Import OMT package Navigate to the location where you stored the OMT package. Choose the and click on Open A pop up opens. Click Yes . Translate/Reconcile/Adapt/Review the files in the package. When you are done working for the day, close OmegaT. Access the package after import \u00b6 The next times you want to access the project in OmegaT, go to Project>Open Recent Project . The project you were working on is the first one in the list: Navigation \u00b6 Navigation between the different panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane . The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show you if a repeated segment was translated differently. Navigation between the different files \u00b6 If the project contains multiple files, they are listed in the Project Files pane . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files pane. You can also see the name of the file that is open in the Editor pane's title bar. Navigation between the different segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working in. When a translation is inserted, it will appear below the source text. Press the Enter key on your keyboard to go to the next segment. A segment can also be activated by double clicking on it. It then becomes green. In OmegaT, a color code will help you find your way around between the different segments: Green = the segment you are working in (active segment) Grey = translated segment. The translation is displayed below the source text. Orange = pretranslated and locked segment (e.g. trend). If you want to make a change to a trend segment, document it in the monitoring document but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. All segments should appear translated in a project for adaptation either in gray or in orange (trend) and the translation should be displayed below the source. If you notice an untranslated segment in * *, please provide a translation and document it in the monitoring document. Handling tags ( Ctrl + T ) \u00b6 Recognizing tags \u00b6 If you are in a segment which contains tags, you will recognize them because they are in red font . There are two types of tags - standalone tags and double tags: Standalone tags = a single tag with a precise role (e.g. tag which introduces a new paragraph in HTML) Double tags are composed of an opening and a closing tag, such as the HTML tags for making text bold, italic, underlined, etc. Double tags affect the text between them and you need to ensure they are positioned around the exact same words in the source and in the translation. Fixing tag issues \u00b6 For your language task, all tags should be present in the translation. What is important is to correct potential errors that you may see. In the screenshot below, in the source segment the **** are around the letter \"n\" while in the target they are around the word \"which\" . To correct this issue, you would have to perform the following steps: double click on the first incorrectly inserted tag in the target segment to select it and press Backspace on your keyboard to delete it repeat the operation until you deleted all incorrectly inserted tags place your mouse where the first tag should be correctly inserted and press Ctrl + T on your keyboard to insert the first tag insert all other missing tags. Please note that tags are inserted in the order of their appearance in the source segment. Most common HTML tags \u00b6 Below you will find the most common HTML tags you may encounter. Using Fuzzy matches ( Ctrl + I ) \u00b6 Any changes you make during adaptation are saved in the translation memory of the project. When you activate a segment which is similar to one you have already adapted, you may see suggestions in the fuzzy matches pane. The source in the fuzzy matches pane shows the difference between the active segment and the previous translation in \u201ctrack changes\u201d mode like in Word: Parts that do not appear in the active segment are in ~~~~ Parts that are added are in ____ Do not hesitate to consult the fuzzy matches pane to ensure you make the same changes consistently throughout. You can insert a fuzzy match or a part of a fuzzy match with Ctrl + I : Activate the fuzzy match you wish to use by double clicking on it. With your mouse, select the part you wish to insert. Press Ctrl + I on your keyboard to insert it. Do not forget to delete all unnecessary/remaining text from the target segment to ensure everything is correct. Using the Glossary \u00b6 OmegaT supports glossaries. Your package may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Inserting glossary terms \u00b6 When you arrive in an active segment which contains a glossary term, the respective term is underlined in blue in the source segment. You will see the suggested target term in the Glossary pane , on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding terms to the glossary \u00b6 If in the project you are working on you keep adapting the same term over and over you may wish to add it to the glossary to ensure you adapt consistently throughout. In the active segment,** select the term** you want to insert with your mouse Right click and choose Add glossary entry from the contextual menu A pop-up window will open Enter the Target term and press the OK button. Handling repeated segments \u00b6 Some segments are identical to each other. They are called \u201c repeated segments \u201d and their translation is autopropagated . Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because it has gray font. When a repeated segment is active, the segment number will indicate how many repetitions exist: If you right click on a repeated segment, the contextual menu will point out the other occurrences of a repeated segment. It can be useful to jump to them (by selecting them from the contextual menu) to see the different contexts in which a repeated segment appears. Autopropagation \u00b6 If you edit the translation of a repeated segment, by default, the changes will be automatically reflected in all the repetitions. This happens in the same file, but also in all the files of the OmegaT package. Create alternative translation \u00b6 In some cases, you may not wish to modify the translation of all repeated segments. Due to a different context, you may need to change only ONE of the repeated segments: Right click on the segment Choose Create Alternative Translation from the contextual menu Change the translation of your active segment and then either press Ctrl + S or move to the next one. If you return on the repeated segment, you will see the different translations appear in the Multiple Translations pane. Other useful features \u00b6 Using the character table \u00b6 Special characters can be inserted with the Special Characters Table. Special characters can be: quotation marks: \u00ab\u00bb, \u201e\u201c, \u2018\u2019, etc. mathematical symbols: \u00d7, \u03c0, \u00f7, \u2264, \u2260, \u221a, etc. other characters: \u00ae, \u2122 When you arrive in a segment in which you need to insert a special character, perform the following steps: Press Ctrl + Space on your keyboard several times until you reach the special characters table. Select the character you want to insert Press Enter and continue editing your segment. Inserting non-breaking spaces \u00b6 In order to insert non-breaking spaces in OmegaT, please make sure you have installed Auto Hot Key . If you haven't installed it yet, please check the Third Party Tools section of the OmegaT Installation guide Once Auto Hot Key is installed, you can insert non-breaking spaces with the same keyboard shortcut as in Word: Ctrl + Shift + Space . You can recognize a non breaking space because it is gray. Performing concordance searches \u00b6 A concordance search allows you to look for words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word you want to search for with your mouse. Press Ctrl + F on your keyboard. The Search window will open. Press Search. The results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the target translation at the right place. TIP: There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting. Performing QA checks in OmegaT \u00b6 Completion check \u00b6 All segments of the OmegaT package must have a translation. To ensure that is the case, please check for completion prior to delivery: Go to Project>Project Files The project files pane will open OK: If the Number of unique segments is equal to the number of Translated unique segments . NOT OK : the Number of unique segments is different from the number of Translated unique segments . To correct: Close the Project Files Pane Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . When the cursor stops moving from the active segment then all segments have a translation. Recheck for completion, to make sure by opening the Project Files pane. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools>Check Issues . A pop up window will open. By default, other types of checks (Spelling, Terminology, LanguageTool) are ticked. If you want to check for issues related to tags before performing the rest of the checks, you can untick them. You will notice that the Tag Issues box cannot be unticked. Press OK . An error report will open. Go through the issues one by one: Correct the issue by clicking on Jump to Segment . You will arrive at the appropriate segment in the editor pane. Place your cursor where the missing tag needs to be inserted and press Ctrl + T to insert the missing tag. Press Enter to move to the next segment. Open the Error report again. It has automatically refreshed. Finish going through the issues. TIP : If in the source there are tags that you do not use in your language which are present in the source segment, to avoid having false positives in the error report, you can insert them at the end of the segment. They would not have an impact on any text. Caution Please do not click on \"Apply fix\", fix each issue manually. Glossary adherence check \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools>Check Issues Make sure the box next to Terminology Issues is ticked Press** OK.** An error report will open Go through the issues one by one and jump to segment to correct the eventual error if needed. Creating target files \u00b6 Press Ctrl + Shift + D to create the target file you were working on. This will allow you to preview the translated file with your changes. To access the file, go to Project>Access Project Contents>Target Files . A window with the contents of the \"target\" folder will open. Find the file you were working on, if there are several files and preview it to read the translation in context. Delivering the project \u00b6 Once you have finished editing the OmegaT package and have performed the appropriate Q&A checks, you need to Export the . Go to Project>Export OMT Package A pop up window will open. Click Save Press OK in the Pop-up window notifying that the package was successfully created. You will be automatically directed to the location the exported package is stored. You will recognize the package because it has the extension OMT. It should be the 4th from the bottom. This is the file you have to deliver. OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Adaptation"}, {"location": "sp-guides/tec-cb-ome-adp/#adaptation", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to enable you to perform your task.", "title": "Adaptation"}, {"location": "sp-guides/tec-cb-ome-adp/#quick-walkthrough", "text": "Download the package for adaptation and the Excel document from the portal Import the OMT package in OmegaT as described in the section The OmegaT project for adaptation will open: If you're borrowing another translation, all segments will probably appear translated in the Editor pane (the main pane of OmegaT, which contains the source text and the translation). If you are adapting from a base version (your target version is a variation of the source version), you might find it useful to automatically insert the source text in every segment . You can distinguish trend segments from non-trend segments thanks to a color coding: trend segments appear highlighted in orange. For more information about navigation between segments, please refer to the section of this user guide. If you adapt any recurring term or recurring instructions in a file, please make sure that the adaptation is done consistently. You can perform a concordance search on a specific term or phrase and OmegaT will display all segments containing it. You can go through the results to make sure that everything has been adapted consistently. For more information about concordance searches, please check the section Concordance search", "title": "Quick walkthrough"}, {"location": "sp-guides/tec-cb-ome-adp/#installation-and-setup", "text": "To install OmegaT on a computer running on Windows, please consult the .", "title": "Installation and setup"}, {"location": "sp-guides/tec-cb-ome-adp/#accessing-the-package", "text": "", "title": "Accessing the package"}, {"location": "sp-guides/tec-cb-ome-adp/#accessing-the-package-for-the-first-time", "text": "The following steps need to be performed only once per OmegaT package : when you access each package for the first time: Download the from the portal Store the in a location you will remember on your computer. Import the in OmegaT: Open OmegaT Go to Project>Import OMT package Navigate to the location where you stored the OMT package. Choose the and click on Open A pop up opens. Click Yes . Translate/Reconcile/Adapt/Review the files in the package. When you are done working for the day, close OmegaT.", "title": "Accessing the package for the first time"}, {"location": "sp-guides/tec-cb-ome-adp/#access-the-package-after-import", "text": "The next times you want to access the project in OmegaT, go to Project>Open Recent Project . The project you were working on is the first one in the list:", "title": "Access the package after import"}, {"location": "sp-guides/tec-cb-ome-adp/#navigation", "text": "", "title": "Navigation"}, {"location": "sp-guides/tec-cb-ome-adp/#navigation-between-the-different-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane . The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show you if a repeated segment was translated differently.", "title": "Navigation between the different panes"}, {"location": "sp-guides/tec-cb-ome-adp/#navigation-between-the-different-files", "text": "If the project contains multiple files, they are listed in the Project Files pane . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files pane. You can also see the name of the file that is open in the Editor pane's title bar.", "title": "Navigation between the different files"}, {"location": "sp-guides/tec-cb-ome-adp/#navigation-between-the-different-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working in. When a translation is inserted, it will appear below the source text. Press the Enter key on your keyboard to go to the next segment. A segment can also be activated by double clicking on it. It then becomes green. In OmegaT, a color code will help you find your way around between the different segments: Green = the segment you are working in (active segment) Grey = translated segment. The translation is displayed below the source text. Orange = pretranslated and locked segment (e.g. trend). If you want to make a change to a trend segment, document it in the monitoring document but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. All segments should appear translated in a project for adaptation either in gray or in orange (trend) and the translation should be displayed below the source. If you notice an untranslated segment in * *, please provide a translation and document it in the monitoring document.", "title": "Navigation between the different segments"}, {"location": "sp-guides/tec-cb-ome-adp/#handling-tags-ctrlt", "text": "", "title": "Handling tags (Ctrl+T)"}, {"location": "sp-guides/tec-cb-ome-adp/#recognizing-tags", "text": "If you are in a segment which contains tags, you will recognize them because they are in red font . There are two types of tags - standalone tags and double tags: Standalone tags = a single tag with a precise role (e.g. tag which introduces a new paragraph in HTML) Double tags are composed of an opening and a closing tag, such as the HTML tags for making text bold, italic, underlined, etc. Double tags affect the text between them and you need to ensure they are positioned around the exact same words in the source and in the translation.", "title": "Recognizing tags"}, {"location": "sp-guides/tec-cb-ome-adp/#fixing-tag-issues", "text": "For your language task, all tags should be present in the translation. What is important is to correct potential errors that you may see. In the screenshot below, in the source segment the **** are around the letter \"n\" while in the target they are around the word \"which\" . To correct this issue, you would have to perform the following steps: double click on the first incorrectly inserted tag in the target segment to select it and press Backspace on your keyboard to delete it repeat the operation until you deleted all incorrectly inserted tags place your mouse where the first tag should be correctly inserted and press Ctrl + T on your keyboard to insert the first tag insert all other missing tags. Please note that tags are inserted in the order of their appearance in the source segment.", "title": "Fixing tag issues"}, {"location": "sp-guides/tec-cb-ome-adp/#most-common-html-tags", "text": "Below you will find the most common HTML tags you may encounter.", "title": "Most common HTML tags"}, {"location": "sp-guides/tec-cb-ome-adp/#using-fuzzy-matches-ctrli", "text": "Any changes you make during adaptation are saved in the translation memory of the project. When you activate a segment which is similar to one you have already adapted, you may see suggestions in the fuzzy matches pane. The source in the fuzzy matches pane shows the difference between the active segment and the previous translation in \u201ctrack changes\u201d mode like in Word: Parts that do not appear in the active segment are in ~~~~ Parts that are added are in ____ Do not hesitate to consult the fuzzy matches pane to ensure you make the same changes consistently throughout. You can insert a fuzzy match or a part of a fuzzy match with Ctrl + I : Activate the fuzzy match you wish to use by double clicking on it. With your mouse, select the part you wish to insert. Press Ctrl + I on your keyboard to insert it. Do not forget to delete all unnecessary/remaining text from the target segment to ensure everything is correct.", "title": "Using Fuzzy matches (Ctrl+I)"}, {"location": "sp-guides/tec-cb-ome-adp/#using-the-glossary", "text": "OmegaT supports glossaries. Your package may already contain a glossary with key terms, but you can also add terms to the glossary yourself.", "title": "Using the Glossary"}, {"location": "sp-guides/tec-cb-ome-adp/#inserting-glossary-terms", "text": "When you arrive in an active segment which contains a glossary term, the respective term is underlined in blue in the source segment. You will see the suggested target term in the Glossary pane , on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting glossary terms"}, {"location": "sp-guides/tec-cb-ome-adp/#adding-terms-to-the-glossary", "text": "If in the project you are working on you keep adapting the same term over and over you may wish to add it to the glossary to ensure you adapt consistently throughout. In the active segment,** select the term** you want to insert with your mouse Right click and choose Add glossary entry from the contextual menu A pop-up window will open Enter the Target term and press the OK button.", "title": "Adding terms to the glossary"}, {"location": "sp-guides/tec-cb-ome-adp/#handling-repeated-segments", "text": "Some segments are identical to each other. They are called \u201c repeated segments \u201d and their translation is autopropagated .", "title": "Handling repeated segments"}, {"location": "sp-guides/tec-cb-ome-adp/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because it has gray font. When a repeated segment is active, the segment number will indicate how many repetitions exist: If you right click on a repeated segment, the contextual menu will point out the other occurrences of a repeated segment. It can be useful to jump to them (by selecting them from the contextual menu) to see the different contexts in which a repeated segment appears.", "title": "Identifying repeated segments"}, {"location": "sp-guides/tec-cb-ome-adp/#autopropagation", "text": "If you edit the translation of a repeated segment, by default, the changes will be automatically reflected in all the repetitions. This happens in the same file, but also in all the files of the OmegaT package.", "title": "Autopropagation"}, {"location": "sp-guides/tec-cb-ome-adp/#create-alternative-translation", "text": "In some cases, you may not wish to modify the translation of all repeated segments. Due to a different context, you may need to change only ONE of the repeated segments: Right click on the segment Choose Create Alternative Translation from the contextual menu Change the translation of your active segment and then either press Ctrl + S or move to the next one. If you return on the repeated segment, you will see the different translations appear in the Multiple Translations pane.", "title": "Create alternative translation"}, {"location": "sp-guides/tec-cb-ome-adp/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "sp-guides/tec-cb-ome-adp/#using-the-character-table", "text": "Special characters can be inserted with the Special Characters Table. Special characters can be: quotation marks: \u00ab\u00bb, \u201e\u201c, \u2018\u2019, etc. mathematical symbols: \u00d7, \u03c0, \u00f7, \u2264, \u2260, \u221a, etc. other characters: \u00ae, \u2122 When you arrive in a segment in which you need to insert a special character, perform the following steps: Press Ctrl + Space on your keyboard several times until you reach the special characters table. Select the character you want to insert Press Enter and continue editing your segment.", "title": "Using the character table"}, {"location": "sp-guides/tec-cb-ome-adp/#inserting-non-breaking-spaces", "text": "In order to insert non-breaking spaces in OmegaT, please make sure you have installed Auto Hot Key . If you haven't installed it yet, please check the Third Party Tools section of the OmegaT Installation guide Once Auto Hot Key is installed, you can insert non-breaking spaces with the same keyboard shortcut as in Word: Ctrl + Shift + Space . You can recognize a non breaking space because it is gray.", "title": "Inserting non-breaking spaces"}, {"location": "sp-guides/tec-cb-ome-adp/#performing-concordance-searches", "text": "A concordance search allows you to look for words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word you want to search for with your mouse. Press Ctrl + F on your keyboard. The Search window will open. Press Search. The results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the target translation at the right place. TIP: There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Performing concordance searches"}, {"location": "sp-guides/tec-cb-ome-adp/#performing-qa-checks-in-omegat", "text": "", "title": "Performing QA checks in OmegaT"}, {"location": "sp-guides/tec-cb-ome-adp/#completion-check", "text": "All segments of the OmegaT package must have a translation. To ensure that is the case, please check for completion prior to delivery: Go to Project>Project Files The project files pane will open OK: If the Number of unique segments is equal to the number of Translated unique segments . NOT OK : the Number of unique segments is different from the number of Translated unique segments . To correct: Close the Project Files Pane Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . When the cursor stops moving from the active segment then all segments have a translation. Recheck for completion, to make sure by opening the Project Files pane.", "title": "Completion check"}, {"location": "sp-guides/tec-cb-ome-adp/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools>Check Issues . A pop up window will open. By default, other types of checks (Spelling, Terminology, LanguageTool) are ticked. If you want to check for issues related to tags before performing the rest of the checks, you can untick them. You will notice that the Tag Issues box cannot be unticked. Press OK . An error report will open. Go through the issues one by one: Correct the issue by clicking on Jump to Segment . You will arrive at the appropriate segment in the editor pane. Place your cursor where the missing tag needs to be inserted and press Ctrl + T to insert the missing tag. Press Enter to move to the next segment. Open the Error report again. It has automatically refreshed. Finish going through the issues. TIP : If in the source there are tags that you do not use in your language which are present in the source segment, to avoid having false positives in the error report, you can insert them at the end of the segment. They would not have an impact on any text. Caution Please do not click on \"Apply fix\", fix each issue manually.", "title": "Check and fix tags"}, {"location": "sp-guides/tec-cb-ome-adp/#glossary-adherence-check", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools>Check Issues Make sure the box next to Terminology Issues is ticked Press** OK.** An error report will open Go through the issues one by one and jump to segment to correct the eventual error if needed.", "title": "Glossary adherence check"}, {"location": "sp-guides/tec-cb-ome-adp/#creating-target-files", "text": "Press Ctrl + Shift + D to create the target file you were working on. This will allow you to preview the translated file with your changes. To access the file, go to Project>Access Project Contents>Target Files . A window with the contents of the \"target\" folder will open. Find the file you were working on, if there are several files and preview it to read the translation in context.", "title": "Creating target files"}, {"location": "sp-guides/tec-cb-ome-adp/#delivering-the-project", "text": "Once you have finished editing the OmegaT package and have performed the appropriate Q&A checks, you need to Export the . Go to Project>Export OMT Package A pop up window will open. Click Save Press OK in the Pop-up window notifying that the package was successfully created. You will be automatically directed to the location the exported package is stored. You will recognize the package because it has the extension OMT. It should be the 4th from the bottom. This is the file you have to deliver.", "title": "Delivering the project"}, {"location": "sp-guides/tec-cb-ome-adp/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "sp-guides/tec-cb-ome-prf/", "text": "Proofreading \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to enable you to perform your task. Quick walkthrough for proofreading \u00b6 Download the OMT package and the Excel file containing the translation and adaptation guidelines from Plunet. Import the OMT package in OmegaT. To see how to do so, please read the section Accessing the package for the first time . Create the target files for preview on the portal. To see how to create the files, please refer to the section Creating target files Connect to the PISA portal with the credentials provided in the dispatch mail: PISA PORTAL Go to the Translations TAB Drag and drop the target XLIFF you wish to preview and press the Preview chosen XLIFF Button The XLIFF for preview in your language opens. You can also preview the source text by clicking on Preview eng-ZZZ button Read the items in your language on the portal. Focus on the following: Fluency Grammar & Typos Punctuation To navigate from one screen to the other and read through the full item press the \"Next\" arrows on the screen If you notice something you wish to correct, copy the sentence/part of the sentence in your language from the preview In OmegaT, press Ctrl + F on your keyboard. The search dialog opens. Paste the sentence/part of sentence you copied from the portal and press the Search button. Double click on the result to go to the appropriate segment in OmegaT. In the screenshot below, the segment number is 40 Before you make any changes, double check in the Excel file if there is no guideline for that segment, or if there is no comment from the reconciler. The changes you make cannot contradict a guideline or the reconciler's decision. If you are in a case where you believe something should be changed and it goes against the guidelines, please send us an e-mail to explain the situation. Repeat this process for all files in your batch. When you are done, create the target OMT package for delivery Delivering the project and upload it on Plunet together with the Excel for documentation. Accessing the package \u00b6 Accessing the package for the first time \u00b6 The following steps need to be performed only once per OmegaT package : when you access each package for the first time: Download the from the portal Store the in a location you will remember on your computer. Import the in OmegaT: Open OmegaT Go to Project>Import OMT package Navigate to the location where you stored the OMT package. Choose the and click on Open A pop up opens. Click Yes . Translate/Reconcile/Adapt/Review the files in the package. When you are done working for the day, close OmegaT. Access the package after import \u00b6 The next times you want to access the project in OmegaT, go to Project>Open Recent Project . The project you were working on is the first one in the list: Navigation \u00b6 Navigation between the different panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane . The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show you if a repeated segment was translated differently. Navigation between the different files \u00b6 If the project contains multiple files, they are listed in the Project Files pane . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files pane. You can also see the name of the file that is open in the Editor pane's title bar. Navigation between the different segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working in. The translation is displayed right below the source text. Press the Enter key on your keyboard to go to the next segment. A segment can also be activated by double clicking on it. It then becomes green. In OmegaT, a color code will help you find your way around between the different segments: Green = the segment you are working in (active segment) Grey = translated segment. The translation is displayed below the source text. Orange = pretranslated and locked segment (e.g. trend). These segments cannot be edited in OmegaT. All segments should appear translated in a project for proofreading. If you notice an untranslated segment in * *, please contact cApStAn's project managers to see how it should be handled. Recognizing tags \u00b6 If you are in a segment which contains tags, you will recognize them because they are in red font . There are two types of tags - standalone tags and double tags: Standalone tags = a single tag with a precise role (e.g. tag which introduces a new paragraph in HTML) Double tags are composed of an opening and a closing tag, such as the HTML tags for making text bold, italic, underlined, etc. Double tags affect the text between them and you need to ensure they are positioned around the exact same words in the source and in the translation. Fixing tag issues \u00b6 For your language task, all tags should be present in the translation. What is important is to correct potential errors that you may see. In the screenshot below, in the source segment the **** are around the letter \"n\" while in the target they are around the word \"which\" . To correct this issue, you would have to perform the following steps: double click on the first incorrectly inserted tag in the target segment to select it and press Backspace on your keyboard to delete it repeat the operation until you deleted all incorrectly inserted tags place your mouse where the first tag should be correctly inserted and press Ctrl + T on your keyboard to insert the first tag insert all other missing tags. Please note that tags are inserted in the order of their appearance in the source segment. Handling repeated segments \u00b6 Some segments are identical to each other. They are called \u201c repeated segments \u201d and their translation is autopropagated . Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because it has gray font. When a repeated segment is active, the segment number will indicate how many repetitions exist: If you right click on a repeated segment, the contextual menu will point out the other occurrences of a repeated segment. It can be useful to jump to them (by selecting them from the contextual menu) to see the different contexts in which a repeated segment appears. Autopropagation \u00b6 If you edit the translation of a repeated segment, by default, the changes will be automatically reflected in all the repetitions. This happens in the same file, but also in all the files of the OmegaT package. Create alternative translation \u00b6 In some cases, you may not wish to modify the translation of all repeated segments. Due to a different context, you may need to change only ONE of the repeated segments: Right click on the segment Choose Create Alternative Translation from the contextual menu Change the translation of your active segment and then either press Ctrl + S or move to the next one. If you return on the repeated segment, you will see the different translations appear in the Multiple Translations pane. Other useful features \u00b6 Using the character table \u00b6 Special characters can be inserted with the Special Characters Table. Special characters can be: quotation marks: \u00ab\u00bb, \u201e\u201c, \u2018\u2019, etc. mathematical symbols: \u00d7, \u03c0, \u00f7, \u2264, \u2260, \u221a, etc. other characters: \u00ae, \u2122 When you arrive in a segment in which you need to insert a special character, perform the following steps: Press Ctrl + Space on your keyboard several times until you reach the special characters table. Select the character you want to insert Press Enter and continue editing your segment. Inserting non-breaking spaces \u00b6 In order to insert non-breaking spaces in OmegaT, please make sure you have installed Auto Hot Key . If you haven't installed it yet, please check the Third Party Tools section of the OmegaT Installation guide Once Auto Hot Key is installed, you can insert non-breaking spaces with the same keyboard shortcut as in Word: Ctrl + Shift + Space . You can recognize a non breaking space because it is gray. Performing concordance searches \u00b6 A concordance search allows you to look for words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word you want to search for with your mouse. Press Ctrl + F on your keyboard. The Search window will open. Press Search. The results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the target translation at the right place. TIP: There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting. Performing QA checks in OmegaT \u00b6 Completion check \u00b6 All segments of the OmegaT package must have a translation. To ensure that is the case, please check for completion prior to delivery: Go to Project>Project Files The project files pane will open OK: If the Number of unique segments is equal to the number of Translated unique segments . NOT OK : the Number of unique segments is different from the number of Translated unique segments . To correct: Close the Project Files Pane Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . When the cursor stops moving from the active segment then all segments have a translation. Recheck for completion, to make sure by opening the Project Files pane. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools>Check Issues . A pop up window will open. By default, other types of checks (Spelling, Terminology, LanguageTool) are ticked. If you want to check for issues related to tags before performing the rest of the checks, you can untick them. You will notice that the Tag Issues box cannot be unticked. Press OK . An error report will open. Go through the issues one by one: Correct the issue by clicking on Jump to Segment . You will arrive at the appropriate segment in the editor pane. Place your cursor where the missing tag needs to be inserted and press Ctrl + T to insert the missing tag. Press Enter to move to the next segment. Open the Error report again. It has automatically refreshed. Finish going through the issues. TIP : If in the source there are tags that you do not use in your language which are present in the source segment, to avoid having false positives in the error report, you can insert them at the end of the segment. They would not have an impact on any text. Caution Please do not click on \"Apply fix\", fix each issue manually. Creating target files \u00b6 Press Ctrl + Shift + D to create the target file you were working on. This will allow you to preview the translated file with your changes. To access the file, go to Project>Access Project Contents>Target Files . A window with the contents of the \"target\" folder will open. Find the file you were working on, if there are several files and preview it to read the translation in context. Delivering the project \u00b6 Once you have finished editing the OmegaT package and have performed the appropriate Q&A checks, you need to Export the . Go to Project>Export OMT Package A pop up window will open. Click Save Press OK in the Pop-up window notifying that the package was successfully created. You will be automatically directed to the location the exported package is stored. You will recognize the package because it has the extension OMT. It should be the 4th from the bottom. This is the file you have to deliver. OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Proofreading"}, {"location": "sp-guides/tec-cb-ome-prf/#proofreading", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to enable you to perform your task.", "title": "Proofreading"}, {"location": "sp-guides/tec-cb-ome-prf/#quick-walkthrough-for-proofreading", "text": "Download the OMT package and the Excel file containing the translation and adaptation guidelines from Plunet. Import the OMT package in OmegaT. To see how to do so, please read the section Accessing the package for the first time . Create the target files for preview on the portal. To see how to create the files, please refer to the section Creating target files Connect to the PISA portal with the credentials provided in the dispatch mail: PISA PORTAL Go to the Translations TAB Drag and drop the target XLIFF you wish to preview and press the Preview chosen XLIFF Button The XLIFF for preview in your language opens. You can also preview the source text by clicking on Preview eng-ZZZ button Read the items in your language on the portal. Focus on the following: Fluency Grammar & Typos Punctuation To navigate from one screen to the other and read through the full item press the \"Next\" arrows on the screen If you notice something you wish to correct, copy the sentence/part of the sentence in your language from the preview In OmegaT, press Ctrl + F on your keyboard. The search dialog opens. Paste the sentence/part of sentence you copied from the portal and press the Search button. Double click on the result to go to the appropriate segment in OmegaT. In the screenshot below, the segment number is 40 Before you make any changes, double check in the Excel file if there is no guideline for that segment, or if there is no comment from the reconciler. The changes you make cannot contradict a guideline or the reconciler's decision. If you are in a case where you believe something should be changed and it goes against the guidelines, please send us an e-mail to explain the situation. Repeat this process for all files in your batch. When you are done, create the target OMT package for delivery Delivering the project and upload it on Plunet together with the Excel for documentation.", "title": "Quick walkthrough for proofreading"}, {"location": "sp-guides/tec-cb-ome-prf/#accessing-the-package", "text": "", "title": "Accessing the package"}, {"location": "sp-guides/tec-cb-ome-prf/#accessing-the-package-for-the-first-time", "text": "The following steps need to be performed only once per OmegaT package : when you access each package for the first time: Download the from the portal Store the in a location you will remember on your computer. Import the in OmegaT: Open OmegaT Go to Project>Import OMT package Navigate to the location where you stored the OMT package. Choose the and click on Open A pop up opens. Click Yes . Translate/Reconcile/Adapt/Review the files in the package. When you are done working for the day, close OmegaT.", "title": "Accessing the package for the first time"}, {"location": "sp-guides/tec-cb-ome-prf/#access-the-package-after-import", "text": "The next times you want to access the project in OmegaT, go to Project>Open Recent Project . The project you were working on is the first one in the list:", "title": "Access the package after import"}, {"location": "sp-guides/tec-cb-ome-prf/#navigation", "text": "", "title": "Navigation"}, {"location": "sp-guides/tec-cb-ome-prf/#navigation-between-the-different-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane . The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show you if a repeated segment was translated differently.", "title": "Navigation between the different panes"}, {"location": "sp-guides/tec-cb-ome-prf/#navigation-between-the-different-files", "text": "If the project contains multiple files, they are listed in the Project Files pane . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files pane. You can also see the name of the file that is open in the Editor pane's title bar.", "title": "Navigation between the different files"}, {"location": "sp-guides/tec-cb-ome-prf/#navigation-between-the-different-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working in. The translation is displayed right below the source text. Press the Enter key on your keyboard to go to the next segment. A segment can also be activated by double clicking on it. It then becomes green. In OmegaT, a color code will help you find your way around between the different segments: Green = the segment you are working in (active segment) Grey = translated segment. The translation is displayed below the source text. Orange = pretranslated and locked segment (e.g. trend). These segments cannot be edited in OmegaT. All segments should appear translated in a project for proofreading. If you notice an untranslated segment in * *, please contact cApStAn's project managers to see how it should be handled.", "title": "Navigation between the different segments"}, {"location": "sp-guides/tec-cb-ome-prf/#recognizing-tags", "text": "If you are in a segment which contains tags, you will recognize them because they are in red font . There are two types of tags - standalone tags and double tags: Standalone tags = a single tag with a precise role (e.g. tag which introduces a new paragraph in HTML) Double tags are composed of an opening and a closing tag, such as the HTML tags for making text bold, italic, underlined, etc. Double tags affect the text between them and you need to ensure they are positioned around the exact same words in the source and in the translation.", "title": "Recognizing tags"}, {"location": "sp-guides/tec-cb-ome-prf/#fixing-tag-issues", "text": "For your language task, all tags should be present in the translation. What is important is to correct potential errors that you may see. In the screenshot below, in the source segment the **** are around the letter \"n\" while in the target they are around the word \"which\" . To correct this issue, you would have to perform the following steps: double click on the first incorrectly inserted tag in the target segment to select it and press Backspace on your keyboard to delete it repeat the operation until you deleted all incorrectly inserted tags place your mouse where the first tag should be correctly inserted and press Ctrl + T on your keyboard to insert the first tag insert all other missing tags. Please note that tags are inserted in the order of their appearance in the source segment.", "title": "Fixing tag issues"}, {"location": "sp-guides/tec-cb-ome-prf/#handling-repeated-segments", "text": "Some segments are identical to each other. They are called \u201c repeated segments \u201d and their translation is autopropagated .", "title": "Handling repeated segments"}, {"location": "sp-guides/tec-cb-ome-prf/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because it has gray font. When a repeated segment is active, the segment number will indicate how many repetitions exist: If you right click on a repeated segment, the contextual menu will point out the other occurrences of a repeated segment. It can be useful to jump to them (by selecting them from the contextual menu) to see the different contexts in which a repeated segment appears.", "title": "Identifying repeated segments"}, {"location": "sp-guides/tec-cb-ome-prf/#autopropagation", "text": "If you edit the translation of a repeated segment, by default, the changes will be automatically reflected in all the repetitions. This happens in the same file, but also in all the files of the OmegaT package.", "title": "Autopropagation"}, {"location": "sp-guides/tec-cb-ome-prf/#create-alternative-translation", "text": "In some cases, you may not wish to modify the translation of all repeated segments. Due to a different context, you may need to change only ONE of the repeated segments: Right click on the segment Choose Create Alternative Translation from the contextual menu Change the translation of your active segment and then either press Ctrl + S or move to the next one. If you return on the repeated segment, you will see the different translations appear in the Multiple Translations pane.", "title": "Create alternative translation"}, {"location": "sp-guides/tec-cb-ome-prf/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "sp-guides/tec-cb-ome-prf/#using-the-character-table", "text": "Special characters can be inserted with the Special Characters Table. Special characters can be: quotation marks: \u00ab\u00bb, \u201e\u201c, \u2018\u2019, etc. mathematical symbols: \u00d7, \u03c0, \u00f7, \u2264, \u2260, \u221a, etc. other characters: \u00ae, \u2122 When you arrive in a segment in which you need to insert a special character, perform the following steps: Press Ctrl + Space on your keyboard several times until you reach the special characters table. Select the character you want to insert Press Enter and continue editing your segment.", "title": "Using the character table"}, {"location": "sp-guides/tec-cb-ome-prf/#inserting-non-breaking-spaces", "text": "In order to insert non-breaking spaces in OmegaT, please make sure you have installed Auto Hot Key . If you haven't installed it yet, please check the Third Party Tools section of the OmegaT Installation guide Once Auto Hot Key is installed, you can insert non-breaking spaces with the same keyboard shortcut as in Word: Ctrl + Shift + Space . You can recognize a non breaking space because it is gray.", "title": "Inserting non-breaking spaces"}, {"location": "sp-guides/tec-cb-ome-prf/#performing-concordance-searches", "text": "A concordance search allows you to look for words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word you want to search for with your mouse. Press Ctrl + F on your keyboard. The Search window will open. Press Search. The results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the target translation at the right place. TIP: There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Performing concordance searches"}, {"location": "sp-guides/tec-cb-ome-prf/#performing-qa-checks-in-omegat", "text": "", "title": "Performing QA checks in OmegaT"}, {"location": "sp-guides/tec-cb-ome-prf/#completion-check", "text": "All segments of the OmegaT package must have a translation. To ensure that is the case, please check for completion prior to delivery: Go to Project>Project Files The project files pane will open OK: If the Number of unique segments is equal to the number of Translated unique segments . NOT OK : the Number of unique segments is different from the number of Translated unique segments . To correct: Close the Project Files Pane Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . When the cursor stops moving from the active segment then all segments have a translation. Recheck for completion, to make sure by opening the Project Files pane.", "title": "Completion check"}, {"location": "sp-guides/tec-cb-ome-prf/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools>Check Issues . A pop up window will open. By default, other types of checks (Spelling, Terminology, LanguageTool) are ticked. If you want to check for issues related to tags before performing the rest of the checks, you can untick them. You will notice that the Tag Issues box cannot be unticked. Press OK . An error report will open. Go through the issues one by one: Correct the issue by clicking on Jump to Segment . You will arrive at the appropriate segment in the editor pane. Place your cursor where the missing tag needs to be inserted and press Ctrl + T to insert the missing tag. Press Enter to move to the next segment. Open the Error report again. It has automatically refreshed. Finish going through the issues. TIP : If in the source there are tags that you do not use in your language which are present in the source segment, to avoid having false positives in the error report, you can insert them at the end of the segment. They would not have an impact on any text. Caution Please do not click on \"Apply fix\", fix each issue manually.", "title": "Check and fix tags"}, {"location": "sp-guides/tec-cb-ome-prf/#creating-target-files", "text": "Press Ctrl + Shift + D to create the target file you were working on. This will allow you to preview the translated file with your changes. To access the file, go to Project>Access Project Contents>Target Files . A window with the contents of the \"target\" folder will open. Find the file you were working on, if there are several files and preview it to read the translation in context.", "title": "Creating target files"}, {"location": "sp-guides/tec-cb-ome-prf/#delivering-the-project", "text": "Once you have finished editing the OmegaT package and have performed the appropriate Q&A checks, you need to Export the . Go to Project>Export OMT Package A pop up window will open. Click Save Press OK in the Pop-up window notifying that the package was successfully created. You will be automatically directed to the location the exported package is stored. You will recognize the package because it has the extension OMT. It should be the 4th from the bottom. This is the file you have to deliver.", "title": "Delivering the project"}, {"location": "sp-guides/tec-cb-ome-prf/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "sp-guides/tec-cb-ome-rec/", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk. Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine. Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy : Reconciling using matches \u00b6 During the reconciliation task, the translations from translator 1 and translator 2 are handled as matches and are displayed in the Matches pane. A reconciler's task in practice consists of one of these three options: Inserting one of the two matches (and then modify it if needed), OR Inserting part of one of the two matches and then inserting part of the other match, OR Translating the segment from scratch if none of the two matches is suitable. By default, the match from translator 1 is activated. It is the first one in the list and it is bolded . If you want to use the match from translator 2, double click on it to activate that one instead (the activated match will become bolded ). To insert the active match in full, press Ctrl + I on your keyboard. After inserting it, make any necessary changes so that it fits the segment you are reconciling. Alternatively, you can also insert only part of a match or combine several matches: Double-click the match you want to use to activate it Drag your mouse over the part of the match you wish to insert to select it Press Ctrl + I on your keyboard to insert it Select (part of) another match if appropriate or type the rest of the translation Remember It is important to make sure the final translation is harmonized as the two translators may use different terms and styles. To ensure this, make sure you preview the item prior to delivery and perform concordance searches on recurring instructions and terminology. Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags: standalone tags and paired tags or double tags: Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags. To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags, enjoy : Fixing tag issues \u00b6 All tags you see in the source text should be present in the translation too and in the correct position. You must correct any errors that you may see when that's not the case. You may find two types of issue: A tag or tag pair is missing: in that case, the solution is simply to insert it . A tag is inserted but misplaced: the solution may be either to drag and drop single tags to the correct position, or simply to delete the tag (or tag pair) and insert it again correctly. Warning for RTL languages In right-to-left languages such as Arabic or Hebrew, moving tags will not work. Please delete the tag and insert it again if you work with any of these languages. Deleting tags \u00b6 If you have inserted a tag incorrectly and need to insert it again, double click on the tag to select it in full and press Backspace or Del on your keyboard to delete it first. Moving tags \u00b6 If you have inserted a tag in the wrong position and need to insert it somewhere else, you can simply drag and drop it. Alternatively, you can also delete it and insert it again. Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry. Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy : Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting. QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue. Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver. OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Tec cb ome rec"}, {"location": "sp-guides/tec-cb-ome-rec/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "sp-guides/tec-cb-ome-rec/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "sp-guides/tec-cb-ome-rec/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "sp-guides/tec-cb-ome-rec/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "sp-guides/tec-cb-ome-rec/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "sp-guides/tec-cb-ome-rec/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "sp-guides/tec-cb-ome-rec/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "sp-guides/tec-cb-ome-rec/#navigation", "text": "", "title": "Navigation"}, {"location": "sp-guides/tec-cb-ome-rec/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "sp-guides/tec-cb-ome-rec/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "sp-guides/tec-cb-ome-rec/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "sp-guides/tec-cb-ome-rec/#reconciling-using-matches", "text": "During the reconciliation task, the translations from translator 1 and translator 2 are handled as matches and are displayed in the Matches pane. A reconciler's task in practice consists of one of these three options: Inserting one of the two matches (and then modify it if needed), OR Inserting part of one of the two matches and then inserting part of the other match, OR Translating the segment from scratch if none of the two matches is suitable. By default, the match from translator 1 is activated. It is the first one in the list and it is bolded . If you want to use the match from translator 2, double click on it to activate that one instead (the activated match will become bolded ). To insert the active match in full, press Ctrl + I on your keyboard. After inserting it, make any necessary changes so that it fits the segment you are reconciling. Alternatively, you can also insert only part of a match or combine several matches: Double-click the match you want to use to activate it Drag your mouse over the part of the match you wish to insert to select it Press Ctrl + I on your keyboard to insert it Select (part of) another match if appropriate or type the rest of the translation Remember It is important to make sure the final translation is harmonized as the two translators may use different terms and styles. To ensure this, make sure you preview the item prior to delivery and perform concordance searches on recurring instructions and terminology.", "title": "Reconciling using matches"}, {"location": "sp-guides/tec-cb-ome-rec/#tags", "text": "", "title": "Tags"}, {"location": "sp-guides/tec-cb-ome-rec/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "sp-guides/tec-cb-ome-rec/#types-of-tags", "text": "There are two types of tags: standalone tags and paired tags or double tags: Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "sp-guides/tec-cb-ome-rec/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags. To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags, enjoy :", "title": "Inserting tags"}, {"location": "sp-guides/tec-cb-ome-rec/#fixing-tag-issues", "text": "All tags you see in the source text should be present in the translation too and in the correct position. You must correct any errors that you may see when that's not the case. You may find two types of issue: A tag or tag pair is missing: in that case, the solution is simply to insert it . A tag is inserted but misplaced: the solution may be either to drag and drop single tags to the correct position, or simply to delete the tag (or tag pair) and insert it again correctly. Warning for RTL languages In right-to-left languages such as Arabic or Hebrew, moving tags will not work. Please delete the tag and insert it again if you work with any of these languages.", "title": "Fixing tag issues"}, {"location": "sp-guides/tec-cb-ome-rec/#deleting-tags", "text": "If you have inserted a tag incorrectly and need to insert it again, double click on the tag to select it in full and press Backspace or Del on your keyboard to delete it first.", "title": "Deleting tags"}, {"location": "sp-guides/tec-cb-ome-rec/#moving-tags", "text": "If you have inserted a tag in the wrong position and need to insert it somewhere else, you can simply drag and drop it. Alternatively, you can also delete it and insert it again.", "title": "Moving tags"}, {"location": "sp-guides/tec-cb-ome-rec/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "sp-guides/tec-cb-ome-rec/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "sp-guides/tec-cb-ome-rec/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "sp-guides/tec-cb-ome-rec/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "sp-guides/tec-cb-ome-rec/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "sp-guides/tec-cb-ome-rec/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "sp-guides/tec-cb-ome-rec/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "sp-guides/tec-cb-ome-rec/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "sp-guides/tec-cb-ome-rec/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "sp-guides/tec-cb-ome-rec/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "sp-guides/tec-cb-ome-rec/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "sp-guides/tec-cb-ome-rec/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "sp-guides/tec-cb-ome-rec/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "sp-guides/tec-cb-ome-rec/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "sp-guides/tec-cb-ome-rec/#qa-checks", "text": "", "title": "QA checks"}, {"location": "sp-guides/tec-cb-ome-rec/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "sp-guides/tec-cb-ome-rec/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "sp-guides/tec-cb-ome-rec/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "sp-guides/tec-cb-ome-rec/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "sp-guides/tec-cb-ome-rec/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "sp-guides/tec-cb-ome-rec/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "sp-guides/tec-cb-ome-rec/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "sp-guides/tec-cb-ome-rec/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "sp-guides/tec-cb-ome-tra/", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk. Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine. Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy : Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags: standalone tags and paired tags or double tags: Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags. To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags, enjoy : Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment. Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry. Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy : Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting. QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue. Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver. OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Tec cb ome tra"}, {"location": "sp-guides/tec-cb-ome-tra/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "sp-guides/tec-cb-ome-tra/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "sp-guides/tec-cb-ome-tra/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "sp-guides/tec-cb-ome-tra/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "sp-guides/tec-cb-ome-tra/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "sp-guides/tec-cb-ome-tra/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "sp-guides/tec-cb-ome-tra/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "sp-guides/tec-cb-ome-tra/#navigation", "text": "", "title": "Navigation"}, {"location": "sp-guides/tec-cb-ome-tra/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "sp-guides/tec-cb-ome-tra/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "sp-guides/tec-cb-ome-tra/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "sp-guides/tec-cb-ome-tra/#tags", "text": "", "title": "Tags"}, {"location": "sp-guides/tec-cb-ome-tra/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "sp-guides/tec-cb-ome-tra/#types-of-tags", "text": "There are two types of tags: standalone tags and paired tags or double tags: Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "sp-guides/tec-cb-ome-tra/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags. To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags, enjoy :", "title": "Inserting tags"}, {"location": "sp-guides/tec-cb-ome-tra/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "sp-guides/tec-cb-ome-tra/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "sp-guides/tec-cb-ome-tra/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "sp-guides/tec-cb-ome-tra/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "sp-guides/tec-cb-ome-tra/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "sp-guides/tec-cb-ome-tra/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "sp-guides/tec-cb-ome-tra/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "sp-guides/tec-cb-ome-tra/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "sp-guides/tec-cb-ome-tra/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "sp-guides/tec-cb-ome-tra/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "sp-guides/tec-cb-ome-tra/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "sp-guides/tec-cb-ome-tra/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "sp-guides/tec-cb-ome-tra/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "sp-guides/tec-cb-ome-tra/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "sp-guides/tec-cb-ome-tra/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "sp-guides/tec-cb-ome-tra/#qa-checks", "text": "", "title": "QA checks"}, {"location": "sp-guides/tec-cb-ome-tra/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "sp-guides/tec-cb-ome-tra/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "sp-guides/tec-cb-ome-tra/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "sp-guides/tec-cb-ome-tra/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "sp-guides/tec-cb-ome-tra/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "sp-guides/tec-cb-ome-tra/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "sp-guides/tec-cb-ome-tra/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "sp-guides/tec-cb-ome-tra/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "sp-guides/tec-cb-ome-ver/", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk. Your user Name/ID \u00b6 When opening OmegaT for the first time, please update your Name/ID. To do that click on Options > Preferences > Team . The Name/ID box might already contain your username. If that's the case, please prepend your username with VER . If the box is empty, please enter VER_your-name (e.g. VER_souto , VER_msoutopico , etc.). Then press OK. Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine. Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy : Warning All segments should appear translated for an editing task (such as verification, proofreading, etc.), i.e. highlighted either in gray (translated) or in pink (pretranslated) or in orange (pretranslated and locked, for trend or legacy translations). If you notice an untranslated segment in blue , please contact cApStAn's project managers to see how it should be handled. Revising and editing \u00b6 Revising the translation \u00b6 To revise the translation, you must move through segments one by one. Read every translation, while comparing with the source text, considering the rest of the context and taking into account any specific instructions you may have received for your particular task. Press the Enter key to move to the next segment. The segment you jump to becomes active and ready for edits. This will also allow you to keep track of your progress. If you need to move backwards, you can press Ctrl + Enter . Editing the translation \u00b6 To correct an error in the translation, you must edit the target text. To edit a translation, simply delete the text that must be removed and type the text that must be added. You can only edit the translation of the active segment. You must activate a segment to make it editable. The segment you jump to pressing Enter becomes active and ready for edits. You may also activate any segment (and make it editable) by double-clicking it, but in that case you might want to return to the segment you were originally to continue revising from there. Tip You can recognize the active segment because it is highlighted in green . Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy : Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment. Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry. Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy : Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting. QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue. Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver. OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Tec cb ome ver"}, {"location": "sp-guides/tec-cb-ome-ver/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "sp-guides/tec-cb-ome-ver/#your-user-nameid", "text": "When opening OmegaT for the first time, please update your Name/ID. To do that click on Options > Preferences > Team . The Name/ID box might already contain your username. If that's the case, please prepend your username with VER . If the box is empty, please enter VER_your-name (e.g. VER_souto , VER_msoutopico , etc.). Then press OK.", "title": "Your user Name/ID"}, {"location": "sp-guides/tec-cb-ome-ver/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "sp-guides/tec-cb-ome-ver/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "sp-guides/tec-cb-ome-ver/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "sp-guides/tec-cb-ome-ver/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "sp-guides/tec-cb-ome-ver/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "sp-guides/tec-cb-ome-ver/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "sp-guides/tec-cb-ome-ver/#navigation", "text": "", "title": "Navigation"}, {"location": "sp-guides/tec-cb-ome-ver/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "sp-guides/tec-cb-ome-ver/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "sp-guides/tec-cb-ome-ver/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy : Warning All segments should appear translated for an editing task (such as verification, proofreading, etc.), i.e. highlighted either in gray (translated) or in pink (pretranslated) or in orange (pretranslated and locked, for trend or legacy translations). If you notice an untranslated segment in blue , please contact cApStAn's project managers to see how it should be handled.", "title": "Navigation through segments"}, {"location": "sp-guides/tec-cb-ome-ver/#revising-and-editing", "text": "", "title": "Revising and editing"}, {"location": "sp-guides/tec-cb-ome-ver/#revising-the-translation", "text": "To revise the translation, you must move through segments one by one. Read every translation, while comparing with the source text, considering the rest of the context and taking into account any specific instructions you may have received for your particular task. Press the Enter key to move to the next segment. The segment you jump to becomes active and ready for edits. This will also allow you to keep track of your progress. If you need to move backwards, you can press Ctrl + Enter .", "title": "Revising the translation"}, {"location": "sp-guides/tec-cb-ome-ver/#editing-the-translation", "text": "To correct an error in the translation, you must edit the target text. To edit a translation, simply delete the text that must be removed and type the text that must be added. You can only edit the translation of the active segment. You must activate a segment to make it editable. The segment you jump to pressing Enter becomes active and ready for edits. You may also activate any segment (and make it editable) by double-clicking it, but in that case you might want to return to the segment you were originally to continue revising from there. Tip You can recognize the active segment because it is highlighted in green .", "title": "Editing the translation"}, {"location": "sp-guides/tec-cb-ome-ver/#tags", "text": "", "title": "Tags"}, {"location": "sp-guides/tec-cb-ome-ver/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "sp-guides/tec-cb-ome-ver/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "sp-guides/tec-cb-ome-ver/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "sp-guides/tec-cb-ome-ver/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "sp-guides/tec-cb-ome-ver/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "sp-guides/tec-cb-ome-ver/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "sp-guides/tec-cb-ome-ver/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "sp-guides/tec-cb-ome-ver/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "sp-guides/tec-cb-ome-ver/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "sp-guides/tec-cb-ome-ver/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "sp-guides/tec-cb-ome-ver/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "sp-guides/tec-cb-ome-ver/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "sp-guides/tec-cb-ome-ver/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "sp-guides/tec-cb-ome-ver/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "sp-guides/tec-cb-ome-ver/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "sp-guides/tec-cb-ome-ver/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "sp-guides/tec-cb-ome-ver/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "sp-guides/tec-cb-ome-ver/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "sp-guides/tec-cb-ome-ver/#qa-checks", "text": "", "title": "QA checks"}, {"location": "sp-guides/tec-cb-ome-ver/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "sp-guides/tec-cb-ome-ver/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "sp-guides/tec-cb-ome-ver/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "sp-guides/tec-cb-ome-ver/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "sp-guides/tec-cb-ome-ver/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "sp-guides/tec-cb-ome-ver/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "sp-guides/tec-cb-ome-ver/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "sp-guides/tec-cb-ome-ver/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "sp-guides/tec-cb-ome-wlk-thr/", "text": "Quick walkthrough (for reconciliation) \u00b6 Download the package for reconciliation and the Excel document from the portal Import the OMT package in OmegaT as described in the section The OmegaT project for reconciliation will open: All segments will appear untranslated in the Editor pane (the main pane of OmegaT, which contains the source text). To find out how to recognize reconciled segments from unreconciled ones and from potential trend segments, please refer to the section The** suggestions from Translator 1 and Translator 2** for the active segment (green) appear below, in the Fuzzy matches pane In the Fuzzy matches pane, the suggestions from the 2 translators display the source text of the active segment , the suggested translation for the active segment as well as the identity of the author . By default, the suggestion from translator 1 appears in bold. It means it is selected. If you want to insert it, no need to retype the text, you can simply press Ctrl + I on your keyboard and it will appear below the active segment. To learn how to reconcile and insert the suggestions from translator 2 or how to combine both, please read the section You can preview the file you are reconciling on the portal. Please consult the section Creating the target file to learn how to create and access the reconciled file. This is the file you will have to drag and drop on the portal for preview. If you notice errors in formatting while previewing (e.g. words that are bolded in your language but were not bolded in the source, or vice-versa), please consult the section Fixing tag issues to learn how to correct them. If you notice identical source sentences that need to be reconciled differently, please consult the section Create alternative translation After performing a few QA checks , most importantly the Completion check , you can create the reconciled package and deliver it on the portal. To create the reconciled package , go to Project>Export OMT package in OmegaT. More details about how to create the package for delivery can be found in the section Exporting the package for delivery", "title": "Quick walkthrough (for reconciliation)"}, {"location": "sp-guides/tec-cb-ome-wlk-thr/#quick-walkthrough-for-reconciliation", "text": "Download the package for reconciliation and the Excel document from the portal Import the OMT package in OmegaT as described in the section The OmegaT project for reconciliation will open: All segments will appear untranslated in the Editor pane (the main pane of OmegaT, which contains the source text). To find out how to recognize reconciled segments from unreconciled ones and from potential trend segments, please refer to the section The** suggestions from Translator 1 and Translator 2** for the active segment (green) appear below, in the Fuzzy matches pane In the Fuzzy matches pane, the suggestions from the 2 translators display the source text of the active segment , the suggested translation for the active segment as well as the identity of the author . By default, the suggestion from translator 1 appears in bold. It means it is selected. If you want to insert it, no need to retype the text, you can simply press Ctrl + I on your keyboard and it will appear below the active segment. To learn how to reconcile and insert the suggestions from translator 2 or how to combine both, please read the section You can preview the file you are reconciling on the portal. Please consult the section Creating the target file to learn how to create and access the reconciled file. This is the file you will have to drag and drop on the portal for preview. If you notice errors in formatting while previewing (e.g. words that are bolded in your language but were not bolded in the source, or vice-versa), please consult the section Fixing tag issues to learn how to correct them. If you notice identical source sentences that need to be reconciled differently, please consult the section Create alternative translation After performing a few QA checks , most importantly the Completion check , you can create the reconciled package and deliver it on the portal. To create the reconciled package , go to Project>Export OMT package in OmegaT. More details about how to create the package for delivery can be found in the section Exporting the package for delivery", "title": "Quick walkthrough (for reconciliation)"}, {"location": "translation/", "tags": ["Translation"], "text": "a.md-footer__link--prev[aria-label^=\"Previous:\"], .md-nav__icon { display: none !important; } \ud83d\udc4b Welcome to the OmegaT translation guide! \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "Translation"}, {"location": "translation/#welcome-to-the-omegat-translation-guide", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "\ud83d\udc4b Welcome to the OmegaT translation guide!"}, {"location": "translation/accessing-the-project/", "text": "Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Accessing a project"}, {"location": "translation/accessing-the-project/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "translation/accessing-the-project/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "translation/accessing-the-project/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "translation/accessing-the-project/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "translation/accessing-the-project/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "translation/accessing-the-project/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "translation/creating-target-files/", "text": "Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "translation/creating-target-files/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "translation/creating-your-deliverable/", "text": "Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Creating your deliverable"}, {"location": "translation/creating-your-deliverable/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "translation/creating-your-deliverable/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "translation/creating-your-deliverable/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "translation/glossary/", "text": "Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Glossary"}, {"location": "translation/glossary/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "translation/glossary/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "translation/glossary/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "translation/install-and-setup/", "text": "Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "translation/install-and-setup/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "translation/matches/", "text": "Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "translation/matches/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "translation/navigation/", "text": "Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation"}, {"location": "translation/navigation/#navigation", "text": "", "title": "Navigation"}, {"location": "translation/navigation/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "translation/navigation/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "translation/navigation/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "translation/other-useful-features/", "text": "Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Other useful features"}, {"location": "translation/other-useful-features/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "translation/other-useful-features/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "translation/other-useful-features/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "translation/other-useful-features/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "translation/other-useful-features/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "translation/other-useful-features/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "translation/other-useful-features/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "translation/qa-checks/", "text": "QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "QA checks"}, {"location": "translation/qa-checks/#qa-checks", "text": "", "title": "QA checks"}, {"location": "translation/qa-checks/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "translation/qa-checks/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "translation/qa-checks/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "translation/repetitions/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Repetitions"}, {"location": "translation/repetitions/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "translation/repetitions/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "translation/repetitions/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "translation/repetitions/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "translation/shortcuts/", "text": "a.md-footer__link--next[aria-label^=\"Next:\"], .md-nav__icon { display: none !important; } OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "translation/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "translation/tags/", "text": "Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Tags"}, {"location": "translation/tags/#tags", "text": "", "title": "Tags"}, {"location": "translation/tags/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "translation/tags/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "translation/tags/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "verification/", "tags": ["Verification"], "text": "a.md-footer__link--prev[aria-label^=\"Previous:\"], .md-nav__icon { display: none !important; } \ud83d\udc4b Welcome to the OmegaT verification guide! \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "Verification"}, {"location": "verification/#welcome-to-the-omegat-verification-guide", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "\ud83d\udc4b Welcome to the OmegaT verification guide!"}, {"location": "verification/accessing-the-project/", "text": "Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Accessing a project"}, {"location": "verification/accessing-the-project/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "verification/accessing-the-project/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "verification/accessing-the-project/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "verification/accessing-the-project/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "verification/accessing-the-project/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "verification/accessing-the-project/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "verification/creating-target-files/", "text": "Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "verification/creating-target-files/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "verification/creating-your-deliverable/", "text": "Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Creating your deliverable"}, {"location": "verification/creating-your-deliverable/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "verification/creating-your-deliverable/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "verification/creating-your-deliverable/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "verification/editing/", "text": "Revising and editing \u00b6 Revising the translation \u00b6 To revise the translation, you must move through segments one by one. Read every translation, while comparing with the source text, considering the rest of the context and taking into account any specific instructions you may have received for your particular task. Press the Enter key to move to the next segment. The segment you jump to becomes active and ready for edits. This will also allow you to keep track of your progress. If you need to move backwards, you can press Ctrl + Enter . Editing the translation \u00b6 To correct an error in the translation, you must edit the target text. To edit a translation, simply delete the text that must be removed and type the text that must be added. You can only edit the translation of the active segment. You must activate a segment to make it editable. The segment you jump to pressing Enter becomes active and ready for edits. You may also activate any segment (and make it editable) by double-clicking it, but in that case you might want to return to the segment you were originally to continue revising from there. Tip You can recognize the active segment because it is highlighted in green .", "title": "Editing"}, {"location": "verification/editing/#revising-and-editing", "text": "", "title": "Revising and editing"}, {"location": "verification/editing/#revising-the-translation", "text": "To revise the translation, you must move through segments one by one. Read every translation, while comparing with the source text, considering the rest of the context and taking into account any specific instructions you may have received for your particular task. Press the Enter key to move to the next segment. The segment you jump to becomes active and ready for edits. This will also allow you to keep track of your progress. If you need to move backwards, you can press Ctrl + Enter .", "title": "Revising the translation"}, {"location": "verification/editing/#editing-the-translation", "text": "To correct an error in the translation, you must edit the target text. To edit a translation, simply delete the text that must be removed and type the text that must be added. You can only edit the translation of the active segment. You must activate a segment to make it editable. The segment you jump to pressing Enter becomes active and ready for edits. You may also activate any segment (and make it editable) by double-clicking it, but in that case you might want to return to the segment you were originally to continue revising from there. Tip You can recognize the active segment because it is highlighted in green .", "title": "Editing the translation"}, {"location": "verification/glossary/", "text": "Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Glossary"}, {"location": "verification/glossary/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "verification/glossary/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "verification/glossary/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "verification/install-and-setup-macos/", "text": "OmegaT 5.7.2 setup guide for macOS \u00b6 Carefully choose your path here: If there is no current installation of OmegaT in your machine, you can skip the following steps about configuration and jump directly to the installation section . OmegaT will configure itself as part of the installation. If you already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed, you'll have to update your configuration first: to do so please go to the configuration section (next section right down below). Configuration \u00b6 This section applies to users that already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed. Please follow the next steps to update your configuration for starteers. Run OmegaT and go to Tools > Scripting to open your scripting console, In OmegaT 5.7.1, please open the scripting console. Check whethers you have a script called \" Update Customisation Bundle (v572) \": Warning If you don't see the \" v572 \" bit, then it's not the script we're looking for. See next step to fetch the script. If the script \" Update Customisation Bundle (v572) \" is there, please click on it to select it and press the Run button (at the bottom left) to run it. The script will run to update your config files and will quit OmegaT. After that, skip the next step and jump directly to the installation section . If the script is not there, go to the next step to download it. Click on the button below to download the configuration script (e.g. to your Desktop) Download UpdateConfigBundle.groovy In OmegaT, follow these steps to run the configuration script you have downloaded: Tools > Scripting > File > Open script browse to your Desktop (or the folder where you have saved the script) and select the groovy file press the Open button to open the script file and press Run button (on the bottom left) The script will install the necessary config files for OmegaT 5.7.2 and delete old config files for OmegaT 5.7.1, and after that it will quit OmegaT. Uninstall your current version of OmegaT. To do that, simply move the installed OmegaT.app to Trash. Finally, proceed now to the installation section (next step below). Installation \u00b6 Click on the button below to download OmegaT 5.7.2. This is a custom version prepared by cApStAn which includes several bug fixes and enhancements not available in other versions. Download OmegaT 5.7.2 If you're using Safari, then the file will be unzipped automatically when the download ends.\u200b If you use another browser, double-click the file when the download ends to unzip it. A folder is created, open it to see its contents. You'll see that it contains the OmegaT.app file. Drag the OmegaT.app file to the Applications folder. OmegaT is now installed. Go to the Applications folder and open OmegaT there. Your Mac might ask for confirmation that you want to open it. If that's the case, please press Open . OmegaT will now run. If you want to run a post-installation check to confirm that you have the correct version, you can check that in Help > About > Copy Support Info . You should see: Version: OmegaT-5.7.2_0_a978d82ee Platform: [your operating system] Java: 11.0.19 amd64 You're done now. You can start using OmegaT 5.7.2. Please do not forget to set your user name in OmegaT . Your user Name/ID \u00b6 When opening OmegaT for the first time, please update your Name/ID. To do that click on Options > Preferences > Team . The Name/ID box might already contain your username. If that's the case, please prepend your username with VER_ . If the box is empty, please enter VER_your-name (e.g. VER_souto , VER_msoutopico , etc.). Then press OK.", "title": "Install and setup macos"}, {"location": "verification/install-and-setup-macos/#omegat-572-setup-guide-for-macos", "text": "Carefully choose your path here: If there is no current installation of OmegaT in your machine, you can skip the following steps about configuration and jump directly to the installation section . OmegaT will configure itself as part of the installation. If you already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed, you'll have to update your configuration first: to do so please go to the configuration section (next section right down below).", "title": "OmegaT 5.7.2 setup guide for macOS"}, {"location": "verification/install-and-setup-macos/#configuration", "text": "This section applies to users that already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed. Please follow the next steps to update your configuration for starteers. Run OmegaT and go to Tools > Scripting to open your scripting console, In OmegaT 5.7.1, please open the scripting console. Check whethers you have a script called \" Update Customisation Bundle (v572) \": Warning If you don't see the \" v572 \" bit, then it's not the script we're looking for. See next step to fetch the script. If the script \" Update Customisation Bundle (v572) \" is there, please click on it to select it and press the Run button (at the bottom left) to run it. The script will run to update your config files and will quit OmegaT. After that, skip the next step and jump directly to the installation section . If the script is not there, go to the next step to download it. Click on the button below to download the configuration script (e.g. to your Desktop) Download UpdateConfigBundle.groovy In OmegaT, follow these steps to run the configuration script you have downloaded: Tools > Scripting > File > Open script browse to your Desktop (or the folder where you have saved the script) and select the groovy file press the Open button to open the script file and press Run button (on the bottom left) The script will install the necessary config files for OmegaT 5.7.2 and delete old config files for OmegaT 5.7.1, and after that it will quit OmegaT. Uninstall your current version of OmegaT. To do that, simply move the installed OmegaT.app to Trash. Finally, proceed now to the installation section (next step below).", "title": "Configuration"}, {"location": "verification/install-and-setup-macos/#installation", "text": "Click on the button below to download OmegaT 5.7.2. This is a custom version prepared by cApStAn which includes several bug fixes and enhancements not available in other versions. Download OmegaT 5.7.2 If you're using Safari, then the file will be unzipped automatically when the download ends.\u200b If you use another browser, double-click the file when the download ends to unzip it. A folder is created, open it to see its contents. You'll see that it contains the OmegaT.app file. Drag the OmegaT.app file to the Applications folder. OmegaT is now installed. Go to the Applications folder and open OmegaT there. Your Mac might ask for confirmation that you want to open it. If that's the case, please press Open . OmegaT will now run. If you want to run a post-installation check to confirm that you have the correct version, you can check that in Help > About > Copy Support Info . You should see: Version: OmegaT-5.7.2_0_a978d82ee Platform: [your operating system] Java: 11.0.19 amd64 You're done now. You can start using OmegaT 5.7.2. Please do not forget to set your user name in OmegaT .", "title": "Installation"}, {"location": "verification/install-and-setup-macos/#your-user-nameid", "text": "When opening OmegaT for the first time, please update your Name/ID. To do that click on Options > Preferences > Team . The Name/ID box might already contain your username. If that's the case, please prepend your username with VER_ . If the box is empty, please enter VER_your-name (e.g. VER_souto , VER_msoutopico , etc.). Then press OK.", "title": "Your user Name/ID"}, {"location": "verification/install-and-setup/", "text": "OmegaT 5.7.2 setup guide for Windows \u00b6 Other operating systems It's possible to install OmegaT 5.7.2 in other operating systems like macOS or Linux. Follow this other guide to install on macOS . Please get in touch through the Helpdesk if you are a Linux user. Choose your path here carefully , depending on your starting point: IF you already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed, you'll have to update your configuration first: to do so please go to the configuration section (next section right down below). IF there is no current installation of OmegaT in your machine, you can skip the following steps about configuration and jump directly to the installation section . OmegaT will configure itself as part of the installation. Configuration \u00b6 This section applies to users that already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed. Please follow the next steps to update your configuration. Run OmegaT and go to Tools > Scripting to open your scripting console, In OmegaT 5.7.1, please open the scripting console. Check whethers you have a script called \" Update Customisation Bundle (v572) \": Warning If you don't see the \" v752 \" bit, then it's not the script we're looking for. See next step to fetch the script. If the script \" Update Customisation Bundle (v572) \" is there, please click on it to select it and press the Run button (at the bottom left) to run it. The script will run to update your config files and will quit OmegaT. After that, skip the next step and jump directly to the installation section . If the script is not there, you may download it yourself. See next steps for how to do that. Click on the button below to download the configuration script (e.g. to your Desktop) Download UpdateConfigBundle.groovy In OmegaT, follow these steps to run the configuration script you have downloaded: Tools > Scripting > File > Open script browse to your Desktop (or the folder where you have saved the script) and select the groovy file press the Open button to open the script file and press Run button (on the bottom left) The script will install the necessary config files for OmegaT 5.7.2 and delete old config files for OmegaT 5.7.1, and after that it will quit OmegaT. Uninstall your current version of OmegaT. Finally, proceed now to the installation section (next step below). Installation \u00b6 Warning You must have a 64-bit machine to install OmegaT. If that's not the case, please get in touch with our Helpdesk. Click on the button below to download OmegaT 5.7.2. This is a custom version prepared by cApStAn which includes several bug fixes and enhancements not available in other versions. Download OmegaT 5.7.2 Trouble to download? Some browsers (e.g. Microsoft Edge) might ask you whether downloading the installer is safe. It is safe, and you can follow the following steps in the video below to let your browser download the file. Double-click the installer file to start the installation wizard. Windows Defender might show a dialog warning against the risk of running an unrecognized app. s If you see that, click on the More info link in that dialog. In the information displayed you should see that cApStAn is the publisher of this installer. If that's the case, prease press the Run anyway button to proceed with the installation. In the next dialog, you may choose the language of the installation, then press Ok : Please accept the GPL license agreement to proceed, and press Next : OmegaT will propose the path C:\\Users\\USER\\AppData\\Local\\Programs\\OmegaT for the installation, where it should be possible for non-admin users to install. Warning Please do not modify this installation path unless you're IT personnel and you know what you're doing. A desktop shortcut (launcher) will be created on your Desktop (which you can double-click later on to launch OmegaT). Do not uncheck that option. You may modify the name of the OmegaT folder in the start menu, but \"OmegaT \" is fine, no need to change it in a standard installation. You're ready to proceed with the installation, press Next . After a couple of minutes, your installation should be complete. If you want to run a post-installation check to confirm that you have the correct version, you can check that in Help > About > Copy Support Info . You should see: Version: OmegaT-5.7.2_0_a978d82ee Platform: [your operating system] Java: 11.0.19 amd64 You're done now. You can start using OmegaT 5.7.2. Please do not forget to set your user name in OmegaT . Your user Name/ID \u00b6 When opening OmegaT for the first time, please update your Name/ID. To do that click on Options > Preferences > Team . The Name/ID box might already contain your username. If that's the case, please prepend your username with VER_ . If the box is empty, please enter VER_your-name (e.g. VER_souto , VER_msoutopico , etc.). Then press OK.", "title": "Installation and setup"}, {"location": "verification/install-and-setup/#omegat-572-setup-guide-for-windows", "text": "Other operating systems It's possible to install OmegaT 5.7.2 in other operating systems like macOS or Linux. Follow this other guide to install on macOS . Please get in touch through the Helpdesk if you are a Linux user. Choose your path here carefully , depending on your starting point: IF you already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed, you'll have to update your configuration first: to do so please go to the configuration section (next section right down below). IF there is no current installation of OmegaT in your machine, you can skip the following steps about configuration and jump directly to the installation section . OmegaT will configure itself as part of the installation.", "title": "OmegaT 5.7.2 setup guide for Windows"}, {"location": "verification/install-and-setup/#configuration", "text": "This section applies to users that already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed. Please follow the next steps to update your configuration. Run OmegaT and go to Tools > Scripting to open your scripting console, In OmegaT 5.7.1, please open the scripting console. Check whethers you have a script called \" Update Customisation Bundle (v572) \": Warning If you don't see the \" v752 \" bit, then it's not the script we're looking for. See next step to fetch the script. If the script \" Update Customisation Bundle (v572) \" is there, please click on it to select it and press the Run button (at the bottom left) to run it. The script will run to update your config files and will quit OmegaT. After that, skip the next step and jump directly to the installation section . If the script is not there, you may download it yourself. See next steps for how to do that. Click on the button below to download the configuration script (e.g. to your Desktop) Download UpdateConfigBundle.groovy In OmegaT, follow these steps to run the configuration script you have downloaded: Tools > Scripting > File > Open script browse to your Desktop (or the folder where you have saved the script) and select the groovy file press the Open button to open the script file and press Run button (on the bottom left) The script will install the necessary config files for OmegaT 5.7.2 and delete old config files for OmegaT 5.7.1, and after that it will quit OmegaT. Uninstall your current version of OmegaT. Finally, proceed now to the installation section (next step below).", "title": "Configuration"}, {"location": "verification/install-and-setup/#installation", "text": "Warning You must have a 64-bit machine to install OmegaT. If that's not the case, please get in touch with our Helpdesk. Click on the button below to download OmegaT 5.7.2. This is a custom version prepared by cApStAn which includes several bug fixes and enhancements not available in other versions. Download OmegaT 5.7.2 Trouble to download? Some browsers (e.g. Microsoft Edge) might ask you whether downloading the installer is safe. It is safe, and you can follow the following steps in the video below to let your browser download the file. Double-click the installer file to start the installation wizard. Windows Defender might show a dialog warning against the risk of running an unrecognized app. s If you see that, click on the More info link in that dialog. In the information displayed you should see that cApStAn is the publisher of this installer. If that's the case, prease press the Run anyway button to proceed with the installation. In the next dialog, you may choose the language of the installation, then press Ok : Please accept the GPL license agreement to proceed, and press Next : OmegaT will propose the path C:\\Users\\USER\\AppData\\Local\\Programs\\OmegaT for the installation, where it should be possible for non-admin users to install. Warning Please do not modify this installation path unless you're IT personnel and you know what you're doing. A desktop shortcut (launcher) will be created on your Desktop (which you can double-click later on to launch OmegaT). Do not uncheck that option. You may modify the name of the OmegaT folder in the start menu, but \"OmegaT \" is fine, no need to change it in a standard installation. You're ready to proceed with the installation, press Next . After a couple of minutes, your installation should be complete. If you want to run a post-installation check to confirm that you have the correct version, you can check that in Help > About > Copy Support Info . You should see: Version: OmegaT-5.7.2_0_a978d82ee Platform: [your operating system] Java: 11.0.19 amd64 You're done now. You can start using OmegaT 5.7.2. Please do not forget to set your user name in OmegaT .", "title": "Installation"}, {"location": "verification/install-and-setup/#your-user-nameid", "text": "When opening OmegaT for the first time, please update your Name/ID. To do that click on Options > Preferences > Team . The Name/ID box might already contain your username. If that's the case, please prepend your username with VER_ . If the box is empty, please enter VER_your-name (e.g. VER_souto , VER_msoutopico , etc.). Then press OK.", "title": "Your user Name/ID"}, {"location": "verification/matches/", "text": "Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "verification/matches/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "verification/navigation/", "text": "Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy : Warning All segments should appear translated for an editing task (such as verification, proofreading, etc.), i.e. highlighted either in gray (translated) or in pink (pretranslated) or in orange (pretranslated and locked, for trend or legacy translations). If you notice an untranslated segment in blue , please contact cApStAn's project managers to see how it should be handled.", "title": "Navigation"}, {"location": "verification/navigation/#navigation", "text": "", "title": "Navigation"}, {"location": "verification/navigation/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "verification/navigation/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "verification/navigation/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy : Warning All segments should appear translated for an editing task (such as verification, proofreading, etc.), i.e. highlighted either in gray (translated) or in pink (pretranslated) or in orange (pretranslated and locked, for trend or legacy translations). If you notice an untranslated segment in blue , please contact cApStAn's project managers to see how it should be handled.", "title": "Navigation through segments"}, {"location": "verification/other-useful-features/", "text": "Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Other useful features"}, {"location": "verification/other-useful-features/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "verification/other-useful-features/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "verification/other-useful-features/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "verification/other-useful-features/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "verification/other-useful-features/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "verification/other-useful-features/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "verification/other-useful-features/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "verification/qa-checks/", "text": "QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "QA checks"}, {"location": "verification/qa-checks/#qa-checks", "text": "", "title": "QA checks"}, {"location": "verification/qa-checks/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "verification/qa-checks/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "verification/qa-checks/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "verification/repetitions/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Repetitions"}, {"location": "verification/repetitions/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "verification/repetitions/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "verification/repetitions/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "verification/repetitions/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "verification/shortcuts/", "text": "a.md-footer__link--next[aria-label^=\"Next:\"], .md-nav__icon { display: none !important; } OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "verification/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "verification/tags/", "text": "Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy : Fixing tag issues \u00b6 All tags you see in the source text should be present in the translation too and in the correct position. You must correct any errors that you may see when that's not the case. You may find two types of issue: A tag or tag pair is missing: in that case, the solution is simply to insert it . A tag is inserted but misplaced: the solution may be either to drag and drop single tags to the correct position, or simply to delete the tag (or tag pair) and insert it again correctly. Warning for RTL languages In right-to-left languages such as Arabic or Hebrew, moving tags will not work. Please delete the tag and insert it again if you work with any of these languages. Deleting tags \u00b6 If you have inserted a tag incorrectly and need to insert it again, double click on the tag to select it in full and press Backspace or Del on your keyboard to delete it first. Moving tags \u00b6 If you have inserted a tag in the wrong position and need to insert it somewhere else, you can simply drag and drop it. Alternatively, you can also delete it and insert it again.", "title": "Tags"}, {"location": "verification/tags/#tags", "text": "", "title": "Tags"}, {"location": "verification/tags/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "verification/tags/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "verification/tags/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "verification/tags/#fixing-tag-issues", "text": "All tags you see in the source text should be present in the translation too and in the correct position. You must correct any errors that you may see when that's not the case. You may find two types of issue: A tag or tag pair is missing: in that case, the solution is simply to insert it . A tag is inserted but misplaced: the solution may be either to drag and drop single tags to the correct position, or simply to delete the tag (or tag pair) and insert it again correctly. Warning for RTL languages In right-to-left languages such as Arabic or Hebrew, moving tags will not work. Please delete the tag and insert it again if you work with any of these languages.", "title": "Fixing tag issues"}, {"location": "verification/tags/#deleting-tags", "text": "If you have inserted a tag incorrectly and need to insert it again, double click on the tag to select it in full and press Backspace or Del on your keyboard to delete it first.", "title": "Deleting tags"}, {"location": "verification/tags/#moving-tags", "text": "If you have inserted a tag in the wrong position and need to insert it somewhere else, you can simply drag and drop it. Alternatively, you can also delete it and insert it again.", "title": "Moving tags"}, {"location": "misc/tags/", "text": "Adaptation \u00b6 Adaptation Editing Proofreading \u00b6 Editing Review Reconciliation \u00b6 Reconciliation Review \u00b6 Editing Editing Review Revision \u00b6 Editing Review Translation \u00b6 Translation Verification \u00b6 Editing Verification", "title": "Tags"}, {"location": "misc/tags/#adaptation", "text": "Adaptation Editing", "title": "Adaptation"}, {"location": "misc/tags/#proofreading", "text": "Editing Review", "title": "Proofreading"}, {"location": "misc/tags/#reconciliation", "text": "Reconciliation", "title": "Reconciliation"}, {"location": "misc/tags/#review", "text": "Editing Editing Review", "title": "Review"}, {"location": "misc/tags/#revision", "text": "Editing Review", "title": "Revision"}, {"location": "misc/tags/#translation", "text": "Translation", "title": "Translation"}, {"location": "misc/tags/#verification", "text": "Editing Verification", "title": "Verification"}]} \ No newline at end of file +{"config": {"indexing": "full", "lang": ["en"], "min_search_length": 3, "prebuild_index": false, "separator": "[\\s\\-]+"}, "docs": [{"location": "", "text": "OmegaT guides \u00b6 Welcome to cApStAn's OmegaT guides. A guide for each task \u00b6 Translation Reconciliation Adaptation Verification Review Other stuff \u00b6 Videos Exercises Miscellanea", "title": "Contents"}, {"location": "#omegat-guides", "text": "Welcome to cApStAn's OmegaT guides.", "title": "OmegaT guides"}, {"location": "#a-guide-for-each-task", "text": "Translation Reconciliation Adaptation Verification Review", "title": "A guide for each task"}, {"location": "#other-stuff", "text": "Videos Exercises Miscellanea", "title": "Other stuff"}, {"location": "adaptation/", "tags": ["Adaptation"], "text": "a.md-footer__link--prev[aria-label^=\"Previous:\"], .md-nav__icon { display: none !important; } \ud83d\udc4b Welcome to the OmegaT adaptation guide! \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "Adaptation"}, {"location": "adaptation/#welcome-to-the-omegat-adaptation-guide", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "\ud83d\udc4b Welcome to the OmegaT adaptation guide!"}, {"location": "adaptation/accessing-the-project/", "text": "Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Accessing a project"}, {"location": "adaptation/accessing-the-project/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "adaptation/accessing-the-project/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "adaptation/accessing-the-project/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "adaptation/accessing-the-project/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "adaptation/accessing-the-project/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "adaptation/accessing-the-project/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "adaptation/creating-target-files/", "text": "Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "adaptation/creating-target-files/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "adaptation/creating-your-deliverable/", "text": "Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Creating your deliverable"}, {"location": "adaptation/creating-your-deliverable/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "adaptation/creating-your-deliverable/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "adaptation/creating-your-deliverable/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "adaptation/glossary/", "text": "Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Glossary"}, {"location": "adaptation/glossary/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "adaptation/glossary/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "adaptation/glossary/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "adaptation/install-and-setup/", "text": "Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "adaptation/install-and-setup/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "adaptation/matches/", "text": "Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "adaptation/matches/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "adaptation/navigation/", "text": "Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation"}, {"location": "adaptation/navigation/#navigation", "text": "", "title": "Navigation"}, {"location": "adaptation/navigation/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "adaptation/navigation/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "adaptation/navigation/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "adaptation/other-useful-features/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Other useful features"}, {"location": "adaptation/other-useful-features/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "adaptation/other-useful-features/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "adaptation/other-useful-features/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "adaptation/other-useful-features/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "adaptation/qa-checks/", "text": "QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "QA checks"}, {"location": "adaptation/qa-checks/#qa-checks", "text": "", "title": "QA checks"}, {"location": "adaptation/qa-checks/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "adaptation/qa-checks/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "adaptation/qa-checks/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "adaptation/repetitions/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Repetitions"}, {"location": "adaptation/repetitions/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "adaptation/repetitions/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "adaptation/repetitions/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "adaptation/repetitions/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "adaptation/shortcuts/", "text": "a.md-footer__link--next[aria-label^=\"Next:\"], .md-nav__icon { display: none !important; } OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "adaptation/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "adaptation/tags/", "text": "Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Tags"}, {"location": "adaptation/tags/#tags", "text": "", "title": "Tags"}, {"location": "adaptation/tags/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "adaptation/tags/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "adaptation/tags/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "editing/", "tags": ["Verification", "Proofreading", "Adaptation", "Review", "Revision", "Review"], "text": "a.md-footer__link--prev[aria-label^=\"Previous:\"], .md-nav__icon { display: none !important; } \ud83d\udc4b Welcome to the OmegaT verification guide! \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "Editing"}, {"location": "editing/#welcome-to-the-omegat-verification-guide", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "\ud83d\udc4b Welcome to the OmegaT verification guide!"}, {"location": "editing/accessing-the-project/", "text": "Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Accessing a project"}, {"location": "editing/accessing-the-project/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "editing/accessing-the-project/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "editing/accessing-the-project/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "editing/accessing-the-project/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "editing/accessing-the-project/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "editing/accessing-the-project/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "editing/creating-target-files/", "text": "Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "editing/creating-target-files/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "editing/creating-your-deliverable/", "text": "Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Creating your deliverable"}, {"location": "editing/creating-your-deliverable/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "editing/creating-your-deliverable/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "editing/creating-your-deliverable/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "editing/glossary/", "text": "Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Glossary"}, {"location": "editing/glossary/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "editing/glossary/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "editing/glossary/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "editing/install-and-setup/", "text": "Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "editing/install-and-setup/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "editing/matches/", "text": "Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "editing/matches/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "editing/navigation/", "text": "Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation"}, {"location": "editing/navigation/#navigation", "text": "", "title": "Navigation"}, {"location": "editing/navigation/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "editing/navigation/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "editing/navigation/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "editing/other-useful-features/", "text": "Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Other useful features"}, {"location": "editing/other-useful-features/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "editing/other-useful-features/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "editing/other-useful-features/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "editing/other-useful-features/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "editing/other-useful-features/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "editing/other-useful-features/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "editing/other-useful-features/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "editing/qa-checks/", "text": "QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "QA checks"}, {"location": "editing/qa-checks/#qa-checks", "text": "", "title": "QA checks"}, {"location": "editing/qa-checks/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "editing/qa-checks/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "editing/qa-checks/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "editing/repetitions/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Repetitions"}, {"location": "editing/repetitions/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "editing/repetitions/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "editing/repetitions/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "editing/repetitions/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "editing/shortcuts/", "text": "a.md-footer__link--next[aria-label^=\"Next:\"], .md-nav__icon { display: none !important; } OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "editing/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "editing/tags/", "text": "Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Tags"}, {"location": "editing/tags/#tags", "text": "", "title": "Tags"}, {"location": "editing/tags/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "editing/tags/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "editing/tags/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "exercises/", "text": "OmegaT exercises \u00b6 Getting started \u00b6 In order to do these exercises, you'll have to download an offline OmegaT project package. Get your project \u00b6 Download project package project_task_fr-ZZ_offline_omt.omt . Unpack that project from OmegaT: Project > Unpack project from OMT file... Relevant section in the OmegaT guide How to unpack an offline project .", "title": "Getting started"}, {"location": "exercises/#omegat-exercises", "text": "", "title": "OmegaT exercises"}, {"location": "exercises/#getting-started", "text": "In order to do these exercises, you'll have to download an offline OmegaT project package.", "title": "Getting started"}, {"location": "exercises/#get-your-project", "text": "Download project package project_task_fr-ZZ_offline_omt.omt . Unpack that project from OmegaT: Project > Unpack project from OMT file... Relevant section in the OmegaT guide How to unpack an offline project .", "title": "Get your project"}, {"location": "exercises/alt/", "text": "06. Alternative translations \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification In the previous section you saw that translations of repeated segments (or edits in those translations) auto-propagate to all instances of that repeated segment when you save them (or leave the segment). That is convenient in many cases, but not always. Sometimes you'll have to prevent auto-propagation. To do that, you must create an alternative translation . Exercise 06.1: create alternative translation \u00b6 Go to segment #16 in the project. Source text reads: Pretty good Notice that it is translated with an auto-propagated translation. Pretty good and Pretty bad in segments #16 and #17 in this context refer to \"level of English\" which is masculine in French. However, your translations (\"Plut\u00f4t bonNE\" and \"Plut\u00f4t mauvaisE\") refers to \"situation economique\", which is feminine. You want to modify the translation in segments #16 and #17 to make it masculine, so that it agrees with \"level\" in French. Follow these three simple but VERY IMPORTANT steps: Go to Edit > Create Alternative Translation . Tip: Also available if you right-click the segment. Modify the translation to make it masculine Just remove the last character if you don't know French Press Ctrl + S to register the translation Warning This is a very important and delicate function of OmegaT. It's easy to use it correctly if you grasp well the three steps above, but it's also easy to make a mess if you don't. Please make sure you really follow the three steps above to the letter. Did you follow the steps above? If you did, now you'll notice that: your alternative translation appears now in the Multiple Translations pane, below the default translation and followed by the filename and the segment ID. the Segment Properties pane for that segment says now \"Is alternative: TRUE\" the (default) translation of segment #13 hasn't changed Press Enter to move to segment #17 and do the same steps as above. Info If you want more practice on this, go to segment #62 (source text reads: Subject: ), which is also repeated a few times. The first occurrence refers to an email subject line, whereas the other occurrences refer to the topic or subject matter field of books in a library classification system, so each of those requires a different translation, i.e. \"Objet\" vs \"Sujet\".", "title": "06 - Alternative translations"}, {"location": "exercises/alt/#06-alternative-translations", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification In the previous section you saw that translations of repeated segments (or edits in those translations) auto-propagate to all instances of that repeated segment when you save them (or leave the segment). That is convenient in many cases, but not always. Sometimes you'll have to prevent auto-propagation. To do that, you must create an alternative translation .", "title": "06. Alternative translations"}, {"location": "exercises/alt/#exercise-061-create-alternative-translation", "text": "Go to segment #16 in the project. Source text reads: Pretty good Notice that it is translated with an auto-propagated translation. Pretty good and Pretty bad in segments #16 and #17 in this context refer to \"level of English\" which is masculine in French. However, your translations (\"Plut\u00f4t bonNE\" and \"Plut\u00f4t mauvaisE\") refers to \"situation economique\", which is feminine. You want to modify the translation in segments #16 and #17 to make it masculine, so that it agrees with \"level\" in French. Follow these three simple but VERY IMPORTANT steps: Go to Edit > Create Alternative Translation . Tip: Also available if you right-click the segment. Modify the translation to make it masculine Just remove the last character if you don't know French Press Ctrl + S to register the translation Warning This is a very important and delicate function of OmegaT. It's easy to use it correctly if you grasp well the three steps above, but it's also easy to make a mess if you don't. Please make sure you really follow the three steps above to the letter. Did you follow the steps above? If you did, now you'll notice that: your alternative translation appears now in the Multiple Translations pane, below the default translation and followed by the filename and the segment ID. the Segment Properties pane for that segment says now \"Is alternative: TRUE\" the (default) translation of segment #13 hasn't changed Press Enter to move to segment #17 and do the same steps as above. Info If you want more practice on this, go to segment #62 (source text reads: Subject: ), which is also repeated a few times. The first occurrence refers to an email subject line, whereas the other occurrences refer to the topic or subject matter field of books in a library classification system, so each of those requires a different translation, i.e. \"Objet\" vs \"Sujet\".", "title": "Exercise 06.1: create alternative translation"}, {"location": "exercises/aut/", "text": "07. Special characters \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification You may insert special characters in different ways: autotext shortcut, character table, etc. Exercise 07.1: use a known autotext shortcut \u00b6 You may use the autotext shortcut \\sub2 to insert a subscript number 2 (i.e. \u2082 ). Now you know! :) Tip The \"suB\" part in the shorcut \\sub2 stands for subindex or subscript. Go to segment #72 and read the source text. Target text reads Le dioxyde de carbone (CO2) se dissout dans l'eau de mer pour former de l'acide carbonique. Delete number 2 in \u201cCO2\u201d (and keep the cursor right after \"CO\"). A subscript number should be used instead of a regular digit. In that same position, type the autotext shortcut \\sub2 Notice how the auto-completer window opens showing the autotext entry. Press Enter to insert the special character \u2082 . The result should be: CO\u2082 In this exercise you have used an autotext shortcut that you knew already. In the following exercises you'll find out an autotext entry that you don't know. Exercise 07.2: find special character in the list of autotext entries \u00b6 In this exercise, you must insert the multiplication symbol but you don't know what autotext entry you can use. Go to segment #74 Source text reads: Thermal conductivity coefficient
    (W/m \u00d7 K) Open the list of available shortcuts here . Look for the autotext entry for the multiplication symbol. You can use either \\times or \\x (how lucky, this one is shorter!) Translate segment #74 as you like (don't forget the part in parentheses). To translate the part in parenthesis, type \\x (or \\times ) between W/m and K . Notice how the auto-completer opens when you typed the autotext shortcut. Press Enter to insert the caracter. Result should be: W/m \u00d7 K Incorrect translation: W/m x K Info You can find the list of autotext entries in OmegaT guides > Miscellanea > Autotext Exercise 07.3: insert special character from the character table \u00b6 Remember the auto-completer? You used it to insert tags. You'll use it again now to insert a special character. Go to segment #75 Target text reads: \u201cLa densit\u00e9 de population est de 62 personnes par km2 en 2023.\u201d Delete number 2 in \u201ckm2\u201d (and keep your cursor right after \u201ckm\u201d). Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cCharacter table\u201d. Spot the relevant character \u00b2 and double click on it to insert it. The result should be: km\u00b2 Tip You could have inserted character \u00b2 with shortcut \\sup2 (where \"suP\" stands for superscript or superindex or superordinate). Exercise 07.4: insert special quotation marks \u00b6 French uses special quotation marks, called angle quotes or \"chevrons\". You can use autotext to insert them. Go to segment #77. Look at the translation of segment #76 and notice how the angle quotes are used there. L'eau est \u00ab satur\u00e9e \u00bb si... Translate segment #77. You can use the exact match that appears in the Matches pane. Type autotext shortcut << before \"insatur\u00e9e\" to insert character \u00ab followed by a non-breaking space. Type autotext shortcut >> after \"insatur\u00e9e\" to insert character \u00ab preceded by a non-breaking space. Expected results: \u00ab insatur\u00e9e \u00bb Remember If there's a special character that you need which you can't find in the list of autotext entries or the character table, please let us know through the Helpdesk and we'll add it for you.", "title": "07 - Special characters"}, {"location": "exercises/aut/#07-special-characters", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification You may insert special characters in different ways: autotext shortcut, character table, etc.", "title": "07. Special characters"}, {"location": "exercises/aut/#exercise-071-use-a-known-autotext-shortcut", "text": "You may use the autotext shortcut \\sub2 to insert a subscript number 2 (i.e. \u2082 ). Now you know! :) Tip The \"suB\" part in the shorcut \\sub2 stands for subindex or subscript. Go to segment #72 and read the source text. Target text reads Le dioxyde de carbone (CO2) se dissout dans l'eau de mer pour former de l'acide carbonique. Delete number 2 in \u201cCO2\u201d (and keep the cursor right after \"CO\"). A subscript number should be used instead of a regular digit. In that same position, type the autotext shortcut \\sub2 Notice how the auto-completer window opens showing the autotext entry. Press Enter to insert the special character \u2082 . The result should be: CO\u2082 In this exercise you have used an autotext shortcut that you knew already. In the following exercises you'll find out an autotext entry that you don't know.", "title": "Exercise 07.1: use a known autotext shortcut"}, {"location": "exercises/aut/#exercise-072-find-special-character-in-the-list-of-autotext-entries", "text": "In this exercise, you must insert the multiplication symbol but you don't know what autotext entry you can use. Go to segment #74 Source text reads: Thermal conductivity coefficient
    (W/m \u00d7 K) Open the list of available shortcuts here . Look for the autotext entry for the multiplication symbol. You can use either \\times or \\x (how lucky, this one is shorter!) Translate segment #74 as you like (don't forget the part in parentheses). To translate the part in parenthesis, type \\x (or \\times ) between W/m and K . Notice how the auto-completer opens when you typed the autotext shortcut. Press Enter to insert the caracter. Result should be: W/m \u00d7 K Incorrect translation: W/m x K Info You can find the list of autotext entries in OmegaT guides > Miscellanea > Autotext", "title": "Exercise 07.2: find special character in the list of autotext entries"}, {"location": "exercises/aut/#exercise-073-insert-special-character-from-the-character-table", "text": "Remember the auto-completer? You used it to insert tags. You'll use it again now to insert a special character. Go to segment #75 Target text reads: \u201cLa densit\u00e9 de population est de 62 personnes par km2 en 2023.\u201d Delete number 2 in \u201ckm2\u201d (and keep your cursor right after \u201ckm\u201d). Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cCharacter table\u201d. Spot the relevant character \u00b2 and double click on it to insert it. The result should be: km\u00b2 Tip You could have inserted character \u00b2 with shortcut \\sup2 (where \"suP\" stands for superscript or superindex or superordinate).", "title": "Exercise 07.3: insert special character from the character table"}, {"location": "exercises/aut/#exercise-074-insert-special-quotation-marks", "text": "French uses special quotation marks, called angle quotes or \"chevrons\". You can use autotext to insert them. Go to segment #77. Look at the translation of segment #76 and notice how the angle quotes are used there. L'eau est \u00ab satur\u00e9e \u00bb si... Translate segment #77. You can use the exact match that appears in the Matches pane. Type autotext shortcut << before \"insatur\u00e9e\" to insert character \u00ab followed by a non-breaking space. Type autotext shortcut >> after \"insatur\u00e9e\" to insert character \u00ab preceded by a non-breaking space. Expected results: \u00ab insatur\u00e9e \u00bb Remember If there's a special character that you need which you can't find in the list of autotext entries or the character table, please let us know through the Helpdesk and we'll add it for you.", "title": "Exercise 07.4: insert special quotation marks"}, {"location": "exercises/fnd/", "text": "08. Search \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Exercise 08.1: search for a selected expression \u00b6 Try to find the translation of \"translator\" in the translation memories. Press Ctrl + J and enter 47 to go to segment #47. Select the word translator . Press Ctrl + F to open the Text Search dialog. Notice how the word \"translator\" is already filled in in the search box. Check option \"Translated\" so that you will only find translated segments. Check box \"TMs\" under \"Search in\" to search in the translations memories. Press the Search button. Expected result: traducteur Exercise 08.2: search for a segment identifier \u00b6 You might need to refer to a certain segment by its identifier (the segment ID or key). Press Ctrl + F to open the Text Search dialog unless it's already open. Check option: In comments Type 123abc in the search box, and press Search . Expected results: 01_qq/03_qq_paq.xml -- 22> Neither good nor bad # name = 123abc Info Here # name refers to the segment identifier. Exercise 08.3: search for some source text \u00b6 One instance of the repeated segment \"Rather satisfied\" was not translated consistenly. Press Ctrl + F to open the Text Search dialog. Check options: Exact search In source All matching segments Search in: Memory Do not check options: Search in: TMs Type Rather satisfied in the search box, and press Search . Expected results: 27> Plut\u00f4t satisfait 32> Assez satisfait 37> Plut\u00f4t satisfait Notice that here is one instance of the repeated segment \"Rather satisfied\" that was not translated consistenly. Can you see which translation is inconsistent?", "title": "08 - Search"}, {"location": "exercises/fnd/#08-search", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification", "title": "08. Search"}, {"location": "exercises/fnd/#exercise-081-search-for-a-selected-expression", "text": "Try to find the translation of \"translator\" in the translation memories. Press Ctrl + J and enter 47 to go to segment #47. Select the word translator . Press Ctrl + F to open the Text Search dialog. Notice how the word \"translator\" is already filled in in the search box. Check option \"Translated\" so that you will only find translated segments. Check box \"TMs\" under \"Search in\" to search in the translations memories. Press the Search button. Expected result: traducteur", "title": "Exercise 08.1: search for a selected expression"}, {"location": "exercises/fnd/#exercise-082-search-for-a-segment-identifier", "text": "You might need to refer to a certain segment by its identifier (the segment ID or key). Press Ctrl + F to open the Text Search dialog unless it's already open. Check option: In comments Type 123abc in the search box, and press Search . Expected results: 01_qq/03_qq_paq.xml -- 22> Neither good nor bad # name = 123abc Info Here # name refers to the segment identifier.", "title": "Exercise 08.2: search for a segment identifier"}, {"location": "exercises/fnd/#exercise-083-search-for-some-source-text", "text": "One instance of the repeated segment \"Rather satisfied\" was not translated consistenly. Press Ctrl + F to open the Text Search dialog. Check options: Exact search In source All matching segments Search in: Memory Do not check options: Search in: TMs Type Rather satisfied in the search box, and press Search . Expected results: 27> Plut\u00f4t satisfait 32> Assez satisfait 37> Plut\u00f4t satisfait Notice that here is one instance of the repeated segment \"Rather satisfied\" that was not translated consistenly. Can you see which translation is inconsistent?", "title": "Exercise 08.3: search for some source text"}, {"location": "exercises/mat/", "text": "02. Matches \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Exercise 02.1: translate from scratch \u00b6 Press Ctrl + J and enter 1 to go to segment #1. Source text reads Welcome to this survey! Translate segment #1. Suggested translation: Bienvenue \u00e0 cette enqu\u00e8te ! Press Enter to go to the next segment. Exercise 02.2: pretranslated and locked \u00b6 You're now in segment #2. Notice how this segment is pretranslated. Notice that it has an orange background. That means that this is an enforced translation. In other words, the translation is not editable. Make some edits to modify the translation. Press F5 to reload the project. Notice how your edits are now gone. Press Ctrl + U to go to the next untranslated segment. That should take you to segment #3. Exercise 02.3: insert match and update it \u00b6 You're now in segment #3. Notice that there's a fuzzy match you can use. Press Ctrl + I to insert it. Looking at the match in the Matches pane, notice the difference between the new source text and the source text in \"tracked changes\". Update the inserted translation so that it corresponds to the source text you're translating. Tip: Replace sanitaire with \u00e9conomique . Press Ctrl + U to go to the next untranslated segment. That should take you to segment #5. Exercise 02.4: insert match and update it \u00b6 Notice how pressing Ctrl + U has jumped over segment #4, which was already translated. You're in segment #5. There is a 50% match that you could use. Press Ctrl + I to insert it. Now update the translation so that it corresponds to the source text. Tip: delete Tr\u00e8s and change the case of the first letter. Expected result: Bon Press Ctrl + U to go to the next untranslated segment. That should take you to segment #6. Exercise 02.5: insert exact match \u00b6 You're in segment #6. Notice that there's an exact match which you can use as is. Your lucky day! Press Ctrl + I to insert it. There's nothing else to do this time :) Press Ctrl + U to go to the next untranslated segment. That should take you to segment #7. Exercise 02.6: select text and insert \u00b6 You're in segment #7. Notice that there are two 50% matches that you could use. See what is the part that can be used in the first match. Press Ctrl + 2 to select the second match. See what is the part that can be used in the second match. Press Ctrl + 1 to select the first match again. Alternate between Ctrl + 1 and Ctrl + 2 to highlight the differences in each match. With your mouse, select Tr\u00e8s in match #1. The translation of \"very\" in the first match is something you can use. Press Ctrl + I to insert your selection. With your mouse, select mauvais in match #2. You can also use the translation of \"bad\" in the second match. Press Ctrl + I to insert your selection. Expected result: tr\u00e8s mauvais Press Ctrl + U to go to the next untranslated segment. That should take you to segment #8. Exercise 02.7: select a match and insert it \u00b6 You're now in segment #8. Notice how the first match is not so convenient as the second match. Press Ctrl + 2 to select match #2. Press Ctrl + I to insert match #2. Exercise 02.8: pretranslated and editable \u00b6 You're still in segment #8. Notice how segments #9 and #10 are pretranslated. Notice that they have a pink background. That means that they can be edited. Press Ctrl + U to go to the next untranslated segment. Exercise 02.9: almost identical match \u00b6 You're in segment #11. Notice how pressing Ctrl + U has jumped over the two pretranslated segments. Source text reads Welcome to this survey. Notice how this segment is almost identical to the first segment you translated. The only difference is in the final punctuation. Press Ctrl + I to insert the match. Update the translation now. Replace the exclamation mark ! with a full stop . Press Ctrl + U to go to the next untranslated segment. That should take you to segment #12. Exercise 02.10: insert match and update it \u00b6 Ok, the last one if you have time :) You're now in segment #12. Notice that there's a fuzzy match you can use. Press Ctrl + I to insert it. Looking at the match in the Matches pane, notice the difference between the new source text and the source text in \"tracked changes\". Update the inserted translation so that it corresponds to the source text you're translating. Tip: Replace financi\u00e8re with \u00e9conomique Well done!", "title": "02 - Matches"}, {"location": "exercises/mat/#02-matches", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification", "title": "02. Matches"}, {"location": "exercises/mat/#exercise-021-translate-from-scratch", "text": "Press Ctrl + J and enter 1 to go to segment #1. Source text reads Welcome to this survey! Translate segment #1. Suggested translation: Bienvenue \u00e0 cette enqu\u00e8te ! Press Enter to go to the next segment.", "title": "Exercise 02.1: translate from scratch"}, {"location": "exercises/mat/#exercise-022-pretranslated-and-locked", "text": "You're now in segment #2. Notice how this segment is pretranslated. Notice that it has an orange background. That means that this is an enforced translation. In other words, the translation is not editable. Make some edits to modify the translation. Press F5 to reload the project. Notice how your edits are now gone. Press Ctrl + U to go to the next untranslated segment. That should take you to segment #3.", "title": "Exercise 02.2: pretranslated and locked"}, {"location": "exercises/mat/#exercise-023-insert-match-and-update-it", "text": "You're now in segment #3. Notice that there's a fuzzy match you can use. Press Ctrl + I to insert it. Looking at the match in the Matches pane, notice the difference between the new source text and the source text in \"tracked changes\". Update the inserted translation so that it corresponds to the source text you're translating. Tip: Replace sanitaire with \u00e9conomique . Press Ctrl + U to go to the next untranslated segment. That should take you to segment #5.", "title": "Exercise 02.3: insert match and update it"}, {"location": "exercises/mat/#exercise-024-insert-match-and-update-it", "text": "Notice how pressing Ctrl + U has jumped over segment #4, which was already translated. You're in segment #5. There is a 50% match that you could use. Press Ctrl + I to insert it. Now update the translation so that it corresponds to the source text. Tip: delete Tr\u00e8s and change the case of the first letter. Expected result: Bon Press Ctrl + U to go to the next untranslated segment. That should take you to segment #6.", "title": "Exercise 02.4: insert match and update it"}, {"location": "exercises/mat/#exercise-025-insert-exact-match", "text": "You're in segment #6. Notice that there's an exact match which you can use as is. Your lucky day! Press Ctrl + I to insert it. There's nothing else to do this time :) Press Ctrl + U to go to the next untranslated segment. That should take you to segment #7.", "title": "Exercise 02.5: insert exact match"}, {"location": "exercises/mat/#exercise-026-select-text-and-insert", "text": "You're in segment #7. Notice that there are two 50% matches that you could use. See what is the part that can be used in the first match. Press Ctrl + 2 to select the second match. See what is the part that can be used in the second match. Press Ctrl + 1 to select the first match again. Alternate between Ctrl + 1 and Ctrl + 2 to highlight the differences in each match. With your mouse, select Tr\u00e8s in match #1. The translation of \"very\" in the first match is something you can use. Press Ctrl + I to insert your selection. With your mouse, select mauvais in match #2. You can also use the translation of \"bad\" in the second match. Press Ctrl + I to insert your selection. Expected result: tr\u00e8s mauvais Press Ctrl + U to go to the next untranslated segment. That should take you to segment #8.", "title": "Exercise 02.6: select text and insert"}, {"location": "exercises/mat/#exercise-027-select-a-match-and-insert-it", "text": "You're now in segment #8. Notice how the first match is not so convenient as the second match. Press Ctrl + 2 to select match #2. Press Ctrl + I to insert match #2.", "title": "Exercise 02.7: select a match and insert it"}, {"location": "exercises/mat/#exercise-028-pretranslated-and-editable", "text": "You're still in segment #8. Notice how segments #9 and #10 are pretranslated. Notice that they have a pink background. That means that they can be edited. Press Ctrl + U to go to the next untranslated segment.", "title": "Exercise 02.8: pretranslated and editable"}, {"location": "exercises/mat/#exercise-029-almost-identical-match", "text": "You're in segment #11. Notice how pressing Ctrl + U has jumped over the two pretranslated segments. Source text reads Welcome to this survey. Notice how this segment is almost identical to the first segment you translated. The only difference is in the final punctuation. Press Ctrl + I to insert the match. Update the translation now. Replace the exclamation mark ! with a full stop . Press Ctrl + U to go to the next untranslated segment. That should take you to segment #12.", "title": "Exercise 02.9: almost identical match"}, {"location": "exercises/mat/#exercise-0210-insert-match-and-update-it", "text": "Ok, the last one if you have time :) You're now in segment #12. Notice that there's a fuzzy match you can use. Press Ctrl + I to insert it. Looking at the match in the Matches pane, notice the difference between the new source text and the source text in \"tracked changes\". Update the inserted translation so that it corresponds to the source text you're translating. Tip: Replace financi\u00e8re with \u00e9conomique Well done!", "title": "Exercise 02.10: insert match and update it"}, {"location": "exercises/nav/", "text": "01. Navigation \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Remember The active segment always has a green background. Exercise 01.1: moving through the project \u00b6 Press Ctrl + J and enter 1 to go to segment #1. Source text reads Welcome to this survey! Press Enter to move to the next segment. You are now in segment #2. Press Ctrl + U to move to the next untranslated segment. You are now in segment #3. Press Enter twice in a row to go forward 2 segments. You end up in segment #5. Press Ctrl + Enter twice in a row to go backwards 2 segments. You are now in segment #3. Press Ctrl + U once to go to the next untranslated segment. You end up in segment #5 again. Notice that you have jumped segment #4, which is already translated (in pink). Tip Press Ctrl + U when you're translating. Press Enter when you're reviewing a translation. Exercise 01.2: moving through the project a bit more \u00b6 Press Ctrl + J and enter number 25 to go to segment #25. Source text reads: Generally speaking, please tell me how satisfied you are with public transport where you live. Press Ctrl + U to jump to the next untranslated segment. You are now on segment #30. Press Enter to move the next segment. You are now on segment #31. Oops, you haven't translated segment #30. Press Ctrl + Enter to go back to it. You are now on segment #30 again. Scroll down until you see another untranslated segment in that file. Source text reads: Generally speaking, please tell me how satisfied you are with schools and other educational facilities where you live. Double click on that segment. You are now on segment #53. Press keyboard shortcut Ctrl + J and enter number 1 to go to segment number #1. Recap In this exercise you have practiced several ways to activate a segment: Enter opens the next segment Ctrl + Enter opens the previous segment Ctrl + U opens the next untranslated segment Ctrl + J (plus the segment numberj) opens a specific segment", "title": "01 - Navigation"}, {"location": "exercises/nav/#01-navigation", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Remember The active segment always has a green background.", "title": "01. Navigation"}, {"location": "exercises/nav/#exercise-011-moving-through-the-project", "text": "Press Ctrl + J and enter 1 to go to segment #1. Source text reads Welcome to this survey! Press Enter to move to the next segment. You are now in segment #2. Press Ctrl + U to move to the next untranslated segment. You are now in segment #3. Press Enter twice in a row to go forward 2 segments. You end up in segment #5. Press Ctrl + Enter twice in a row to go backwards 2 segments. You are now in segment #3. Press Ctrl + U once to go to the next untranslated segment. You end up in segment #5 again. Notice that you have jumped segment #4, which is already translated (in pink). Tip Press Ctrl + U when you're translating. Press Enter when you're reviewing a translation.", "title": "Exercise 01.1: moving through the project"}, {"location": "exercises/nav/#exercise-012-moving-through-the-project-a-bit-more", "text": "Press Ctrl + J and enter number 25 to go to segment #25. Source text reads: Generally speaking, please tell me how satisfied you are with public transport where you live. Press Ctrl + U to jump to the next untranslated segment. You are now on segment #30. Press Enter to move the next segment. You are now on segment #31. Oops, you haven't translated segment #30. Press Ctrl + Enter to go back to it. You are now on segment #30 again. Scroll down until you see another untranslated segment in that file. Source text reads: Generally speaking, please tell me how satisfied you are with schools and other educational facilities where you live. Double click on that segment. You are now on segment #53. Press keyboard shortcut Ctrl + J and enter number 1 to go to segment number #1. Recap In this exercise you have practiced several ways to activate a segment: Enter opens the next segment Ctrl + Enter opens the previous segment Ctrl + U opens the next untranslated segment Ctrl + J (plus the segment numberj) opens a specific segment", "title": "Exercise 01.2: moving through the project a bit more"}, {"location": "exercises/qac/", "text": "09. QA checks \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Exercise 09.1: check tag issues \u00b6 Open the QA checks dialog in Tools > Check for issues... . Uncheck all options except \"Tag Issues\" The \"Tag Issues\" check is mandatory, you cannot unselect it. Press \"OK\" Notice that there is (at least) an issue about \"Bad nesting\". Press the \"Jump to segment\" button. OmegaT will open the segment with the issue. You should be on segment #25 Look at the tags and notice what the issue is about. The order of tags is incorrect. Remove the two tags and insert them again. Expected result: De mani\u00e8re g\u00e9n\u00e9rale, dites-moi si \u00e0 quel point vous \u00eates satisfait avec les transports publics l\u00e0 o\u00f9 vous vivez. Press the \"Refresh\" button in the Issues dialog to confirm that the issue is gone. Tip If you're not sure how to fix a tag issue during a production task, please request support through the Helpdesk. Exercise 09.2: check completion \u00b6 Go to Tools > Statistics . Look at the Remaining row in the project statistics. Notice whether the project is fully translated. Tip If you see a number higher than zero in the Remaining row(s), that means that there are still some remaining untranslated segments. All segments should be translated before you can finalize your task. Tip Press Ctrl + U to go to the next untranslated segment.", "title": "09 - QA checks"}, {"location": "exercises/qac/#09-qa-checks", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification", "title": "09. QA checks"}, {"location": "exercises/qac/#exercise-091-check-tag-issues", "text": "Open the QA checks dialog in Tools > Check for issues... . Uncheck all options except \"Tag Issues\" The \"Tag Issues\" check is mandatory, you cannot unselect it. Press \"OK\" Notice that there is (at least) an issue about \"Bad nesting\". Press the \"Jump to segment\" button. OmegaT will open the segment with the issue. You should be on segment #25 Look at the tags and notice what the issue is about. The order of tags is incorrect. Remove the two tags and insert them again. Expected result: De mani\u00e8re g\u00e9n\u00e9rale, dites-moi si \u00e0 quel point vous \u00eates satisfait avec les transports publics l\u00e0 o\u00f9 vous vivez. Press the \"Refresh\" button in the Issues dialog to confirm that the issue is gone. Tip If you're not sure how to fix a tag issue during a production task, please request support through the Helpdesk.", "title": "Exercise 09.1: check tag issues"}, {"location": "exercises/qac/#exercise-092-check-completion", "text": "Go to Tools > Statistics . Look at the Remaining row in the project statistics. Notice whether the project is fully translated. Tip If you see a number higher than zero in the Remaining row(s), that means that there are still some remaining untranslated segments. All segments should be translated before you can finalize your task. Tip Press Ctrl + U to go to the next untranslated segment.", "title": "Exercise 09.2: check completion"}, {"location": "exercises/rec/", "text": "03. Reconciliation \u00b6 The relevant section in the guide... See the relevant section (about matches) in your guide: Reconciliation This section includes some bonus exercises specifically addressed to reconcilers. You may skip this section if you're not going to reconcile. Getting started \u00b6 Here's a UI preference that may be useful for you when you reconcile. In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 100 With that setting, the Matches pane will show you only the translations you need to reconcile. Please remember to restore the default value when you're not reconciling. Exercise 03.01: inserting one match \u00b6 Go to segment #55 and read it. Here comes a story for you. Source text reads Once upon a time there was a reconciler who worked in OmegaT. You have one exact match. Press Ctrl + I to insert it. Easy start. Now press Ctrl + U to move to the next unreconciled segment. Read segment #56. You have one exact match. Press Ctrl + I to translate the segment with that match. Still easy. Press Ctrl + U to move to the next unreconciled segment. Info You only see one match if \"translation 1\" and \"translation 2\" are identical. Exercise 03.02: selecting the match \u00b6 You're now on segment #57. Read segment #57. Notice that now you can see two matches because \"translation 1\" and \"translation 2\" are different now. You want to use the first translation (selected by default). Press Ctrl + I to insert match #1. Translation reads Parfois, l'une des deux traductions \u00e9tait bonne, et l'autre \u00e9tait mauvaise, donc le choix \u00e9tait clair. Press Ctrl + U to move to the next unreconciled segment. You're now on segment #58. 11. Read segment #58. 11. Here you want to use the second translation. Press Ctrl + 2 to select match #2. 12. Press Ctrl + I to insert it. Translation reads D'autres fois, la premi\u00e8re traduction \u00e9tait mauvaise, mais la seconde \u00e9tait bonne, donc le choix \u00e9tait \u00e9galement clair. Press Ctrl + U to move to the next unreconciled segment. Exersise 04.03: editing the inserted translation \u00b6 You're now on segment #59. Read segment #59. Press Ctrl + I to insert the exiting match. Edit the translation to make it a good translation. Tip: Remove the excessive SSs in parfoisSSs . Press Ctrl + U to move to the next unreconciled segment. Exercise 03.03: assembling fragments \u00b6 You are in segment #60. In match #1, select Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, Press Ctrl + I to insert the text you have selected. In match #2, select , mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. Press Ctrl + I to insert the text you have selected now. Expected result: Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. You have combined two parts of two translations to create one single reconciled version. Congrats! Finally \u00b6 Please remember to restore the default threshold to show matches: In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 50.", "title": "03 - Reconciliation"}, {"location": "exercises/rec/#03-reconciliation", "text": "The relevant section in the guide... See the relevant section (about matches) in your guide: Reconciliation This section includes some bonus exercises specifically addressed to reconcilers. You may skip this section if you're not going to reconcile.", "title": "03. Reconciliation"}, {"location": "exercises/rec/#getting-started", "text": "Here's a UI preference that may be useful for you when you reconcile. In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 100 With that setting, the Matches pane will show you only the translations you need to reconcile. Please remember to restore the default value when you're not reconciling.", "title": "Getting started"}, {"location": "exercises/rec/#exercise-0301-inserting-one-match", "text": "Go to segment #55 and read it. Here comes a story for you. Source text reads Once upon a time there was a reconciler who worked in OmegaT. You have one exact match. Press Ctrl + I to insert it. Easy start. Now press Ctrl + U to move to the next unreconciled segment. Read segment #56. You have one exact match. Press Ctrl + I to translate the segment with that match. Still easy. Press Ctrl + U to move to the next unreconciled segment. Info You only see one match if \"translation 1\" and \"translation 2\" are identical.", "title": "Exercise 03.01: inserting one match"}, {"location": "exercises/rec/#exercise-0302-selecting-the-match", "text": "You're now on segment #57. Read segment #57. Notice that now you can see two matches because \"translation 1\" and \"translation 2\" are different now. You want to use the first translation (selected by default). Press Ctrl + I to insert match #1. Translation reads Parfois, l'une des deux traductions \u00e9tait bonne, et l'autre \u00e9tait mauvaise, donc le choix \u00e9tait clair. Press Ctrl + U to move to the next unreconciled segment. You're now on segment #58. 11. Read segment #58. 11. Here you want to use the second translation. Press Ctrl + 2 to select match #2. 12. Press Ctrl + I to insert it. Translation reads D'autres fois, la premi\u00e8re traduction \u00e9tait mauvaise, mais la seconde \u00e9tait bonne, donc le choix \u00e9tait \u00e9galement clair. Press Ctrl + U to move to the next unreconciled segment.", "title": "Exercise 03.02: selecting the match"}, {"location": "exercises/rec/#exersise-0403-editing-the-inserted-translation", "text": "You're now on segment #59. Read segment #59. Press Ctrl + I to insert the exiting match. Edit the translation to make it a good translation. Tip: Remove the excessive SSs in parfoisSSs . Press Ctrl + U to move to the next unreconciled segment.", "title": "Exersise 04.03: editing the inserted translation"}, {"location": "exercises/rec/#exercise-0303-assembling-fragments", "text": "You are in segment #60. In match #1, select Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, Press Ctrl + I to insert the text you have selected. In match #2, select , mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. Press Ctrl + I to insert the text you have selected now. Expected result: Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. You have combined two parts of two translations to create one single reconciled version. Congrats!", "title": "Exercise 03.03: assembling fragments"}, {"location": "exercises/rec/#finally", "text": "Please remember to restore the default threshold to show matches: In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 50.", "title": "Finally"}, {"location": "exercises/rep/", "text": "05. Repetitions \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Exercise 05.1: recognize repeated segments \u00b6 Press Ctrl + J and enter 13 to go to segment #13. Source text reads: Pretty good Notice how the segment marker says that this segment is repeated three more times. . Look at the Segment Properties pane. It says \"Is duplicate: FIRST\" Right click on the segment. See how all the instances are listed and identified by their segment number. Select Segment 16 on the list to go to segment #16. Look at the Segment Properties pane for segment #16. It says \"Is duplicate: NEXT\" Right click on segment #16 to see instances listed again, go back to segment #13 again. Exercise 05.2: auto-propagate translations \u00b6 Go to segment #12. Translate segment #12. You can insert the match ( Ctrl + I ) and update it (replace financi\u00e8re with \u00e9conomique ) Notice how \"situation \u00e9conomique\" is grammatically feminine in French. Go to segment #13 and translate it. Suggested translation: Plut\u00f4t bonNE The -NE ending is the feminine suffix, because \"Good\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #13 to go to segment #14. Notice how the translation is auto-propagated to segment #16. Translate segment #14. Suggested translation: Plut\u00f4t mauvaisE The -E ending is the feminine suffix, because \"Bad\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #14 to confirm the translation of segment #14 and go to the next segment. Notice how the translation is auto-propagated to segment #17. Exercise 05.3: auto-propagate edits in translations \u00b6 Go to segment #16 in the project. You can see that it is translated with your auto-propagated translation. Modify the translation (append \"xx\") in segment #16 and press Ctrl + S to save the translation. Notice how the translation of segment #13 also changes. Do the same in segment #17 and see how changes auto-propagate to segment #14. Tip Shortcut Ctrl + S saves the translation. You can also save in Project > Save , but using the mouse takes longer ;)", "title": "05 - Repetitions"}, {"location": "exercises/rep/#05-repetitions", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification", "title": "05. Repetitions"}, {"location": "exercises/rep/#exercise-051-recognize-repeated-segments", "text": "Press Ctrl + J and enter 13 to go to segment #13. Source text reads: Pretty good Notice how the segment marker says that this segment is repeated three more times. . Look at the Segment Properties pane. It says \"Is duplicate: FIRST\" Right click on the segment. See how all the instances are listed and identified by their segment number. Select Segment 16 on the list to go to segment #16. Look at the Segment Properties pane for segment #16. It says \"Is duplicate: NEXT\" Right click on segment #16 to see instances listed again, go back to segment #13 again.", "title": "Exercise 05.1: recognize repeated segments"}, {"location": "exercises/rep/#exercise-052-auto-propagate-translations", "text": "Go to segment #12. Translate segment #12. You can insert the match ( Ctrl + I ) and update it (replace financi\u00e8re with \u00e9conomique ) Notice how \"situation \u00e9conomique\" is grammatically feminine in French. Go to segment #13 and translate it. Suggested translation: Plut\u00f4t bonNE The -NE ending is the feminine suffix, because \"Good\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #13 to go to segment #14. Notice how the translation is auto-propagated to segment #16. Translate segment #14. Suggested translation: Plut\u00f4t mauvaisE The -E ending is the feminine suffix, because \"Bad\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #14 to confirm the translation of segment #14 and go to the next segment. Notice how the translation is auto-propagated to segment #17.", "title": "Exercise 05.2: auto-propagate translations"}, {"location": "exercises/rep/#exercise-053-auto-propagate-edits-in-translations", "text": "Go to segment #16 in the project. You can see that it is translated with your auto-propagated translation. Modify the translation (append \"xx\") in segment #16 and press Ctrl + S to save the translation. Notice how the translation of segment #13 also changes. Do the same in segment #17 and see how changes auto-propagate to segment #14. Tip Shortcut Ctrl + S saves the translation. You can also save in Project > Save , but using the mouse takes longer ;)", "title": "Exercise 05.3: auto-propagate edits in translations"}, {"location": "exercises/tag/", "text": "04. Tags \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Exercise 04.1: insert paired tags \u00b6 Press Ctrl + J and enter 40 to go to segment #40, which is untranslated. Source text reads: Click Play to see it in action. Notice the two tags in the segment. With your mouse, hover over the two tags and notice how the two tags are paired . The first tag stands for and the second tag stands for . Translate segment #40. Suggested translation: Cliquez sur Jouer pour voir \u00e7a en action. Select the part of the translation that corresponds to \"Play\" Tip: you should select Jouer Press Ctrl + Space to open the auto-completer. Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cMissing tags\u201d section. The first option (i.e. | ) is selected by default. Press Enter to insert tag pair. Notice how the two paired tags are inserted around the selected text in the translation. Expected result: Cliquez sur Jouer pour le voir en action. Well done! Exercise 04.2: see what tags stand for \u00b6 Go to segment #41. Source text reads if sensor detects black Notice how the segment contains one standalone tag. Hover over the tag to see what the tag stands for. The tooltip should show {{ sensor_type }} Go to the next segment, #42. Notice how this segment has two standalone tags, not two paired tags! Check what the two tags stand for. The tooltips should show {{ object1 }} and {{ object2 }} Warning The difference between two standalone tags and two paired tags is very important. Exercise 04.3: insert standalone tags \u00b6 Go to segment #43. Notice that the tag is missing in the translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: right at the end of the translation Press Ctrl + Space to launch the auto-completer and insert the tag. Go to segment #44. Notice how the tag is also missing in this translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: click between tourner \u00e0 droite jusqu'\u00e0 ce que and le capteur d\u00e9tecte le noir Use the auto-completer to insert the missing tag. Exercise 04.4: insert standalone tag as you translate \u00b6 Go to segment #45. To translate the segment and insert the tag, proceed in this way: Translate \"repeat\" Suggested translation of the first part: r\u00e9p\u00e9ter Use the auto-completer to insert the missing tag Remember the shortcut to launch the auto-completer is Ctrl + Space . Translate \"times\" Suggested translation of the second part: fois You have inserted the tag as you made progress through the translation. Exercise 04.5: trigger the tag tooltip \u00b6 Press Ctrl + J and enter 48 to go to segment #48. Source text reads: The translator had to pay attention to formatting such as bold, italics, underline. Hover over the tags with your mouse to display a tooltip that shows the line code the tags stand for. Tip: the tooltip should display HTML tags , , etc. Exercise 04.6: insert more tags \u00b6 Still in segment #48, press Ctrl + I to insert the fuzzy match. Notice how most tags are missing in the translation. Select the part of the translation that corresponds to \u201cbold\u201d Tip: le gras Press Ctrl + Space to open the \"Missing tags\" section in the auto-completer. The first line (i.e. ) is selected by default. Press Enter to insert the tag pair that appears in the first line of the auto-completer. Notice how the tags have been inserted around the selected text Results should be le gras Do the same for the translation of \u201citalics\u201d Results should be l\u2019italique Notice how you cannot insert a tag pair around the translation of \u201cunderline\u201d because closing tag     is already inserted. Place the mouse cursor in the position where you would like to insert the tag that is paired with . Use the auto-completer ( Ctrl + Space ) to insert tag . Results should be le soulignement Well done!", "title": "04 - Tags"}, {"location": "exercises/tag/#04-tags", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification", "title": "04. Tags"}, {"location": "exercises/tag/#exercise-041-insert-paired-tags", "text": "Press Ctrl + J and enter 40 to go to segment #40, which is untranslated. Source text reads: Click Play to see it in action. Notice the two tags in the segment. With your mouse, hover over the two tags and notice how the two tags are paired . The first tag stands for and the second tag stands for . Translate segment #40. Suggested translation: Cliquez sur Jouer pour voir \u00e7a en action. Select the part of the translation that corresponds to \"Play\" Tip: you should select Jouer Press Ctrl + Space to open the auto-completer. Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cMissing tags\u201d section. The first option (i.e. | ) is selected by default. Press Enter to insert tag pair. Notice how the two paired tags are inserted around the selected text in the translation. Expected result: Cliquez sur Jouer pour le voir en action. Well done!", "title": "Exercise 04.1: insert paired tags"}, {"location": "exercises/tag/#exercise-042-see-what-tags-stand-for", "text": "Go to segment #41. Source text reads if sensor detects black Notice how the segment contains one standalone tag. Hover over the tag to see what the tag stands for. The tooltip should show {{ sensor_type }} Go to the next segment, #42. Notice how this segment has two standalone tags, not two paired tags! Check what the two tags stand for. The tooltips should show {{ object1 }} and {{ object2 }} Warning The difference between two standalone tags and two paired tags is very important.", "title": "Exercise 04.2: see what tags stand for"}, {"location": "exercises/tag/#exercise-043-insert-standalone-tags", "text": "Go to segment #43. Notice that the tag is missing in the translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: right at the end of the translation Press Ctrl + Space to launch the auto-completer and insert the tag. Go to segment #44. Notice how the tag is also missing in this translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: click between tourner \u00e0 droite jusqu'\u00e0 ce que and le capteur d\u00e9tecte le noir Use the auto-completer to insert the missing tag.", "title": "Exercise 04.3: insert standalone tags"}, {"location": "exercises/tag/#exercise-044-insert-standalone-tag-as-you-translate", "text": "Go to segment #45. To translate the segment and insert the tag, proceed in this way: Translate \"repeat\" Suggested translation of the first part: r\u00e9p\u00e9ter Use the auto-completer to insert the missing tag Remember the shortcut to launch the auto-completer is Ctrl + Space . Translate \"times\" Suggested translation of the second part: fois You have inserted the tag as you made progress through the translation.", "title": "Exercise 04.4: insert standalone tag as you translate"}, {"location": "exercises/tag/#exercise-045-trigger-the-tag-tooltip", "text": "Press Ctrl + J and enter 48 to go to segment #48. Source text reads: The translator had to pay attention to formatting such as bold, italics, underline. Hover over the tags with your mouse to display a tooltip that shows the line code the tags stand for. Tip: the tooltip should display HTML tags , , etc.", "title": "Exercise 04.5: trigger the tag tooltip"}, {"location": "exercises/tag/#exercise-046-insert-more-tags", "text": "Still in segment #48, press Ctrl + I to insert the fuzzy match. Notice how most tags are missing in the translation. Select the part of the translation that corresponds to \u201cbold\u201d Tip: le gras Press Ctrl + Space to open the \"Missing tags\" section in the auto-completer. The first line (i.e. ) is selected by default. Press Enter to insert the tag pair that appears in the first line of the auto-completer. Notice how the tags have been inserted around the selected text Results should be le gras Do the same for the translation of \u201citalics\u201d Results should be l\u2019italique Notice how you cannot insert a tag pair around the translation of \u201cunderline\u201d because closing tag is already inserted. Place the mouse cursor in the position where you would like to insert the tag that is paired with . Use the auto-completer ( Ctrl + Space ) to insert tag . Results should be le soulignement Well done!", "title": "Exercise 04.6: insert more tags"}, {"location": "exercises/tgt/", "text": "10. Working with team projects \u00b6 Unlike in previous cycles, in this cycle you will work on an online team project hosted in a git repository. Download team project from git repository \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification Details \u00b6 Here are the details of a team project you can download for training purposes. Warning This is not the project where you must work to produce your translation. URL of the git repository: https://github.com/capstanlqc/project_task_fr-ZZ_omt.git Username: pisa25npm Password: password (For security reasons, the password is provided in a separate page. Just click on the link above to open it.) Steps \u00b6 In OmegaT, go to Project > Download Team Project . Paste the URL of the git repository in the \"Repository URL\" field. Then click on the \"New Local Project Folder\" field. OmegaT will propose a location to clone the project in your machine, e.g. something like C:\\Users\\USER\\project_task_fr-ZZ_omt (where USER is your username). The name of the project is highlighted in yellow in the screenshot below: If the proposed path to the local project folder is fine, just press OK . All files in the project will be downloaded and the project will be open in OmegaT after a few seconds. Want to edit the local project folder? You may change or edit the path to the location where the project will be created, e.g. to create the project in a PISA folder: In any case, do not change the name of the project (highlighted in yellow below): Please check our File organization tips, they could help you keep your files and folders more organized. Warning The location where you create the team project should not be inside a folder sync'ed by Dropbox, OneDrive, Nextcloud, etc. (any sync'ing service in your machine). Commit target files \u00b6 The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification To commit target files (e.g. to update the preview): Go to Project > Commit Target Files .", "title": "10 - Team projects"}, {"location": "exercises/tgt/#10-working-with-team-projects", "text": "Unlike in previous cycles, in this cycle you will work on an online team project hosted in a git repository.", "title": "10. Working with team projects"}, {"location": "exercises/tgt/#download-team-project-from-git-repository", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification", "title": "Download team project from git repository"}, {"location": "exercises/tgt/#details", "text": "Here are the details of a team project you can download for training purposes. Warning This is not the project where you must work to produce your translation. URL of the git repository: https://github.com/capstanlqc/project_task_fr-ZZ_omt.git Username: pisa25npm Password: password (For security reasons, the password is provided in a separate page. Just click on the link above to open it.)", "title": "Details"}, {"location": "exercises/tgt/#steps", "text": "In OmegaT, go to Project > Download Team Project . Paste the URL of the git repository in the \"Repository URL\" field. Then click on the \"New Local Project Folder\" field. OmegaT will propose a location to clone the project in your machine, e.g. something like C:\\Users\\USER\\project_task_fr-ZZ_omt (where USER is your username). The name of the project is highlighted in yellow in the screenshot below: If the proposed path to the local project folder is fine, just press OK . All files in the project will be downloaded and the project will be open in OmegaT after a few seconds. Want to edit the local project folder? You may change or edit the path to the location where the project will be created, e.g. to create the project in a PISA folder: In any case, do not change the name of the project (highlighted in yellow below): Please check our File organization tips, they could help you keep your files and folders more organized. Warning The location where you create the team project should not be inside a folder sync'ed by Dropbox, OneDrive, Nextcloud, etc. (any sync'ing service in your machine).", "title": "Steps"}, {"location": "exercises/tgt/#commit-target-files", "text": "The relevant section in the guides... See the relevant section in your guide: Translation Reconciliation Adaptation Verification To commit target files (e.g. to update the preview): Go to Project > Commit Target Files .", "title": "Commit target files"}, {"location": "exercises_02/", "text": "OmegaT exercises - Getting started \u00b6 Getting your project \u00b6 For countries (NOT READY YET): \u00b6 Download project package project_task_fr-ZZ_offline_omt.omt . Unpack that project. Reminder How to unpack an offline project", "title": "OmegaT exercises - Getting started"}, {"location": "exercises_02/#omegat-exercises-getting-started", "text": "", "title": "OmegaT exercises - Getting started"}, {"location": "exercises_02/#getting-your-project", "text": "", "title": "Getting your project"}, {"location": "exercises_02/#for-countries-not-ready-yet", "text": "Download project package project_task_fr-ZZ_offline_omt.omt . Unpack that project. Reminder How to unpack an offline project", "title": "For countries (NOT READY YET):"}, {"location": "exercises_02/alt/", "text": "06. Alternative translations \u00b6 In the previous section you saw that translations of repeated segments (or edits in those translations) auto-propagate to all instances of that repeated segment when you save them (or leave the segment). That is convenient in many cases, but not always. Sometimes you'll have to prevent auto-propagation. To do that, you must create an alternative translation . Exercise 06.1: create alternative translation \u00b6 Go to segment #5 in the project. Source text reads: Good Notice that it is translated with an auto-propagated translation. Good and Bad in segments #5 and #6 in this context refer to \"level of English\" which is masculine in French. However, your translation (\"BonNE\" and \"MauvaisE\") refers to \"situation economique\" and therefore is feminine. You want to modify the translation in segments #16 and #17 to make it masculine, so that it agrees with \"level\" in French. Follow these three simple but VERY IMPORTANT steps: Go to Edit > Create Alternative Translation . Tip: Also available if you right-click the segment. Modify the translation to make it masculine Just remove the last character if you don't know French Press Ctrl + S to register the translation Warning This is a very important and delicate function of OmegaT. It's easy to use it correctly if you grasp well the three steps above, but it's also easy to make a mess if you don't. Please make sure you really follow the three steps above to the letter. Did you follow the steps above? If you did, now you'll notice that: your alternative translation appears now in the Multiple Translations pane, below the followed the default translation and followed by the filename and the segment ID. the Segment Properties pane for that segment says now \"Is alternative: TRUE\" the (default) translation of segment #2 hasn't changed Press Enter to move to segment #6 and do the same steps as above. Info If you want more practice, go to segment #29 (source text reads: Subject: ), which is also repeated a few times. The first occurrence refers to an email subject line, whereas the other occurrences refer to the topic or subject matter field of books in a library classification system, so each of those requires a different translation, i.e. \"Objet\" vs \"Sujet\".", "title": "06. Alternative translations"}, {"location": "exercises_02/alt/#06-alternative-translations", "text": "In the previous section you saw that translations of repeated segments (or edits in those translations) auto-propagate to all instances of that repeated segment when you save them (or leave the segment). That is convenient in many cases, but not always. Sometimes you'll have to prevent auto-propagation. To do that, you must create an alternative translation .", "title": "06. Alternative translations"}, {"location": "exercises_02/alt/#exercise-061-create-alternative-translation", "text": "Go to segment #5 in the project. Source text reads: Good Notice that it is translated with an auto-propagated translation. Good and Bad in segments #5 and #6 in this context refer to \"level of English\" which is masculine in French. However, your translation (\"BonNE\" and \"MauvaisE\") refers to \"situation economique\" and therefore is feminine. You want to modify the translation in segments #16 and #17 to make it masculine, so that it agrees with \"level\" in French. Follow these three simple but VERY IMPORTANT steps: Go to Edit > Create Alternative Translation . Tip: Also available if you right-click the segment. Modify the translation to make it masculine Just remove the last character if you don't know French Press Ctrl + S to register the translation Warning This is a very important and delicate function of OmegaT. It's easy to use it correctly if you grasp well the three steps above, but it's also easy to make a mess if you don't. Please make sure you really follow the three steps above to the letter. Did you follow the steps above? If you did, now you'll notice that: your alternative translation appears now in the Multiple Translations pane, below the followed the default translation and followed by the filename and the segment ID. the Segment Properties pane for that segment says now \"Is alternative: TRUE\" the (default) translation of segment #2 hasn't changed Press Enter to move to segment #6 and do the same steps as above. Info If you want more practice, go to segment #29 (source text reads: Subject: ), which is also repeated a few times. The first occurrence refers to an email subject line, whereas the other occurrences refer to the topic or subject matter field of books in a library classification system, so each of those requires a different translation, i.e. \"Objet\" vs \"Sujet\".", "title": "Exercise 06.1: create alternative translation"}, {"location": "exercises_02/aut/", "text": "06. Special characters \u00b6 \u2190TODO Add link to the section in the guide. You may insert special characters in different ways: autotext shortcut, character table, etc. Exercise 06.1: use a known autotext shortcut \u00b6 You may use the autotext shortcut \\sub2 to insert a subscript number 2 (i.e. \u2082 ). Now you know! :) Tip The \"suB\" part in the shorcut \\sub2 stands for subindex or subscript. \u2190TODO @quiz: what do you notice in segment #47 (@todo: complete) Go to segment #47 and read the source text. Target text reads Le dioxyde de carbone (CO2) se dissout dans l'eau de mer pour former de l'acide carbonique. Delete number 2 in \u201cCO2\u201d (and keep the cursor right after \"CO\"). A subscript number should be used instead of a regular digit. In that same position, type the autotext shortcut \\sub2 Notice how the auto-completer window opens showing the autotext entry. Press Enter to insert the special character \u2082 . The result should be: CO\u2082 In this exercise you have used an autotext shortcut that you knew already. In the following exercises you'll find out an autotext entry that you don't know. Exercise 06.2: find special character in the list of autotext entries \u00b6 In this exercise, you must insert the multiplication symbol but you don't know what autotext entry you can use. Go to segment #52 Source text reads: Thermal conductivity coefficient
    (W/m \u00d7 K) Open the list of available shortcuts here . Look for the autotext entry for the multiplication symbol. You can use either \\times or \\x (how lucky, this one is shorter!) Translate segment #52 as you like (don't forget the part in parentheses). To translate the part in parenthesis, type \\x (or \\times ) between W/m and K . Notice how the auto-completer opens when you typed the autotext shortcut. Press Enter to insert the caracter. Result should be: W/m \u00d7 K Incorrect translation: W/m x K Info You can find the list of autotext entries in OmegaT guides > Miscellanea > Autotext Exercise 06.3: insert special character from the character table \u00b6 Remember the auto-completer? You used it to insert tags. You'll use it again now to insert a special character. Go to segment #49 Target text reads: \u201cLa densit\u00e9 de population est de 62 personnes par km2 en 2023.\u201d Delete number 2 in \u201ckm2\u201d (and keep your cursor right after \u201ckm\u201d). Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cCharacter table\u201d. Spot the relevant character \u00b2 and double click on it to insert it. The result should be: km\u00b2 Tip You could have inserted character \u00b2 with shortcut \\sup2 (where \"suP\" stands for superscript or superindex or superordinate).", "title": "06. Special characters"}, {"location": "exercises_02/aut/#06-special-characters", "text": "\u2190TODO Add link to the section in the guide. You may insert special characters in different ways: autotext shortcut, character table, etc.", "title": "06. Special characters"}, {"location": "exercises_02/aut/#exercise-061-use-a-known-autotext-shortcut", "text": "You may use the autotext shortcut \\sub2 to insert a subscript number 2 (i.e. \u2082 ). Now you know! :) Tip The \"suB\" part in the shorcut \\sub2 stands for subindex or subscript. \u2190TODO @quiz: what do you notice in segment #47 (@todo: complete) Go to segment #47 and read the source text. Target text reads Le dioxyde de carbone (CO2) se dissout dans l'eau de mer pour former de l'acide carbonique. Delete number 2 in \u201cCO2\u201d (and keep the cursor right after \"CO\"). A subscript number should be used instead of a regular digit. In that same position, type the autotext shortcut \\sub2 Notice how the auto-completer window opens showing the autotext entry. Press Enter to insert the special character \u2082 . The result should be: CO\u2082 In this exercise you have used an autotext shortcut that you knew already. In the following exercises you'll find out an autotext entry that you don't know.", "title": "Exercise 06.1: use a known autotext shortcut"}, {"location": "exercises_02/aut/#exercise-062-find-special-character-in-the-list-of-autotext-entries", "text": "In this exercise, you must insert the multiplication symbol but you don't know what autotext entry you can use. Go to segment #52 Source text reads: Thermal conductivity coefficient
    (W/m \u00d7 K) Open the list of available shortcuts here . Look for the autotext entry for the multiplication symbol. You can use either \\times or \\x (how lucky, this one is shorter!) Translate segment #52 as you like (don't forget the part in parentheses). To translate the part in parenthesis, type \\x (or \\times ) between W/m and K . Notice how the auto-completer opens when you typed the autotext shortcut. Press Enter to insert the caracter. Result should be: W/m \u00d7 K Incorrect translation: W/m x K Info You can find the list of autotext entries in OmegaT guides > Miscellanea > Autotext", "title": "Exercise 06.2: find special character in the list of autotext entries"}, {"location": "exercises_02/aut/#exercise-063-insert-special-character-from-the-character-table", "text": "Remember the auto-completer? You used it to insert tags. You'll use it again now to insert a special character. Go to segment #49 Target text reads: \u201cLa densit\u00e9 de population est de 62 personnes par km2 en 2023.\u201d Delete number 2 in \u201ckm2\u201d (and keep your cursor right after \u201ckm\u201d). Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cCharacter table\u201d. Spot the relevant character \u00b2 and double click on it to insert it. The result should be: km\u00b2 Tip You could have inserted character \u00b2 with shortcut \\sup2 (where \"suP\" stands for superscript or superindex or superordinate).", "title": "Exercise 06.3: insert special character from the character table"}, {"location": "exercises_02/fnd/", "text": "07. Search: AM \u00b6 @\u0167odo: review Using the search function, try to find the following segments in the project: Notice that here is one instance of the repeated segment \"Rather unsatisfied\" that was not translated consistenly. @quiz: can you find it? Find the segment with \"How\" in a note. Try to find the translation of \"translator\" in the translation memories. Find \"Subject\", but only if it has a translation.", "title": "07. Search: AM"}, {"location": "exercises_02/fnd/#07-search-am", "text": "@\u0167odo: review Using the search function, try to find the following segments in the project: Notice that here is one instance of the repeated segment \"Rather unsatisfied\" that was not translated consistenly. @quiz: can you find it? Find the segment with \"How\" in a note. Try to find the translation of \"translator\" in the translation memories. Find \"Subject\", but only if it has a translation.", "title": "07. Search: AM"}, {"location": "exercises_02/mat/", "text": "02. Matches @WIP \u00b6 @todo: check whether tags + matches or matches + tags @todo: update numbers or remove them Exercise 02.1: translate from scratch \u00b6 Translate segment #1. Suggested translation: Bienvenue \u00e0 cette enqu\u00e8te. Press Ctrl + U to go to segment #2. Exercise 02.2: insert match and update it \u00b6 You're in segment #2. Notice that there's a fuzzy match you can use. Press Ctrl + I to insert it. Looking at the Matches pane, notice that there's a difference between the new source text and the source text in the match. Update the inserted translation so that it corresponds to the source text you're translating. Tip: Replace financiere with \u00e9conomique . Press Ctrl + U to go to segment #3. Exercise 02.3: insert exact match \u00b6 You're in segment #3. Notice that there's an exact match which you can use as is. Press Ctrl + I to insert it. There's nothing else to do this time :) Press Ctrl + U to go to segment #4. Exercise 02.4: insert match and update it \u00b6 You're in segment #4. Your previous translation is now a 50% match that you could use. Press Ctrl + I to insert the 50% match. Now update the translation so that it corresponds to the source text. Tip: delete bon , type mauvaise Expected result: Plut\u00f4t mauvaise Exercise 02.5: pretranslated and editable \u00b6 You're still in segment #4. Notice how segment #5 is pretranslated. Notice that it has a pink background. That means that it is editable, if necessary. Press Ctrl + U to go to segment #8. Exercise 02.6: almost identical match \u00b6 You're in segment #8. Source text reads Welcome to this survey! Notice how this segment is almost identical to the first segment you translated. The only difference is in the final punctuation. Press Ctrl + I to insert the match. Update the translation now. Replace final dot . with exclamation mark ! Exercise 02.7: pretranslated and locked \u00b6 You're still in segment #8. Notice how segments #9, #11 and a few others are pretranslated. Notice that they have an orange background. That means they are enforced translations, in other words: not editable. Modify the translation (just add a few characters) Press F5 to reload the project. Notice how your edits are now gone. Exercise 02.8: select match \u00b6 Press Ctrl + J and enter number 15 to go to segment #15. Notice that this segment is pretranslated. Go to segment #16. Source text reads Good Notice how the Matches pane presents two matches you could use. Press Ctrl + 2 to select the second match (match #2). Press Ctrl + I to insert the selected match (match #2). Delete plut\u00f4t and change the case. Expected result: Bon Note In this case both matches required the same amount of work to update them. The only reason why you have to select and insert match #2 is to make you practice ;) Exercise 02.9: insert selection \u00b6 Press Ctrl + U to go to segment #17. Select \"mauvaise\" in the fuzzy match Now press Ctrl + I to insert the selected text Update the match. Change case of m to M Expected result: Mauvais \u00e7 Exercise 02.10: \u00b6 Press Ctrl + U to go to segment #18. Press Ctrl + 2 , then press Ctrl + 3 , as many times as you want. Notice how match #2 and match #3 get seleted when you press the shortcuts above. Select one and insert it, then updated it. Here you're free to update the fuzzy match as you like. Expected resul: Tr\u00e8s mauvais Recap To recap, the available options are: Write Tr\u00e8s , then select mauvaise in match #2 and press Ctrl + I Press Ctrl + 2 , then Ctrl + I to insert match #2, then replace PLut\u00f4t with Tr\u00e8s Press Ctrl + 3 , then Ctrl + I to insert Mauvaise , then update it, then add Tr\u00e8s at the beginning Write Tr\u00e8s , then press Ctrl + 3 , then Ctrl + I to insert match #3, then update it. They are all valid approaches, any is fine as long as the result is correct.", "title": "02. Matches @WIP"}, {"location": "exercises_02/mat/#02-matches-wip", "text": "@todo: check whether tags + matches or matches + tags @todo: update numbers or remove them", "title": "02. Matches @WIP"}, {"location": "exercises_02/mat/#exercise-021-translate-from-scratch", "text": "Translate segment #1. Suggested translation: Bienvenue \u00e0 cette enqu\u00e8te. Press Ctrl + U to go to segment #2.", "title": "Exercise 02.1: translate from scratch"}, {"location": "exercises_02/mat/#exercise-022-insert-match-and-update-it", "text": "You're in segment #2. Notice that there's a fuzzy match you can use. Press Ctrl + I to insert it. Looking at the Matches pane, notice that there's a difference between the new source text and the source text in the match. Update the inserted translation so that it corresponds to the source text you're translating. Tip: Replace financiere with \u00e9conomique . Press Ctrl + U to go to segment #3.", "title": "Exercise 02.2: insert match and update it"}, {"location": "exercises_02/mat/#exercise-023-insert-exact-match", "text": "You're in segment #3. Notice that there's an exact match which you can use as is. Press Ctrl + I to insert it. There's nothing else to do this time :) Press Ctrl + U to go to segment #4.", "title": "Exercise 02.3: insert exact match"}, {"location": "exercises_02/mat/#exercise-024-insert-match-and-update-it", "text": "You're in segment #4. Your previous translation is now a 50% match that you could use. Press Ctrl + I to insert the 50% match. Now update the translation so that it corresponds to the source text. Tip: delete bon , type mauvaise Expected result: Plut\u00f4t mauvaise", "title": "Exercise 02.4: insert match and update it"}, {"location": "exercises_02/mat/#exercise-025-pretranslated-and-editable", "text": "You're still in segment #4. Notice how segment #5 is pretranslated. Notice that it has a pink background. That means that it is editable, if necessary. Press Ctrl + U to go to segment #8.", "title": "Exercise 02.5: pretranslated and editable"}, {"location": "exercises_02/mat/#exercise-026-almost-identical-match", "text": "You're in segment #8. Source text reads Welcome to this survey! Notice how this segment is almost identical to the first segment you translated. The only difference is in the final punctuation. Press Ctrl + I to insert the match. Update the translation now. Replace final dot . with exclamation mark !", "title": "Exercise 02.6: almost identical match"}, {"location": "exercises_02/mat/#exercise-027-pretranslated-and-locked", "text": "You're still in segment #8. Notice how segments #9, #11 and a few others are pretranslated. Notice that they have an orange background. That means they are enforced translations, in other words: not editable. Modify the translation (just add a few characters) Press F5 to reload the project. Notice how your edits are now gone.", "title": "Exercise 02.7: pretranslated and locked"}, {"location": "exercises_02/mat/#exercise-028-select-match", "text": "Press Ctrl + J and enter number 15 to go to segment #15. Notice that this segment is pretranslated. Go to segment #16. Source text reads Good Notice how the Matches pane presents two matches you could use. Press Ctrl + 2 to select the second match (match #2). Press Ctrl + I to insert the selected match (match #2). Delete plut\u00f4t and change the case. Expected result: Bon Note In this case both matches required the same amount of work to update them. The only reason why you have to select and insert match #2 is to make you practice ;)", "title": "Exercise 02.8: select match"}, {"location": "exercises_02/mat/#exercise-029-insert-selection", "text": "Press Ctrl + U to go to segment #17. Select \"mauvaise\" in the fuzzy match Now press Ctrl + I to insert the selected text Update the match. Change case of m to M Expected result: Mauvais \u00e7", "title": "Exercise 02.9: insert selection"}, {"location": "exercises_02/mat/#exercise-0210", "text": "Press Ctrl + U to go to segment #18. Press Ctrl + 2 , then press Ctrl + 3 , as many times as you want. Notice how match #2 and match #3 get seleted when you press the shortcuts above. Select one and insert it, then updated it. Here you're free to update the fuzzy match as you like. Expected resul: Tr\u00e8s mauvais Recap To recap, the available options are: Write Tr\u00e8s , then select mauvaise in match #2 and press Ctrl + I Press Ctrl + 2 , then Ctrl + I to insert match #2, then replace PLut\u00f4t with Tr\u00e8s Press Ctrl + 3 , then Ctrl + I to insert Mauvaise , then update it, then add Tr\u00e8s at the beginning Write Tr\u00e8s , then press Ctrl + 3 , then Ctrl + I to insert match #3, then update it. They are all valid approaches, any is fine as long as the result is correct.", "title": "Exercise 02.10:"}, {"location": "exercises_02/nav/", "text": "01. Navigation \u00b6 Exercise 01.1 \u00b6 Press Ctrl + J and enter 1 to go to segment #1. Source text reads Welcome to this survey. Press Enter to move to the next segment. You are now in segment #2. Press Ctrl + U to move to the next untranslated segment. You are now in segment #3. Press Enter three times in a row to go forward 3 segments. You end up in segment #6. Press Ctrl + Enter twice in a row to go backwards 2 segments. You are now in segment #4. Press Ctrl + U once to go to the next untranslated segment. You end up in segment #6 again. Notice that you have jumped segment #5, which is already translated (in pink). Tip when you tranlsate: ctrl+u when you review: enter Exercise 01.2 \u00b6 Press Ctrl + J and enter number 53 to go to segment #53. Source text reads: Generally speaking, please tell me how satisfied you are with public transport where you live . Press Ctrl + U to jump to the next untranslated segment. You are now on segment #58. Press Enter to move the next segment. You are now on segment #59. Oops, you haven't translated segment #58. Press Ctrl + Enter to go back to it. You are now on segment #58 again. Scroll down until you see another untranslated segment in that file. Source text reads: Generally speaking, please tell me how satisfied you are with schools and other educational facilities where you live. Double click on that segment. You are now on segment #63. Press keyboard shortcut Ctrl + J and enter number 1 to go to segment number #1. Recap In this exercise you have practiced several ways to activate a segment: Enter opens the next segment Ctrl + Enter opens the previous segment Ctrl + U opens the next untranslated segment Ctrl + J (plus the segment numberj) opens a specific segment \u2190TODO Check segment numbers after no more changes.", "title": "01. Navigation"}, {"location": "exercises_02/nav/#01-navigation", "text": "", "title": "01. Navigation"}, {"location": "exercises_02/nav/#exercise-011", "text": "Press Ctrl + J and enter 1 to go to segment #1. Source text reads Welcome to this survey. Press Enter to move to the next segment. You are now in segment #2. Press Ctrl + U to move to the next untranslated segment. You are now in segment #3. Press Enter three times in a row to go forward 3 segments. You end up in segment #6. Press Ctrl + Enter twice in a row to go backwards 2 segments. You are now in segment #4. Press Ctrl + U once to go to the next untranslated segment. You end up in segment #6 again. Notice that you have jumped segment #5, which is already translated (in pink). Tip when you tranlsate: ctrl+u when you review: enter", "title": "Exercise 01.1"}, {"location": "exercises_02/nav/#exercise-012", "text": "Press Ctrl + J and enter number 53 to go to segment #53. Source text reads: Generally speaking, please tell me how satisfied you are with public transport where you live . Press Ctrl + U to jump to the next untranslated segment. You are now on segment #58. Press Enter to move the next segment. You are now on segment #59. Oops, you haven't translated segment #58. Press Ctrl + Enter to go back to it. You are now on segment #58 again. Scroll down until you see another untranslated segment in that file. Source text reads: Generally speaking, please tell me how satisfied you are with schools and other educational facilities where you live. Double click on that segment. You are now on segment #63. Press keyboard shortcut Ctrl + J and enter number 1 to go to segment number #1. Recap In this exercise you have practiced several ways to activate a segment: Enter opens the next segment Ctrl + Enter opens the previous segment Ctrl + U opens the next untranslated segment Ctrl + J (plus the segment numberj) opens a specific segment \u2190TODO Check segment numbers after no more changes.", "title": "Exercise 01.2"}, {"location": "exercises_02/qac/", "text": "08. QA checks \u00b6 @todo: review There are two segments with tag errors, can you find them? On which segment is there a glossary error?", "title": "08. QA checks"}, {"location": "exercises_02/qac/#08-qa-checks", "text": "@todo: review There are two segments with tag errors, can you find them? On which segment is there a glossary error?", "title": "08. QA checks"}, {"location": "exercises_02/rec/", "text": "03. Reconciliation \u00b6 This section includes some bonus exercises specifically addressed to reconcilers. You may skip this section if you're not going to reconcile. Getting started \u00b6 Here's a UI preference that may be useful for you when you reconcile. In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 100 With that setting, the Matches pane will show you only the translations you need to reconcile. Please remember to restore the default value when you're not reconciling. Exercise 04.01: inserting one match \u00b6 Go to segment #62 and read it. Here comes a story for you. Source text reads Once upon a time there was a reconciler who worked in OmegaT. You have one exact match. Press Ctrl + I to insert it. Easy start. Now press Ctrl + U to move to the next unreconciled segment. Read segment #63. You have one exact match. Press Ctrl + I to translate the segment with that match. Still easy. Press Ctrl + U to move to the next unreconciled segment. Info You only see one match if \"translation 1\" and \"translation 2\" are identical. Exercise 04.02: selecting the match \u00b6 You're now on segment #64. Read segment #64. Notice that now you can see two matches because \"translation 1\" and \"translation 2\" are different now. You want to use the first translation (selected by default). Press Ctrl + I to insert match #1. Translation reads Parfois, l'une des deux traductions \u00e9tait bonne, et l'autre \u00e9tait mauvaise, donc le choix \u00e9tait clair. Press Ctrl + U to move to the next unreconciled segment. You're now on segment #65. 11. Read segment #65. 11. Here you want to use the second translation. Press Ctrl + 2 to select match #2. 12. Press Ctrl + I to insert it. Translation reads D'autres fois, la premi\u00e8re traduction \u00e9tait mauvaise, mais la seconde \u00e9tait bonne, donc le choix \u00e9tait \u00e9galement clair. Press Ctrl + U to move to the next unreconciled segment. Exersise 04.03: editing the inserted translation \u00b6 You're now on segment #66. Read segment #66. Press Ctrl + I to insert the exiting match. Edit the translation to make it a good translation. Tip: Remove the excessive SSs in parfoisSSs . Press Ctrl + U to move to the next unreconciled segment. Exercise 04.03: assembling fragments \u00b6 You are in segment #67. In match #1, select Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, Press Ctrl + I to insert the text you have selected. In match #2, select , mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. Press Ctrl + I to insert the text you have selected now. Expected result: Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. You have combined two parts of two translations to create one single reconciled version. Congrats! Finally \u00b6 Please remember to restore the default threshold to show matches: In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 50.", "title": "03. Reconciliation"}, {"location": "exercises_02/rec/#03-reconciliation", "text": "This section includes some bonus exercises specifically addressed to reconcilers. You may skip this section if you're not going to reconcile.", "title": "03. Reconciliation"}, {"location": "exercises_02/rec/#getting-started", "text": "Here's a UI preference that may be useful for you when you reconcile. In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 100 With that setting, the Matches pane will show you only the translations you need to reconcile. Please remember to restore the default value when you're not reconciling.", "title": "Getting started"}, {"location": "exercises_02/rec/#exercise-0401-inserting-one-match", "text": "Go to segment #62 and read it. Here comes a story for you. Source text reads Once upon a time there was a reconciler who worked in OmegaT. You have one exact match. Press Ctrl + I to insert it. Easy start. Now press Ctrl + U to move to the next unreconciled segment. Read segment #63. You have one exact match. Press Ctrl + I to translate the segment with that match. Still easy. Press Ctrl + U to move to the next unreconciled segment. Info You only see one match if \"translation 1\" and \"translation 2\" are identical.", "title": "Exercise 04.01: inserting one match"}, {"location": "exercises_02/rec/#exercise-0402-selecting-the-match", "text": "You're now on segment #64. Read segment #64. Notice that now you can see two matches because \"translation 1\" and \"translation 2\" are different now. You want to use the first translation (selected by default). Press Ctrl + I to insert match #1. Translation reads Parfois, l'une des deux traductions \u00e9tait bonne, et l'autre \u00e9tait mauvaise, donc le choix \u00e9tait clair. Press Ctrl + U to move to the next unreconciled segment. You're now on segment #65. 11. Read segment #65. 11. Here you want to use the second translation. Press Ctrl + 2 to select match #2. 12. Press Ctrl + I to insert it. Translation reads D'autres fois, la premi\u00e8re traduction \u00e9tait mauvaise, mais la seconde \u00e9tait bonne, donc le choix \u00e9tait \u00e9galement clair. Press Ctrl + U to move to the next unreconciled segment.", "title": "Exercise 04.02: selecting the match"}, {"location": "exercises_02/rec/#exersise-0403-editing-the-inserted-translation", "text": "You're now on segment #66. Read segment #66. Press Ctrl + I to insert the exiting match. Edit the translation to make it a good translation. Tip: Remove the excessive SSs in parfoisSSs . Press Ctrl + U to move to the next unreconciled segment.", "title": "Exersise 04.03: editing the inserted translation"}, {"location": "exercises_02/rec/#exercise-0403-assembling-fragments", "text": "You are in segment #67. In match #1, select Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, Press Ctrl + I to insert the text you have selected. In match #2, select , mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. Press Ctrl + I to insert the text you have selected now. Expected result: Et encore d'autres fois, la premi\u00e8re traduction avait une partie qui \u00e9tait bonne, mais l'autre partie \u00e9tait meilleure dans la deuxi\u00e8me traduction, ou vice versa, donc il fallait les combiner les combiner. You have combined two parts of two translations to create one single reconciled version. Congrats!", "title": "Exercise 04.03: assembling fragments"}, {"location": "exercises_02/rec/#finally", "text": "Please remember to restore the default threshold to show matches: In OmegaT, go to Options > Preferences > TM Matches . Change value of setting \"Minimal threshold to show a fuzzy match\" to 50.", "title": "Finally"}, {"location": "exercises_02/rep/", "text": "05 Repetitions \u00b6 Exercise 05.1: notice repeated segments \u00b6 Go to segment #3. Source text reads: Pretty good \u2190TODO @quiz: how many reps in total? Notice how the segment marker says that this segment is repeated three more times: . Look at the Segment Properties pane. It says \"Is duplicate: FIRST\" Right click on the segment. See how all the instances are listed and identified by their segment number. Select Segment 6 on the list to go to segment #6. Look at the Segment Properties pane for segment #6. It says \"Is duplicate: NEXT\" \u2190TODO @quiz: some question about FIRST and NEXT (feedback welcome) Right click on segment #6 to see instances listed again, go back to segment #3 again. Exercise 05.2: auto-propagate translations \u00b6 Translate segment #2. Suggested translation: \"BonNE\" -NE ending: feminine suffix, because \"Good\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #2 to go to segment #3. Notice how the translation is auto-propagated to segment #5. Translate segment #3. Suggested translation: \"MauvaisE\" -E ending: feminine suffix, because \"Bad\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #3 to confirm the translation of segment #3 and go to the next segment. Notice how the translation is auto-propagated to segment #6. Exercise 05.3: auto-propagate edits in translations \u00b6 Go to segment #5 in the project. You can see that it is translated with your auto-propagated translation. Modify the translation in segment #5 and press Ctrl + S to save the translation. Notice how the translation of segment #2 also changes. Tip Shortcut Ctrl + S saves the translation. You can also save in Project > Save , but it takes longer ;)", "title": "05 Repetitions"}, {"location": "exercises_02/rep/#05-repetitions", "text": "", "title": "05 Repetitions"}, {"location": "exercises_02/rep/#exercise-051-notice-repeated-segments", "text": "Go to segment #3. Source text reads: Pretty good \u2190TODO @quiz: how many reps in total? Notice how the segment marker says that this segment is repeated three more times: . Look at the Segment Properties pane. It says \"Is duplicate: FIRST\" Right click on the segment. See how all the instances are listed and identified by their segment number. Select Segment 6 on the list to go to segment #6. Look at the Segment Properties pane for segment #6. It says \"Is duplicate: NEXT\" \u2190TODO @quiz: some question about FIRST and NEXT (feedback welcome) Right click on segment #6 to see instances listed again, go back to segment #3 again.", "title": "Exercise 05.1: notice repeated segments"}, {"location": "exercises_02/rep/#exercise-052-auto-propagate-translations", "text": "Translate segment #2. Suggested translation: \"BonNE\" -NE ending: feminine suffix, because \"Good\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #2 to go to segment #3. Notice how the translation is auto-propagated to segment #5. Translate segment #3. Suggested translation: \"MauvaisE\" -E ending: feminine suffix, because \"Bad\" here refers to \"economic situation\", which is feminine in French Press Enter after translating segment #3 to confirm the translation of segment #3 and go to the next segment. Notice how the translation is auto-propagated to segment #6.", "title": "Exercise 05.2: auto-propagate translations"}, {"location": "exercises_02/rep/#exercise-053-auto-propagate-edits-in-translations", "text": "Go to segment #5 in the project. You can see that it is translated with your auto-propagated translation. Modify the translation in segment #5 and press Ctrl + S to save the translation. Notice how the translation of segment #2 also changes. Tip Shortcut Ctrl + S saves the translation. You can also save in Project > Save , but it takes longer ;)", "title": "Exercise 05.3: auto-propagate edits in translations"}, {"location": "exercises_02/tag/", "text": "04. Tags \u00b6 Reminder Section in the guides about Tags . Exercise 04.1: insert tags \u00b6 Go to segment #10, which is untranslated. Source text reads: There are no right answers. Notice the two tags in the segment. @quiz: what do you think these are? How to we handle them: should we ignore them or reproduce them in the translation? @todo: move to quiz or remove Translate segment #10. Suggested translation: Il n\u2019y a pas de bonne r\u00e9ponse. Select the part of the translation that corresponds to \"right\" Tip: you should select bonne Press Ctrl + Space to open the auto-completer. Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cMissing tags\u201d section. The first option (i.e. | ) is selected by default. Press Enter to insert tag pair. Notice how the two paired tags are inserted around the selected text in the translation. Expected result: Il n\u2019y a pas de bonne r\u00e9ponse. Well done! Exercise 04.2: trigger the tag tooltip \u00b6 Press Ctrl + J and enter 55 to go to segment #55. Source text reads: The translator had to pay attention to formatting such as bold, italics, underline. Hover over the tags with your mouse to display a tooltip that shows the line code the tags stand for. Tip: the tooltip should display HTML tags , , etc. Exercise 04.3: see what standalone tags stand for \u00b6 Press Ctrl + J and enter 75 to go to segment #75. Source text reads if sensor detects black Notice how the segment contains one standalone tag. Hover over the tag to see what the tag stands for. The tooltip should show {{ sensor_type }} Go to the next segment, #76 Notice how this segment has two standalone tags, not two paired tags! Check what the two tags stand for. The tooltips should show {{ object1 }} and {{ object2 }} Warning The difference between two standalone tags and two paired tags is very important. Exercise 04.4: insert standalone tags \u00b6 Go to segment #77. Notice that the tag is missing in the translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: right at the end of the translation Press Ctrl + Space to launch the auto-completer and insert the tag. Go to segment #78. Notice how the tag is also missing in this translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: click between tourner \u00e0 droite jusqu'\u00e0 ce que and le capteur d\u00e9tecte le noir Use the auto-completer to insert the missing tag. Exercise 04.5: insert standalone tag as you translate \u00b6 Go to segment #79. To translate the segment and insert the tag, proceed in this way: Translate \"repeat\" Suggested translation of the first part: r\u00e9p\u00e9ter Use the auto-completer to insert the missing tag Remember the shortcut to launche the auto-completer is Ctrl + Space Translate \"times\" Suggested translation of the second part: fois You have inserted the tag as you made progress through the translation. Exercise 04.6: insert more tags \u00b6 Still in segment #39, notice how most tags are missing in the translation. Select the part of the translation that corresponds to \u201cbold\u201d Tip: le gras Press Ctrl + Space to open the \"Missing tags\" section in the auto-completer. The first line (i.e. ) is selected by default. Press Enter to insert that tag pair. Notice how the tags have been inserted around the selected text Results should be le gras Do the same for the translation of \u201citalics\u201d Tip: l\u2019italique Do the same for the translation of \u201cunderline\u201d Tip: le soulignement", "title": "04. Tags"}, {"location": "exercises_02/tag/#04-tags", "text": "Reminder Section in the guides about Tags .", "title": "04. Tags"}, {"location": "exercises_02/tag/#exercise-041-insert-tags", "text": "Go to segment #10, which is untranslated. Source text reads: There are no right answers. Notice the two tags in the segment. @quiz: what do you think these are? How to we handle them: should we ignore them or reproduce them in the translation? @todo: move to quiz or remove Translate segment #10. Suggested translation: Il n\u2019y a pas de bonne r\u00e9ponse. Select the part of the translation that corresponds to \"right\" Tip: you should select bonne Press Ctrl + Space to open the auto-completer. Press Ctrl + Space several times to cycle through all the sections in the auto-completer. Stop when you reach the \u201cMissing tags\u201d section. The first option (i.e. | ) is selected by default. Press Enter to insert tag pair. Notice how the two paired tags are inserted around the selected text in the translation. Expected result: Il n\u2019y a pas de bonne r\u00e9ponse. Well done!", "title": "Exercise 04.1: insert tags"}, {"location": "exercises_02/tag/#exercise-042-trigger-the-tag-tooltip", "text": "Press Ctrl + J and enter 55 to go to segment #55. Source text reads: The translator had to pay attention to formatting such as bold, italics, underline. Hover over the tags with your mouse to display a tooltip that shows the line code the tags stand for. Tip: the tooltip should display HTML tags , , etc.", "title": "Exercise 04.2: trigger the tag tooltip"}, {"location": "exercises_02/tag/#exercise-043-see-what-standalone-tags-stand-for", "text": "Press Ctrl + J and enter 75 to go to segment #75. Source text reads if sensor detects black Notice how the segment contains one standalone tag. Hover over the tag to see what the tag stands for. The tooltip should show {{ sensor_type }} Go to the next segment, #76 Notice how this segment has two standalone tags, not two paired tags! Check what the two tags stand for. The tooltips should show {{ object1 }} and {{ object2 }} Warning The difference between two standalone tags and two paired tags is very important.", "title": "Exercise 04.3: see what standalone tags stand for"}, {"location": "exercises_02/tag/#exercise-044-insert-standalone-tags", "text": "Go to segment #77. Notice that the tag is missing in the translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: right at the end of the translation Press Ctrl + Space to launch the auto-completer and insert the tag. Go to segment #78. Notice how the tag is also missing in this translation. Place the mouse cursor in the position where you would like to insert the tag. Tip: click between tourner \u00e0 droite jusqu'\u00e0 ce que and le capteur d\u00e9tecte le noir Use the auto-completer to insert the missing tag.", "title": "Exercise 04.4: insert standalone tags"}, {"location": "exercises_02/tag/#exercise-045-insert-standalone-tag-as-you-translate", "text": "Go to segment #79. To translate the segment and insert the tag, proceed in this way: Translate \"repeat\" Suggested translation of the first part: r\u00e9p\u00e9ter Use the auto-completer to insert the missing tag Remember the shortcut to launche the auto-completer is Ctrl + Space Translate \"times\" Suggested translation of the second part: fois You have inserted the tag as you made progress through the translation.", "title": "Exercise 04.5: insert standalone tag as you translate"}, {"location": "exercises_02/tag/#exercise-046-insert-more-tags", "text": "Still in segment #39, notice how most tags are missing in the translation. Select the part of the translation that corresponds to \u201cbold\u201d Tip: le gras Press Ctrl + Space to open the \"Missing tags\" section in the auto-completer. The first line (i.e. ) is selected by default. Press Enter to insert that tag pair. Notice how the tags have been inserted around the selected text Results should be le gras Do the same for the translation of \u201citalics\u201d Tip: l\u2019italique Do the same for the translation of \u201cunderline\u201d Tip: le soulignement", "title": "Exercise 04.6: insert more tags"}, {"location": "exercises_02/tgt/", "text": "09. Download git project + commit target files + helpdesk \u00b6 NOTE FOR HELPERS This is a draft. Go to the C: drive in your computer and create a new folder called Work (or something else if you really dislike \"Work\" as a folder name). | If you don't have permissions to create a folder under C: , you can use another location such as C:\\Users\\USER\\ The path to this folder will be C:\\Work . This is where you will create your project. Copy this URL to your clipboard (select it and press Ctrl+C): https://github.com/capstanlqc-pisa/PISA_2025_fr-ZZ_Verification_OMT.git Open OmegaT, click on the Project menu, select \"Download Team Project\". Click inside the Repository URL field and press Ctrl+V to paste the URL you have copied. Click inside the New Local Project Folder field. OmegaT will propose a default path for you, if that path is not suitable you can edit it to have the project created in your preferred location Note We advise you to use an easy path to remember, such as a folder in your Documents folder Press OK, the project will be loaded after a few seconds.", "title": "09. Download git project + commit target files + helpdesk"}, {"location": "exercises_02/tgt/#09-download-git-project-commit-target-files-helpdesk", "text": "NOTE FOR HELPERS This is a draft. Go to the C: drive in your computer and create a new folder called Work (or something else if you really dislike \"Work\" as a folder name). | If you don't have permissions to create a folder under C: , you can use another location such as C:\\Users\\USER\\ The path to this folder will be C:\\Work . This is where you will create your project. Copy this URL to your clipboard (select it and press Ctrl+C): https://github.com/capstanlqc-pisa/PISA_2025_fr-ZZ_Verification_OMT.git Open OmegaT, click on the Project menu, select \"Download Team Project\". Click inside the Repository URL field and press Ctrl+V to paste the URL you have copied. Click inside the New Local Project Folder field. OmegaT will propose a default path for you, if that path is not suitable you can edit it to have the project created in your preferred location Note We advise you to use an easy path to remember, such as a folder in your Documents folder Press OK, the project will be loaded after a few seconds.", "title": "09. Download git project + commit target files + helpdesk"}, {"location": "misc/", "text": "Miscellanea \u00b6 This section contains some guides that are not specific for any role or task in particular, but that might be useful or interesting for anyone. Some guides are addressed only to people with specific responsibiilities: Bidirectionality (RTL) for RTL languages IT security for IT departments Autotext entries for productivity users", "title": "Miscellanea"}, {"location": "misc/#miscellanea", "text": "This section contains some guides that are not specific for any role or task in particular, but that might be useful or interesting for anyone. Some guides are addressed only to people with specific responsibiilities: Bidirectionality (RTL) for RTL languages IT security for IT departments Autotext entries for productivity users", "title": "Miscellanea"}, {"location": "misc/about/", "text": "About \u00b6 OmegaT \u00b6 team cApStAn \u00b6 bar cApStAn tech team \u00b6 baz", "title": "About"}, {"location": "misc/about/#about", "text": "", "title": "About"}, {"location": "misc/about/#omegat", "text": "team", "title": "OmegaT"}, {"location": "misc/about/#capstan", "text": "bar", "title": "cApStAn"}, {"location": "misc/about/#capstan-tech-team", "text": "baz", "title": "cApStAn tech team"}, {"location": "misc/autotext/", "text": "OmegaT autotext entries \u00b6 The Auto-Completer allows to insert a special character by typing a shortcut. The table below shows the list of shortcuts available in OmegaT. Shorcut Character Description \\lq \u201c upper left double quotation mark (U+201C) \\rq \u201d upper right double quotation mark (U+201D) \\lolq \u201e lower left (low-9) double quotation mark (U+201E) << \u00ab left-pointing double angle quotation mark (U+00AB) >> \u00bb right-pointing duoble angle quotation mark (U+00BB) \\laquo \u00ab left-pointing double angle quotation mark (U+00AB) \\raquo \u00bb right-pointing duoble angle quotation mark (U+00BB) \\rsquo \u2019 right single quotation mark (U+2019) \\apos \u2019 right single quotation mark (U+2019) \\lsquo \u2018 left single quotation mark (U+2018) \\x \u00d7 multiplication symbol / vector product \\times \u00d7 multiplication symbol \\nbsp non-breaking space \\tm \u2122 trademark symbol \\reg \u00ae registered (U+00AE) (tm) \u2122 trademark symbol \\sup0 \u2070 superscript 0 (U+2070) \\sup1 \u00b9 superscript 1 (U+00B9) \\sup2 \u00b2 superscript 2 (U+00B2) \\sup3 \u00b3 superscript 3 (U+00B3) \\sup4 \u2074 superscript 4 (U+2074) \\sup5 \u2075 superscript 5 (U+2075) \\sup6 \u2076 superscript 6 (U+2076) \\sup7 \u2077 superscript 7 (U+2077) \\sup8 \u2078 superscript 8 (U+2078) \\sup9 \u2079 superscript 9 (U+2079) \\supi \u2071 superscript i (U+2071) \\supn \u207f superscript n (U+207F) \\sup( \u207d superscript left parenthesis (U+207D) \\sup) \u207e superscript right parenthesis (U+207E) \\lrm \u200e LRM (U+200E) \\rlm \u200f RLM (U+200F) \\minus \u2013 n-dash (U+2013) \\ndash \u2013 n-dash (U+2013) \\mdash \u2014 m-dash (U+2014) \\pi \u03c0 mathematical pi letter \\thinspace \u2009 thin space \\ellipsis \u2026 horizontal ellipsis \\divided \u00f7 division \\middot \u00b7 interpunct/interpoint/middle dot/middot/centered dot (multiplication / scalar product) \\interpunct \u00b7 interpunct/interpoint/middle dot/middot/centered dot (multiplication / scalar product) \\bullet \u2219 bullet operator (U+2219) \\pm \u00b1 plus or minus \\le \u2264 less than or equal to \\ge \u2265 greater than or equal to \\ne \u2260 does not equal \\approx \u2248 approximately equal to \\emptyset \u2205 empty set \\sqrt \u221a square root (U+221A) \\deg \u00b0 degree \\infty \u221e infinity \\copyright \u00a9 copyright symbol \\smalle \u1d49 modifier letter small e (U+1D49) \\Omegat \u03a9 Greek capital letter omega / Ohm \\pound \u00a3 pound currency \\euro \u20ac euro currency \\cent \u00a2 cent (U+00A2) \\yen \u00a5 yen (U+00A5) \\ordf \u00aa feminine ordinal indicator (U+00AA) \\ordm \u00ba masculine ordinal indicator (U+00BA) \\shy \u00ad soft hyphen (U+00AD) \\micro \u00b5 micro (U+00B5) \\not \u00ac not sign (U+00AC) \\frac12 \u00bd vulgar fraction 1/2 / half \\frac13 \u2153 vulgar fraction 1/3 / third \\frac23 \u2154 vulgar fraction 2/3 \\frac14 \u00bc vulgar fraction 1/4 / quarter \\frac34 \u00be vulgar fraction 3/4 \\frac15 \u2155 vulgar fraction 1/5 / fifth \\frac25 \u2156 vulgar fraction 2/5 \\frac35 \u2157 vulgar fraction 3/5 \\frac45 \u2158 vulgar fraction 4/5 \\frac16 \u2159 vulgar fraction 1/6 \\frac56 \u215a vulgar fraction 5/6 \\frac17 \u2150 vulgar fraction 1/7 \\frac18 \u215b vulgar fraction 1/8 \\frac38 \u215c vulgar fraction 3/8 \\frac58 \u215d vulgar fraction 5/8 \\frac78 \u215e vulgar fraction 7/8 \\frac19 \u2151 vulgar fraction 1/9 \\frac110 \u2152 vulgar fraction 1/10 \\fracslash \u2044 fraction slash (E+2044\u209b) \\9 \u0669 nan \\8 \u0668 nan \\7 \u0667 nan \\6 \u0666 nan \\5 \u0665 nan \\4 \u0664 nan \\3 \u0663 nan \\2 \u0662 nan \\1 \u0661 nan \\0 \u0660 nan \\ar_percent \u2052 commercial minus sign (U+2052) \\nbhy \u2011 non-breaking hyphen \\ordrd \u02b3\u1d48 rd ordinal superscript \\ordnd \u207f\u1d48 nd ordinal superscript \\ordst \u02e2\u1d57 st ordinal superscript \\ordth \u1d57\u02b0 th ordinal superscript \\mathx \ud835\udc65 Mathematical italic small x \\orde \u1d49 superscript small e (for ordinals in French) \\supe \u1d49 superscript small e (for ordinals in French) \\ordde \u1d48\u1d49 superscript small de (for 2nd ordinal in French) \\supde \u1d48\u1d49 superscript small de (for 2nd ordinal in French) \\sup- \u207b superscript minus sign (U+207B) \\sup+ \u207a superscript plus sign (U+207A) \\sub0 \u2080 subscript 0 (U+2080) \\sub1 \u2081 subscript 1 (U+2081) \\sub2 \u2082 subscript 2 (U+2082) \\sub3 \u2083 subscript 3 (U+2083) \\sub4 \u2084 subscript 4 (U+2084) \\sub5 \u2085 subscript 5 (U+2085) \\sub6 \u2086 subscript 6 (U+2086) \\sub7 \u2087 subscript 7 (U+2087) \\sub8 \u2088 subscript 8 (U+2088) \\sub9 \u2089 subscript 9 (U+2089) \\subs \u209b subscript s (U+209B) The list above can also be checked in Options > Preferences > Auto-Completion > Autotext .", "title": "Autotext"}, {"location": "misc/autotext/#omegat-autotext-entries", "text": "The Auto-Completer allows to insert a special character by typing a shortcut. The table below shows the list of shortcuts available in OmegaT. Shorcut Character Description \\lq \u201c upper left double quotation mark (U+201C) \\rq \u201d upper right double quotation mark (U+201D) \\lolq \u201e lower left (low-9) double quotation mark (U+201E) << \u00ab left-pointing double angle quotation mark (U+00AB) >> \u00bb right-pointing duoble angle quotation mark (U+00BB) \\laquo \u00ab left-pointing double angle quotation mark (U+00AB) \\raquo \u00bb right-pointing duoble angle quotation mark (U+00BB) \\rsquo \u2019 right single quotation mark (U+2019) \\apos \u2019 right single quotation mark (U+2019) \\lsquo \u2018 left single quotation mark (U+2018) \\x \u00d7 multiplication symbol / vector product \\times \u00d7 multiplication symbol \\nbsp non-breaking space \\tm \u2122 trademark symbol \\reg \u00ae registered (U+00AE) (tm) \u2122 trademark symbol \\sup0 \u2070 superscript 0 (U+2070) \\sup1 \u00b9 superscript 1 (U+00B9) \\sup2 \u00b2 superscript 2 (U+00B2) \\sup3 \u00b3 superscript 3 (U+00B3) \\sup4 \u2074 superscript 4 (U+2074) \\sup5 \u2075 superscript 5 (U+2075) \\sup6 \u2076 superscript 6 (U+2076) \\sup7 \u2077 superscript 7 (U+2077) \\sup8 \u2078 superscript 8 (U+2078) \\sup9 \u2079 superscript 9 (U+2079) \\supi \u2071 superscript i (U+2071) \\supn \u207f superscript n (U+207F) \\sup( \u207d superscript left parenthesis (U+207D) \\sup) \u207e superscript right parenthesis (U+207E) \\lrm \u200e LRM (U+200E) \\rlm \u200f RLM (U+200F) \\minus \u2013 n-dash (U+2013) \\ndash \u2013 n-dash (U+2013) \\mdash \u2014 m-dash (U+2014) \\pi \u03c0 mathematical pi letter \\thinspace \u2009 thin space \\ellipsis \u2026 horizontal ellipsis \\divided \u00f7 division \\middot \u00b7 interpunct/interpoint/middle dot/middot/centered dot (multiplication / scalar product) \\interpunct \u00b7 interpunct/interpoint/middle dot/middot/centered dot (multiplication / scalar product) \\bullet \u2219 bullet operator (U+2219) \\pm \u00b1 plus or minus \\le \u2264 less than or equal to \\ge \u2265 greater than or equal to \\ne \u2260 does not equal \\approx \u2248 approximately equal to \\emptyset \u2205 empty set \\sqrt \u221a square root (U+221A) \\deg \u00b0 degree \\infty \u221e infinity \\copyright \u00a9 copyright symbol \\smalle \u1d49 modifier letter small e (U+1D49) \\Omegat \u03a9 Greek capital letter omega / Ohm \\pound \u00a3 pound currency \\euro \u20ac euro currency \\cent \u00a2 cent (U+00A2) \\yen \u00a5 yen (U+00A5) \\ordf \u00aa feminine ordinal indicator (U+00AA) \\ordm \u00ba masculine ordinal indicator (U+00BA) \\shy \u00ad soft hyphen (U+00AD) \\micro \u00b5 micro (U+00B5) \\not \u00ac not sign (U+00AC) \\frac12 \u00bd vulgar fraction 1/2 / half \\frac13 \u2153 vulgar fraction 1/3 / third \\frac23 \u2154 vulgar fraction 2/3 \\frac14 \u00bc vulgar fraction 1/4 / quarter \\frac34 \u00be vulgar fraction 3/4 \\frac15 \u2155 vulgar fraction 1/5 / fifth \\frac25 \u2156 vulgar fraction 2/5 \\frac35 \u2157 vulgar fraction 3/5 \\frac45 \u2158 vulgar fraction 4/5 \\frac16 \u2159 vulgar fraction 1/6 \\frac56 \u215a vulgar fraction 5/6 \\frac17 \u2150 vulgar fraction 1/7 \\frac18 \u215b vulgar fraction 1/8 \\frac38 \u215c vulgar fraction 3/8 \\frac58 \u215d vulgar fraction 5/8 \\frac78 \u215e vulgar fraction 7/8 \\frac19 \u2151 vulgar fraction 1/9 \\frac110 \u2152 vulgar fraction 1/10 \\fracslash \u2044 fraction slash (E+2044\u209b) \\9 \u0669 nan \\8 \u0668 nan \\7 \u0667 nan \\6 \u0666 nan \\5 \u0665 nan \\4 \u0664 nan \\3 \u0663 nan \\2 \u0662 nan \\1 \u0661 nan \\0 \u0660 nan \\ar_percent \u2052 commercial minus sign (U+2052) \\nbhy \u2011 non-breaking hyphen \\ordrd \u02b3\u1d48 rd ordinal superscript \\ordnd \u207f\u1d48 nd ordinal superscript \\ordst \u02e2\u1d57 st ordinal superscript \\ordth \u1d57\u02b0 th ordinal superscript \\mathx \ud835\udc65 Mathematical italic small x \\orde \u1d49 superscript small e (for ordinals in French) \\supe \u1d49 superscript small e (for ordinals in French) \\ordde \u1d48\u1d49 superscript small de (for 2nd ordinal in French) \\supde \u1d48\u1d49 superscript small de (for 2nd ordinal in French) \\sup- \u207b superscript minus sign (U+207B) \\sup+ \u207a superscript plus sign (U+207A) \\sub0 \u2080 subscript 0 (U+2080) \\sub1 \u2081 subscript 1 (U+2081) \\sub2 \u2082 subscript 2 (U+2082) \\sub3 \u2083 subscript 3 (U+2083) \\sub4 \u2084 subscript 4 (U+2084) \\sub5 \u2085 subscript 5 (U+2085) \\sub6 \u2086 subscript 6 (U+2086) \\sub7 \u2087 subscript 7 (U+2087) \\sub8 \u2088 subscript 8 (U+2088) \\sub9 \u2089 subscript 9 (U+2089) \\subs \u209b subscript s (U+209B) The list above can also be checked in Options > Preferences > Auto-Completion > Autotext .", "title": "OmegaT autotext entries"}, {"location": "misc/aux/", "text": "Auxiliary tools \u00b6 AutoHotKey (e.g. to insert no-break spaces) \u00b6 If you need to insert non-breaking spaces in your translation, you can use the autotext entry \\nbsp . However, if this is not convenient (e.g. because you need to insert no-break spaces veeeery often) you can use a AutoHotKey script on Windows. AutoHotKey is a standalone software and has nothing to do with OmegaT. The AutoHotKey script can be used to insert autotext (e.g. the no-break space in this case) in any other application in your system. Info AutoHotKey is a Windows-only application. If you're on Mac or Linux, you should find an alternative way to insert non-breaking spaces. Perhaps your operating system natively supports autotext without the need to install third-party apps. How to install the AutoHotKey script \u00b6 Follow these steps: Download and install AutoHotKey . Press Win+R on your keyboard, paste shell:startup and press OK. The startup folder opens up. Right-click the following link to the AHK script , select \u201cSave link as\u201d and save the nbsp.ahk script in your startup folder. In the startup folder, right-click the script file ( nbsp.ahk ) and choose Run script . This script will be run automatically the next time your machine starts. Info You're free to install AutoHotKey and use the AutoHotKey that we provide for your convenience using the steps above. However, we cannot provide support for AutoHotKey. You can find help in the AutoHotKey community. How to insert the no-break space: \u00b6 Click in the position in the text where you want to insert the non-breaking space. Press Ctrl + Shift + Space .", "title": "Auxiliary tools"}, {"location": "misc/aux/#auxiliary-tools", "text": "", "title": "Auxiliary tools"}, {"location": "misc/aux/#autohotkey-eg-to-insert-no-break-spaces", "text": "If you need to insert non-breaking spaces in your translation, you can use the autotext entry \\nbsp . However, if this is not convenient (e.g. because you need to insert no-break spaces veeeery often) you can use a AutoHotKey script on Windows. AutoHotKey is a standalone software and has nothing to do with OmegaT. The AutoHotKey script can be used to insert autotext (e.g. the no-break space in this case) in any other application in your system. Info AutoHotKey is a Windows-only application. If you're on Mac or Linux, you should find an alternative way to insert non-breaking spaces. Perhaps your operating system natively supports autotext without the need to install third-party apps.", "title": "AutoHotKey (e.g. to insert no-break spaces)"}, {"location": "misc/aux/#how-to-install-the-autohotkey-script", "text": "Follow these steps: Download and install AutoHotKey . Press Win+R on your keyboard, paste shell:startup and press OK. The startup folder opens up. Right-click the following link to the AHK script , select \u201cSave link as\u201d and save the nbsp.ahk script in your startup folder. In the startup folder, right-click the script file ( nbsp.ahk ) and choose Run script . This script will be run automatically the next time your machine starts. Info You're free to install AutoHotKey and use the AutoHotKey that we provide for your convenience using the steps above. However, we cannot provide support for AutoHotKey. You can find help in the AutoHotKey community.", "title": "How to install the AutoHotKey script"}, {"location": "misc/aux/#how-to-insert-the-no-break-space", "text": "Click in the position in the text where you want to insert the non-breaking space. Press Ctrl + Shift + Space .", "title": "How to insert the no-break space:"}, {"location": "misc/bidi/", "text": "Handling bidirectionality in OmegaT \u00b6 Text direction and text alignment \u00b6 By default, text direction in the translation editor is left to right (LTR) and text is aligned to the left. That applies to text in any language except languages written in a right-to-left (RTL) script, like Arabic, Hebrew, Syriac, etc., in which case the segment flows from right to left (RTL) and is aligned to the right. Global text direction and alignment of source and target segments is determined by the source and target languages, respectively, indicated in the project settings. Depending on the language, segments are aligned either to the left or to the right. On the other hand, while text direction at the segment level is determined by the project settings, text direction might change inside the segment depending on the script used. For example, English text in a LTR segment will flow left to right but a quotation in Arabic in that same segment will flow right to left. Since OmegaT users are only responsible for producing the translation, let\u2019s focus on what happens in target segments. Everything that follows applies to source segments too, with the difference that they are not directly editable in the translation editor in OmegaT. Bidirectionality mode \u00b6 The bidirectionality mode activates either when at least one of the two languages in the project uses a RTL script or when some text in a RTL is inserted. When the bidirectionality mode is activated, text direction is indicated by a flag on the top of the cursor. In the image below, notice how by default the cursor flag points left in a RTL segment but it may point left or right depending on the previous character: In text written in an LTR script, text flows from left to right, which means that the cursor flag points right and every character typed in LTR script always appears to the right of the previous one. That is always the case for the whole LTR segment unless it contains some fragment in an RTL script, in which case the rules for RTL text apply within that fragment. Strong and weak directionality \u00b6 In text written in an RTL script, text flows from right to left or left to right depending on the characters typed. Alphabetic characters have a RTL directionality: after each alphabetical character, the cursor flag points left, which means that if a new character is inserted, it will appear to the left of the cursor. On the other hand, numeric characters have a LTR directionality: after each number, the cursor flag points right, which means that if a new number is inserted, it will appear to the right of the cursor. Strings in LTR script will behave like numbers. Letters and numbers have a strong directionality, which means that they always flow in the same direction: letters in RTL script flow from right to left, letters in LTR flow from left to right, and numbers in any script always flow from left to right too. However, other characters like punctuation symbols do not have an intrinsic directionality of their own and will inherit the directionality of the segment (hence called of weak or neutral directionality): one same character (e.g. +, as in the image above) will flow right to left in a RTL segment, whereas it will flow left to right in a LTR segment. Orientation \u00b6 Some characters, such as quotation marks, are purely bidirectional and may also have a different orientation depending on the directionality of the segment. For example, the opening double angle quotation mark (Unicode U+00AB) points left when used in a LTR segment, but the same character points right when used in a RTL segment. In the image below, an autotext entry is used to insert that character in an LTR segment: In the image below, in turn, the same autotext entry is used to insert the same character in a LTR segment: The same thing would happen with any other double characters with neutral directionality, such as parenthesis, square brackets, curly brackets, etc. The opening character will point left or right depending on the directionality of the text stretch where it is inserted. Bidirectionality control characters \u00b6 Often the default behaviour described above is fine, but when you\u2019re mixing RTL text and LTR text or using special characters with weak directionality in RTL, you might need to use Unicode bidirectionality control characters (or bidi characters for short) to achieve the expected directionality. Bidi control characters can be found in the menu Edit > Insert Unicode Control Characters and may be used to: insert an invisible character with a certain strong directionality to force a specific position for a character with weak directionality create an embedding which works as a sort of protective environment within which text can flow in the opposite direction of the segment. These control characters are invisible, nothing is display or printed, but they change directionality. If you want to see where these characters are inserted, you can activate option View > Mark Bidirectional Algorithm Control Characters . Marks \u00b6 Let\u2019s see a few examples. Some expressions and brand names combine symbols with letters, e.g. Yahoo!, C++, C#, Hola!, Chips Ahoy!, etc. If you must write, say, \u201cC++\u201d in Arabic, you will notice that by default the + characters will appear to the left of the letter C: That is obviously incorrect. To force the correct position of the ++ characters, type C, then ++, then insert a left-to-right mark (or LRM for short) at the end. The ++ part will then be surrounded by two characters with strong LTR directionality (namely, the letter C and the LRM) and therefore will inherit the directionality of those characters and flow left to right instead of inheriting the directionality of the segment and flow right to left. See that in action in the following image: You might be tempted to type characters in reverse order: first ++, then C. Even though that might look good, that is logically wrong and could bring about issues when the text is further processed later or subjected to different uses. For example, if you type ++C in Arabic, even if it looks visually correct in the translation editor, it will not appear in search results when a user looks for \u201cC++\u201d in the Arabic document. Let alone the fact that often, if the expression is a bit complex, you\u2019ll struggle with trial and error until you obtain something that (only) looks as expected (although underneath it is wrong). Don\u2019t try to fake the looks. LRM and RLM (marks) characters are enough when you must change the directionality and position of one character only at the end or beginning of one homogeneous chunk of text. However, when the expression that must flow in the opposite direction contains several parts separated by spaces, or contains non-alphanumeric characters as well as alphanumeric characters, it\u2019s often better to use RTL or LTR embeddings. Embeddings \u00b6 The behaviour of embeddings is a bit different from that of marks. For starters, two characters must be inserted: one to start the embedding and another one to pop out of it. For example, to create a LTR embedding in an RTL segment, you would insert a left-to-right embedding (LRE) character, then the LTR text, then the pop directional formatting (PDF) character. Likewise, to create a RTL embedding in an LTR segment, you would insert a right-to-left embedding (RLE) character, then the RTL text, then the PDF character. Let\u2019s see an example. Equations, formulas and mathematical notation in general are expressions that must normally run left-to-right in bidirectional languages like Arabic or Hebrew, just like in English. Simply typing or copy-pasting an equation in Arabic will not produce the correct result, as can be seen in the image below: Instead, you should proceed in this way to create a LTR embedding: insert the LRE character, then type or insert the equation, finally insert the PDF character. See that in action: Notice how the red square rim appears around the LTR embedding right after inserting the PDF character, when the option Mark Bidirectional Algorithm Control Characters is activated in the View menu.", "title": "Bidirectionality"}, {"location": "misc/bidi/#handling-bidirectionality-in-omegat", "text": "", "title": "Handling bidirectionality in OmegaT"}, {"location": "misc/bidi/#text-direction-and-text-alignment", "text": "By default, text direction in the translation editor is left to right (LTR) and text is aligned to the left. That applies to text in any language except languages written in a right-to-left (RTL) script, like Arabic, Hebrew, Syriac, etc., in which case the segment flows from right to left (RTL) and is aligned to the right. Global text direction and alignment of source and target segments is determined by the source and target languages, respectively, indicated in the project settings. Depending on the language, segments are aligned either to the left or to the right. On the other hand, while text direction at the segment level is determined by the project settings, text direction might change inside the segment depending on the script used. For example, English text in a LTR segment will flow left to right but a quotation in Arabic in that same segment will flow right to left. Since OmegaT users are only responsible for producing the translation, let\u2019s focus on what happens in target segments. Everything that follows applies to source segments too, with the difference that they are not directly editable in the translation editor in OmegaT.", "title": "Text direction and text alignment"}, {"location": "misc/bidi/#bidirectionality-mode", "text": "The bidirectionality mode activates either when at least one of the two languages in the project uses a RTL script or when some text in a RTL is inserted. When the bidirectionality mode is activated, text direction is indicated by a flag on the top of the cursor. In the image below, notice how by default the cursor flag points left in a RTL segment but it may point left or right depending on the previous character: In text written in an LTR script, text flows from left to right, which means that the cursor flag points right and every character typed in LTR script always appears to the right of the previous one. That is always the case for the whole LTR segment unless it contains some fragment in an RTL script, in which case the rules for RTL text apply within that fragment.", "title": "Bidirectionality mode"}, {"location": "misc/bidi/#strong-and-weak-directionality", "text": "In text written in an RTL script, text flows from right to left or left to right depending on the characters typed. Alphabetic characters have a RTL directionality: after each alphabetical character, the cursor flag points left, which means that if a new character is inserted, it will appear to the left of the cursor. On the other hand, numeric characters have a LTR directionality: after each number, the cursor flag points right, which means that if a new number is inserted, it will appear to the right of the cursor. Strings in LTR script will behave like numbers. Letters and numbers have a strong directionality, which means that they always flow in the same direction: letters in RTL script flow from right to left, letters in LTR flow from left to right, and numbers in any script always flow from left to right too. However, other characters like punctuation symbols do not have an intrinsic directionality of their own and will inherit the directionality of the segment (hence called of weak or neutral directionality): one same character (e.g. +, as in the image above) will flow right to left in a RTL segment, whereas it will flow left to right in a LTR segment.", "title": "Strong and weak directionality"}, {"location": "misc/bidi/#orientation", "text": "Some characters, such as quotation marks, are purely bidirectional and may also have a different orientation depending on the directionality of the segment. For example, the opening double angle quotation mark (Unicode U+00AB) points left when used in a LTR segment, but the same character points right when used in a RTL segment. In the image below, an autotext entry is used to insert that character in an LTR segment: In the image below, in turn, the same autotext entry is used to insert the same character in a LTR segment: The same thing would happen with any other double characters with neutral directionality, such as parenthesis, square brackets, curly brackets, etc. The opening character will point left or right depending on the directionality of the text stretch where it is inserted.", "title": "Orientation"}, {"location": "misc/bidi/#bidirectionality-control-characters", "text": "Often the default behaviour described above is fine, but when you\u2019re mixing RTL text and LTR text or using special characters with weak directionality in RTL, you might need to use Unicode bidirectionality control characters (or bidi characters for short) to achieve the expected directionality. Bidi control characters can be found in the menu Edit > Insert Unicode Control Characters and may be used to: insert an invisible character with a certain strong directionality to force a specific position for a character with weak directionality create an embedding which works as a sort of protective environment within which text can flow in the opposite direction of the segment. These control characters are invisible, nothing is display or printed, but they change directionality. If you want to see where these characters are inserted, you can activate option View > Mark Bidirectional Algorithm Control Characters .", "title": "Bidirectionality control characters"}, {"location": "misc/bidi/#marks", "text": "Let\u2019s see a few examples. Some expressions and brand names combine symbols with letters, e.g. Yahoo!, C++, C#, Hola!, Chips Ahoy!, etc. If you must write, say, \u201cC++\u201d in Arabic, you will notice that by default the + characters will appear to the left of the letter C: That is obviously incorrect. To force the correct position of the ++ characters, type C, then ++, then insert a left-to-right mark (or LRM for short) at the end. The ++ part will then be surrounded by two characters with strong LTR directionality (namely, the letter C and the LRM) and therefore will inherit the directionality of those characters and flow left to right instead of inheriting the directionality of the segment and flow right to left. See that in action in the following image: You might be tempted to type characters in reverse order: first ++, then C. Even though that might look good, that is logically wrong and could bring about issues when the text is further processed later or subjected to different uses. For example, if you type ++C in Arabic, even if it looks visually correct in the translation editor, it will not appear in search results when a user looks for \u201cC++\u201d in the Arabic document. Let alone the fact that often, if the expression is a bit complex, you\u2019ll struggle with trial and error until you obtain something that (only) looks as expected (although underneath it is wrong). Don\u2019t try to fake the looks. LRM and RLM (marks) characters are enough when you must change the directionality and position of one character only at the end or beginning of one homogeneous chunk of text. However, when the expression that must flow in the opposite direction contains several parts separated by spaces, or contains non-alphanumeric characters as well as alphanumeric characters, it\u2019s often better to use RTL or LTR embeddings.", "title": "Marks"}, {"location": "misc/bidi/#embeddings", "text": "The behaviour of embeddings is a bit different from that of marks. For starters, two characters must be inserted: one to start the embedding and another one to pop out of it. For example, to create a LTR embedding in an RTL segment, you would insert a left-to-right embedding (LRE) character, then the LTR text, then the pop directional formatting (PDF) character. Likewise, to create a RTL embedding in an LTR segment, you would insert a right-to-left embedding (RLE) character, then the RTL text, then the PDF character. Let\u2019s see an example. Equations, formulas and mathematical notation in general are expressions that must normally run left-to-right in bidirectional languages like Arabic or Hebrew, just like in English. Simply typing or copy-pasting an equation in Arabic will not produce the correct result, as can be seen in the image below: Instead, you should proceed in this way to create a LTR embedding: insert the LRE character, then type or insert the equation, finally insert the PDF character. See that in action: Notice how the red square rim appears around the LTR embedding right after inserting the PDF character, when the option Mark Bidirectional Algorithm Control Characters is activated in the View menu.", "title": "Embeddings"}, {"location": "misc/faq/", "text": "FAQ \u00b6 Can I export the contents of the OmegaT project in Excel ? \u00b6 Yes. To export the contents of the OmegaT project in Excel, go to Tools > Write Project to Excel . To access the exported Excel, go to Project > Access Project Contents > Root . The Excel will be found in the script_output folder. Warning Please remember that the Excel file cannot be reimported in OmegaT. Any change you make in translations in that Excel export needs to be reflected in the OmegaT project. The size of text in the editor is too small or too big. \u00b6 To change the font size go to Options > Preferences > Font . Change the font size to one you find suitable. This has no impact on the actual font size in the target files, it only changes the display in OmegaT. How do I install the spellchecker files? \u00b6 A spelling checker is available in OmegaT and you must install the spellchecking dictionary for your language in order to use it. Follow these steps: Go to Options > Preferences > Spellchecker . Click on Install new dictionary , and a list of languages will appear. Select the appropriate language for your language version (e.g. es_AR - Spanish (Argentina) if your language is Spanish and your country is Argentina). Press the Install button. You can close the remaining pop up window. The spellchecker is now installed. Tip You can also watch the following video to see those steps in action: There is no spellchecker for my language. \u00b6 If you cannot find your language in the list when you go to Options > Preferences > Spellchecker. and then clicking on Install new dictionary , please contact the helpdesk and our team will try to find a spellchecking dictionary for you. Please note that spellchecking dictionaries might not be available for all languages. I don't have the Unpack project from OMT file item. \u00b6 If you do not see the Unpack project from OMT file option in the Project menu, please follow our OmegaT installation and setup guide (available from the Installation and setup section of these guides) and choose the third path (\"Version 5.7.1 of OmegaT is already installed in your machine\") to install the customization (again). If you still cannot see the Unpack project from OMT file option after doing that, please contact the Helpdesk. How can I correct a typo in a term in the glossary? \u00b6 Yes. Please follow these steps: Go to Project > Access Project contents > Glossaries to access your writeable glossary file. The Glossaries folder will open, which contains a file named glossary.txt . Open it in your plain text editor (e.g. Notepad): Correct any term that contains an error and Save the file. Warning Do not open the glossary file in Microsoft Word or any other similar word processor. Do we have access to the TMs from previous cycles? \u00b6 Yes. TMs (translation memories) from previous cycles should already be included in your project. You may see translations coming from them in the Matches pane, or you may find them by running a text search (see the relevant section in the guide, under Other useful features > Running concordance searches ). You may also access translations from all previous cycles of the project for your language in MemoryLn . Info If you don't see the expected translations in your OmegaT project and in MemoryLn, please contact the Helpdesk. Can I work in Trados or another CAT tool? \u00b6 The answer is no. OmegaT is specifically customized to edit the files you are working on. Such a customization is not possible in Trados or memoQ. Removing the files from the OmegaT project and translating them separately may damage the files and render them unusable for further use. How can I find translations searching by the target text? \u00b6 Proceed as follows: Press Ctrl + F on your keyboard. The search dialog opens. Type the text in the target language that you want to find. Check option \"In translation\" in the search dialog Press the Search button. I only see one 100% match when I am reconciling. \u00b6 If you matches are identical, only one of them will be displayed in the Matches pane to avoid space-consuming duplicates. If you only see one translation in the Matches pane during the reconciliation task, that means the two translators have proposed the exact same translation. Next to the 100% match you will also notice it is written \"+1 more\".", "title": "FAQ"}, {"location": "misc/faq/#faq", "text": "", "title": "FAQ"}, {"location": "misc/faq/#can-i-export-the-contents-of-the-omegat-project-in-excel", "text": "Yes. To export the contents of the OmegaT project in Excel, go to Tools > Write Project to Excel . To access the exported Excel, go to Project > Access Project Contents > Root . The Excel will be found in the script_output folder. Warning Please remember that the Excel file cannot be reimported in OmegaT. Any change you make in translations in that Excel export needs to be reflected in the OmegaT project.", "title": "Can I export the contents of the OmegaT project in Excel ?"}, {"location": "misc/faq/#the-size-of-text-in-the-editor-is-too-small-or-too-big", "text": "To change the font size go to Options > Preferences > Font . Change the font size to one you find suitable. This has no impact on the actual font size in the target files, it only changes the display in OmegaT.", "title": "The size of text in the editor is too small or too big."}, {"location": "misc/faq/#how-do-i-install-the-spellchecker-files", "text": "A spelling checker is available in OmegaT and you must install the spellchecking dictionary for your language in order to use it. Follow these steps: Go to Options > Preferences > Spellchecker . Click on Install new dictionary , and a list of languages will appear. Select the appropriate language for your language version (e.g. es_AR - Spanish (Argentina) if your language is Spanish and your country is Argentina). Press the Install button. You can close the remaining pop up window. The spellchecker is now installed. Tip You can also watch the following video to see those steps in action:", "title": "How do I install the spellchecker files?"}, {"location": "misc/faq/#there-is-no-spellchecker-for-my-language", "text": "If you cannot find your language in the list when you go to Options > Preferences > Spellchecker. and then clicking on Install new dictionary , please contact the helpdesk and our team will try to find a spellchecking dictionary for you. Please note that spellchecking dictionaries might not be available for all languages.", "title": "There is no spellchecker for my language."}, {"location": "misc/faq/#i-dont-have-the-unpack-project-from-omt-file-item", "text": "If you do not see the Unpack project from OMT file option in the Project menu, please follow our OmegaT installation and setup guide (available from the Installation and setup section of these guides) and choose the third path (\"Version 5.7.1 of OmegaT is already installed in your machine\") to install the customization (again). If you still cannot see the Unpack project from OMT file option after doing that, please contact the Helpdesk.", "title": "I don't have the Unpack project from OMT file item."}, {"location": "misc/faq/#how-can-i-correct-a-typo-in-a-term-in-the-glossary", "text": "Yes. Please follow these steps: Go to Project > Access Project contents > Glossaries to access your writeable glossary file. The Glossaries folder will open, which contains a file named glossary.txt . Open it in your plain text editor (e.g. Notepad): Correct any term that contains an error and Save the file. Warning Do not open the glossary file in Microsoft Word or any other similar word processor.", "title": "How can I correct a typo in a term in the glossary?"}, {"location": "misc/faq/#do-we-have-access-to-the-tms-from-previous-cycles", "text": "Yes. TMs (translation memories) from previous cycles should already be included in your project. You may see translations coming from them in the Matches pane, or you may find them by running a text search (see the relevant section in the guide, under Other useful features > Running concordance searches ). You may also access translations from all previous cycles of the project for your language in MemoryLn . Info If you don't see the expected translations in your OmegaT project and in MemoryLn, please contact the Helpdesk.", "title": "Do we have access to the TMs from previous cycles?"}, {"location": "misc/faq/#can-i-work-in-trados-or-another-cat-tool", "text": "The answer is no. OmegaT is specifically customized to edit the files you are working on. Such a customization is not possible in Trados or memoQ. Removing the files from the OmegaT project and translating them separately may damage the files and render them unusable for further use.", "title": "Can I work in Trados or another CAT tool?"}, {"location": "misc/faq/#how-can-i-find-translations-searching-by-the-target-text", "text": "Proceed as follows: Press Ctrl + F on your keyboard. The search dialog opens. Type the text in the target language that you want to find. Check option \"In translation\" in the search dialog Press the Search button.", "title": "How can I find translations searching by the target text?"}, {"location": "misc/faq/#i-only-see-one-100-match-when-i-am-reconciling", "text": "If you matches are identical, only one of them will be displayed in the Matches pane to avoid space-consuming duplicates. If you only see one translation in the Matches pane during the reconciliation task, that means the two translators have proposed the exact same translation. Next to the 100% match you will also notice it is written \"+1 more\".", "title": "I only see one 100% match when I am reconciling."}, {"location": "misc/fonts/", "text": "Fonts \u00b6 Installing suplemental fonts \u00b6 On Windows 10 \u00b6 If your language has special requirements (such as a double-byte writing system for some Asian languages, etc.), please follow these steps (where LANGUAGE would be your language): Go to Windows Settings > Apps > Optional Features > + Add a feature > LANGUAGE Suplemental Fonts . The install that package and then restart OmegaT. Recommended fonts in OmegaT \u00b6 Language Fonts Comment Korean UnDotum, Malgun Gothic Chinese NSimSun Source Han Sans or Source Han Serif (untested!) Amharic, Tigrinya Ebrima Thai Leelawadee UI Japanese Meiryo, NSimSun Khmer Khmer UI", "title": "Fonts"}, {"location": "misc/fonts/#fonts", "text": "", "title": "Fonts"}, {"location": "misc/fonts/#installing-suplemental-fonts", "text": "", "title": "Installing suplemental fonts"}, {"location": "misc/fonts/#recommended-fonts-in-omegat", "text": "Language Fonts Comment Korean UnDotum, Malgun Gothic Chinese NSimSun Source Han Sans or Source Han Serif (untested!) Amharic, Tigrinya Ebrima Thai Leelawadee UI Japanese Meiryo, NSimSun Khmer Khmer UI", "title": "Recommended fonts in OmegaT"}, {"location": "misc/security/", "text": "Security information \u00b6 OmegaT is the translation tool selected for the language tasks of various projects. cApStAn is responsible for customizing this tool so that it can interact optimally with the XLIFF files that will be prepared for those projects, and to streamline language tasks and reduce support requests. OmegaT will be installed from a designated installer that will be downloaded from the http://omegat.org website. The customization consists of editing or adding some settings files to the default installation and an executable developed by cApStAn will be provided to users to save them the effort of doing the customization manually. If you prefer to customize manually, that's also possible, just let us know. The purpose of the present document is to provide information relevant for IT departments who must ensure that any software installed in their organization does not pose any security threads. Updating Windows malware definitions \u00b6 Before downloading the installation files (OmegaT installer and customization utility), you should update Windows Defender's definitions. On the command prompt as administrator: Change directory to C:\\Program Files\\Windows Defender Run MpCmdRun.exe -removedefinitions -dynamicsignatures Run MpCmdRun.exe -SignatureUpdate Source: https://www.microsoft.com/en-us/wdsi/definitions Integrity verification <= UPDATE NEEDED \u00b6 You can check the integrity of the file to make sure that, after download, you have the same file that is available for download in the repository of OmegaT binaries. On Windows, you can compute the cryptographic hash values of a binary file with the File Checksum Integrity Verifier utility (check this for further information and download the utility). The correct hashes of the 64-bit installer (OmegaT_4.1.5_04_Beta_Windows_64.exe) are: SHA1: 9a7560368ca11255c4359c2ed225eb0bd7a7fbe0 MD5: 8c4dd481b715396979ba6ec5e2d1e9a8 The correct hashes of the 32-bit installer (OmegaT_4.1.5_04_Beta_Windows.exe) are: SHA1: 682e38f718ef8736ccb978f45dd13da75184648a MD5: 608417d270bc67f153d92e243abd1f96 These values are taken from the official OmegaT download page . If you obtain the same values, you can be certain that you have the same file as it\u2019s available for download and that it\u2019s safe to whitelist it. Java maintenance \u00b6 OmegaT is developed in Java and needs JRE to run. The OmegaT installers we recommend include the version of JRE that OmegaT needs, and that JRE would be uninstalled when OmegaT is uninstalled. However, in any case, as Java can be a security risk if it\u2019s not kept up to date, it\u2019s worth maintaining that version of JRE up to date after installed if necessary. Data leakage \u00b6 OmegaT can check for new versions, get MT results, get glossary matches from TaaS, download MediaWiki links and use them as source files, have remote files on HTTP, Git and SVN servers mapped locally, and then there's SVN/Git team project functionality. We're not using any of those functions in the translation of the PISA/PIAAC materials, which means we won't instruct users to configure or use them. However, it\u2019s always possible that the user unilaterally uses them. If this is a concern for the organization, OmegaT could be made to work in a complete offline manner, namely it could be started with a non-functional proxy, so it won't connect to internet at all (specifying a non-existing proxy server, e.g. 270.270, in the startup parameters in the OmegaT.l4J.ini file). In other words, it\u2019s up to the organization and their internal policy to decide how much access to the internet it must be allowed to OmegaT. Open source \u00b6 In case of any concerns about vulnerabilities in OmegaT against viruses or other malware, the source code is freely available and used to build software packages in several OS distributions. Any Java engineer can inspect the code and conduct any tests to assess its robustness and reliability. Endorsement by big organizations \u00b6 The European Commission has been promoting the use of open-source software namely within its [R&D programmes]. It is in this context that open source applications like OmegaT are being used in DGT (the European Commission\u2019s Directorate-General for Translation), alongside other commercial applications. DGT has been using OmegaT for prototyping since 2012, customizing it and extending it with some useful improvements. This information can be useful to endorse the usage of OmegaT. Source: http://ec.europa.eu/translation/portuguese/magazine/documents/folha54_ot_en.pdf OmegaT is also one of the Translator Partners of Microsoft. Please see https://www.microsoft.com/en-us/translator/business/partners/ DGT and Microsoft can attest the security of OmegaT.", "title": "IT security"}, {"location": "misc/security/#security-information", "text": "OmegaT is the translation tool selected for the language tasks of various projects. cApStAn is responsible for customizing this tool so that it can interact optimally with the XLIFF files that will be prepared for those projects, and to streamline language tasks and reduce support requests. OmegaT will be installed from a designated installer that will be downloaded from the http://omegat.org website. The customization consists of editing or adding some settings files to the default installation and an executable developed by cApStAn will be provided to users to save them the effort of doing the customization manually. If you prefer to customize manually, that's also possible, just let us know. The purpose of the present document is to provide information relevant for IT departments who must ensure that any software installed in their organization does not pose any security threads.", "title": "Security information"}, {"location": "misc/security/#updating-windows-malware-definitions", "text": "Before downloading the installation files (OmegaT installer and customization utility), you should update Windows Defender's definitions. On the command prompt as administrator: Change directory to C:\\Program Files\\Windows Defender Run MpCmdRun.exe -removedefinitions -dynamicsignatures Run MpCmdRun.exe -SignatureUpdate Source: https://www.microsoft.com/en-us/wdsi/definitions", "title": "Updating Windows malware definitions"}, {"location": "misc/security/#integrity-verification-update-needed", "text": "You can check the integrity of the file to make sure that, after download, you have the same file that is available for download in the repository of OmegaT binaries. On Windows, you can compute the cryptographic hash values of a binary file with the File Checksum Integrity Verifier utility (check this for further information and download the utility). The correct hashes of the 64-bit installer (OmegaT_4.1.5_04_Beta_Windows_64.exe) are: SHA1: 9a7560368ca11255c4359c2ed225eb0bd7a7fbe0 MD5: 8c4dd481b715396979ba6ec5e2d1e9a8 The correct hashes of the 32-bit installer (OmegaT_4.1.5_04_Beta_Windows.exe) are: SHA1: 682e38f718ef8736ccb978f45dd13da75184648a MD5: 608417d270bc67f153d92e243abd1f96 These values are taken from the official OmegaT download page . If you obtain the same values, you can be certain that you have the same file as it\u2019s available for download and that it\u2019s safe to whitelist it.", "title": "Integrity verification <= UPDATE NEEDED"}, {"location": "misc/security/#java-maintenance", "text": "OmegaT is developed in Java and needs JRE to run. The OmegaT installers we recommend include the version of JRE that OmegaT needs, and that JRE would be uninstalled when OmegaT is uninstalled. However, in any case, as Java can be a security risk if it\u2019s not kept up to date, it\u2019s worth maintaining that version of JRE up to date after installed if necessary.", "title": "Java maintenance"}, {"location": "misc/security/#data-leakage", "text": "OmegaT can check for new versions, get MT results, get glossary matches from TaaS, download MediaWiki links and use them as source files, have remote files on HTTP, Git and SVN servers mapped locally, and then there's SVN/Git team project functionality. We're not using any of those functions in the translation of the PISA/PIAAC materials, which means we won't instruct users to configure or use them. However, it\u2019s always possible that the user unilaterally uses them. If this is a concern for the organization, OmegaT could be made to work in a complete offline manner, namely it could be started with a non-functional proxy, so it won't connect to internet at all (specifying a non-existing proxy server, e.g. 270.270, in the startup parameters in the OmegaT.l4J.ini file). In other words, it\u2019s up to the organization and their internal policy to decide how much access to the internet it must be allowed to OmegaT.", "title": "Data leakage"}, {"location": "misc/security/#open-source", "text": "In case of any concerns about vulnerabilities in OmegaT against viruses or other malware, the source code is freely available and used to build software packages in several OS distributions. Any Java engineer can inspect the code and conduct any tests to assess its robustness and reliability.", "title": "Open source"}, {"location": "misc/security/#endorsement-by-big-organizations", "text": "The European Commission has been promoting the use of open-source software namely within its [R&D programmes]. It is in this context that open source applications like OmegaT are being used in DGT (the European Commission\u2019s Directorate-General for Translation), alongside other commercial applications. DGT has been using OmegaT for prototyping since 2012, customizing it and extending it with some useful improvements. This information can be useful to endorse the usage of OmegaT. Source: http://ec.europa.eu/translation/portuguese/magazine/documents/folha54_ot_en.pdf OmegaT is also one of the Translator Partners of Microsoft. Please see https://www.microsoft.com/en-us/translator/business/partners/ DGT and Microsoft can attest the security of OmegaT.", "title": "Endorsement by big organizations"}, {"location": "misc/shortcuts/", "text": "Keyboard shortcuts \u00b6 OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "misc/shortcuts/#keyboard-shortcuts", "text": "", "title": "Keyboard shortcuts"}, {"location": "misc/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "misc/tags/", "text": "Adaptation \u00b6 Adaptation Editing Proofreading \u00b6 Editing Review Reconciliation \u00b6 Reconciliation Review \u00b6 Editing Editing Review Revision \u00b6 Editing Review Translation \u00b6 Translation Verification \u00b6 Editing Verification", "title": "Tags"}, {"location": "misc/tags/#adaptation", "text": "Adaptation Editing", "title": "Adaptation"}, {"location": "misc/tags/#proofreading", "text": "Editing Review", "title": "Proofreading"}, {"location": "misc/tags/#reconciliation", "text": "Reconciliation", "title": "Reconciliation"}, {"location": "misc/tags/#review", "text": "Editing Editing Review", "title": "Review"}, {"location": "misc/tags/#revision", "text": "Editing Review", "title": "Revision"}, {"location": "misc/tags/#translation", "text": "Translation", "title": "Translation"}, {"location": "misc/tags/#verification", "text": "Editing Verification", "title": "Verification"}, {"location": "misc/tips/", "text": "Tips and tricks \u00b6 File organization \u00b6 File organization on your end is very important for the successful execution of your work. Here come some recommendations for a tidy organization. Designate a working folder for the project in your machine, and use that same location for all related tasks. We would suggest a location at a very high level in the folder structure in your computer, e.g. On Windows: C:\\Work\\CLIENT\\PROJECT or C:\\Users\\USER\\Work\\CLIENT\\PROJECT On Mac/Linux: /Users/USER/Work/CLIENT/PROJECT Inside the PROJECT 's working folder above, create the following folder structure (or something similar that fits your purposes): \u251c\u2500\u2500 00_Admin \u251c\u2500\u2500 01_Instructions \u251c\u2500\u2500 02_Tasks \u2514\u2500\u2500 03_Whatever Create your OmegaT project folders inside, say, C:\\Users\\Manolo\\Work\\cApStAn\\Globex\\02_Tasks . The final path to the OmegaT project folder should look like C:\\Users\\USER\\Work\\CLIENT\\PROJECT\\02_Tasks\\OMT-PROJ-DIR , where OMT-PROJ-DIR is (the name of) your local OmegaT project folder. How to copy-paste a URL \u00b6 Select the URL: To select the URL, click right before the first character of the URL and drag your mouse up to the end of the URL. Copy the URL: When the whole URL is highlighted (which means that it's selected), press Ctrl + C in your keyboard. Alternatively, you may right-click the highlighted text and select Copy in the contextual menu that will appear. When you copy text, it'll be stored in your clipboard. Paste the URL: Go to the location where you want to paste the URL and press Ctrl + V to insert it there.", "title": "Tips and tricks"}, {"location": "misc/tips/#tips-and-tricks", "text": "", "title": "Tips and tricks"}, {"location": "misc/tips/#file-organization", "text": "File organization on your end is very important for the successful execution of your work. Here come some recommendations for a tidy organization. Designate a working folder for the project in your machine, and use that same location for all related tasks. We would suggest a location at a very high level in the folder structure in your computer, e.g. On Windows: C:\\Work\\CLIENT\\PROJECT or C:\\Users\\USER\\Work\\CLIENT\\PROJECT On Mac/Linux: /Users/USER/Work/CLIENT/PROJECT Inside the PROJECT 's working folder above, create the following folder structure (or something similar that fits your purposes): \u251c\u2500\u2500 00_Admin \u251c\u2500\u2500 01_Instructions \u251c\u2500\u2500 02_Tasks \u2514\u2500\u2500 03_Whatever Create your OmegaT project folders inside, say, C:\\Users\\Manolo\\Work\\cApStAn\\Globex\\02_Tasks . The final path to the OmegaT project folder should look like C:\\Users\\USER\\Work\\CLIENT\\PROJECT\\02_Tasks\\OMT-PROJ-DIR , where OMT-PROJ-DIR is (the name of) your local OmegaT project folder.", "title": "File organization"}, {"location": "misc/tips/#how-to-copy-paste-a-url", "text": "Select the URL: To select the URL, click right before the first character of the URL and drag your mouse up to the end of the URL. Copy the URL: When the whole URL is highlighted (which means that it's selected), press Ctrl + C in your keyboard. Alternatively, you may right-click the highlighted text and select Copy in the contextual menu that will appear. When you copy text, it'll be stored in your clipboard. Paste the URL: Go to the location where you want to paste the URL and press Ctrl + V to insert it there.", "title": "How to copy-paste a URL"}, {"location": "misc/videos/", "text": "Training videos \u00b6 Accessing a project \u00b6 Change font size \u00b6 Spell checker \u00b6 Navigation through files \u00b6 Navigation through segments \u00b6 Autopropagation \u00b6 Alternative translations \u00b6 Searching in TM \u00b6 Using matches \u00b6 Handling tags \u00b6 QA checks: tags \u00b6 Packing for delivery \u00b6", "title": "Videos"}, {"location": "misc/videos/#training-videos", "text": "", "title": "Training videos"}, {"location": "misc/videos/#accessing-a-project", "text": "", "title": "Accessing a project"}, {"location": "misc/videos/#change-font-size", "text": "", "title": "Change font size"}, {"location": "misc/videos/#spell-checker", "text": "", "title": "Spell checker"}, {"location": "misc/videos/#navigation-through-files", "text": "", "title": "Navigation through files"}, {"location": "misc/videos/#navigation-through-segments", "text": "", "title": "Navigation through segments"}, {"location": "misc/videos/#autopropagation", "text": "", "title": "Autopropagation"}, {"location": "misc/videos/#alternative-translations", "text": "", "title": "Alternative translations"}, {"location": "misc/videos/#searching-in-tm", "text": "", "title": "Searching in TM"}, {"location": "misc/videos/#using-matches", "text": "", "title": "Using matches"}, {"location": "misc/videos/#handling-tags", "text": "", "title": "Handling tags"}, {"location": "misc/videos/#qa-checks-tags", "text": "", "title": "QA checks: tags"}, {"location": "misc/videos/#packing-for-delivery", "text": "", "title": "Packing for delivery"}, {"location": "reconciliation/", "tags": ["Reconciliation"], "text": "a.md-footer__link--prev[aria-label^=\"Previous:\"], .md-nav__icon { display: none !important; } \ud83d\udc4b Welcome to the OmegaT reconciliation guide! \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "Reconciliation"}, {"location": "reconciliation/#welcome-to-the-omegat-reconciliation-guide", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "\ud83d\udc4b Welcome to the OmegaT reconciliation guide!"}, {"location": "reconciliation/accessing-the-project/", "text": "Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Accessing a project"}, {"location": "reconciliation/accessing-the-project/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "reconciliation/accessing-the-project/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "reconciliation/accessing-the-project/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "reconciliation/accessing-the-project/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "reconciliation/accessing-the-project/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "reconciliation/accessing-the-project/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "reconciliation/creating-target-files/", "text": "Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "reconciliation/creating-target-files/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "reconciliation/creating-your-deliverable/", "text": "Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Creating your deliverable"}, {"location": "reconciliation/creating-your-deliverable/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "reconciliation/creating-your-deliverable/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "reconciliation/creating-your-deliverable/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "reconciliation/glossary/", "text": "Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Glossary"}, {"location": "reconciliation/glossary/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "reconciliation/glossary/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "reconciliation/glossary/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "reconciliation/install-and-setup/", "text": "Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "reconciliation/install-and-setup/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "reconciliation/matches/", "text": "Reconciling using matches \u00b6 During the reconciliation task, the translations from translator 1 and translator 2 are handled as matches and are displayed in the Matches pane. A reconciler's task in practice consists of one of these three options: Inserting one of the two matches (and then modify it if needed), OR Inserting part of one of the two matches and then inserting part of the other match, OR Translating the segment from scratch if none of the two matches is suitable. By default, the match from translator 1 is activated. It is the first one in the list and it is bolded . If you want to use the match from translator 2, double click on it to activate that one instead (the activated match will become bolded ). To insert the active match in full, press Ctrl + I on your keyboard. After inserting it, make any necessary changes so that it fits the segment you are reconciling. Alternatively, you can also insert only part of a match or combine several matches: Double-click the match you want to use to activate it Drag your mouse over the part of the match you wish to insert to select it Press Ctrl + I on your keyboard to insert it Select (part of) another match if appropriate or type the rest of the translation Remember It is important to make sure the final translation is harmonized as the two translators may use different terms and styles. To ensure this, make sure you preview the item prior to delivery and perform concordance searches on recurring instructions and terminology.", "title": "Matches"}, {"location": "reconciliation/matches/#reconciling-using-matches", "text": "During the reconciliation task, the translations from translator 1 and translator 2 are handled as matches and are displayed in the Matches pane. A reconciler's task in practice consists of one of these three options: Inserting one of the two matches (and then modify it if needed), OR Inserting part of one of the two matches and then inserting part of the other match, OR Translating the segment from scratch if none of the two matches is suitable. By default, the match from translator 1 is activated. It is the first one in the list and it is bolded . If you want to use the match from translator 2, double click on it to activate that one instead (the activated match will become bolded ). To insert the active match in full, press Ctrl + I on your keyboard. After inserting it, make any necessary changes so that it fits the segment you are reconciling. Alternatively, you can also insert only part of a match or combine several matches: Double-click the match you want to use to activate it Drag your mouse over the part of the match you wish to insert to select it Press Ctrl + I on your keyboard to insert it Select (part of) another match if appropriate or type the rest of the translation Remember It is important to make sure the final translation is harmonized as the two translators may use different terms and styles. To ensure this, make sure you preview the item prior to delivery and perform concordance searches on recurring instructions and terminology.", "title": "Reconciling using matches"}, {"location": "reconciliation/navigation/", "text": "Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation"}, {"location": "reconciliation/navigation/#navigation", "text": "", "title": "Navigation"}, {"location": "reconciliation/navigation/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "reconciliation/navigation/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "reconciliation/navigation/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "reconciliation/other-useful-features/", "text": "Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Other useful features"}, {"location": "reconciliation/other-useful-features/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "reconciliation/other-useful-features/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "reconciliation/other-useful-features/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "reconciliation/other-useful-features/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "reconciliation/other-useful-features/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "reconciliation/other-useful-features/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "reconciliation/other-useful-features/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "reconciliation/qa-checks/", "text": "QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "QA checks"}, {"location": "reconciliation/qa-checks/#qa-checks", "text": "", "title": "QA checks"}, {"location": "reconciliation/qa-checks/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "reconciliation/qa-checks/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "reconciliation/qa-checks/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "reconciliation/repetitions/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Repetitions"}, {"location": "reconciliation/repetitions/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "reconciliation/repetitions/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "reconciliation/repetitions/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "reconciliation/repetitions/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "reconciliation/shortcuts/", "text": "a.md-footer__link--next[aria-label^=\"Next:\"], .md-nav__icon { display: none !important; } OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "reconciliation/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "reconciliation/tags/", "text": "Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy : Fixing tag issues \u00b6 All tags you see in the source text should be present in the translation too and in the correct position. You must correct any errors that you may see when that's not the case. You may find two types of issue: A tag or tag pair is missing: in that case, the solution is simply to insert it . A tag is inserted but misplaced: the solution may be either to drag and drop single tags to the correct position, or simply to delete the tag (or tag pair) and insert it again correctly. Warning for RTL languages In right-to-left languages such as Arabic or Hebrew, moving tags will not work. Please delete the tag and insert it again if you work with any of these languages. Deleting tags \u00b6 If you have inserted a tag incorrectly and need to insert it again, double click on the tag to select it in full and press Backspace or Del on your keyboard to delete it first. Moving tags \u00b6 If you have inserted a tag in the wrong position and need to insert it somewhere else, you can simply drag and drop it. Alternatively, you can also delete it and insert it again.", "title": "Tags"}, {"location": "reconciliation/tags/#tags", "text": "", "title": "Tags"}, {"location": "reconciliation/tags/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "reconciliation/tags/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "reconciliation/tags/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "reconciliation/tags/#fixing-tag-issues", "text": "All tags you see in the source text should be present in the translation too and in the correct position. You must correct any errors that you may see when that's not the case. You may find two types of issue: A tag or tag pair is missing: in that case, the solution is simply to insert it . A tag is inserted but misplaced: the solution may be either to drag and drop single tags to the correct position, or simply to delete the tag (or tag pair) and insert it again correctly. Warning for RTL languages In right-to-left languages such as Arabic or Hebrew, moving tags will not work. Please delete the tag and insert it again if you work with any of these languages.", "title": "Fixing tag issues"}, {"location": "reconciliation/tags/#deleting-tags", "text": "If you have inserted a tag incorrectly and need to insert it again, double click on the tag to select it in full and press Backspace or Del on your keyboard to delete it first.", "title": "Deleting tags"}, {"location": "reconciliation/tags/#moving-tags", "text": "If you have inserted a tag in the wrong position and need to insert it somewhere else, you can simply drag and drop it. Alternatively, you can also delete it and insert it again.", "title": "Moving tags"}, {"location": "review/", "tags": ["Proofreading", "Revision", "Review"], "text": "a.md-footer__link--prev[aria-label^=\"Previous:\"], .md-nav__icon { display: none !important; } \ud83d\udc4b Welcome to the OmegaT proofreading guide! \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "Review"}, {"location": "review/#welcome-to-the-omegat-proofreading-guide", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "\ud83d\udc4b Welcome to the OmegaT proofreading guide!"}, {"location": "review/accessing-the-project/", "text": "Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Accessing a project"}, {"location": "review/accessing-the-project/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "review/accessing-the-project/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "review/accessing-the-project/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "review/accessing-the-project/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "review/accessing-the-project/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "review/accessing-the-project/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "review/creating-target-files/", "text": "Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "review/creating-target-files/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "review/creating-your-deliverable/", "text": "Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Creating your deliverable"}, {"location": "review/creating-your-deliverable/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "review/creating-your-deliverable/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "review/creating-your-deliverable/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "review/glossary/", "text": "Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Glossary"}, {"location": "review/glossary/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "review/glossary/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "review/glossary/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "review/install-and-setup/", "text": "Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "review/install-and-setup/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "review/matches/", "text": "Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "review/matches/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "review/navigation/", "text": "Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation"}, {"location": "review/navigation/#navigation", "text": "", "title": "Navigation"}, {"location": "review/navigation/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "review/navigation/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "review/navigation/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "review/other-useful-features/", "text": "Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Other useful features"}, {"location": "review/other-useful-features/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "review/other-useful-features/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "review/other-useful-features/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "review/other-useful-features/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "review/other-useful-features/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "review/other-useful-features/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "review/other-useful-features/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "review/qa-checks/", "text": "QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "QA checks"}, {"location": "review/qa-checks/#qa-checks", "text": "", "title": "QA checks"}, {"location": "review/qa-checks/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "review/qa-checks/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "review/qa-checks/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "review/repetitions/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Repetitions"}, {"location": "review/repetitions/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "review/repetitions/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "review/repetitions/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "review/repetitions/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "review/shortcuts/", "text": "a.md-footer__link--next[aria-label^=\"Next:\"], .md-nav__icon { display: none !important; } OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "review/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "review/tags/", "text": "Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Tags"}, {"location": "review/tags/#tags", "text": "", "title": "Tags"}, {"location": "review/tags/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "review/tags/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "review/tags/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "sp-guides/", "text": "Hello world \u00b6", "title": "Hello world"}, {"location": "sp-guides/#hello-world", "text": "", "title": "Hello world"}, {"location": "sp-guides/tec-cb-ome-adp/", "text": "Adaptation \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to enable you to perform your task. Quick walkthrough \u00b6 Download the package for adaptation and the Excel document from the portal Import the OMT package in OmegaT as described in the section The OmegaT project for adaptation will open: If you're borrowing another translation, all segments will probably appear translated in the Editor pane (the main pane of OmegaT, which contains the source text and the translation). If you are adapting from a base version (your target version is a variation of the source version), you might find it useful to automatically insert the source text in every segment . You can distinguish trend segments from non-trend segments thanks to a color coding: trend segments appear highlighted in orange. For more information about navigation between segments, please refer to the section of this user guide. If you adapt any recurring term or recurring instructions in a file, please make sure that the adaptation is done consistently. You can perform a concordance search on a specific term or phrase and OmegaT will display all segments containing it. You can go through the results to make sure that everything has been adapted consistently. For more information about concordance searches, please check the section Concordance search Installation and setup \u00b6 To install OmegaT on a computer running on Windows, please consult the . Accessing the package \u00b6 Accessing the package for the first time \u00b6 The following steps need to be performed only once per OmegaT package : when you access each package for the first time: Download the from the portal Store the in a location you will remember on your computer. Import the in OmegaT: Open OmegaT Go to Project>Import OMT package Navigate to the location where you stored the OMT package. Choose the and click on Open A pop up opens. Click Yes . Translate/Reconcile/Adapt/Review the files in the package. When you are done working for the day, close OmegaT. Access the package after import \u00b6 The next times you want to access the project in OmegaT, go to Project>Open Recent Project . The project you were working on is the first one in the list: Navigation \u00b6 Navigation between the different panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane . The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show you if a repeated segment was translated differently. Navigation between the different files \u00b6 If the project contains multiple files, they are listed in the Project Files pane . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files pane. You can also see the name of the file that is open in the Editor pane's title bar. Navigation between the different segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working in. When a translation is inserted, it will appear below the source text. Press the Enter key on your keyboard to go to the next segment. A segment can also be activated by double clicking on it. It then becomes green. In OmegaT, a color code will help you find your way around between the different segments: Green = the segment you are working in (active segment) Grey = translated segment. The translation is displayed below the source text. Orange = pretranslated and locked segment (e.g. trend). If you want to make a change to a trend segment, document it in the monitoring document but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. All segments should appear translated in a project for adaptation either in gray or in orange (trend) and the translation should be displayed below the source. If you notice an untranslated segment in * *, please provide a translation and document it in the monitoring document. Handling tags ( Ctrl + T ) \u00b6 Recognizing tags \u00b6 If you are in a segment which contains tags, you will recognize them because they are in red font . There are two types of tags - standalone tags and double tags: Standalone tags = a single tag with a precise role (e.g. tag which introduces a new paragraph in HTML) Double tags are composed of an opening and a closing tag, such as the HTML tags for making text bold, italic, underlined, etc. Double tags affect the text between them and you need to ensure they are positioned around the exact same words in the source and in the translation. Fixing tag issues \u00b6 For your language task, all tags should be present in the translation. What is important is to correct potential errors that you may see. In the screenshot below, in the source segment the **** are around the letter \"n\" while in the target they are around the word \"which\" . To correct this issue, you would have to perform the following steps: double click on the first incorrectly inserted tag in the target segment to select it and press Backspace on your keyboard to delete it repeat the operation until you deleted all incorrectly inserted tags place your mouse where the first tag should be correctly inserted and press Ctrl + T on your keyboard to insert the first tag insert all other missing tags. Please note that tags are inserted in the order of their appearance in the source segment. Most common HTML tags \u00b6 Below you will find the most common HTML tags you may encounter. Using Fuzzy matches ( Ctrl + I ) \u00b6 Any changes you make during adaptation are saved in the translation memory of the project. When you activate a segment which is similar to one you have already adapted, you may see suggestions in the fuzzy matches pane. The source in the fuzzy matches pane shows the difference between the active segment and the previous translation in \u201ctrack changes\u201d mode like in Word: Parts that do not appear in the active segment are in ~~~~ Parts that are added are in ____ Do not hesitate to consult the fuzzy matches pane to ensure you make the same changes consistently throughout. You can insert a fuzzy match or a part of a fuzzy match with Ctrl + I : Activate the fuzzy match you wish to use by double clicking on it. With your mouse, select the part you wish to insert. Press Ctrl + I on your keyboard to insert it. Do not forget to delete all unnecessary/remaining text from the target segment to ensure everything is correct. Using the Glossary \u00b6 OmegaT supports glossaries. Your package may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Inserting glossary terms \u00b6 When you arrive in an active segment which contains a glossary term, the respective term is underlined in blue in the source segment. You will see the suggested target term in the Glossary pane , on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding terms to the glossary \u00b6 If in the project you are working on you keep adapting the same term over and over you may wish to add it to the glossary to ensure you adapt consistently throughout. In the active segment,** select the term** you want to insert with your mouse Right click and choose Add glossary entry from the contextual menu A pop-up window will open Enter the Target term and press the OK button. Handling repeated segments \u00b6 Some segments are identical to each other. They are called \u201c repeated segments \u201d and their translation is autopropagated . Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because it has gray font. When a repeated segment is active, the segment number will indicate how many repetitions exist: If you right click on a repeated segment, the contextual menu will point out the other occurrences of a repeated segment. It can be useful to jump to them (by selecting them from the contextual menu) to see the different contexts in which a repeated segment appears. Autopropagation \u00b6 If you edit the translation of a repeated segment, by default, the changes will be automatically reflected in all the repetitions. This happens in the same file, but also in all the files of the OmegaT package. Create alternative translation \u00b6 In some cases, you may not wish to modify the translation of all repeated segments. Due to a different context, you may need to change only ONE of the repeated segments: Right click on the segment Choose Create Alternative Translation from the contextual menu Change the translation of your active segment and then either press Ctrl + S or move to the next one. If you return on the repeated segment, you will see the different translations appear in the Multiple Translations pane. Other useful features \u00b6 Using the character table \u00b6 Special characters can be inserted with the Special Characters Table. Special characters can be: quotation marks: \u00ab\u00bb, \u201e\u201c, \u2018\u2019, etc. mathematical symbols: \u00d7, \u03c0, \u00f7, \u2264, \u2260, \u221a, etc. other characters: \u00ae, \u2122 When you arrive in a segment in which you need to insert a special character, perform the following steps: Press Ctrl + Space on your keyboard several times until you reach the special characters table. Select the character you want to insert Press Enter and continue editing your segment. Inserting non-breaking spaces \u00b6 In order to insert non-breaking spaces in OmegaT, please make sure you have installed Auto Hot Key . If you haven't installed it yet, please check the Third Party Tools section of the OmegaT Installation guide Once Auto Hot Key is installed, you can insert non-breaking spaces with the same keyboard shortcut as in Word: Ctrl + Shift + Space . You can recognize a non breaking space because it is gray. Performing concordance searches \u00b6 A concordance search allows you to look for words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word you want to search for with your mouse. Press Ctrl + F on your keyboard. The Search window will open. Press Search. The results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the target translation at the right place. TIP: There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting. Performing QA checks in OmegaT \u00b6 Completion check \u00b6 All segments of the OmegaT package must have a translation. To ensure that is the case, please check for completion prior to delivery: Go to Project>Project Files The project files pane will open OK: If the Number of unique segments is equal to the number of Translated unique segments . NOT OK : the Number of unique segments is different from the number of Translated unique segments . To correct: Close the Project Files Pane Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . When the cursor stops moving from the active segment then all segments have a translation. Recheck for completion, to make sure by opening the Project Files pane. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools>Check Issues . A pop up window will open. By default, other types of checks (Spelling, Terminology, LanguageTool) are ticked. If you want to check for issues related to tags before performing the rest of the checks, you can untick them. You will notice that the Tag Issues box cannot be unticked. Press OK . An error report will open. Go through the issues one by one: Correct the issue by clicking on Jump to Segment . You will arrive at the appropriate segment in the editor pane. Place your cursor where the missing tag needs to be inserted and press Ctrl + T to insert the missing tag. Press Enter to move to the next segment. Open the Error report again. It has automatically refreshed. Finish going through the issues. TIP : If in the source there are tags that you do not use in your language which are present in the source segment, to avoid having false positives in the error report, you can insert them at the end of the segment. They would not have an impact on any text. Caution Please do not click on \"Apply fix\", fix each issue manually. Glossary adherence check \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools>Check Issues Make sure the box next to Terminology Issues is ticked Press** OK.** An error report will open Go through the issues one by one and jump to segment to correct the eventual error if needed. Creating target files \u00b6 Press Ctrl + Shift + D to create the target file you were working on. This will allow you to preview the translated file with your changes. To access the file, go to Project>Access Project Contents>Target Files . A window with the contents of the \"target\" folder will open. Find the file you were working on, if there are several files and preview it to read the translation in context. Delivering the project \u00b6 Once you have finished editing the OmegaT package and have performed the appropriate Q&A checks, you need to Export the . Go to Project>Export OMT Package A pop up window will open. Click Save Press OK in the Pop-up window notifying that the package was successfully created. You will be automatically directed to the location the exported package is stored. You will recognize the package because it has the extension OMT. It should be the 4th from the bottom. This is the file you have to deliver. OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Adaptation"}, {"location": "sp-guides/tec-cb-ome-adp/#adaptation", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to enable you to perform your task.", "title": "Adaptation"}, {"location": "sp-guides/tec-cb-ome-adp/#quick-walkthrough", "text": "Download the package for adaptation and the Excel document from the portal Import the OMT package in OmegaT as described in the section The OmegaT project for adaptation will open: If you're borrowing another translation, all segments will probably appear translated in the Editor pane (the main pane of OmegaT, which contains the source text and the translation). If you are adapting from a base version (your target version is a variation of the source version), you might find it useful to automatically insert the source text in every segment . You can distinguish trend segments from non-trend segments thanks to a color coding: trend segments appear highlighted in orange. For more information about navigation between segments, please refer to the section of this user guide. If you adapt any recurring term or recurring instructions in a file, please make sure that the adaptation is done consistently. You can perform a concordance search on a specific term or phrase and OmegaT will display all segments containing it. You can go through the results to make sure that everything has been adapted consistently. For more information about concordance searches, please check the section Concordance search", "title": "Quick walkthrough"}, {"location": "sp-guides/tec-cb-ome-adp/#installation-and-setup", "text": "To install OmegaT on a computer running on Windows, please consult the .", "title": "Installation and setup"}, {"location": "sp-guides/tec-cb-ome-adp/#accessing-the-package", "text": "", "title": "Accessing the package"}, {"location": "sp-guides/tec-cb-ome-adp/#accessing-the-package-for-the-first-time", "text": "The following steps need to be performed only once per OmegaT package : when you access each package for the first time: Download the from the portal Store the in a location you will remember on your computer. Import the in OmegaT: Open OmegaT Go to Project>Import OMT package Navigate to the location where you stored the OMT package. Choose the and click on Open A pop up opens. Click Yes . Translate/Reconcile/Adapt/Review the files in the package. When you are done working for the day, close OmegaT.", "title": "Accessing the package for the first time"}, {"location": "sp-guides/tec-cb-ome-adp/#access-the-package-after-import", "text": "The next times you want to access the project in OmegaT, go to Project>Open Recent Project . The project you were working on is the first one in the list:", "title": "Access the package after import"}, {"location": "sp-guides/tec-cb-ome-adp/#navigation", "text": "", "title": "Navigation"}, {"location": "sp-guides/tec-cb-ome-adp/#navigation-between-the-different-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane . The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show you if a repeated segment was translated differently.", "title": "Navigation between the different panes"}, {"location": "sp-guides/tec-cb-ome-adp/#navigation-between-the-different-files", "text": "If the project contains multiple files, they are listed in the Project Files pane . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files pane. You can also see the name of the file that is open in the Editor pane's title bar.", "title": "Navigation between the different files"}, {"location": "sp-guides/tec-cb-ome-adp/#navigation-between-the-different-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working in. When a translation is inserted, it will appear below the source text. Press the Enter key on your keyboard to go to the next segment. A segment can also be activated by double clicking on it. It then becomes green. In OmegaT, a color code will help you find your way around between the different segments: Green = the segment you are working in (active segment) Grey = translated segment. The translation is displayed below the source text. Orange = pretranslated and locked segment (e.g. trend). If you want to make a change to a trend segment, document it in the monitoring document but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. All segments should appear translated in a project for adaptation either in gray or in orange (trend) and the translation should be displayed below the source. If you notice an untranslated segment in * *, please provide a translation and document it in the monitoring document.", "title": "Navigation between the different segments"}, {"location": "sp-guides/tec-cb-ome-adp/#handling-tags-ctrlt", "text": "", "title": "Handling tags (Ctrl+T)"}, {"location": "sp-guides/tec-cb-ome-adp/#recognizing-tags", "text": "If you are in a segment which contains tags, you will recognize them because they are in red font . There are two types of tags - standalone tags and double tags: Standalone tags = a single tag with a precise role (e.g. tag which introduces a new paragraph in HTML) Double tags are composed of an opening and a closing tag, such as the HTML tags for making text bold, italic, underlined, etc. Double tags affect the text between them and you need to ensure they are positioned around the exact same words in the source and in the translation.", "title": "Recognizing tags"}, {"location": "sp-guides/tec-cb-ome-adp/#fixing-tag-issues", "text": "For your language task, all tags should be present in the translation. What is important is to correct potential errors that you may see. In the screenshot below, in the source segment the **** are around the letter \"n\" while in the target they are around the word \"which\" . To correct this issue, you would have to perform the following steps: double click on the first incorrectly inserted tag in the target segment to select it and press Backspace on your keyboard to delete it repeat the operation until you deleted all incorrectly inserted tags place your mouse where the first tag should be correctly inserted and press Ctrl + T on your keyboard to insert the first tag insert all other missing tags. Please note that tags are inserted in the order of their appearance in the source segment.", "title": "Fixing tag issues"}, {"location": "sp-guides/tec-cb-ome-adp/#most-common-html-tags", "text": "Below you will find the most common HTML tags you may encounter.", "title": "Most common HTML tags"}, {"location": "sp-guides/tec-cb-ome-adp/#using-fuzzy-matches-ctrli", "text": "Any changes you make during adaptation are saved in the translation memory of the project. When you activate a segment which is similar to one you have already adapted, you may see suggestions in the fuzzy matches pane. The source in the fuzzy matches pane shows the difference between the active segment and the previous translation in \u201ctrack changes\u201d mode like in Word: Parts that do not appear in the active segment are in ~~~~ Parts that are added are in ____ Do not hesitate to consult the fuzzy matches pane to ensure you make the same changes consistently throughout. You can insert a fuzzy match or a part of a fuzzy match with Ctrl + I : Activate the fuzzy match you wish to use by double clicking on it. With your mouse, select the part you wish to insert. Press Ctrl + I on your keyboard to insert it. Do not forget to delete all unnecessary/remaining text from the target segment to ensure everything is correct.", "title": "Using Fuzzy matches (Ctrl+I)"}, {"location": "sp-guides/tec-cb-ome-adp/#using-the-glossary", "text": "OmegaT supports glossaries. Your package may already contain a glossary with key terms, but you can also add terms to the glossary yourself.", "title": "Using the Glossary"}, {"location": "sp-guides/tec-cb-ome-adp/#inserting-glossary-terms", "text": "When you arrive in an active segment which contains a glossary term, the respective term is underlined in blue in the source segment. You will see the suggested target term in the Glossary pane , on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting glossary terms"}, {"location": "sp-guides/tec-cb-ome-adp/#adding-terms-to-the-glossary", "text": "If in the project you are working on you keep adapting the same term over and over you may wish to add it to the glossary to ensure you adapt consistently throughout. In the active segment,** select the term** you want to insert with your mouse Right click and choose Add glossary entry from the contextual menu A pop-up window will open Enter the Target term and press the OK button.", "title": "Adding terms to the glossary"}, {"location": "sp-guides/tec-cb-ome-adp/#handling-repeated-segments", "text": "Some segments are identical to each other. They are called \u201c repeated segments \u201d and their translation is autopropagated .", "title": "Handling repeated segments"}, {"location": "sp-guides/tec-cb-ome-adp/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because it has gray font. When a repeated segment is active, the segment number will indicate how many repetitions exist: If you right click on a repeated segment, the contextual menu will point out the other occurrences of a repeated segment. It can be useful to jump to them (by selecting them from the contextual menu) to see the different contexts in which a repeated segment appears.", "title": "Identifying repeated segments"}, {"location": "sp-guides/tec-cb-ome-adp/#autopropagation", "text": "If you edit the translation of a repeated segment, by default, the changes will be automatically reflected in all the repetitions. This happens in the same file, but also in all the files of the OmegaT package.", "title": "Autopropagation"}, {"location": "sp-guides/tec-cb-ome-adp/#create-alternative-translation", "text": "In some cases, you may not wish to modify the translation of all repeated segments. Due to a different context, you may need to change only ONE of the repeated segments: Right click on the segment Choose Create Alternative Translation from the contextual menu Change the translation of your active segment and then either press Ctrl + S or move to the next one. If you return on the repeated segment, you will see the different translations appear in the Multiple Translations pane.", "title": "Create alternative translation"}, {"location": "sp-guides/tec-cb-ome-adp/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "sp-guides/tec-cb-ome-adp/#using-the-character-table", "text": "Special characters can be inserted with the Special Characters Table. Special characters can be: quotation marks: \u00ab\u00bb, \u201e\u201c, \u2018\u2019, etc. mathematical symbols: \u00d7, \u03c0, \u00f7, \u2264, \u2260, \u221a, etc. other characters: \u00ae, \u2122 When you arrive in a segment in which you need to insert a special character, perform the following steps: Press Ctrl + Space on your keyboard several times until you reach the special characters table. Select the character you want to insert Press Enter and continue editing your segment.", "title": "Using the character table"}, {"location": "sp-guides/tec-cb-ome-adp/#inserting-non-breaking-spaces", "text": "In order to insert non-breaking spaces in OmegaT, please make sure you have installed Auto Hot Key . If you haven't installed it yet, please check the Third Party Tools section of the OmegaT Installation guide Once Auto Hot Key is installed, you can insert non-breaking spaces with the same keyboard shortcut as in Word: Ctrl + Shift + Space . You can recognize a non breaking space because it is gray.", "title": "Inserting non-breaking spaces"}, {"location": "sp-guides/tec-cb-ome-adp/#performing-concordance-searches", "text": "A concordance search allows you to look for words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word you want to search for with your mouse. Press Ctrl + F on your keyboard. The Search window will open. Press Search. The results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the target translation at the right place. TIP: There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Performing concordance searches"}, {"location": "sp-guides/tec-cb-ome-adp/#performing-qa-checks-in-omegat", "text": "", "title": "Performing QA checks in OmegaT"}, {"location": "sp-guides/tec-cb-ome-adp/#completion-check", "text": "All segments of the OmegaT package must have a translation. To ensure that is the case, please check for completion prior to delivery: Go to Project>Project Files The project files pane will open OK: If the Number of unique segments is equal to the number of Translated unique segments . NOT OK : the Number of unique segments is different from the number of Translated unique segments . To correct: Close the Project Files Pane Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . When the cursor stops moving from the active segment then all segments have a translation. Recheck for completion, to make sure by opening the Project Files pane.", "title": "Completion check"}, {"location": "sp-guides/tec-cb-ome-adp/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools>Check Issues . A pop up window will open. By default, other types of checks (Spelling, Terminology, LanguageTool) are ticked. If you want to check for issues related to tags before performing the rest of the checks, you can untick them. You will notice that the Tag Issues box cannot be unticked. Press OK . An error report will open. Go through the issues one by one: Correct the issue by clicking on Jump to Segment . You will arrive at the appropriate segment in the editor pane. Place your cursor where the missing tag needs to be inserted and press Ctrl + T to insert the missing tag. Press Enter to move to the next segment. Open the Error report again. It has automatically refreshed. Finish going through the issues. TIP : If in the source there are tags that you do not use in your language which are present in the source segment, to avoid having false positives in the error report, you can insert them at the end of the segment. They would not have an impact on any text. Caution Please do not click on \"Apply fix\", fix each issue manually.", "title": "Check and fix tags"}, {"location": "sp-guides/tec-cb-ome-adp/#glossary-adherence-check", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools>Check Issues Make sure the box next to Terminology Issues is ticked Press** OK.** An error report will open Go through the issues one by one and jump to segment to correct the eventual error if needed.", "title": "Glossary adherence check"}, {"location": "sp-guides/tec-cb-ome-adp/#creating-target-files", "text": "Press Ctrl + Shift + D to create the target file you were working on. This will allow you to preview the translated file with your changes. To access the file, go to Project>Access Project Contents>Target Files . A window with the contents of the \"target\" folder will open. Find the file you were working on, if there are several files and preview it to read the translation in context.", "title": "Creating target files"}, {"location": "sp-guides/tec-cb-ome-adp/#delivering-the-project", "text": "Once you have finished editing the OmegaT package and have performed the appropriate Q&A checks, you need to Export the . Go to Project>Export OMT Package A pop up window will open. Click Save Press OK in the Pop-up window notifying that the package was successfully created. You will be automatically directed to the location the exported package is stored. You will recognize the package because it has the extension OMT. It should be the 4th from the bottom. This is the file you have to deliver.", "title": "Delivering the project"}, {"location": "sp-guides/tec-cb-ome-adp/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "sp-guides/tec-cb-ome-prf/", "text": "Proofreading \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to enable you to perform your task. Quick walkthrough for proofreading \u00b6 Download the OMT package and the Excel file containing the translation and adaptation guidelines from Plunet. Import the OMT package in OmegaT. To see how to do so, please read the section Accessing the package for the first time . Create the target files for preview on the portal. To see how to create the files, please refer to the section Creating target files Connect to the PISA portal with the credentials provided in the dispatch mail: PISA PORTAL Go to the Translations TAB Drag and drop the target XLIFF you wish to preview and press the Preview chosen XLIFF Button The XLIFF for preview in your language opens. You can also preview the source text by clicking on Preview eng-ZZZ button Read the items in your language on the portal. Focus on the following: Fluency Grammar & Typos Punctuation To navigate from one screen to the other and read through the full item press the \"Next\" arrows on the screen If you notice something you wish to correct, copy the sentence/part of the sentence in your language from the preview In OmegaT, press Ctrl + F on your keyboard. The search dialog opens. Paste the sentence/part of sentence you copied from the portal and press the Search button. Double click on the result to go to the appropriate segment in OmegaT. In the screenshot below, the segment number is 40 Before you make any changes, double check in the Excel file if there is no guideline for that segment, or if there is no comment from the reconciler. The changes you make cannot contradict a guideline or the reconciler's decision. If you are in a case where you believe something should be changed and it goes against the guidelines, please send us an e-mail to explain the situation. Repeat this process for all files in your batch. When you are done, create the target OMT package for delivery Delivering the project and upload it on Plunet together with the Excel for documentation. Accessing the package \u00b6 Accessing the package for the first time \u00b6 The following steps need to be performed only once per OmegaT package : when you access each package for the first time: Download the from the portal Store the in a location you will remember on your computer. Import the in OmegaT: Open OmegaT Go to Project>Import OMT package Navigate to the location where you stored the OMT package. Choose the and click on Open A pop up opens. Click Yes . Translate/Reconcile/Adapt/Review the files in the package. When you are done working for the day, close OmegaT. Access the package after import \u00b6 The next times you want to access the project in OmegaT, go to Project>Open Recent Project . The project you were working on is the first one in the list: Navigation \u00b6 Navigation between the different panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane . The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show you if a repeated segment was translated differently. Navigation between the different files \u00b6 If the project contains multiple files, they are listed in the Project Files pane . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files pane. You can also see the name of the file that is open in the Editor pane's title bar. Navigation between the different segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working in. The translation is displayed right below the source text. Press the Enter key on your keyboard to go to the next segment. A segment can also be activated by double clicking on it. It then becomes green. In OmegaT, a color code will help you find your way around between the different segments: Green = the segment you are working in (active segment) Grey = translated segment. The translation is displayed below the source text. Orange = pretranslated and locked segment (e.g. trend). These segments cannot be edited in OmegaT. All segments should appear translated in a project for proofreading. If you notice an untranslated segment in * *, please contact cApStAn's project managers to see how it should be handled. Recognizing tags \u00b6 If you are in a segment which contains tags, you will recognize them because they are in red font . There are two types of tags - standalone tags and double tags: Standalone tags = a single tag with a precise role (e.g. tag which introduces a new paragraph in HTML) Double tags are composed of an opening and a closing tag, such as the HTML tags for making text bold, italic, underlined, etc. Double tags affect the text between them and you need to ensure they are positioned around the exact same words in the source and in the translation. Fixing tag issues \u00b6 For your language task, all tags should be present in the translation. What is important is to correct potential errors that you may see. In the screenshot below, in the source segment the **** are around the letter \"n\" while in the target they are around the word \"which\" . To correct this issue, you would have to perform the following steps: double click on the first incorrectly inserted tag in the target segment to select it and press Backspace on your keyboard to delete it repeat the operation until you deleted all incorrectly inserted tags place your mouse where the first tag should be correctly inserted and press Ctrl + T on your keyboard to insert the first tag insert all other missing tags. Please note that tags are inserted in the order of their appearance in the source segment. Handling repeated segments \u00b6 Some segments are identical to each other. They are called \u201c repeated segments \u201d and their translation is autopropagated . Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because it has gray font. When a repeated segment is active, the segment number will indicate how many repetitions exist: If you right click on a repeated segment, the contextual menu will point out the other occurrences of a repeated segment. It can be useful to jump to them (by selecting them from the contextual menu) to see the different contexts in which a repeated segment appears. Autopropagation \u00b6 If you edit the translation of a repeated segment, by default, the changes will be automatically reflected in all the repetitions. This happens in the same file, but also in all the files of the OmegaT package. Create alternative translation \u00b6 In some cases, you may not wish to modify the translation of all repeated segments. Due to a different context, you may need to change only ONE of the repeated segments: Right click on the segment Choose Create Alternative Translation from the contextual menu Change the translation of your active segment and then either press Ctrl + S or move to the next one. If you return on the repeated segment, you will see the different translations appear in the Multiple Translations pane. Other useful features \u00b6 Using the character table \u00b6 Special characters can be inserted with the Special Characters Table. Special characters can be: quotation marks: \u00ab\u00bb, \u201e\u201c, \u2018\u2019, etc. mathematical symbols: \u00d7, \u03c0, \u00f7, \u2264, \u2260, \u221a, etc. other characters: \u00ae, \u2122 When you arrive in a segment in which you need to insert a special character, perform the following steps: Press Ctrl + Space on your keyboard several times until you reach the special characters table. Select the character you want to insert Press Enter and continue editing your segment. Inserting non-breaking spaces \u00b6 In order to insert non-breaking spaces in OmegaT, please make sure you have installed Auto Hot Key . If you haven't installed it yet, please check the Third Party Tools section of the OmegaT Installation guide Once Auto Hot Key is installed, you can insert non-breaking spaces with the same keyboard shortcut as in Word: Ctrl + Shift + Space . You can recognize a non breaking space because it is gray. Performing concordance searches \u00b6 A concordance search allows you to look for words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word you want to search for with your mouse. Press Ctrl + F on your keyboard. The Search window will open. Press Search. The results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the target translation at the right place. TIP: There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting. Performing QA checks in OmegaT \u00b6 Completion check \u00b6 All segments of the OmegaT package must have a translation. To ensure that is the case, please check for completion prior to delivery: Go to Project>Project Files The project files pane will open OK: If the Number of unique segments is equal to the number of Translated unique segments . NOT OK : the Number of unique segments is different from the number of Translated unique segments . To correct: Close the Project Files Pane Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . When the cursor stops moving from the active segment then all segments have a translation. Recheck for completion, to make sure by opening the Project Files pane. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools>Check Issues . A pop up window will open. By default, other types of checks (Spelling, Terminology, LanguageTool) are ticked. If you want to check for issues related to tags before performing the rest of the checks, you can untick them. You will notice that the Tag Issues box cannot be unticked. Press OK . An error report will open. Go through the issues one by one: Correct the issue by clicking on Jump to Segment . You will arrive at the appropriate segment in the editor pane. Place your cursor where the missing tag needs to be inserted and press Ctrl + T to insert the missing tag. Press Enter to move to the next segment. Open the Error report again. It has automatically refreshed. Finish going through the issues. TIP : If in the source there are tags that you do not use in your language which are present in the source segment, to avoid having false positives in the error report, you can insert them at the end of the segment. They would not have an impact on any text. Caution Please do not click on \"Apply fix\", fix each issue manually. Creating target files \u00b6 Press Ctrl + Shift + D to create the target file you were working on. This will allow you to preview the translated file with your changes. To access the file, go to Project>Access Project Contents>Target Files . A window with the contents of the \"target\" folder will open. Find the file you were working on, if there are several files and preview it to read the translation in context. Delivering the project \u00b6 Once you have finished editing the OmegaT package and have performed the appropriate Q&A checks, you need to Export the . Go to Project>Export OMT Package A pop up window will open. Click Save Press OK in the Pop-up window notifying that the package was successfully created. You will be automatically directed to the location the exported package is stored. You will recognize the package because it has the extension OMT. It should be the 4th from the bottom. This is the file you have to deliver. OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Proofreading"}, {"location": "sp-guides/tec-cb-ome-prf/#proofreading", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to enable you to perform your task.", "title": "Proofreading"}, {"location": "sp-guides/tec-cb-ome-prf/#quick-walkthrough-for-proofreading", "text": "Download the OMT package and the Excel file containing the translation and adaptation guidelines from Plunet. Import the OMT package in OmegaT. To see how to do so, please read the section Accessing the package for the first time . Create the target files for preview on the portal. To see how to create the files, please refer to the section Creating target files Connect to the PISA portal with the credentials provided in the dispatch mail: PISA PORTAL Go to the Translations TAB Drag and drop the target XLIFF you wish to preview and press the Preview chosen XLIFF Button The XLIFF for preview in your language opens. You can also preview the source text by clicking on Preview eng-ZZZ button Read the items in your language on the portal. Focus on the following: Fluency Grammar & Typos Punctuation To navigate from one screen to the other and read through the full item press the \"Next\" arrows on the screen If you notice something you wish to correct, copy the sentence/part of the sentence in your language from the preview In OmegaT, press Ctrl + F on your keyboard. The search dialog opens. Paste the sentence/part of sentence you copied from the portal and press the Search button. Double click on the result to go to the appropriate segment in OmegaT. In the screenshot below, the segment number is 40 Before you make any changes, double check in the Excel file if there is no guideline for that segment, or if there is no comment from the reconciler. The changes you make cannot contradict a guideline or the reconciler's decision. If you are in a case where you believe something should be changed and it goes against the guidelines, please send us an e-mail to explain the situation. Repeat this process for all files in your batch. When you are done, create the target OMT package for delivery Delivering the project and upload it on Plunet together with the Excel for documentation.", "title": "Quick walkthrough for proofreading"}, {"location": "sp-guides/tec-cb-ome-prf/#accessing-the-package", "text": "", "title": "Accessing the package"}, {"location": "sp-guides/tec-cb-ome-prf/#accessing-the-package-for-the-first-time", "text": "The following steps need to be performed only once per OmegaT package : when you access each package for the first time: Download the from the portal Store the in a location you will remember on your computer. Import the in OmegaT: Open OmegaT Go to Project>Import OMT package Navigate to the location where you stored the OMT package. Choose the and click on Open A pop up opens. Click Yes . Translate/Reconcile/Adapt/Review the files in the package. When you are done working for the day, close OmegaT.", "title": "Accessing the package for the first time"}, {"location": "sp-guides/tec-cb-ome-prf/#access-the-package-after-import", "text": "The next times you want to access the project in OmegaT, go to Project>Open Recent Project . The project you were working on is the first one in the list:", "title": "Access the package after import"}, {"location": "sp-guides/tec-cb-ome-prf/#navigation", "text": "", "title": "Navigation"}, {"location": "sp-guides/tec-cb-ome-prf/#navigation-between-the-different-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane . The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show you if a repeated segment was translated differently.", "title": "Navigation between the different panes"}, {"location": "sp-guides/tec-cb-ome-prf/#navigation-between-the-different-files", "text": "If the project contains multiple files, they are listed in the Project Files pane . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files pane. You can also see the name of the file that is open in the Editor pane's title bar.", "title": "Navigation between the different files"}, {"location": "sp-guides/tec-cb-ome-prf/#navigation-between-the-different-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working in. The translation is displayed right below the source text. Press the Enter key on your keyboard to go to the next segment. A segment can also be activated by double clicking on it. It then becomes green. In OmegaT, a color code will help you find your way around between the different segments: Green = the segment you are working in (active segment) Grey = translated segment. The translation is displayed below the source text. Orange = pretranslated and locked segment (e.g. trend). These segments cannot be edited in OmegaT. All segments should appear translated in a project for proofreading. If you notice an untranslated segment in * *, please contact cApStAn's project managers to see how it should be handled.", "title": "Navigation between the different segments"}, {"location": "sp-guides/tec-cb-ome-prf/#recognizing-tags", "text": "If you are in a segment which contains tags, you will recognize them because they are in red font . There are two types of tags - standalone tags and double tags: Standalone tags = a single tag with a precise role (e.g. tag which introduces a new paragraph in HTML) Double tags are composed of an opening and a closing tag, such as the HTML tags for making text bold, italic, underlined, etc. Double tags affect the text between them and you need to ensure they are positioned around the exact same words in the source and in the translation.", "title": "Recognizing tags"}, {"location": "sp-guides/tec-cb-ome-prf/#fixing-tag-issues", "text": "For your language task, all tags should be present in the translation. What is important is to correct potential errors that you may see. In the screenshot below, in the source segment the **** are around the letter \"n\" while in the target they are around the word \"which\" . To correct this issue, you would have to perform the following steps: double click on the first incorrectly inserted tag in the target segment to select it and press Backspace on your keyboard to delete it repeat the operation until you deleted all incorrectly inserted tags place your mouse where the first tag should be correctly inserted and press Ctrl + T on your keyboard to insert the first tag insert all other missing tags. Please note that tags are inserted in the order of their appearance in the source segment.", "title": "Fixing tag issues"}, {"location": "sp-guides/tec-cb-ome-prf/#handling-repeated-segments", "text": "Some segments are identical to each other. They are called \u201c repeated segments \u201d and their translation is autopropagated .", "title": "Handling repeated segments"}, {"location": "sp-guides/tec-cb-ome-prf/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because it has gray font. When a repeated segment is active, the segment number will indicate how many repetitions exist: If you right click on a repeated segment, the contextual menu will point out the other occurrences of a repeated segment. It can be useful to jump to them (by selecting them from the contextual menu) to see the different contexts in which a repeated segment appears.", "title": "Identifying repeated segments"}, {"location": "sp-guides/tec-cb-ome-prf/#autopropagation", "text": "If you edit the translation of a repeated segment, by default, the changes will be automatically reflected in all the repetitions. This happens in the same file, but also in all the files of the OmegaT package.", "title": "Autopropagation"}, {"location": "sp-guides/tec-cb-ome-prf/#create-alternative-translation", "text": "In some cases, you may not wish to modify the translation of all repeated segments. Due to a different context, you may need to change only ONE of the repeated segments: Right click on the segment Choose Create Alternative Translation from the contextual menu Change the translation of your active segment and then either press Ctrl + S or move to the next one. If you return on the repeated segment, you will see the different translations appear in the Multiple Translations pane.", "title": "Create alternative translation"}, {"location": "sp-guides/tec-cb-ome-prf/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "sp-guides/tec-cb-ome-prf/#using-the-character-table", "text": "Special characters can be inserted with the Special Characters Table. Special characters can be: quotation marks: \u00ab\u00bb, \u201e\u201c, \u2018\u2019, etc. mathematical symbols: \u00d7, \u03c0, \u00f7, \u2264, \u2260, \u221a, etc. other characters: \u00ae, \u2122 When you arrive in a segment in which you need to insert a special character, perform the following steps: Press Ctrl + Space on your keyboard several times until you reach the special characters table. Select the character you want to insert Press Enter and continue editing your segment.", "title": "Using the character table"}, {"location": "sp-guides/tec-cb-ome-prf/#inserting-non-breaking-spaces", "text": "In order to insert non-breaking spaces in OmegaT, please make sure you have installed Auto Hot Key . If you haven't installed it yet, please check the Third Party Tools section of the OmegaT Installation guide Once Auto Hot Key is installed, you can insert non-breaking spaces with the same keyboard shortcut as in Word: Ctrl + Shift + Space . You can recognize a non breaking space because it is gray.", "title": "Inserting non-breaking spaces"}, {"location": "sp-guides/tec-cb-ome-prf/#performing-concordance-searches", "text": "A concordance search allows you to look for words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word you want to search for with your mouse. Press Ctrl + F on your keyboard. The Search window will open. Press Search. The results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the target translation at the right place. TIP: There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Performing concordance searches"}, {"location": "sp-guides/tec-cb-ome-prf/#performing-qa-checks-in-omegat", "text": "", "title": "Performing QA checks in OmegaT"}, {"location": "sp-guides/tec-cb-ome-prf/#completion-check", "text": "All segments of the OmegaT package must have a translation. To ensure that is the case, please check for completion prior to delivery: Go to Project>Project Files The project files pane will open OK: If the Number of unique segments is equal to the number of Translated unique segments . NOT OK : the Number of unique segments is different from the number of Translated unique segments . To correct: Close the Project Files Pane Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . When the cursor stops moving from the active segment then all segments have a translation. Recheck for completion, to make sure by opening the Project Files pane.", "title": "Completion check"}, {"location": "sp-guides/tec-cb-ome-prf/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools>Check Issues . A pop up window will open. By default, other types of checks (Spelling, Terminology, LanguageTool) are ticked. If you want to check for issues related to tags before performing the rest of the checks, you can untick them. You will notice that the Tag Issues box cannot be unticked. Press OK . An error report will open. Go through the issues one by one: Correct the issue by clicking on Jump to Segment . You will arrive at the appropriate segment in the editor pane. Place your cursor where the missing tag needs to be inserted and press Ctrl + T to insert the missing tag. Press Enter to move to the next segment. Open the Error report again. It has automatically refreshed. Finish going through the issues. TIP : If in the source there are tags that you do not use in your language which are present in the source segment, to avoid having false positives in the error report, you can insert them at the end of the segment. They would not have an impact on any text. Caution Please do not click on \"Apply fix\", fix each issue manually.", "title": "Check and fix tags"}, {"location": "sp-guides/tec-cb-ome-prf/#creating-target-files", "text": "Press Ctrl + Shift + D to create the target file you were working on. This will allow you to preview the translated file with your changes. To access the file, go to Project>Access Project Contents>Target Files . A window with the contents of the \"target\" folder will open. Find the file you were working on, if there are several files and preview it to read the translation in context.", "title": "Creating target files"}, {"location": "sp-guides/tec-cb-ome-prf/#delivering-the-project", "text": "Once you have finished editing the OmegaT package and have performed the appropriate Q&A checks, you need to Export the . Go to Project>Export OMT Package A pop up window will open. Click Save Press OK in the Pop-up window notifying that the package was successfully created. You will be automatically directed to the location the exported package is stored. You will recognize the package because it has the extension OMT. It should be the 4th from the bottom. This is the file you have to deliver.", "title": "Delivering the project"}, {"location": "sp-guides/tec-cb-ome-prf/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "sp-guides/tec-cb-ome-rec/", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk. Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine. Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy : Reconciling using matches \u00b6 During the reconciliation task, the translations from translator 1 and translator 2 are handled as matches and are displayed in the Matches pane. A reconciler's task in practice consists of one of these three options: Inserting one of the two matches (and then modify it if needed), OR Inserting part of one of the two matches and then inserting part of the other match, OR Translating the segment from scratch if none of the two matches is suitable. By default, the match from translator 1 is activated. It is the first one in the list and it is bolded . If you want to use the match from translator 2, double click on it to activate that one instead (the activated match will become bolded ). To insert the active match in full, press Ctrl + I on your keyboard. After inserting it, make any necessary changes so that it fits the segment you are reconciling. Alternatively, you can also insert only part of a match or combine several matches: Double-click the match you want to use to activate it Drag your mouse over the part of the match you wish to insert to select it Press Ctrl + I on your keyboard to insert it Select (part of) another match if appropriate or type the rest of the translation Remember It is important to make sure the final translation is harmonized as the two translators may use different terms and styles. To ensure this, make sure you preview the item prior to delivery and perform concordance searches on recurring instructions and terminology. Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags: standalone tags and paired tags or double tags: Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags. To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags, enjoy : Fixing tag issues \u00b6 All tags you see in the source text should be present in the translation too and in the correct position. You must correct any errors that you may see when that's not the case. You may find two types of issue: A tag or tag pair is missing: in that case, the solution is simply to insert it . A tag is inserted but misplaced: the solution may be either to drag and drop single tags to the correct position, or simply to delete the tag (or tag pair) and insert it again correctly. Warning for RTL languages In right-to-left languages such as Arabic or Hebrew, moving tags will not work. Please delete the tag and insert it again if you work with any of these languages. Deleting tags \u00b6 If you have inserted a tag incorrectly and need to insert it again, double click on the tag to select it in full and press Backspace or Del on your keyboard to delete it first. Moving tags \u00b6 If you have inserted a tag in the wrong position and need to insert it somewhere else, you can simply drag and drop it. Alternatively, you can also delete it and insert it again. Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry. Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy : Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting. QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue. Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver. OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Tec cb ome rec"}, {"location": "sp-guides/tec-cb-ome-rec/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "sp-guides/tec-cb-ome-rec/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "sp-guides/tec-cb-ome-rec/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "sp-guides/tec-cb-ome-rec/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "sp-guides/tec-cb-ome-rec/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "sp-guides/tec-cb-ome-rec/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "sp-guides/tec-cb-ome-rec/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "sp-guides/tec-cb-ome-rec/#navigation", "text": "", "title": "Navigation"}, {"location": "sp-guides/tec-cb-ome-rec/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "sp-guides/tec-cb-ome-rec/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "sp-guides/tec-cb-ome-rec/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "sp-guides/tec-cb-ome-rec/#reconciling-using-matches", "text": "During the reconciliation task, the translations from translator 1 and translator 2 are handled as matches and are displayed in the Matches pane. A reconciler's task in practice consists of one of these three options: Inserting one of the two matches (and then modify it if needed), OR Inserting part of one of the two matches and then inserting part of the other match, OR Translating the segment from scratch if none of the two matches is suitable. By default, the match from translator 1 is activated. It is the first one in the list and it is bolded . If you want to use the match from translator 2, double click on it to activate that one instead (the activated match will become bolded ). To insert the active match in full, press Ctrl + I on your keyboard. After inserting it, make any necessary changes so that it fits the segment you are reconciling. Alternatively, you can also insert only part of a match or combine several matches: Double-click the match you want to use to activate it Drag your mouse over the part of the match you wish to insert to select it Press Ctrl + I on your keyboard to insert it Select (part of) another match if appropriate or type the rest of the translation Remember It is important to make sure the final translation is harmonized as the two translators may use different terms and styles. To ensure this, make sure you preview the item prior to delivery and perform concordance searches on recurring instructions and terminology.", "title": "Reconciling using matches"}, {"location": "sp-guides/tec-cb-ome-rec/#tags", "text": "", "title": "Tags"}, {"location": "sp-guides/tec-cb-ome-rec/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "sp-guides/tec-cb-ome-rec/#types-of-tags", "text": "There are two types of tags: standalone tags and paired tags or double tags: Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "sp-guides/tec-cb-ome-rec/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags. To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags, enjoy :", "title": "Inserting tags"}, {"location": "sp-guides/tec-cb-ome-rec/#fixing-tag-issues", "text": "All tags you see in the source text should be present in the translation too and in the correct position. You must correct any errors that you may see when that's not the case. You may find two types of issue: A tag or tag pair is missing: in that case, the solution is simply to insert it . A tag is inserted but misplaced: the solution may be either to drag and drop single tags to the correct position, or simply to delete the tag (or tag pair) and insert it again correctly. Warning for RTL languages In right-to-left languages such as Arabic or Hebrew, moving tags will not work. Please delete the tag and insert it again if you work with any of these languages.", "title": "Fixing tag issues"}, {"location": "sp-guides/tec-cb-ome-rec/#deleting-tags", "text": "If you have inserted a tag incorrectly and need to insert it again, double click on the tag to select it in full and press Backspace or Del on your keyboard to delete it first.", "title": "Deleting tags"}, {"location": "sp-guides/tec-cb-ome-rec/#moving-tags", "text": "If you have inserted a tag in the wrong position and need to insert it somewhere else, you can simply drag and drop it. Alternatively, you can also delete it and insert it again.", "title": "Moving tags"}, {"location": "sp-guides/tec-cb-ome-rec/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "sp-guides/tec-cb-ome-rec/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "sp-guides/tec-cb-ome-rec/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "sp-guides/tec-cb-ome-rec/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "sp-guides/tec-cb-ome-rec/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "sp-guides/tec-cb-ome-rec/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "sp-guides/tec-cb-ome-rec/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "sp-guides/tec-cb-ome-rec/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "sp-guides/tec-cb-ome-rec/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "sp-guides/tec-cb-ome-rec/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "sp-guides/tec-cb-ome-rec/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "sp-guides/tec-cb-ome-rec/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "sp-guides/tec-cb-ome-rec/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "sp-guides/tec-cb-ome-rec/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "sp-guides/tec-cb-ome-rec/#qa-checks", "text": "", "title": "QA checks"}, {"location": "sp-guides/tec-cb-ome-rec/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "sp-guides/tec-cb-ome-rec/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "sp-guides/tec-cb-ome-rec/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "sp-guides/tec-cb-ome-rec/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "sp-guides/tec-cb-ome-rec/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "sp-guides/tec-cb-ome-rec/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "sp-guides/tec-cb-ome-rec/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "sp-guides/tec-cb-ome-rec/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "sp-guides/tec-cb-ome-tra/", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk. Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine. Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy : Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags: standalone tags and paired tags or double tags: Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags. To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags, enjoy : Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment. Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry. Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy : Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting. QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue. Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver. OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Tec cb ome tra"}, {"location": "sp-guides/tec-cb-ome-tra/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "sp-guides/tec-cb-ome-tra/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "sp-guides/tec-cb-ome-tra/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "sp-guides/tec-cb-ome-tra/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "sp-guides/tec-cb-ome-tra/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "sp-guides/tec-cb-ome-tra/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "sp-guides/tec-cb-ome-tra/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "sp-guides/tec-cb-ome-tra/#navigation", "text": "", "title": "Navigation"}, {"location": "sp-guides/tec-cb-ome-tra/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "sp-guides/tec-cb-ome-tra/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "sp-guides/tec-cb-ome-tra/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "sp-guides/tec-cb-ome-tra/#tags", "text": "", "title": "Tags"}, {"location": "sp-guides/tec-cb-ome-tra/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "sp-guides/tec-cb-ome-tra/#types-of-tags", "text": "There are two types of tags: standalone tags and paired tags or double tags: Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "sp-guides/tec-cb-ome-tra/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags. To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags, enjoy :", "title": "Inserting tags"}, {"location": "sp-guides/tec-cb-ome-tra/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "sp-guides/tec-cb-ome-tra/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "sp-guides/tec-cb-ome-tra/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "sp-guides/tec-cb-ome-tra/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "sp-guides/tec-cb-ome-tra/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "sp-guides/tec-cb-ome-tra/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "sp-guides/tec-cb-ome-tra/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "sp-guides/tec-cb-ome-tra/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "sp-guides/tec-cb-ome-tra/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "sp-guides/tec-cb-ome-tra/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "sp-guides/tec-cb-ome-tra/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "sp-guides/tec-cb-ome-tra/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "sp-guides/tec-cb-ome-tra/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "sp-guides/tec-cb-ome-tra/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "sp-guides/tec-cb-ome-tra/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "sp-guides/tec-cb-ome-tra/#qa-checks", "text": "", "title": "QA checks"}, {"location": "sp-guides/tec-cb-ome-tra/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "sp-guides/tec-cb-ome-tra/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "sp-guides/tec-cb-ome-tra/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "sp-guides/tec-cb-ome-tra/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "sp-guides/tec-cb-ome-tra/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "sp-guides/tec-cb-ome-tra/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "sp-guides/tec-cb-ome-tra/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "sp-guides/tec-cb-ome-tra/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags. character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "sp-guides/tec-cb-ome-ver/", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk. Your user Name/ID \u00b6 When opening OmegaT for the first time, please update your Name/ID. To do that click on Options > Preferences > Team . The Name/ID box might already contain your username. If that's the case, please prepend your username with VER . If the box is empty, please enter VER_your-name (e.g. VER_souto , VER_msoutopico , etc.). Then press OK. Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine. Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy : Warning All segments should appear translated for an editing task (such as verification, proofreading, etc.), i.e. highlighted either in gray (translated) or in pink (pretranslated) or in orange (pretranslated and locked, for trend or legacy translations). If you notice an untranslated segment in blue , please contact cApStAn's project managers to see how it should be handled. Revising and editing \u00b6 Revising the translation \u00b6 To revise the translation, you must move through segments one by one. Read every translation, while comparing with the source text, considering the rest of the context and taking into account any specific instructions you may have received for your particular task. Press the Enter key to move to the next segment. The segment you jump to becomes active and ready for edits. This will also allow you to keep track of your progress. If you need to move backwards, you can press Ctrl + Enter . Editing the translation \u00b6 To correct an error in the translation, you must edit the target text. To edit a translation, simply delete the text that must be removed and type the text that must be added. You can only edit the translation of the active segment. You must activate a segment to make it editable. The segment you jump to pressing Enter becomes active and ready for edits. You may also activate any segment (and make it editable) by double-clicking it, but in that case you might want to return to the segment you were originally to continue revising from there. Tip You can recognize the active segment because it is highlighted in green . Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy : Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment. Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry. Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy : Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting. QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue. Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver. OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Tec cb ome ver"}, {"location": "sp-guides/tec-cb-ome-ver/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "sp-guides/tec-cb-ome-ver/#your-user-nameid", "text": "When opening OmegaT for the first time, please update your Name/ID. To do that click on Options > Preferences > Team . The Name/ID box might already contain your username. If that's the case, please prepend your username with VER . If the box is empty, please enter VER_your-name (e.g. VER_souto , VER_msoutopico , etc.). Then press OK.", "title": "Your user Name/ID"}, {"location": "sp-guides/tec-cb-ome-ver/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "sp-guides/tec-cb-ome-ver/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "sp-guides/tec-cb-ome-ver/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "sp-guides/tec-cb-ome-ver/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "sp-guides/tec-cb-ome-ver/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "sp-guides/tec-cb-ome-ver/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "sp-guides/tec-cb-ome-ver/#navigation", "text": "", "title": "Navigation"}, {"location": "sp-guides/tec-cb-ome-ver/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "sp-guides/tec-cb-ome-ver/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "sp-guides/tec-cb-ome-ver/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy : Warning All segments should appear translated for an editing task (such as verification, proofreading, etc.), i.e. highlighted either in gray (translated) or in pink (pretranslated) or in orange (pretranslated and locked, for trend or legacy translations). If you notice an untranslated segment in blue , please contact cApStAn's project managers to see how it should be handled.", "title": "Navigation through segments"}, {"location": "sp-guides/tec-cb-ome-ver/#revising-and-editing", "text": "", "title": "Revising and editing"}, {"location": "sp-guides/tec-cb-ome-ver/#revising-the-translation", "text": "To revise the translation, you must move through segments one by one. Read every translation, while comparing with the source text, considering the rest of the context and taking into account any specific instructions you may have received for your particular task. Press the Enter key to move to the next segment. The segment you jump to becomes active and ready for edits. This will also allow you to keep track of your progress. If you need to move backwards, you can press Ctrl + Enter .", "title": "Revising the translation"}, {"location": "sp-guides/tec-cb-ome-ver/#editing-the-translation", "text": "To correct an error in the translation, you must edit the target text. To edit a translation, simply delete the text that must be removed and type the text that must be added. You can only edit the translation of the active segment. You must activate a segment to make it editable. The segment you jump to pressing Enter becomes active and ready for edits. You may also activate any segment (and make it editable) by double-clicking it, but in that case you might want to return to the segment you were originally to continue revising from there. Tip You can recognize the active segment because it is highlighted in green .", "title": "Editing the translation"}, {"location": "sp-guides/tec-cb-ome-ver/#tags", "text": "", "title": "Tags"}, {"location": "sp-guides/tec-cb-ome-ver/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "sp-guides/tec-cb-ome-ver/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "sp-guides/tec-cb-ome-ver/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "sp-guides/tec-cb-ome-ver/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "sp-guides/tec-cb-ome-ver/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "sp-guides/tec-cb-ome-ver/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "sp-guides/tec-cb-ome-ver/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "sp-guides/tec-cb-ome-ver/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "sp-guides/tec-cb-ome-ver/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "sp-guides/tec-cb-ome-ver/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "sp-guides/tec-cb-ome-ver/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "sp-guides/tec-cb-ome-ver/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "sp-guides/tec-cb-ome-ver/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "sp-guides/tec-cb-ome-ver/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "sp-guides/tec-cb-ome-ver/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "sp-guides/tec-cb-ome-ver/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "sp-guides/tec-cb-ome-ver/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "sp-guides/tec-cb-ome-ver/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "sp-guides/tec-cb-ome-ver/#qa-checks", "text": "", "title": "QA checks"}, {"location": "sp-guides/tec-cb-ome-ver/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "sp-guides/tec-cb-ome-ver/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "sp-guides/tec-cb-ome-ver/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "sp-guides/tec-cb-ome-ver/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "sp-guides/tec-cb-ome-ver/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "sp-guides/tec-cb-ome-ver/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "sp-guides/tec-cb-ome-ver/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "sp-guides/tec-cb-ome-ver/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "sp-guides/tec-cb-ome-wlk-thr/", "text": "Quick walkthrough (for reconciliation) \u00b6 Download the package for reconciliation and the Excel document from the portal Import the OMT package in OmegaT as described in the section The OmegaT project for reconciliation will open: All segments will appear untranslated in the Editor pane (the main pane of OmegaT, which contains the source text). To find out how to recognize reconciled segments from unreconciled ones and from potential trend segments, please refer to the section The** suggestions from Translator 1 and Translator 2** for the active segment (green) appear below, in the Fuzzy matches pane In the Fuzzy matches pane, the suggestions from the 2 translators display the source text of the active segment , the suggested translation for the active segment as well as the identity of the author . By default, the suggestion from translator 1 appears in bold. It means it is selected. If you want to insert it, no need to retype the text, you can simply press Ctrl + I on your keyboard and it will appear below the active segment. To learn how to reconcile and insert the suggestions from translator 2 or how to combine both, please read the section You can preview the file you are reconciling on the portal. Please consult the section Creating the target file to learn how to create and access the reconciled file. This is the file you will have to drag and drop on the portal for preview. If you notice errors in formatting while previewing (e.g. words that are bolded in your language but were not bolded in the source, or vice-versa), please consult the section Fixing tag issues to learn how to correct them. If you notice identical source sentences that need to be reconciled differently, please consult the section Create alternative translation After performing a few QA checks , most importantly the Completion check , you can create the reconciled package and deliver it on the portal. To create the reconciled package , go to Project>Export OMT package in OmegaT. More details about how to create the package for delivery can be found in the section Exporting the package for delivery", "title": "Quick walkthrough (for reconciliation)"}, {"location": "sp-guides/tec-cb-ome-wlk-thr/#quick-walkthrough-for-reconciliation", "text": "Download the package for reconciliation and the Excel document from the portal Import the OMT package in OmegaT as described in the section The OmegaT project for reconciliation will open: All segments will appear untranslated in the Editor pane (the main pane of OmegaT, which contains the source text). To find out how to recognize reconciled segments from unreconciled ones and from potential trend segments, please refer to the section The** suggestions from Translator 1 and Translator 2** for the active segment (green) appear below, in the Fuzzy matches pane In the Fuzzy matches pane, the suggestions from the 2 translators display the source text of the active segment , the suggested translation for the active segment as well as the identity of the author . By default, the suggestion from translator 1 appears in bold. It means it is selected. If you want to insert it, no need to retype the text, you can simply press Ctrl + I on your keyboard and it will appear below the active segment. To learn how to reconcile and insert the suggestions from translator 2 or how to combine both, please read the section You can preview the file you are reconciling on the portal. Please consult the section Creating the target file to learn how to create and access the reconciled file. This is the file you will have to drag and drop on the portal for preview. If you notice errors in formatting while previewing (e.g. words that are bolded in your language but were not bolded in the source, or vice-versa), please consult the section Fixing tag issues to learn how to correct them. If you notice identical source sentences that need to be reconciled differently, please consult the section Create alternative translation After performing a few QA checks , most importantly the Completion check , you can create the reconciled package and deliver it on the portal. To create the reconciled package , go to Project>Export OMT package in OmegaT. More details about how to create the package for delivery can be found in the section Exporting the package for delivery", "title": "Quick walkthrough (for reconciliation)"}, {"location": "translation/", "tags": ["Translation"], "text": "a.md-footer__link--prev[aria-label^=\"Previous:\"], .md-nav__icon { display: none !important; } \ud83d\udc4b Welcome to the OmegaT translation guide! \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "Translation"}, {"location": "translation/#welcome-to-the-omegat-translation-guide", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "\ud83d\udc4b Welcome to the OmegaT translation guide!"}, {"location": "translation/accessing-the-project/", "text": "Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Accessing a project"}, {"location": "translation/accessing-the-project/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "translation/accessing-the-project/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "translation/accessing-the-project/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "translation/accessing-the-project/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "translation/accessing-the-project/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "translation/accessing-the-project/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "translation/creating-target-files/", "text": "Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "translation/creating-target-files/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "translation/creating-your-deliverable/", "text": "Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Creating your deliverable"}, {"location": "translation/creating-your-deliverable/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "translation/creating-your-deliverable/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "translation/creating-your-deliverable/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "translation/glossary/", "text": "Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Glossary"}, {"location": "translation/glossary/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "translation/glossary/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "translation/glossary/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "translation/install-and-setup/", "text": "Installation and setup \u00b6 To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "translation/install-and-setup/#installation-and-setup", "text": "To install OmegaT and set it up on a computer running Windows, please follow the OmegaT installation and setup guide below: If you use Mac or Linux, please see the second slide above or get in touch through the Helpdesk.", "title": "Installation and setup"}, {"location": "translation/matches/", "text": "Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "translation/matches/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "translation/navigation/", "text": "Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation"}, {"location": "translation/navigation/#navigation", "text": "", "title": "Navigation"}, {"location": "translation/navigation/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "translation/navigation/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "translation/navigation/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy :", "title": "Navigation through segments"}, {"location": "translation/other-useful-features/", "text": "Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Other useful features"}, {"location": "translation/other-useful-features/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "translation/other-useful-features/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "translation/other-useful-features/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "translation/other-useful-features/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "translation/other-useful-features/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "translation/other-useful-features/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "translation/other-useful-features/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "translation/qa-checks/", "text": "QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "QA checks"}, {"location": "translation/qa-checks/#qa-checks", "text": "", "title": "QA checks"}, {"location": "translation/qa-checks/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "translation/qa-checks/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "translation/qa-checks/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "translation/repetitions/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Repetitions"}, {"location": "translation/repetitions/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "translation/repetitions/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "translation/repetitions/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "translation/repetitions/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "translation/shortcuts/", "text": "a.md-footer__link--next[aria-label^=\"Next:\"], .md-nav__icon { display: none !important; } OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "translation/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "translation/tags/", "text": "Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Tags"}, {"location": "translation/tags/#tags", "text": "", "title": "Tags"}, {"location": "translation/tags/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "translation/tags/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "translation/tags/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "verification/", "tags": ["Verification"], "text": "a.md-footer__link--prev[aria-label^=\"Previous:\"], .md-nav__icon { display: none !important; } \ud83d\udc4b Welcome to the OmegaT verification guide! \u00b6 OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "Verification"}, {"location": "verification/#welcome-to-the-omegat-verification-guide", "text": "OmegaT is the open source computer-assisted translation tool (CAT tool) which will be used to translate, reconcile, adapt, review and verify materials. The software has been customized to optimize your task. This guide includes information about all the functions in OmegaT that you need to perform the translation task. Make sure you can see the navigation pane on the left-hand side. You can use that menu or the arrow button at the bottom to go to the next section.", "title": "\ud83d\udc4b Welcome to the OmegaT verification guide!"}, {"location": "verification/accessing-the-project/", "text": "Accessing a project \u00b6 Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here . Accessing a new project \u00b6 There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects . Unpacking an offline project \u00b6 If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project. Downloading a team project \u00b6 If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git . Authentication \u00b6 At some point during the steps below, or afterwards, OmegaT will ask you to authenticate, so please make sure you have your credentials at hand. OmegaT might ask you to authenticate one or more times (depending on the project settings), please just enter the same credentials as many time as requested. How to download the project from the repository \u00b6 To download the team project, follow these steps: Define a location in your machine where you would like to create the OmegaT project. We recommend a Work folder (or whatever you prefer to call it) in your user's home directory. Let's assume path C:\\Users\\USER\\Work\\ (for user USER ). Danger \u2757\u2757\u2757 \ud83d\udc80 Make sure that location is NOT inside a sync'ed folder such as Dropbox, OneDrive, Nextcloud, Google Drive, Syncthing or the like, or in a server. Copy the URL of the project repository to your clipboard (select it and press Ctrl + C or right-click it and select Copy). In OmegaT, go to Project > Download Team Project . In the Download Team Project dialog, click in the Repository URL field and then press Ctrl + V to paste the URL from your clipboard. Click in the New Local Project Folder field. OmegaT will propose a path to the location where it will create the project folder. Please wait until you see that path. Failure DO NOT click on the ... button. See the three steps above in the following animation: You might want to modify that path to create the folder in the location that you have defined in the first step above. For example: By default, it's likely that OmegaT proposes to create the project inside your home directory, e.g. C:\\Users\\USER\\repo-name . Modify that path so that it points ot the actual location you prefer, e.g. if you follow our recommendation above, that would be C:\\Users\\USER\\Work\\repo-name . For example: Caution Make sure there's a slash between every two folders in your path. Closing the project \u00b6 When you are done working for the day, quit OmegaT ( Ctrl + Q ). Re-opening an existing project \u00b6 After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Accessing a project"}, {"location": "verification/accessing-the-project/#accessing-a-project", "text": "Tip Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here .", "title": "Accessing a project"}, {"location": "verification/accessing-the-project/#accessing-a-new-project", "text": "There are two ways you may access a project for the first time, depending on whether it is an online project (or team project ) or an offline project . If you must work on an offline project , you will receive a new OmegaT project package (aka an OMT package, or a file with .omt extension). Go to the section Unpacking an offline project below to see what you must do to unpack a project package. If you must work on an online project (or team project ), you will receive the URL to the repository where the OmegaT project is hosted. Go to the section Downloading a team project below to see what you must to do download a team project from a repository. If you're not sure whether your project is online or offline, it's very easy: if you receive an OMT package, the project is offline, and if you receive a URL to a git repository, the project is online. You receive Project is OMT file offline/package URL to git repo online/team Caution Unpacking or downloading an OmegaT project (depending on the distribution mode) needs to be done only once for each project. After you have unpacked or downloaded a project, you can simply re-open it from the list of recent projects .", "title": "Accessing a new project"}, {"location": "verification/accessing-the-project/#unpacking-an-offline-project", "text": "If you receive an OMT package, you must unpack the project (from the OMT package) to access the project for the first time. To unpack a project, follow these steps: Store the OMT package in the folder where you would like to create the OmegaT project. To unpack the project from the OMT package: Launch OmegaT. Go to Project > Unpack project from OMT file : Navigate to the location where you stored the OMT package. Select the OMT package and click on Open: A pop up opens. Click Yes . You can now perform your task in the project.", "title": "Unpacking an offline project"}, {"location": "verification/accessing-the-project/#downloading-a-team-project", "text": "If you receive a URL to a git repository, you must download the team project from that repository to access the project for the first time. Info The URL should look a bit like this: https://domain.com/path/to/repo-name.git .", "title": "Downloading a team project"}, {"location": "verification/accessing-the-project/#closing-the-project", "text": "When you are done working for the day, quit OmegaT ( Ctrl + Q ).", "title": "Closing the project"}, {"location": "verification/accessing-the-project/#re-opening-an-existing-project", "text": "After you have received and opened a project for the first time, the project exists in your machine and OmegaT will remember it. The next times you want to access the project in OmegaT, go to Project > Open Recent Project . The project you were working on will appear in the list: Note Make sure the disctinction between opening a recent project and downloading or unpacking a new project (depending on the distribution mode) is clear. You can open a project that already exists only after you have already unpacked it or downloaded it. In turn, you only need to download or unpack (once) a project that doesn't exist yet in your machine.", "title": "Re-opening an existing project"}, {"location": "verification/creating-target-files/", "text": "Creating target files \u00b6 A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "verification/creating-target-files/#creating-target-files", "text": "A target file (or translated document) has the same structure as the source file but contains the target text (your translation). If you need to use the target file directly, you must create it every time you update the translation in the editor. Press Ctrl + Shift + D (or go to Project > Create Current Translated Document ) to create the target file you were working on. To access the file(s), go to Project > Access Project Contents > Target Files to open your file explorer in the /target folder of the project. The file you were working on should be there. Info The target file will be overwritten every time you press Ctrl + Shift + D", "title": "Creating target files"}, {"location": "verification/creating-your-deliverable/", "text": "Delivery \u00b6 Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project . Online / team project (via repository) \u00b6 To deliver from a team project: Go to Project > Commit Target Files . That's it! Offline project (via package) \u00b6 Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Creating your deliverable"}, {"location": "verification/creating-your-deliverable/#delivery", "text": "Once you have finished your task in the OmegaT project and have performed the relevant QA checks, you need to deliver the project. The delivery mode will vary depending on whether it's an offline project or a team project .", "title": "Delivery"}, {"location": "verification/creating-your-deliverable/#online-team-project-via-repository", "text": "To deliver from a team project: Go to Project > Commit Target Files . That's it!", "title": "Online / team project (via repository)"}, {"location": "verification/creating-your-deliverable/#offline-project-via-package", "text": "Go to Project > Pack project as OMT file... In the window that pops up, select the location where you want to save the OMT package. Press Save Press OK in the Pop-up window notifying that the package was successfully created. The folder where exported package is stored will open automatically in your file explorer. You will recognize the package because it has the extension .omt . That's the file you have to deliver.", "title": "Offline project (via package)"}, {"location": "verification/editing/", "text": "Revising and editing \u00b6 Revising the translation \u00b6 To revise the translation, you must move through segments one by one. Read every translation, while comparing with the source text, considering the rest of the context and taking into account any specific instructions you may have received for your particular task. Press the Enter key to move to the next segment. The segment you jump to becomes active and ready for edits. This will also allow you to keep track of your progress. If you need to move backwards, you can press Ctrl + Enter . Editing the translation \u00b6 To correct an error in the translation, you must edit the target text. To edit a translation, simply delete the text that must be removed and type the text that must be added. You can only edit the translation of the active segment. You must activate a segment to make it editable. The segment you jump to pressing Enter becomes active and ready for edits. You may also activate any segment (and make it editable) by double-clicking it, but in that case you might want to return to the segment you were originally to continue revising from there. Tip You can recognize the active segment because it is highlighted in green .", "title": "Editing"}, {"location": "verification/editing/#revising-and-editing", "text": "", "title": "Revising and editing"}, {"location": "verification/editing/#revising-the-translation", "text": "To revise the translation, you must move through segments one by one. Read every translation, while comparing with the source text, considering the rest of the context and taking into account any specific instructions you may have received for your particular task. Press the Enter key to move to the next segment. The segment you jump to becomes active and ready for edits. This will also allow you to keep track of your progress. If you need to move backwards, you can press Ctrl + Enter .", "title": "Revising the translation"}, {"location": "verification/editing/#editing-the-translation", "text": "To correct an error in the translation, you must edit the target text. To edit a translation, simply delete the text that must be removed and type the text that must be added. You can only edit the translation of the active segment. You must activate a segment to make it editable. The segment you jump to pressing Enter becomes active and ready for edits. You may also activate any segment (and make it editable) by double-clicking it, but in that case you might want to return to the segment you were originally to continue revising from there. Tip You can recognize the active segment because it is highlighted in green .", "title": "Editing the translation"}, {"location": "verification/glossary/", "text": "Using the glossary \u00b6 OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project. Inserting terms from the glossary \u00b6 When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard. Adding new entries to the glossary \u00b6 Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Glossary"}, {"location": "verification/glossary/#using-the-glossary", "text": "OmegaT supports glossaries. Your project may already contain a glossary with key terms, but you can also add terms to the glossary yourself. Help yourself! Adding new term pairs to the glossary might seem like extra work, but if done well it will be of valuable help to insert frequent expressions or to ensure that sensitive terms are translated consistently across the project.", "title": "Using the glossary"}, {"location": "verification/glossary/#inserting-terms-from-the-glossary", "text": "When the active segment contains a source term that is in the glossary, it is underlined in blue in the source text. You will see the suggested target term in the Glossary pane, on the right. OmegaT has predictive typing : when you start typing the first character of the target term in the glossary, the auto-completer will suggest the term. To insert it, press Enter on your keyboard.", "title": "Inserting terms from the glossary"}, {"location": "verification/glossary/#adding-new-entries-to-the-glossary", "text": "Tip Feeding the glossary with technical or sensitive wording or terms or expressions that appear frequently can be very useful to speed up typing, to keep consistency, to avoid typos, etc.. To add a new term entry to the glossary: In the active segment, drag your mouse over the term you want to insert to select it . Right click and choose Add glossary entry from the contextual menu. In the Create Glossary Entry that will pop up, enter the target term (and any comments you want). Press the OK button to save the new entry.", "title": "Adding new entries to the glossary"}, {"location": "verification/install-and-setup-macos/", "text": "OmegaT 5.7.2 setup guide for macOS \u00b6 Carefully choose your path here: If there is no current installation of OmegaT in your machine, you can skip the following steps about configuration and jump directly to the installation section . OmegaT will configure itself as part of the installation. If you already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed, you'll have to update your configuration first: to do so please go to the configuration section (next section right down below). Configuration \u00b6 This section applies to users that already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed. Please follow the next steps to update your configuration for starteers. Run OmegaT and go to Tools > Scripting to open your scripting console, In OmegaT 5.7.1, please open the scripting console. Check whethers you have a script called \" Update Customisation Bundle (v572) \": Warning If you don't see the \" v572 \" bit, then it's not the script we're looking for. See next step to fetch the script. If the script \" Update Customisation Bundle (v572) \" is there, please click on it to select it and press the Run button (at the bottom left) to run it. The script will run to update your config files and will quit OmegaT. After that, skip the next step and jump directly to the installation section . If the script is not there, go to the next step to download it. Click on the button below to download the configuration script (e.g. to your Desktop) Download UpdateConfigBundle.groovy In OmegaT, follow these steps to run the configuration script you have downloaded: Tools > Scripting > File > Open script browse to your Desktop (or the folder where you have saved the script) and select the groovy file press the Open button to open the script file and press Run button (on the bottom left) The script will install the necessary config files for OmegaT 5.7.2 and delete old config files for OmegaT 5.7.1, and after that it will quit OmegaT. Uninstall your current version of OmegaT. To do that, simply move the installed OmegaT.app to Trash. Finally, proceed now to the installation section (next step below). Installation \u00b6 Click on the button below to download OmegaT 5.7.2. This is a custom version prepared by cApStAn which includes several bug fixes and enhancements not available in other versions. Download OmegaT 5.7.2 If you're using Safari, then the file will be unzipped automatically when the download ends.\u200b If you use another browser, double-click the file when the download ends to unzip it. A folder is created, open it to see its contents. You'll see that it contains the OmegaT.app file. Drag the OmegaT.app file to the Applications folder. OmegaT is now installed. Go to the Applications folder and open OmegaT there. Your Mac might ask for confirmation that you want to open it. If that's the case, please press Open . OmegaT will now run. If you want to run a post-installation check to confirm that you have the correct version, you can check that in Help > About > Copy Support Info . You should see: Version: OmegaT-5.7.2_0_a978d82ee Platform: [your operating system] Java: 11.0.19 amd64 You're done now. You can start using OmegaT 5.7.2. Please do not forget to set your user name in OmegaT . Your user Name/ID \u00b6 When opening OmegaT for the first time, please update your Name/ID. To do that click on Options > Preferences > Team . The Name/ID box might already contain your username. If that's the case, please prepend your username with VER_ . If the box is empty, please enter VER_your-name (e.g. VER_souto , VER_msoutopico , etc.). Then press OK.", "title": "Install and setup macos"}, {"location": "verification/install-and-setup-macos/#omegat-572-setup-guide-for-macos", "text": "Carefully choose your path here: If there is no current installation of OmegaT in your machine, you can skip the following steps about configuration and jump directly to the installation section . OmegaT will configure itself as part of the installation. If you already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed, you'll have to update your configuration first: to do so please go to the configuration section (next section right down below).", "title": "OmegaT 5.7.2 setup guide for macOS"}, {"location": "verification/install-and-setup-macos/#configuration", "text": "This section applies to users that already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed. Please follow the next steps to update your configuration for starteers. Run OmegaT and go to Tools > Scripting to open your scripting console, In OmegaT 5.7.1, please open the scripting console. Check whethers you have a script called \" Update Customisation Bundle (v572) \": Warning If you don't see the \" v572 \" bit, then it's not the script we're looking for. See next step to fetch the script. If the script \" Update Customisation Bundle (v572) \" is there, please click on it to select it and press the Run button (at the bottom left) to run it. The script will run to update your config files and will quit OmegaT. After that, skip the next step and jump directly to the installation section . If the script is not there, go to the next step to download it. Click on the button below to download the configuration script (e.g. to your Desktop) Download UpdateConfigBundle.groovy In OmegaT, follow these steps to run the configuration script you have downloaded: Tools > Scripting > File > Open script browse to your Desktop (or the folder where you have saved the script) and select the groovy file press the Open button to open the script file and press Run button (on the bottom left) The script will install the necessary config files for OmegaT 5.7.2 and delete old config files for OmegaT 5.7.1, and after that it will quit OmegaT. Uninstall your current version of OmegaT. To do that, simply move the installed OmegaT.app to Trash. Finally, proceed now to the installation section (next step below).", "title": "Configuration"}, {"location": "verification/install-and-setup-macos/#installation", "text": "Click on the button below to download OmegaT 5.7.2. This is a custom version prepared by cApStAn which includes several bug fixes and enhancements not available in other versions. Download OmegaT 5.7.2 If you're using Safari, then the file will be unzipped automatically when the download ends.\u200b If you use another browser, double-click the file when the download ends to unzip it. A folder is created, open it to see its contents. You'll see that it contains the OmegaT.app file. Drag the OmegaT.app file to the Applications folder. OmegaT is now installed. Go to the Applications folder and open OmegaT there. Your Mac might ask for confirmation that you want to open it. If that's the case, please press Open . OmegaT will now run. If you want to run a post-installation check to confirm that you have the correct version, you can check that in Help > About > Copy Support Info . You should see: Version: OmegaT-5.7.2_0_a978d82ee Platform: [your operating system] Java: 11.0.19 amd64 You're done now. You can start using OmegaT 5.7.2. Please do not forget to set your user name in OmegaT .", "title": "Installation"}, {"location": "verification/install-and-setup-macos/#your-user-nameid", "text": "When opening OmegaT for the first time, please update your Name/ID. To do that click on Options > Preferences > Team . The Name/ID box might already contain your username. If that's the case, please prepend your username with VER_ . If the box is empty, please enter VER_your-name (e.g. VER_souto , VER_msoutopico , etc.). Then press OK.", "title": "Your user Name/ID"}, {"location": "verification/install-and-setup/", "text": "OmegaT 5.7.2 setup guide for Windows \u00b6 Other operating systems It's possible to install OmegaT 5.7.2 in other operating systems like macOS or Linux. Follow this other guide to install on macOS . Please get in touch through the Helpdesk if you are a Linux user. Choose your path here carefully , depending on your starting point: IF you already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed, you'll have to update your configuration first: to do so please go to the configuration section (next section right down below). IF there is no current installation of OmegaT in your machine, you can skip the following steps about configuration and jump directly to the installation section . OmegaT will configure itself as part of the installation. Configuration \u00b6 This section applies to users that already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed. Please follow the next steps to update your configuration. Run OmegaT and go to Tools > Scripting to open your scripting console, In OmegaT 5.7.1, please open the scripting console. Check whethers you have a script called \" Update Customisation Bundle (v572) \": Warning If you don't see the \" v572 \" bit, then it's not the script we're looking for. See next step to fetch the script. If the script \" Update Customisation Bundle (v572) \" is there, please click on it to select it and press the Run button (at the bottom left) to run it. The script will run to update your config files and will quit OmegaT. After that, skip the next step and jump directly to the installation section . If the script is not there, you may download it yourself. See next steps for how to do that. Click on the button below to download the configuration script (e.g. to your Desktop) Download UpdateConfigBundle.groovy In OmegaT, follow these steps to run the configuration script you have downloaded: Tools > Scripting > File > Open script browse to your Desktop (or the folder where you have saved the script) and select the groovy file press the Open button to open the script file and press Run button (on the bottom left) The script will install the necessary config files for OmegaT 5.7.2 and delete old config files for OmegaT 5.7.1, and after that it will quit OmegaT. Uninstall your current version of OmegaT. Finally, proceed now to the installation section (next step below). Installation \u00b6 Warning You must have a 64-bit machine to install OmegaT. If that's not the case, please get in touch with our Helpdesk. Click on the button below to download OmegaT 5.7.2. This is a custom version prepared by cApStAn which includes several bug fixes and enhancements not available in other versions. Download OmegaT 5.7.2 Trouble to download? Some browsers (e.g. Microsoft Edge) might ask you whether downloading the installer is safe. It is safe, and you can follow the following steps in the video below to let your browser download the file. Double-click the installer file to start the installation wizard. Windows Defender might show a dialog warning against the risk of running an unrecognized app. s If you see that, click on the More info link in that dialog. In the information displayed you should see that cApStAn is the publisher of this installer. If that's the case, prease press the Run anyway button to proceed with the installation. In the next dialog, you may choose the language of the installation, then press Ok : Please accept the GPL license agreement to proceed, and press Next : OmegaT will propose the path C:\\Users\\USER\\AppData\\Local\\Programs\\OmegaT for the installation, where it should be possible for non-admin users to install. Warning Please do not modify this installation path unless you're IT personnel and you know what you're doing. A desktop shortcut (launcher) will be created on your Desktop (which you can double-click later on to launch OmegaT). Do not uncheck that option. You may modify the name of the OmegaT folder in the start menu, but \"OmegaT \" is fine, no need to change it in a standard installation. You're ready to proceed with the installation, press Next . After a couple of minutes, your installation should be complete. If you want to run a post-installation check to confirm that you have the correct version, you can check that in Help > About > Copy Support Info . You should see: Version: OmegaT-5.7.2_0_a978d82ee Platform: [your operating system] Java: 11.0.19 amd64 You're done now. You can start using OmegaT 5.7.2. Please do not forget to set your user name in OmegaT . Your user Name/ID \u00b6 When opening OmegaT for the first time, please update your Name/ID. To do that click on Options > Preferences > Team . The Name/ID box might already contain your username. If that's the case, please prepend your username with VER_ . If the box is empty, please enter VER_your-name (e.g. VER_souto , VER_msoutopico , etc.). Then press OK.", "title": "Installation and setup"}, {"location": "verification/install-and-setup/#omegat-572-setup-guide-for-windows", "text": "Other operating systems It's possible to install OmegaT 5.7.2 in other operating systems like macOS or Linux. Follow this other guide to install on macOS . Please get in touch through the Helpdesk if you are a Linux user. Choose your path here carefully , depending on your starting point: IF you already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed, you'll have to update your configuration first: to do so please go to the configuration section (next section right down below). IF there is no current installation of OmegaT in your machine, you can skip the following steps about configuration and jump directly to the installation section . OmegaT will configure itself as part of the installation.", "title": "OmegaT 5.7.2 setup guide for Windows"}, {"location": "verification/install-and-setup/#configuration", "text": "This section applies to users that already have a previous version (e.g. 5.7.1 or 4.2.0) of OmegaT installed. Please follow the next steps to update your configuration. Run OmegaT and go to Tools > Scripting to open your scripting console, In OmegaT 5.7.1, please open the scripting console. Check whethers you have a script called \" Update Customisation Bundle (v572) \": Warning If you don't see the \" v572 \" bit, then it's not the script we're looking for. See next step to fetch the script. If the script \" Update Customisation Bundle (v572) \" is there, please click on it to select it and press the Run button (at the bottom left) to run it. The script will run to update your config files and will quit OmegaT. After that, skip the next step and jump directly to the installation section . If the script is not there, you may download it yourself. See next steps for how to do that. Click on the button below to download the configuration script (e.g. to your Desktop) Download UpdateConfigBundle.groovy In OmegaT, follow these steps to run the configuration script you have downloaded: Tools > Scripting > File > Open script browse to your Desktop (or the folder where you have saved the script) and select the groovy file press the Open button to open the script file and press Run button (on the bottom left) The script will install the necessary config files for OmegaT 5.7.2 and delete old config files for OmegaT 5.7.1, and after that it will quit OmegaT. Uninstall your current version of OmegaT. Finally, proceed now to the installation section (next step below).", "title": "Configuration"}, {"location": "verification/install-and-setup/#installation", "text": "Warning You must have a 64-bit machine to install OmegaT. If that's not the case, please get in touch with our Helpdesk. Click on the button below to download OmegaT 5.7.2. This is a custom version prepared by cApStAn which includes several bug fixes and enhancements not available in other versions. Download OmegaT 5.7.2 Trouble to download? Some browsers (e.g. Microsoft Edge) might ask you whether downloading the installer is safe. It is safe, and you can follow the following steps in the video below to let your browser download the file. Double-click the installer file to start the installation wizard. Windows Defender might show a dialog warning against the risk of running an unrecognized app. s If you see that, click on the More info link in that dialog. In the information displayed you should see that cApStAn is the publisher of this installer. If that's the case, prease press the Run anyway button to proceed with the installation. In the next dialog, you may choose the language of the installation, then press Ok : Please accept the GPL license agreement to proceed, and press Next : OmegaT will propose the path C:\\Users\\USER\\AppData\\Local\\Programs\\OmegaT for the installation, where it should be possible for non-admin users to install. Warning Please do not modify this installation path unless you're IT personnel and you know what you're doing. A desktop shortcut (launcher) will be created on your Desktop (which you can double-click later on to launch OmegaT). Do not uncheck that option. You may modify the name of the OmegaT folder in the start menu, but \"OmegaT \" is fine, no need to change it in a standard installation. You're ready to proceed with the installation, press Next . After a couple of minutes, your installation should be complete. If you want to run a post-installation check to confirm that you have the correct version, you can check that in Help > About > Copy Support Info . You should see: Version: OmegaT-5.7.2_0_a978d82ee Platform: [your operating system] Java: 11.0.19 amd64 You're done now. You can start using OmegaT 5.7.2. Please do not forget to set your user name in OmegaT .", "title": "Installation"}, {"location": "verification/install-and-setup/#your-user-nameid", "text": "When opening OmegaT for the first time, please update your Name/ID. To do that click on Options > Preferences > Team . The Name/ID box might already contain your username. If that's the case, please prepend your username with VER_ . If the box is empty, please enter VER_your-name (e.g. VER_souto , VER_msoutopico , etc.). Then press OK.", "title": "Your user Name/ID"}, {"location": "verification/matches/", "text": "Matches \u00b6 Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "verification/matches/#matches", "text": "Translations are saved in the working TM of the project. When you open a segment that is similar to one that has already been translated, you will see translation suggestions (or matches) appearing in the Matches pane. The source text in the Matches pane uses \u201ctrack changes\u201d mode to show the differences (e.g. old new ) between the new source text in the active segment and the source text in the fuzzy match selected. Parts that do not appear in the active segment are struck through Parts that appear in the match are underlined Also, the Matches pane shows a similarity score that tells you how different the new source text is from the source text of every match. When there are several matches for a segment, they are sorted by their similarity to the new segment. The active match is the one in bold (by default, the one at the top of the list). If you want to use a different match, double click on it to activate it. To insert the match in full, press Ctrl + I on your keyboard. After inserting it, do not forget to make any necessary changes so that it fits the segment you are translating. Alternatively, you can also insert only a part of the fuzzy match or combine several matches: Double-click the match you want to use to activate it With your mouse, select the part you wish to insert Press Ctrl + I on your keyboard to insert it Do the same to insert (part of) other matches if appropriate or finish translating the segment.", "title": "Matches"}, {"location": "verification/navigation/", "text": "Navigation \u00b6 Navigation across panes \u00b6 When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations. Navigation through files \u00b6 If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files: Navigation through segments \u00b6 In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy : Warning All segments should appear translated for an editing task (such as verification, proofreading, etc.), i.e. highlighted either in gray (translated) or in pink (pretranslated) or in orange (pretranslated and locked, for trend or legacy translations). If you notice an untranslated segment in blue , please contact cApStAn's project managers to see how it should be handled.", "title": "Navigation"}, {"location": "verification/navigation/#navigation", "text": "", "title": "Navigation"}, {"location": "verification/navigation/#navigation-across-panes", "text": "When you open OmegaT you will notice the screen is split in several panes: The Editor pane is the main pane in which you will be working. Translation suggestions will appear in the Fuzzy Matches pane (or just Matches pane). The Glossary pane will display the existing glossary entries and the ones you may add. The Multiple Translations pane will show if a repeated segment has alternative translations.", "title": "Navigation across panes"}, {"location": "verification/navigation/#navigation-through-files", "text": "If the project contains multiple files, they are listed in the Project Files window. You can open this window by pressing Ctrl + L . The file currently open is highlighted in blue. If you want to open a different file in the Editor pane, click on it in the Project Files window. You can also see the name of the file that is open in the Editor pane's title bar. The following video shows navigation through files:", "title": "Navigation through files"}, {"location": "verification/navigation/#navigation-through-segments", "text": "In the editor pane, the active segment is highlighted in green. This is the segment you are working on. When you type or insert a translation, it will appear right below the source text . Press Enter on your keyboard to go to the next segment. You can also use Ctrl + U to jump to the next untranslated segment. A segment can also be activated by double clicking on it, it then becomes green. In OmegaT, the color of the segment's background will help you find your way around between the different segments: Color Language Meaning Green Source active segment (the segment you are working on) Blue Source untranslated segment Grey Source manually translated segment Pink Target pretranslated segment Orange Target pretranslated and locked segment (e.g. trend) Caution If you want to change a trend translation, document it in the monitoring form but do not try to change it in OmegaT. Any changes you make to these segments will not be saved. The existing translation will be maintained. The following video shows navigation through segments, enjoy : Warning All segments should appear translated for an editing task (such as verification, proofreading, etc.), i.e. highlighted either in gray (translated) or in pink (pretranslated) or in orange (pretranslated and locked, for trend or legacy translations). If you notice an untranslated segment in blue , please contact cApStAn's project managers to see how it should be handled.", "title": "Navigation through segments"}, {"location": "verification/other-useful-features/", "text": "Other useful features \u00b6 Inserting source segment in target \u00b6 In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer. Creating an empty translation \u00b6 All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation. Inserting special characters \u00b6 You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc. Character table \u00b6 We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert. Autotext \u00b6 Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list. Running concordance searches \u00b6 A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Other useful features"}, {"location": "verification/other-useful-features/#other-useful-features", "text": "", "title": "Other useful features"}, {"location": "verification/other-useful-features/#inserting-source-segment-in-target", "text": "In some cases, the translation must be identical to the source text. To copy the source text in the translation, press Ctrl + Shift + S on your keyboard. Of course, you may also copy-paste the source text in the translation if you prefer.", "title": "Inserting source segment in target"}, {"location": "verification/other-useful-features/#creating-an-empty-translation", "text": "All segments must have a translation, even if it's an empty translation. If you want to produce an empty translation, simply press the space bar in your keyboard to insert a space as the translation.", "title": "Creating an empty translation"}, {"location": "verification/other-useful-features/#inserting-special-characters", "text": "You may need to type special characters such as: quotation marks: \u00ab\u00bb , \u201e\u201c , \u2018\u2019 , etc. mathematical symbols: \u00d7 , \u03c0 , \u00f7 , \u2264 , \u2260 , \u221a , etc. superindex or subindex numbers or letters: \u2082 , \u00b2 , \u00b3 , etc. other characters: \u00ae , \u2122 , etc.", "title": "Inserting special characters"}, {"location": "verification/other-useful-features/#character-table", "text": "We put the most frequent special characters in the Character Table . To insert a special character from the Character Table , follow these steps: Press Ctrl + Space on your keyboard several times until you reach the Character Table . Double-click the character you want to insert.", "title": "Character table"}, {"location": "verification/other-useful-features/#autotext", "text": "Alternatively, you may use Autotext entries to insert a special character by typing a shortcut. You can see the list of available shortcuts here . Let's see some examples: For example, to write the abbreviation of square meters (\"m\u00b2\"), you can type shortcut \\sup2 to insert superindex character \u00b2 . Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. \"CO\u2082\". To insert character \u2082 , type shortcut \\sub2 . In order to insert a non-breaking space, type \\nbsp : the auto-completer will propose to insert the character from the autotext list.", "title": "Autotext"}, {"location": "verification/other-useful-features/#running-concordance-searches", "text": "A concordance search allows you to find words and expressions in the translation memory and the glossary. To perform a search follow the steps below: In the active segment, select the word or fragment you want to search for with your mouse. While that part of the text is selected, press Ctrl + F on your keyboard. Press the Search button in the Search window that will open. The list results will be displayed. You can copy (select with mouse and press Ctrl + C on your keyboard) what you need from the results and paste it in the right place in the translation. Note There might be small differences (in punctuation, spacing, etc.) between the text you're searching for and other occurrences of the same text that would prevent an exact match . The option \"Keyword search\" might help overcome that problem, please use it if you don't get the results you were expecting.", "title": "Running concordance searches"}, {"location": "verification/qa-checks/", "text": "QA checks \u00b6 Completion check \u00b6 All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion. Check and fix tags \u00b6 To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation. Check glossary adherence \u00b6 You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "QA checks"}, {"location": "verification/qa-checks/#qa-checks", "text": "", "title": "QA checks"}, {"location": "verification/qa-checks/#completion-check", "text": "All segments in the project must have a translation. To confirm that is the case, please check for completion before your delivery. To check completion, hover with your mouse pointer over the progress status bar, in the bottom right corner of OmegaT's main window. That bar shows some statistics: unique translated (unique left) per file (e.g. 100% (0 left) as above) unique translated (unique left) per project (e.g. 100% (0 left) as above) total number of segments (e.g. 54 as above) If you see something like 100% (0 left) / 100% (0 left), 54 , that means that all 54 segments in the project are translated. If you see a number higher that zero segments left, the translation is not complete. If you have left some segment(s) untranslated, proceed as follows to fix that: Press Esc to close the Project Files window. Press Ctrl + U on your keyboard to jump to the Next Untranslated Segment . Translate the segment Repeat the steps above until no untranslated segments remain. Finally, check the progress status bar again to confirm completion.", "title": "Completion check"}, {"location": "verification/qa-checks/#check-and-fix-tags", "text": "To ensure that all tags have been inserted correctly: Go to Tools > Check Issues to open the Issues window. Tip You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. Press OK . An error report will open. Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor Fix the tag issue (as explained in the Fixing tag issues section) Press the Refresh button to update the list of issues. Avoid Please do not click on \"Apply fix\". Fix each issue manually. Tip If the source text has tags that you do not use in your language, you can insert them at the end of the segment to avoid having false positives in the error report. That should not have an impact on the translation.", "title": "Check and fix tags"}, {"location": "verification/qa-checks/#check-glossary-adherence", "text": "You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout: Go to Tools > Check Issues Make sure the box next to Terminology Issues is ticked Press OK A list of potential errors will open: Go through the issues one by one. For every issue in the list, do the following: Click a row in the list (or click on Jump to Segment ) to open that segment in the editor. Correct the error if necessary. Press the Refresh button to update the list of issues. Info Not all flagged issues are errors by default. In some cases, you may get false positives . In the screenshot below, \"apple trees\" should be translated as \"pommiers\" as in the first segment. In the second segment (active segment) \"apple trees\" was rendered as \"ces arbres\" (backtranslation: these trees) to avoid a repetition that would be disturbing in French. Such deviations from the glossary are intentional, so you would disregard the issue.", "title": "Check glossary adherence"}, {"location": "verification/repetitions/", "text": "Handling repetitions \u00b6 Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances. Identifying repeated segments \u00b6 You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project. Autopropagation \u00b6 When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project. Create alternative translation \u00b6 In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Repetitions"}, {"location": "verification/repetitions/#handling-repetitions", "text": "Some segments may be repeated in the project. By default, the translation of a repeated segment is autopropagated to all its instances.", "title": "Handling repetitions"}, {"location": "verification/repetitions/#identifying-repeated-segments", "text": "You can recognize that you are in a repeated segment because the Segment Properties pane will show a field called Is duplicate (with value FIRST for the first repetitions and value NEXT for any others). Also, the segment number also includes how many more repetitions the active segment has. Also, repeated segments from the second instance onwards have grey font, which could help you realize they are instances of a repeated segment. If you right click on a repeated segment, the contextual menu will list all the other instances. It can be useful to jump to them (by clicking on one of them from the contextual menu) to see the different contexts in which that repeated segment appears in the project.", "title": "Identifying repeated segments"}, {"location": "verification/repetitions/#autopropagation", "text": "When you edit the translation of a repeated segment, as soon as the edit is saved the changes will be automatically reflected in all the repetitions in the project.", "title": "Autopropagation"}, {"location": "verification/repetitions/#create-alternative-translation", "text": "In some cases, two instances of a repeated segment might need to be translated differently in different contexts. In that situation, you may want to modify the translation of only one of the repetitions without altering the rest. In other words, you must create an alternative translation to prevent auto-propagating your update. To create an alternative translation : Right click on the segment and choose Create Alternative Translation from the contextual menu. Edit the translation of the active segment. Press Ctrl + S to register the alternative translation. The Multiple Translations pane will show the different translations. And here's a quick summary: Danger Alternative translations may be treacherous if not applied correctly. Make sure you follow the three steps above precisely. The following video shows how to create alternative translations, enjoy :", "title": "Create alternative translation"}, {"location": "verification/shortcuts/", "text": "a.md-footer__link--next[aria-label^=\"Next:\"], .md-nav__icon { display: none !important; } OmegaT shortcuts \u00b6 Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "Shortcuts"}, {"location": "verification/shortcuts/#omegat-shortcuts", "text": "Here is a table summarizing all functions you need to remember to work in OmegaT. Shortcuts (keyboard combinations) are provided if they are frequently used. Shortcut Action Function Ctrl + L Project > Project Files Open the Project Files window Ctrl + J Go To > Segment Number\u2026 Go to the segment thus numbered Ctrl + Space N/A Open the Auto-Completer and cycle through it (every time you press this shorcut, a different section of the auto-completer is available: tags . character table, etc.) Ctrl + U Go To > Next Untranslated Segment Go to the next untranslated segment Ctrl + T Edit > Insert Next Missing Tag Insert the next missing tag Enter Go to Next Segment Ctrl + I Insert active fuzzy match or selection of fuzzy match N/A Right click > Create Alternative Translation Mark a segment as alternative translation Ctrl + Shift + S Mark a segment as a translation identical to the source Ctrl + Shift + V Tools > Check issues Run the QA checks Ctrl + Shift + D Project > Create Current Translated Document Export or generate the target file for the current document Ctrl + D Project > Create Translated Documents Export or generate all target files N/A Project > Access Project Contents > \u2026 Go to the project folders Shift + F3 Change capitalization of selected text", "title": "OmegaT shortcuts"}, {"location": "verification/tags/", "text": "Tags \u00b6 What are tags \u00b6 The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code: Types of tags \u00b6 There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures Inserting tags \u00b6 Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy : Fixing tag issues \u00b6 All tags you see in the source text should be present in the translation too and in the correct position. You must correct any errors that you may see when that's not the case. You may find two types of issue: A tag or tag pair is missing: in that case, the solution is simply to insert it . A tag is inserted but misplaced: the solution may be either to drag and drop single tags to the correct position, or simply to delete the tag (or tag pair) and insert it again correctly. Warning for RTL languages In right-to-left languages such as Arabic or Hebrew, moving tags will not work. Please delete the tag and insert it again if you work with any of these languages. Deleting tags \u00b6 If you have inserted a tag incorrectly and need to insert it again, double click on the tag to select it in full and press Backspace or Del on your keyboard to delete it first. Moving tags \u00b6 If you have inserted a tag in the wrong position and need to insert it somewhere else, you can simply drag and drop it. Alternatively, you can also delete it and insert it again.", "title": "Tags"}, {"location": "verification/tags/#tags", "text": "", "title": "Tags"}, {"location": "verification/tags/#what-are-tags", "text": "The source text might include some inline codes that stand for formatting or other elements. In OmegaT, those inline codes are handled as tags . For example, part of the source text could be, say, underlined (e.g. the word \"after\" below): I came to this school after the start of this school year. The segment in OmegaT will look like this (notice the paired tags enclosing the word \"after\"): I came to this school after the start of this school year. You will recognize tags because they are in red font . Hover over a tag if you want to see what it stands for. A tooltip will show the original inline code:", "title": "What are tags"}, {"location": "verification/tags/#types-of-tags", "text": "There are two types of tags : standalone tags and paired tags or double tags : Standalone tags : a single tag (e.g. ) which stands for some element that appears at that position, such as a line break, an image, an input field, etc. Paired tags are composed of an opening tag and a closing tag (e.g. and ) and affect the text between them. You can see that two tags are paired when they have the same number. When the source text contains paired tags around a word or expression, you must insert the same paired tags around the part of the translation that corresponds to the formatted word or expression in the source text. For example, here the paired tags represent some formatting that applies to the word \"after\" and its translation \"apr\u00e8s\". I came to this school after the start of this school year. Je suis venu \u00e0 cette \u00e9cole apr\u00e8s le d\u00e9but de cette ann\u00e9e scolaire. When the source text contains one or more standalone tags , you must insert them in the translation in a position that is equivalent to their position in the source text. In the following example, the standalone tag represents a text entry field where the respondent will have to select a number: hours heures", "title": "Types of tags"}, {"location": "verification/tags/#inserting-tags", "text": "Before inserting tags you must know whether it is a standalone tag or two paired tags . To insert paired tags in your translation, proceed as follows: Translate the segment. Select the part of the translation that corresponds to the formatted part in the source text. Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the paired tags you want to insert. Info The auto-completer has several sections, so if you don't see the tags section straight-away, just press Ctrl + Space again to cycle through the auto-completer until you see it. To insert a standalone tag , proceed as follows: Click on the position where you want to insert the tag (before, after or while translating). Press Ctrl + Space to launch the auto-completer. In the tags section of the auto-completer, select the standalone tag you want to insert. You can also insert a tag one by one with shortcut Ctrl + T . The following video shows how to handle tags , enjoy :", "title": "Inserting tags"}, {"location": "verification/tags/#fixing-tag-issues", "text": "All tags you see in the source text should be present in the translation too and in the correct position. You must correct any errors that you may see when that's not the case. You may find two types of issue: A tag or tag pair is missing: in that case, the solution is simply to insert it . A tag is inserted but misplaced: the solution may be either to drag and drop single tags to the correct position, or simply to delete the tag (or tag pair) and insert it again correctly. Warning for RTL languages In right-to-left languages such as Arabic or Hebrew, moving tags will not work. Please delete the tag and insert it again if you work with any of these languages.", "title": "Fixing tag issues"}, {"location": "verification/tags/#deleting-tags", "text": "If you have inserted a tag incorrectly and need to insert it again, double click on the tag to select it in full and press Backspace or Del on your keyboard to delete it first.", "title": "Deleting tags"}, {"location": "verification/tags/#moving-tags", "text": "If you have inserted a tag in the wrong position and need to insert it somewhere else, you can simply drag and drop it. Alternatively, you can also delete it and insert it again.", "title": "Moving tags"}, {"location": "misc/tags/", "text": "Adaptation \u00b6 Adaptation Editing Proofreading \u00b6 Editing Review Reconciliation \u00b6 Reconciliation Review \u00b6 Editing Editing Review Revision \u00b6 Editing Review Translation \u00b6 Translation Verification \u00b6 Editing Verification", "title": "Tags"}, {"location": "misc/tags/#adaptation", "text": "Adaptation Editing", "title": "Adaptation"}, {"location": "misc/tags/#proofreading", "text": "Editing Review", "title": "Proofreading"}, {"location": "misc/tags/#reconciliation", "text": "Reconciliation", "title": "Reconciliation"}, {"location": "misc/tags/#review", "text": "Editing Editing Review", "title": "Review"}, {"location": "misc/tags/#revision", "text": "Editing Review", "title": "Revision"}, {"location": "misc/tags/#translation", "text": "Translation", "title": "Translation"}, {"location": "misc/tags/#verification", "text": "Editing Verification", "title": "Verification"}]} \ No newline at end of file diff --git a/sitemap.xml.gz b/sitemap.xml.gz index 82e17924..e5f7a7ca 100644 Binary files a/sitemap.xml.gz and b/sitemap.xml.gz differ diff --git a/verification/install-and-setup-macos/index.html b/verification/install-and-setup-macos/index.html index 278e94fb..a3b5834e 100644 --- a/verification/install-and-setup-macos/index.html +++ b/verification/install-and-setup-macos/index.html @@ -2321,7 +2321,7 @@

    Installation

  • Click on the button below to download OmegaT 5.7.2. This is a custom version prepared by cApStAn which includes several bug fixes and enhancements not available in other versions.

    -

    Download OmegaT 5.7.2

    +

    Download OmegaT 5.7.2

  • If you're using Safari, then the file will be unzipped automatically when the download ends.​ If you use another browser, double-click the file when the download ends to unzip it.

    diff --git a/verification/install-and-setup/index.html b/verification/install-and-setup/index.html index 7ad478cd..8ea9b2f3 100644 --- a/verification/install-and-setup/index.html +++ b/verification/install-and-setup/index.html @@ -2348,7 +2348,7 @@

    ConfigurationRun OmegaT and go to Tools > Scripting to open your scripting console, In OmegaT 5.7.1, please open the scripting console. Check whethers you have a script called "Update Customisation Bundle (v572)":

    Warning

    -

    If you don't see the "v752" bit, then it's not the script we're looking for. See next step to fetch the script.

    +

    If you don't see the "v572" bit, then it's not the script we're looking for. See next step to fetch the script.

    If the script "Update Customisation Bundle (v572)" is there, please click on it to select it and press the Run button (at the bottom left) to run it. The script will run to update your config files and will quit OmegaT. After that, skip the next step and jump directly to the installation section.