>
> I have been really troubled by the broken Apertium-viewer (special
> characters like å ä ö é è ê didn't work). I even considered to correct
> the program myself, but found that my knowledge in Python wasn't
> sufficient.
>
I think that you are talking about
apertium-view<http://wiki.apertium.org/wiki/Apertium-view>and not
apertium-viewer <http://wiki.apertium.org/wiki/Apertium-viewer>.
Apertium-viewer is written in Java and, if I'm not wrong, it was developed
to replace apertium-view. Java uses UTF-16 internally, so you shouldn't
have any problem with special characters.
I am eager to see the new version.
>
You can always find the last version at
http://javabog.dk:8080/apertium-viewer/launch.jnlp. I committed a newer
version two days ago with some new features but we haven't released it yet.
as an OmegaT user I cannot but agree. In vain I have tried to install
> Apertium Server to call it from OmegaT. An easy way to use translations
> from Apertium in OmegaT would be welcome.
>
I didn't know about OmegaT, but I see that a plugin for it would be
welcome. I've been investigating a bit and I think that it would be
relatively easy to implement it. I see two possible approaches:
1) Make the Jars that I've been working on OmegaT plugins (i.e., apart from
being usable as self-executable apps and Android packages, they would also
act as OmegaT plugins if placed at the plugins folder there). It would
probably be the easiest solution, and it would be enough to write a class
for the plugin at lttoolbox-java together with some stub classes to make it
possible to compile it. It wouldn't make lttoolbox-java much bigger (let's
say 10 more KB), but it's true that perhaps it isn't the logical place to
implement it... It could also be seen as something similar to the
ApertiumGUI and Translator classes that I wrote (not strictly necessary for
lttoolbox-java, but useful to have them there). What do you think, Jacob?
2) Develop an independent plugin for OmegaT that would be, at the same
time, using the Jars that we currently have.
*For OmegaT users*: What's your opinion? And, just in case, if I'm not
wrong OmegaT can already work with Apertium, so what you want is to make it
work offline, right?
*
For my mentors*: Should I be working on this? After all, it wasn't in the
original plan so perhaps I should concentrate my efforts on something
else... In any case, I think that it wouldn't take much time (1-2 days, I
guess).
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Apertium-stuff mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
