I'm so happy seeing a Linux-user translator. I was installing this on my Linux Mint, having some difficulties, and ending up breaking my setting and finally, installing a new distro (I gave up finding out how to fix it, LOL). It's awesome though since this CAT tool is free. For me, I've been using Matecat and it has helped me a lot. Cool video anyway. Danke.
Basically they are just tab-separated text-files (encoded in UTF8, IIRC). The first column contains the word in the source-language, the second column contains a definition in the target-language. A third column can be used for more details. If one defines multiple lines with the same word, all possible "matches" will be shown within OmegaT. To create, use a text-editor (which will not replace TABs with spaces), or use spreadsheets from Open/Libre-Office, export as CSV (with tabs as delimiter)
Did you update to a newer version of OmegaT? If not, please try it out, as the later versions have new features and bugfixes too. About your unreadable target-document: if your translation is displayed correctly within OmegaT - maybe your external txt-viewer can not handle Unicode (UTF-8) or is using the wrong encoding? At OmegaT's website you will find some documentation, HOWTOs and a FAQ. If this does not help, there is also an active yahoo-usergroup called "omegat" :-) Good luck! ;)
Hi, thanks for the nice video. I have a question. Sometimes - or the last time - I dragged an .odt-folder into OmegaT, it separates the text incredibly strangely. For example, it separates the word t from ranslation, and so on, for no particular reason. How am I supposed to translated a the letter t and ranslation? The original text is correct. Do you know how I can fix this? I would be extremely grateful for your help. Thank you.
Mhmmm, the only thing that comes to my mind: >tags< in the source-document. Maybe you can try to activate the check-box called "Remove Tags" under "Properties" (Ctrl-E) of the project?
Thank you for sharing this tutorial! The output file turned out to be a TXT document file, is there any possibility to export our translation in a word document instead? Thank you!
That sounds interesting. Normally a .doc should result in a .doc-file. What kind of format was the source-file? PS: If the source was a txt-file, the result will be too. But with LibreOffice or MS Word all txt-files can be opened, formatted and saved as .doc-files.
i have a problem went i translate a word it appears on the left side and the word translated doesn't disappear i hope you could help and the vidéo was very informative 👌
Thank you! Do you have any expierience on translating latex files with OmegaT? I failed to do that, the target files have line endings removed which make the output latex files corrupted and impossible to generate pdf on the fly.
For this video I used version 2.2.3_4 ... currently version 2.3.0 is considered the standard-version, while 2.5.x is under development (and is looking quite stable already). Get your version 2.3.x from Omegat . org -> "Download OmegaT" - it is free software.
Thanks a lot for the video! I would like to ask if this free software is as effective/useful as the paid ones (e.g. Trados)? I mean, is it worth it to buy Trados, or is it that that OmegaT does the job? Thank you!
I can not open the target document, it says that there ist an error with the subdocument "content.xml" (The source document ist just text, *.odt) Could you help me?
The odt is "just" a container (like .docx and many other newer formats), basically packing/zipping various (sub-)files into one. The underlying files are indeed mostly xml-based, just as your "content.xml". Since I don't know what happened to your specific file, I just have few ideas to try out: * use zip or 7z to check the content of your odt ... is there a content.xml? * update to the latest version of OmegaT (if not done already) * try converting your original source into a different format, e.g. doc, docx, or (lastly) even xml .. both LibreOffice/OpenOffice can export into those formats Hope that helps. PS: Beyond that it might be a good idea to check the bugtracker for known issues (or even open a ticket there): sourceforge.net/p/omegat/bugs/
thanks for the video! I have a problem, I closed the project I made and now I cannot get in because I get this message: Failed to load specific project! java.lang.NullPointerException. Any ides what this means ? thanks a lot!
That is a big question. And I am not part of the coders developing OmegaT, but this looks like a bug or at least some unhandled condition (e.g. files were renamed or moved, etc.) leading to this error. The project is hosted at SourceForge: sourceforge.net/projects/omegat/ - there is a ticket-tab with a list of reported bugs. Unfortunately I could not find your problem in the list of open issues. So maybe you can try a different (newer? or older??) version of OmegaT? Maybe it was fixed/disappeared at one point? Hope you can get rid of this problem! *fingers crossed* ;-)
Sorry, I do not understand your question. 😕 Do you mean TH-cam-Videos/Tutorials? There are so many out there by now, I really do not know. This video here is for those, who know what they want to achieve. ... and how to start working in OmegaT. Side-note: with the amazing Online-translations nowadays, CAT-tools become less and less important. I guess they are only helpful for long or complex/technical/scientific texts, where domain-knowledge is required and computer-translations fail or produce dubious results.
Hi, probably a dumb question, but kindly have mercy. Since my source document is in paper form, and I'd need to do a hell of a job, to type it all down - is it possible to work without the source-document? If not with OmegaT, which Cat Tool would be suitable for such work?
Mhmmm... that sounds challenging. So why not split up the task? 1. get the source-text into any digital format (via OCR), *then* 2. translate And yes, both steps will require manual labour... if aiming for quality. The better the source, the easier the translation (or any other translations to come). Just my 2 cents. Not sure whether this helps with your particular issue. In the end ... your question has soooo/too many variables ... but maybe answering the most relevant/critical questions (pick yours) can help to find a way on how to solve the issue? e.g. Is money the issue? To what extend? Is it time-critical? Is it a hobby? Are the sources sensitive/confidential or public domain? Do you trust big players (e.g. Google)? How good is the quality of the sources? Is the format and layout of the resulting document of any importance? How many pages are we talking about? What level of proficiency are you trying to achieve (a manual written for pilots vs. funny subtitles for cat-videos)? etc. etc.pp.
Hello, is there any other way for translation not just Segment-by-segment? So I have TMX, source document with 800 segment that I want switch to target language for proofreading. I cannot see any "Select all/translate". It is not possbile open ALL segments manualy, I hope there is any way to do it automaticaly.
+iannickCZ Sorry, I am not sure I understand your question(s). Do you want to machine-translate (MT) all the segments automatically? Since I am not experienced with MT, I am not much of help. However, if you want to proofread, you will do so most likely segment by segment (or sentence per sentence). Either way, on each "block", the MT will be displayed (if any was found), and with CTRL-M can be taken over into the translation. Please note, that OmegaTs main-purpose is not MT. Further readings: ob.nubati.net/ditundat/omegat/docs/en30/chapter.machine.translate.html www.omegat.org/en/howtos/google_translate.html Or do you want to export the document for proof-reading? If you have a source, and the partially translated blocks, you can at any given time select "Create Translated Documents" (in the menu below "Project"). After doing so, the project-folder will contain a new sub-directory called "target" with a new document, containing both the translated and (still) untranslated segments. Easy for proofreading (if you do not like to read within OmegaT). Sorry again, I hope I got your question right. Cheers!
+CATnerd In Tradost there is function called "Pre-translate", so you can choose e.g. 100% match and application will use mine TM created (We haven't bought key for machine translation form third party). I was just curious if I can do the same without manual opening every segment. Hopefully it makes sense to you.
+iannickCZ Sorry, I am not aware of some feature like that in OmegaT. The only (automatic) pre-fill I know of is for "fuzzy" matches ("Options" -> "Editing Behaviour")... So I guess one has to "walk" through the translation step-by-step :-/
Hello i want to ask, how to make source document with all picture like that, i mean copy from web or article that contain picture to oppen office writer ? thanks
When translating, most of the time the "source"/original is provided (by someone else). So I am not really too familiar with creating content. However, OmegaT can import directly from MediaWiki (e.g. Wikipedia), but the output is supposed to go to a MediaWiki-article again (just in the new "target"-language). If you want to create a PDF or OpenOffice/LibreOffice Document for later use, save the web-page as "complete webpage" (HTML and also the images & styles). Open the saved HTML in OOffice. (Quality of a saved webpages will vary a lot, depending on the sources.) After editing and tuning the layout in OOffice, one could translate with OmegaT and then export from OOffice the translated document to PDF or to MediaWiki-Article again. Good luck! ;-) PS: Take care of legal issues when copying content from the web (copyrights, etc)!
Thank you so much for info Catnerd, i will try it, i used OmegaT 3.5.4, may i ask is it better to mediawiki article again or create pdf ? and how to save web page as complete webpage>?
and if you said output go to mediawiki article again, sorry i dont understand, if that means i change their web with my language for public? or just for me ?
Hello again :) The translation of MediaWiki-articles is only useful, if you want to translate e.g. an article from Wikipedia into another language. For example, I would take a good article from the English Wikipedia and translate it to German, so I can publish the translated article in the German. The creation of a PDF-file is useful, if you want to have a document that can be read on almost any platform, that can also be printed directly and that will not be changed by other persons later on. If you want to give the translated document to someone for correction or layout-work, stay with OpenDocument-Format (OOffice) until the document is ready to be released/published in a final version. @saving webpages: most web-browsers should support this. Just open the page you are interested in, and use the web-browsers menu to save the page. Most of the time, there will be options on how to save (HTML only, HTML and images, Text only, etc). For even better results, there are a few plugins available (e.g. Scrapbook for Firefox). Those plugins/extensions can save whole pages locally.
Hi! I was doing some beginners tests in OmegaT and in the pane I am finding each word of source text followed by a tag...I thought tags were appearing only to highlight Bold, special characters....can you help? Thank you!
Hello Romesh, assuming you are working with a docx-file, please read the chapter: "How to remove unwanted formatting code from .docx files" (it is a common issue): www.omegat.org/en/howtos/docx.html Edit/Add: While I dont have MS Office, I remember there was a way to remove those from within MS Office - maybe this can help a bit? support.microsoft.com/en-us/kb/284927
Hello, hopefully "Options -> Editing Behaviour" is what you are looking for. There you can select to automatically insert translations from fuzzy matching segments (of course, just considering the ones with a translation). If you want to select a fuzzy match to be inserted into (or replace) the current segment, just right-click the match of your choice in the fuzzy-window on the right.
Hello, and thank you for the tutorial. I have a question please. How can we proceed so the original-source language does not disappear, once the segment translated ? Thank you in advance
Yes, this is the default behavior: as soon as one entered some text, the source-segment will not be displayed anymore. To always see the original segments/blocks, check ""Display Source Segments" in the "View"-menu.
Sorry, I am afraid that I can not help you on this. For me it just worked for the job that wanted/needed to be done, so I never considered commercial alternatives :-/ Maybe you give OmegaT a try and see, whether it provides enough? The choice of the proper tool depends on so many things ...
Sorry, not a single question was raised that day. If you have something on your mind or ran into problems, please feel free to ask. It has been a while now, but maybe I can still be of help ;)
I just started using Omega T. I was confusing how to start with it. This video is very helpful, thank you!
Mix it with J inside then watch what happens
@@Dragon-Slay3r what is J inside?
Thanks, i got the grasp of how to work with Omega quickly thanks to your video. Well done!
I'm so happy seeing a Linux-user translator. I was installing this on my Linux Mint, having some difficulties, and ending up breaking my setting and finally, installing a new distro (I gave up finding out how to fix it, LOL). It's awesome though since this CAT tool is free. For me, I've been using Matecat and it has helped me a lot. Cool video anyway. Danke.
Basically they are just tab-separated text-files (encoded in UTF8, IIRC).
The first column contains the word in the source-language, the second column contains a definition in the target-language. A third column can be used for more details.
If one defines multiple lines with the same word, all possible "matches" will be shown within OmegaT.
To create, use a text-editor (which will not replace TABs with spaces), or use spreadsheets from Open/Libre-Office, export as CSV (with tabs as delimiter)
Thank you! I never translated using OmegaT and I was looking for an easy tutorial, yours was great!
Great tutorial, I am a freelance translator and it is always good to catch up with technology
Please could you give a bit of info about the glossary files?
Thanks
Thank you! I am going to try this one. I have installed the OmegaT.
Thank you man, I never understuande OmegaT so basic!
Excellent video, thank you so much for posting this :)
Thank you, very straightforward and helpful! 🙏😊
Did you update to a newer version of OmegaT? If not, please try it out, as the later versions have new features and bugfixes too.
About your unreadable target-document: if your translation is displayed correctly within OmegaT - maybe your external txt-viewer can not handle Unicode (UTF-8) or is using the wrong encoding?
At OmegaT's website you will find some documentation, HOWTOs and a FAQ.
If this does not help, there is also an active yahoo-usergroup called "omegat" :-)
Good luck! ;)
Thank you for this, I'm just getting into the world of translation. It's a big help!
Hi, thanks for the nice video. I have a question. Sometimes - or the last time - I dragged an .odt-folder into OmegaT, it separates the text incredibly strangely. For example, it separates the word t from ranslation, and so on, for no particular reason. How am I supposed to translated a the letter t and ranslation? The original text is correct. Do you know how I can fix this? I would be extremely grateful for your help. Thank you.
Mhmmm, the only thing that comes to my mind: >tags< in the source-document.
Maybe you can try to activate the check-box called "Remove Tags" under "Properties" (Ctrl-E) of the project?
Thank you very much, I will check the same.
Thank you very much, it was brief and helpful.
Thank you for sharing this tutorial! The output file turned out to be a TXT document file, is there any possibility to export our translation in a word document instead? Thank you!
That sounds interesting.
Normally a .doc should result in a .doc-file.
What kind of format was the source-file?
PS: If the source was a txt-file, the result will be too. But with LibreOffice or MS Word all txt-files can be opened, formatted and saved as .doc-files.
i have a problem went i translate a word it appears on the left side and the word translated doesn't disappear i hope you could help
and the vidéo was very informative 👌
Thank you! Do you have any expierience on translating latex files with OmegaT? I failed to do that, the target files have line endings removed which make the output latex files corrupted and impossible to generate pdf on the fly.
thanks a lot, what is the Machine translation about in OmegaT?
Very helpful, thank you!
Thanks, really clear walkthrough!
Great thanks! I‘m going to try this one.It's big help!
How can I add a dictionary to OmegaT, is that possible?
For this video I used version 2.2.3_4 ... currently version 2.3.0 is considered the standard-version, while 2.5.x is under development (and is looking quite stable already).
Get your version 2.3.x from Omegat . org -> "Download OmegaT" - it is free software.
Hi, my glossary on the program didn't show anything. What files do you put in glossary?
I'm translating Chinese to English.
Thanks a lot for the video!
I would like to ask if this free software is as effective/useful as the paid ones (e.g. Trados)?
I mean, is it worth it to buy Trados, or is it that that OmegaT does the job?
Thank you!
I can not open the target document, it says that there ist an error with the subdocument "content.xml" (The source document ist just text, *.odt) Could you help me?
The odt is "just" a container (like .docx and many other newer formats), basically packing/zipping various (sub-)files into one.
The underlying files are indeed mostly xml-based, just as your "content.xml".
Since I don't know what happened to your specific file, I just have few ideas to try out:
* use zip or 7z to check the content of your odt ... is there a content.xml?
* update to the latest version of OmegaT (if not done already)
* try converting your original source into a different format, e.g. doc, docx, or (lastly) even xml .. both LibreOffice/OpenOffice can export into those formats
Hope that helps.
PS: Beyond that it might be a good idea to check the bugtracker for known issues (or even open a ticket there): sourceforge.net/p/omegat/bugs/
is it possible to use your own glossary for automatic translation ?
thanks for the video! I have a problem, I closed the project I made and now I cannot get in because I get this message: Failed to load specific project! java.lang.NullPointerException. Any ides what this means ? thanks a lot!
That is a big question.
And I am not part of the coders developing OmegaT, but this looks like a bug or at least some unhandled condition (e.g. files were renamed or moved, etc.) leading to this error.
The project is hosted at SourceForge: sourceforge.net/projects/omegat/ - there is a ticket-tab with a list of reported bugs. Unfortunately I could not find your problem in the list of open issues.
So maybe you can try a different (newer? or older??) version of OmegaT? Maybe it was fixed/disappeared at one point?
Hope you can get rid of this problem!
*fingers crossed* ;-)
Thank you, I have a question please. Which one is the appropriate for first time user in OmegaT?
Sorry, I do not understand your question. 😕
Do you mean TH-cam-Videos/Tutorials?
There are so many out there by now, I really do not know.
This video here is for those, who know what they want to achieve.
... and how to start working in OmegaT.
Side-note: with the amazing Online-translations nowadays, CAT-tools become less and less important.
I guess they are only helpful for long or complex/technical/scientific texts, where domain-knowledge is required and computer-translations fail or produce dubious results.
Hi, probably a dumb question, but kindly have mercy. Since my source document is in paper form, and I'd need to do a hell of a job, to type it all down - is it possible to work without the source-document? If not with OmegaT, which Cat Tool would be suitable for such work?
Mhmmm... that sounds challenging.
So why not split up the task?
1. get the source-text into any digital format (via OCR), *then*
2. translate
And yes, both steps will require manual labour... if aiming for quality.
The better the source, the easier the translation (or any other translations to come).
Just my 2 cents.
Not sure whether this helps with your particular issue.
In the end ... your question has soooo/too many variables ... but maybe answering the most relevant/critical questions (pick yours) can help to find a way on how to solve the issue?
e.g. Is money the issue? To what extend?
Is it time-critical? Is it a hobby?
Are the sources sensitive/confidential or public domain?
Do you trust big players (e.g. Google)?
How good is the quality of the sources?
Is the format and layout of the resulting document of any importance?
How many pages are we talking about?
What level of proficiency are you trying to achieve (a manual written for pilots vs. funny subtitles for cat-videos)?
etc.
etc.pp.
very helpful buddy, my first impression is that OmgaT is a very friendly program to work with
Hello, is there any other way for translation not just Segment-by-segment? So I have TMX, source document with 800 segment that I want switch to target language for proofreading. I cannot see any "Select all/translate". It is not possbile open ALL segments manualy, I hope there is any way to do it automaticaly.
+iannickCZ Sorry, I am not sure I understand your question(s).
Do you want to machine-translate (MT) all the segments automatically?
Since I am not experienced with MT, I am not much of help.
However, if you want to proofread, you will do so most likely segment by segment (or sentence per sentence). Either way, on each "block", the MT will be displayed (if any was found), and with CTRL-M can be taken over into the translation.
Please note, that OmegaTs main-purpose is not MT. Further readings:
ob.nubati.net/ditundat/omegat/docs/en30/chapter.machine.translate.html
www.omegat.org/en/howtos/google_translate.html
Or do you want to export the document for proof-reading?
If you have a source, and the partially translated blocks, you can at any given time select "Create Translated Documents" (in the menu below "Project").
After doing so, the project-folder will contain a new sub-directory called "target" with a new document, containing both the translated and (still) untranslated segments. Easy for proofreading (if you do not like to read within OmegaT).
Sorry again, I hope I got your question right. Cheers!
+CATnerd In Tradost there is function called "Pre-translate", so you can choose e.g. 100% match and application will use mine TM created (We haven't bought key for machine translation form third party). I was just curious if I can do the same without manual opening every segment. Hopefully it makes sense to you.
+iannickCZ Sorry, I am not aware of some feature like that in OmegaT.
The only (automatic) pre-fill I know of is for "fuzzy" matches ("Options" -> "Editing Behaviour")...
So I guess one has to "walk" through the translation step-by-step :-/
Hello i want to ask, how to make source document with all picture like that, i mean copy from web or article that contain picture to oppen office writer ? thanks
When translating, most of the time the "source"/original is provided (by someone else).
So I am not really too familiar with creating content.
However, OmegaT can import directly from MediaWiki (e.g. Wikipedia), but the output is supposed to go to a MediaWiki-article again (just in the new "target"-language).
If you want to create a PDF or OpenOffice/LibreOffice Document for later use, save the web-page as "complete webpage" (HTML and also the images & styles). Open the saved HTML in OOffice. (Quality of a saved webpages will vary a lot, depending on the sources.)
After editing and tuning the layout in OOffice, one could translate with OmegaT and then export from OOffice the translated document to PDF or to MediaWiki-Article again.
Good luck! ;-)
PS: Take care of legal issues when copying content from the web (copyrights, etc)!
Thank you so much for info Catnerd, i will try it, i used OmegaT 3.5.4, may i ask is it better to mediawiki article again or create pdf ? and how to save web page as complete webpage>?
and if you said output go to mediawiki article again, sorry i dont understand, if that means i change their web with my language for public? or just for me ?
and how to translate to media wiki article again, sorry much question cause im new with cat tool
Hello again :)
The translation of MediaWiki-articles is only useful, if you want to translate e.g. an article from Wikipedia into another language. For example, I would take a good article from the English Wikipedia and translate it to German, so I can publish the translated article in the German.
The creation of a PDF-file is useful, if you want to have a document that can be read on almost any platform, that can also be printed directly and that will not be changed by other persons later on. If you want to give the translated document to someone for correction or layout-work, stay with OpenDocument-Format (OOffice) until the document is ready to be released/published in a final version.
@saving webpages: most web-browsers should support this. Just open the page you are interested in, and use the web-browsers menu to save the page. Most of the time, there will be options on how to save (HTML only, HTML and images, Text only, etc).
For even better results, there are a few plugins available (e.g. Scrapbook for Firefox). Those plugins/extensions can save whole pages locally.
Hi! I was doing some beginners tests in OmegaT and in the pane I am finding each word of source text followed by a tag...I thought tags were appearing only to highlight Bold, special characters....can you help? Thank you!
Hello Romesh, assuming you are working with a docx-file, please read the chapter: "How to remove unwanted formatting code from .docx files" (it is a common issue):
www.omegat.org/en/howtos/docx.html
Edit/Add: While I dont have MS Office, I remember there was a way to remove those from within MS Office - maybe this can help a bit? support.microsoft.com/en-us/kb/284927
Thnx, concise to the point.
Yes, I'll give it a try and see for myself,
Thank you again.
Hi Catnerd. Nice video. I went through your steps and they work. How do I get fuzzy matches to work? If you could help that would be terrific.
Hello, hopefully "Options -> Editing Behaviour" is what you are looking for. There you can select to automatically insert translations from fuzzy matching segments (of course, just considering the ones with a translation).
If you want to select a fuzzy match to be inserted into (or replace) the current segment, just right-click the match of your choice in the fuzzy-window on the right.
Hello, and thank you for the tutorial. I have a question please. How can we proceed so the original-source language does not disappear, once the segment translated ?
Thank you in advance
Yes, this is the default behavior: as soon as one entered some text, the source-segment will not be displayed anymore.
To always see the original segments/blocks, check ""Display Source Segments" in the "View"-menu.
@@weasel75 thank you very much
Thank you!
Hi, I just found your video. Easy to understand. Thank you very much!
I just wonder what language is the mother tongue of the speaker.
from what he said at the end i'd say german
@@danielmoura2959
Thank you for the reply.
@@danielmoura2959 Yes, very true.
And I blame the microphone for the hard "s" and "th" ;-)
Sorry, I am afraid that I can not help you on this. For me it just worked for the job that wanted/needed to be done, so I never considered commercial alternatives :-/
Maybe you give OmegaT a try and see, whether it provides enough?
The choice of the proper tool depends on so many things ...
Thank you so much!
Thanks!
Great!
I like the video - thanks for that. However, I would check the pronunciation of the word "target" :P
+Weronika Będuch Thanks, just did!
A tiny lesson learned (for the future), but for this video it will stay like that ;)
Thanks man
Thanks.
I just randomly stumbled upon this
Translating newbie here .hello everyone
and not a single question was answered that day.
Sorry, not a single question was raised that day.
If you have something on your mind or ran into problems, please feel free to ask.
It has been a while now, but maybe I can still be of help ;)
Are you German?
Yes, but thats a total coincidence ... I wasn't even asked ;)
tarGet :D
Can somebody please teach him an english "th"? I stopped listening, because it hurts my ears tooooooo much. Sorry!
Sorry too, working on it ^_^
If it is just too painful for you, maybe turn off the volume and turn on the captions?