jmdobry / angular-i18n-properties

Internationalization (i18n) for Angular.js using the common Java .properties resource bundle file format.

angular-i18n-properties (0.4.0-alpha)

Not for production use (yet)

Internationalization (i18n) for Angular.js using the common Java .properties resource bundle file format.

The goal of the project is to solve a general problem, not satisfy a specific scenario.

Quick Introduction

View the Demo

// put quick intro demo code here

Table of Contents

1. Demo
2. Features
3. Status
4. Download
5. Install
6. Usage
7. Roadmap
8. Changelog
9. Contributing
10. License

Features

put list of features here

Status

Version	Branch	Build status	Test Coverage
0.4.0-alpha	master		Test Coverage
0.4.0-alpha	develop
0.4.0-alpha	all

Download

Latest Stable Version

| Type | File | Size | | ------------- | ----------------- | ------------------- | ---- | | Production | angular-i18n-properties-0.4.0-alpha.min.js | 3.86 KB | | Development | angular-i18n-properties-0.4.0-alpha.js | 13 KB |

Installation

Install with bower

bower install angular-i18n-properties

Include src/angular-i18n-properties.js on your web page after you include angular.js.

Manual install

Get angular-i18n-properties from the Download section and include it on your web page after angular.js.

Usage

• Load angular-i18n-properties
• API Documentation

Load angular-i18n-properties

Make sure angular-i18n-properties is included on your web page after angular.js.

angular.module('myApp', ['jmdobry.angular-i18n-properties']);

See angular-i18n-properties

API Documentation

Roadmap

0.6.0-alpha

• Unit tests complete.

0.8.0-beta

• Demo and documentation complete

1.0.0

• Stable 1.0.0 Release

Changelog

0.4.0-alpha - 06 September 2013

• Wrote file parser. #1
• Wrote file loader. #2
• Wrote i18n filter. #3

Contributing

Submitting Issues

1. Make sure you aren't submitting a duplicate issue.
2. Carefully describe how to reproduce the problem.
3. Expect prompt feedback.

Submitting Pull Requests

Basic Idea

• Checkout a new branch based on develop and name it to what you intend to do:
  • Example:

    $ git checkout -b BRANCH_NAME
    

  • Use one branch per fix/feature
  • Prefix your branch name with feature- or fix- appropriately.
• Make your changes
  • Make sure to provide a spec for unit tests
  • Run your tests with either karma start or grunt test
  • Make sure the tests pass
• Commit your changes
  • Please provide a git message which explains what you've done
  • Commit to the forked repository
• Make a pull request
  • Make sure you send the PR to the develop branch
  • Travis CI is watching you!

More details

Read the detailed Contributing Guide

License

MIT License

Copyright (C) 2013 Jason Dobry

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.