Any #OmegaT users out there who can recommend a good MT engine that a low-tech person like can setup? I tried the DeepL API but the plugin seem deprecated. (I need English-Danish language packs specifically, so Apertium doesn't work)
#OmegaT
@OmegaTOfficial@floss.social
Hello!
I'm translating .srt subtitles from Japanese to Russian and I have problem.
File has 517 segments (you can see it at first image), but #OmegaT can see only 440 segments (second image).
So, when I translated all 440 segments my target file still has untranslated parts (you also can see it at first image).
My question is this my mistake and I made something wrong, or this is bug in program? I'm using OmegaT 6.0.1 from flatpak.
For testing I can give you my .srt file or whole project.
Thank you!
@trucker Yes. I switched from one of the technofeudal AI-scraping options to open-source #OmegaT. I hesitated at first, because the interface looked difficult to use, but I was surprised how easily it was and more importantly, the community help is 10x better and faster than the "customer service" in the corporate version. They're even present in the fediverse: @OmegaTOfficial One of my best experiences with open source software in recent years.
Une belle page sur #OmegaT en français.
@Wuppi42 En plus de S+V+
C, il y a des tas de raisons pour inverser l'ordre des balises, par exemple la position des adjectifs. "Il" l'a bien compris, et c'est pour ça qu'il y a "Options > Préférences > Traitement des balises > Autoriser un ordre différent pour les balises traduites". On peut aussi décocher "Bloquer la création de fichiers traduits avec des problèmes de balises", si on est sûr de ce qu'on fait.
Des idées de la Team OmegaT pour contourner le blocage de création du fichier traduit quand l'ordre des balises n'est pas le même que dans le segment d'origine ?
L'a pas compris que toutes les langues ne fonctionnent pas S+V+C...
Et si vous savez pas, vous pouvez rebooster 🙏
Merci !
#OmegaT, ça aligne bien du Word ? On peut déplacer et appairer les segments facilement (aussi en 1:2) ?
Moi d'il y a 15 jours : Ah, j'ai juste le temps de modifier les cibles des copains, je ferai un alignement viteuf plus tard.
Aujourd'hui : déjà 2 outils de TAO qui me font la misère pour aligner [en même temps, Crados, j'ai tenté par acquit de conscience]. C'est peut-être la faute à Word, mais grmpf, quoi.
#OmegaT small fix, 16 years in the making 🙂
Translators of #Latex files: it looks like #OmegaT has a bug in its LaTeX filter.
https://sourceforge.net/p/omegat/bugs/1284/
The patch that was proposed in 2019 has been applied to releases/6.0 and we need your feedback.
@downey - "What #OpenSource project has the best experience for localization/translation volunteers?"
- What better than an open source project that offers translators/localizers actual open source software to do their job?: #OmegaT
After many mistakes, I finally have a proper notarized version of OmegaT 6.0.1.
It is slightly different from the official version because it includes a more recent version of junixsocket.
https://sourceforge.net/p/omegat/mailman/message/59125531/
The note also has been updated (we *do not* have an issue with the launcher):
https://github.com/omegat-org/omegat/blob/topic/jc/macos/notarization/notarization.md
I have a working prototype of a notarized version of #OmegaT.app for #macOS packaged in a signed standard dmg volume. Both open nicely on 2 different #Sequoia machines that I tried them on.
The document where I describe the process is here:
https://github.com/omegat-org/omegat/blob/topic/jc/macos/notarization/notarization.md
The prototype is here:
https://traductaire-libre.org/omegat/OmegaT-Mac_x64_Notarized.dmg
Thank you @amake for your #macport version of OmegaT. I used its launcher script to fix our "can’t launch the JRE" issue.
I am working on #OmegaT’s documentation fixes for the 6.0 (+) series here:
https://github.com/omegat-org/omegat/tree/topic/jc/docfix/6.0.1
Please register your issues with the manual here:
https://sourceforge.net/p/omegat/documentation/
Issues can be about problems with translations of the manual.
#Notarization works, #OmegaT.app opens on a "App store + know devs" #Sequoia machine, but is "unable to load the #Java runtime environment".
@amake do you have any idea what’s going on?
Notarizing #OmegaT for #macOS distribution.
This article was helpful:
https://medium.com/@yo7chen/effortless-mac-code-signing-and-notarization-a-comprehensive-guide-using-terminal-b8285df9bf9c
And this apple-dev one too:
https://developer.apple.com/documentation/security/resolving-common-notarization-issues#3087735
Successfully received submission info
createdDate: 2025-01-19T13:09:18.924Z
id: 50a973ea-d902-4d15-a536-46db80f63017
name: OmegaT.app.zip
status: Accepted
#omegat and #okapi have been on #macports thanks to @amake for at least 5 years and I totally missed that.
sudo port install omegat
puts OmegaT in /opt/local/share/java/OmegaT
adds an "omegat" script in /opt/local/bin to directly run the app
and adds an "OmegaT.app" package in /Applications/Macport that uses the /opt/local/share/java/OmegaT executable.
Same for Okapi's apps, where "rainbow" and the others are neatly put into /Application/Macport, but can also be run from the command line.
A welcome to all the new followers, and a happy new year to everyone. Here's hoping for the best for the #OmegaT project, and for your professional and personal projects in 2025!
Slowly resuming the "OmegaT as a Book" project.
https://sr.ht/~brandelune/omegat-as-a-book/
https://lists.sr.ht/~brandelune/omegat-as-a-book
#OmegaT #Computerliteracy #freesoftware
Thank you @AdamBishop for being there. Other members, please raise your hand 😃
Nach einer Woche Arbeit mit dem auf #Linux -Basis reanimierten PC (vielen Dank, @Karlosbubi) würde ich sagen: funktioniert. Ein paar Dinge sind noch gewöhnungsbedürftig, aber das legt sich wohl mit der Zeit.
Ist hier noch jemand mit #OmegaT unterwegs?
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst