> Those fields should stick in CafeTran-based project. Then, the project properties propagate to TM attributes just fine.
I see, that explains it then. I'm translating a Trados package.
> I've tried to set Project and Client values in Project properties but nothing seems to stick
Those fields should stick in CafeTran-based project. Then, the project properties propagate to TM attributes just fine.
"One of the easiest is to systematically create a ProjectTM (simply tick the box in the Dashboard) for each project (and attach your Huge TM as "read-only").
At the end of the project, make sure your ProjectTM is fully up to date (Memory > Import > Import segments from project).
Then, you can set your Huge TM as non-read only (just to complete this action, then save it and switch it back to read-only), use Memory > Join memory, and select the ProjectTM to merge (if that memory is open, you may need to close it). Now your Huge Memory will include that ProjectTM units, with their separate properties."
Thanks! This seems to work :)
Hans, please do not summon me in the forum. Thank you.
---
Note regarding the above provided explanation. In TM options > Filter, the Properties filter is for filtering not for setting TM properties.
These properties are defined during Project creation (recommended) or in Project project configuration, if not already previously set.
---
Project configuration settings are project-specific.
You can set properties to TMX units via Task > TMX memory > Set property for TMX units and Remove property from TMX units. When you click "Property names", you can reuse previously defined property "Names" (see Preferences > Definitions).
This should work both in the translation workflow and in the TMX editing worfklow (where you edit TMX files).
Unless mistaken, properties tasks are applied to all TMX units for a given memory, however.
---
Regarding your huge TM method and the use of project properties, there are many to go about it in CafeTran.
One of the easiest is to systematically create a ProjectTM (simply tick the box in the Dashboard) for each project (and attach your Huge TM as "read-only").
At the end of the project, make sure your ProjectTM is fully up to date (Memory > Import > Import segments from project).
Then, you can set your Huge TM as non-read only (just to complete this action, then save it and switch it back to read-only), use Memory > Join memory, and select the ProjectTM to merge (if that memory is open, you may need to close it). Now your Huge Memory will include that ProjectTM units, with their separate properties.
An even simpler method (but caution is advised, since you need to understand how TR works, and its limitations) is to use Total Recall and add the ProjectTM to Total Recall at the end of the project, (Memory > Store memory in Total Recall) for future reuse.
Thanks Jean! I guess that makes sense, even though it seems to mean that you cannot have more than one Project/Client per TM. I'm so used to using one huge TM and just changing the attributes between projects. I hope it's somehow possible with CafeTran as well.
I suppose one option is to split my TM into smaller pieces based on clients and projects and change my whole approach. But that sounds like some serious WORK!
When you create a new memory, you have to click on the Filter button, then you can set the Properties:
Regarding assigning properties to existing memories, some other user has to answer your question :).
Hello and good morning, Jean!
vmartik
I couldn't find this topic anywhere so I hope it's not a duplicate. I've been using Trados these past years and I'm used to saving things like Client and Project name with each TM segment.
I can see the ones created with Trados when looking at matches but for some reason I cannot create any new one with CT (I tried this with old, converted tmx files and a brand new one).
Am I missing something? I've tried to set Project and Client values in Project properties but nothing seems to stick – the fields are empty when I re-open the configuration and no info is saved with new added memory segments. The only attributes are Creation Date and Creation ID. I'm running 10.7.