Mark segments as translated Initiator des Themas: erikdeboeck
|
|---|
I've got a project in which a lot of terminology will be carried over from English to Dutch. There's an entire chapter explaining the terminology, in which the terms themselves are subtitles.
These titles are all separate segments in OmegaT. But the "translation" will be identical to the source segment.
Is there a way to mark these segments as translated?
I know it's possible to allow source and translation to be the same for the ... See more I've got a project in which a lot of terminology will be carried over from English to Dutch. There's an entire chapter explaining the terminology, in which the terms themselves are subtitles.
These titles are all separate segments in OmegaT. But the "translation" will be identical to the source segment.
Is there a way to mark these segments as translated?
I know it's possible to allow source and translation to be the same for the entire document, but that's not what I want. By merely scrolling through the segments, a lot of them would be marked as translated, which would be a recipe for disaster.
I also don't want to leave the translation field empty, because I always work with the source text as raw material to work with.
Surely I'm not the first one to encounter this problem?
Thanks in advance for your help! ▲ Collapse
| | | | Samuel Murray 
Niederlande
Local time: 13:57
Mitglied (2006)
Englisch > Afrikaans
+ ...
erikdeboeck wrote:
Is there a way to mark these segments as translated?
No.
The solution here is source text preparation. You should edit the original source file so that the source text of each segment would be different from its translation in OmegaT. For example, add the letters DNT ("do not translate") to the start or end of the segment in the original source text. Reload your project, and then translate those segments without the "DNT". Or add "!!!" anywhere in the middle of the segment.
Or, replace all spaces in those segments with an underscore (and add one more just in case you have segments without spaces). This will also prevent those segments from showing up as fuzzy matches elsewhere.
| | | |
I see...
Thanks for your answer, although it's a disappointing one
Maybe an idea for a feature in future versions...?
| | | | Jiří Štros
Tschechische Republik
Local time: 13:57
Koreanisch > Tschechisch
+ ...
If you right click the identical text, there is a pop-up saying "Register Identical Translation".
I think this is what you were looking for?
Omega 5.4.1
| | |
|
|
|
| In TMX is no field to save a status of translation | Mar 31, 2021 |
Samuel Murray wrote:
erikdeboeck wrote:
Is there a way to mark these segments as translated?
No.
A status field is in XLIFF file. OmegaT saves translation into TMX.
I do not remember if there is a workaround, i.e. in DGT-OmegaT.
Some solutions are in team projects - I have no practice with them.
When I translate downloaded web sites, I manually go through each file a I copy source to target segment with links, product and company names. OmegaT shows me segments as translated.
Then I run a script for extracting untranslated segments. Now can I translate with TMX or use MT or my head.
Milan
| | | | Samuel Murray
Niederlande
Local time: 13:57
Mitglied (2006)
Englisch > Afrikaans
+ ...
erikdeboeck wrote:
These titles are all separate segments in OmegaT. But the "translation" will be identical to the source segment.
Is there a way to mark these segments as translated?
More options:
OmegaT will always write the source text for untranslated segments when creating the target file, unless you right-click the active segment and select "Set empty translation". (This will cause to appear in the editor when the segment is not active, but the segment will be empty when you make it the active segment.) If you **do** want the source text to appear in the final file, but you want the segment to be marked as translated, choose "Register identical translation" when you right-click the segment. "Identical translation" is the OmegaT developers' way of saying "source = target".
How things behave depends on whether Autopropagation is enabled in Project Properties. If Autopropagation is not enabled, each segment can have a unique translation, even if two or more segments are identical to each other. If Autopropagation is enabled, then all identical source segments will always get the same translation, unless you mark individual segments as something different.
When Autopropagation is enabled, two new items will be present in the right-click menu called "Use as Default translation" and "Use as alternative translation". Select "Use as Default translation" if you want the segment's current translation to be (or to become) the translation that is propagated to all other repeating segments that haven't been marked as alternative yet. Use "Use as Alternative translation" if you want the current segment's translation to be unique (i.e. protected against autopropagation from other segments).
| | | | Dieses Forum wird von keinem Moderator betreut. Um Verstöße gegen die ProZ.com-Regeln zu melden oder um Hilfe zu erhalten, wenden Sie sich bitte an unsere ProZ.com-Mitarbeiter » Mark segments as translated | Pastey | Your smart companion app
Pastey is an innovative desktop application that bridges the gap between human expertise and artificial intelligence. With intuitive keyboard shortcuts, Pastey transforms your source text into AI-powered draft translations.
Find out more » |
| | Protemos translation business management system | Create your account in minutes, and start working! 3-month trial for agencies, and free for freelancers!
The system lets you keep client/vendor database, with contacts and rates, manage projects and assign jobs to vendors, issue invoices, track payments, store and manage project files, generate business reports on turnover profit per client/manager etc.
More info » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
