This is genius. I translate .sdlxliff files several times a week; like you, I could have saved myself a whole lot of trouble if I'd known how to extract the source file myself rather than having to ask the client to provide it separately.
Now all we need is a similar trick for generating a "clean" translated document from a translated .sdlxliff file!
There a bit more info to come on this matter, in particular advice on getting past that 20 MB limit on the embedded file size and what sort of error results if the settings aren't right. It's a TradoZe problem, but those working in that environment may encounter it, and if you run into a case like that at least you'll know how to advise the client.
Now all I have to learn is how to highlight massive amounts of code that go far beyond my window. There must be some kind of keyboard trick to doing it that I don't know.
I was actually working on an alternative importing the SDLXLIFF with a generic XML filter configured to grab only the desired coded content. But when I try to export that as plain text it chokes the tool I tried it with. I could do an XSL transform on the file and direct people to one of those free XSLT pages, but I suspect they have file size limits, and that's probably all way too nerdy for most people anyway.
Select the first bit (as I did in the video). Then scroll all the way down to where that gibberish ends. Shift+Click select the whole range. I should have put a hint on the screen for that, but since it's one of those basic Windows (and maybe Mac & Linux) skills that works in most any app, I didn't think about it. I also recorded that video under time pressure, as dinner was ready, and any delay on my part to set the table might have had serious orthopedic consequences.....
This is genius. I translate .sdlxliff files several times a week; like you, I could have saved myself a whole lot of trouble if I'd known how to extract the source file myself rather than having to ask the client to provide it separately.
Now all we need is a similar trick for generating a "clean" translated document from a translated .sdlxliff file!
There a bit more info to come on this matter, in particular advice on getting past that 20 MB limit on the embedded file size and what sort of error results if the settings aren't right. It's a TradoZe problem, but those working in that environment may encounter it, and if you run into a case like that at least you'll know how to advise the client.
Now all I have to learn is how to highlight massive amounts of code that go far beyond my window. There must be some kind of keyboard trick to doing it that I don't know.
But I tried it with a shorter file, and it works.
I was actually working on an alternative importing the SDLXLIFF with a generic XML filter configured to grab only the desired coded content. But when I try to export that as plain text it chokes the tool I tried it with. I could do an XSL transform on the file and direct people to one of those free XSLT pages, but I suspect they have file size limits, and that's probably all way too nerdy for most people anyway.
Select the first bit (as I did in the video). Then scroll all the way down to where that gibberish ends. Shift+Click select the whole range. I should have put a hint on the screen for that, but since it's one of those basic Windows (and maybe Mac & Linux) skills that works in most any app, I didn't think about it. I also recorded that video under time pressure, as dinner was ready, and any delay on my part to set the table might have had serious orthopedic consequences.....