• We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      It would be nice to be able to have the Confluence frontend in muliple labguages (e.g. have multiple .properties files) and let the user choose a language in their profile.

            [CONFSERVER-1315] Internationalization

            Our company also needs to translate documents in different languages, thus it would really be an advantage if Confluence has the ability to translate documents to other languages.

            Y van den Berg added a comment - Our company also needs to translate documents in different languages, thus it would really be an advantage if Confluence has the ability to translate documents to other languages.

            To correct my comment above, the document on creating language pack plugins is located at:

            http://confluence.atlassian.com/display/DOC/Language+Pack+Plugins

            Jeremy Higgs added a comment - To correct my comment above, the document on creating language pack plugins is located at: http://confluence.atlassian.com/display/DOC/Language+Pack+Plugins

            We are desperately waitiing for that feature. When do you plan to roll out version 2.2?

            Thanks!

            Andreas

            Andreas Deimer added a comment - We are desperately waitiing for that feature. When do you plan to roll out version 2.2? Thanks! Andreas

            Just an update on Jeremy's comments, whilst Confluence 2.2 will support localisation, there would not be any language packs included on its release.

            Ernest Wong (Inactive) added a comment - Just an update on Jeremy's comments, whilst Confluence 2.2 will support localisation, there would not be any language packs included on its release.

            Hi guys,

            You'll be pleased to know that this has been implemented for the 2.2 release. We currently have three translations (German, Russian and Japanese). I have created a document on creating language pack plugins at http://confluence.atlassian.com/display/DOC/Language+Pack+Flags

            Jeremy

            Jeremy Higgs added a comment - Hi guys, You'll be pleased to know that this has been implemented for the 2.2 release. We currently have three translations (German, Russian and Japanese). I have created a document on creating language pack plugins at http://confluence.atlassian.com/display/DOC/Language+Pack+Flags Jeremy

            in minimum give us a possibility to add .properties files with own text parts, make it dependent to the locale of the browser and add a language select field to the profile and to the usernavbar

            Stefan Baader added a comment - in minimum give us a possibility to add .properties files with own text parts, make it dependent to the locale of the browser and add a language select field to the profile and to the usernavbar

            For use, it is although indispensable

            Matthieu Lainné added a comment - For use, it is although indispensable

            Actually I can't understand why is it so hard to solve, as soon as in JIRA it is implemented quite well.

            Mikhail Kolesnik added a comment - Actually I can't understand why is it so hard to solve, as soon as in JIRA it is implemented quite well.

            SD added a comment -

            Also note that BIDI langauges such as Hebrew and Arabic have additional requirements:

            • Velocity templates must be made RTL (right-to-left)
            • Breadcrumb ">" should be changed to "<"
            • Fixed positions within the page should be avoided
            • ...

            -R.

            SD added a comment - Also note that BIDI langauges such as Hebrew and Arabic have additional requirements: Velocity templates must be made RTL (right-to-left) Breadcrumb ">" should be changed to "<" Fixed positions within the page should be avoided ... -R.

            Internationalization should also provide internationalization of created pages, attachments and Velocity templates.
            In our organization, we must communicate to other teams located in different countries and we need to write every pages, documents and templates in two languages.
            It means that you should associate a language property to the pages, the attachments and the templates.
            You should also manage a default language that is used wether the requested page is not available in the current language.

            Richard THIBAULT added a comment - Internationalization should also provide internationalization of created pages, attachments and Velocity templates. In our organization, we must communicate to other teams located in different countries and we need to write every pages, documents and templates in two languages. It means that you should associate a language property to the pages, the attachments and the templates. You should also manage a default language that is used wether the requested page is not available in the current language.

              Unassigned Unassigned
              ae2e024659a5 Michael Trezzi
              Votes:
              22 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: