LASERAY  The requirements on this page are wrong. OmegaT needs Java 1.5 or greater to work. Thus it will not run on OS X 10.3 of lower, since Apple does not make Java 1.5 for anything below OS X 10.4.  
(Version 2.0.2b)

LASERAY  "I've read the below comments made by the developer of OmegaT+ with sympathy, but after his appreciative words about the philosophy behind FOSS it's odd to see his licence not being a free software licence and OmegaT ("open source propireity") being under GPL. Perhaps I'm ignorant of something."

Yes, you missed something. The OPL license is a free license. It is not 100% compatible with the GPL, but it is only being used for documentation on OmegaT+. All the code in OmegaT+ is under the GPL. So no real problem exists.

What you should consider is that OmegaT uses code/libraries that are not completely compatible with the GPL. That is they do not practice due diligence to ensure that the extra stuff they use has proper licenses before they add it in. They go ahead and slap stuff in without any real thought. I have called them on this numbers of times, only to be treated badly for it. They removed some stuff I pointed out and then later put it back in or just continue on ignorantly.

Then look at their use of a trademark on "OmegaT". Trademarks are completely anathema to free software. I argued this with them numbers of times and have even read articles recently that say the same things as I have been saying in this regard for a few years. Trademarks go against what free software is about, just as software patents and completely proprietary (the correct spelling) copyrights do. In spite of this OmegaT keeps going along as if there is no question in this that they have a right to a trademark (they are not even a company or other commercial interest, which is what trademarks are for). It is quite ridiculous in that they blatantly misrepresent themselves as being about FOSS, then get a German trademark (i.e., only applies in Germany), and act like the trademark is worldwide. I have called them on this lie numbers of times and never get any response.

I could be quite happy to just make changes to the fork I created and keep it all to myself, but I put out a version out for others to benefit from. OmegaT on the other hand is now more about getting others to come along and do the programming work for them, for the personal benefit of the main users of OmegaT (the project members themselves). The majority of project members on OmegaT have not written one line of code that goes into the program. Yet these same people have no problem putting it up on a pedestal as if it is near perfect when any questions arise as to its quality. How would they know?  
(Version 2.0.2b)

LASERAY  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.  
(Version 1.8)

LASERAY  Well thanks for liking OmegaT+, but you are actually talking about OmegaT. So get a clue before commenting. There is a massive reason I have a bee in my bonnet. I participated in OmegaT development a few years ago and was treated very badly, even though I was giving my software expertise away for free. Since they refused to cooperate, I was forced to fork OmegaT into OmegaT+ so that I could continue to do what I want with the program. I did that and then was unfairly attacked for exercising my rights (as given by the GPL license that OmegaT is distributed under).

It is my assertion that OmegaT as a project is just an instance of what is known as proprietary open source software. That is, a project which basically just claims that it is all for the ideals of free software, but really just wants to further itself for the interests of a small core of users. It gives the program away, and the source code, but has not historically responded in the proper manner to use of its code in other projects. Not to mention the number of times I have actually caught that project violating the GPL itself, which I called them on and thus forced them to make changes to come in line with the rules of the license.

Nonetheless, they still persist in not following the letter of the license in all respects. This is basically their way of operating and it goes a long way to showing that OmegaT is just a proprietary open source project riding on the free software bandwagon. And expect that they will continue to make

violations in the future due to a lack of due diligence and disregard for proper conduct.

Helary was one of the main reasons I did not remain on OmegaT and that there was so much dispute between many of the parties involved. He periodically spreads false propaganda that both attempts to prop up OmegaT and beat down OmegaT+. All of which can be easily shown to have little logical or factual basis for any person with enough intellect to check for their self.

On top of this, I have been busy working on a new version of OmegaT+ and it is just incredible the amount of garbage code and lack of attention to detail that the core OmegaT programmers seem to think is acceptable. Even in the latest development version 2.0 (much of which has been retained from version 1.6, 1.7, 1.8) there is so much bad coding it is incredible to me that they feel fine thinking of it as a next new version. Personally, I would not feel good as professional putting it out in that way and it could even be considered as a blemish on the careers of those involved.

New OmegaT+ versions will still have some of that could, but it will not be released as a stable version with all that garbage in it. Thus there will be a lot of work going into version 1.0 that OmegaT developers just do not have the professionalism to do.

Don't be fooled. Just because OmegaT seems to work to some extent that does not mean that is a good piece of work. It isn't. And I defy anyone to take the source code and have it peer reviewed and analyzed by independent, experienced, third party, computing professionals. I am absolutely certain they will think it is trash work that need a complete redesign.  
(Version 1.8)

LASERAY  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.  
(Version 1.6.1)