sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roland Dahlem (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-6983) i18n: "source" option not working
Date Mon, 26 Jun 2017 12:32:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063019#comment-16063019
] 

Roland Dahlem commented on SLING-6983:
--------------------------------------

I experience it with the bundle org.apache.sling.scripting.sightly in version 1.0.2

> i18n: "source" option not working
> ---------------------------------
>
>                 Key: SLING-6983
>                 URL: https://issues.apache.org/jira/browse/SLING-6983
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>            Reporter: Roland Dahlem
>              Labels: htl
>
> The [Adobe HTL Documentation|https://docs.adobe.com/docs/en/htl/docs/expression-language.html#Internationalization]
states that you can specify the source for the translation:
> {quote}
> The default source for the language is 'resource', meaning that the text gets translated
to the same language as the content. This can be changed to 'user', meaning that the language
is taken from the browser locale or from the locale of the logged-in user:
> {quote}
> {code}
> ${'Page' @ i18n, source='user'}
> {code}
> But using the {{source}} option seems to have no impact at all.
> Looking at  [I18nRuntimeExtension.java|https://github.com/apache/sling/blob/trunk/bundles/scripting/sightly/engine/src/main/java/org/apache/sling/scripting/sightly/impl/engine/extension/I18nRuntimeExtension.java]
there is no code addressing this feature (all other i18n options are addressed here)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message