[
https://issues.apache.org/jira/browse/ISIS-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325671#comment-14325671
]
ASF subversion and git services commented on ISIS-903:
------------------------------------------------------
Commit 21390d260fff7d88b240ef31d5c0b5ab4a32fbf5 in isis's branch
refs/heads/ISIS-903 from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=21390d2 ]
ISIS-903: simplifying design...
... get rid of the ServicesInstallerFallback hack, now register
TranslationServicePo as a regular @DomainService. Also remove the
LocaleProviderDefault. Use the absence of a TranslationResolver and/or
LocaleProviderDefault as a hint to put the TranslationService into write mode
> Improve i18n support (in NamedFacetDecorator etc) to honour client-side
> locale.
> -------------------------------------------------------------------------------
>
> Key: ISIS-903
> URL: https://issues.apache.org/jira/browse/ISIS-903
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: core-1.6.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: core-1.9.0
>
>
> from the mailing list: http://markmail.org/message/wifsrte2p2q6tces
> ok, here's the scoop.
> It *is* possible to add i18n for Isis apps, but the implementation we have
> reflects the locale of the server, rather than the client.
> If client-side i18n is what you require then it ought to be possible to
> implement a different implementation of I18nFacetDecoratorInstaller. You can
> get hold of the user's locale using:
> AuthenticatedWebSessionForIsis.get().getLocale()
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
