OmegaT4.3.2

Current version is 3.1.9. :-)

Current version is 3.1.9. :-)

I've already got clues and I'm giving them to you about OmegaT. And I am someone who knows what they are talking about. I never said you insulted me, where did you read that? But you did mix up OmegaT and OmegaT+ and still have to some extent in this current reply. "OmegaT+ is a solid and improving alternative to the incredibly expensive Trados." Yes, this is the case, but I have only released one version of OmegaT+. So it is a little odd that you would think so. Insufficient information for you to come to that conclusion. When the next version (1.0.M2) is out then you might have a little more to go on. "It's tough to master (as are all translation memory programs) and there may be questions re. compatibility, but it is Mac-compatible and doesn't force you to use Windows and Word for Windows, etc." True. And newer OmegaT+ has improved compatibility on Mac (have been working on that in the past weeks). " As to the perhaps justifiably (perhaps not) upset laseray, how you were treated while working on OmegaT software development is something that Macupdate posters know nothing about and may or may not be relevant to how well the software works, but what seems clear is that you have a grudge against the software maker that may be more properly discussed and settled in another venue, such as a labor rights and/or intellectual property rights case. Not here at Macupdate, in my opinion, though I'm honest enough to admit I may be wrong." It is your opinion and I see no notice about not commenting on aspects beyond the basic usage or things that you deem appropriate. The points I make are germane due to the software being released as FOSS under the GPL. there is a whole philosophy behind that and it is very important, not just to me, but to the future of FOSS for projects to act properly. If projects do not want to conduct their activities in a just manner then they should go away or change their license. "In any case, please premise all your comments with the information re. your past work with the OmegaT team and your grudge against them. It's the honest thing to do." Excuse me, that would be rather long. Much of the activity is documented on public forums/mailing lists. And even if I point to proof, investigating by asking OmegaT (to see the other side) will only lead to them denying it, lying, and other incredibly skewed reactions. Plus I have already explained my position to others many times before. My inclination is to explain things in the way I want rather than having to submit a whole thesis before I may talk. Anyway, as long as their no kind of limit on how I might comment, I will comment as I like.

I'm very happy with OmegaT. Using an Apple computer, I'm not sticking to Microsoft Office and even glad when I can avoid it - which also means I'm using Open Office anyways. OmegaT certainly requires some time until one gets used to it, but then it really works fine!

Mr. Helary's comments for OmegaT are biased due to him being an OmegaT project member. There is no way to gauge exactly how many people currently use OmegaT, yet he claims that thousands use it. OmegaT has a Yahoo user's group with approximately 600 members. If that is any indication of use then it is significantly less than even one thousand users. Next, the claim that OmegaT is supported by a very active development team is blatantly false. Any one can go to the OmegaT CVS archives on that project and see that the level of activity is rather low with only a few developers having done any work in months. He leaves out a lot of important information for users. For instance, while OmegaT can import/export TMX, it can only do it properly for certain TMX versions whereas commercial tools almost always have complete support for all versions. He fails to clearly mention that users will need to install OpenOffice.org to work with MS Office formats. The overall intention of his writing is to persuade people to use OmegaT by misusing language so as to cloak certain facts about the application that would probably cause some potential users to take a pass on it. I have personally have had numerous dealings with Mr. Helary and this is typical of the way he operates. A less than fair and honest character.

OmegaT is used by thousands of professional translators all over the world, either freelance or in-house. It works as advertized and is supported by a very active team of developpers, localizers, power users in a variety of languages. People who want to stick to Word based tools are free to do so. People who need to work in a flexible way will consider the options that OmegaT offers as well as its ease of use. Its ability to import and export standard TMX files makes it a tool of choice for people who rely on a number of different tools. The current (2007/02/15) CVS version includes a Microsoft Office 2007 file filter for the "Word or nothing" people, but the rest of the world will be satisfied with its numerous filters (including ODF/XHTML/DocBook etc) and the free conversion tools that can be used in combination: OpenOffice.org (multiplatform) for MSO files access, Okapi tools (.NET 2.0) for a number of localization formats, the Translate Toolkit (python) for convertion to PO from a number of formats. There is not one ideal tool for translating. And any professional knows that. Different source files require different processes. OmegaT is here to satisfy translators who know simplicity is most of the time more valuable than anything else.

I use Trados professionally and I am always looking for something similar I can use with my Macs, but Omega obviously isn't it. The fact it cannot directly read Word files is absurd and makes it useless top me and, no doubt, to most professionals who would otherwise use it regularly. Make it able to read Word documents or at least RTF files, and then we can talk again.