You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For l10n and i18n there needs to be a way to access translation strings from properties files.
The bundled expression language provides a function called "text" to access resource bundles. You can say ${text('title')} to get the text labeled title. However this only works with the bundled EL but not with other alternatives like MVEL or Spring EL.
The ExpressionLanguage implementations should be able to provide custom ways to access resource bundles and there should be support in the template engine parser to access to resource bundles without too much typing.
New syntax could be:
<div>@{title}</div><div>@{hello, user}</div>
a file like messages.properties would look like:
title=This is the title
hell=Hello {0}
The text was updated successfully, but these errors were encountered:
For l10n and i18n there needs to be a way to access translation strings from properties files.
The bundled expression language provides a function called "text" to access resource bundles. You can say ${text('title')} to get the text labeled title. However this only works with the bundled EL but not with other alternatives like MVEL or Spring EL.
The ExpressionLanguage implementations should be able to provide custom ways to access resource bundles and there should be support in the template engine parser to access to resource bundles without too much typing.
New syntax could be:
a file like messages.properties would look like:
The text was updated successfully, but these errors were encountered: