Translate this page

macOS - Starting JaVaWa applications & language issues

Most of my programs are 32 bit, therefore they won't work on MacOS Catalina. The exceptions are CleanEject and JaVaWa IMGname, these two are 64 bit.

With the release of OS X 10.8 Mountain Lion Apple has introduced a new security feature: Gatekeeper. With Gatekeeper it isn't possible to install just any application; only those that are distributed through the Mac App Store and/or are signed with a certificate. To obtain such a certificate for your applications a developer needs to join the "Mac Developer Program" at an annual fee of $ 99. Very nice, but when you give away your software for free it's becoming an expensive hobby... (yes, I do get donations now and then, and no, that doesn't cover the Apple fee)

So the JaVaWa applications won't make it to the Mac App Store, and won't get a certificate.

When you download a JaVaWa application and try to run it, depending on the security settings of your system you will get one of the following messages:

GateKeeper 1st message A  Gatekeeper 1st message B

This problem can be solved this way:

Gatekeeper 2nd message A  Gatekeeper 2nd message B

When you click "Open" the application will start up normally. You need to do this only once; macOS remembers your choice. The next time you can start the application in the usual way.

Authorisation issues

Some of my programs need to communicate directly with the underlying system to function properly. For certain MacOS versions, permission is requested from the user. If this permission is not given, an error message will appear every time the program is used. This problem can be solved by correcting the settings at "System Preferences". Go to "Security & Privacy" > "Privacy", select "Automation" and check every item that belongs to the program.

Automation setting

Language issues

Many of my programs are available in Dutch and English (and some in French). A German user of Yosemite reported that my programs used Dutch for the interface, instead of the default English. When the same happens to you, this is the solution:

Open System Preferences > Language & Region > Language, click (+) to add the English language (if it's not already present in the list). Then drag it to the second position on the list, so that you have your own language at the top and English next (as your second language).

If an app does not have resources for the first language on the list, macOS should use the resources for the next language on the list. If you're not using English it's good to have English on the second position, because if an app is not translated to your language, the English version will be used. If you have only one language on the list, Yosemite assumes another language as the "fallback plan" for apps not localized to your language.

This solution was posted by user "g-7" on MacRumors
Last updated: 2023-11-03
Copyright © 2008-2024 JaVaWa | terms of use | contact