The general rules for naming files must be followed. To furthermore let the system know a HTML page should be used for a certain language, append the three letter language code to the file name, preceded by an underscore. The code must be in lowercase:
mainmenu_tur.html - the Main Menu page in Turkish.
Graphic files are customized by language in the same way as HTML files, by adding the three letter language code to the file name:
startover.gif - English Start Over button
startover_por.gif - Portuguese version of the button
If the graphic file is going to be used with a BUT_ Web Option, it is of extreme importance that the whole file name is consistent for all languages, and that the file is in GIF format. That is because BUT_ options cannot vary by language. Instead the variation is done by naming the corresponding gif files consistently:
mystartagain.gif - name of English Start Over button
mystartagain_spi.gif - name of corresponding Spanish button
The only Web Option you need is:
BUT_STARTOVER= /screens/mystartagain.gif
NOTE: the .gif extension has to be included in the value of the Web Option, otherwise results may be unexpected.
For further details, refer to Innovative Guide & Reference, Page #106916 Graphic Buttons.
When a user is running the WebPAC in Spanish the server will look for a file named mystartagain_spi.gif. If there is no such file it will use the mystartagain.gif instead.
For Web Options that can vary by language, append the language code to the option name in the same manner as for files:
STARTOVER - English version
STARTOVER_ITA - Italian version
The language code can usually be either upper or lower case.
To vary a command link by language, append an asterisk and the language code:
/search - link to English OPAC Menu, opacmenu.html
/search*por - link to Portuguese OPAC Menu, opacmenu_por.html
|