Once decisions have been made regarding design and functions to be used, the work on setting up the WebPAC for alternate language(s) can begin.

• If the library will use the example set, translate all HTML pages that are going to be used. Create new pages as needed, using appropriate naming conventions. Pay special attention to links. Make sure all command links have the correct language extension. Make sure links to specific HTML pages or graphic files are pointing to files with the correct language extension - and that those files actually exist.
• Create/edit the webpub_[lang].def file(s) to correspond with the webpub.def file.
• Create graphic files for all buttons and other images that are language dependent. Name them consistently for all languages.
  TIP: Sort files by Type in the live or staging directory in Web Master mode. Grouping all gifs together makes it easier to see if anything is missing or if the names don't match.

• Check Web Options
  • First of all, set the "startover" options so that navigation will work across all pages.
  • Check through the option groups and add versions with appropriate language extension for all options that must vary by language. Generally speaking, that should be any option that can contain a piece of text and/or refer to a file.
  • If the default language should be something other than English, set the ROOTLANG option
• Translate OPAC option Patron self-identification prompts & examples as desired.
  TIP: In order to add translations, log in with a login associated with the appropriate language, or change language from the main menu.

• Test thoroughly. Use all available indexes to search; look at displays; use buttons and other links; test optional functions; log in as a user and try out all functions offered.

To view the same page in English, simply remove the language code element and reload the page (hit <Enter> ). Alternatively, from an English page add the language element (*[lang]) and reload the page.

Some common problems and their solutions:

• The Home/Start Over button is displayed in the correct language, but it links to the English Opac menu (or other English page).
  • The behavior of this button is governed by Web Option STARTOVER. Most likely STARTOVER_[lang] is missing.
  • XSTARTOVER and PSTARTOVER work in the same way.
• The toplogo_[lang] file has a "Home" link that does not work. It links to the English home page.
  • This is probably related to the use of a command link, such as "/ " (mainmenu) or /search (opacmenu). The command link needs a language extension, e.g. /search*rus .
• A search in one or more of the indexes results in an English index browse or record display, even though it started at a page in the alternate language, e.g. /search*rus/d (srchhelp_d_rus.html).
  • Check the HTML in the file. The link for the Submit button is probably 'hand coded' and set incorrectly. Change it to link to the correct language.

  • TIP: on most pages token {submit} can be used. It will look at the language and link correctly. The linking will be correct even if the corresponding Web Option does not exist for the alternate language.

• A navigation button, e.g. Another Search, displays in English even though there is an anothersearch_[lang].gif file and the BUT_ANOTHER_[lang] option is set to use that file.
  • Firstly, BUT_ options cannot vary by language, so BUT_ANOTHER_[lang] is ignored.
  • Then, if the name of the file is not consistent with the English file name, the system will use the English file defined in BUT_ANOTHER.
  • For more detail, refer to the Naming conventions section of this tutorial.
• A form displays in English, although the navigation button or command link is set correctly for the alternate language.
  • Check if an optional page or form is used, e.g. srchmod.html (Limit/Sort form). If so, you also need a srchmod_[lang].html. Create it, or disable the English form, e.g by renaming it slightly. The system will then use its own default form instead, and translations will be provided by the general translation file.
  • Refer to Optional pages vs default forms in this tutorial for a description of how the system treats optional pages in reference to alternate languages.
• Toplogo_[lang].html exists and works fine except on certain pages, such as help_[lang].html, where the toplogo is in English.
  • This is likely related to the use of token {toplogo}. The token only works on pages that are system generated or called by command links. On all other pages the toplogo has to be coded directly on the page, because the system cannot interpret the language context.
• Some parts of a search result page are in English and it is difficult to figure out how to fix it.
  • This is probably caused by missing Web Options.
    Refer to the Innovative Guide & Reference, Page #106890: Navigating the WebPAC Browse Display and Page #106872: Search Results Options to help identify the options that are used and that need to vary by language.

• A user is searching the WebPAC in the alternate language but the record display is in English.
  • If all or some field labels are in English it means webpub_[lang].def is missing or incomplete.
  • If the record content is in English, this is correct - the language will be whatever the individual record was cataloged in and does not change.