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 spen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jean-Christophe Helary ha scritto:
> Ale,
>
> I was wondering if you eventually had considered this procedure. I works
> very correctly and considerably increases productivity thanks to
> OmegaT's HTML handling features. I think I'm going to investiga
On 11 juil. 07, at 15:29, Arthur Buijs wrote:
The overhead of using po-files in the translation process is minimal
(exept from the initial trying out).
It is not when you have to modify the tagged links to fit the source.
In OmegaT that is done automatically without you even noticing it.
Hi Jean-Christophe,
Jean-Christophe Helary schreef:
The reason why I tried to do that is because using the .po created with
oo2po along with the TMX created with po2tmx does not work well. The
po2tmx removes data from escape sequences and that means more things to
type in the OmegaT edit windo
Ale,
I was wondering if you eventually had considered this procedure. I
works very correctly and considerably increases productivity thanks
to OmegaT's HTML handling features. I think I'm going to investigate
the possibility of having an .sdf filter for OmegaT rather than
having to go thr
The reason why I tried to do that is because using the .po created
with oo2po along with the TMX created with po2tmx does not work well.
The po2tmx removes data from escape sequences and that means more
things to type in the OmegaT edit window.
So, the idea was to consider the .sdf file as
