delocalize value provided in options as long as it is not a String

[Advisa]

It seems that if a String is specified then that value should not be delocalized, but if a number, date or time object is provided it makes more sense to delocalize it.

[fmluizao]

Makes sense... I think the behavior is more consistent, acording to the rails API.

What do you think @clemens?

[pederbl]

What are your thoughts on this? This is a critical fix for me. I would love to get back on your official version instead of using my own.

[clemens]

Oh, I had totally forgotten about this one, sorry.

Conceptionally, this looks good. Could you please also add tests for values that are dates/times/datetimes and also a test that verifies that it doesn't modify strings?

After that, I think we're good to merge.

[clemens]

Is this still relevant? If so, could you open another pull request based on the current master and provide the tests I've asked for? Thanks!

[clemens]

I've included your proposed changes in the current master and spike branch. The only change was that I've kept the options[:value].blank? guard so with a blank string it would still fall back to delocalizing the model's own value.

Thanks for contributing. :)