now it's not possible to distinguish between a changeset that has no
comment and one whose comment is equivalent to the text of
'changeset.changeset.no_comment'.
* "OpenStreetMap" project name in <title> and <h1>
* Tooltips for the greeting bar for anonymous and logged in users
* Alternate text for the OSM logo
* Now using a CSS class for bolding inbox(N) instead of hard-coding font-weight: bold
* Separate tooltips for inbox(n) depending on whether it's 0, 1 or > 1
(e.g. w3m). And there's no reason to include plain URLs to CC-BY-SA
and OSM *AND* mention both in the message below without including any
links.
Instead erase those links and work them into the message instead.
The multiline 'notifier.gpx_notification.success.loaded_successfully'
message is how one should properly do multiline messages to be
embedded into E-Mail. It wraps at 80 columns (if translated correctly)
and isn't as inhererently limited as splitting the E-Mail into one
message per-line like the other notification messages do it.
I think the best thing to do here is to simply remove the RSS link, if
someone wants a RSS feed without a bbox they can click the Recent
Changes link and get a feed there.
of these pages have been translated into other languages and users
using other languages would want to visit those in preference to the
English version.
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.
The following pages now have a <title> that can be set in localizations:
* /user/USER_DOES_NOT_EXIST
* /user/USER_DOES_NOT_EXIST/diary
* /user/USER_DOES_NOT_EXIST/traces
* /message/*/ID_DOES_NOT_EXIST
In addition I've cleaned up the i18n message keys of all the
''no_such_user.rhtml'' pages involved. They now all use
title/heading/body for the <title>, <h2> and <p> respectively. And the
message key {{user}} instead of {{name}}.
that getting the database to do the filtering is much better as it
avoids us constructing thousands of user objects only to then throw
most of them away again.
