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)?
Torsten: maybe different shades of, ha, grey
Very funny indeed :). Did you enjoy the reading?
Too little time for reading. I must confess how I ever managed to read most of the books in my library (the other unread stuff is of my wife). But no, the genre of painters' biographies does not interest me too much (that's what this book is about, isn't it?).
- Since the removal of a save/restore settings function (I understand it was removed because it broke things), the surefire solution is to revert to a previous system full or partial backup. Isn't backing up a highly expected behavior for translators? I use Back In Time on Linux.
- @michael and @treI mostly use Add segment to memory and go to next segment (Alt+Down for me), and Add segment to memory and go to next untranslated segment (Ctlr+Shift+Down for me). I mostly do not use Checked segments. When I do, I do that by filtering segments by number, example: "1-233", and Set checked status. I sometimes use the Bookmark segment function for remembering partial deliveries/goals/"game progress".T
I feel the discussion of what are the best/most sane default settings is an important one, but one that would require a thorough user experience review. I'm quite startled when I revert to default settings, but what imports me more is the possibility to set them to my taste. And that, CafeTran provides aplenty.
> previous system full or partial backup
Restoring a previous full backup is IMHO only an option in case of full crashes. And for partial backups the problem is that we do not have a „.cafetran“ subfolder or sth similar, but some files spread around the system (also depending on your OS). For this topic see also here.
Sorry tre, I meant partial restore (specific files/folders) of a full - incremental - backup, not partial backup.
>Sorry tre, I meant partial restore (specific files/folders) of a full - incremental - backup, not partial backup.
CT is so old perhaps that I do not remember whether it ever had a backup and restore feature Jean describes (did it?).
Just in defence of Igor:
A backup and restore feature (restoring can be a program-assisted or a manual process) might make some problems, such as:
Sure, you can tell users to use a feature at your own risk, but most or many translators are a PEBKAC, so this could mean to have more support work. The other solution is to create OS-specific settings that are not interchangeable, just to avoid hassle, or to create parameters inside the file (e.g. "OS=Windows", "Screen size=27", "Resolution=1024x768") that stop the restoring process (well, only if program-assisted) if it does not fit the host OS. You see, things can quickly go complicated.
But having all or nearly all settings at one place would be really a nice-to-have (I wonder if there ever was a user that missed his non-translatables lists, additions to his custom dictionary and all the other things that are inside the Mac app after doing a "clean" reinstall).
BTW, I know that I might repeatedly be asking for certain features, but at least I am learning and in the meanwhile create hyperlinks to my elder posts, just to underline my persistence (and maybe ignorance of the „Igorsh“ principles) and to link the threads.
Exporting and importing of preferences might return in the future. It caused issues with some settings (some paths, screen resolution, complex layouts and docking positions etc.) when importing them to CT installation on another computer.
>It caused issues with some settings (some paths, screen resolution, complex layouts and docking positions etc.)
At least screen resolution, complex layouts and docking positions could be left out, since they can be handled via templates. About paths: perhaps let CafeTran ask them for them on first start up?