From d23b1cccec34c46d695a9f2b5758061f779afae4 Mon Sep 17 00:00:00 2001 From: Jochen Topf Date: Mon, 13 Dec 2010 22:57:21 +0100 Subject: more new style javascript and translations --- web/i18n/en.yml | 53 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 53 insertions(+) (limited to 'web/i18n/en.yml') diff --git a/web/i18n/en.yml b/web/i18n/en.yml index 882f750..3ca3177 100644 --- a/web/i18n/en.yml +++ b/web/i18n/en.yml @@ -114,14 +114,67 @@ sources: reports: characters_in_keys: name: Characters in Keys + intro: | +

Any valid Unicode character can appear in an OSM key but usually only lower + case latin letters (a-z) and the underscore (_) are used. Sometimes the colon + (:) is added as a separator character.

+ statistics: + tab: Statistics + title: Statistics Overview + characters_in_keys: + plain: Only latin lowercase letters (a to z) and underscore (_), first and last characters are letters. + colon: Like A but with one or more colons (:) inside. + letters: Like B but with uppercase latin letters or letters from other alphabets. + space: Like C but contains at least one whitespace character (space, tab, new line, carriage return, or from other alphabets). + problem: Like C but contains possibly problematic characters =+/&<>;'"?%#@\,. + rest: Everything else. + whitespace: + tab: Whitespace + title: Keys With Whitespace + intro: | +

Keys that contain whitespace characters such as space, tab, new + line, carriage return, or whitespace characters from other + alphabets.
+ Whitespace in keys can be confusing, especially at the + beginning or end of the key, because they are invisible. Generally + the underscore (_) should be used instead.

+ problematic: + tab: Problematic + title: Keys With Possibly Problematic Characters + intro: | +

Keys that contain possibly problematic characters: =+/&<>;'"?%#@\,. These characters + can be problematic, because they are used to quote strings in + different programming languages or have special meanings in XML, HTML, + URLs, and other places. The equal sign is used often as separator + between tag keys and values.
+ Keys that appear in this list are not necessarily wrong though. But + in many cases they are just results of some error.

frequently_used_keys_without_wiki_page: name: Frequently Used Keys Without Wiki Page key_lengths: name: Key Lengths language_comparison_table_for_keys_in_the_wiki: name: Language Comparison Table for Keys in the Wiki + icons: + template: Page in wiki available and contains standard template. + error: Page in wiki available and contains standard template, but couldn't be parsed. + page: Page in wiki available but doesn't contain standard template. + redirect: Page is a redirect. + intro: | +

This table shows all tag keys for which there are wiki pages available and in what languages they are.

languages: name: Languages + intro: | +

OpenStreetMap is an international project. Tags and their descriptions can + be in any language. This table lists the languages Taginfo knows about and how + many wiki pages there are in these languages documenting keys and tags, + respectively.

wiki_pages_about_non_existing_keys: name: Wiki Pages About Non-Existing Keys + intro: | +

This table shows keys for which a wiki page exists but there is not a single + instance in the database. This is not necessarily an error (maybe somebody + added the documentation in the wiki as preparation for using a key or the wiki + page documents a now obsolete key), but it can also be a typo or other error.

-- cgit v1.2.3