Quick Start with an SDL Studio package - part 1: https://youtu.be/GPg8TbYLpYE
Quick Start with an SDL Studio package - part 2: https://youtu.be/hKT87eOpj3w
Sorry, I actually do not have the patience to see this all right now (aren't 40 minutes a bit too long perhaps?), surely later. I would not start with possible problems (only "we will address possible issues later on"). This is really confusing IMHO.
Keep it simple, as CT keeps it simple, too. Maybe I had this problem once or twice, but mosz SDL packages work fine here, so I would not waste the audience's time with possible, but not really (?) frequent issues..
And I hope that the manual won't take a SDL package as first and/or only quick start example (instead of a simple Word doc).
Thanks for your great work.
Hi, I had a question about starting a Studio Package project in Cafetran: I just opened one and the integrated TM did not appear - what did I do wrong?
This sometimes happens. Sometimes because the TM was placed in a wrong folder inside the zip. Best: add .zip to the package name and unzip it, look for the TM.
As a comfort: in 99% of the cases, the recognition works.
Oh, and you can make a ticket so that Igor can have a look at why the TM hasn't been found.
Thanks for your replies - I don't have a .ZIP just an .SDLPPX
Can I still look up the TM somehow?
Rename the .sdlppx to .sdlppx.zip. Sorry for being not clear here. If you prefer, we can have a quick Skype or teamviewer session: just mail me at firstname.lastname@example.org
Eh, it is much easier to drag and drop the package on the dashboard (= start screen) of CT, isn't it?
After that, for a package named "hallelujah.sdlppx" there will be a folder "hallelujah" with some subfolders. Usually these subfolders will be e.g.
Some of these folders (not the SL and the TL) are optional.
It is good practice to check always if there is a TM or not (or if there are even several TMs). There is no problem to add a SDL TM or the whole folder (in case of several TMs) later on after starting in CafeTran – no need to convert them. As the return package won't contain a TM, it is good practice to set the Studio TM(s) to read-only.
Hope this helps.
> Eh, it is much easier to drag and drop the package on the dashboard (= start screen) of CT, isn't it?
Yes, it is.
Thanks for all your help guys - I found the TM and was able to work with it. I'm still only using Cafetran for a few projects at this stage. One client has asked me for a returns package - no problem - as well as an export of the final translation in Word. Am I right in thinking the latter isn't possible with CafeTran? I have the original in Word format.
as well as an export of the final translation in Word. Am I right in thinking the latter isn't possible with CafeTran? I have the original in Word format.
You can create the target doc only with Studio and with no other tool. For short texts you have the option to create a CafeTran project, import the source doc and work with the TM, but the segmentation will be different, so you have to rework a bit (and for this reason it is not an option for middle long or long projects).
On the other hand side, Studio customers are able to open the xlf created with CT. Some clients do not care whether they get a xlf or a sdlxliff file, as long as the cleaned file is being delivered.
When I am done translating the Studio Package and save it, where do the sdlxliff files go? Back into the sdlppx package?
They are saved into the unpacked sdlppx package folder. When you create a package, the folder is packed back.