New Component: Localized

i18n is boring. Adding labels, and then in every properties file define a value for each supported language. To reduce the effort here, especially for one-time-shot big paragraph translations, we created an inlineTranslation component. Example usage:

<pe:inlineTranslation>
    <pe:translation language="en">
        To register yourself via eID, you simply need to login.
    </pe:translation>
    <pe:translation language="nl">
        Om jezelf via eID te registreren, dien je je simpelweg eens aan te melden.
    </pe:translation>
    <pe:translation language="fr">
        Pour vous inscrire via eID, il vous suffit de vous connecter.
    </pe:translation>
</pe:inlineTranslation>

Here inlineTranslation will render the content of the translation child that comes closest to the UIViewRoot locale, i.e., nl-be will select the nl one. If no match is found, inlineTranslation simply takes the first one.

If there is interest in such component as part of primefaces-extensions, please make some noise here.

[jepsar]

It’s not JSF, it’s the way the showcase is built. If no locale is provided to the component, indeed the view locale is used. Normally one would have something like this in a multi language application:

<f:view locale="#{user.locale}">

[jepsar]

I personally prefer LocalizedContent or just Localized or Localization.

From those three I like Localized the most.