Okay, here we are.
I am really a fan of CT, but this is a bit too much. I would have loved to unleash the power of CT with a new machine, but this is disappointing. As stated above, this is High Sierra with 8 GB allocated (and 16 GB for the whole machine). At this moment I switch back to memoQ and only work on mqxliff files, hoping that the Alt key keeps working and that I do not need to open resources.
Any chances to get these things resolved?
All of the above issues, I can only confirm the right ALT key issue on my Mac (High Sierra and Java 9.0.4). It stops some operating system keyboard shortcuts. This is a Java issue as I experienced it in another Java (Swing UI based) software too. We need to wait for the fix from Oracle. Please use the left Alt key for those system shortcuts as it functions okay.
> On my systems (the old and the new) both Alt keys stop working.
They stop working after pressing the right alt. Press the left one instead.
> Concerning the other symptoms
It makes me wonder why it kept working for you just fine for so long and all of the sudden, those issues appear in your system without any change to CT in the last few weeks.
> They stop working after pressing the right alt. Press the left one instead.
Nope, this has no influence. so even an amputation of my right arm (that I could perhaps consider otherwise) would not help here.
> It makes me wonder why it kept working for you just fine for so long and all of the sudden, those issues appear in your system without any change to CT in the last few weeks.
If you read the postings more carefully, you would see we are talking about a new machine with High Sierra (the elder one had 'only" Sierra) and much more RAM. This is also the reason why I chose the title.
Torsten: ...a newer, more powerful machine
Would that be the 2017 27" iMac? Fusion Drive or SSD? I want to buy the latter, but I still can't get it here. The SSD version could be part of the problem:
I still use the late 2009 27" iMac with an external, FW800 SSD. It runs under High Sierra, but it wouldn't change the file system of the SSD to APFS while installing HS. Java 1.9. And no problems here.
I wouldn't be surprised if the file system caused the problems, or rather, that His Igorness didn't test Akua on a Mac with the new file system.
Switching resources on and off on the Dashboard (DeepL, perhaps also others) results in a higher frequency of successfully opened projects. Maybe a problem with the internal browser and its RAM usage.
When I change the RAM in Preferences, the cafetran.conf in the Package remains unchanged. Is this correct?
Torsten: Fusion Drive (I wonder whether this is different to SSD, as AFAIK frequently used apps will be administrated on SSD).
The new file system can't be installed on the Fusion Drive. That's why. That also means it can't be the problem...
Torsten: When I change the RAM in Preferences, the cafetran.conf in the Package remains unchanged. Is this correct?
Good question. I asked it years ago, and forgot the answer, so I changed it manually in the .conf as well.
Torsten: ...as AFAIK frequently used apps will be administrated on SSD
It's dynamic, so macOS decides ad hoc what should be on the SSD. The SSD will always be fully utilised. If you have the 1TB fusion drive, everything that would benefit from storage on SSD for a particular activity will be on the 32GB SSD. That's usually good enough for translators, but for video-editing and things, a larger SSD would be preferable to a fusion drive, although a 2TB (and more) FD comes with a 128GB SSD. To be on the safe side, I want the iMac with SSD only (but you can't always get what you want, says Mick)
There is no way to fix something easily which does not occur in my systems (here also Mac with High Sierra, 8 GB RAM, no APFS yet). I can only guess that SDL TM included in the Studio package hanged CT when opening this package on your High Sierra. In the latest build of update 1 (2018030201) , loading of SDL TM from the SDL package is slightly delayed until other resources open in their tabs.
Nowadays, cafetran.conf file is not used on Mac machines. The Java memory settings are stored in Info.plist file located inside CafeTran.app package.
IK: There is no way to fix something easily which does not occur in my systems
That's the problem. If you sell an app for all operating systems, you should check it on all operating systems. And preferably before they are released, which isn't a huge problem for macOS because there are betas at least a year before the launch. The hardware can be another problem, but it's your problem.
> If you sell an app for all operating systems, you should check it on all operating systems.
I always do it with the latest official versions of major OSes. In this case, the OS (High Sierra on my Mac) is not an issue.