TypeScript definition fix

Fixes a TypeScript issue where getTranslate() did not match the signature in LocalizeProps#translate

Support language names

You can now pass a language name when initializing languages (See Issue #30):

const languages = [
  { name: 'English', code: 'en' },
  { name: 'French', code: 'fr' },
  { name: 'Spanish', code: 'es' }
];
store.dispatch(initialize(languages));

Added support for HTML entities

• Now you can use HTML entities like   © etc.. in translation data

React 16 update plus minor updates

• updated dependencies and tests to ensure library will work with react v16
• add enhanced type definitions for single and multiple translation data
• update docs

new initialize options

Added two new initialize options:

• showMissingTranslationMsg: Controls whether missing translation message will be rendered when translation is undefined.
• missingTranslationCallback: A function that will be called when attempting to get an undefined translation. See Handle missing translations for details.

Custom translation data support

• Add support for custom translation data formats for user's that can't use the supported formats.

TypeScript Support

• add TypeScript definition file

flow support

• added flow typings support

v2.6.0

• add new initialize action creator
• add new options argument to translate function
• deprecate setLanguges action creator
• optimize customeEqualSelector
• update documentation

IE11 fix

• Fix issue where references to array.find were breaking in IE.