Ola, 

Non sei se será de moita interese para esta conversa, pero cópiovos ao final 
deste correo o que lle escribiu Friedel Wolff ao tradutor de francés do seu 
libro sobre o proceso que fixo para convertelo de ODF a po. (Teño o seu permiso 
para copialo aquí).
Eu traballei na tradución ao español (a tradución ao galego tócame agora) e 
traducimos usando Pootle e Virtaal. Foi un proceso interesante, aínda que houbo 
que "testear" moito na versión final en odf (despois da conversión) porque 
había pequenas cousas que houbo que correxir (tamaño das táboas, omisión de 
espazos entre parágrafos, hipervínculos que non estaban ben colocados, etc.), 
pero eran todo erros "cosméticos" que se detectaron a simple vista. Outra 
cousa, para a revisión eu preferín facelo no formato final (odf ou pdf), porque 
a lectura faise moito más cómoda e vense máis os erros.

Lucía


Here is what I did for the book:

Our ODF converter didn't seem reliable enough yet, so I opted to use OmegaT. I 
created a project and added the one file, and saved the project. I think I 
disabled sentence segmentation. I don't know if you will want to be translating 
in sentence segments, but I guess it is at least an option for you in French. 
For the Arabic translation, it was definitely not an option, and I wanted to 
keep the things the same.

Hopefully you'll prefer to translate in Virtaal instead of OmegaT :-) Of 
course, you can translate inside the OmegaT GUI, but because I wanted to manage 
the translation outside of OmegaT (and translate outside of it), I only use it 
to create an empty TMX file (you can think about it like a POT file) from the 
command line.

path/to/OmegaT omegat_project_dir/  --mode=console-createpseudotranslatetmx 
--pseudotranslatetmx=allsegments.tmx  --pseudotranslatetype=empty

Then I wrote a very basic script (which I can gladly share if you want to 
follow this route) to convert it to a pot file, simply so that we could use a 
PO workflow for the rest:
tmx2po allsegments.tmx allsegments.pot

Then you can do your translation, review, etc. as you want.

To generate the document, I have to convert the PO file to tmx (po2tmx is part 
of the Translate Toolkit), and copy it into the correct directory, for example 
omegat_project_dir/omegat/  (while OmegaT is not running).

Then you open OmegaT and generate the final document in the GUI (I think
Ctrl+D or something).  It creates the translated document in
omegat_project_dir/target/

Then you still have to do some postprocessing, like regenerating the index or 
any "calculated" content like that (I think page numbers are automatically 
correct). Of course you might need to make more manual changes, like layout, 
column sizes, etc.


__However__

If I were to do the same thing now, I'd consider using Okapi, and at least try 
it out. I don't yet know enough to actually use their tools, but I think it 
might be worth while to try. If you can get a POT file (or empty XLIFF file) 
out of their tools, you can use podebug from the Translate Toolkit to do a 
pseudo-translation, and then try to complete the whole process to test how well 
it works. So you can do this reasonably easily without translating on something 
that won't work out.
The main shortcoming I saw with OmegaT (as far as I remember), is that 
identical segments were merged, with no possibility of not doing that.
I'm hoping that Okapi will give more choice. The other problem was that the 
literal page numbers in references were in the text and would constantly change 
causing fuzzy strings. I redid those many times to protect you guys from it. If 
the source document won't change while you translate and you don't expect to 
have to do updates, I guess this doesn't matter.

Of course you are free to try our odf2xliff converter, but I know there are 
some cases that it doesn't handle well. If you do a quick translation with 
podebug and everything works well, then you can use that as well, of course, 
but make sure that you use an XLIFF editor that supports inline tags. Virtaal 
should handle that well, but to be honest all of that has not had a lot of 
testing, so I can't recommend it with confidence yet.

-----Original Message-----
From: proxecto-boun...@trasno.net [mailto:proxecto-boun...@trasno.net] On 
Behalf Of Fran Dieguez
Sent: 01 June 2011 19:18
To: proxecto@trasno.net
Subject: Re: Traducción de libros

Seino porque eu fora que lle fixera a investigación de como facer a
conversión de po a docbook e escribiralle un pequeno script para iso:

http://gitorious.net/poss-gl/poss-gl/blobs/master/xml/generate-gl-xml.sh

-- 
Fran Dieguez <lis...@mabishu.com>

O Mér, 01-06-2011 ás 20:10 +0200, Antón Méixome escribiu:
> - En xeral
> http://traduccionymundolibre.com/wiki/Category:Translation_Tools
> 
> - En concreto sobe libro traducido por Ghandalf
> 
> Non sei moi ben que dicirche. Creo lembrar que tiñan un interface web
> para traducir por capítulos e estes por cadeas. A clave é como
> chegaron a ese punto usando
> "certas ferramentas" como din eles.
> 
> Intúo que sería utilizando as ferramentas en liña de ordes de PO-XML
> de KDE. Algo do tipo destas http://man.cx/split2po%281%29
> 
> Quen o ten que saber é Andrés Maneiro.
> 
> Supoño que primeiro obtiveron o texto orixe separado por parágrafos e
> transformaron cada parágrafo nunha cadea e, de aí, facer un catálogo
> en formato PO.
> O resto sería a xestión de cadeas habitual de calquera aplicativo con
> tecnoloxía gettext.
> 
> O que si está claro é que xestionaron o versionado cun xestor de código:
> 
> http://gitorious.net/poss-gl/poss-gl/commit/5e5b1ab91f9fcba421adc4503f7134d932e8ddc5
> 
> Un saúdo,
> 
> Antón
> 
> 
> 
> 2011/6/1 Alejo Pacín Jul <alej...@gmail.com>:
> > Boas.
> >
> > Nos foro de Blogdrake no que ando normalmente, anda tamén un usuario que
> > ultimamente vén de preguntar por un aplicativo específico para a traducción
> > de libros. ¿Alguén controla do tema? ¿Sabedes que ferramentas empregaron en
> > Ghandalf para traducir "Creando Software Libre", por exemplo?
> >
> > Graciñas a todos de antemán.
> >
> > _______________________________________________
> > Proxecto mailing list
> > Proxecto@trasno.net
> > http://listas.trasno.net/listinfo/proxecto
> >
> >
> _______________________________________________
> Proxecto mailing list
> Proxecto@trasno.net
> http://listas.trasno.net/listinfo/proxecto

_______________________________________________
Proxecto mailing list
Proxecto@trasno.net
http://listas.trasno.net/listinfo/proxecto
_______________________________________________
Proxecto mailing list
Proxecto@trasno.net
http://listas.trasno.net/listinfo/proxecto

Responderlle a