You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Dan Klco (Jira)" <ji...@apache.org> on 2021/07/13 17:36:00 UTC

[jira] [Resolved] (SLING-8918) CMS - Consistently Implement i18n

     [ https://issues.apache.org/jira/browse/SLING-8918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Klco resolved SLING-8918.
-----------------------------
    Fix Version/s: App CMS 1.0.4
       Resolution: Fixed

Fixed in https://github.com/apache/sling-org-apache-sling-app-cms/commit/6067066952e2a2f9d4506d7c5e12a46ac7b0bda7

> CMS - Consistently Implement i18n
> ---------------------------------
>
>                 Key: SLING-8918
>                 URL: https://issues.apache.org/jira/browse/SLING-8918
>             Project: Sling
>          Issue Type: Improvement
>          Components: App CMS
>            Reporter: Dan Klco
>            Priority: Minor
>              Labels: backlog, newbie
>             Fix For: App CMS 1.0.4
>
>
> Currently, the Sling CMS has support for i18n and some of the screens support it, but most are not using i18n. Consistently implementing i18n would allow us to translate the application.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)