One client can have three different kinds of resources (actually more, when you have created a web resource).
It's not always easy to see, which pane displays which kind of resource for a client. So I must start using some scheme, like:
mueller for the TM
Mueller for the glossary
MUELLER for the non-translatables glossary
All true. Haven't made up my mind yet.
BTW: I thought that it'd be easy to create a Keyboard Maestro macro that I could assign to Ctrl+Alt+P (for placeable) and use this to add non-translatables to a user specific glossary for non-translatables.
However, the selection of that glossary is currently something that I'm breaking my teeth on.
All my projects have a path like: /Users/Hans/Dropbox/CT/prj/mueller
So I could extract the last part of the path and use this to set the non-translatables glossary:
But how can I determine with project is currently active/which is the project folder that's currently written too. I could also use the memory name/path to determine that, if that's easier.
I could search /Users/Hans/Library/Preferences/com.apple.java.util.prefs.plist for the key "original" and parse its value:
But it looks like this key is only updated when the project has been closed in CafeTran.
Via Bordmittel. I can simply click the button in the New term dialogue box, corresponding to the dedicated non-translatables glossary!
Okay, I've made up my mind:
non-translatables.txt for general non-translatables, like regular expressions and units
field-specific non-translatable lists, e.g. for software localisation
custom-specific non-translatables glossaries that are fed on the fly during the translation process
two examples attached