Re: PO-based Documentation Translation (wa Re: Weekly i18n statusupdate)

[Gudmund Areskoug <fta algonet se>]

Hi,

Stephen Holmes wrote:

> TMX can also be used as a document content repository format -
> though the intent is portability in the separation of content
> from structure.

just BTW: XLIFF is for what you first suggested TMX for.
http://www.opentag.com/xliff.htm
http://www.oasis-open.org/committees/xliff/documents/xliff-specification.htm
http://www.oasis-open.org/committees/xliff/documents/xliff-core-1.1.xsd

http://www.opentag.com/tmx.htm
http://www.lisa.org/tmx/tmx.htm

Since you've got to segment stuff anyway to make good use of 
translation memory content, compendia etc. leveraging and 
terminology consistency, po's probably the smarter and faster way to 
go here.

If problems of the kind you suggested pop up, it's probably (?) 
easier solving them by means of segment joining and splitting within 
whatever tool is used.

Just my 2 öre :),
Gudmund