SDL Support wrote:
Grzegorz Gryc wrote:
If it doesn't work, take a look on Swordfish (a 30 days trial is available), it permits to convert SDLXLIFF to TTX.
If it works OK, import and translate in MQ, then export an convert back to SDLXLIFF.
Risky I think.
The CAT hopping is always risky.
The cascaded CAT hopping may be a pure suicide but sometimes it's still the best way to deal with the initial crap.
I played with this a little as it's shown up in a few threads and if your source file is plain text it's ok (although it still won't give you the match values) but if your file is formatted I think you are likely to find problems with some formatted source text being unavailable for translation, changes made to tags that prevent a proper clean up etc.
Yes, I know Swordfish sometimes may behave incorrectly (e.g. joining segments across the paragraph boundary causes errors but, at least, Swordfish displays a warning).
If you know well where the problems may arise, you simply make attention.
If you don't know what may go wrong, you must make some tests 
But let's not get into picking holes, the point I really wanted to make was just about the risks of going to TTX through the mechanism GG mentioned... unless I just fail to see how to create the TTX properly in Swordfish (also possible
)
Well, it's not a "true" TTX but it's still a valid TTX-like format you can easily process in TagEditor (or compatible) and export in Swordfish
Cheers
GG
Login to reply/comment 
