On 1/19/07, Jean-Christophe Helary <[EMAIL PROTECTED]> wrote:
On 19 janv. 07, at 19:48, Ain Vagula wrote: > By the way, I noticed that xliff files are stored in packed format, > xlz? It > means that when using xliff as only intermdiate version, without po- > step, > you'll not have any overview over changes in version control system? > Its only a question, not statement - I dont know almost anything about > deeper mechanism of version control. VC is fine for some processes but I think it is a little too much for our purposes. As long as you have past documents stored as translation memories (TMX) you don't need to have VC at all anymore (at least if you mean VC the way I mean it). If your text has already been translated it will be there in the TMX and either you have a system to automatically update it or you do that manually. There are a number of issues related to TMX: do we store everything as sentences, or as paragraphs etc. And if we leave translators free to use the process they want, how do we guaranty that they deliver a TMX with the final document. That is where XLIFF comes in: as long as the delivered document is XLIFF it is trivial to extract a TMX from it for recycling in the next translation. etc. Sorry, I think as I type and maybe that was not the kind of answer you were looking for.
I mean version control as CVS, SVN etc. We keep currently po-files in CVS repository. When someone with write-access commits something to CVS, system automatically sends a notification with full diff to projects cvs mailing lists. (po-format is very easy readable) So is easy for all members to have overview whats happening, also it is easy to write comments or questions about commits, reply to comments and make proofreading immediately after commit. This is the way how all free software projects where I participate are functioning. ain --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
