Hi, I was trying version 1.6 RC5 to see how it was working with XLIFF documents, and while my test files load and can be translated without issue, I had to...
... OmegaT is not specifically tailored to be a xliff editor. Basically source files are monolingual files. Their whole structure copied and the translation is...
Hi Jean-Christophe, ... It would be nice to have a minimal monolingual support for XLIFF: only translating things between <target>. That would assume the XLIFF...
... Yves, thank you for your suggestions. It was considered to have a process fill automatically the "target" field, or to create an intermediate file with...
Hi JC and Yves, ... In conjuntion with an article I recently wrote, I implemented something like this. It's an XLIFF pre-processor and available under GPL (see...
... Martin, If my memory serves me well, it was decided to keep Java 1.4 since even if OSX gets a end-user default version of 1.5, the OSX user base will not...
... Great! On a side note about XML and translation: A possible way to look at how to decide what is translatable or not in XML documents could be to implement...
Hi Henry, ... I just had a look. The only place where I did use xpath is a method with the following signature: public NodeList getChildrenByTagName(Node...
Hi JC ... Right, I do have a faint memory of some issues with Mac OSX. The problem was that 1.5 was linked to a paid upgrade to OS 10.4 or something. Cheers, ...
... Java 1.5 is available from Apple with no hacks only on OSX 10.4 Now, it does happen that there are simple hacks that allow for its installation on 10.3 :) ...
... To get a list of all sub elements with a certain tag name, you can call getElementsByTagName (in class Element). If you really only want direct children,...
... JC, this is what I was talking about earlier. I think it'd be useful to implement this for OmegaT, instead of making up our own version of "translatable...
... My understanding is that the ITS is meant to propose meta info to xml based standards for translatable data specification. It does not actually specify...
Hi Henry, ... When I started working on the SRX implementation, I was smarter (or so I thought) and made extensive use of XPath. It does save a lot of work. In...
... Correct. ... Mmmm... I think I understand, but correct me if not. Knowing the translatable parts and knowing if the client wants these parts to be...
... I think I got the whole point anyway. I'm glad "Learning XML" is going to find practical usages ;) Thank you for pointing that to us ! JC ps: way past bed...
On to SRX... :) I do realize that OmegaT does not have a complete implementation yet. But looking at the segmentation implementation so far I've noticed a...
... From what I understood, ITS has 2 ways of telling us what bits are translatable: 1) By adding the attribute its:translate to an element that contains ...
Hi Yves and all, Here's a message from the TMX Implementation list in which David clarified the use of SRX: DP> The way that it's implemented in SDLX is that...
Hi Henry, ... And 3) by adding a set of "dislocated" rules in a separate standalone file, or somewhere in a document instance. This for example to work with...
... Did you drink too much chouchene for the new year ? ;) ... Here Maxym could comment more meaningfully than I do... ... Besides for the fact that SRX is not...
... 1) will have to be supported eventually if/when the proposal becomes a standard. ... So we could establish "definition lists" based on ITS to ease the ...
... The fact that something is a standard, does not mean it should be supported. It should be supported when the standard gets acceptance and is used enough. ...