Just a couple of comments. On Thu, Feb 9, 2012 at 6:24 AM, Jimmy O'Regan <[email protected]> wrote: > On 9 February 2012 00:05, Bernard Chardonneau <[email protected]> wrote: >>> lttoolbox-java works fine with all the existing dictionaries, and should >>> be feature-complete with the C++ version. lttoolbox and lttoolbox-java >>> are completely independent of each other, so you don't need the C++ >>> version to use the Java version and vice versa, so keeping everything >>> within Java should work fine. >> So, you mean lttolbox in C++ and in java are doing the same ? >> >> Does it means that (at least with java) Apertium is now perfectly >> multi platform (without additive tools). >> > > No, nobody said that. The Java version of lttoolbox is feature > complete, the version of Apertium is not. That said, enough parts of > it work that it might be suitable for your uses.
Yes, the basics are there, but some language pairs use additional tools that haven't been ported, so if the Java runtime doesn't recognize the tool being called for in the language's modes file, then it defers to the C++ runtime for that component. > Also, being written in Java does not automatically make something > cross platform. Sun's marketing was referring to the _binaries_, which > is not an advantage for those of us who distribute source. There may > be some assumptions of a Unix based platform in the Java version of > Apertium, though, IIRC, Steven was using Windows and would have had to > change those. Yes, I was using Windows for the Java development, so I tried to abstract platform differences as much as possible. However, there are still some assumptions that Cygwin is present if we are on Windows. For instance, almost all filesystem calls route through an abstraction layer meant to deal with the differences in how paths are represented in Windows and Unix. This assumes that if we have a unix-style path but are on Windows, that we have Cygwin installed and so uses the cygpath utility to convert the path. This is most commonly seen in the modes files in language pairs that have been compiled and installed in the local Cygwin environment. And in that same vein, what I mentioned above about deferring to the C++ runtime if the tool called for in the language pair is unknown/unported also means that Cygwin is assumed, since that's the only way the C++ runtime will actually work under Windows. -- Stephen ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
