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-i18nprocessor

v0.0.2

Published

Grunt i18n processor

Downloads

1

Readme

grunt-i18nprocessor

Grunt i18n processor

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-i18nprocessor --save-dev

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

grunt.loadNpmTasks('grunt-i18nprocessor');

The "i18nprocessor" task

Overview

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

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

The task is designed to take a JSON i18n Langauge file and split it into separate language specific files

{
    "validateFail_number": {
        "en": "Numeric value required",
        "de": "Numerischer Wert erforderlich",
        "fr": "Valeur num�rique obligatoire",
        "nl": "Numerieke waarde verplicht",
        "fi": "T�yt� numeerinen arvo"
    },
    "validateFail_email": {
        "en": "Valid email address required",
        "de": "G�ltige E-Mail-Adresse erforderlich.",
        "fr": "Adresse mail valide obligatoire",
        "nl": "Geldig e-mailadres verplicht",
        "fi": "Lis�� toimiva s�hk�postiosoite"
    }
}

will produce separate files for each language..

eg. lang.en.js...

{
 "copyrightNotice":"My Company (c) Copyright 2006-2015 All Rights Reserved.",
 "strings":{
        "validateFail_number":"Numeric value required",
        "validateFail_email":"Valid email address required"
    }
}

Options

options.languages

Type: Array Default value: ["en"]

A array of base language codes. A new language file will get created for each of these languages

options.pretty

Type: Boolean Default value: false

If true the output JSON is tab separated and readable.

options.copyright

Type: String Default value: ``

The copyright string to add into the output json

options.filenameMask

Type: String Default value: ux4.%1.js

The filename mask for the output files. %1 gets replaced with the language code

options.outputEnglishIfNoTranslation

Type: Boolean Default value: true

Output the english string if the string doesn't have a translation for the current language

Usage Examples

Default Options

In this example, the default options are used to do something with whatever. So if the testing file has the content Testing and the 123 file had the content 1 2 3, the generated result would be Testing, 1 2 3.

grunt.initConfig({
  i18nprocessor: {
    options: {
        languages: ['en','de'],
        pretty: false,
        copyright: "MyCompany (c) 2015"
    },
    ux4: {
        'src': 'myappi18nfile.json',
        'dest': '/i18n/'
    },
  },
});

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

(Nothing yet)