Introduction
  Installing
  Handling
  Virtual servers
  Modules
  Filesystems
  RXML tags
  Graphics
  Proxy
  Miscellaneous modules
  Security considerations
  Scripting
  Databases
  LDAP
  SiteBuilder
  Access Control
  IntraSeek
    Directories
    Configuring
    Creating new profile
    Indexing
    Languages
    Logs
    Advanced profile
    Technical document
  LogView
  FrontPage
  Upgrading
  Third party extensions
  Portability
  Reporting bugs
  Appendix
 
Languages

The IntraSeek output in search forms and summaries can be translated into several languages. It should be noted that IntraSeek does not translate the search result summaries but only the static IntraSeek output information like buttons, summary status, etc. See the IntraSeek tags pages how to use the language support.

The languages in the table below are supported by default in IntraSeek.
Country   Code   Country   Code  
Danish   da   English   en  
Finnish   fi   French   fr  
German   de   Hungarian   hu  
Italian   it   Lithuanian   lt  
Norwegian   no   Portuguese   pt  
Romanian   ro   Slovenian   sl  
Spanish   es   Swedish   se  

Character sets
IntraSeek has additional support for five charsets, of which iso-8859-1 is the default one.

iso-8859-1 (Latin 1)
Covers Albanian, Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish, and Swedish.

iso-8859-2 (Latin 2)
Covers Czech, German, Hungarian, Polish, Romanian, Slovak, Sorbian, Slovenian, Serbian, Croatian.

iso-8859-3 (Latin 3)
Covers Esperanto, Galician, Maltese, and Turkish.

iso-8859-4 (Latin 4)
Covers Estonian, Latvian, and Lithuanian.

iso-8859-9 (Latin 5)
Covers the Same as Latin 1, except that Turkish is covered instead of Icelandic.

It is important for the IntraSeek crawler to know which character set a document is using for the purpose of being able to supply the users browser with a proper query response. One problem is the lowercase representation of words. If for example the user is searching for FOO or FoO he should still get the same results, so to make a correct lowercase representation of international characters the crawler has to know which character set to use.

To make sure that documents are delivered with the correct content type several methods can be used. The <meta> tag proposed by Netscape is one means but we recommend using the RXML tag <header> as it adds the content type information to the HTTP header, making it less browser dependent than the <meta> tag. The <header> tag should be placed within the <head> container. Remember that when writing the name of the charset it should always be stated in lowercased letters.