After a power blackout all settings are gone.
CT has rest me to my elder license (that still is valid). The TR tables are still there, everything else has vanished from the Dashboard.
This is a f.. situation and happens only when you are in a hurry. One more argument to have all settings in one path. You are not even able to open the project templates (what would save my day at least a bit).
Any chance to get back the settings (here under Mac)?
> Why can’t you open a template (as you know, the items of the Dashboard are stored there too)?
If I knew how... Drag and Drop does not work.
> As for the settings you could try to restore the Java plist file
Eh, where exactly ... the library folder is quite huge...
Save your current template to the folder where you keep all your CT templates. After that CT should list them all again.
Ha! That's what I'd wanted to suggest too :).
Anyway, the plist: /Users/<your name>/Library/Preferences/com.apple.java.util.prefs.plist
If I remember correctly, after restoring this, you'll have to import your license again.
> Save your current template to the folder where you keep all your CT templates. After that CT should list them all again.
That simple ... great!
Thanks for pointing to plist, Hans.
Anyway, this must be good for something.
The following settings were not remembered:
You need to remember that templates are Project templates - not meant for all settings backup. The only sure-fire method to protect against power outage is a system-wide backup of your files (e.g. Time machine on Mac).
> applying QA to checked segments (why is this deactivated by default? this can destroy – eh – happy days, at least for users who set segments to check and do a spell check/QA afterwards*)
Checked segments are supposed to be checked by definition. That's fine if you wish to do the order way round e.g. mark as checked, and after that spell check or perform other QA actions. However, you cannot expect that applying QA to checked segments to be a default option. BTW, for CafeTran projects, the final check of the target document is usually done in the target application (e.g. MS Word) itself after the export.
Wow, only just realised that QA for checked segments is off by default. I was wondering why QA never found anything. I think this should definitely be set to ON by default!
I use the KBS: Add checked segment memory and go to next segment as I translate, to help me visually differentiate which segments I have translated so far.
In my opinion, the confusion is caused by the following:
In CT, segments can have two different statuses:
1. Translated (which is basically just for SDL files, and all but useless in CT), and
I would strongly suggest changing the wording from Checked to Confirmed.
In this context, "Checked" is ambiguous. Does it mean that the translator has checked, as in proofread, the relevant segment? Or does it mean checked, as in checking off (ticking) something from a list, with a tick/check mark.
If you want to keep the current naming scheme, can we then have a (different) highlighting colour for Translated segments, so that we can actually use it in the common sense of marking the segments as having been Translated or Confirmed? (like in all other CAT tools)
> Wow, only just realised that QA for checked segments is off by default.
Well, after a reinstall some months ago I reinstalled the spell checker several times before realizing this (and wondered why CT did not find double spaces and other mistakes).
> I would strongly suggest changing the wording from Checked to Confirmed.
Seconded, this is only logical (though assuming Igor does not want to change the wording).
> can we then have a (different) highlighting colour for Translated segments, so that we can actually use it in the common sense of marking the segments as having been Translated or Confirmed?
Seconded (but colours are going out, I fear, maybe different shades of, ha, grey).
@ Igor: Sorry, I read only the first sentence before replying above.
> Checked segments are supposed to be checked by definition.
It is difficult to speak of a definition here. I am strongly influenced by the memoQ philosophy. You might add anything to a segment, but you will confirm it in the end. From any point of view „checked“ in CT excludes any non-digital or external checks (one more argument to switch to Confirm instead). The changed colour will lead many rookies to take „Checked“ instead of „Translated“ without being aware of this definition.
Naming apart, at least for a while, why don't you consider the recently added Locked status (for CT projects) as a synonim for confirmed segments?
It has the same colour, it has no filter (only unlocked) and (even if) it does not have a shortcut, has it? Is "locked" now an official state? I thought it was for external file formats only.