Alternate Languages Introduction and Prerequisites Basic SetupPrint this Page
Basic setup
The first step in the process is to enable your system to recognize the language(s) you have purchased. This is done by Innovative and will automatically activate the ability to translate labels and code values and to create files with the appropriate [lang] extension. Innovative will inform you of the code that is used as extension for each language, spi =Spanish, ara =Arabic.

The code is always three letters, but is not always the same as the international standard language code.

When your system is installed it comes with a standard set of files:

  • A file with translations of system generated messages and texts. This file contains translations of e.g. error messages ("Sorry, the information you submitted was not valid") and texts that appear on default forms ("Please type in your comment").

    Updated files are offered on a regular basis and can be downloaded using option Admin - Install Latest Translations in Millennium Administration. Missing translations can be requested via a Service Commitment on CSDirect. In this tutorial the file is referred to as the 'general translation file'.

  • Generic HTML files and graphics with the appropriate [lang] extension. Normally they are duplicates of corresponding English files and act as placeholders to guide you and ensure that your WebPAC is functional for testing while you work on translation and customization.

  • For some languages a set of Web Options for the alternate language(s) may also be offered at installation.

In addition to this you may be asked to provide translations of:

  • Field labels
  • Index labels
  • Options for limiting
  • Other information that is kept in separate files, unique to each library. This will vary depending on your setup and the products you have purchased.

If a library staff member has taken the ASAA workshop (Advanced System Access and Administration) the library can maintain some of these files from Millennium Administration.

Values from some fixed fields are displayed in the WebPAC and you need to ensure that all code descriptions have proper translations. Some typical examples: item information normally includes Location and Status, and Material Type from the bibliographic record is usually one of the limiting options.