Translations can be added to i-net PDFC by using additional resources, such as those generated by the Translations Plugin, or by manually creating zip files with the structure given below. To enable plugin localizations, add the appropriate <plugin_name>.translation.zip file to the <persistence directory>/plugins/translation directory of the i-net PDFC server.

Localization resources are based on Java *_<language>.properties files which use the key=value coding format and the ISO-8859-1 code page. This means that special characters like umlauts must be properly encoded. The base language is English, which does not require the _<language> part of the filename.

All localized resources have to be stored in the correct location. The edit panel has section headlines with the package/name of the resource, e.g. com.inet.plugin.structure.i18n.ConfigStructure. That means that the ConfigStructure_<language>.properties resource has to be stored in the com/inet/plugin/structure/i18n directory of the <plugin_name>.translation.zip file. For example:

# myPlugin.localization.zip
 
 __ com
  |__ inet
    |__ plugin
    | |__ structure
    |   |__ i18n
    |     |_ ConfigStructure.properties
    |     |_ ConfigStructure_de.properties
    |     |_ ConfigStructure_es.properties
    |
    |__ client
      |__ resources
        |__ i18n
          |_ LanguageResource.properties
          |_ LanguageResource_de.properties
          |_ LanguageResource_es.properties

Due to several cache restrictions it may sometimes be difficult to force the browser to load the newly translated texts. However, the caches can be tricked into sending the new texts by giving the request a custom locale with an imaginary country code. Most server side caches have a timeout of about 15 minutes of inactivity before they will newly load the localized texts.

https://<server>:<port>/<path>?locale=es_AA
https://<server>:<port>/<path>?locale=es_AB
...
https://<server>:<port>/<path>?locale=es_ZZ