[
https://issues.apache.org/jira/browse/SLING-6983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063011#comment-16063011
]
Konrad Windszus edited comment on SLING-6983 at 6/26/17 12:40 PM:
------------------------------------------------------------------
[~Roland Dahlem] Can you please also tell with which version of the according
HTL bundle you experience this behaviour?
Also the HTL spec
(https://github.com/Adobe-Marketing-Cloud/htl-spec/blob/master/SPECIFICATION.md#123-i18n)
only mandates the options {{locale}} and {{hint}}. I would assume that
{{source}} is rather an AEM-specific extension, i.e. not part of what is
shipped with Sling.
was (Author: kwin):
[~Roland Dahlem] Can you please also tell with which version of the according
HTL bundle you experience this behaviour?
> 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)
