We need to install the endDrag routine as the "done" handler after
creating the control otherwise the control will overwrite our handler
with one of it's own.
Use a preinitializer to load the settings from application.yml so
that they are available as early as possible. All settings can also
be overridden using environment variables.
The ad-hoc settins in environment.rb are then moved to this new
system so we have one consistent location for settings.
feature use the name key corresponding to the user's
locale. E.g. "name:is" for Icelandic.
This will fall back on "name". The interface will be equivalent unless
the user has selected another language than English in the preferences
and objects with localized name:* tags corresponding to the user's
language are being displayed.
These messages now don't use JavaScript string concatenation but
variable interpolation:
* browse.start_rjs.history_for_feature
* browse.start_rjs.edited_by_user_at_timestamp
* browse.start_rjs.object_list.selected.type.node
* browse.start_rjs.object_list.selected.type.way
* browse.start_rjs.object_list.history.type.node
* browse.start_rjs.object_list.history.type.way
These previously extant messages have been deleted, merged, and given
more descriptive names:
* browse.start_rjs.history_for
* browse.start_rjs.edited_by
* browse.start_rjs.at_timestamp
translation strings from Ruby, doing the string replacement lient-side
instead of on the server.
This partially solves ticket:1919. I still have to move the rest of
the JS functions over to the new system.
* Object list, API, Display object list, Details
Also make node/way/relation translatable, and in different contexts
too (e.g. Icelandic needs this).
This introduces more stuff that needs to be fixed in ticket 1919.
