Mikel Forcada m...@dlsi.ua.es writes:
[...]
There is one thing that could be easily solved. Víctor Sánchez
(cc-ed) maybe can help you. When one uses the Apertium
webservice from inside OmegaT, we avoid translating the tags
(u0, etc.). Some minor changes were
I guess that you are talking about this. I might be blind, but I
haven't been able to identify the relevant piece of code there...
You're right. Most of the work is done at the Apertium server when it
receives format=omegat.
Perhaps you can just use the
translate
Cool. Works like a charm. A minor quibble: I said I wanted it installed
in /tmp and it decided that every file in there was an already installed
language pair. Perhaps a regex identifying language pairs by name would be
very helpful.
I now look at the file extension to filter JAR files. I
Mikel [et al]:
Yes, but the JARs online follow a different naming convention so that
we can know the exact modes they contain without downloading them
(that is, simply looking at their name). For instance, en-eo,eo-en.jar
is used instead of apertium-eo-en.jar, expressing that the contained
So, basically, what we need is to not translate anything between
tags, right? For instance, if we have something like Ez dakit zer arraio
idatzi, we should avoid translating zer arraio... is that all we need?
If so, it shouldn't be too hard to achieve.
Yeah, turning all of that into a
On 19 July 2012 18:12, Mikel Artetxe artet...@gmail.com wrote:
char ch0 = (sf != null) ? sf.charAt(0) : (char) Character.UNASSIGNED;
or even something like
char ch0 = (sf != null) ? sf.charAt(0) : '\0';
Character.UNASSIGNED is 0, so this is the same thing. I'd lean towards
