aboutsummaryrefslogtreecommitdiffstats
path: root/src/js/i18n.js
Commit message (Collapse)AuthorAgeFilesLines
* code reviewgorhill2015-03-091-1/+1
|
* code review: do not pollute global namespacegorhill2015-03-091-1/+1
|
* this fixes #313gorhill2015-03-091-0/+28
|
* Change extension descriptionDeathamns2015-03-071-1/+1
|
* use blank string if no translation foundgorhill2015-03-031-4/+1
|
* request log filtering: add i18n promptChris2015-03-031-0/+6
|
* Building extension filesDeathamns2014-11-091-3/+3
| | | | | | | | | | | | | | | | | | | | Adds possibility to build extension files (Chrome and Safari) from command line. To run from the project directory: python tools/build.py [meta] If the optional `meta` argument is set, then only the manifest and language files are uptated. Without that everything is being built (extension files too) into the `dist/build/version_number` folder. For Chrome there will be two files, a crx, and a .zip file which includes the key.pem private key (so this must not be shared, it's just a bit help for publishing it to the Chrome Web Store). Beside the extension files, update-files are generated too (for self hosting - Safari needs it).
* Add .jshintrc, and use the "use strict" directiveDeathamns2014-11-091-0/+5
| | | | | | | | | .jshintrc's otion-set is a personal choice, merely a suggestion. Beside that, it includes some common globals for specific browsers, so there's no need to set the globals in every .js file. In order to force strict coding, "use strict" directive was added into every .js file.
* Work on vendor API abstraction, and near complete Safari supportDeathamns2014-11-091-0/+40