The EASA web pages may display languages other than English via translation tables stored within a spreadsheet.

System translation is focused primarily on User mode web pages and generic EASA Client and Web Browser Client content. However, Author and Administrator modes allow translated menu labels.

Language preferences are set in the User's browser, if the browser language setting does not match an existing language configured in EASA, then the default English version will be displayed.

The EASAP Builder only supports English.

Managing languages in EASA is performed on the Languages page under the Configure tab in Administrator mode. To add a new language and perform the required translation, please perform the following steps:

• Open a web browser on your computer and go to the EASA web address.
• Log in to EASA and then set your mode to Administrator.
• Select Languages under the Configure menu.
• Click on Add Language button.
• On Add Language page that appears:
  • Select the language from the available list and then click on the Add Language button.
  • A new row in the language table appears with the proportion translated set to 0%.

To perform the translation for the new language:

• Click on the Export Data button () in the Export column of the Languages table.
• Save the resulting spreadsheet file.

The spreadsheet will contain a number of sheets each of which has four columns. For more details on the columns and sheets in this file see:

• Translation Spreadsheet Columns
• Translation Spreadsheet Sheets
• Next, open the translation spreadsheet within Microsoft Excel or another spreadsheet tool compatible with Excel (xls) files
• Translate the values in the third column of the various worksheets to the appropriate values for the language to be translated.

An example of a translation spreadsheet after being translated is shown:

• below in the next paragraph.
• Save and close the spreadsheet.

Rare error diagnostics and common jargon words like 'EASA' may be left untranslated as they will not diminish usability.

• Finally, import the newly translated spreadsheet back into EASA by clicking on the Import Data button () in the Import column of the Languages table to be taken to the Import Translation page.
• Use the Browse button to select the translated spreadsheet file
• Click on the Import button.

Repeat the process of updating a language by exporting the translation spreadsheet, modifying the translation values and importing the spreadsheet back into EASA when required.

The first column in the worksheets in a translation spreadsheet, Key, identifies the page context for text replacement.

The second column contains the default English text to translate into the target language. These values should not be modified.

The third column is labeled with the target language and should be edited to contain the desired translated values.

The fourth column,Notes, contains further information to aid the person carrying out a translation.

The translation spreadsheet files contain several worksheets, each containing translations for a specific section of EASA content. These worksheets are listed below:

• Web Menus - All of the EASA web page menus and sub menus.

• Web Content - All user mode web page content.

• EASA Client - All of the non-EASAP specific sections of the EASA Client in user mode. The menubar section is the most immediately visible to end users.

• Web Browser Client - All of the non-EASAP-specific sections of the Web Browser Client.

• Other - Covers the Graphing and Proxy Settings clients.

Within the text to be translated there may be special symbols: {n} and {\n}, where n is an integer. The majority of these special terms appear on the Web Content sheet.

An {n} by itself represents a placeholder where EASA will dynamically add, for example, this might be the title of the EASA application. The translated string should also contain the {n} symbol so that EASA knows where to insert the information.

An {n} followed later by a {\n} is used to mark a section of text, typically as a web page link. Again the translated string should also contain the {n} and {\n} tags so that EASA knows where to apply a link.

On importing the translation spreadsheet into EASA, if the above symbols in the translated text are missing, a warning will be given, and the error column in the translation table will be non-blank. On re-exporting the spreadsheet, highlighting identifies problematic rows in the notes column.

The second set of special characters are HTML tags, identified by text delimited by < > brackets. Preserve these tags during the translation process as they are for mark-up purposes.