Für diese Seite gibt es noch keine deutsche Übersetzung. Bitte lesen Sie solange die englische Version. Wir bitten Sie um Verständnis.

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

The language files <translate /> uses are explained here.

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

The language files <translate /> uses are explained here.

A página ainda não foi traduzido para o Português. Por favor, leia a tradução em Inglês. Pedimos desculpas por qualquer inconveniente.

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

The language files <translate /> uses are explained here.

Für diese Seite gibt es noch keine deutsche Übersetzung. Bitte lesen Sie solange die englische Version. Wir bitten Sie um Verständnis.

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

The language files <translate /> uses are explained here.