npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

grunt-glotpress

v0.2.2

Published

Gets translations from a GlotPress installation

Downloads

33

Readme

grunt-glotpress

Gets translations from a GlotPress installation

Getting Started

This plugin requires Grunt ~0.4.5

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-glotpress --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-glotpress');

The "glotpress_download" task

Overview

In your project's Gruntfile, add a section named glotpress_download to the data object passed into grunt.initConfig().

grunt.initConfig({
  glotpress_download: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
});

Options

options.domainPath

Type: String Default value: languages

The folder where all downloaded files will be stored

options.url

Type: String Default value: false

The url of the GlotPress installation (required).

options.slug

Type: String Default value: false

The slug is the path in the GlotPress installation which can also be main-folder/sub-folder (required).

options.textdomain

Type: String Default value: false

The textdomain that is used for WordPress. This is needed for the files. If not set, it will fallback to the slug.

options.file_format

Type: String Default value: %domainPath%/%textdomain%-%wp_locale%.%format%

The structure how the file is being stored. Is based on previous settings but you could create your own format. For now only those four values and short locale can be used. You could however save the files in different folders if you move a placeholder.

options.formats

Type: Array Default value: ['po','mo']

The file formats that will be downloaded for each translation set.

options.filter

Type: object Default value: {translation_sets: false, minimum_percentage: 30, waiting_strings: false}

You can filter which files you want to have. By default it only checks the minimum percentage translation sets need to be translated. The other parameters still need to be implemented.

Usage Examples

Default Options

In this example, the default options are used to download all translations sets from a project.

grunt.initConfig({
  glotpress_download: {
    core: {
      options: {
        domainPath: 'languages',
        url: 'http://wp-translate.org',
        slug: 'tabify-edit-screen',
        textdomain: 'tabify-edit-screen',
      }
    },
  },
});

Default Options

In this example, we add our own file format like for a theme. By default the format is set for plugins which do include the textdomain.

grunt.initConfig({
  glotpress_download: {
    core: {
      options: {
        domainPath: 'languages',
        url: 'http://wp-translate.org',
        slug: 'cool-theme',
        textdomain: 'cool-theme',
        file_format: '%domainPath%/%wp_locale%.%format%',
      }
    },
  },
});

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

  • 0.2.2 - Add CWD support.
  • 0.2.1 - Fix broken download of translation files.
  • 0.2.0 - Complete rewrite of the codebase. Add ability to include waiting strings. Fallback to locale if wp_locale doesn't exists. Fixes encoding issue where downloadeded files didn't work. Further coding style fixes.
  • 0.1.1 - Fix dependency and downloading issues.
  • 0.1.0 - Initial Release.