Start a new topic

How seamless is interoperability with SDL Studio?

I've been using CafeTran for a while yet, but I haven't got around to using it for a Studio project.

I'm trying to work out whether trying to use CT for a Studio project is going to save time or whether it's quicker just to use Studio (of which I am not a fan at all).

I've looked at various postings and resources on this subject, but it is still not clear to me how easy it is to work with Studio packages in CafeTran in practice. There are a lot of forum postings about how to get around this or that limitation of processing Studio files in CT, which doesn't exactly inspire confidence.

If any of the experienced hands could give a quick run-through of the basic process for and, in particular, pitfalls of translating a straightforward Studio Package in CT, I would be very grateful.

Many thanks,


Hi Masato,

yes, the project file has a timestamp, but it's not added by CafeTran.
The package file is just than a zip file . If you look inside it (on Ubuntu Linux the native archive manager will unzip it directly, but otherwise just rename a copy to .zip), you'll see that the package already contains this timestamped project file. All CafeTran (and indeed Studio) does is unzip

Coming back for a moment to the original topic, as far as I can see, all you need to be able to switch seamlessly between CT and Studio is for both programs to be 'aware' of the project.
What do I mean by that? As far as I can tell (I'm open to correction), there is no way in either CT or Studio to start work on an already unzipped package - in both cases you need to be able to select the project from the recently opened projects. (This also meant that I wasn't able to open this Studio project on my home computer - Igor, is there a workaround for this??)

One solution would be to open the package in CT (or Studio), immediately close it, delete the unzipped version then open it in the same location in Studio (or CT). Then, as long as you don't try to open files at the same time, you should be able to switch seamlessly between the two. One caveat - that's assuming that both programs use the package name as the folder name. This is normally the case, but in my experience not always.


>Also, SDL is a big organisation, mainly focussed on big clients. When you have an issue, you'll be contacted and they'll listen to you. And that's it.

I meant: when you're 'only' a freelancer, they'll have the courtesy to contact you. But that's it then.

There's no Igor trying to help you, even in the early evening. Of course this is related to an installed user base, but it's a great support.

Hi Masato and Hans,

many thanks for your extremely helpful responses, which answer almost all of my questions.
If those are the only limitations, then I'll be very happy to use CafeTran to process Studio projects.



Don't export as a return package but as SDLPPX. Open this in Studio.
Following on from the above, I've just finished my first run-through on my first Studio project in CafeTran and now want to open it in Studio (2014). How do I do this.
The project was supplied as a package.
I tried opening the .sdlproj file in Studio, but that didn't work (got an error message). Do I need to zip it back up into a package??
Note: I can produce a return package from CafeTran, but I really want to see what it looks like (and probably proof-read it) in Studio first. I assumed I could switch between CafeTran and Studio at will. Was that overly optimistic?

Please help!!

Many thanks,

I think Hans can give you much better advice, so this is a workaround just in case.

1. Can you open the sdlxliff file(s) in the project's target-language folder directly with Studio? It contains your translation.

If you cannot, please try the following workaround.

1. Open the finished project in CT once again, create a new TM, and import the project segments into it (see Memory menu), and save.
2. Open the original sdlppx package with Studio, create a project folder, and save.
3. Open the file(s) in the project's target-language folder with CT, perform the task "insert all exact matches" with that new TM and then the task "set translated status for target segments," and save the project.
4. Now, you can see the translation in Studio.


BTW, do you see something like a time code added to the Studio package file name? It occurs in my environment.


Hi Masato.

thanks for your suggestions. I can indeed open the target sdlxliff files, so at a pinch I can do my proofreading with copies of these. Still hoping Hans might be able to tell me the easy way to do this.

And yes, there is something resembling a timestamp on the .sdlproj file, but note that it's also present on the .sdlproj file contained in the original packge received from the client and appears to be unvarying.



Login to post a comment