It depends how you work:
If you want to work on both computers independently, including ability to export target docs, you need to copy the whole project folder and/or put in in the cloud. To export the target doc, you need the source doc that has been copied to your project directory when starting the project.
If you want to work on the 2nd computer occasionally, you can save the project as package (a CTP file, indeed nothing more than a zip file with the TM, the source doc and the xlf file. Save it (or put it) in the cloud and open it on the other machine. When you are done, save the project and put the TM and the xlf file in the cloud (if it is not there yet).
Then, on the 1st computer, you might replace the xlf file and the TM in the project folder by the two newer versions in the cloud (if the TM is too big or to put it simpler, only copy/replace the xlf file and update the memory by Memory > Import > Import segments from project (assuming that you do not have any unchecked segments that must not be imported into the memory).
In the same sense it is no problem to sync glossaries via the cloud.
To avoid data cluttering and network overload, I'd recommend to pause the synchronization when working on files that else would be constantly synchronized. This is usually no problem with the apps for Dropbox, ownCloud etc.pp. (for iCloud on Mac OS X, it is in the system settings).
Thanks Hans and Torsten!
I hate to admit this, but I do not know how tot find that folder.
Okay, CafeTran usually has a default folder where it puts all its projects. I actually do not remember how to set a certain folder as default, but when starting a project, you are being told – on any system – where the project should be be located. You will find this for any running project under Project > Project configuration. And hey, there is even a button to open this folder.
The folder contains any Project TM or Project TB, the source file copied from the original path with a language code ending (e.g. test.docx becomes test_fr-FR.docx) and a xlf file (in this case without language code - e.g. test.docx will have a xlf file named test.xlf). The xlf gets constantly changed when working with CafeTran so be sure not to put this folder into the cloud or at least to pause syncing during your work - simply imagine a 20 MB or 30 MB file constantly changing. This would be challenge even for a lightning fast connection, not to forget traffic volume limits (if any) and the cloud software that needs to keep accurate track of the newest version without confusing the versions.
The above mentioned folder will later on be the default folder for the target file and the docx file with the bilingual table (if any, for proofreading). Do not delete this copied source file, as you will need it to generate your target file.
>The xlf gets constantly changed when working with CafeTran so be sure not to put this folder into the cloud or at least to pause syncing during your work - simply imagine a 20 MB or 30 MB file constantly changing.
If you like to live on the edge, you could also set the Auto-save project (segments) value to 100 or so.
Thank you Torsten and Hans!
I found the Project File Folder on my laptop. It contains 5 files:
The original file: Filename_en-US.docx
The target file: Filename_de-DE.docx
The xlf file: Filename.xlf
Project Terms: ProjectTerms.txt
The ™ : ProjectTM.tmx
I transferred the Project File Folder to the Desktop of my desktop computer. I then opened a new project, trying to make sure that the Project Location was pointing to the Project File Folder that I had saved on the desktop computer. Unfortunately, upon clicking ok on the Project Configuration page, the translation file did not open showing the already translated segments.
To make matters worse, my laptop computer quit yesterday (it is a late 2010 MacBook Air, 4 GB Ram, 250 GB Flash Storage, 200 GB available storage), and I was concerned that I had lost my ™ file. I do have the exported file that shows the parts already translated into German. Fortunately, my laptop worked fine today, although I am thinking of replacing it.
I must be doing something wrong, but what?
In your suggestions, you say "you can save the project as package (a CTP file, indeed nothing more than a zip file with the TM, the source doc and the xlf file." Is it required for the project files package to be in a zip file? Or do they need to be a .cpt file?
>I transferred the Project File Folder to the Desktop of my desktop computer. I then opened a new project, trying to make sure that the Project Location was pointing to the Project File Folder that I had saved on the desktop computer. Unfortunately, upon clicking ok on the Project Configuration page, the translation file did not open showing the already translated segments.
You cannot simply move the location of your project! Please start a new project at the correct location. You can use the TM!
>To make matters worse, my laptop computer quit yesterday (it is a late 2010 MacBook Air, 4 GB Ram, 250 GB Flash Storage, 200 GB available storage), and I was concerned that I had lost my ™ file. I do have the exported file that shows the parts already translated into German. Fortunately, my laptop worked fine today, although I am thinking of replacing it.
The TM contains all you need :). When you write 'quit' what exactly happened?
I had opened a new project.
I am going to do it once more: The new project is named DIT-MCO 8-22-2015 945 CDT
Here is a screenshot of the project file as it is on my laptop, and as it is on a folder that I placed on the desktop of my IMac:
And here is a screenshot of the Project configuration just before clicking ok to open the new DIT-MCO 8-22-2015 945 CDT project:
After clicking OK, CT opens, but the already translated segments do not show. I did notice though that at the very top of the window, it only says "CafeTran Espresso 2015" instead of "Filename_en-US.docx - CafeTran Espresso 2015"
Please let me know if you would prefer to continue this discussion in private e-mails rather than on this forum.
This was supposed to be the second screenshot in my message above:
I've had a look at your screenshots and other information but I cannot find any error (perhaps others can?).
As you know, der Teufel steckt im Detail, so I'd rather create yet another new project before losing time with finding where it went wrong.
On a side note: It is good to have an experienced Cessna engineer on board :). CafeTran is considered to be the Cessna among the CAT tools.
I tried, but it still did not work. I will, either today or tomorrow, go through your steps and record what I did.
I do not have an original DOCX document. The document I got from my client was a Word 2004 document, that I saved as a docx, of the following type: Office Open XML word processing document. While I realize that the lack of a real DOCX document may be an issue, it works fine in CT on my laptop...
I presume that between steps two and three of your instructions above I need to open CT, and make sure that all boxes are unchecked, both under Translation memories, Glossaries, and under the TMX memory box (where Translation memory and Termbase are).
Good news! I was able to work on my translation on the iMac. I searched through the many tabs in the program and found the statistics utility, among others. Something told me that CT, on the iMac, knew what I had already translated.
What was happening was that the translated test was not visible in the target segments. The target segments themselves were visible. I had to tap NEXT about 3000 times to reach the end the segments I had already translated.
Is there an explanation why the translated text was not visible?
So the target segments where there in the grid, you 'just' had to go to them? By clicking this icon:
You can set the number of segments that constitute one page (e.g. 100), that would have reduced the number of clicks to 30 :).
While switching between projects there is indeed no simple way to go to the last segment translated on the other computer.
As a work-around you can filter on Untranslated segments and e.g. place $$ in the target, go to the next segment, unfiltered and search for the $$. All a bit clumsy, of course.
A feature to go to the next untranslated segment would come in handy.