Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

1171: Ensure translatable strings in blocks can actually be translated #1173

Merged
merged 5 commits into from
May 29, 2018
Merged

1171: Ensure translatable strings in blocks can actually be translated #1173

merged 5 commits into from
May 29, 2018

Commits on May 24, 2018

  1. Ensure JS strings can be translated.

    @miina
    miina committed May 24, 2018
    Configuration menu
    Copy the full SHA
    437bf32 View commit details
    Browse the repository at this point in the history

  2. Fix translation file name.

    @miina
    miina committed May 24, 2018
    Configuration menu
    Copy the full SHA
    c967dee View commit details
    Browse the repository at this point in the history

  3. Add separate locale for blocks.

    @miina
    miina committed May 24, 2018
    1 Configuration menu
    Copy the full SHA
    8ac7759 View commit details
    Browse the repository at this point in the history

Commits on May 25, 2018

  1. Create .php translation file from JS translations.

    @miina
    miina committed May 25, 2018
    Configuration menu
    Copy the full SHA
    5275055 View commit details
    Browse the repository at this point in the history

Commits on May 29, 2018

  1. Make sure translations are included in release builds 

    * Avoid running translation logic when creating normal builds.
* Add Grunt task for invoking Webpack.
* Add build-release command for creating a ZIP with translations.
    @westonruter
    westonruter committed May 29, 2018
    Configuration menu
    Copy the full SHA
    cc636ce View commit details
    Browse the repository at this point in the history