OmegaT is a freeware translation memory program that doesn't run on Microsoft Word. It seamlessly imports and exports plaintext, OpenOffice Writer documents and HTML.OmegaT is a no-nonsense tool that increases productivity and consistency without taking creativity out of a translator's hands. As far as I can tell, aside from those aimed at translating programs, there are no general-purpose translation applications in portage. OmegaT is a tool aimed at professional translators. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 73327 [details] omegat-1.4.5.04.ebuild
Created attachment 73328 [details, diff] Make OmegaT look for help docs in "/usr/share/doc ... " instead of user's home directory.
Created attachment 73329 [details] omegat-1.4.5.04.ebuild Tidied up the ebuild a bit.
Comments: 1. Your DEPENDS are not sufficient. You need for example ant-core and unzip. You should also check that the OmegaT does not include packed jars. http://gentooexperimental.org/svn/java/axxo-overlay/README/docs/java-devel.html 2. src_compile() { cd ${WORKDIR} S="${WORKDIR}" and you don't need to cd. 3. mv dist/OmegaT.jar dist/omegat.jar insinto ${MY_INSTALL_DIR} doins -r dist/* jars should be installed using java-pkg_dojar 4. # Icons and stuff insinto ${MY_INSTALL_DIR}/share doins images/* There are functions in eutils.eclass for installing icons (doicon) and making .desktop entries (make_desktop_entry) Thanks for the work so far. #gentoo-java@freenode is available for you if you want to talk to java maintainers/have questions.
Created attachment 73366 [details] updated omegat-1.4.5.04.ebuild Thanks for the pointers. Fixed the ebuild as per the recommendations, and some other stuff as well.
Created attachment 73375 [details] omegat-1.4.5.04.ebuild Removed sed as a dependency - it shouldn't be there because it's part of "system", right?
Created attachment 73497 [details] omegat-1.4.5.04.ebuild After some, perhaps, excessive posting - this is as near "done" I can get on my own. I've refined and simplified the ebuild as much as possible. The addon "properties-import" has been moved to an ebuild of its own as it's intended to be used standalone, see separate attachment.
Created attachment 73498 [details] omegat-properties-import-1.1.ebuild
Created attachment 73601 [details] omegat-properties-import-1.1.ebuild, final bid Removed unneded dependency. Won't touch any of these files any more until I hear from a developer.
Created attachment 100642 [details] omegat-1.6.0_rc12.ebuild It doesn't seem that developers recommend to use the 1.4.5 series. This is a modification of Magnus Lind's 1.4.5.04 ebuild for the latest 1.6 release candidate.
Created attachment 100643 [details, diff] 1.6.0-helppath.patch A patch needed for 1.6.0_rc12, similar to the one for 1.4.5.04.
Finally, OmegaT 1.6.0 has been released. Please consider to put it in the portage tree. Here are my ebuild file and patches.
Created attachment 101450 [details] omegat-1.6.0_p01.ebuild It's almost same as the previous ebuild but one more patching is needed.
Created attachment 101451 [details, diff] 1.6.0_p01-helppath.patch It's just like 1.6.0-helppath.patch, but line ending might have been changed.
Created attachment 101453 [details, diff] 1.6.0_p01-platforms.patch This patch is necessary for platforms.* properties, which seem to have proper definitions. They are referred by two nbproject/build-impl.xml files, so I guess they are defined on netbeans environment. I just set them to /usr/bin/java, etc. It is just a hack, but I don't know other ways.
Created attachment 102379 [details] omegat-1.6.1.ebuild The version 1.6.1 has been released a few days ago. The ebuild is almost same as the previous ones. 1.6.0_p01-helppath.patch is required but this time no platforms patch.
Created attachment 104994 [details] omegat-1.6.1_p02.ebuild This ebuild is for OmegaT 1.6.1 update 2.
Created attachment 104995 [details, diff] 1.6.1_p02-helppath.patch A patch needed for 1.6.1_p02 ebuild. As the part of code the previous patches were applied is changed, the patch is updated.
Is there still some reason not to accept this into portage?
(In reply to comment #19) > Is there still some reason not to accept this into portage? > We have near 500 java packages in the tree and only a few of use developers. Every new package makes the situation even more hopeless.
This is a tool for translation just using java as its implementation language, and it won't be in a dev-java category, maybe should be in app-misc. So I don't think it should necessarily be maintained by java team, but don't know who else appropriate, either. If java team is too busy, please recommend some other developers who the team thinks appropriate.
(In reply to comment #21) > This is a tool for translation just using java as its implementation language, > and it won't be in a dev-java category, maybe should be in app-misc. > So I don't think it should necessarily be maintained by java team, > The thing is there aren't people many people outside the java team with enough knowledge to write java ebuilds. The category does not have a direct relation to the people who maintain the package.
in cvs.
Created attachment 325896 [details] omegat-2.6.1_p01_beta.ebuild
