TM, segmentation, introduction? Thread poster: kristienw
|
|---|
Hello,
I am currently helping a young developer translating his websites (English - French - Dutch). I would like to create a translation memory with the most common words (ok, save, decline, ...) that I can send him and other translators.
Is this possible with OmegaT (version 1.0M3.2) and how? And next: how do we use the TM? Copy it to "translation memory" in the project folder?
I also have encountered a problem with segmentation: he sends me the text f... See more Hello,
I am currently helping a young developer translating his websites (English - French - Dutch). I would like to create a translation memory with the most common words (ok, save, decline, ...) that I can send him and other translators.
Is this possible with OmegaT (version 1.0M3.2) and how? And next: how do we use the TM? Copy it to "translation memory" in the project folder?
I also have encountered a problem with segmentation: he sends me the text files as .txt, and when I load them in OmegaT, it does not segment per line but per paragraph. Since each line needs its own translation, I want is segmented per line. How do I do that?
And last, but not least, where can I find a good introduction to this OmegaT version (I've found some for older versions).
Thank you! ▲ Collapse
| | | | Susan Welsh 
United States
Local time: 23:56
Russian to English
+ ...
| See the documentation at omegat.org | Apr 21, 2014 |
All of the information you are looking for is available at the website. Here is the link to English documentation, but there is documentation in other languages as well.
http://www.omegat.org/en/documentation.php
There is a complete user's manual, a tutorial for beginners, and several useful videos.
I'm not sure what "version 1.0M3.2" is. We are now on version 3.1.0. S... See more All of the information you are looking for is available at the website. Here is the link to English documentation, but there is documentation in other languages as well.
http://www.omegat.org/en/documentation.php
There is a complete user's manual, a tutorial for beginners, and several useful videos.
I'm not sure what "version 1.0M3.2" is. We are now on version 3.1.0. So maybe you made a typo, but it looks like you have an ancient version.
What you describe as a TM is not a TM, but a glossary. ▲ Collapse
| | | | esperantisto
Local time: 06:56
Member (2006)
English to Russian
+ ...
SITE LOCALIZER | Use genuine OmegaT | Apr 22, 2014 |
kristienw wrote:
OmegaT (version 1.0M3.2)
The version number makes me think that you're using omegat+. It's a fork of OmegaT based on very old code. You'd better use genuine OmegaT and, yes, read the user manual.
| | | |
Thank you for your help!
Yesterday evening, I've browsed some websites and found out that this version is indeed very old... I'll download the new version and hope the tutorial "works" for this one (the version I had did not have all the buttons etc).
| | |
|
|
|
Samuel Murray
Netherlands
Local time: 05:56
Member (2006)
English to Afrikaans
+ ...
| Yes, you have the wrong "OmegaT" there... | Apr 22, 2014 |
kristienw wrote:
Is this possible with OmegaT (version 1.0M3.2) and how?
If your "OmegaT" has a version number like "1.0M3.2" then it is not "OmegaT" but an offshoot called "OmegaT+" which was developed by a disgruntled member of the OmegaT development team. For a few short weeks after its creation, OmegaT+ had better features than OmegaT. However, there have been no new versions of OmegaT+ plus for many years, and its developer had changed certain aspects of it to ensure that it is incompatible with the original OmegaT.
My little introductory video (for version 2.0.0) should still be mostly valid for the latest version of OmegaT (which is version 3.1.0), although it sounds as if you want to use the Glossary feature, which is not covered in my video. It is now also much, much easier to work with tags in OmegaT than in version 2.0.0.
You can download OmegaT here:
http://sourceforge.net/projects/omegat/files/OmegaT%20-%20Latest/
(note that this is the "bleeding edge" version, which means that the documentation or help files are slightly outdated for the most recently added features).
And next: how do we use the TM? Copy it to "translation memory" in the project folder?
From your description I get the impression that you want to create a glossary, not a TM, so keep that in mind when you read the user manual. The user manual (of the real OmegaT) will explain what to do with the TM and the glossary.
I also have encountered a problem with segmentation: he sends me the text files as .txt, and when I load them in OmegaT, it does not segment per line but per paragraph. Since each line needs its own translation, I want is segmented per line. How do I do that?
Is it a plain text file or is it some kind of specially formatted text file?
To tell OmegaT to segment a text file by line break instead of by double line breaks, you have to edit the "file filter".
| | | | Didier Briel
France
Local time: 05:56
English to French
+ ...
| In localisation, TMs can be used for terms | Apr 22, 2014 |
Samuel Murray wrote: kristienw wrote: And next: how do we use the TM? Copy it to "translation memory" in the project folder? From your description I get the impression that you want to create a glossary, not a TM, so keep that in mind when you read the user manual. The user manual (of the real OmegaT) will explain what to do with the TM and the glossary.
In localisation, it is often useful to have a TM with the user interface terms (in addition to the same information used as a glossary). Perhaps that's what kristienw has in mind. The answer is, yes, copy the translation memory to the /tm folder of the project.
I also have encountered a problem with segmentation: he sends me the text files as .txt, and when I load them in OmegaT, it does not segment per line but per paragraph. Since each line needs its own translation, I want is segmented per line. How do I do that? Is it a plain text file or is it some kind of specially formatted text file?
To tell OmegaT to segment a text file by line break instead of by double line breaks, you have to edit the "file filter".
Yes. Options > File Filters > Text > Options > Segment source text into paragraphs on: Line breaks.
Didier
| | | | There is no moderator assigned specifically to this forum. To report site rules violations or get help, please contact site staff » TM, segmentation, introduction? | CafeTran Espresso | You've never met a CAT tool this clever!
Translate faster & easier, using a sophisticated CAT tool built by a translator / developer.
Accept jobs from clients who use Trados, MemoQ, Wordfast & major CAT tools.
Download and start using CafeTran Espresso -- for free
Buy now! » |
| | TM-Town | Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
