In some cases, you may not wish to modify the translation of repeated segments. If you want your edits to be autopropagated, nothing special needs to be done: just edit one segment in a group of repetitions and save. If however, due to a different context, you may need to change the translation of only ONE of the repeated segments:
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.
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.
You may need to type special characters such as:
«»
„“
‘’
×
π
÷
≤
≠
√
₂
²
³
®
™
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²"), you can type shortcut \sup2 to insert superindex character ².
\sup2
Another example: in chemical formulas, the number of atoms is often noted with a subindex number, e.g. "CO₂". To insert character ₂, type shortcut \sub2. - +
\sub2
In order to insert a non-breaking space, type \nbsp: the auto-completer will propose to insert the character from the autotext list. -
\nbsp
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:
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.
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:
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:
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 :
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.
When the active segment contains a source term that is in the glossary, it is underlined in blue in the source 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.
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:
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.
Below you will find the most common HTML tags you may encounter.
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.
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.
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.
!!! 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.
Right-click on the button below and select "Save Link As" 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:
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.
Tools > Scripting > File > Open script
To do that, simply move the installed OmegaT.app to Trash.
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. If you use another browser, double-click the file when the download ends to unzip it.
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 +Version: OmegaT-5.7.2_0_a978d82ee Platform: [your operating system] Java: 11.0.19 amd64
Version: OmegaT-5.7.2_0_a978d82ee +
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.
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.
s
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.
C:\Users\USER\AppData\Local\Programs\OmegaT
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.
See the section below to know how to run a few post-installation checks to confirm that everything is okay.
The steps above will normally get up and running, but but it's always a good idea to check that everything is okay just in case. One stick in time saves nine. These are the things that you can check:
OmegaT version
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] +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
> Version: OmegaT-5.7.2_0_a978d82ee +> Platform: [your operating system] > Java: 11.0.19 amd64
Custom configuration version
To confirm that your custom configuration is up to date, you can go to Options > Access Configuration Folder and find a file called local_version_notes.txt there.
local_version_notes.txt
If you open that file, the line at the top showing the most recent update should be the same as the one you can see in page https://cat.capstan.be/OmegaT/v572/.
OMT un/packaging menu entries
Even if you don't use OMT packages, you should have three entries under the Project menu in OmegaT:
Scripts and script shortcuts
In the Tools menu, under Scripting, you should see a list of 12 script shortcuts.
The script shortcuts might be updated occasionally, don't worry if your list is not identical to the screenshot above.
Also, if you open the scripting dialog, you should see the whole list of scripts on the left-hand side.
- -
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:
Do the same to insert (part of) other matches if appropriate or finish translating the segment.
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.
/target
Info
The target file will be overwritten every time you press Ctrl+Shift+D
In order to insert non-breaking spaces in OmegaT, type \nbsp. The auto-completer will propose to insert a non-breaking space.
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.
To deliver from a team project:
That's it!
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.
.omt
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:
100% (0 left)
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)
54
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.
100% (0 left) / 100% (0 left), 54
If you have left some segment(s) untranslated, proceed as follows to fix that:
Repeat the steps above until no untranslated segments remain.
Finally, check the progress status bar again to confirm completion.
Make sure the box next to Terminology Issues is ticked
Press OK
Go through the issues one by one. For every issue in the list, do the following:
A list of potential errors will open:
Click a row in the list (or click on Jump to Segment) to open that segment in the editor.
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.
 +
To ensure that all tags have been inserted correctly:
!!! tip inline end + You may untick the other checks (Spelling, Terminology, LanguageTool) if you want to focus on tags only first. +
Go to Tools > Check Issues to open the Issues window.
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.
Click a row in the list (or click on Jump to Segment) to open that segment in the editor
Avoid
Please do not click on "Apply fix". Fix each issue manually.
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.
You can check whether the translation adheres to the glossary and key terms have been translated consistently throughout:
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:
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.
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.
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. @@ -2286,25 +2312,24 @@ What are tags 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¶ There are two types of tags: standalone tags and paired tags or double tags: - -Standalone tags: a single tag (e.g. <x1/>) 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. <g2> and </g2>) and affect the text between them. You can see that two tags are paired when they have the same number. - - +Standalone tags: a single tag (e.g. <x1/>) 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. <g2> and </g2>) 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. @@ -2314,42 +2339,41 @@ Types of tags<g1>après</g1> le début de cette année scolaire.
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:
- +
There are two types of tags: standalone tags and paired tags or double tags:
Standalone tags: a single tag (e.g. <x1/>) 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. <g2> and </g2>) 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.
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:
-<x1/> hours -<x1/> heures +<x1/> hours > <x1/> heures
<x1/> hours -<x1/> heures
<x1/> hours > <x1/> heures
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:
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:
You can also insert a tag one by one with shortcut Ctrl+T.
The following video shows how to handle tags, enjoy :
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.
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.
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.
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.
Also, the segment number also includes how many more repetitions the active segment has.
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.
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:
The Multiple Translations pane will show the different translations.
And here's a quick summary: -
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 :
Remember that you can't create an alternative translation if the segment already has an alternative translation. See the section below to learn how you can recognize an alternative translation.
If you must modify an existing alternative translation, simply edit the target text and save (Ctrl+S).
Here's how you can recognize whether a segment has an alternative translation.
On the one hand, if a segment has an alternative translation, the Segment properties pane will show a property called Is alternative with value true. That field will flash in orange when you active the segment or when you save the project while that segment is active.
true
On the other hand, you will notice that the Multiple translations pane shows that translation and the context properties that the alternative translation binds too (typically the file name and some identifier, e.g. the segment ID or a key).
Finally, and most eloquent, you can see that the segment has an alternative translation if the Create Alternative Translation item in the segment's contextual menu (or the Edit menu) is grayed out and cannot be selected.
If for some reason an existing alternative translation is unnecessary and you would like to restore auto-propagation into that segment, the simplest way is to just delete the alternative translation. To do that, follow these simple steps:
I came to this school after the start of this school year. @@ -2285,9 +2311,10 @@ What are tags 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: - + + - + @@ -2330,12 +2357,12 @@ What are tags - + - + - + diff --git a/_includes/omt-tag-iss/index.html b/en/_includes/omt-tag-iss/index.html old mode 100644 new mode 100755 similarity index 91% rename from _includes/omt-tag-iss/index.html rename to en/_includes/omt-tag-iss/index.html index cabc04f6..9650f8a5 --- a/_includes/omt-tag-iss/index.html +++ b/en/_includes/omt-tag-iss/index.html @@ -8,9 +8,9 @@ - + - + @@ -19,10 +19,10 @@ - + - + @@ -39,9 +39,9 @@ - + - + @@ -84,9 +84,9 @@ - + - + @@ -144,6 +144,32 @@ + + + + + + + + + + + + English + + + + + + Russian + + + + + + + + @@ -199,7 +225,7 @@ - + Contents @@ -356,9 +382,9 @@ - + - + OmegaT guides [cApStAn] @@ -374,7 +400,7 @@ - + Contents @@ -2275,10 +2301,10 @@ Omt tag iss Fixing tag issues¶ 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: +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 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. @@ -2286,31 +2312,31 @@ Fixing tag issues 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. +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¶ 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¶ 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. - + - @@ -2355,12 +2381,12 @@ Moving tags - + - + - + diff --git a/_includes/omt-tag-recog/index.html b/en/_includes/omt-tag-recog/index.html old mode 100644 new mode 100755 similarity index 90% rename from _includes/omt-tag-recog/index.html rename to en/_includes/omt-tag-recog/index.html index c6840c81..3123fc58 --- a/_includes/omt-tag-recog/index.html +++ b/en/_includes/omt-tag-recog/index.html @@ -8,9 +8,9 @@ - + - + @@ -19,10 +19,10 @@ - + - + @@ -39,9 +39,9 @@ - + - + @@ -84,9 +84,9 @@ - + - + @@ -144,6 +144,32 @@ + + + + + + + + + + + + English + + + + + + Russian + + + + + + + + @@ -199,7 +225,7 @@ - + Contents @@ -356,9 +382,9 @@ - + - + OmegaT guides [cApStAn] @@ -374,7 +400,7 @@ - + Contents @@ -2276,17 +2302,15 @@ Omt tag recog Types of tags¶ There are two types of tags: standalone tags and paired tags or double tags: - -Standalone tags: a single tag (e.g. <x1/>) 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. <g2> and </g2>) and affect the text between them. You can see that two tags are paired when they have the same number. - - +Standalone tags: a single tag (e.g. <x1/>) 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. <g2> and </g2>) 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. @@ -2296,15 +2320,14 @@ Types of tags<g1>après</g1> le début de cette année scolaire.
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.
I came to this school after the start of this school year. @@ -2286,25 +2312,24 @@ What are tags 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¶ There are two types of tags: standalone tags and paired tags or double tags: - -Standalone tags: a single tag (e.g. <x1/>) 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. <g2> and </g2>) and affect the text between them. You can see that two tags are paired when they have the same number. - - +Standalone tags: a single tag (e.g. <x1/>) 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. <g2> and </g2>) 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. @@ -2314,42 +2339,41 @@ Types of tags<g1>après</g1> le début de cette année scolaire.
Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here. -
Please give some thought to the organization of your files and folders before you proceed with the steps below. We provide some tips here.
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.
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 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.
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.
The URL should look a bit like this: https://domain.com/path/to/repo-name.git.
https://domain.com/path/to/repo-name.git
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.
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).
Work
C:\Users\USER\Work\
USER
Danger ❗❗❗
💀 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 or a network drive.
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:
C:\Users\USER\repo-name
C:\Users\USER\Work\repo-name
For example:
Make sure there's a slash between every two folders in your path.
+ 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. +
<!-- To do that:
+ Copy the path to the location where you want to create the project, e.g. `C:/Work/`. + ++ Then, in the **New Local Project Folder** field, select the part of the path up to the slash before the project folder and delete it. ++ Then, press ++ctrl+v++ to paste your path in replacement of the deleted part. + +!!! Caution + Make sure there's a slash between the path that you paste and the project folder name. +
-->
When you are done working for the day, quit OmegaT (Ctrl+Q).
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:
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.
OmegaT is the open source computer-assisted translation tool (CAT tool) which we use to translate, reconcile, adapt, review and verify materials. You must install OmegaT and set it up with some additional files, in order to ensure an optimal interface and compatibility with the project we'll prepare for you.
In particular, OmegaT 6.1 is necessary to work with Myanmar languages.
Please:
@@ -2310,74 +2337,78 @@ 1.1. Download installer It's a safe download, even if your browser might not trust the file. 1.2. Install OmegaT¶ -In order to proceed with the installation, please follow these steps: +In order to proceed with the installation, please follow these steps: Double click the executable file (e.g. OmegaT_6.1.0_Beta_Windows_64_Signed.exe) that you have downloaded. -Windows could display a blue screen saying that it might be risky to install OmegaT. If that's the case, click on "More info" - -That will show information about the application and the publisher. You can be confidently press the Run anyway button as long as you see the publisher is cApStAn. - +Windows could display a blue screen saying that it might be risky to install OmegaT. If that's the case, click on "More info" + + +That will show information about the application and the publisher. You can be confidently press the Run anyway button as long as you see the publisher is cApStAn. + + If you see the following screen, click on "Yes": - - - - -Choose (or keep) English as the language of the installation: - - - - -Please also use English as the language of the OmegaT user interface: - - - - -In the License Agreement screen, please select "I accept the agreement” and click “Next”: - + + + + +Choose (or keep) English as the language of the installation: + + + + +Please also use English as the language of the OmegaT user interface: + + + + +In the License Agreement screen, please select "I accept the agreement” and click “Next”: + + + In all the next dialogs, just press “Next” to use the default options until you reach the Ready to Install screen. We recommend that you do not change the default installation path, just click Next in this screen: - - - -We also recommend that you create a desktop shortcut (if that's a useful way for you to run OmegaT): - - - -In the Ready to Install screen, click on “Install”. - - - -When the installation is finalized, you will see the last screen: - + + +We also recommend that you create a desktop shortcut (if that's a useful way for you to run OmegaT): + + + +In the Ready to Install screen, click on “Install”. + + + +When the installation is finalized, you will see the last screen: + + After that, you'll be able to run OmegaT from the OmegaT desktop shortcut icon (if you have created one) or from the applications menu. 1.3. Configure OmegaT¶ -To configure OmegaT, please do: +To configure OmegaT, please do: Launch OmegaT once and then close it. Launch OmegaT again and let it run for a few seconds. Close OmegaT. During the second execution, OmegaT will be configured automatically in the brackground. When you run OmegaT for the third time, you will be able to start working on your project(s). - - - - +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¶ -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. +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. @@ -2388,37 +2415,36 @@ Accessing a new project 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 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¶ -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: +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. - - - +
It's a safe download, even if your browser might not trust the file.
In order to proceed with the installation, please follow these steps:
Double click the executable file (e.g. OmegaT_6.1.0_Beta_Windows_64_Signed.exe) that you have downloaded.
OmegaT_6.1.0_Beta_Windows_64_Signed.exe
Windows could display a blue screen saying that it might be risky to install OmegaT. If that's the case, click on "More info"
That will show information about the application and the publisher. You can be confidently press the Run anyway button as long as you see the publisher is cApStAn.
If you see the following screen, click on "Yes":
Choose (or keep) English as the language of the installation:
Please also use English as the language of the OmegaT user interface:
In the License Agreement screen, please select "I accept the agreement” and click “Next”:
In all the next dialogs, just press “Next” to use the default options until you reach the Ready to Install screen.
We recommend that you do not change the default installation path, just click Next in this screen:
We also recommend that you create a desktop shortcut (if that's a useful way for you to run OmegaT):
In the Ready to Install screen, click on “Install”.
When the installation is finalized, you will see the last screen:
After that, you'll be able to run OmegaT from the OmegaT desktop shortcut icon (if you have created one) or from the applications menu.
To configure OmegaT, please do:
During the second execution, OmegaT will be configured automatically in the brackground. When you run OmegaT for the third time, you will be able to start working on your project(s).