GrandPerspective is fully internationalized and supports Base Internationalization since May 2016. This means it is now easier to provide translations. You do not have to update the UI anymore in Interface Builder.
If you want to help out with making GrandPerspective available in your mother tongue, or any other language you speak fluently, go to the GrandPerspective Localization forum to express your interest. I will then get back in touch and provide you with the XLIFF file that you can then start translating.
Adding a new localization to GrandPerspective requires creation of an XLIFF file that contains all translations. This file can be imported in Xcode to create a new version of the app. See Apple's localization documentation for details.
In short, we will follow the following steps:
Note: If you want to, you can run GrandPerspective with your translations before you return the translated XLIFF to me. This requires using Xcode and retrieving the GrandPerspective source code. From Xcode you can then open the GrandPerspective project, import your XLIFF, build the application yourself, and run it. However, this is not recommended unless you are familiar with building Mac apps.
You should not translate the following:
Not all strings in the XLIFF file require translation. This holds for all strings that are hidden or placeholders which are replaced at runtime. This includes the following:
Use Apple's terminology when possible. Check Apple applications to see what terms are used in your locale.
If you decide to also translate the help documentation watch out for the following:
Do not translate the content of the AppleTitle meta tag in the main help file. The content of this tag in the GrandPerspectiveHelp.html should be set to "GrandPerspective Help", as the help documentation will otherwise not load in the Help Viewer. The reason is that the content must match the value of CFBundleHelpBookName in the application's Info.plist file (which is not localizable).