stefanyohansson / sz-i18n Goto Github PK

today we have this usage below, but user needs to provide all arguments every time and sometimes this is a annoying task. I think lib can load from a config file [too].

Usage:
    sz-i18n export <source> -o <dest> -t <langs>
    sz-i18n import <source> -b <base> -o <dest> [-t <langs>]
    sz-i18n generate
    sz-i18n -h | --help | --version

https://github.com/alexei/sprintf.js

This api seems to be really useful when working with template engines like mustache, underscore template...

Example:

var ts = i18n.translate_object('LANG', { 'x' : value_x, 'y': value_y });
-> {
'x': 'translated_value_x',
'y': 'translated_value_y',
}

var tmpl = _.template(...);
tmpl.render(ts);

Generate a source map file with:
file+line: string

We'll generate a source map in extractor this way we can export translator strings for each source file.

• Extract from code to normalized json
• Extract from normalized json to simple json or PO, MO

Make a sz-i18n command for extract i18n strings from source code.

sz-i18n extract <source_folder> <dest_folder> -t <langs>

example:

sz-i18n extract src/ lang/ -t 'en-US,pt-BR'

We need to run in CommonJS enviroments too.

It's nice to add source lang example just by running:

sz-cli generate en-US [--empty]

My proposal to use pure JS instead of coffee script.