normalize keys so scope works when sending translations individually
Merge 'master' into include_scope_in_key
Merge pull request #108 from joaomilho/master

Submit default when an array containing a string is supplied
[test] failing rspec test demonstrating the issue #109
Fix Updater bug if a namespace matches a deleted key, fix issue #109
Merge branch 'include_scope_in_key' of https://github.com/substantial/localeapp
Add a test for normalizing the scope attribute before posting a
translation
Merge pull request #110 from maximerety/fix_109

The Updater should not delete a namespace having the same name as a previously deleted key
Safely create synchronization data file
update CHANGELOG
Handle I18n::Backend::Fallbacks

The problem was that by the time `default` was called "for real" it gets called without the `object` parameter. It gets called once with `options[:fallback] = true` and a valid `object`, so, without the patch, the code fails:

```
  1) I18n::Backend::Base#default records missing translations when fallbacks are enabled
     Failure/Error: i18n.translate('en', 'object', :default => 'subject')
       #<Localeapp::MissingTranslations:0x007f8403ae9190> received :add with unexpected arguments
         expected: ("en", "object", "subject", {:default=>"subject"})
              got: ("en", nil, nil, {:default=>"subject"})
     # ./lib/localeapp/default_value_handler.rb:9:in `default'
     # ./spec/localeapp/default_value_handler_spec.rb:74:in `block (3 levels) in <top (required)>'
     # ./spec/localeapp/default_value_handler_spec.rb:72:in `block (2 levels) in <top (required)>'
```

Obviously `nil` is not the value that was intended.

These are the calls to default:

```ruby
i18n.translate(:en, 'my.object', :default => 'my default')

call to default(locale, object, subject, options)
:en
"my.object"
[]
{:default=>[], :fallback=>true}

call to default(locale, object, subject, options)
"en"
nil
"my default"
{:default=>"my default"}
```

As you can see, by the time the subject is the default, the object is nil.
Allow for strings for locale
Merge branch 'handle_i18n_fallbacks' of https://github.com/substantial/localeapp
Patch I18n::Backend::Fallbacks for key remembering

This will work across different versions of i18n
Use more aggressive approach that should work...

Fixes 1.8 I hope
Merge pull request #47 from substantial/handle_i18n_fallbacks

default sender should handle I18n::Backend::Fallbacks
Update the changelog
Bump version to 0.6.11
Use mkdir_p so app can start if log dir already exists

The way it was, if the log dir existed but localeapp.yml did not, the app would blow up:

```
Errno::EEXIST: File exists - /home/deploy/buildAgent/work/8823f7f94dd0e3f9/log
```
Merge pull request #112 from aaronjensen/patch-1

Use mkdir_p so app can start if log dir already exists