Previous Page
Next Page

User Translation

Translating the Menus and Messages

The first step in making your own translation of Aurora Suite is to go to the \Program Files\Aurora Suite 2005\resources\lang folder and create a new folder that is the name of the language you are going to translate.

Once that folder is made, go to the english folder and copy the messages.txt file to the new language folder of the language you are translating to. So if you were translating to Spanish, you would copy messages.txt from \Program Files\Aurora Suite 2005\resources\lang\english to \Program Files\Aurora Suite 2005\resources\etalk2\lang\spanish to start.

Selecting an Editor

To edit the messages.txt file, any ASCII editor such as Windows Notepad will work, however if you require accented characters, you may need to instead use an editor that supports UNICODE. Windows Notepad in Windows 2000 and later support UNICODE as an option when you save the file and this is the editor we recommend. Note that if you use UNICODE rather than ASCII, the messages file will take longer to load at startup as it will take double the disk space of the ASCII version. We recommend you do not use Microsoft Word or other word processor to edit this file, it will most likely damage the formatting rendering your work difficult and possibly unusable. Be very careful of using any editor that does automatic line-length wrapping, since each line must stay intact for the translated file to work.

Anatomy of messages.txt

The messages.txt file contains instructions throughout to assist you in your translation. Here is some additional information about the file:

Defining the Language Name

Within the messages.txt file there is one line that looks like:

LanguageEnglish English (U.S.A./Canada)

This is the one exception to the "don't change the name rule." The name of this line must be modified to include the folder of the language you are translating to, and the string part (green) must be changed to the language name you wish to have presented to the user in the language selection dialog. So for example, for French, change the line to:

LanguageFrench Francais (Quebec)

The word added to the end of "Language" MUST be the name of the language directory that this version of messages.txt is stored in.

An Example

Below are three lines taken from the top of the messages.txt file. These lines are colored to make it clearer the two parts of each line. In the messages.txt file when you are editing, unfortunately the lines are not colored. To translate these, ignore the first (blue) word on each line which is the name of the string, and translate the rest (green).

MSGNOTFOUND >> Message not found, sorry. <<
Copyright Copyright (C)2004 Aurora Systems, Inc., All Rights Reserved.
Support For technical support see

So if I were translating these into imaginary language (since my high school French is very rusty,) they would become:

MSGNOTFOUND >> Gleeker nada founda, toobadda. <<
Copyright Na maken da copies (C)2004 Aurora Systems, Inc., All stufsa reserven.
Support Whensuh broken goda

Note that the blue name parts on each line in both the original and the translated versions are identical.


Some strings in the file have special characters within them, they are a % sign followed by a case-sensitive letter or sequence of letters. These %x markers will be replaced by other information when the string is displayed.

Do not remove, add, or rearrange the order of these markers. Doing so will result in incorrect displays on the screen. There is a possibility that these parameters may need to be rearranged for optimal translation, however in this release this is not supported. Please work with them in the order provided.

SMsg1 Script Error: %S '%S' on line %i

would translate in imaginary language to:

SMsg1 Writen Boo Boo: %S '%S' atsa locashun %i

If your language's syntax would better be served by a translation like:

SMsg1 Writen atsa locashun %i Boo Boo: %S '%S'

Don't! You've rearranged the parameters and the resulting string will either display incorrectly or cause Aurora Suite to crash. Find a way to work your translation around the requirement that these parameters stay in the right order. We have endeavoured to minimize the number of such strings.

When the message is presented to the user, the % markers will be replaced and the resulting message will look something like:

Script Error: Missing Identifier 'strcpy' on line 4


You may find determining context within the messages.txt file difficult. To aid in this, each section of strings has some information before them about where they will end up in Aurora Suite when you run it.

; Speech error messages
SynthTitle Speech Synthesizer Warning
SynthNoneFoundPC No Speech drivers (PCV*.DLL) found. Speech output will be disabled.
SDE_NONE No error.
SDE_ERROR Generic error.
SDE_BADPARM Bad Parameter for Function
SDE_BADERRORCODE Bad Driver Error code returned

As indicated by the red comment line, all of the above messages are related to speech synthesis and are error messages.

Technical Terms

There are computer technical terms and terms related to this program that are used throughout the messages.txt file. Translating these terms can be difficult if you are not familiar with their meaning. Most of the terms can be found in this manual with some looking. I'd suggest using your web browser's "find" feature on the Printer Friendly version. For computer and other technical terms, you might find a computer related online glossary such as this one to help you.

Testing your Translation

Once you have started your translation and have moved the messages.txt file to the correct directory and changed the LanguageXXX line as described above, you are ready to test your new translation. Start Aurora Suite, go into Setup, and select your new language on the Language page. The user interface should immediately change to use your translation.


One issue that will come up during testing is that you will most likely find that some of the translations do not fit in the space provided. All that can be done is to look for these problem areas and try to adjust them to fit.


If there are sections of the file which you are not going to translate, we recommend that you delete those lines from the translated messages.txt file. Any messages that do not exist in the translated file will be taken from the English resources, and a smaller language-specific file will load faster.

Previous Page
Next Page

[Previous] [First Page] [Last Page] [Next]
Page 75 of 101

Copyright (C) 2006 Aurora Systems, Inc. All Rights Reserved.