| Table of Contents | ||
|---|---|---|
|
...
The Identity Provider software contains by default US English messages.properties file(s) that contain the strings to render messages in the various views included in the software. In addition, the built-in attribute registry rules define names and descriptions of many standardized Attributes.
Many deployers may want to present these pages this information in the local language(s) or customize/localize some strings. To translate or adapt the IdP messages and thus support multiple languages, the IdP supports translations of the corresponding properties message files. The servlet container will then automatically select a matching properties message file based on the client's Accept-Languages header as provided by the web browser.
All of these messages are packaged into a single file, system/messages/messages.properties.
To e.g. The attribute metadata is, by contrast, directly embedded in the various default rule files we include.
Managing Translations
A Git repository, java-idp-translations, is the authoritative source of all of the internationalizable information for all our software products. We are willing to offer commit access to that repository to anybody willing to maintain translation(s) into any languages. Access is by public key and you can contact us at the usual places to express interest.
Within the repository, each software product is represented by a folder tree with a subdirectory for each major release version:
https://git.shibboleth.net/view/?p=java-idp-translations.git;a=tree
For example, the IdP is laid out thusly right now:
java-identity-provider/
5/
messages/
attributes/
Several plugins that contain translatable material are also represented with their own folders.
At the time of each release, we will incorporate any translation updates provided (copying the changed files into the actual software projects).
Notably, while message translations can generally be added to existing installs automatically during upgrades, as they’re internal, changes to attribute metadata require deployer action, as those files are created alongside the “existing” files.
Messages
For example, to create a German translation of the IdP's error messages strings, copy the default (US English) messages file, to a file named messages_de.properties (see also error messages configuration) and and translate/adapt the strings in the new properties file. For example, one would translate the string idp.title.suffix = Error to idp.title.suffix = Fehler
The IdP will select the correct a language file based on the locale of the browser without additional configuration. Note that Spring (and by extension the IdP) does not support a precedence of languages to fall back to, so the support for full i18n is constrained by that limitation.
In addition to the default use of the filenames noted above, you can freely change the message files used in conf/services.xml if you prefer that.
Translated Message Properties
These are the already completely translated versions of the messages.properties files available for download. All translations were provided by volunteers from the community. They are listed in the Translation Credits. See Contribute to the Translation Project below how you can contribute yourself.
General Installation Instructions
Download the languages your IdP should support
Copy them into the
shibboleth-idp/messagesdirectory. A software upgrade will not touch them, but you will have to manually fetch new versions as they become available.Best watch this page (login and click on "Watch") to get informed on changes.
You should also consider merging your own customization, such as idp.logo and idp.logo.alt-text.
Important: No deployer should use the text provided for example-tou-1.text as is. You need to replace that text with one that fits your local legal framework.
...
TBD: need to update with any translations provided
...
Language Code
...
Language
...
File Download
...
Last Update
...
cs
...
Czech
...
...
2020-02-13
...
de
...
German
...
...
2020-02-13
...
de_CH
...
German (Switzerland)
...
...
2020-02-13
...
es
...
Spanish
...
...
2018-10-25
...
es_ES
...
Spanish (Spain)
...
...
2018-11-01
...
fr
...
French
...
...
2021-05-26
...
it
...
Italian
...
...
2020-02-13
...
ja
...
Japanese
...
...
2020-02-12
...
nl
...
Dutch
...
...
2020-02-13
...
pl
...
Polish
...
...
2021-05-26
...
tr
...
Turkish
...
...
2021-05-26
...
zh_CN
...
Chinese, Simplified
...
...
2020-02-14
...
Several federation operators created a translation project on the free translation service Zanata. Translations are available in the Shibboleth IdPv3 Translation project (that now also covers IdPv4).
If you just want to download existing translations pick from the files listed above or ask your local federation operator.Also, note that if the browser does not specify a locale to use, the OS default will generally dictate what is selected, so this may or may not be the right answer.
Attributes
The names and descriptions for each default attribute transcoding rule are laid out as property sets in XML syntax in the various default rule files, which are found under the attributes folder in a given product’s tree. These can be extended/changed as required, though obviously this means avoiding stepping on others' translations.
Contributing to the Translation Effort
If you want to contribute translations for other languages, please:
Go to http://zanata.org/ and create an account
The send your account name to aai@switch.ch and ask to be added as contributor/maintainer for the Shibboleth translations.
That way you'll get access to the translation project.
...
Contact us via contact@shibboleth.net
Be prepared to provide a a Unix-style username and your SSH public key via some mechanism other than e-mail.
We will get you commit access to the translations repository.
Join the i18n list to be aware of impending release schedules or connect to other translators.
Thank you for your interest and help!