On 13 juil. 07, at 02:40, Alessandro Cattelan wrote:
Actually I haven't tried going through the procedure you described, I
think I'll give it a try with the next batch of files. We'll have
around
4,200 words to translate and as it is a reasonable volume, I think
I'll
have some time to spend in testing a new procedure.
What I fear, though, is that OmegaT would become extremely slow
processing a huge SDF file. If I have a bunch of PO files I can just
import only a few of them into the OmT project at a time and that
makes
it possible to translate without too much "CPU sweat" :o). When I
tried
loading the whole OLH project on which we worked in June, my computer
was almost collapsing: it took me over an hour just to load the
project!
I don't have a powerful machine (AMD Athlon XP, 1500Mhz, 700MB RAM)
but I think that if you have a big TM it is not wise to load a project
with over a thousand segments.
You are definitely right here: the bigger the TMX the more memory it
takes.
Which is the reason why I just suggested (in the "Imagine" thread)
that we have TMX by modules.
Also, you can assign OmegaT more memory that you actually have on
your machine, I use OmegaT like this:
java -server -Xmx2048M -jar OmegaT.jar &
The -server option makes it faster too.
The sdf files we have are not that big though. So you have to be
selective with the TMX you use.
Maybe we could split the SDF file into smaller ones, but I'm not sure
that would work.
If you try my method, you can translate bits by bits. There are no
problems with that. What matters is that the reverse conversion is
properly made.
JC
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
