How to translate Makelangelo software
As of Makelangelo Software 7.23.0 it’s now easy for you to translate Makelangelo software into your favorite language. Here’s how!
All existing translations can be found…
…on Github at https://github.com/MarginallyClever/Makelangelo-software/tree/master/src/main/resources/languages.
…on Crowdin at https://crowdin.com/project/makelangelo-software
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE language>
<language>
<meta>
<name>English</name>
<author>Dan Royer ([email protected])</author>
</meta>
</language>- The
<name>field is the display name of the language as it appears in the selection dialog. It MUST be there. - The
<author>field should be your name and contact. Credit where it is due! It MUST be there.
Save your new file
If I am translating to Pig Latin I would save a copy as piglatin.xml and put it in the same folder as the Makelangelo-[version numbre]-with-dependencies.jar file. On Windows computers that would be in the C:\Program Files\Makelangelo\app folder. When I run the app it will load the new XML file first.
Missing Translations
If a translation key is not found in the file it will write “Missing:[key]” in the app.
Now I’ll have to add the missing values. In the XML file, I’m going to fix one value by adding the following:
<string><key>MenuMakelangelo</key><value>File</value></string>Each <string> element must contain a <key> and a <value> element. Keys should never be translated. Values should always be translated. In the example above, Missing:MenuMakelangelo will be replaced with File.
A very small number of values have a %1, %2, and so on. These will be replaced with a number or some other value from inside the app.
Share your translation
When your translation is ready, please share it on our forums. Then everyone can download your work, tell you how grateful they are, and we can package it in the next release. We prefer pull requests.
