CafeTran
How can we help you today?
How seamless is interoperability with SDL Studio?
>And, there is also a free Java program (here).
I've just tested Toon van Nellen's Java app to convert a Multiterm termbase in an SDLPPX (unzipped first) to a tab-delimited file.
Question to Igor: Since this seems to be possible, wouldn't it be a nice service to CafeTran users who don't possess Studio, to implement the extraction of termbases too?
Perhaps Toon is willing to share his code, I don't know. The answer is one e-mail away ;).
> And, there is also a free Java program
That looks fantastic!
I do have Windows, but I only have a very old version of Access (and LibreOffice doesn't seem to be able to import Access databases).
Thanks a lot!
Martin
Martin: How difficult is it to convert a Studio glossary to a text/Excel/CSV file? Is that possible even if I don't have Studio, or would I have to ask my client to do the conversion?
It's not particularly difficult, it can be done without Studio. It can be a lot of trouble though, especially if the termbase is multilingual.
http://cafetran4mac.blogspot.com/2015/04/sdlxliff-sdltm-and-sdltb-in-cafetran.html
That's for OS X of course, but if you still use Windows, you can either use MS Access, or something similar to Axxess.
H.
> but some amount of additional work is required on your part if:
>
> you want to use Studio's termbase (you've got to convert it somehow into a text or Excel file)
I've never translated a Studio package in CT either (but some of my clients might ask me to), so my question is: How difficult is it to convert a Studio glossary to a text/Excel/CSV file? Is that possible even if I don't have Studio, or would I have to ask my client to do the conversion?
Cheers,
Martin
> My next question - what does 'finalise' actually do??
It sets the 'Translated' status for target segments and saves the Studio project.
Igor
My next question - what does 'finalise' actually do??
It's clear to me now.
After you finish the translation of sdlppx package, finalize it and then export back to package via Project > Export > To package.... Then, you have two options for the export: a Project package or Return package.
The translated return package (sdlrpx) should be opened in Studio which created the normal (sdlppx) package. If you did not create this project yourself, export to as a normal project package (sdlppx) to review it in your installation of Studio.
Igor
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.
Jeremy
I just want to confirm if the issue I've been experiencing is the same as yours.
The project file in the project folder created by CT has a timestamp (?) that is not included in the package file name, and it cannot be opened in Studio.
I confess that hacking the files like this leaves me feeling nervous. (What unintended consequences might await?)
Igor, genuine no-hacking required interoperability with SDL would be a huge selling point for CafeTran.
Yes I can open the individual target files directly in Studio as described by Masato above.
I'm reluctant to go down that route, however, as if I spend a day reviewing and correcting everything in SDL and then find that CafeTran doesn't like the modified files, then I'm sunk.
If there a way of opening the project in SDL?????
I tried zipping up the contents of the project folder and renaming the .zip file to .sdlppx, but SDL wouldn't open it ((Igor if you're reading this, this may be something for your attention):
When I try to open it, I see the 'Review package' screen, but note that the package type is shown as a "Return package".
When I then click on "Finish", the 'Importing package' screen is displayed, but I get the following error message:
"Failed to import return package because it contains a project that does not exist in your setup:
(Name = '{0}', ID = '{1}')"
I'm speculating that somewhere along the line, CafeTran has set some flag in the project file to say it's a return package. (I did previously use the create return package function in CafeTran for testing purposes).
Would appreciate any help anyone can provide.
Cheers,
Jeremy
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.
Jeremy
amos
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,
Jeremy