I usually reuse projects, as I always did in DV.
But in the last few days I did some errors during the creation of different projects in nested folders, and now it happens that I have several ProjectTMs in these folders, while I need only one in the head folder where I want all translation segments of the various subfolders go.
Now, how can I instruct CafeTran to use only the ProjectTM in the main folder and ignore those in the subfolders?
As I understand, you wish to use a ProjectTM.tmx single file created in a previous project for the new project. Then, just choose this single .tmx file in the Dashboard > Translation Memories panel. I would suggest renaming in before, not to confuse it with the ProjectTM of the new project.
Sorry, in a hurry I confused TMs with Glossaries! My bad.
But let me rephrase my question: since I prefer txt glossarries for size and ease of maintenance, is it possible to have only one txt project glossary for all projects in a folder? For certain types of works I usually create the following folder structure:
D://CafeTran/Projects/Project Type A/Project 1, Project 2, Project 3, etc.(where Project Type A is only a container for Project 1, 2 and 3). Then, each of these three projects contains a bunch of translation files.
Again, the Project Glossary (txt) should be only one and the same for every project that add to the Project Type A main folder. Is this possible or the only solution is creating a tmx glossary do add separately?
> is it possible to have only one txt project glossary for all projects in a folder
Of course, it is possible. Just create a new glossary (or add the existing one) in the Dashboard (Glossaries panel > New or Add glossary) saving the glossary file anywhere you wish (e.g. in your pojects main folder), and disable (uncheck) Project Glossary in the Dashboard for individual projects.
Igor: Of course, it is possible.
You are right, I feel ashamed that I asked a question on a subject that is explained very well everywhere as soon as you get closer to CafeTran. Sorry for this waste of time.
Apart from certain functions that objectively are not very intuitive (although very useful) and a certain nomenclature that differs from that of mainstream CAT tools, after some initial difficulties I'm beginning to think that after all CafeTran is not that "difficult" to understand for translators coming from other CAT tools, provided that they approach it with an open mind, which might be not that easy for people of my age...
Of course, if a thorough manual existed in one place everything would be a lot easier for newbies, but probably it's only me because I don't see many newbie questions here.
In any case, one thing is true: CafeTran is fun to use the more you get to know it.
> translators coming from other CAT tools, provided that they approach it with an open mind
Yes, that's very true.
> which might be not that easy for people of my age...
I strongly disagree. :)