Content

Page tree



Introduction

Language File Container

Language file container may consist of a list of language file URLs each one representing a different language. The following language file container are currently supported:

  1. Phone User Interface language file container (<gui-languages> tag)
  2. Web User Interface language file container (<web-languages> tag)


<gui-languages> tag

Syntax
<?xml version="1.0" encoding="utf-8" ?>
 <gui-languages>
  <language url="<Phone User Interface Language file URL(1)>" name="<language_name(1)>" />
  ...
  <language url="<Phone User Interface Language file URL(n)>" name="<language_name(n)>" />
 </gui-languages>

  • language url string contains phone user interface language file URLs (1)..(n)
  • name string determines the language's name in the phone user interface language list.

 



<web-languages> tag

Syntax
<?xml version="1.0" encoding="utf-8" ?>
 <web-languages>
  <language url="<Web User Interface Language file URL(1)>" name="<language_name(1)>" />
  ...
  <language url="<Web User Interface Language file URL(n)>" name="<language_name(n)>" />
 </web-languages>

Important notice

Language URL should point out to file with correct prefix "gui_lang_" for GUI interface and "web_lang_" for WEB interface.
File should end with ".xml" suffix.

Examples:
<gui-languages>
  <language url="http://192.168.0.110/gui_lang_Custom_GUI.xml" name="Custom_GUI" />
 </gui-languages>

<web-languages>
  <language url="http://192.168.0.110/web_lang_Custom_WEB.xml" name="Custom_WEB" />
 </web-languages>

 


Language files

Language files contain the language phrases. When selecting a new language from the phone or web user interface language list the content of the associated file will be stored in the phone´s RAM. The following language files are currently supported:

  1. Phone User Interface language files (<phrases> tag)
  2. WUI - Web User Interface language files (<w_phrases> tag)

Language files depend on the firmware version, i.e. each file is unique per firmware version. However the language files of the latest release are always backwards compatible.

 


<phrases> tag

Syntax
<?xml version="1.0" encoding="utf-8"?>
 <phrases>
  <phrase i="<index>" n="<name>" t="<translation>"/>
  ...
  <phrase i="<index>" n="<name>" t="<translation>"/>
  <language i="<index>" t="<language name>"/>
 </phrases>
  • phrase tag defines one Phone User Interface phrase
    • i string represents the running <index> of the phrases
    • n string represents the internally used (english) variable <name> used for the translation
    • t string represents the <translation>
  • language tag defines the language name
    • i string represents the <index> of the language name, usually equal 0
    • t string represents the <language name>, should match the name string used in (<gui-languages> tag)

 


<w_phrases> tag

Syntax
<?xml version="1.0" encoding="utf-8"?>
 <w_phrases>
  <w_phrase i="<index>" n="<name>" t="<translation>"/>
  ...
  <w_phrase i="<index>" n="<name>" t="<translation>"/>
  <language i="<index>" t="<language name>"/>
 </w_phrases>

  • w_phrase tag defines one WUI - Web User Interface phrase
    • i string represents the running <index> of the phrases
    • n string represents the internally used (english) variable <name> used for the translation
    • t string represents the translation
  • language tag defines the language name
    • i string represents the index of the language name, usually equal 0
    • t string represents the <language name>, should match the name string used in (<web-languages> tag)