translate and i18n (server-side widget)

AngularFaces automatically translates most texts of a JSF application to foreign languages, provided the language file exists.
However, there are some texts that can't be translated by AngularFaces automatically. AngularFaces can only translate
texts that are attributes of a JSF components. Every other text - in particular, texts that are simply written
in the JSF page - needs to be surrounded by a <translate /> tag. Alternatively, you can use the <i18n /> tag (which is merely
a synonym of <translate /> tag).

<translate /> isn't a regular JSF component. The AngularTagDecorator converts it
to a regular JSF h:outputText tag. Therefore only texts are allowed between <translate> and </translate>.
Images, input field and other JSF elements are not allowed.

Example

Language files

translate and i18n (server-side widget)

AngularFaces automatically translates most texts of a JSF application to foreign languages, provided the language file exists.
However, there are some texts that can't be translated by AngularFaces automatically. AngularFaces can only translate
texts that are attributes of a JSF components. Every other text - in particular, texts that are simply written
in the JSF page - needs to be surrounded by a <translate /> tag. Alternatively, you can use the <i18n /> tag (which is merely
a synonym of <translate /> tag).

<translate /> isn't a regular JSF component. The AngularTagDecorator converts it
to a regular JSF h:outputText tag. Therefore only texts are allowed between <translate> and </translate>.
Images, input field and other JSF elements are not allowed.

Language files

translate and i18n (server-side widget)

AngularFaces automatically translates most texts of a JSF application to foreign languages, provided the language file exists.
However, there are some texts that can't be translated by AngularFaces automatically. AngularFaces can only translate
texts that are attributes of a JSF components. Every other text - in particular, texts that are simply written
in the JSF page - needs to be surrounded by a <translate /> tag. Alternatively, you can use the <i18n /> tag (which is merely
a synonym of <translate /> tag).

<translate /> isn't a regular JSF component. The AngularTagDecorator converts it
to a regular JSF h:outputText tag. Therefore only texts are allowed between <translate> and </translate>.
Images, input field and other JSF elements are not allowed.

Language files

translate and i18n (server-side widget)

AngularFaces automatically translates most texts of a JSF application to foreign languages, provided the language file exists.
However, there are some texts that can't be translated by AngularFaces automatically. AngularFaces can only translate
texts that are attributes of a JSF components. Every other text - in particular, texts that are simply written
in the JSF page - needs to be surrounded by a <translate /> tag. Alternatively, you can use the <i18n /> tag (which is merely
a synonym of <translate /> tag).

<translate /> isn't a regular JSF component. The AngularTagDecorator converts it
to a regular JSF h:outputText tag. Therefore only texts are allowed between <translate> and </translate>.
Images, input field and other JSF elements are not allowed.