mainmenu.html - English version
mainmenu_spi.html - Spanish version
mainmenu_cht.html - Traditional Chinese version

Optional pages can be used to replace system generated default forms, such as the patron verification form. Refer to the next page for a detailed discussion of optional pages.

Other HTML pages are created as needed, and can exist in one or more languages; i.e. the design of the WebPAC can to some extent differ between languages.

Normally you will have a set of pages in English with the appropriate [lang] extension to start with. The example set includes all standard pages but also many optional pages. If the library chooses to keep these pages rather than create their own, the content of the pages needs to be translated, and links also need to be adjusted so they point to pages in the correct language. Typically there are two types of links:

• Specific link to a named page, such as <a href=\"/screens/help_index.html\">Help</a>
  To link to the corresponding page in Italian you need to have a help_index_ita.html file and change the link to something like:
  <a href=\"/screens/help_index_ita.html\">Aiuto</a>

• Links using commands, such as /search .
  This link takes you to the opacmenu.html page. To have it point to the Italian version of the opacmenu (opacmenu_ita.html), you add an asterisk and the language code: /search*ita .
  Not all command links need the language extension. Some of them will work correctly anyway, because their use is not language specific, e.g. /clearhist which clears the Search History list.

Tokens themselves cannot be varied by language. The context decides which language they will use. They can only interpret language on standard ('mandatory') pages and system generated pages and forms. Therefore they will not work correctly for alternate languages on non-standard pages, even though the page in question may seem to support the token (most commonly <!--{toplogo}-->). You should always use actual coding on such pages.

For a complete list of customizable forms, refer to Innovative Guide & Reference, Page #106941: Customizable Web OPAC Forms.

For example the <!--{availlim}--> token is used to call a checkbox with text. The text is set with Web Option AVAILLIM that you need to define for the language you are working with. In some cases a token starts a chain reaction. The <!--{toplogo}--> token for example will look at Web Option TOPLOGO that in turn is usually pointing to a file. You need to define the Web Option for the language as well as have an appropriate version of the file it is calling to make it work correctly.

Some tokens will generate text messages from the server, for example the <!--{holds}--> token. The message text is provided by the general translation file.

Tokens themselves cannot be varied by language. The context decides which language they will use. They can only interprete language on standard ('mandatory') pages and system generated pages and forms. Therefore they will not work correctly for alternate languages on non-standard pages, even though the page in question may seem to support the token (most commonly <!--{toplogo}-->). You should always use actual coding on such pages.