You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Shingo Omura (JIRA)" <ji...@apache.org> on 2014/04/08 08:42:14 UTC

[jira] [Updated] (MESOS-1198) Toward Supporting i18n website

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

Shingo Omura updated MESOS-1198:
--------------------------------

    Attachment: toward-supporting-i18n-website-r1584219.patch

This patch performs
* version up middleman to 3.3.0
* change config.rb so that i18n is active
* reconstruct source folder (localizable folder is introduced).
* chnage Rakefile so that 'update_docs', 'build' works properly.
* delete unnecesary files.

> Toward Supporting i18n website
> ------------------------------
>
>                 Key: MESOS-1198
>                 URL: https://issues.apache.org/jira/browse/MESOS-1198
>             Project: Mesos
>          Issue Type: Documentation
>          Components: project website
>            Reporter: Shingo Omura
>            Priority: Minor
>         Attachments: toward-supporting-i18n-website-r1584219.patch
>
>
> In this [thread of mesos-user|http://mail-archives.apache.org/mod_mbox/mesos-user/201310.mbox/%3CCA+40=G2bUO_bZ81FNf8MsJ=T4ZqL64Pq0wHqVYK64UpQXgK9rg@mail.gmail.com%3E] mailing list, some volunteers who are interested in translation of mesos documents are showed up.
> Mesos website's CMS has already been switched to middleman (MESOS-829).  And, fortunately, Middleman supports nice  [i18n function|http://middlemanapp.com/advanced/localization/].
> This ticket is opened to support i18n for mesos website.  It can be inefficient to put translations of large blocks of text into the locale YAML files.  So, I think we better to use "Localizing Entire Templates" way.
> * Step1. version up middleman to 3.3.0.
>   * due to [this bug|https://github.com/middleman/middleman/pull/1057], current middleman 3.2.0 doesn't work properly.
> * Step2. modify config.rb
>   * support i18n. and update proxy pages setting.
> * Step3. reconstruct source folder
>   * introduce 'localizable' folder in 'source' directory
>     * all localizable file are put in the folder.
>   * mv documentation files to the folder.
>   * rename files "foo.html.md" to "foo.en.html.md" followed by middleman document.
> * Step4. update Rakefile so that 'update_docs' and 'build' task works properly.
>   * change copy logic so that the logic meets with above filename rules.



--
This message was sent by Atlassian JIRA
(v6.2#6252)