Gigatrees Blog

Translating Your Gigatree

Translating Your Gigatree

All of the display text that generates is translatable. International users can use this feature to translate Gigatrees into their native language. English speakers can use this feature to display alternate text. GEDCOM data is not translated. If you need to translate the data found in your GEDCOM file you will need to use the Replace Text option instead. You can translate your web pages either manually or automatically (using a translation service). The installation folder's include directory contains two translation files. The first, lang.txt contains only the default display strings. The second, en.txt contains both the default display strings and their associated English translations. The files are delimited by semi-colons (;) with the first column containing the default display strings and the second column containing the translated strings. Neither file is loaded automatically, but must be specified in the translation section as discussed below. When no input file is specified, Gigatrees will use its default strings. When an input file is specified in the configuration, Gigatrees will generate an alert in the build log if either a default string or a translated string is not found within the file. I try to keep these files up-to-date, but occasionally I slip up. If a missing display string is reported in the build log, you can add it yourself to your input file yourself. If an output file is specified, the input file, along with any newly translated strings, will be saved to that file. It is common to specify the same file for both the input file and the output file so that any updated strings will also be available the next time your run the application.

"Translations Options Page (top)"
Translations Options Page (top)
"Translations Options Page (bottom)"
Translations Options Page (bottom)

To translate Gigatrees manually, you should copy the lang.txt file to a new file, add the translated strings to this file, set the Translation Input File option to the disk path of that file and then run the application.

To translate Gigatrees automatically, you will need to use one of the suppported translation services. Gigatrees supports both the for-FREE Microsoft translation service and the for-FEE Google translation service. To use the Microsoft translation service, you must sign-up for a free account at and register a dummy application at to obtain a valid Client Id and Client Secret. To use the Google translation service, you must sign up for an account at and follow the instructions there to create a dummy application and obtain a valid API Key.

To configure Gigatrees for automatic translations, you will need to first enable the service in the Translation options. You must then set the Service Provider to either "Microsoft" or "Google", set the Service Id to the dummy application id (Microsoft only) and the Service Key to the dummy application key/secret. You will also need to set the Language Code to your preferred language. For a list of Microsoft supported languages and codes see: To get a list of supported languages and codes from Google see:

You will also need to make a copy of the lang.txt file and add the disk path of this new file to both the Translation Input File and the Output File.

When Gigatree runs, it will read in the default strings from the Input File file and for any (initially, all) missing translations it will query the translation service requesting a translation string using the Language Code specified. When finished, it will save the results to the Output File. On any error, it will stop querying the service and log an error. Automatic translations, especially on incomplete sentences, can be wonky at times. You may want to make final additional manual modifications to translated strings.

Gigatrees' translations have been tested with various language codes and languages, ranging from Arabic to Zulu, so if you're looking to create a family tree website in your own language, why not try out Gigatrees.

Built with Innuendo (0.1.4)