Localization (Translating Into Another Language)

Translating FlightPath into another language is relatively straight-forward.

You will need to be using the latest version of FlightPath (version 4.3.2 or above).  Download and install the Locale module.

This module will allow you to create a new language entry for your site, then "discover" untranslated text.  You can then export the untranslated "sources" to an XML file.  It is then your job to edit the XML with a standard text editor (Notepad++ is excellent and free), then re-import your changes back into FlightPath.

See the Locale module's READEME.txt for more complete instructions.

 

Do you have a translation you'd like to share?

If you've translated all or parts of FlightPath (or an addon module) into another language, we'd love to post the XML file online for others to use!  Please use the Contact form to notify the project maintainer.

 

What languages and character sets are supported?

Generally, any language which can be represented with the UTF-8 character set is supported.  UTF-8 comprises most characters from most of the languages on Earth, and is a standard around the world, so there is a fairly good chance that FlightPath will be able to be translated into your language.

 

What if the characters look weird?

If your characters end up not displaying correctly in FlightPath, make sure that (1) your text editor can save in UTF-8 format (by default, Notepad++ seems to work fine with no modifications), (2) make sure that your browser has been told to use UTF-8 character encoding in the site's theme.  This is set by default in the "classic" theme which accompanies FlightPath.  Basically, make sure this <meta> tag is present at the top of your theme:

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

This tells your browser how to output characters onto the screen.  It goes between the <head> </head> tags.

It could also be possible that your database table is set to an unusual character set.  Make sure the locale_sources and locale_translations tables have the default character set to "utf8".  This should be set by default when the module is installed.