How to fix wrong punctuation from source in target Initiator des Themas: Roman Voříšek
|
|---|
Hello everyone,
please, I need help - I have a huge source file (more than 1000 pages). In this source, there is a lot of mistakes such as two dots, missing dot, space before colon etc. I would like to fix these kind of mistakes in the target. But if I fix it during the translations, OmegaT considers the segment as non-translated, probably because of different "pattern" of the segment / segment rules.
Because of size of the document, I can't fix such a mistakes before translat... See more Hello everyone,
please, I need help - I have a huge source file (more than 1000 pages). In this source, there is a lot of mistakes such as two dots, missing dot, space before colon etc. I would like to fix these kind of mistakes in the target. But if I fix it during the translations, OmegaT considers the segment as non-translated, probably because of different "pattern" of the segment / segment rules.
Because of size of the document, I can't fix such a mistakes before translation. I would like to force such segments as translated. Is it possible?
The document is updated twice a year and I just would like to jump over rally non-translated segments (the new ones) and not over the segments that have been translated but with corrected punctuation.
Thank you very much in advance. ▲ Collapse
| | | | | No acceptable way | Nov 8, 2021 |
Roman Voříšek wrote:
2. Because of size of the document, I can't fix such a mistakes before translation. I would like to force such segments as translated. Is it possible?
1. The document is updated twice a year and I just would like to jump over rally non-translated segments
OmegaT open a whole project and its files. To fix mistakes in source project is on author of text.
If translator "splits or merges" segments or their parts, the segmentation is changed and project is re-opened for translating.
It can be accepted by small project only.
Changing of segmentation rules in OmegaT: set-up paragraph instead o sentence segmentation.
Milan
[Edited at 2021-11-08 15:45 GMT]
| | | | Dragomir Kovacevic (X) 
Italien
Local time: 01:37
Italienisch > Serbisch
+ ...
| in project_save.tmx | Nov 8, 2021 |
Make a copy of this file, positioned in omegat folder within your project.
Open it with some powerful text editor, like Notepad++; if not with it, even with Notepad (try), in order to execute one series of different commands; one of them might be:
[space][dot]
replace all with
[dot]
In Notepad++, there is a very sofisticated Search menu; in your case it is the sub-menu "Replace", and more in it...
After refurbishing of this copy of project... See more Make a copy of this file, positioned in omegat folder within your project.
Open it with some powerful text editor, like Notepad++; if not with it, even with Notepad (try), in order to execute one series of different commands; one of them might be:
[space][dot]
replace all with
[dot]
In Notepad++, there is a very sofisticated Search menu; in your case it is the sub-menu "Replace", and more in it...
After refurbishing of this copy of project_save.tmx file, put it into the omegat folder (or it can be already there, why not), zip-archive the real project_save.tmx, and replace it with your edited file; of course you need to rename the edited file in order that it bears the exact name as OmegaT requires.
And after that, re-open the project.
That will fix your previously translated and compiled material.
You can try FIRST, to zip-archive the previous files in Source folder; so the above project_save.tmx file, wont' ENCOUNTER any of old files, but just the very ones you work on.
All above concerns working on engine TM; we translators usually fix all these things in real source file, but it might be tricky if you work with full xml files like xliff kind.
Roman Voříšek wrote:
Hello everyone,
please, I need help - I have a huge source file (more than 1000 pages). In this source, there is a lot of mistakes such as two dots, missing dot, space before colon etc. I would like to fix these kind of mistakes in the target. But if I fix it during the translations, OmegaT considers the segment as non-translated, probably because of different "pattern" of the segment / segment rules.
Because of size of the document, I can't fix such a mistakes before translation. I would like to force such segments as translated. Is it possible?
The document is updated twice a year and I just would like to jump over rally non-translated segments (the new ones) and not over the segments that have been translated but with corrected punctuation.
Thank you very much in advance.
[Edited at 2021-11-08 12:44 GMT]
[Edited at 2021-11-08 12:46 GMT]
[Edited at 2021-11-08 12:51 GMT] ▲ Collapse
| | | | 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 » How to fix wrong punctuation from source in target | LinguaCore |
|---|
AI Translation at Your Fingertips
The underlying LLM technology of LinguaCore offers AI translations of unprecedented quality. Quick and simple. Add a human linguistic review at the end for expert-level quality at a fraction of the cost and time.
More info » |
| | 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 » |
|
| | | | X Sign in to your ProZ.com account... | | | | | |
Login to reply/comment 
