# ----- COMMENTS BELOW THIS WILL BE DESTROYED -----

# Please see README in this same directory for notes on syntax and general
# guidelines on how to translate text.
__ignore__: junk

# Do not translate these!
de_DE: Deutsch
el_GR: Ελληνικά
en_US: English
es_ES: Español
fr_FR: Français
pl_PL: Polski
pt_BR: Português
ru_RU: Русский

################################################################################
#
#  Overview of File
#
#  Translations are presented roughly in order of decreasing importance,
#  starting with things that are seen on every page, progressing through
#  commonly-used to rarely-used pages, to emails, error messages, and finally
#  administrative and debugging messages. Sections:
#
#    COMMON WORDS AND PHRASES
#    ENUMERATED SETS OF VALUES
#    APPLICATION LAYOUT
#    MOST POPULAR PAGES
#    LESS POPULAR PAGES
#    ADMIN-TYPE PAGES
#    EMAIL MESSAGES
#    INTRO PAGE
#    HOW TO HELP PAGE
#    HOW TO USE PAGE (COMMON TASKS)
#    HOW TO USE PAGE (GLOSSARY)
#    LOCATION HELP PAGE
#    ERROR MESSAGES
#    DEBUGGING STUFF
#
################################################################################

# COMMON WORDS AND PHRASES

# Object titles, all nouns.
COMMENT: Commentaire
comment: commentaire
COMMENTS: Commentaires
comments: commentaires
DESCRIPTION: Description
description: description
DESCRIPTIONS: Descriptions
descriptions: descriptions
DRAFT: Brouillon
draft: brouillon
DRAFTS: Brouillons
drafts: brouillons
IMAGE: Image
image: image
IMAGES: Images
images: images
LICENSE: Licence
license: licence
LICENSES: Licences
licenses: licences
LOCATION: Endroit
location: endroit
LOCATIONS: Endroits
locations: endroits
LOCATION_DESCRIPTION: Description d'endroit
location_description: description d'endroit
LOCATION_DESCRIPTIONS: Descriptions d'endroit
location_descriptions: descriptions d'endroit
LOG: Log
log: log
LOGS: Logs
logs: logs
MAP: Carte
map: carte
MAPS: Cartes
maps: cartes
NAME: Nom
name: nom
NAMES: Noms
names: noms
NAME_DESCRIPTION: Description de nom
name_description: description de nom
NAME_DESCRIPTIONS: Descriptions de nom
name_descriptions: descriptions de nom
NAMING: Nom Proposé
naming: nom proposé
NAMINGS: Noms Proposés
namings: noms proposés
NOTIFICATION: Notification
notification: notification
NOTIFICATIONS: Notifications
notifications: notifications
OBSERVATION: Observation
observation: observation
OBSERVATIONS: Observations
observations: observations
PAST_LOCATION: Changement d'endroit
past_location: changement d'endroit
PAST_LOCATIONS: Changements d'endroit
past_locations: changements d'endroit
PAST_NAME: Changement de nom
past_name: changement de nom
PAST_NAMES: Changements de nom
past_names: changements de nom
PROJECT: Projet
project: projet
PROJECTS: Projets
projects: projets
RSS_LOG: Journal d'activité
rss_log: journals d'activité
RSS_LOGS: Journal d'activité
rss_logs: journals d'activité
SOURCE: Source
source: source
SOURCES: Sources
sources: sources
SPECIES_LIST: Liste d'observations
species_list: liste d'observations
SPECIES_LISTS: Listes d'observations
species_lists: listes d'observations
USER: Utilisateur
user: utilisateur
USERS: Utilisateurs
users: utilisateurs
USER_GROUP: Groupe d'utilisateurs
user_group: groupe d'utilisateurs
USER_GROUPS: Groupes d'utilisateurs
user_groups: groupes d'utilisateurs
VOTE: Vote
vote: vote
VOTES: Votes
votes: votes

# Other common nouns:
ACCOUNT: Compte
account: compte
ACCOUNTS: Comptes
accounts: comptes
ADMIN: Admin
admin: admin
ADMINS: Admins
admins: admins
ADMIN_GROUP: Groupe d'administrateurs
admin_group: groupe d'administrateurs
ADMIN_GROUPS: Groupes d'administrateurs
admin_groups: groupes d'administrateurs
# ("Author" is person who wrote a book or description.)
AUTHOR: Auteur
author: auteur
AUTHORS: Auteurs
authors: auteurs
# ("Authority" is authority on a scientific name.)
AUTHORITY: Auteur
authority: auteur
AUTHORITYS: Auteurs
authoritys: auteurs
CHANGE: Changement
change: changement
CHANGES: Changements
changes: changements
CITATION: Citation
citation: citation
CITATIONS: Citations
citations: citations
CONFIDENCE_LEVEL: Niveau de confiance
confidence_level: niveau de confiance
CONFIDENCE_LEVELS: Niveaux de confiance
confidence_levels: niveaux de confiance
COPYRIGHT_HOLDER: Titulaire du droit d'auteur
copyright_holder: Titulaire du droit d'auteur
COPYRIGHT_HOLDERS: Titulaires du droit d'auteur
copyright_holders: Titulaires du droit d'auteur
CORRECT_SPELLING: Orthographe correcte
correct_spelling: orthographe correcte
CORRECT_SPELLINGS: Orthographes correctes
correct_spellings: orthographes correctes
DATE: Date
date: date
DATES: Dates
dates: dates
EDITOR: Rédacteur
editor: rédacteur
EDITORS: Rédacteurs
editors: rédacteurs
EMAIL: E-mail
email: e-mail
EMAILS: E-mails
emails: e-mails
EMAIL_ADDRESS: Adresse électronique
email_address: adresse électronique
EMAIL_ADDRESSS: Adresses électronique
email_addresss: adresses électronique
FULL_NAME: Nom complet
full_name: nom complets
FULL_NAMES: Noms complet
full_names: noms complets
IDENTIFIER: Indentificateur
identifier: indentificateur
IDENTIFIERS: Indentificateurs
identifiers: indentificateurs
INDEX: Index
index: index
INDEXES: Indices
indexes: indices
LATITUDE: Latitude
latitude: latitude
LATITUDES: Latitudes
latitudes: latitudes
LOGIN_NAME: Nom d'utilisateur
login_name: nom d'utilisateur
LOGIN_NAMES: Noms d'utilisateur
login_names: noms d'utilisateur
LONGITUDE: Longitude
longitude: longitude
LONGITUDES: Longitudes
longitudes: longitudes
MEMBER: Membre
member: membre
MEMBERS: Membres
members: membres
MESSAGE: Message
message: message
MESSAGES: Messages
messages: messages
NOTE: Note
note: note
NOTES: Notes
notes: notes
OBSERVER: Observateur
observer: observateur
OBSERVERS: Observateurs
observers: observateurs
OWNER: Propriétaire
owner: propriétaire
OWNERS: Propriétaires
owners: propriétaires
PASSWORD: Mot de passe
password: mot de passe
PASSWORDS: Mots de passe
passwords: mots de passe
# (Only used by validation errors, I think.)
PASSWORD_CONFIRMATION: Confirmation de mot de passe
password_confirmation: confirmation de mot de passe
PASSWORD_CONFIRMATIONS: Confirmations de mot de passe
password_confirmations: confirmations de mot de passe
PREFERENCES: Préférences
preferences: préférences
PREFERRED_NAME: Nom préféré
preferred_name: nom préféré
PREFERRED_NAMES: Noms préférés
preferred_names: noms préférés
PROFILE: Profil
profile: profil
PROFILES: Profils
profiles: profils
QUALITY: Qualité
quality: qualité
RANK: Rang
rank: rang
RANKS: Rangs
ranks: rangs
REVIEWER: Évaluateur
reviewer: évaluateur
REVIEWERS: Évaluateurs
reviewers: évaluateurs
SIZE: Taille
size: taille
STATUS: État
status: état
STATUSS: États
statuss: états
SUBJECT: Sujet
subject: sujet
SUBJECTS: Sujets
subjects: sujets
SUMMARY: Résumé
summary: résumé
SUMMARYS: Résumés
summarys: résumés
# ("Tag" refers to a keyword, will be used to tag names and images.)
TAG: Tag
tag: tag
TAGS: Tags
tags: tags
TIME: Temps
time: temps
TIMES: Temps
times: Temps
TITLE: Titre
title: titre
TITLES: Titres
titles: titres
VERSION: Version
version: version
VERSIONS: Versions
versions: versions

# Common nouns/adjectives used as labels, never pluralized:
ALL: Tous
all: tous
NONE: Rien
none: rien
HIGH: Haute
high: haute
LOW: Basse
low: basse
LESS: Moins
less: moins
MORE: Plus
more: plus
PREV: Précédent
prev: précédent
NEXT: Suivant
next: suivant
BACK: Dernier
back: dernier
FORWARD: Prochain
forward: prochain
EAST: Est
east: est
NORTH: Nord
north: nord
SOUTH: Sud
south: sud
WEST: Ouest
west: ouest

# Labels for fields answering: "What did you observe?", "When did you observe
# it?", "Where did you observe it?", and "Who observed it?".
WHAT: Quelle
what: quelle
WHEN: Quand
when: quand
WHERE: Où
where: où
WHO: Qui
who: qui

# Common verbs/actions used as button labels:
ADD: Ajouter
add: ajouter
APPROVE: Approuver
approve: approuver
CANCEL: Annuler
cancel: annuler
CLOSE: Fermer
close: fermer
CREATE: Créer
create: créer
DEPRECATE: Déprécier
deprecate: déprécier
DESTROY: Détruire
destroy: détruire
DISABLE: Désactiver
disable: désactiver
EDIT: Modifier
edit: modifier
ENABLE: Activer
enable: activer
MERGE: Fusionner
merge: fusionner
OKAY: Bien
okay: bien
REMOVE: Supprimer
remove: supprimer
SAVE: Enregistrer
save: enregistrer
SAVE_CHANGES: Enregistrer les modifications
save_changes: enregistrer les modifications
SAVE_EDITS: Enregistrer les modifications
save_edits: enregistrer les modifications
SEARCH: Rechercher
search: rechercher
SEND: Envoyer
send: envoyer
SUBMIT: Envoyer
submit: envoyer
UPDATE: Mise à jour
update: mise à jour
UPLOAD: Télécharger
upload: télécharger

# Common adjectives.
BY: Par
by: par
CREATED: Créé
created: cree
DESTROYED: Détruite
destroyed: détruite
MODIFIED: Mise à jour
modified: mise à jour
OPTIONAL: En option
optional: en option
REQUIRED: Nécessaire
required: nécessaire
WATCHING: Regardé
watching: regardé
IGNORING: Ignoré
ignoring: ignoré
TRACKING: Suivi
tracking: suivi
VIEWED: Vu
viewed: vu

# Common adjectives describing species names. (Note: "approved" seems to be
# interchangable with "accepted" in our site -- both indicate that the
# scientific community accepts this name as correct.  "Reviewed" on the
# other hand indicates that a user in the "reviewers" group has looked at
# an object and didn't see any obvious mistakes.)
APPROVED: Approuvé
approved: approuvé
ACCEPTED: Correcte
accepted: Correcte
DEPRECATED: Obsolète
deprecated: obsolète
MISSPELLED: Mal orthographié
misspelled: mal orthographié
NOT_MISSPELLED: Correctement orthographié
not_misspelled: correctement orthographié
REVIEWED: Évalué
reviewed: évalué
UNKNOWN: Inconnue
unknown: inconnue

# Permissions: restricted means access is restricted but the current user has
# access; private means the current user does not have access; default means
# this is the default description that shows up on the show_name/location page
# (synonyms that might work better are "principle" or "main" or "official").
PRIVATE: Privé
private: privé
PUBLIC: Publique
public: publique
RESTRICTED: Restreint
restricted: restreint
DEFAULT: Par défaut
default: par défaut

# Common verbs/actions with objects:
add_object: Ajouter [type]
add_objects: Ajouter les [types]
all_objects: Tous/Toutes les [types]
cancel_and_show: Annuler (afficher [type])
create_object: Créer [type]
destroy_object: Détruire [type]
edit_object: Modifier [type]
list_objects: Énumérer les [types]
remove_object: Supprimer [type]
remove_objects: Supprimer les [types]
show_all: Afficher tous
show_name: A propos de [name]
show_object: Afficher [type]
show_objects: Afficher les [types]
sort_by_object: Trier par [type]

# Other generic phrases.
and_num_more: et plus [num]
are_you_sure: Etes-vous sûr?
click_for_map: Cliquez pour voir la carte
google_images: Google images
many_times: "[num] fois"
one_time: un fois
permission_denied: Autorisation refusée.
"YES": "Oui"
"NO": "Non"
"yes": "oui"
"no": "non"

################################################################################

# ENUMERATED SETS OF VALUES

# Units.
units_meters: mètres

# Quality values.
image_vote_long_0: Sans opinion.
image_vote_long_1: **Pas mal**, mais pas très utile.
image_vote_long_2: **Utile** pour l'identification.
image_vote_long_3: **Bon**, convient pour un guide.
image_vote_long_4: **Super!** Au-delà des travaux de mortels.

image_vote_help_0: Sans opinion.
image_vote_help_1: Pas mal, mais pas très utile.
image_vote_help_2: Utile pour l'identification.
image_vote_help_3: Bon, convient pour un guide.
image_vote_help_4: Super! Au-delà des travaux de mortels.

image_vote_short_0: Pas noté
image_vote_short_1: Pas mal
image_vote_short_2: Utile
image_vote_short_3: Bon
image_vote_short_4: Super

# Review statuses. (Note: "unvetted" means it's been looked at but the reviewer
# doesn't feel comfortable declaring it "accurate"; thus "unvetted" means
# "reviewed" and "vetted" means "approved".  Sorry, we inherited these odd
# terms from EOL; they weren't my choice!)
review_unreviewed: Pas évalué
review_unvetted: Évalué
review_vetted: Approuvé
review_inaccurate: Inexactes / incomplète
review_no_export: Non pour l'exportation
review_ok_for_export: Okay pour l'exportation

# Naming reasons.
naming_reason_label_1: Reconnu par la vue.
naming_reason_label_2: Utilisant des références.
naming_reason_label_3: Basé sur des caractéristiques microscopiques.
naming_reason_label_4: Basé sur des caractéristiques chimiques.

# Description types, note full_title combines the titles below with the title
# of the object the description is describing, e.g. "User's [:description] of
# Agaricus campestris" or "Draft for EOL Initiative by login of Amanita lanei".

# These are used as page title and in index results: must include both the type
# of description and the title of the object ([object]) they're describing.
description_full_title_public: "Description publique de: [object]"
description_full_title_foreign: "Description de [text] de: [object]"
description_full_title_project: "Brouillon pour [text] par [user] de: [object]"
description_full_title_source: "Description de [text] de: [object]"
description_full_title_user: "Description de [user] de: [object]"

# These are used when listing the available descriptions in the show_name page.
description_part_title_public: "Description publique"
description_part_title_user: "Description de [user]"

# Same thing, but this time the optional text field was filled in.  Note that
# the text field is not optional for half of the source types.
description_part_title_public_with_text: "[TEXT]"
description_part_title_foreign_with_text: "Description de [text]"
description_part_title_project_with_text: "Brouillon pour [text] (par [user])"
description_part_title_source_with_text: "Description de [text]"
description_part_title_user_with_text: "[TEXT] (par [USER])"

# Footers: "Created: [date]", "By: [user]", "Obs Created: 2008-11-03", etc.
footer_created_at: "*Créé:* [date]"
footer_created_by: "*Créé:* [date] *par* [user]"
footer_modified_at: "*Mise à jour:* [date]"
footer_modified_by: "*Mise à jour:* [date] *par* [user]"
footer_last_modified_at: "*Dernier changement:* [date]"
footer_last_modified_by: "*Dernier changement:* [date] *par* [user]"
footer_viewed: "*Vu:* [times], *dernier vu:* [date]"
footer_version_out_of: "*Version:* [num] *de* [total]"

# Taxonomic ranks.
RANK_CLASS: Classe
rank_class: classe
RANK_FAMILY: Famille
rank_family: famille
RANK_FORM: Forme
rank_form: forme
RANK_GENUS: Genre
rank_genus: genre
RANK_GROUP: Groupe
rank_group: groupe
RANK_DOMAIN: Domaine
rank_domain: domaine
RANK_KINGDOM: Règne
rank_kingdom: règne
RANK_ORDER: Ordre
rank_order: ordre
RANK_PHYLUM: Division
rank_phylum: division
RANK_SPECIES: Espèce
rank_species: espèce
RANK_SUBSPECIES: Sous-espèce
rank_subspecies: sous-espèce
RANK_VARIETY: Variété
rank_variety: variété
RANK_PLURAL_CLASS: Classes
rank_plural_class: classes
RANK_PLURAL_FAMILY: Familles
rank_plural_family: familles
RANK_PLURAL_FORM: Formes
rank_plural_form: formes
RANK_PLURAL_GENUS: Genres
rank_plural_genus: genres
RANK_PLURAL_GROUP: Groupes
rank_plural_group: groupes
RANK_PLURAL_KINGDOM: Règnes
rank_plural_kingdom: règnes
RANK_PLURAL_ORDER: Ordres
rank_plural_order: ordres
RANK_PLURAL_PHYLUM: Divisions
rank_plural_phylum: divisions
RANK_PLURAL_SPECIES: Espèces
rank_plural_species: espèces
RANK_PLURAL_SUBSPECIES: Sous-espèces
rank_plural_subspecies: Sous-espèces
RANK_PLURAL_VARIETY: Variétés
rank_plural_variety: variétés

# user statistics field names
user_stats_comments: "[:COMMENTS]"
user_stats_images: "[:IMAGES]"
user_stats_location_descriptions_authors: Descriptions d'endroit créées
user_stats_location_descriptions_editors: Descriptions d'endroit modifiées
user_stats_locations: Endroits creés
user_stats_locations_versions: Endroits modifiés
user_stats_name_descriptions_authors: Descriptions de nom créées
user_stats_name_descriptions_editors: Descriptions de nom modifiées
user_stats_names: Noms créés
user_stats_names_versions: Noms
user_stats_namings: Noms proposés
user_stats_observations: "[:OBSERVATIONS]"
user_stats_species_list_entries: Entrées de [:species_list]
user_stats_species_lists: "[:SPECIES_LISTS]"
user_stats_votes: "[:VOTES]"

# site statistics field names
site_stats_comments: "[:COMMENTS]"
site_stats_images: "[:IMAGES]"
site_stats_listed_taxa: Taxons figurants
site_stats_location_descriptions_authors: Descriptions d'endroit
site_stats_location_descriptions_editors: ""
site_stats_locations: Endroits définis
site_stats_locations_versions: ""
site_stats_name_descriptions_authors: Descriptions de nom
site_stats_name_descriptions_editors: ""
site_stats_names: ""
site_stats_names_versions: ""
site_stats_namings: Noms proposés
site_stats_observations: "[:OBSERVATIONS]"
site_stats_observed_taxa: Taxons
site_stats_species_list_entries: Entrées de [:species_list]
site_stats_species_lists: "[:SPECIES_LISTS]"
site_stats_users: Membres
site_stats_votes: "[:VOTES]"

# vote descriptions
vote_no_opinion: Sans opinion
vote_confidence_100: Je dirais que
vote_confidence_80: Prometteur
vote_confidence_60: Peut-être
vote_confidence_40: Douteux
vote_confidence_20: Peu probable
vote_confidence_0: Comme si!
vote_agreement_100: Je dirais que
vote_agreement_80: Prometteur
vote_agreement_60: Peut-être
vote_agreement_40: Douteux
vote_agreement_20: Peu probable
vote_agreement_0: Comme si!

# Query titles. Notes on [args]:
#
# [type] is type of object being indexed / searched for (singular)
# [types], [Type] and [Types] are the same thing but capitalized and/or plural
# [order] is sort order (singular), e.g., "Name" or "Date"
# [name], [location], [where], [pattern], etc. are un-translatable strings
#
query_title_advanced_search: "[:app_advanced_search]"
query_title_all: Index des [types]
query_title_all_by: "[TYPES] par [order]"
query_title_at_location: "[TYPES] à: [location]"
query_title_at_where: "[TYPES] à: '[user_where]'"
query_title_by_author: "[TYPES] écrites par [user]"
query_title_by_editor: "[TYPES] modifiées par [user]"
query_title_by_rss_log: "[TYPES] dans le journal d'activité"
query_title_by_user: "[TYPES] créé(e)s par [user]"
query_title_for_object: "[TYPES] sur [object]"
query_title_for_user: "[TYPES] pour [user]"
query_title_in_set: "[TYPES] choisi(e)s"
query_title_in_species_list: "[TYPES] dans: [species_list]"
query_title_inside_observation: "[TYPES] de: [observation]"
query_title_of_children: "[TYPES] de taxons inférieurs de: [name]"
query_title_of_name: "[TYPES] de: [name]"
query_title_of_name_synonym: "[TYPES] de synonymes de: [name]"
query_title_of_name_nonconsensus: "[TYPES] qui pourraient être: [name]"
query_title_of_parents: "Taxons supérieurs contenant: [name]"
query_title_pattern_search: "[TYPES] correspondant: '[pattern]'"
query_title_with_descriptions: "[TYPES] avec des [:descriptions]"
query_title_with_descriptions_by_author: "[TYPES] avec des descriptions écrites par [user]"
query_title_with_descriptions_by_editor: "[TYPES] avec des descriptions modifiées par [user]"
query_title_with_descriptions_by_user: "[TYPES] avec des descriptions créées par [user]"
query_title_with_descriptions_in_set: "[TYPES] avec des [descriptions]"
query_title_with_observations: "[TYPES] avec des observations"
query_title_with_observations_at_location: "[TYPES] avec des observations à: [location]"
query_title_with_observations_at_where: "[TYPES] avec des observations à: '[user_where]'"
query_title_with_observations_by_user: "[TYPES] avec des observations créées par [user]"
query_title_with_observations_in_set: "[TYPES] avec des observations"
query_title_with_observations_in_species_list: "[TYPES] avec des observations dans: [species_list]"
query_title_with_observations_of_children: "[TYPES] avec des observations de taxons inférieurs de: [name]"
query_title_with_observations_of_name: "[TYPES] avec des observations de: [name]"
query_title_with_observations_of_name_synonym: "[TYPES] avec des observations de synonymes de: [name]"
query_title_with_observations_of_name_nonconsensus: "[TYPES] avec des observations qui pourraient être: [name]"

# Brief description of each query flavor.
query_help_comment_all: tous les commentaires
query_help_comment_by_user: les commentaires créées par un utilisateur particulier
query_help_comment_in_set: les commentaires dans une ensemble particulière
query_help_comment_for_object: les commentaires sur un objet particulier
query_help_comment_for_user: les commentaires envoyés à un utilisateur particulier
query_help_comment_pattern_search: les commentaires correspondant à une chaîne de recherche
query_help_image_advanced_search: les images d'observations correspondant à des critères de recherche avancée
query_help_image_all: toutes les images
query_help_image_by_user: les images créées par un utilisateur particulier
query_help_image_in_set: les images dans une ensemble particulière
query_help_image_inside_observation: les images appartenant à une requête d'observation externe
query_help_image_pattern_search: les images correspondant à une chaîne de recherche
query_help_image_with_observations: iles mages appartenant à des observations
query_help_image_with_observations_at_location: les images appartenant à des observations à un endroit défini
query_help_image_with_observations_at_where: les images appartenant à des observations à un endroit indéfini
query_help_image_with_observations_by_user: les images appartenant à des observations d'un utilisateur particulier
query_help_image_with_observations_in_set: les images appartenant à des observations dans une ensemble particulière
query_help_image_with_observations_in_species_list: les images appartenant à des observations dans une liste particulière
query_help_image_with_observations_of_children: les images appartenant à des observations d'enfants d'un nom particulier
query_help_image_with_observations_of_name: les images appartenant à des observations d'un nom particulier
query_help_location_advanced_search: les endroits des observations correspondant à des critères de recherche avancée
query_help_location_all: tous les endroits
query_help_location_by_user: les endroits créés par un utilisateur particulier
query_help_location_by_editor: les endroits modifiés par un utilisateur particulier
query_help_location_by_rss_log: les endroits avec activité récent
query_help_location_in_set: les endroits dans une ensemble particulière
query_help_location_pattern_search: les endroits correspondant à une chaîne de recherche
query_help_location_with_descriptions: les endroits avec des descriptions
query_help_location_with_descriptions_by_author: les endroits avec des descriptions écrites par un utilisateur particulier
query_help_location_with_descriptions_by_editor: les endroits avec des descriptions modifiées par un utilisateur particulier
query_help_location_with_descriptions_by_user: les endroits avec des descriptions créées par un utilisateur particulier
query_help_location_with_descriptions_in_set: les endroits avec des descriptions dans une ensemble particulière
query_help_location_with_observations: les endroits appartenant à des observations
query_help_location_with_observations_by_user: les endroits appartenant à des observations d'un utilisateur particulier
query_help_location_with_observations_in_set: les endroits appartenant à des observations dans une ensemble particulière
query_help_location_with_observations_in_species_list: les endroits appartenant à des observations dans une liste particulière
query_help_location_with_observations_of_children: les endroits appartenant à des observations d'enfants d'un nom particulier
query_help_location_with_observations_of_name: les endroits appartenant à des observations d'un nom particulier
query_help_location_description_all: toutes les descriptions d'endroit
query_help_location_description_by_author: les descriptions d'endroit écrites par un utilisateur particulier
query_help_location_description_by_editor: les descriptions d'endroit modifiées par un utilisateur particulier
query_help_location_description_by_user: les descriptions d'endroit créées par un utilisateur particulier
query_help_location_description_in_set: les descriptions d'endroit dans une ensemble particulière
query_help_name_advanced_search: les noms avec observations correspondant à des critères de recherche avancée
query_help_name_all: tous les noms
query_help_name_by_user: les noms créés par un utilisateur particulier
query_help_name_by_editor: les noms modifiéés par un utilisateur particulier
query_help_name_by_rss_log: les noms avec activité récent
query_help_name_in_set: les noms dans une ensemble particulière
query_help_name_of_children: les enfants d'un nom particulier
query_help_name_of_parents: les parents d'un nom particulier
query_help_name_pattern_search: les noms correspondant à une chaîne de recherche
query_help_name_with_descriptions: les noms avec des descriptions
query_help_name_with_descriptions_by_author: les noms avec des descriptions écrites par un utilisateur particulier
query_help_name_with_descriptions_by_editor: les noms avec des descriptions modifiées par un utilisateur particulier
query_help_name_with_descriptions_by_user: les noms avec des descriptions créées par un utilisateur particulier
query_help_name_with_descriptions_in_set: les noms avec des descriptions dans une ensemble particulière
query_help_name_with_observations: les noms avec des observations
query_help_name_with_observations_at_location: les noms avec des observations à un endroit défini
query_help_name_with_observations_at_where: les noms avec des observations à un endroit indéfini
query_help_name_with_observations_by_user: les noms avec des observations d'un utilisateur particulier
query_help_name_with_observations_in_set: les noms avec des observations dans une ensemble particulière
query_help_name_with_observations_in_species_list: les noms avec des observations dans une liste particulière
query_help_name_description_all: toutes les descriptions de nom
query_help_name_description_by_author: les descriptions de nom écrites par un utilisateur particulier
query_help_name_description_by_editor: les descriptions de nom modifiées par un utilisateur particulier
query_help_name_description_by_user: les descriptions de nom créées par un utilisateur particulier
query_help_name_description_in_set: les descriptions de nom dans une ensemble particulière
query_help_observation_advanced_search: les observations correspondant à des critères de recherche avancée
query_help_observation_all: toutes les observations
query_help_observation_at_location: les observations à un endroit défini
query_help_observation_at_where: les observations à un endroit indéfini
query_help_observation_by_rss_log: les observations avec activité récent
query_help_observation_by_user: les observations créées par un utilisateur particulier
query_help_observation_in_set: les observations dans une ensemble particulière
query_help_observation_in_species_list: les observations dans une liste particulière
query_help_observation_of_children: les observations d'enfants d'un nom particulier
query_help_observation_of_name: les observations d'un nom particulier
query_help_observation_pattern_search: les observations correspondant à une chaîne de recherche
query_help_project_all: tous les projets
query_help_project_by_rss_log: les projets avec activité récent
query_help_project_in_set: les projets dans une ensemble particulière
query_help_project_pattern_search: les projets correspondant à une chaîne de recherche
query_help_rss_log_all: Log d'activité récent
query_help_rss_log_in_set: Log d'activité récent dans une ensemble particulière
query_help_species_list_all: toutes les listes d'observation
query_help_species_list_at_location: les listes d'observation à un endroit défini
query_help_species_list_at_where: les listes d'observation à un endroit indéfini
query_help_species_list_by_rss_log: les listes d'observation avec activité récent
query_help_species_list_by_user: les listes d'observation par un utilisateur particulier
query_help_species_list_in_set: les listes d'observation dans une ensemble particulière
query_help_species_list_pattern_search: les listes d'observation correspondant à une chaîne de recherche
query_help_user_all: tous les utilisateurs
query_help_user_in_set: les utilisateurs dans une ensemble particulière
query_help_user_pattern_search: les utilisateurs correspondant à une chaîne de recherche

# Sorting criteria.
sort_by_header: "Trier par:"
sort_by_id: ID
sort_by_name: nom
sort_by_title: titre
sort_by_summary: résumé
sort_by_date: date
sort_by_posted: date de publication
sort_by_created: date de création
sort_by_modified: date de dernière modification
sort_by_rss_log: date de dernière modification
sort_by_last_login: date de dernière connexion
sort_by_user: utilisateur
sort_by_login: nom d'utilisateur
sort_by_copyright_holder: titulaire du droit d'auteur
sort_by_where: endroit
sort_by_location: endroit
sort_by_confidence: niveau de confiance
sort_by_image_quality: qualité d'image
sort_by_thumbnail_quality: qualité de la vignette
sort_by_num_views: popularité
sort_by_contribution: contribution
sort_by_reverse: Inverser l'ordre

# RSS log messages.
log_ancient: "[String]"
log_approved_by: Approuvé par [user].
log_approved_by_with_comment: "[:log_approved_by] [comment]"
log_consensus_changed: "Consensus rejeté [old] en faveur de: [new]"
log_consensus_reached: "Consensus a été établi: [name]"
log_deprecated_by: Désapprouvé par [user].
log_deprecated_by_with_comment: "[:log_deprecated_by] [comment]"
log_changed_default_description: "Description par défaut a été changé par [user] en: [name]"
log_changed_permissions: "Autorisations modifié par [user]: [name]"
log_name_approved: "Approuvé par [user] sur: [other]"
log_name_approved_with_comment: "[:log_name_approved] [comment]"
log_name_deprecated: "Desapprouvé par [user] en faveur de: [other]"
log_name_deprecated_with_comment: "[:log_name_deprecated] [comment]"
log_name_merged: "[This] a fusionné avec [that]."
log_object_added_by_user: "[Type] a été ajouté par [user]."
log_object_added_by_user_with_name: "[Type] a été ajouté par [user]: [name]"
log_object_added_no_user: "[Type] a été ajouté."
log_object_created_by_user: "[Type] a été créé par [user]."
log_object_created_by_user_with_name: "[Type] a été créé par [user]: [name]"
log_object_created_no_user: "[Type] a été créé."
log_object_destroyed_by_user: "[Type] a été détruit par [user]."
log_object_destroyed_by_user_with_name: "[Type] a été détruit par [user]: [name]"
log_object_destroyed_no_user: "[Type] a été détruit."
log_object_merged_by_user: "[FROM] a été fusionné avec [to] par [user]."
log_object_merged_no_user: "[FROM] a été fusionné avec [to]."
log_object_moved_by_user: "[FROM] a été déplacé dans [to] par [user]."
log_object_moved_no_user: "[FROM] a été déplacé dans [to]."
log_object_removed_by_user: "[Type] a été éliminé par [user]."
log_object_removed_by_user_with_name: "[Type] a été éliminé par [user]: [name]"
log_object_removed_no_user: "[Type] a été éliminé."
log_object_updated_by_user: "[Type] a été mis à jour par [user]."
log_object_updated_by_user_with_name: "[Type] a été mis à jour par [user]: [name]"
log_object_updated_no_user: "[Type] a été mis à jour."
log_orphan: "[Title]"
log_published_description: "Description a été publié par [user]: [name]"
log_updated_by: Mis à jour par [user].

# These should not need any translation.
log_comment_added: "[:log_object_added_by_user_with_name(type=:comment,name=summary)]"
log_comment_destroyed: "[:log_object_destroyed_by_user_with_name(type=:comment,name=summary)]"
log_comment_updated: "[:log_object_updated_by_user_with_name(type=:comment,name=summary)]"
log_description_created: "[:log_object_created_by_user_with_name(type=:description)]"
log_description_destroyed: "[:log_object_destroyed_by_user_with_name(type=:description)]"
log_description_updated: "[:log_object_updated_by_user_with_name(type=:description)]"
log_image_created0: "[:log_object_added_no_user(type=:image)]"
log_image_created: "[:log_object_added_by_user_with_name(type=:image)]"
log_image_destroyed0: "[:log_object_destroyed_no_user(type=:image)]"
log_image_destroyed: "[:log_object_destroyed_by_user_with_name(type=:image)]"
log_image_removed0: "[:log_object_removed_no_user(type=:image)]"
log_image_removed: "[:log_object_removed_by_user_with_name(type=:image)]"
log_image_reused0: "[:log_object_added_no_user(type=:image)]"
log_image_reused: "[:log_object_added_by_user_with_name(type=:image)]"
log_image_updated0: "[:log_object_updated_no_user(type=:image)]"
log_image_updated: "[:log_object_updated_by_user_with_name(type=:image)]"
log_location_created: "[:log_object_created_by_user(type=:location)]"
log_location_destroyed: "[:log_object_destroyed_by_user(type=:location)]"
log_location_updated: "[:log_object_updated_by_user(type=:location)]"
log_name_created: "[:log_object_created_by_user(type=:name)]"
log_name_destroyed: "[:log_object_destroyed_by_user(type=:name)]"
log_name_updated: "[:log_object_updated_by_user(type=:name)]"
log_naming_created: "[:log_object_created_by_user_with_name(type=:naming)]"
log_naming_destroyed: "[:log_object_destroyed_by_user_with_name(type=:naming)]"
log_naming_updated: "[:log_object_updated_by_user_with_name(type=:naming)]"
log_observation_created: "[:log_object_created_by_user(type=:observation)]"
log_observation_destroyed2: "[:log_object_destroyed_by_user_with_name(type=:observation)]"
log_observation_destroyed: "[:log_object_destroyed_by_user(type=:observation)]"
log_observation_updated: "[:log_object_updated_by_user(type=:observation)]"
log_project_added_admin: "[:log_object_added_by_user_with_name(type=:admin)]"
log_project_added_member: "[:log_object_added_by_user_with_name(type=:member)]"
log_project_created: "[:log_object_created_by_user(type=:project)]"
log_project_destroyed: "[:log_object_destroyed_by_user(type=:project)]"
log_project_removed_admin: "[:log_object_removed_by_user_with_name(type=:admin)]"
log_project_removed_member: "[:log_object_removed_by_user_with_name(type=:member)]"
log_project_updated: "[:log_object_updated_by_user(type=:project)]"
log_species_list_created: "[:log_object_created_by_user(type=:species_list)]"
log_species_list_destroyed: "[:log_object_destroyed_by_user(type=:species_list)]"
log_species_list_updated: "[:log_object_updated_by_user(type=:species_list)]"
log_object_added: "[:log_object_added_by_user]"
log_object_created: "[:log_object_created_by_user]"
log_object_destroyed: "[:log_object_destroyed_by_user]"
log_object_removed: "[:log_object_removed_by_user]"
log_object_updated: "[:log_object_updated_by_user]"

################################################################################

# APPLICATION LAYOUT -- this stuff appears on every single page

# This goes in the title bar of the browser.  You don't need to translate this,
# it's up to you.
app_title: Mushroom Observer

# This goes in the left-hand column.  The "<br/>" forces a line-break.
app_banner: Mushroom<br/>Observer

# These are the controls/links in the left-hand panel.
app_intro: Introduction
app_how_to_use: Comment utiliser
app_how_to_help: Comment aider
app_send_a_comment: Envoyer commentaire
app_index_a_z: Index A->Z
app_list_locations: Énumérer les endroits
app_list_projects: Énumérer les projets
app_latest: La plus réciente
app_latest_changes: Activité
app_newest_images: Images
app_comments: Commentaires
app_news: Fonctionnalités
app_observations_left: Observations
app_create_observation: Créer observation
app_sort_by_date_obs: Trier par date
app_sort_by: "[:sort_by_object(type=order)]"
app_species_list: Listes d'observation
app_create_list: Créer une liste
app_sort_by_date_spl: Trier par date
app_sort_by_title: Trier par titre
app_account: Compte
app_login: Connexion
app_create_account: Créer un compte
app_current_user: Utilisateur en cours
app_comments_for_you: Commentaires pour vous
app_your_observations: Vos observations
app_your_interests: Vos intérêts
app_your_summary: Votre profil
app_preferences: Votre préférences
app_join_mailing_list: Rejoindre liste de diffusion
app_logout: Déconnexion
app_admin: Admin
app_users: Énumérer les utilisateurs
app_email_all_users: E-mail tous les utilisateurs
app_add_to_group: Ajouter au groupe
app_turn_admin_on: Activer la mode admin
app_turn_admin_off: Désactiver la mode admin
app_languages: Autres langues
app_contributors: Contributeurs
app_site_stats: Stats du site
app_colors_from: Couleurs selon [theme]
app_powered_by: Construite sur
app_preferred_browser: Navigateur préféré
app_feature_tracker:  Feature Tracker

# This is for the search bar at the top of every page.
app_find: Trouver
app_search: Rechercher
app_search_google: Site (via google)
app_refine_search: Affiner la recherche
app_advanced_search: Recherche avancée
app_timer: "durée: [seconds] sec"
app_index_timer: "[num] résultats dans [seconds] sec"

# This shows up at the bottom of every page.  We recommend something like:
# "Translated into <Language> by _user your-login_"
app_translators_credit: Traduit en français (mal) par _user jason_

# These are general alerts that appear near the top of the page.
app_no_ajax: Votre navigateur est obsolète
app_no_browser: Nous ne reconnaissons pas votre navigateur
app_no_javascript: Javascript est désactivé
app_no_session: Vous avez désactivé les cookies

# Title of the RSS auto-discovery link in the HTML header section.
app_rss: "[:app_title] RSS"

# Donation stuff.
# CHANGED: 20110601
# app_donate_banner: '"Better than it was before. Better...Stronger...Faster! Thanks to donors and Jason!":/support/donate'
app_donate_banner: Consultez notre "«tracker de fonction»":/pivotal/index nouveau et amélioré.
app_donate: Faire un don

################################################################################

# MOST POPULAR PAGES

# observer/ask_observation_question
ask_observation_question_title: Question sur [name]
ask_observation_question_label: >
  Entrez votre question ci-dessous.  Lorsque vous cliquez sur «[:SEND]», il
  sera envoyé par courriel à [user].  L'email contiendra automatiquement un
  lien vers cette observation ainsi que votre adresse e-mail.



# observer/ask_user_question
ask_user_question_title: Envoyer un email à [user]
ask_user_question_message: "[:Message]"
ask_user_question_subject: "[:Subject]"



# observer/ask_webmaster_question
ask_webmaster_title: Nous envoyer une question ou une commentaire
ask_webmaster_your_email: Votre addresse électronique
ask_webmaster_question: La question ou commentaire
# CHANGED: 20110615
ask_webmaster_note: >
  Merci de votre intérêt pour le Mushroom Observer.  Ce site a été lancé à la
  mi-2006.  Jason et moi sommes actuellement les développeurs principaux et les
  responsables.  Nous accueillons toutes les questions que vous pourriez avoir
  sur l'utilisation du site ou des commentaires sur la façon dont le site
  pourrait être améliorée.  S'il vous plaît jeter un oeil à notre "tracker de
  fonction":/pivotal/index ou notre "compte sur Pivotal
  Tracker":https://www.pivotaltracker.com/projects/224629 pour voir ce que nous
  avons prévu.  Vous pouvez voter et commenter sur toutes les suggestions
  diverses pour le développement futur.  Toutefois, ils ne sont que des
  guides bruts, soumis à des bugs ou autres problèmes qui pourraient surgir et,
  bien sûr, la disponibilité de notre temps à travailler sur le site.
  \n\n
  Nathan Wilson\n
  Jason Hollinger\n
  WebMasters du Mushroom Observer



# comment/add_comment
comment_add_title: Ajouter une commentaire sur [name]
comment_add_create: "[:CREATE]"



# comment/edit_comment
comment_edit_title: Modifier votre commentaire sur [name]



# comment/list_comments (This is used to describe the object the comment is
# about if the object has been deleted, orphaning the comment.)
comment_list_deleted: objet a été supprimé



# comment/show_comment
comment_show_title: "Commentaire sur [Name]"
comment_show_created: "[:Created]"
comment_show_by: "[:By]"
comment_show_summary: "[:Summary]"
comment_show_comment: "[:Comment]"
comment_show_show: "[:show_object]"
comment_show_edit: "[:EDIT]"
comment_show_destroy: "[:DESTROY]"



# observer/commercial_inquiry
commercial_inquiry_title: Enquête de commerce relatives à [name]
commercial_inquiry_header: >
  Entrez votre demande commerciale de cette image.  Lorsque vous cliquez sur
  «[:SEND]», il sera envoyé par courriel à [user].  L'email contiendra
  automatiquement un lien vers cette image.



# location/create_location_description
create_location_description_title: "[:create_name_description_title]"



# location/create_location
create_location_title: Créer un endroit



# name/create_name_description
create_name_description_title: Créer une description pour [name]



# name/create_name
create_name_title: Créer un nom



# observer/create_naming
create_naming_title: "Proposer un nom pour l'observation #[id]"



# observer/create_observation
create_observation_title: Créer une observation"



# location/edit_location
edit_location_title: Modifier un endroit



# location/edit_location_description
edit_location_description_title: Modifier la description de [name]



# name/edit_name_description
edit_name_description_title: Modifier [name]



# name/edit_name
edit_name_title: Modifier la description de [name]



# observer/edit_naming
edit_naming_title: "Modifier votre nom proposé pour l'observation #[id]"



# observer/edit_observation
edit_observation_title: "Modifier votre observation: [name]"



# account/email_new_password
email_new_password_title: Réinitialiser le mot de passe
email_new_password_login: Connexion



# observer/_form_comments
form_comments_comment: "[:Comment]"
form_comments_summary: "[:Summary]"



# shared/_form_description
form_description_source: Source
form_description_source_public: La description publique du [:app_title]
form_description_source_foreign: Fourni par un autre serveur du [:app_title]
form_description_source_project: Projet
form_description_source_source: Source indépendante
form_description_source_user: Utilisateur
form_description_permissions: Autorisations
form_description_public_writable: Modifiable par le grand public.
form_description_public_readable: Visible au grand public.
form_description_source_help: >
  Il y a trois sortes de descriptions que vous pouvez créer.\n
  1. *Publique:* Ce sont des documents que vous pouvez trouber sur wikipedia.
  Ils sont modifiables par tout le monde.  Le titre par défaut est
  «[:description_part_title_public]».  Utilisez le champ texte ci-dessus pour
  le personnaliser.\n
  2. *Source:* Ces descriptions proviennent d'une source tierce partie,
  et ne sont généralement pas destinés à être modifiable.  Entrez le nom
  de la source dans le champ texte ci-dessus.  Notez bien, si vous postez
  une description que dérive de matériel protégé, s'il vous plaît n'oubliez
  pas de le réécrire dans vos propres mots.\n
  3. *Utilisateur:* Utilisez cette option pour créer votre propre description
  personalisée.  Le titre par défaut est
  «[:description_part_title_user(user=:name)]».  Utilisez le champ texte
  ci-dessus pour le personnaliser.  Dans ce cas et celle ci-dessus, «Source»,
  vous aurez droit exclusif de choisir qui peut voir et modifier cette
  description (voir les cases ci-dessous).\n

form_description_permissions_help: >
  Est-ce que le grand public est autorisé à afficher ou apporter des
  modifications à cette description?  Si vous souhaitez avoir plus de contrôle
  sur les autorisations lire, écrire, et admin, s'il vous plaît utiliser le
  lien «[:show_description_adjust_permissions]» ci-dessus.

form_description_license_help: >
  S'il vous plaît sélectionnez «la license»:/observer/how_to_use#license à
  utiliser pour cette description.



# observer/_form_images
form_images_when_taken: Quand a-t-elle pris?
form_images_when_help: La date que l'image ou le dessin a été créé.
form_images_notes_help: Entrez les notes que sont spécifique à cette image particulière.
form_images_copyright_holder: "[:COPYRIGHT_HOLDER]"
form_images_select_license: Sélectionnez la license
form_images_license_help: >
  «La license»:/observer/how_to_use#license que vous souhaitez utiliser pour cette image.



# observer/_form_list_feedback
form_list_feedback_missing_names: Les noms suivants n'ont pas pu être trouvé.
form_list_feedback_missing_names_help: >
  Cliquez sur «[:SAVE]» / «[:UPDATE]» pour créer ces noms. Si vous voulez corriger
  ceux que vous avez entré à la main, faites-le dans le champs ci-dessous et
  soumettez à nouveau le formulaire. Si les noms proviennent d'une liste téléchargé,
  corrigez le fichier et le téléchargez à nouveau.



# location/_form_location
form_locations_gen_desc:  General Description
form_locations_ecology:  Habitat Description
form_locations_species:  Interesting Species
form_locations_notes:  "[:Notes]"
form_locations_refs:  "[:form_names_refs]"
form_locations_refs_help:  "[:form_names_refs_help]"
form_locations_help:  <a href="/location/help" target="_new">Help</a>
form_locations_find_on_map:  Find on Map =>

form_locations_lat_long_help:  >
  All values should be in decimal degrees.

form_locations_license_help:  >
  Select "license":/observer/how_to_use#license you want to give for the
  above text.

form_locations_gen_desc_help:  >
  Describe the geographical location of this location.

form_locations_ecology_help:  >
  Summarize the climate, geology, ecology, plant communities, etc.

form_locations_species_help:  >
  List the common, rare, or otherwise interesting species found here.

form_locations_notes_help:  >
  Enter notes that are specific to this particular location.  For example,
  whether it is private or public, whether permits are required, driving
  directions, etc.

form_locations_dubious_help:  >
  Submit again to use this location name or edit the text below to correct any typo.



# observer/_form_name
form_names_text_name:  Scientific Name
form_names_misspelling:  This name is misspelt.
form_names_misspelling_it_should_be:  It should be
form_names_taxonomic_notes:  Notes on Taxonomy
form_names_classification:  Taxonomic Classification
form_names_gen_desc:  General Description
form_names_diag_desc:  Diagnostic Description
form_names_look_alikes:  Look Alikes
form_names_habitat:  Habitat
form_names_distribution:  Distribution
form_names_uses:  Uses
form_names_notes:  Notes
form_names_refs:  References
form_names_text_name_help:  >
  Unformatted version of the name without any author info.\n
  E.g., "Amanita muscara var. flavivolvata".

form_names_text_name_locked:  >
  Name is in use.  Make name changes in each observation.

form_names_author_help:  >
  The author citation using the standard ICBN format.\n
  E.g., "(Singer) Jenkins".

form_names_author_locked:  >
  Name with this author citation is in use.  Make name changes in each
  observation.

form_names_citation_help:  >
  Citation for the publication of this name.

form_names_citation_textilize_note:  >
  Citations can be formatted using the Textile markup system.

form_names_misspelling_note:  >
  If this name is misspelt, please check the box and enter the correct
  spelling. *NOTE:* Please do not use this to deprecate correctly-spelled
  synonyms.

form_names_classification_help:  >
  List the higher taxa containing this [rank], one name per rank.  Example:<br/>
  Domain: _Eukarya_<br/>
  Kingdom: _Fungi_<br/>
  Phylum: _Basidiomycota_<br/>
  Class: _Agaricomycetes_<br/>
  Order: _Agaricales_<br/>
  Family: _Agaricaceae_<br/>
  Genus: _Agaricus_<br/>

form_names_gen_desc_help:  >
  Describe the general appearance of this taxon.

form_names_diag_desc_help:  >
  Describe what distinguishes this taxon from closely related taxa.

form_names_look_alikes_help:  >
  What other taxa look similar to this one?

form_names_habitat_help:  >
  What habitats has taxon has been found in?

form_names_distribution_help:  >
  Where geographically has this taxon been found and where is it expected to
  occur?

form_names_uses_help:  >
  How has this taxon been used by people?

form_names_notes_help:  >
  Please include notes about the validity of this name, common misuses of the
  name, and more appropriate names to be used when applicable.

form_names_refs_help:  >
  Each line is considered a separate reference, but no other formatting is
  enforced.



# observer/_form_naming
form_naming_confidence:  Confidence
form_naming_valid_synonyms:  Valid synonyms are
form_naming_deprecated:  The name '[name]' is deprecated.
form_naming_not_recognized:  The name '[name]' was not recognized.
form_naming_name_help_create:  >
  The name you would apply to this observation.  If you don't know what it is,
  just leave it blank.  If you find a better name in the future, you can always
  propose a name later.

form_naming_name_help:  >
  Scientific names are currently required, but do not include any author
  information.  If multiple names apply, you will be given the option to select
  between them.  If the name is not recognized in the database, then you will
  be given the option to add the name or fix the spelling if it's just a typo.

form_naming_deprecated_help:  >
  Select a valid name or click '[button]' to use '[name]'.

form_naming_correct_help:  >
  Did you mean one of the following names? [:form_naming_deprecated_help]

form_naming_not_recognized_help:  >
  Click '[button]' to create this name or edit the name below to correct any
  typo.

form_naming_multiple_names:  >
  Multiple names match '[name]'.  Select the one you intended.

form_naming_multiple_names_help:  >
  The number after each name is how many observations are currently using
  that name.

form_naming_confidence_help:  >
  How confident are you of this identification?  Please justify how you arrived
  at your decision in the boxes below, as well.



# observer/_form_observations
form_observations_specimen_available: Spécimen d'herbier est disponible
form_observations_is_collection_location: L'endroit de collection
form_observations_upload_images: Images à télécharger
form_observations_upload_another: Télécharger une autre...
form_observations_edit_image: Modifier l'image
form_observations_remove_image: Supprimer l'image
form_observations_lat_long_help: >
  Localisation GPS facultatif.  La latitude doit être comprise entre -90,0 et
  90,0 et la longitude entre -180,0 et 180,0.  Si vous choisissez de fournir
  ces données, s'il vous plaît le rendre aussi précis que possible.

form_observations_log_change: Enregistrez les changements dans le journal.
form_observations_is_collection_location_help: >
  Cochez cette case si c'est l'endroit où le champignon a été croissant.
  Décochez quand il a été recuelli ailleurs, par exemple, pour les faires aux
  champignons, à l'épicerie, sur la table d'une incursion où l'endroit de
  collection est inconnue, etc.

# CHANGED: 20110616
form_observations_notes_help: >
  S'il vous plaît incluir toute information supplémentaire que vous pouvez
  penser à propos de cette observation que n'est pas clair à partir des
  photographies: habitat, substrat, arbers à proximité; texture, scent ou goût
  particulière; réaction de color ou contusion; les résultats des analyses
  chimiques ou microscopiques; etc.

form_observations_remove_image_confirm: >
  Etes-vous sûr de vouloir supprimer cette image?  Cela ne fera que retirer
  cette image à partir de cette observation, et non pas le détruire.  Si elle
  est attachée à d'autres observations, il restera attaché à eux.

form_observations_specimen_available_help: >
  Cochez cette case quand il y a un spécimen séché disponible pour une étude
  plus approfondie.  Cela peut être soit un herbier officiel ou partie d'une
  collection personnelle.  S'il vous plaît notez où le spécimen est dans notes.

form_observations_upload_help: >
  Utilisez les cases sur la gauche pour sélectionner l'image que vous souhaitez
  utiliser comme la vignette pour cette observation.

form_observations_where_help: >
  C'est là où l'observation a été faite.  Aux E.E.U.U. cela devrait au moins
  être exante dans le comté.  Exemples:\n
  Albion, Mendocino Co., California, USA\n
  Hotel Parque dos Coqueiros, Aracaju, Sergipe, Brazil

form_observations_dubious_help: >
  Cliquez sur «[button]» d'utilizer ce nom d'endroit, sinon modifiez le text
  ci-dessous pour corriger les fautes de frappe.



# observer/_form_species_list
form_species_lists_title:  Title
form_species_lists_species_to_add:  Select Species to Add
form_species_lists_write_in_species:  "Write-In Species: (enter a name on each line)"
form_species_lists_list_notes:  Species List Notes
form_species_lists_member_notes:  Notes for each new member
form_species_lists_deprecated:  The following names are deprecated
form_species_lists_deprecated_help:  >
  Select any names you would prefer to use.  If you prefer a name you entered
  then don't select one of the suggested synonyms.

form_species_lists_multiple_names:  >
  Multiple names match each of the following entries

form_species_lists_multiple_names_help:  >
  In each case, select the intended name.  The number after each name is how
  many observations are currently using that name.

form_species_lists_bulk_help:  >
  Bulk name creation has moved to the "[:name_bulk_title]":/name/bulk_name_edit
  page.



# observer/_form_synonyms
form_synonyms_names:  Names
form_synonyms_names_help:  >
  List the names you want to be synonymized with [name].

form_synonyms_current_synonyms:  Current Synonyms
form_synonyms_current_synonyms_help:  >
  Unchecked items will no longer be synonymized with this name, but will
  remain synonymized with each other.

form_synonyms_proposed_synonyms:  Proposed Synonyms
form_synonyms_proposed_synonyms_help:  >
  Unchecked items will no longer be synonymized with this name, but will retain
  their relationships with each other.

form_synonyms_deprecate_synonyms:  Deprecate Synonyms
form_synonyms_deprecate_synonyms_help:  >
  If checked all listed synonyms become deprecated names.  Otherwise, they are
  left as they are with new names created as not deprecated.

form_synonyms_missing_names:  The following names could not be found.
form_synonyms_missing_names_help:  >
  Click 'Add' to create these names.  If you want to correct any names, do so
  in the area below and click 'Add' to re-evaluate the list.



# image/add_image
image_add_title: "Téléchargez une image pour: [name]"
image_add_edit: Modifier l'observation
image_add_default: vignette par défaut
image_add_image: Image
image_add_optional: facultatif
image_add_upload: Télécharger
image_add_warning: >
  S'il vous plaît ne téléchargez les images que vous créez ou pour lesquels
  voud détenez les droits d'auteur.  Par télécharger des images vous nous
  donnez la permission de les distribuer aux autres utilisateurs ("jargon
  juridique":http://creativecommons.org/licenses/by-nc-sa/2.5/).  Vous êtes
  également nous donner la permission de les afficher le long côté des
  publicités ou d'autres outils de collecte de fonds qui peuvent être utilisés
  pour soutenir ce site.



# image/reuse_image_for_user
image_reuse_all_users: Incluir les images des utres utilisateurs.
image_reuse_just_yours: Afficher seulement vos images.



# image/edit_image
image_edit_title: "Modifier l'image: [name]"



# image/remove_images
image_remove_edit: Modifier l'observation
image_remove_remove: Supprimer
image_remove_title: "Supprimer des images de: [name]"



# image/reuse_images
image_reuse_title: "Partager une image pour: [name]"
image_reuse_edit: Modifier l'observation
image_reuse_id: ID de l'image
image_reuse_reuse: Partager
image_reuse_id_help: >
  Soit cliquez sur une des images ci-dessous, ou si vous connaissez l'ID de
  l'image, il suffit d'entrez-le ici et cliquez sur «[:image_reuse_reuse]'.».



# image/show_image
image_show_title: "Image: [name]"
image_show_inquiry: Envoyer une enquête de commerce relatives à cette image
image_show_edit: Modifier l'image
image_show_destroy: Détruire
image_show_when: Quand
image_show_notes: Notes
image_show_copyright: Droits d'auteur
image_show_quality: Qualité
image_show_your_vote: Votre vote
image_show_vote_and_next: Voter et Suivant
image_show_comments: "[num] commentaire(s)"
image_show_observations: Observations
image_show_thumbnail: Vignette
image_show_small: Petit
image_show_medium: Moyen
image_show_large: Grande
image_show_huge: Énorme
image_show_full_size: Taille entière
image_show_original: Afficher l'image originale
image_show_make_default: Faire de cette la taille par défaut.



# observation/list_observations
list_observations_location_all: Tous les endroits
list_observations_location_define: Definer c'endroit
list_observations_location_merge: Fusionner avec un endroit definé



# location/list_place_names
list_place_names_known: Endroits definés
list_place_names_known_order: '(par nom)'
list_place_names_undef: Endroits undefinés
list_place_names_undef_order: '(par fréquence)'
list_place_names_map: Afficher sur une carte
list_place_names_merge: Fusionner



# _location (RSS log display)
location_change: Changement dans endroit


# model/location
location_dubious_ambiguous_country:  Ambiguous country or state, '[country]'
location_dubious_bad_char:  Contains unexpected character '[char]'
location_dubious_bad_term:  Contains bad term, '[bad]', rather than '[good]'
location_dubious_commas:  All commas should be followed by a space and another word
location_dubious_empty:  Empty location given
location_dubious_redundant_county:  County may be redundant
location_dubious_redundant_state:  Both '[state]' and '[country]' are on the list of countries and continents
location_dubious_unknown_country:  Unknown country '[country]'
location_dubious_unknown_state:  Unknown state '[state]', '[country]'


# account/login
login_please_login: S'il vous plaît vous connectez.
login_login: Connexion
login_user: Nom d'utilisateur ou addresse électronique
login_password: Mot de passe
login_remember_me: Rester connecté.
login_forgot_password: >
  J'ai oublié mon mot de passe. "Envoyez-moi un nouveau.":/account/email_new_password

login_no_account: >
  Je n'ai pas un compte.  "Créer un nouveau compte.":/account/signup

login_having_problems: >
  Si vous avez des problèmes pour vous connecter à votre compte, "envoyez-nous
  us message":/observer/ask_webmaster_question.



# account/logout
logout_title: Déconnexion
logout_note: >
  Vous êtes maintenant déconnecté du [:app_title].  Fonctions d'édition sont désactivées.



# location/map_locations
map_locations_title:  Map of [locations]
map_locations_global_map:  Global Map



# name/approve_name
name_approve_title:  Approve [name]
name_approve_comment_summary:  "[:Approved]"
name_approve_comments:  "[:Comments]"
name_approve_comments_help:  >
  Please include any notes about why this name has been approved.\n
  This will be added to the notes for [name].

name_approve_deprecate:  Deprecate the following synonyms
name_approve_deprecate_help:  >
  If you want to split up a set of synonyms, click 'Approve' or 'Cancel' and
  then click the 'Change Synonyms' link.



# name/change_synonyms
name_change_synonyms_title:  "Synonyms for [name]"
name_change_synonyms_submit:  Submit Changes
name_change_synonyms_confirm:  Please confirm that this is what you intended.



# name/deprecate_name
name_deprecate_title:  Deprecate [name]
name_deprecate_preferred:  Preferred name
name_deprecate_comment_summary:  "[:Deprecated]"
name_deprecate_comments:  "[:Comments]"
name_deprecate_submit:  "[:SUBMIT]"
name_deprecate_preferred_help:  >
  Enter the preferred name.  Author citation is recommended but not required.

name_deprecate_comments_help:  >
  Please include any notes about why this name has been deprecated.\n
  This will be added to the notes for [name].



# name/name_index (and other actions using same view)
name_index_add_name:  Add Name
name_index_bulk_edit:  "[:name_bulk_title]"



# name/map
name_map_title:  Occurrence Map for [name]
name_map_about:  "[:show_name]"
name_map_no_maps:  No observations of [name] have mappable location information.



# observer/news
news_title:  News
news_header:  >
  This page lists the latest changes to and news about the [:app_title]
  website.



# shared/_observation_list
observation_made_confidence: La confiance de la communauté



# account/prefs
prefs_title:  Change Preferences
prefs_link:  Edit Preferences
prefs_login:  Login
prefs_email:  Email address
prefs_password_new:  New password
prefs_password_confirm:  Confirm new password
prefs_theme:  Preferred theme
prefs_locale:  Language
prefs_location_format:  Location Format
prefs_location_format_postal:  "Postal (New York, USA)"
prefs_location_format_scientific:  "Scientific (USA, New York)"
prefs_votes_anonymous:  Votes on proposed names
prefs_votes_anonymous_no:  Always public
prefs_votes_anonymous_yes:  Always anonymous
prefs_votes_anonymous_old:  "Public after [cutoff]"
prefs_license_note:  Default "license":/observer/how_to_use#license you want for new images.
prefs_thumbnail_size:  Thumbnail size
prefs_thumbnail_small:  "[:image_show_small]"
prefs_thumbnail_large:  "[:image_show_large]"
prefs_image_size:  Image size
prefs_image_size_help:  Size shown when you click on an image.
prefs_image_small:  "[:image_show_small] (320 x 320)"
prefs_image_medium:  "[:image_show_medium] (640 x 640)"
prefs_image_large:  "[:image_show_large] (960 x 960)"
prefs_image_huge:  "[:image_show_huge] Huge (1280 x 1280)"
prefs_image_full_size:  "[:image_show_full_size]"
prefs_layout_title:  List page layout
prefs_rows_by:  rows x
prefs_columns:  columns
prefs_alt_col_colors:  Alternate column colors.
prefs_alt_row_colors:  Alternate row colors.
prefs_text_below_images:  Put text below images.
prefs_email_prefs:  Email preferences
prefs_email_please_notify:  Please notify me when...
prefs_email_general:  General Email
prefs_email_general_commercial:  someone is interested in using an image of mine for commercial purposes.
prefs_email_general_features:  new features come out.
prefs_email_general_questions:  someone wants to send me a question about my observations, etc.
prefs_email_comments:  "[:Comment] Email"
prefs_email_comments_all:  anyone comments on anything.
prefs_email_comments_owner:  someone comments on my observations, names, etc.
prefs_email_comments_response:  someone posts responses to my comments.
prefs_email_locations:  "[:Location] Email"
prefs_email_locations_all:  anyone changes any location.
prefs_email_locations_admin:  someone changes a location I administrate.
prefs_email_locations_author:  someone changes a location I'm author on.
prefs_email_locations_editor:  someone changes a location I've edited.
prefs_email_observations:  "[:Observation] Email"
prefs_email_observations_all:  anything happens to any observation.
prefs_email_observations_consensus:  consensus name changes for one of my observations.
prefs_email_observations_naming:  someone propose a name for one of my observations.
prefs_email_names:  "[:Name] Email"
prefs_email_names_all:  anyone changes any name.
prefs_email_names_admin:  someone changes a name I administate.
prefs_email_names_author:  someone changes a name I'm author on.
prefs_email_names_editor:  someone changes a name I've edited.
prefs_email_names_reviewer:  someone changes a name I've reviewed.
prefs_email_html:  It's okay to use HTML in my emails.
prefs_email_digest_daily:  Send me summary at the end of the day.
prefs_email_digest_immediate:  Notify me of events as they happen.
prefs_email_digest_weekly:  Send me summary at the end of the week.
prefs_email_note:  >
  Note that none of these email features will cause your email address to be
  displayed on a webpage or allow the person who wants to contact you to obtain
  your email address.  You will be sent an email from news at
  mushroomobserver.org that will contain the contact information for the person
  who wants to contact you.  It will be entirely up to you if you want to
  respond to them.



# account/profile
profile_title:  "[:edit_object(type=:profile)]"
profile_link:  "[:edit_object(type=:profile)]"
profile_button:  "[:SAVE_CHANGES]"
profile_name:  "[:Name]"
profile_notes:  About yourself
profile_location:  Primary location
profile_mailing_address:  Mailing Address for Collections
profile_image_create:  Upload photo
profile_image_change:  Upload new photo
profile_image_remove:  (Remove photo.)
profile_image_reuse:  (Reuse another photo.)
profile_copyright_holder:  Copyright holder and license for this image
profile_copyright_warning:  >
  Please only upload an image that you created or which you own the copyright of.



# account/reverify
reverify_welcome:  Reverify Account
reverify_link:  Reverify
reverify_note:  >
  Your account, [user], has not been verified yet.
  \n\n
  Check your email for your verification URL or click the link below to have
  the mail resent.



# observer/rss
rss_description: Liste des modifications apportées à [:app_title] mesure qu'ils surviennent.
rss_log_of_deleted_item: Record\nd'objet\nsupprimé
rss_log_title: Journal d'activité
rss_by: "par [user]"
rss_title: "[:app_title]"
rss_show: "Afficher:"
rss_hide: "Masquer:"
rss_all: Tous
rss_all_help: Afficher tous les types d'objets.
rss_one: "[TYPES]"
rss_one_help: Afficher seulement les [types].
rss_make_default: Faire de cette mes défaut
rss_this_is_default: Ceci est votre défaut
rss_created: "[TYPE] a été créé(e)"
rss_changed: "[TYPE] a été modifié(e)"



# shared/_textile_help
shared_textile_link:  More details here.
shared_textile_help:  >
  Notes can be formatted using the <a href="/observer/textile" target="_new">Textile markup system</a>.<br/>
  _Amanita ocreata_, _A. ocreata_ ---> <u><b><i>Amanita ocreata</i></b></u> (linked to name description)<br/>
  __italic__, **bold** ---> <i>italic</i>, <b>bold</b><br/>



# comment/_show_comments
show_comments_add_comment:  "[:add_object(type=:comment)]"
show_comments_no_comments_yet:  No one has commented yet.
show_comments_and_more:  And [num] more...



# observation/_show_consensus
show_consensus_list_of_species:  "List of species in [name]"



# name/show_name_description or location/show_location_description
show_description_empty:  Nothing has been written for this description yet.
show_description_destroy:  "[:DESTROY]"
show_description_edit:  "[:EDIT]"
show_description_clone:  Clone
show_description_merge:  Merge With Another
show_description_publish:  Publish
show_description_make_default:  Make Default
show_description_adjust_permissions:  Adjust Permissions
show_description_read_permissions:  View
show_description_write_permissions:  Edit
show_description_clone_help:  >
  Create your own description based on this description.

show_description_merge_help:  >
  Merge this description into another, then remove this one.

show_description_publish_help:  >
  Publish this draft and make it the default public description.

show_description_make_default_help:  >
  Make this the default description that is shown on the main
  '[:show_name(name=:name)]' page.

show_description_adjust_permissions_help:  >
  Change the set of users who are allowed to view, modify or administrate this
  description.



# observer/_show_images
show_images_small_thumbs: "(vignettes petites)"
show_images_large_thumbs: "(vignettes grandes)"



# observer/_show_lists
show_lists_header:  "[:SPECIES_LISTS]"



# location/show_location
show_location_title:  "[:LOCATION]: [name]"
show_location_create:  "[:create_object(type=:location)]"
show_location_edit:  "[:edit_object(type=:location)]"
show_location_destroy:  "[:destroy_object(type=:location)]"
show_location_observations:  "Observations at this Location"
show_location_highest:  Highest Altitude
show_location_lowest:  Lowest Altitude
show_location_no_descriptions:  There are no descriptions for this location yet.
show_location_create_description:  "[:CREATE]"
show_location_creator:  User who defined this location
show_location_editor:  "[:Editors]"
show_location_editors:  "[:Editors]"
show_location_reverse:  Reverse Location


# name/show_name
show_name_title:  "[:NAME]: [name]"
show_name_add_name:  "[:add_object(type=:name)]"
show_name_edit_name:  "[:edit_object(type=:name)]"
show_name_bulk_name_edit:  "[:name_bulk_title]"
show_name_distribution_map:  Occurrence Map
show_name_change_synonyms:  Change Synonyms
show_name_email_tracking:  Email Tracking
show_name_create_description:  "[:CREATE]"
show_name_synonyms:  Synonym(s)
show_name_preferred_synonyms:  Preferred Synonym(s)
show_name_deprecated_synonyms:  Deprecated Synonym(s)
show_name_misspelling:  This name is misspelled.
show_name_misspelling_correct:  "[:CORRECT_SPELLING]"
show_name_notes:  Notes on Taxonomy
show_name_descriptions:  "[:DESCRIPTIONS]"
show_name_create_draft:  Create New Draft for
show_name_no_descriptions:  There are no descriptions for this name yet.
show_name_description_author:  "[:Description] author"
show_name_description_authors:  "[:Description] authors"
show_name_description_editor:  "[:Description] editor"
show_name_description_editors:  "[:Description] editors"
show_name_author_request:  Request Authorship Credit
show_name_content_status:  Description status
show_name_latest_review:  "Latest review: [date] by [user]"
show_name_previous_version:  Previous Version
show_name_other_versions:  Other Versions
show_name_observations:  "More [:OBSERVATIONS]"
show_name_observations_of:  "More [:OBSERVATIONS] of [name]"
show_name_all_observations:  "More [:OBSERVATIONS] (all synonyms)"
show_name_synonym_observations:  "Synonym [:OBSERVATIONS]"
show_name_other_observations:  "Similar [:OBSERVATIONS]"
show_name_subtaxa_observations:  "Subtaxa [:OBSERVATIONS]"
show_name_creator:  First person to use this name on MO
show_name_editor:  "[:Editors]"
show_name_editors:  "[:Editors]"
show_name_other_observations_notes:  >
  (Someone proposed [name] for these observations, but consensus hasn't
  accepted it.  Confidence value is for __this__ name, not the consensus
  name.)



# observer/_show_namings
show_namings_proposed_name:  "[:NAMING]"
show_namings_proposed_names:  "[:NAMINGS]"
show_namings_no_names_yet:  No names have been proposed yet.
show_namings_propose_new_name:  Propose Another Name
show_namings_eye_help:  Observer's choice
show_namings_eyes_help:  Current consensus
show_namings_community_favorite:  This is the community favorite.
show_namings_consensus:  Community Vote
show_namings_no_votes:  no votes
show_namings_your_vote:  Your Vote
show_namings_update_votes:  Update Votes
show_namings_cast:  Cast Vote
show_namings_user:  "[:User]"
show_namings_consensus_help:  >
  For each name listed above select your opinion of how well that name applies
  to this observation.  Select '[:show_namings_propose_new_name]' if you want
  to suggest another option.  See the "How to Use":/observer/how_to_use#voting
  page for more details on how the votes are tallied.

show_namings_lose_changes:  >
  You must click '[:show_namings_update_votes]' to save any changes you've made to your votes.

show_namings_please_login:  >
  Please login to propose your own names and vote on existing names.



# observer/show_observation
show_observation_title: "Observation: [name]"
show_observation_header:  "[:OBSERVATION]"
show_observation_edit_observation: Modifier l'observation
show_observation_propose_new_name: "[:show_namings_propose_new_name]"
show_observation_debug_consensus: Déboguer le consensus
show_observation_alternative_name: Nom alternatif
show_observation_alternative_names: Noms alternatifs
show_observation_preferred_name: Nom préféré
show_observation_preferred_names: Noms préférés
show_observation_observation_created: Observation créé
# This is used if this is the location where the thing was growing.
show_observation_collection_location: L'endroit de collection
# This is used if this is NOT the location where the thing was growing.
show_observation_seen_at: L'endroit où il a été vu
show_observation_specimen_available: Spécimen d'herbier est disponible
show_observation_specimen_not_available: Aucun spécimen disponible.
show_observation_remove_images: Supprimer des images
show_observation_reuse_image: Partager une image
show_observation_add_images: Télécharger des images
show_observation_species_lists: "[:SPECIES_LISTS]"
show_observation_manage_species_lists: Gérer vos listes d'observation
show_observation_send_question: Envoyer une question à l'observateur
show_observation_view_notifications: Afficher notifications



# location/show_past_location
show_past_location_title:  "[:VERSION] [num]: [name]"
show_past_location_other_versions:  Other Versions



# location/show_past_location_description
show_past_location_description_title:  "[:VERSION] [num]: [name]"



# name/show_past_name
show_past_name_title:  "[:VERSION] [num]: [name]"



# name/show_past_name_description
show_past_name_description_title:  "[:VERSION] [num]: [name]"



# object/show_past_versions
show_past_version_merged_with:  "(merged with #[id])"



# observer/show_rss_log
show_rss_log_title:  Log for [title]



# observer/show_site_stats
show_site_stats_title:  Site Statistics



# observer/_show_votes
show_votes_title:  Show Votes for [name]
show_votes_users:  "[:Users]"
show_votes_vote:  "[:Vote]"
show_votes_weight:  Weight
show_votes_average:  Average
show_votes_score:  Score
show_votes_go_public:  Make all of my votes public.
show_votes_go_private:  Make all of my votes anonymous.
show_votes_total:  >
  Overall Score\n
  sum(score * weight) /\n
  (total weight + 1)

show_votes_descript:  >
  User's votes are weighted by their contribution to the site
  (log<span style='font-size:50%'>10</span> contribution).
  In addition, the user who created the observation gets an extra vote.

show_votes_go_public_confirm:  >
  This will make all your votes for all observations public, not just your vote
  for this name.  Is this what you want to do?

show_votes_go_private_confirm:  >
  This will make all your votes for all observations anonymous, not just your
  vote for this name.  Is this what you want to do?

show_votes_gone_public:  >
  Thank you!  Your preferences have been updated.  Other users can now see your
  votes.

show_votes_gone_private:  >
  Your preferences have been updated.  Other users can no longer see your votes.



# observer/show_user
show_user_title:  Contribution Summary for [user]
show_user_contributors:  "[:app_contributors]"
show_user_observations_by:  "Observations by [name]"
show_user_your_observations:  Your Observations
show_user_comments_for:  "Comments for [name]"
show_user_comments_for_you:  "Comments for You"
show_user_your_notifications:  Your Email Alerts
show_user_edit_profile:  Edit Profile
show_user_email_to:  Email [name]
show_user_joined:  Joined [:app_title]
show_user_mailing_address:  Mailing Address for Collections
show_user_primary_location:  Primary Location
show_user_total:  Total



# account/signup
signup_title:  Account signup
signup_name:  Name (optional)
signup_login:  Desired login
signup_email_address:  Email address
signup_choose_password:  Choose password
signup_confirm_password:  Confirm password
signup_preferred_theme:  Preferred Theme (optional)
signup_random:  Random
signup_button:  Signup
signup_email_help:  >
  A working email address is required to verify your account.  This helps us keep the spammers out.  Once
  you have verified your account, you can change it or remove it entirely by going to the Preferences page.
  We are very careful to never show your email address on a webpage that others can access.  We will never
  sell your email address.  We will only share your email address if you ask us to (e.g., when you send an
  email to another member, they will see your email).  By default your email address will be used to send
  you information about changes to the site as well as notifications relevant to your contributions to the
  site.  You can opt out of these uses by changing your Preferences.



# species_list/create_species_list
species_list_create_title:  "[:create_object(type=:species_list)]"



# species_list/edit_species_list
species_list_edit_title:  "[:edit_object(type=:species_list)]: [name]"



# species_list/manage_species_lists
species_list_manage_title:  Manage Species Lists for [name]
species_list_manage_belongs_to:  This observation belongs to
species_list_manage_doesnt_contain:  Lists you own that do not contain this observation




# species_list/show_species_list
species_list_show_title:  "[:SPECIES_LIST]: [name]"
species_list_show_save_as_txt:  Save as Plain Text
species_list_show_save_as_rtf:  Save as Rich Text
species_list_show_save_as_csv:  Save as Spreadsheet
species_list_show_edit:  Edit Species List
species_list_show_clone_list:  Clone Species List
species_list_show_set_source:  Save for Later
species_list_show_members:  Members
species_list_show_no_members:  This list contains no observations.
species_list_show_clone_list_help:  >
  Create a new species list using this one as the template.

species_list_show_set_source_help:  >
  Save this species list for the next time you create or edit a species list.
  It will display a list of the species in this list for you to choose from.



# species_list/species_lists_by_title
species_list_by_title_title:  "[:SPECIES_LISTS] by Title"
species_list_by_title_created:  "[:Created]"
species_list_by_title_list_name:  List Name
species_list_by_title_owner:  Owner
species_list_by_title_size:  Size



# species_list/upload_species_list
species_list_upload_title:  "[:UPLOAD] [:SPECIES_LIST]"
species_list_upload_label:  "[:UPLOAD] [:SPECIES_LIST]"
species_list_upload_help:  >
  A species list can either be a simple text file with each name on its own
  line, or the 'list' format generated by the Name species listing program.



# observer/users_by_contribution
users_by_contribution_title:  List of Contributors
users_by_contribution_2a:  "[:images]"
users_by_contribution_2b:  "[:name]"
users_by_contribution_2c:  "[:observation]"
users_by_contribution_2d:  "[:naming]"
users_by_contribution_2e:  "[:vote]"
users_by_contribution_2f:  points
users_by_contribution_1:  >
  The order is currently based on an automated estimation of what each person
  has contributed to the site.  The purpose of creating this order is to
  recognize the individual contributions of the members of the
  [:app_title] community.
  \n\n
  The current formula is a weighted sum of each contribution.  The current
  weighting is:

users_by_contribution_2:  >
  Thus an observation of a species not previously in the site with three images
  would count as:

users_by_contribution_3:  >
  These weights or the overall method of ranking is likely to change over time
  based on feedback from the members of the community.



# account/verify
verify_note:  >
  Your account has been verified...
  \n\n
  You should now be able to post observations, upload images, edit name
  descriptions, define new locations, add comments, and propose and vote on
  identifications at "[:app_title]":[domain].
  \n\n
  Thanks for joining!



# account/welcome
welcome_no_user_title:  User not set in session
welcome_logout_link:  Logout
welcome_no_user_note:  If you are not a spammer, please report this as an error.
welcome_note:  You are now logged into the system...



# support/donate
donate_title:  Donate to Mushroom Observer
donate_tab:  Donate
donate_other:  Other Amount
donate_anonymous:  Anonymous donation
donate_who:  Name for Donors Page
donate_email:  Email (to ensure uniqueness)
donate_confirm:  Confirm
donors_order:  The donors names are ordered based first on the total amount donated and then by who has donated the most recently.
donors_title:  The Mushroom Observer Community Thanks Our Donors
donors_tab:  Show Donors

donate_thanks:  >
  Thank you for your interest in donating to Mushroom Observer!  Check out this
  "2011 wrapup letter to the Mushroom Observer Community":/support/wrapup_2011
  if you are curious what we are using your donations for.

donate_explanation:  >
  Donations can be made in any amount through PayPal using most common credit cards or a PayPal account by clicking on the button below.
  Donors are normally acknowledged by name on the "Mushroom Observer Donors Page":/support/donors once the funds are received.  If you would
  like special arrangements for your acknowledgement please "send us a comment":/observer/ask_webmaster_question.

donate_fine_print:  >
  Charges will be made to the "Consortium for Digital Mycology Resources":http://digitalmycology.org (CDMR) and will be applied
  to the Mushroom Observer.  You can learn more about the CDMR at "http://digitalmycology.org":http://digitalmycology.org.
  The CDMR has been incorporated in the state of California
  and recognized by the state as a non-profit.  In addition, the corporation has applied for 501c3 status with the US federal government
  and as such our understanding is that donations to Mushroom Observer are tax deductible to the full extent allowed by law.\n\n
  If you would prefer not to use PayPal, you are welcome to send a check or money order in US dollars payable to the
  "Consortium for Digital Mycology Resources" to:\n\n
  Mushroom Observer\n
  c/o Nathan Wilson\n
  43 Cameron Rd.\n
  North Falmouth, MA 02556\n\n
  Please indicate on the check or on an included note that the donation is intended for the Mushroom Observer.



# support/confirm
confirm_title:  Donation Confirmation
confirm_amount:  Amount
confirm_text:  >
  Thank you for offering to make the following donation.  To transfer the money to
  the "Consortium for Digital Mycology Resources":http://digitalmycology.org (CDMR)
  using PayPal, click the button below.



# support/thanks
thanks_title:  Thanks for Your Support!
thanks_no_amount:  Sorry, we were unable to determine the amount of your donation.  Please send us a comment about this.
thanks_note:  >
  Thank you for helping to support the Mushroom Observer.  Your support is
  greatly appreciated and will help Mushroom Observer continue its mission.
  \n\n
  Your donation will be acknowledged by name on the "Mushroom Observer Donors
  Page":/support/donors once the funds are received unless you have requested
  special arrangements for your acknowledgement.  Examples of special
  arrangements might be to make the donation anonymously or to leave it in
  someone else's name.  If you would like special arrangements for your
  acknowledgement please "send us a comment":/observer/ask_webmaster_question.



# support/letter
letter_title:  Open Letter to the Community
letter_body:  >
  To the Mushroom Observer Community,
  \n\n
  It has been an amazing year for us.  This year we hit some major milestones:
  100,000 images, 50,000 observations and 2,000 registered users.  This means
  we have essentially been doubling every year.  While Jason has achieved some
  minor miracles in his volunteer efforts to keep things going with the bare
  bones server configuration we are using, it is becoming clear that we will
  soon need more memory and more processors to support our continued growth.
  \n\n
  Unfortunately, this means our server expenses will be going up.  So far I
  have been happy to support the Mushroom Observer server needs out of my own
  pocket, but those expenses have also been essentially doubling every year and
  I will soon not be able to afford it.  As a result, I would like to start
  asking for donations from the community.  Those of you who have gotten a lot
  out of the site and want to see it continue to grow and expand, now is your
  chance to give a little back and help with the financial support of the site.
  \n\n
  To that end, we have setup a "donation page":/support/donate that can
  securely accept money from a PayPal account or a regular credit card.
  \n\n
  I would like to raise at least $2000 to cover basic server costs.  The more
  we get, the more we can expand our capacity for traffic and growth.  And the
  fewer times you will encounter server down time and failed uploads.
  \n\n
  When you make a donation, your name by default will be added to our "donors
  page":/support/donors as soon as we confirm the donation.  If you would
  prefer to donate anonymously or make other special arrangements for your
  acknowledgement, "send a comment":/observer/ask_webmaster_question after you
  make your donation.
  \n\n
  Please help support this active internet community of people who enjoy
  sharing and learning more about the mushrooms around us.
  \n\n
  Thanks,\n
  -Nathan



# support/wrapup_2011
wrapup_2011_title:  2011 Wrapup to the Mushroom Observer Community
wrapup_2011_body:  >
  To the Mushroom Observer Community,
  \n\n
  2011 has been a relatively quiet year for Mushroom Observer at least from
  the perspective of new development.  I have personally been working overtime
  on a new version of the Encyclopedia of Life and Jason has been working hard
  on a new lichen related website and book.
  \n\n
  Even so the site has continued to grow.  We now have over 180,000 images, 80,000
  observations and we are very close to 3,000 registered users.  This continues
  our trend of nearly doubling every year.  Fortunately, due to generous
  donations from all of you, Jason was able to substantially upgrade our
  server configuration and to the best of our knowledge the system has been
  working very well despite the ever growing demand.  While we still have some
  money in the bank, we will continue to need "additional donations":/support/donate
  to keep the system going.
  \n\n
  As was true last year, the donations are made through a not-for-profit corporation
  called The Consortium for Digital Mycology Resources (CDMR).  The CDMR is recognized
  as a non-profit by the state of California, but is still not an official federal
  501c3 non-profit.  However, the application process has moved forward and for
  now we continue to act as a non-profit and donations are tax deductible.  For anyone
  interested in the details of that process please visit the "CDMR website":http://digitalmycology.org.
  \n\n
  There have been a few notable new features added to Mushroom Observer over the
  last year.  Jason did a great job developing
  the "MO Feature Tracker":/pivotal/index interface that interacts with our
  new freely accessible "Pivotal Tracker account":https://www.pivotaltracker.com/projects/224629
  for tracking bugs and feature requests.  In addition,
  I have been working quite a bit behind the scenes to prepare for a roughly 10 fold
  increase in the number of Mushroom Observer images that will be sharable with
  the broader biodiversity community and EOL in particular.
  \n\n
  Along with this note, we are also releasing the newly developed
  "Black on White":/observer/BlackOnWhite color theme.  With this theme I am 
  trying to provide a more current and professional look for the site.
  "Feedback on the theme or suggestions for improvements":/observer/ask_webmaster_question
  are very welcome.
  \n\n
  While there have not been a lot of new features released this year, there have
  been a number of important discussions going on about potential future development.
  These have included discussions of better ways of managing naming and voting
  so they align better with standard herbarium practices, improving the expressiveness of the voting
  system, rearranging the interface to be more workflow driven, and expanding the role of projects to
  encourage more focused collaboration within MO.
  \n\n
  Which brings us to the biggest news.  I have begun doing some of my own research
  with the data from the Mushroom Observer and I have received several
  inquiries from other scientists interested in either using Mushroom
  Observer as it is to support their own research or to support additional
  development of the Mushroom Observer to expand the connections between
  Mushroom Observer and the scientific community.
  \n\n
  My own research has included some preliminary analysis of the data in
  the Mushroom Observer database.  The most interesting finding has been that
  "users who collect in the Western US on average find more species there than users who collect in the Eastern US":/images/fungal_biogeography.png.
  I am currently in the process of developing funding and collaborators to
  more fully pursue this and other interesting questions that can be answered
  using our data.  Another area of research development has been with some of
  the computer scientists at Rensselaer Polytechnic Institute.  The group I
  am working with are focused on the emerging "semantic web":http://en.wikipedia.org/wiki/Semantic_web.
  We are developing a system for creating a new naming system for amateur/citizen mycologists.
  It will include a global, web-based registration system for names that are then associated with
  rigorous definitions that computers can reason about.  We have plans to support a summer internship
  through the EOL to help develop this idea.
  \n\n
  In addition, as many of you are aware Tom Bruns at UC Berkeley has already
  been using Mushroom Observer to catalog the collections his collaborators (including
  many of you) have been finding in Yosemite National Park.  He and I have also
  begun discussions of what features would be valuable to add Mushroom Observer
  to support his call for developing a "North American Mycoflora":http://msafungi.org/wp-content/uploads/Inoculum/62(4).pdf.
  Another promising development was being asked to write a letter of support for a
  proposal that Barabara Thiers and Roy Haling have submitted to digitize the
  fungal herbaria throughout the US.  If that gets funded, they
  are interested in making their data available through the Mushroom Observer.
  \n\n
  Finally, through connections at the EOL, I was able to participate in a workshop
  focused on citizen science biodiversity observation systems.  The workshop was
  held in October outside of London and included representatives from "iSpot":http://www.ispot.org.uk/
  and "iNaturalist":http://inaturalist.org along with several other significant global
  projects.  I went to the workshop not only to represent
  the technical side of the EOL, but also the Mushroom Observer.  As a result the group
  of projects involved in the workshop, including Mushroom Observer, are participating in a competition
  called "Badges for Lifelong Learning":http://www.dmlcompetition.net/Competition/4/badges-competition-cfp.php.
  We have already successfully passed the first stage of the competition and are working on our
  application for the second stage.
  \n\n
  While many of these projects promise exciting developments for MO over the next year and some
  may even include financial support for the development of new Mushroom Observer features, the on-going
  support for the site relies on "donations":/support/donate from you our users.
  Please help support this active internet community of people who enjoy
  sharing and learning more about the mushrooms around us.
  \n\n
  Thanks for all your contributions to the Mushroom Observer,\n
  -Nathan


# pivotal/index
pivotal_index_title:  Directions for Future Development
pivotal_post_comment:  Post Comment
pivotal_index_header:  >
  Use this page to browse through the many features requested by users and
  developers.  Some are very specific bug fixes or requests for new
  capabilities.  Others are just general areas people are interested in seeing
  Mushroom Observer grow.  Features are organized by use of the following set
  of labels.  Click on a label to see a list of features with that label.
  Click on a feature to see more detail and discussion.  If you are logged in,
  you will be able to vote features up or down, and you can add your own
  comments to the discussion.  If you would like to request a new feature, for
  now we request that you "send us an email":/observer/ask_webmaster_question
  describing what it is you'd like to do.  Please try to be as detailed as
  possible; concrete examples are generally the best.

pivotal_vote_failed:  >
  We were unable to process your vote.\n
  If the problem persists please notify to admins.\n
  Sorry for the inconvenience!\n

pivotal_story_failed:  >
  We were unable to get the story you requested.\n
  If the problem persists please notify to admins.\n
  Sorry for the inconvenience!\n

pivotal_comment_failed:  >
  We were unable to post your comment.\n
  If the problem persists please notify to admins.\n
  Sorry for the inconvenience!\n

pivotal_story_loading:  Loading story details...
pivotal_posting_comment:  Posting comment...
pivotal_posted_by:  Posted by

pivotal_state_unscheduled:  unscheduled
pivotal_state_unstarted:  in the queue
pivotal_state_started:  in progress

pivotal_head_critical:  serious bugs or mission-critical work
pivotal_head_bottleneck:  stuff required by lots of other things
pivotal_head_api:  programmer's interface via XML-RPC, etc.
pivotal_head_design:  web layout and graphic design
pivotal_head_email:  notification emails
pivotal_head_eol:  EOL content sharing
pivotal_head_i18n:  translation text and all the associated machinery
pivotal_head_interface:  web interface
pivotal_head_lists:  species lists, checklists, etc.
pivotal_head_locations:  'location descriptions and/or geocoding'
pivotal_head_names:  species descriptions
pivotal_head_projects:  group projects
pivotal_head_search:  search capabilities and data mining
pivotal_head_taxonomy:  synonymy, hierarchy, syntax, etc.
pivotal_head_voting:  voting on observations, their names, images, etc.
pivotal_head_other:  uncategorized
pivotal_head_admin:  administration tasks
pivotal_head_code:  internal code, e.g. documentation, refactoring, etc.
pivotal_head_server:  server installation, configuration, and diagnostics
pivotal_head_open:  areas we are actively soliciting feedback
pivotal_head_started:  areas developers are actively working
pivotal_head_unstarted:  scheduled for work soon
pivotal_head_unscheduled:  for the indefinite future
pivotal_head_day:  has comments within last day
pivotal_head_week:  has comments within last week 
pivotal_head_month:  has comments within last month  
pivotal_head_none:  has no recent comments
pivotal_head_all:  show everything

pivotal_label_critical:  critical
pivotal_label_bottleneck:  bottleneck
pivotal_label_api:  api
pivotal_label_design:  design
pivotal_label_email:  email
pivotal_label_eol:  eol
pivotal_label_i18n:  translations
pivotal_label_interface:  interface
pivotal_label_lists:  lists
pivotal_label_locations:  locations
pivotal_label_names:  names
pivotal_label_projects:  projects
pivotal_label_search:  searching
pivotal_label_taxonomy:  taxonomy
pivotal_label_voting:  voting
pivotal_label_other:  other
pivotal_label_admin:  admin
pivotal_label_code:  code
pivotal_label_server:  server
pivotal_label_open:  open
pivotal_label_day:  day
pivotal_label_week:  week
pivotal_label_month:  month
pivotal_label_none:  none 
pivotal_label_unscheduled:  "[:pivotal_state_unscheduled]"
pivotal_label_unstarted:  "[:pivotal_state_unstarted]"
pivotal_label_started:  "[:pivotal_state_started]"
pivotal_label_all:  "[:all]"

################################################################################

# LESS POPULAR PAGES

# description/adjust_permissions
adjust_permissions_user_header:  User or Group
adjust_permissions_reader_header:  View
adjust_permissions_writer_header:  "[:EDIT]"
adjust_permissions_admin_header:  "[:ADMIN]"
adjust_permissions_all_users:  All Users
adjust_permissions_site_admin:  site admin


# observer/advanced_search
advanced_search_at_least_one:  Please provide at least one search parameter
advanced_search_caveat:  >
  Advanced search was added in February, 2009 to [:app_title].  There are
  a lot of directions this feature could go.  I have intentionally kept it
  somewhat limited since I am concerned that it may have performance issues
  that result in timeouts.  Please send "email to the
  webmaster":/observer/ask_webmaster_question if you experience timeouts or if
  there are particular types of searches you would like to have added.
  \n\n
  Hints: It's okay to leave some of the fields blank, e.g., if you leave
  'Observer' blank, it will return results by all [:users].
  It matches the exact string given.  Use "OR" (all caps) to tell it to match
  one of several possible strings, e.g. "Xanthoria OR Xanthomendoza".  Use a
  star as a wildcard, e.g. "Wells Gray*Canada" will match "Wells Gray, Canada",
  "Wells Gray Park, Canada", and "Wells Gray Provincial Park, Canada".  (See
  notes under 'Content', too.)

advanced_search_content:  Content
advanced_search_content_help:  Text contained in [:observation] notes or [:comments]
advanced_search_content_notes:  >
  Content search supports full Google syntax, including "OR", double quotes, and negation:\n
  aaa bbb -> contains "aaa" and "bbb" in any order\n
  "aaa bbb" -> contains "aaa" followed immediately by "bbb"\n
  aaa OR bbb -> contains either "aaa" or "bbb"\n
  -aaa -bbb -> reject anything that contains "aaa" or "bbb"\n

advanced_search_location_help:  Where was the mushroom found
advanced_search_name_help:  Name of the mushroom
advanced_search_none_found:  No matches found
advanced_search_observer_help:  Who observed the mushroom
advanced_search_result_type:  Result Type
advanced_search_result_type_help:  >
  Do you want [:observations], [:images] or [:names]/[:descriptions]?


# observer/license_updater
bulk_license_link:  Bulk License Updater


# observer/color_themes
color_themes_text:  >
  **General Concept:** The [:app_title] website provides a number of color
  themes, some based on different groups of mushrooms.  By default the simple
  clean "Black on White" theme is used.  However, a [:user] can choose to use a particular
  theme throughout the site by selecting the theme on the [:user] preference page.
  \n\n
  The idea of using mushrooms for color follows in the tradition of using
  mushrooms to dye fabrics.  Each color in a mushroom theme was pulled from a photograph
  included in the site from the given group.  The colors attempt to express the
  characteristic colors of the group.  In a few cases, the [:images] were adjusted
  using an automatic color balance operation in order to get a more
  characteristic color.
  \n\n
  The following links describe each of the available themes including links to
  the [:images] the colors were extracted from:

color_themes_title:  Color Themes


# name/email_tracking
email_tracking_enabled_only_for:  >
  Enabled only for [name] -- contained taxa not yet supported for [rank].

email_tracking_help:  >
  If you enable tracking then a note will be sent to the email address you have
  provided whenever this name is applied to an [:observation].  A link to this
  page will be given in each tracking email.  You can save your mailing address
  for collections in "your profile":/account/profile.

email_tracking_no_longer_tracking:  No longer tracking [name].
email_tracking_note:  Template for notifying an observer
email_tracking_note_help:  >
  Provide a note template that will be sent as an email or shown to the
  observer when this name is applied to an [:observation].  If you leave it blank,
  then the observer will not be notified.

email_tracking_note_template:  >
  Dear :observer,
  \n\n
  I am currently doing research related to [species_name].
  \n\n
  If possible, please make a dried specimen of any of the mushrooms described
  in :observation and send them to:
  \n\n
  [mailing_address]
  \n\n
  Thanks,
  \n\n
  [users_name]

email_tracking_now_tracking:  Now tracking [name].
email_tracking_title:  Email Tracking for [name]
email_tracking_updated_messages:  Updated tracking messages.


# name/eol_expanded_review_title
eol_expanded_review_title:  EOL Preview
eol_expanded_review_count:  >
  [count] taxa

# name/eol_for_taxon
eol_for_taxon_images:  Images for EOL
eol_for_taxon_observation:  Observation [id]
eol_for_taxon_title:  EOL Review for [name]
eol_for_taxon_voteless_images:  Images with No Votes
eol_for_taxon_voteless_observations:  Observations with No Votes

# name/eol_need_review
eol_need_review_title:  EOL Need Review


# name/eol_preview
eol_preview_name_count:  >
  [count] description(s)

eol_preview_image_count:  >
  [count] image(s)

eol_preview_title:  EOL Preview
eol_preview_explanation:  >
  This page provides links to or shows the content that is currently scheduled
  for delivery to the "Encyclopedia of Life":http://eol.org (EOL).  The
  features related to this effort are still very new and far from polished
  since it has been implemented quickly to meet the immediate needs to develop
  the fungus related content on the EOL.  The content delivered from
  [:app_title] to the EOL will be credited both as coming from the [:app_title]
  website and the individual content providers.
  \n\n
  On this page each section represents one taxon.  The descriptive paragraphs
  for each listed taxon will be sent with the exception of any paragraphs
  marked 'Notes'.  Both the taxa and the images that are being sent have been
  at least quickly reviewed by expert members of the [:app_title]
  community.
  \n\n
  The review status of a specific taxon is given on the page for that taxon and
  can only be set by a designated expert.  Images are selected based on the
  voting history of specific observations and their quality.  Currently only
  designated experts can set the quality level of an image, but this is
  expected to become a open voting process for the entire [:app_title]
  community in the near future.
  \n\n
  Currently the designated experts are either mycology professors that are
  teaching classes that are planning to provide data to EOL through the
  [:app_title] or individuals in the [:app_title] community who have
  shown dedication to the site and are recognized experts in mushroom or fungal
  identification.  All aspect of the process of providing data to EOL are under
  discussion and open to change so please send any questions or comments you
  have to the [:app_title] webmaster.
  \n\n
  The best way to participate in this amazing opportunity is to find a taxon
  you care about and work to expand the descriptive paragraphs for this taxon.


# image/license_updater
image_updater_count:  Count
image_updater_license:  "[:LICENSE]"
image_updater_holder:  "[:COPYRIGHT_HOLDER]"
image_updater_title:  Updating Licenses for [user]
image_updater_update:  "[:UPDATE]"
image_updater_help:  >
  Listed below are all the different licenses you've posted images under, along
  with the number of your images which use that license.  Make any changes you
  want to the license or the name listed as the copyright holder, then click
  "[:UPDATE]" to submit changes.


# interest-related controls in name/show_name, observation/show_observation, etc.
interest_watch:  Watch
interest_ignore:  Ignore
interest_watch_help:  >
  Click here if you want us to send you email whenever there is a change in
  this [object].

interest_ignore_help:  >
  Click here if you want to stop getting any emails about this [object].

interest_default_help:  >
  Click here if you want to go back to the default -- having your account
  preferences determine whether you get email about this [object].

interest_watching:  >
  You have told us to email you about changes in this [object].  Click one
  of the small icons below to change.

interest_ignoring:  >
  You have told us never to email you about changes in this [object].  Click
  one of the small icons below to change.


# interest/list_interests
list_interests_title:  Your Notification Requests
list_interests_turn_on:  Change to Watch
list_interests_turn_off:  Change to Ignore


# location/list_merge_options
list_merge_are_you_sure:  Do merge?  This cannot be undone.
list_merge_options_near_matches:  Near Matches
list_merge_options_others:  Other Available [:locations]
list_merge_options_title:  Merge Options for [where]


# observer/list_notifications
list_notifications_title:  Email Alerts for [user]


# observer/list_users
list_users_joined:  Joined
list_users_contribution:  Contribution


# location/add_to_location
location_merge_success:  Successfully merged [this] with [that].


# species_list/make_report
make_report_not_supported:  We don't support report filetype *.[type].


# description/merge_descriptions
merge_descriptions_title:  Merge [object]
merge_descriptions_merge_header:  Merge with another description
merge_descriptions_move_header:  Move / copy to a synonym
merge_descriptions_merge:  "[:MERGE]"
merge_descriptions_move:  "Move / Copy"
merge_descriptions_merge_or_move:  "Merge / Move / Copy"
merge_descriptions_no_others:  "(there are no other descriptions)"
merge_descriptions_delete_after:  "Delete old description after merge?"
merge_descriptions_merge_help:  >
  This will copy any non-blank sections from the source description into the
  description you select below.  If the target description already has text in
  any of those fields, you will be given an editing form with the text from
  both descriptions.  This will allow you to reconcile any conflicts by hand
  before saving the form and making the merger official.

merge_descriptions_move_help:  >
  This will move the source description into a synonym.  It will just copy it
  if you elect not to delete the old description.  If you wish to merge with an
  existing description in the other name, you must first move your description
  into that name, then select [:show_description_merge] again from there.



# name/bulk_name_edit
name_bulk_help:  >
  Each line indicates a set of changes.
  \n\n
  p(bulk_text). To ensure a name is in the database, just list the name.  E.g.,
  \n\n
  p(bulk_pre). Agaricus bisporus
  \n\n
  p(bulk_text). To ensure a name exists with a particular author, give the name
  followed by the author.  E.g.,
  \n\n
  p(bulk_pre). Agaricus bisporus (J.E. Lange) Pilát
  \n\n
  p(bulk_text). To add a taxon above the species level, give the rank followed
  by the name.  E.g.,
  \n\n
  p(bulk_pre). Order Agaricales
  \n\n
  p(bulk_text). To make a name a deprecated synonym of another name, follow
  the valid name with the deprecated synonym.  E.g.,
  \n\n
  p(bulk_pre). Agaricus bisporus (J.E. Lange) Pilát = Agaricus hortensis (Cke.)
  Imai
  \n\n
  The changes are cumulative, so the last example by itself would ensure that
  the names **__@Agaricus bisporus@__** @(J.E. Lange) Pilát@ and __@Agaricus
  hortensis@__ @(Cke.) Imai@ exist, as well as making __@A. hortensis@__ a
  deprecated synononym of **__@A. bisporus@__**.  If a name exists with no
  author and you provide an author, then the existing name is updated.
  Otherwise, if the author is given and it does not match the current author, a
  new name is created.
  \n\n
  p(bulk_text). You may include an optional one-line comment by inserting it
  after either the accepted or deprecated name, enclosed in square brackets.
  This will be saved in the notes when the name is created.
  \n\n
  p(bulk_pre). Herpothallon Tobler [[citation:Aptroot, A, G Thor, ...]]

name_bulk_label:  Name Edits
name_bulk_success:  All names are now in the database.
name_bulk_title:  Bulk Name Edit


# species_list/name_lister
name_lister_bad_browser:  This page will not work on your browser, sorry!
name_lister_bad_submit:  Invalid commit button '[button]'.
name_lister_charset:  Character Encoding
name_lister_charset_help:  (Try changing this if authors get garbled.)
name_lister_classic:  Classic [:SPECIES_LIST] Generator
name_lister_genera:  Genera
name_lister_help:  >
  *Create List:* Click a genus in the first column to pull up a list of
  species in that genus.  Select any of these taxa and press return or
  double-click to add species to your list.  Accepted names are in boldface;
  deprecated names are followed by one or more accepted alternatives.  You may
  choose any.  To remove a name, select it in the third column, and press
  delete or double-click.  (You may also use arrows to navigate, or type
  partial names to search within a column.)
  \n\n
  *Save List:* When you are finished, click any of the buttons at the bottom
  of the page.  "Create [:species_list]" takes you back to the old creation form,
  where you will be able to enter date, location, notes, etc. before saving the
  list.
  \n\n
  *Reports:* The plain text report gives you a simple list of taxa with no
  formatting.  Rich text can be used to import the list into Microsoft Word
  complete with authors and all the formatting intact.  Spreadsheet produces a
  CSV file, with name, author, citation, and accepted columns.  Common names
  are not available yet.  Reports should automatically download in a separate
  tab or window; if not, go to your browser's File menu and click 'Save As'.

name_lister_names:  Selected
name_lister_no_js:  This page will not work if javascript is disabled.
name_lister_species:  Species
name_lister_submit_csv:  Save as Spreadsheet
name_lister_submit_rtf:  Save as Rich Text
name_lister_submit_spl:  Create [:species_list]
name_lister_submit_txt:  Save as Plain Text
name_lister_title:  Name List Generator


# name/needed_descriptions
needed_descriptions_help:  >
  The following species names are the ones that have the most [:observations], but
  do not have a general description in the [:app_title].  Adding a general
  description to these common species would be a big help.

needed_descriptions_title:  Top 100 Needed Species [:descriptions]


# observer/no_ajax
no_ajax_body:  >
  It looks like your browser is out of date.  You still have access to all of
  the capabilities of this site, however unless you upgrade your browser we
  will not be able to make use of some very useful javascript features that
  modern browsers support.  This includes dynamic forms, auto-completion of
  scientific names and locations, the new version of the [:species_list] creator,
  and more.

no_ajax_browsers:  >
  Browsers that we recommend (and test the site on regularly) are:
  \n\n
  * Firefox / Iceweasel 1.0 or higher
  \n\n
  * Internet Explorer 5.5 or higher
  \n\n
  * Netscape 7.0 or higher
  \n\n
  * Safari 1.2 or higher
  \n\n
  * Opera (we know 8.0 works)
  \n\n
  * Chrome
  \n\n
  If you know that your browser supports AJAX but it's not listed here,
  please "send us an e-mail":/observer/ask_webmaster_question.

no_ajax_dont_care:  >
  If you don't care and you're tired of seeing the "Your Browser is Out of
  Date" tab at the top of every page, "please click
  here":/observer/turn_javascript_off.  (Login and go to preferences to
  re-enable auto-detection.)

no_ajax_title:  Your Browser is Out of Date


# observer/no_browser
no_browser_body:  >
  We have not seen your browser before.  This means we don't know if it
  supports the full capabilities of this site.  Since there are pages that
  won't work if we guess wrong (like voting on [:observation] names), we have to
  assume the worst.  However this means that a number of useful features are
  not available, like dynamic forms, auto-completion of scientific names and
  locations, the new version of the [:species_list] creator, and more.
  \n\n
  If you would like to override this decision, "click here to turn javascript
  on":/observer/turn_javascript_on.  If you are tired of seeing the "We Don't
  Recognize Your Browser" tab at the top of every page, please "click here to
  turn javascript off":/observer/turn_javascript_off.  (Login and go to
  preferences to re-enable auto-detection.)

no_browser_title:  We Don't Recognize Your Browser


# account/no_email
no_email_how_to_reenable:  Go to your "Preferences":/account/prefs page to re-enable this feature.
no_email_some_maybe_queued:  >
  Note: For the next few minutes you may continue to receive emails that have
  already been queued.

no_email_comments_owner_note:  >
  You will no longer receive email notifications when other [:users] of the
  [:app_title] website post [:comments] about your [:observations], names, etc.

no_email_comments_response_note:  >
  You will no longer receive email notifications when other [:users] of the
  [:app_title] website post responses to your [:comments].

no_email_comments_all_note:  >
  You will no longer receive email notifications of all [:comments].

no_email_observations_consensus_note:  >
  You will no longer receive email notifications when the names of your
  [:observations] change.

no_email_observations_naming_note:  >
  You will no longer receive email notifications when other [:users] of the
  [:app_title] website propose names for your [:observations].

no_email_observations_all_note:  >
  You will no longer receive email notifications whenenver [:observations] change.

no_email_names_admin_note:  >
  You will no longer receive email notifications when other [:users] make changes
  to name descriptions you administrate.

no_email_names_author_note:  >
  You will no longer receive email notifications when other [:users] make changes
  to descriptions you have written.

no_email_names_editor_note:  >
  You will no longer receive email notifications when other [:users] make changes
  to descriptions you have edited.

no_email_names_reviewer_note:  >
  You will no longer receive email notifications when other [:users] make changes
  to descriptions you have reviewed.

no_email_names_all_note:  >
  You will no longer receive email notifications about all name changes.

no_email_locations_admin_note:  >
  You will no longer receive email notifications when other [:users] make changes
  to location descriptions you administrate.

no_email_locations_author_note:  >
  You will no longer receive email notifications when other [:users] make changes
  to [:locations] you have created.

no_email_locations_editor_note:  >
  You will no longer receive email notifications when other [:users] make changes
  to [:locations] you have edited.

no_email_locations_all_note:  >
  You will no longer receive email notifications about all location changes.

no_email_general_feature_note:  >
  Automated email about new features has been disabled for your account.

no_email_general_commercial_note:  >
  Other [:users] of the [:app_title] website can no longer send you
  commercial inquiries about your [:images].

no_email_general_question_note:  >
  Other [:users] of the [:app_title] website can no longer send you questions
  about your [:observations].

no_email_comments_owner_success:  "[:comment] notifications disabled for [name]."
no_email_comments_response_success:  "[:comment] response notifications disabled for [name]."
no_email_comments_all_success:  "[:comment] notifications disabled for [name]."
no_email_observations_consensus_success:  Consensus change notifications disabled for [name].
no_email_observations_naming_success:  Name proposal notifications disabled for [name].
no_email_observations_all_success:  "[:observation] notifications disabled for [name]."
no_email_names_admin_success:  Admin name change notifications disabled for [name].
no_email_names_author_success:  Author name change notifications disabled for [name].
no_email_names_editor_success:  Editor name change notifications disabled for [name].
no_email_names_reviewer_success:  Reviewer name change notifications disabled for [name].
no_email_names_all_success:  All name change notifications disabled for [name].
no_email_locations_admin_success:  Admin location change notifications disabled for [name].
no_email_locations_author_success:  Author location change notifications disabled for [name].
no_email_locations_editor_success:  Editor location change notifications disabled for [name].
no_email_locations_all_success:  All location change notifications disabled for [name].
no_email_general_feature_success:  Automated feature email disabled for [name].
no_email_general_commercial_success:  Commercial inquiries disabled for [name].
no_email_general_question_success:  Question email disabled for [name].


# observer/no_javascript
no_javascript_body:  >
  It looks like you have javascript disabled on your browser.  You will still
  have access to all of the capabilities of this site, however unless you
  enable javascript we will not be able to make use of some very useful
  features that modern browsers support.  This includes dynamic forms,
  auto-completion of scientific names and locations, the new version of the
  [:species_list] creator, and more.
  \n\n
  If you would like to turn Javascript on, but aren't sure how, try looking it
  up on google with this search: "How do I enable JavaScript in my
  browser?":http://www.google.com/search?hl=en&q=How+do+I+enable+Javascript+in+my+browser%3F&btnG=Google+Search

no_javascript_dont_care:  >
  If you *do* have javascript enabled, but our auto-detection algorithm is
  failing to detect it correctly, "please click
  here":/observer/turn_javascript_on.  If you don't care and you're tired of
  seeing the "Javascript Disabled" tab at the top of every page, "please click
  here":/observer/turn_javascript_off. (Login and go to preferences to
  re-enable auto-detection.)

no_javascript_title:  You Have Javascript Disabled


# observer/no_session
no_session_body:  >
  It looks like your browser is refusing cookies.  Without cookies, our site
  has no way of remembering who you are from one page to the next.  This means
  that you will not be able to create an account and login, and therefore you
  will not be able to create [:observations], upload [:images], make [:comments], and
  much more.  You will still be able to view everything that the general public
  has access to, but you will just be an observer, you will not be able to
  participate actively.
  \n\n
  All we will do is store a big long number on your computer.  Next time you go
  to our site, we will look up that number and use it to keep track of who you
  are.  (We get multiple requests every second from around the world -- without
  this ID we wouldn't stand a chance of keeping everyone straight!)  This ID is
  encrypted and keeps no sensitive information in it.
  \n\n
  If you would like to turn cookies on, but aren't sure how, try looking it up
  on google with this search: "How do I enable cookies in my
  browser?":http://www.google.com/search?hl=en&q=How+do+I+enable+cookies+on+my+browser%3F&btnG=Google+Search
  Note that most browsers will let you enable cookies for individual sites,
  allowing you to protect your privacy everywhere else.  For example, in
  Firefox, go into Edit -> Preferences -> Privacy Tab -> Exceptions.

no_session_title:  You Have Cookies Disabled



# observer/refine_search
refine_search_title:  "Refine [TYPE] Search"
refine_search_query:  Query
refine_search_model:  Data type
refine_search_flavor:  Basic flavor
refine_search_order:  Sort order
refine_search_num_results:  Matches
refine_search_joins:  Joined tables
refine_search_success:  Modified query now matches [num] objects.
refine_search_goto_index:  "[:show_object(type=:index)]"
refine_search_conditions:  Parameters
refine_search_unknown_object:  "Unknown [TYPE] #[id]"
refine_search_help:  "[[Help]]"
refine_search_max_size:  Max Size

refine_search_advanced_search_content:  "[:refine_search_pattern_search]"
refine_search_advanced_search_location:  "[:Location]"
refine_search_advanced_search_name:  "[:Name]"
refine_search_advanced_search_user:  "[:Observer]"
refine_search_all_children:  Which children?
refine_search_all_children_false:  only immediate children
refine_search_all_children_true:  all children
refine_search_author_has:  Search authority
refine_search_children_names:  Restrict to children of these
refine_search_citation_has:  Search citation
refine_search_classification_has:  Search classification
refine_search_comment_types:  Object type(s)
refine_search_comments_has:  Search comments
refine_search_confidence:  Confidence level
refine_search_content_has:  Search message body
refine_search_content_types:  Original image type(s)
refine_search_copyright_holder_has:  Search copyright holder
refine_search_created:  Date created
refine_search_date_image:  Date taken
refine_search_date_observation:  Date observed
refine_search_date_species_list:  Date of list
refine_search_deprecated:  Include deprecated names?
refine_search_deprecated_either:  doesn't matter
refine_search_deprecated_no:  only approved names
refine_search_deprecated_only:  only deprecated names
refine_search_desc_content:  Search description text
refine_search_desc_creator:  Description creator
refine_search_desc_project:  Draft for project
refine_search_desc_type:  Description type
refine_search_desc_type_foreign:  foreign
refine_search_desc_type_project:  draft
refine_search_desc_type_public:  public
refine_search_desc_type_source:  other
refine_search_desc_type_user:  personal
refine_search_has_author:  Has an authority?
refine_search_has_citation:  Has a citation?
refine_search_has_classification:  Has classification?
refine_search_has_comments:  Does it have comments?
refine_search_has_has_default_desc:  Has a default description?
refine_search_has_images:  Does it have images?
refine_search_has_location:  Does it a defined location?
refine_search_has_name:  Does it have a name?
refine_search_has_notes:  Does it have notes?
refine_search_has_observation:  Does it have an observation?
refine_search_has_specimen:  Is a specimen available?
refine_search_has_synonyms:  Has synonyms?
refine_search_has_votes:  Does it have votes?
refine_search_include_admin:  Include pseudo-observations?
refine_search_is_col_loc:  Was this where it was seen?
refine_search_is_deprecated:  Is deprecated?
refine_search_join_desc:  Which descriptions to search?
refine_search_join_desc_any:  all descriptions
refine_search_join_desc_default:  default only
refine_search_license:  "[:License]"
refine_search_location_defined:  Location (defined)
refine_search_location_undefined:  Location (undefined)
refine_search_locations:  Restrict to these location(s)
refine_search_misspellings:  Include misspellings?
refine_search_misspellings_either:  doesn't matter
refine_search_misspellings_no:  only correct names
refine_search_misspellings_only:  only misspelt names
refine_search_model_flavor:  Query flavor
refine_search_modified:  Date last modified
refine_search_name:  Species name
refine_search_names:  Restrict to these species
refine_search_nonconsensus:  Include "other" observations?
refine_search_nonconsensus_all:  use any proposed name
refine_search_nonconsensus_exclusive:  only nonconsensus names
refine_search_nonconsensus_no:  just use consensus name
refine_search_notes_has:  Search notes
refine_search_ok_for_export:  Okay for export?
refine_search_pattern_comment:  "[:refine_search_pattern_search]"
refine_search_pattern_image:  "[:refine_search_pattern_search]"
refine_search_pattern_location:  "[:refine_search_pattern_search]"
refine_search_pattern_name:  "[:refine_search_pattern_search]"
refine_search_pattern_observation:  "[:refine_search_pattern_search]"
refine_search_pattern_project:  "[:refine_search_pattern_search]"
refine_search_pattern_search:  Search string
refine_search_pattern_species_list:  "[:refine_search_pattern_search]"
refine_search_pattern_user:  "[:refine_search_pattern_search]"
refine_search_quality:  Image quality
refine_search_rank:  "[:Rank]"
refine_search_rss_log_type:  Type of object
refine_search_rss_modified:  Date of last activity
refine_search_size:  Available sizes
refine_search_species_lists:  Belongs to these species list(s)
refine_search_summary_has:  Search message summary
refine_search_synonym_names:  Restrict to synonyms of these
refine_search_synonyms:  Include synonym observations?
refine_search_synonyms_all:  this name and synonyms
refine_search_synonyms_exclusive:  only synonyms
refine_search_synonyms_no:  just this name
refine_search_text_name_has:  Search taxon name
refine_search_title_has:  Search title
refine_search_users:  Restrict to these user(s)

refine_search_advanced_search_content_help:  >
  Search text of observations' notes and comments. [:refine_search_google_help]

refine_search_advanced_search_location_help:  >
  Where the mushroom was found. [:refine_search_locations_help]

refine_search_advanced_search_name_help:  >
  Name of the mushroom.  [:refine_search_names_help]

refine_search_advanced_search_user_help:  >
  Who observed the mushroom.  [:refine_search_users_help]

refine_search_all_children_help:  >
  Should we include all taxa below the name given above, or just immediate
  children?  For example, immediate children of a Agaricus would be all the
  species in Agaricus, but not subspecies or varieties.

refine_search_author_has_help:  >
  [:refine_search_google_help]

refine_search_children_names_help:  >
  [:refine_search_multiple_help(things="names")]  It will include results for
  both the names given and their children (e.g., species in a genus).

refine_search_citation_has_help:  >
  [:refine_search_google_help]

refine_search_classification_has_help:  >
  [:refine_search_google_help]

refine_search_comment_types_help:  ""
refine_search_comments_has_help:  >
  [:refine_search_google_help]

refine_search_content_has_help:  >
  [:refine_search_google_help]

refine_search_conditions_help:  >
  Use the following conditions to narrow down your query results.  Only the
  fields in boldface are required (if any).  Results must match all of the
  conditions that are not left blank.  Many of the conditions accept a range or
  allow multiple values.  Syntax can be complicated; click on the
  [:refine_search_help] tags next to the fields for pointers on what kind of
  values are accepted.

refine_search_confidence_help:  >
  This refers to the average confidence of the community to the current
  consensus name of the observation.

refine_search_content_types_help:  >
  All reduced sizes are JPEGs.  This only applies to the original image.  Most
  users upload JPEGs, however a small percentage are in other formats.

refine_search_copyright_holder_has_help:  ""
refine_search_created_help:  >
  [:refine_search_time_help]

refine_search_date_help:  >
  Enter a year or year range (e.g., "2008"), month or month range (e.g.,
  "Dec" or "March"), or a full or partial date or range in
  "YYYY-MM-DD" format (e.g., "2008-03" or "2008-03-31").

refine_search_date_image_help:  >
  Date the photograph was taken.  [:refine_search_date_help]

refine_search_date_observation_help:  >
  Date the mushroom was observed.  [:refine_search_date_help]

refine_search_date_species_list_help:  >
  Date of the species list, not necessarily when it was first created.  The
  meaning of this date may vary from list to list.  In some lists it may not
  have any meaning at all.  [:refine_search_date_help]

refine_search_deprecated_help:  ""
refine_search_desc_content_help:  >
  Searches all the text fields of the description.
  [:refine_search_google_help]

refine_search_desc_creator_help:  >
  Restrict to names with descriptions created by these user(s).

refine_search_desc_project_help:  >
  Restrict to names with drafts for these project(s).

refine_search_desc_type_help:  >
  Restrict to names with descriptions of these type(s).

refine_search_google_help:  >
  Enter one word or phrase at a time.  Each time you update the form you will
  see all the previous entries, and you will get another empty field.  Records
  must match each line you have filled in.  If you enter a minus sign as the
  first letter, it will require that the subsequent word or phrase NOT be
  present, e.g., "-Joe Public".  You may list alternatives with the special
  word "OR" in all caps, e.g., "red OR pink OR orange".  Records must contain
  at least one of these alternatives.  Unlike on the google search bar,
  double-quotes are unnecessary for grouping words into a phrase here.  For
  example, this does what you'd expect: "Agaricus sp. OR Leucoagaricus sp.".

refine_search_has_author_help:  ""
refine_search_has_citation_help:  ""
refine_search_has_classification_help:  ""
refine_search_has_comments_help:  ""
refine_search_has_has_default_desc_help:  ""
refine_search_has_images_help:  ""
refine_search_has_location_help:  ""
refine_search_has_name_help:  ""
refine_search_has_notes_help:  ""
refine_search_has_observation_help:  ""
refine_search_has_specimen_help:  ""
refine_search_has_synonyms_help:  ""
refine_search_has_votes_help:  ""
refine_search_include_admin_help:  >
  Some observations are created just to fill out species lists.  These "fake"
  observations have no votes, images, notes, location, comments, or anything.
  By default they are excluded from search results.

refine_search_is_col_loc_help:  ""
refine_search_is_deprecated_help:  ""
refine_search_join_desc_help:  >
  The fields below require that names be joined with their descriptions.  There
  are two ways this can be done: (1) You may join with just the default
  description, in which case the following fields will only apply to the
  default description and will automatically restrict the results to names that
  actually have a default description.  (2) You may also join with all of a
  name's descriptions, in which case the following fields can apply to any
  description.  This will only restrict the results to names that have
  descriptions, not just names with a default one.

refine_search_license_help:  ""
refine_search_location_defined_help:  >
  Enter name or id of a location.  This will only include results that belong
  to a DEFINED location. [:refine_search_location_apology(other=undefined)]
  [:refine_search_location_help]

refine_search_location_undefined_help:  >
  Enter name of a location.  This will only include results that DO NOT belong
  to a defined location. [:refine_search_location_apology(other=defined)]
  [:refine_search_location_help]

refine_search_locations_help:  >
  Includes both defined or undefined locations.
  [:refine_search_multiple_help(things="location_names")]
  [:refine_search_location_help]

refine_search_location_help:  >
  Use "*" as a wildcard.  Punctuation and case is ignored, but abbreviations
  must be correct if included.  For example "Marin County, CA" will NOT match
  "Marin Co., California".  However, "marin co california" and
  "Marin*California" will.

refine_search_location_apology:  >
  Sorry, you must use a different flavor of query to search for results that
  belong to [other] locations.  A good starting point is
  '[:app_list_locations]' in the left-hand panel.

refine_search_misspellings_help:  >
  Use this parameter to tell it how to deal with misspellings.  All name
  queries accept this parameter.  By default it screens out misspellings
  ("[:refine_search_misspellings_no]"), however you can ask it to return both
  ("[:refine_search_misspellings_either]") or only misspelt ones
  ("[:refine_search_misspellings_only]").

refine_search_model_flavor_help:  >
  These are all of our basic query flavors.  The names might be a bit obscure.
  It might be easier to go browsing around normally until you find a query
  that is close to what you want and refine that query instead.  Another
  option is to select one of the unconstrained queries like "all observations"
  or "all images" as good starting points.

refine_search_modified_help:  >
  [:refine_search_time_help]

refine_search_multiple_help:  >
  List one or more [things].  Either enter them one at a time on separate
  lines, updating the form after each one, or enter several at once on the same
  line, separated by the special word "OR".

refine_search_name_help:  >
  Enter the name the query is based on.  If this is an "observations of
  children of a given name" query, this is the "given name" whose children it
  uses.  This can be any rank, but must resolve to a single name.  In the case
  of ambiguity, it takes the first one it finds.  Update the form to see which
  name it chooses.

refine_search_names_help:  >
  [:refine_search_multiple_help(things="names")] You can enter any rank, not
  just species, e.g.  "A*muscaria*flavivolvata" or "Agaricales".  Note,
  however, that listing higher taxa returns those taxa only, not the children
  of it.  Thus Agaricus returns only Agarcius, not the species of Agaricus.

refine_search_nonconsensus_help:  >
  Use this parameter to tell it how to deal with alternate proposed names for
  observations.  By default it only considers the consensus name
  ("[:refine_search_nonconsensus_no]"), however you can tell it to include all
  proposed names ("[:refine_search_nonconsensus_all]") or JUST the alternates
  ("[:refine_search_nonconsensus_exclusive]").

refine_search_notes_has_help:  >
  [:refine_search_google_help]

refine_search_ok_for_export_help:  ""
refine_search_pattern_comment_help:  >
  Searches both summary and content.
  [:refine_search_google_help]

refine_search_pattern_image_help:  >
  Searches image notes, copyright holder, location and species name(s).
  [:refine_search_google_help]

refine_search_pattern_location_help:  >
  Searches name and default description (if exists).
  [:refine_search_google_help]

refine_search_pattern_name_help:  >
  Searches name, author, citation, notes, and default description (if exists).
  [:refine_search_google_help]

refine_search_pattern_observation_help:  >
  Searches name, location, and notes (but not comments).
  [:refine_search_google_help]

refine_search_pattern_project_help:  >
  Searches title and summary notes.
  [:refine_search_google_help]

refine_search_pattern_species_list_help:  >
  Searches title, location and notes.
  [:refine_search_google_help]

refine_search_pattern_user_help:  >
  Searches login and name only.
  [:refine_search_google_help]

refine_search_quality_help:  ""
refine_search_rank_help:  ""
refine_search_rss_log_type_help:  ""
refine_search_rss_modified_help:  >
  [:refine_search_time_help]

refine_search_size_help:  >
  Restrict to images of a minimum size.  You may also indicate a maximum size,
  although in practice this is less useful.

refine_search_species_lists_help:  >
  [:refine_search_multiple_help(things="titles")] Use "*" for a wildcard.  You
  may also enter partial titles.

refine_search_summary_has_help:  >
  [:refine_search_google_help]

refine_search_synonym_names_help:  >
  [:refine_search_multiple_help(things="names")]

refine_search_synonyms_help:  >
  Use this parameter to tell it how to deal with synonyms of the name given
  above.  By default it includes observations of synonyms
  ("[:refine_search_synonyms_all]"), however you can tell it to ignore synonyms
  ("[:refine_search_synonyms_no]") or include JUST synonyms
  ("[:refine_search_synonyms_exclusive]").  Note that for this purpose,
  misspelt names are treated exactly the same as the correctly-spelled name.

refine_search_text_name_has_help:  >
  [:refine_search_google_help]

refine_search_title_has_help:  >
  [:refine_search_google_help]

refine_search_time_help:  >
  Enter a date or date range in the format "YYYY-MM-DD HH:MM:SS".  Enter only
  as many figures as you want, starting with year.  Example: "2010-01" or
  "2010-1-31 1am".

refine_search_users_help:  >
  [:refine_search_multiple_help(things="names")] Use "*" for a wildcard.



# observer/textile
sandbox_enter:  Enter Textile you wish to test here
sandbox_header:  >
  This page let's you play with the textile markup language.  Click 'Test' to
  see what your markup looks like.  You will need to copy the results from this
  page to where ever you want to use it.

sandbox_link1:  Another quick reference and sandbox for testing syntax.
sandbox_link2:  More than anyone could ever want to know.
sandbox_link3:  Homepage of the original author, Dean Allen.
sandbox_look_like:  This is what it will look like
sandbox_quick_ref:  Quick Reference
sandbox_sample:  >
  __italics__        trademark(tm)  \\n
  **boldface**       copyright(c)    | (must follow letters, not punctuation)\n
  +underline+        registered(r)  /\n
  @monospace@\n
  ^superscript^      1.6 &amp;micro;m  ->  1.6 &micro;m\n
  ~subscript~        34&amp;deg;17' N  ->  34&deg;17' N\n
  \n
  "External Link":http://google.com\n
  !http://random.com/image.jpg!\n
  \n
  Internal links:\n
  _name 371, _Amanita ocreata_, or _A. ocreata_\n
  _location 382_, _location Mt. Wilson_\n
  _user 252_, _user jason_\n
  _observation 12345_\n
  _image 12345_, !image 12345!, or !image 640/12345!\n
  _comment 12345_\n
  \n
  Include footnote[[1]] references after any word[[2]].\n
  \n
  fn1. And then define the footnote at the bottom.\n
  \n
  fn2. Be sure to leave blank lines around these "xx." directives.\n
  \n
  h1. Header\n
  \n
  bq. Block quote or indent a paragraph.\n
  \n
  * bullet list item 1\n
  * bullet list item 2\n
  \n
  # numbered list item 1\n
  # numbered list item 2\n
  \n
  Tables are useful for comparing species:\n
  | Species 1 | value 1.1 | value 1.2 |\n
  | Species 2 | value 2.1 | value 2.2 |\n
  | Species 3 | value 3.1 | value 3.2 |\n

sandbox_test:  Test
sandbox_test_codes:  Show HTML
sandbox_title:  Textile Sandbox
sandbox_web_refs:  Web References


# interest/set_interest
set_interest_already_deleted:  You have expressed no interest in [name].
set_interest_already_off:  You have already told us to ignore [name].
set_interest_already_on:  You have already told us to watch [name].
set_interest_bad_object:  "Object [type] #[id] doesn't exist."
set_interest_failure:  >
  Could not save changes.  Please try again or report this to the webaster.

set_interest_success_was_off:  Cancelled your ban on emails about [name].
set_interest_success_was_on:  Cancelled your request for emails about [name].
set_interest_success_off:  We will now ignore any changes in [name].
set_interest_success_on:  You will now be notified of any changes in [name].
set_interest_user_mismatch:  Another [:user] is logged on at this machine.  Please log them off, log back in as you, and try again.


# observer/show_notifications
show_notifications_title:  New Notifications for [user]


# observer/<Theme>
theme_agaricus:  _Agaricus_ Theme
theme_agaricus_augustus:  "[link] is used for the left-hand panel's background color."
theme_agaricus_campestris:  "[link] is used for the primary background and the default link hover background color."
theme_agaricus_cupreobrunneus:  "[link] is used for the default text color and the visited link color."
theme_agaricus_lilaceps:  "[link] is used for the background color for the some rows on the list pages and the unvisited link color for the other rows."
theme_agaricus_semotus:  "[link] is used for the banner background color."
theme_agaricus_subrufescens:  "[link] is used for most unvisited links."
theme_agaricus_xanthodermus:  "[link] is used for the background color for some rows on the list pages and the unvisited link color for the other rows."

theme_amanita:  _Amanita_ Theme
theme_amanita_calyptroderma:  "[link] is used for all the colors of half the rows on the list pages."
theme_amanita_muscaria:  "[link] is used for the banner background and text, the default visited link and link hover colors as well as the text for the left-hand panel."
theme_amanita_pachycolea:  "[link] is used for the primary background, the default text and default unvisited links."
theme_amanita_phalloides:  "[link] is used for all the colors of the other half of the rows on the list pages."
theme_amanita_velosa:  "[link] is used for the left-hand panel's background color and the left-hand panel's visited and unvisited link colors."

theme_cantharellaceae:  _Cantharellaceae_ Theme
theme_cantharellaceae_californicus:  "[link] is used for the primary, banner and left-hand panel backgrounds."
theme_cantharellaceae_cinnabarinus:  "[link] is used for the default link and visited link colors."
theme_cantharellaceae_cornucopioides:  "[link] is used for the default text and all the colors of half the rows on the list pages."
theme_cantharellaceae_tubaeformis:  "[link] is used for all the colors of the other half of the rows on the list pages."

theme_hygrocybe:  _Hygrocybe_ Theme
theme_hygrocybe_conica:  "[link] is used for the default text and all the colors of half the rows on the list pages."
theme_hygrocybe_miniata:  "[link] is used for the left-hand panel background and link text colors."
theme_hygrocybe_pittacina:  "[link] is used for the default link text colors."
theme_hygrocybe_punicea:  "[link] is used for the default background color, the banner background color, and all the colors of the other half of the rows on the list pages."

theme_random:  Random
theme_list:  List of Themes

theme_black_on_white:  Black on White Theme
theme_black_on_white_description:  >
  This is a simple Black on White theme that attempts to be as readable and clean as possible.
  The logo colors come from the [link] theme.

theme_switch:  'To select this as your theme, go to your "preferences":/account/prefs and select [theme] as your Preferred Theme'

Agaricus:  Agaricus
Amanita:  Amanita
Cantharellaceae:  Cantharellaceae
Hygrocybe:  Hygrocybe
BlackOnWhite:  Black on White

# observer/translators_note
translators_note:  >
  Please help us make this website available around the world!  It's easy.
  There is somewhere around 1600 lines or 11000 words of text on this site at
  the moment, but don't let that scare you.  We've organized it so someone with
  limited time can concentrate on just the first few sections, and get the most
  commonly-used text done first.  Then as time and energy permits, they or
  someone else can continue working down the list until one day it is all
  finished.  Please feel free to pick up a copy of the "translation
  files":[repo] and start plugging away in any language you wish.  Then just
  "pop us an email":/observer/ask_webmaster_question when you finish doing what
  you can, and we'll tell you how to submit your work.  You will receive
  prominant credit for your contribution, in addition to, of course, our
  undying gratitude.

translators_note_title:  Translator's Note


# observer/turn_javascript_nil
turn_javascript_nil_body:  We will resume auto-detection of the state of javascript.
turn_javascript_nil_title:  Auto-Detect Javascript


# observer/turn_javascript_off
turn_javascript_off_body:  We will now ignore javascript.
turn_javascript_off_title:  Turn Javascript Off


# observer/turn_javascript_on
turn_javascript_on_body:  We will now assume javascript is on.
turn_javascript_on_title:  Turn Javascript On


# account/create_alert and show_alert
user_alert_create_title:  Edit User Alert for [user]
user_alert_created:  Created on
user_alert_create_alert:  Create/Edit User Alert
user_alert_delete:  Delete
user_alert_deleted:  Deleted alert for [user].
user_alert_later:  Later
user_alert_later_help:  Not now! Remind me to look into it again tomorrow.
user_alert_missing:  Tried to show you an alert that no longer exists, sorry.
user_alert_missing_type:  Please select an alert type.
user_alert_next_showing:  Next showing
user_alert_notes:  Other notes
user_alert_okay:  Okay
user_alert_okay_help:  Click here if you don't want to see this message again.
user_alert_save:  Save
user_alert_saved:  Saved alert for [user].
user_alert_show_title:  Alert for [user]
user_alert_type:  Alert type
user_alert_type_bounced_email:  email is bouncing
user_alert_type_other:  other
user_alert_user:  Created by
user_alert_message_bounced_email:  >
  Hi [login],\n\n
  We've noticed that email to your address is bouncing.\n\n
  Please check the address we're using and make sure it is correct.\n\n
  Email: [email]\n\n
  "Click here to change it.":/account/prefs\n\n
  [notes]

user_alert_message_other:  "[notes]"

################################################################################

# ADMIN-TYPE PAGES

# project/add_members
add_members_change_status:  Change Status
add_members_denied:  >
  Permission denied: only admins for a project can add new members.

add_members_title:  Add [:users] to [title]


# project/add_project
add_project_already_exists:  A project named '[title]' already exists.
add_project_group_exists:  >
  Unable to create project because a [:user_group] named '[group]' already exists.

add_project_need_title:  Projects must have a title.
add_project_success:  Project was successfully created.
add_project_title:  Create New Project


# account/add_user_to_group
add_user_to_group_already:  "[user] is already a member of [group]."
add_user_to_group_group:  Group name
add_user_to_group_no_group:  Unable to find the group, '[group]'.
add_user_to_group_no_user:  Unable to find the [:user], '[user]'.
add_user_to_group_success:  "[user] added to [group]."
add_user_to_group_title:  Add [:user] to Group
add_user_to_group_user:  "[:user] name"


# admin_request/author_request emails
admin_request_change_member_status:  Change [:user]'s status
admin_request_success:  Successfully sent admin request for [title]
admin_request_title:  Admin Request for [title]
author_request_add_author:  Make sender an author
author_request_title:  Authorship Request for [title]
request_message:  Message
request_show_user:  Show details on sender
request_subject:  Subject
request_success:  Delivered email.


# project/change_member_status
change_member_status_admins:  Current Project Admins
change_member_status_change_status:  Change Status
change_member_status_edit:  Edit Project
change_member_status_make_admin:  Make Admin
change_member_status_make_admin_help:  >
  Make Admin - Allows [:user] to perform admin functions.  They will be able to
  add or remove members, change the ability for other members to perform admin
  functions, and edit any draft names for this project.  [:user] is also made a
  member of the project if they are not already.

change_member_status_make_member:  Make Regular Member
change_member_status_make_member_help:  >
  Make Regular Member - Ensures that [:user] is a member of the project, but not
  in the admin group. Afterwords the [:user] will be able to view and create
  draft names for this project.  They will be the only non-admin members able
  to edit their drafts.

change_member_status_members:  Current Project Members
change_member_status_remove_member:  Remove Member
change_member_status_remove_member_help:  >
  Remove Member - Removes all member and admin priviledges for a project.  [:user]
  will no longer be able view or create draft names for this project.  They
  will not be able to perform any admin functions.

change_member_status_denied:  >
  Only the admins for a project can change member permissions.

change_member_status_title:  Changing [:user] Status of [name] for [title]


# observer/change_user_bonuses
change_user_bonuses_title:  Contribution Bonuses for [user]
change_user_bonuses:  Award Bonus
change_user_bonuses_help:  >
  List one bonus per line, each specifiying a number of points and reason, like
  this:
  \n\n
  10000 German translations\n
  50000 Expert in hypogeous fungi\n
  \n\n
  These will appear on the show_user page below the usual contribution scores.
  Keep the reasons short or it might mess up the formatting of the table on
  that page.


# project/destroy_project
destroy_project_failed:  Failed to destroy project.
destroy_project_success:  Project destroyed.


# project/edit_project
edit_project_destroy:  "[:destroy_object(type=:project)]"
edit_project_title:  "[:edit_object(type=:project)]: [title]"


# project/_form_projects
form_projects_title:  "[:Title]"


# project/list_projects
list_projects_title:  "[:list_objects(type=:project)]"
list_projects_add_project:  "[:add_object(type=:project)]"


# draft/publish_draft
publish_draft_denied:  >
  Permission denied: Only the creator of a draft or a project admin can publish
  a draft.


# observer/refresh_vote_cache
refresh_vote_cache:  Refreshed vote caches.


# project/review_authors
review_authors_add_author:  Add
review_authors_authors:  Current [:description] Authors
review_authors_denied:  >
  Only existing authors and reviewers can change the description authors.

review_authors_note:  >
  This page changes the recorded author(s) of a taxon description on the
  [:app_title] website.  This is in no direct way related to the original
  publishing author of the taxon.

review_authors_review_authors:  Review Authors
review_authors_other_users:  Other [:users]
review_authors_remove_author:  Remove
review_authors_title:  Reviewing Author(s) for [name]


# observer/send_feature_email
send_feature_email_success:  Delivered feature mail.
send_feature_email_denied:  Only the admin can send feature mail.


# project/show_project
show_project_add_members:  Add Members
show_project_admin_group:  Admin Group
show_project_admin_request:  Admin Request
show_project_by:  Owned By
show_project_created:  Created
show_project_destroy:  Destroy Project
show_project_drafts:  Drafts
show_project_edit:  Edit Project
show_project_published:  Reviewed Published Names
show_project_summary:  Summary
show_project_title:  "Project: [title]"
show_project_user_group:  User Group


# observer/users_by_name
users_by_name_title:  Users by Name
users_by_name_created:  Created
users_by_name_groups:  Groups
users_by_name_id:  ID
users_by_name_last_login:  Last login
users_by_name_login:  Login
users_by_name_name:  Name
users_by_name_theme:  Theme
users_by_name_verified:  Verified


# support/create_donation
create_donation_title:  Record Mushroom Observer Donation
create_donation_not_allowed:  Only admins can record donations
create_donation_add:  Add
create_donation_tab:  Record Donation


# support/review_donations
review_donations_title:  Review All Donations
review_donations_not_allowed:  Only admins can review donations
review_donations_update:  Update
review_donations_tab:  Review Donations
review_reviewed:  Reviewed
review_id:  Id
review_who:  Who
review_anon:  Anon
review_amount:  Amount
review_email:  Email

################################################################################

# EMAIL MESSAGES

# Subject lines.
email_subject_comment:  "[:COMMENT] About [name]"
email_subject_commercial_inquiry:  Commercial Inquiry About [Name]
email_subject_consensus_change:  Consensus Changed from [old] to [new]
email_subject_denied:  "[:USER] Creation Blocked"
email_subject_features:  New [:app_title] Features
email_subject_location_change:  "[name] Has Been Changed"
email_subject_naming_for_observer:  Research Request
email_subject_naming_for_tracker:  Naming Notification
email_subject_name_change:  "[name] Has Been Changed"
email_subject_name_proposal:  "[:OBSERVATION] #[id] May Be [name]"
email_subject_new_password:  New Password
email_subject_observation_change:  "[:OBSERVATION] Changed, [name]"
email_subject_observation_destroy:  "[:OBSERVATION] Destroyed, [name]"
email_subject_observation_question:  Question About [name]
email_subject_publish_name:  Name Published
email_subject_verify:  Email Verification
email_subject_webmaster_question:  Question From [user]

# Field labels in the "object_change" emails.
email_field_added_images:  Added image(s)
email_field_changed_thumbnail:  Changed thumbnail
email_field_collection_location:  Specimen _was_ collected at this location
email_field_collection_not_location:  Specimen _was not_ collected at this location
email_field_east:  "[:East] edge"
email_field_image_count:  "[:Image] count"
email_field_new_name:  New [:name]
email_field_no_specimen_available:  Specimen is no longer available
email_field_north:  "[:North] edge"
email_field_old_name:  Old [:name]
email_field_published:  Published by
email_field_removed_images:  Removed image(s)
email_field_south:  "[:South] edge"
email_field_specimen_available:  Specimen is now available
email_field_west:  "[:West] edge"

# This is used like this: "<Label>: <old_value> changed to <new_value>"
email_field_is_now:  changed to

# "Helpful" links at the bottom of the email.
email_links_change_prefs:  Change your preferences
email_links_disable_tracking:  Disable tracking for this [type]
email_links_email_publisher:  Send email to the publisher
email_links_latest_changes:  Latest changes at [:app_title]
email_links_not_interested:  I'm not interested in this [type]
email_links_post_comment:  Post a [:comment]
email_links_show_object:  Show this [type]
email_links_show_user:  Show [:user]'s profile
email_links_show_observer:  Show [:observer]'s profile
email_links_show_identifier:  Show [:identifier]'s profile
email_links_stop_sending:  Stop sending me email like this
email_links_your_interests:  Review your [:notifications]

# Some other common phrases and sections.
email_can_respond:  >
  It is entirely up to you whether you want to reply to [name] ([email]) by
  replying directly to this email.

email_handy_links:  "Here are some handy links:"
email_no_respond:  Please do not reply to this email!
email_report_abuse:  >
  If you feel this user is abusing this service please forward this entire
  email message to: [email]

email_respond_via_comment:  >
  Use the link below to respond via your own public comment.

email_welcome:  Welcome, [user]


# Main message contents.
email_admin_request_intro:  >
  h2. *Admin Request*
  \n\n
  [user] ([email]) asked the [:app_title] website to forward the
  following request to you regarding [project]:

email_author_request_intro:  >
  h2. *Author Request*
  \n\n
  [user] ([email]) asked the [:app_title] website to forward the
  following request to you regarding [object]:

email_comment_intro_other:  >
  h2. *Comment on [Type]*
  \n\n
  The following comment was posted on the [:app_title] website
  regarding the [type] <u>[name]</u>:

email_comment_intro_response:  >
  h2. *Comment Response*
  \n\n
  The following comment was posted on the [:app_title] website in response
  to your comment regarding the [type] <u>[name]</u>:

email_comment_intro_to_owner:  >
  h2. *Comment on Your [Type]*
  \n\n
  The following comment was posted on the [:app_title] website
  regarding your [type] <u>[name]</u>:

email_commercial_intro:  >
  h2. *Commercial Inquiry*
  \n\n
  [user] ([email]) asked the [:app_title] website to forward the
  following commercial inquiry to you about your image [image]:

email_consensus_change_intro:  >
  h2. *Consensus Change*
  \n\n
  Consensus has changed for observation #[id]:

email_features_intro:  >
  h2. *New Features*
  \n\n
  The following new features have been released at the [:app_title] website:

email_location_merge:  >
  User [user] wants to merge the location [this] into [that].

email_name_merge:  >
  User [user] wants to merge the name [this] into [that].

email_name_proposal_intro:  >
  h2. *Name Proposal*
  \n\n
  A name was proposed for observation #[id]:

email_naming_for_observer_intro:  >
  h2. *Research Request*
  \n\n
  [user] ([email]) asked the [:app_title] website to forward the
  following message to you about your [type] <u>[name]</u>:

email_naming_for_tracker_intro:  >
  h2. *Tracking Alert*
  \n\n
  An [obs] on the [:app_title] website has been given the name [name], which
  you are currently tracking.  You can contact either the [:observer] or the
  [:identifier] by going to the appropriate link below and clicking the email
  link near the top of the page.

email_new_password_intro:  >
  h2. *New Password*
  \n\n
  Your new [:app_title] password is:

email_new_password_what_now:  >
  Once you have logged in, you should change your password to something easier
  to remember by going to the '[:app_preferences]' page.

email_object_change_intro:  >
  h2. *[Type] was Changed*
  \n\n
  There were change(s) made to the [type] <u>[name]</u>:

email_object_new_intro:  >
  h2. *[Type] was Created*
  \n\n
  The [type] <u>[name]</u> was created.

email_object_change_reason_all:  >
  You received this email because you have requested to be notified when any
  [type] changes.

email_object_change_reason_admin:  >
  You received this email because you are an admin for a description of the
  changed [type].

email_object_change_reason_editor:  >
  You received this email because you have edited a description of the changed
  [type].

email_object_change_reason_author:  >
  You received this email because you are an author of a description of the
  changed [type].

email_object_change_reason_reviewer:  >
  You received this email because you reviewed a description of this [type].

email_object_change_reason_interest:  >
  You received this email because you expressed interest in this [type].

email_observation_destroyed_intro:  >
  h2. *Observation Destroyed*

email_observation_question_intro:  >
  h2. *Question from Another User*
  \n\n
  [user] ([email]) asked the [:app_title] website to forward the
  following question to you about your observation <u>[name]</u>:

email_publish_name_intro:  >
  h2. *Draft of Name Has Been Published*
  \n\n
  A description of a name has been published on the [:app_title] website.
  You are receiving this email since you are listed as either an author for
  this taxon or as a reviewer on the site.

email_user_question_intro:  >
  h2. *Question from Another User*
  \n\n
  [user] ([email]) asked the [:app_title] website to forward the
  following email to you:

email_verify_intro:  >
  h2. *Hello [user]*
  \n\n
  Please click the following link to verify that you received this email and
  activate your [:app_title] account:
  \n\n
  [link]

################################################################################

# INTRO PAGE

# observer/intro
intro_title:  Introduction
intro_purpose:  >
  *Purpose:* The purpose of this site is to record observations about
  mushrooms, help people identify mushrooms they aren't familiar with, and
  expand the community around the scientific exploration of mushrooms
  (mycology).  Some have asked what counts as a mushroom.  This site takes a
  very broad view.  While the emphasis is on the large fleshy fungi, other
  fungi such as lichens, rust and molds as well as fungus-like organisms such
  as slime-molds are all welcome.  Ultimately, I hope this site will become a
  valuable resource for both amateur and professional mycologists.  I like to
  think of it as a living field guide for mushrooms or a collaborative mushroom
  field journal.
  \n\n
  For those new to mycology, there is a huge amount of basic research that
  still needs to be done.  By some estimates less that 5% of the world's
  species of fungi are known to science.  While things are slightly better for
  the large fleshy fungi known as mushrooms, it is still a common experience to
  come across a mushroom that cannot be easily identified in the available
  books or which doesn't really fit the definition of any recognized species.
  This site is intended to address that gap by creating a place for us to talk
  about and record what we've found, as well as connect to the existing
  literature about mushrooms.  Please do not feel intimidated by the scientific
  bent of the site.  Everyone is welcome to dive in and add their own mushroom
  observations, upload mushroom photos and make [:comments] on other people's
  observations.

intro_image_sharing:  >
  *Image Sharing:* This site follows the principles of cooperative sharing
  pioneered by the "Free Software Foundation":http://fsf.org, further expressed
  by the "Open Source software movement":http://opensource.org, and expanded to
  other creative efforts by the "Creative Commons":http://creativecommons.org.
  Consequently all images are made available under one of the Creative Commons
  licenses.  In short this means that when anyone uploads one of their images
  to the site, they are giving others explicit permission to use those images
  under certain "conditions":/observer/how_to_use#license in perpetuity.  This
  type of permission is very important for basic research.  It allows future
  researchers to freely use these data to expand our understanding of
  mushrooms.  It also significantly increases the likelihood that the data will
  continue to be available into the distant future.
  \n\n
  If you upload your own images, this license does not mean you are giving up
  your copyright or your ability to make money off your images.  Depending on
  which license you choose, you can still require that anyone who wishes to use
  any of these images for commercial purposes, get in touch with the copyright
  holder and work out the conditions for that use.  The site includes special
  links on the image pages to help create those relationships.

intro_source_code:  >
  *Source Code:* Source code for the site is available at: "[repo]":[repo] and
  is licensed under the "Open Source MIT
  License":http://www.opensource.org/licenses/mit-license.php.  Source code
  contributions are welcome ("README":[readme]). Here's a list of "planned features":[todo_list].
  All suggestions and comments are welcome.  If you would like to contribute,
  please send mail to *nathan at collectivesource.com* so we can coordinate
  our efforts.

intro_note:  >
  *Note:* The administrators of this site reserve the right to remove any
  material they deem inappropriate or not in keeping with the purpose of this
  site.

intro_talks:  >
  *Talks:*
  \n\n
  "[:app_title]: The First Year":/talks/MO-First-Year.html

################################################################################

# HOW TO HELP PAGE

# observer/how_to_help
how_help_title:  How to Help Make [:app_title] Better
how_help_intro:  >
  This page provides a list of skills that we could really use some help with.
  If you're interested in helping out just "send an
  email":/observer/ask_webmaster_question and let us know what you want to do.

how_help_contributors:  >
  h2. 1. Contributors
  \n\n
  p(normal).  Beyond adding pictures and descriptions of mushrooms that you've
  seen, you can make a big difference to the site by "describing
  species":/observer/how_to_use#describing_species or "defining
  locations":/observer/how_to_use#defining_locations.

how_help_designers:  >
  h2. 2. Designers
  \n\n
  p(normal).  The site is pretty spare and could use an artisitc eye to help
  with things like icons and themes.

how_help_developers:  >
  h2. 3. Developers
  \n\n
  p(normal).  We have "lots of ideas":[todo_list] about how to improve the
  site.  The framework, Ruby on Rails, is really easy to pick up and we are
  more than happy to mentor anyone who wants to dive in.

how_help_translators:  >
  h2. 4. Translators
  \n\n
  p(normal). The site is set up to support foreign languages.  All we need is
  someone to do the translations.

how_help_donors:  >
  h2. 5. Donors
  \n\n
  p(normal). Help support our server costs by "donating":/support/donate to
  the Mushroom Observer.

how_help_business_planning:  >
  h2. 6. Business Planning
  \n\n
  p(normal).  So far [:app_title] has been an entirely volunteer effort,
  we have begun to make it financially sustainable as the founding resource
  for the non-profit "Consortium for Digital Mycology Resources":http://digitalmycology.org,
  but the effort is just getting so let us know if you want to get involved or
  have any business related advice.

################################################################################

# HOW TO USE PAGE (COMMON TASKS)

# observer/how_to_use
how_title:  How to Use [:app_title]
how_common_tasks:  Common Tasks
how_glossary:  Concepts Glossary

how_intro:  >
  This page provides some short descriptions of common uses of this website
  followed by an overview of the basic concepts used.

how_keeping_up:  >
  *Keeping Up with Changes* - The default page for [:app_title] is the
  '[:rss_log_title]', it is also accessible through the '"Latest Changes":/'
  link in the left-hand panel.  This page shows you the most recent changes on
  the site.  It lists new "Observations":#observation and "Species
  Lists":#species_list as well as significant changes to any already existing
  ones.  Additions of "Images":#image and "Comments":#comment are considered
  significant changes to the relevant observations.  Changes to "Names":#name
  are also listed.  Click the page numbers at the top and bottom of the page
  to browse through older changes.  Observations and names created as a side
  effect of other changes are not listed separately.
  \n\n
  Note: The latest changes can be tracked using our "RSS feed":/observer/rss.
  See this "wikipedia article":http://en.wikipedia.org/wiki/Rss for more
  information about RSS feeds.

how_searching:  >
  *Searching* - There are several interesting ways to search for information on
  the site.  The simplest is to type a search string into the search box near
  the top of each page and click one of the buttons next to it.  This will give
  you a list of all the "Observations":#observation, "Images":#image,
  "Names":#name or "Locations":#location that contain fields matching the given
  string.  If you need a little more control over the search, try clicking
  '[:app_advanced_search]'.
  \n\n
  You may also browse the site using the links in the left-hand panel.  For
  example, '[:app_index_a_z]' shows all the species that have observations,
  listed alphabetically.  You can page through this list, or skip directly to
  the letter of a name you are interested in by clicking the appropriate page
  number or letter along the top or bottom of the list.  Click a name from this
  list to see a description of the species and a list of observations of that
  species.  If you click a genus like 'Agaricus', it will also show a list of
  species in that genus.  Note, however, that in this case it will only show
  observations that have been identified to the genus level, not ones that have
  been identified as a species in that genus.  On the other hand, if two names
  are considered synonyms, you will see observations for either name on this
  page.  (*NOTE*: If you do a search on 'Agaricus', it _will_ show all the
  observations whose name contains that string, so you get all the observations
  that belong to that genus.)
  \n\n
  Whenever you click an observation or other result on an index page, it will
  take you to a page showing that result.  At the top of the page you will see
  '[:PREV]', '[:NEXT]', and '[:INDEX]' links.  These let you browse
  forward or backward through the results or return to the index.  At the top
  of the index page you will often see links allowing you to sort the results
  by different criteria, such as by date, name or user.  In the same place you
  will sometimes find links that let you turn an index of observations into an
  index of names or images of those same observations.  For example, if you
  click '[:app_your_observations]', it will show you a list of observations you
  have posted.  Click '[:show_objects(types=:names)]' at the top of the
  page to see a list of the species you have seen, or click
  '[:show_objects(types=:locations)]' to see a list of all the locations
  you've gone mushrooming in.
  \n\n
  Power users may also be interested in our new API providing direct access to
  our database back-end.  This can be used to mine our database for images or
  species descriptions for inclusion in wikipedia or other public websites.
  You can also use it to upload observations and images and much more.  Please
  contact the webmaster for more information.

how_unknown_help:  >
  *Getting Help with an Unknown* - In order to get help with an unknown, you
  need to have a user account.  These can be created easily by selecting
  '[:app_create_account]' from the left-hand panel.  See the discussion of
  "Users":#user below for more details.
  \n\n
  Once you are logged in, create a new "Observation":#observation by selecting
  '[:app_create_observation]' in the left-hand panel.  Enter all the details
  you can into the resulting form.  You can leave the '[:WHAT]' field blank
  call it '[:unknown]', or if you think you know the genus or family or
  other group, give that "Name":#name followed by 'sp.', e.g., 'Russula sp.'.
  In the '[:NOTES]' field provide information about habitat, odor, smell
  and anything else not clear from the photos.  Once the form is as complete as
  you can make it, click '[:CREATE]'.
  \n\n
  You should now be looking at a page showing you the information you just
  entered.  However, if you used a name that is not currently in the database,
  you will be asked if you want to add the name.  This also gives you a chance
  to catch and fix typos.  In addition, if you use a name that is considered
  deprecated, you will be given the option of using a preferred synonym.
  \n\n
  Once you have created the new observation, you can upload any "Images":#image
  you have by selecting the '[:show_observation_add_images]' link on the
  right-side of the page.  It is very important either that it be an image you
  took or that you have the explicit permission of the person who created the
  image to upload it to the site.  If you did not take the image, please update
  the '[:form_images_copyright_holder]' field to reflect the actual owner.  This
  page also allows you to select the "License":#license you want to release the
  image under.
  \n\n
  When you add unknowns, the community will generally "propose one or more
  names":#proposing_names for it within 24-hours.  If you find any of the
  suggested names compelling, you should not hesitate to revisit your
  observation and "Vote":#vote on them.  Please see the discussion below on
  "voting":#voting, as well.  Members of the community may also post feedback
  via "Comments":#comment.  By default your account is set up to deliver
  comments posted about your observations to you by email.  If you are asked to
  provide more details on the collection, we prefer that you select
  '[:show_observation_edit_observation]' (at the top of the observation page)
  and add them to the '[:NOTES]' field than to just post another comment.

how_adding_observations:  >
  *Adding Observations You Have Identified* - Use the same process as "Getting
  Help with an Unknown":#unknown_help, except this time provide your
  identification in the '[:WHAT]' field.  You are strongly encouraged to
  say something about how you arrived at the identification.  We've provided a
  small set of checkboxes to make this easy ('[:naming_reason_label_1]',
  '[:naming_reason_label_3]', etc.), but you are encouraged to elaborate on
  them in the provided text fields (e.g., list the references you used, or
  enter 'sequenced the DNA and compared it against the data in GenBank'!).
  Community members will often post "Comments":#comment if there is some
  question about the collection or if they would like clarification as to why
  you ruled out other "Names":#name.

how_proposing_names:  >
  *Proposing Names* - Any member of the community can propose "Names":#name for
  any "Observations":#observation.  Click an observation (e.g., from the
  '[:rss_log_title]' page) and scroll down below the observation notes.  There
  should be a list of "Proposed Names":#proposed_name enclosed in a thin
  outlined box.  Most observations will already have at least one proposed name
  (by the owner).  From here you may either click
  '[:show_namings_propose_new_name]' or "Vote":#voting on existing names.  In
  either case you will have to log in before you are allowed to do so.
  \n\n
  When you click '[:show_namings_propose_new_name]' you will be presented with
  a form much like the one used to create an observation.  In addition to the
  name, you are required to choose a confidence level.  This is your
  "Vote":#vote, and you may change it on the
  '[:show_object(type=:observation)]' page at any time you like.  As with
  creating an observation, you are strongly encouraged to give some explanation
  as to why you think your Name applies to this Observation (and why other
  names don't).  When you are finished, click '[:CREATE]'.  You will be
  given a chance to correct typos or to choose an accepted name if you entered
  a deprecated one.
  \n\n
  Users are not allowed to propose a name if someone else has already done so.
  The only reason to do so would be to describe alternative reasons for
  reaching the same conclusion.  Instead use the discussion forum provided by
  comments to do this.

how_voting:  >
  *Voting on Proposed Names* - Click an "Observation":#observation, e.g., from
  the '[:rss_log_title]' page, and scroll down to the
  '[:show_namings_proposed_names]' box.  Note that you must login before you
  can see or change any of your "Votes":#vote.  Once you have logged in, you
  should see pulldown menus next to each "Proposed Name":#proposed_name.  Your
  vote expresses the degree of confidence or agreement you have with placing
  that name on that observation.  Everything above '[min_neg_vote]' is
  considered a positive vote, everything below '[min_pos_vote]' negative.
  Choose '[no_opinion]' to tell it to delete your vote.  When you've changed
  all the votes you want to, be sure to click '[:show_namings_update_votes]' to
  record your votes.  Don't worry, if you forget and try to navigate away
  without casting your votes it will complain (unless you have Javascript
  disabled).
  \n\n
  Roughly speaking, votes for a name are weighted, summed and then divided by
  the number of votes for that name.  The name with the highest score wins, and
  that name will be applied to that observation throughout the site.  In the
  case where multiple synonyms are proposed for an observation it lumps the
  votes together, choosing each user's strongest vote within that group of
  synonyms.  In the end, assuming that group of synonyms wins, the currently
  accepted name is used as the community consensus.  If there is still debate
  in the scientific community about which name is appropriate for a given
  taxon, then it will use votes the best it can to decide between multiple
  accepted names.  Note that the owner's vote automatically carries a little
  more weight, as do the votes of users who have made a large
  "Contribution":#contribution to [:app_title] or who are considered
  experts.  Click '[:app_contributors]' or click a user's name to see the
  contribution and expert status.  (We use the log base 10 of users'
  contributions.)

how_adding_comments:  >
  *Adding Comments* - When you are looking at an "Observation":#observation, if
  you would like to post or respond to a "Comment":#comment, select the
  '[:show_comments_add_comment]' link near the top of the page.  If you are
  not currently logged in to a "User":#user account, you will be asked to log
  in.  Once you are logged in, you will be given a form asking for a summary
  and your comment.  Note that you can do some simple formatting in the comment
  section.  This is briefly documented below the text field with a link to
  detailed documentation.  You can also add links within a comment using
  standard HTML formatting.  The HTML gets automatically cleaned to avoid
  security problems like script injection, so try not to get too fancy.

how_tracking_species:  >
  *Tracking a Particular Species or Genus Through Email* - [:app_title]
  allows you to request an email any time a particular "Name":#name is given to
  an "Observation":#observation.  If that name is a genus or species it will
  also send you an email whenever a species or subspecies is observed.  To turn
  this feature on, go to the page for a Name you are interested in (see
  "Searching":#searching) and click '[:show_name_email_tracking]'.  You can
  configure it so that the person who made the observation that was given that
  name will be sent a customized email to let them know you are interested in
  their observation.  If you don't provide any instructions, they will not be
  sent an email.  If the observer gives the name at the time the observation is
  created, they will be shown your message immediately through the website.
  You can modify or disable your request for a particular name by going back to
  that name and again selecting '[:show_name_email_tracking]' and clicking the
  '[:DISABLE]' button on the page that comes up.

how_describing_species:  >
  *Describing Species* - Click any "Name":#name link you see throughout the
  site.  For example, click any of the results listed in
  '"[:app_index_a_z]":/name/observation_index', search for a name in the search
  bar, or click the 'About &lt;name&gt;...' link at the top of any
  "Observation":#observation page.  These all take you to a page summarizing
  everything we know about this taxon.  If you are familiar with this species
  and there is something you would like to add, click
  '[:show_name_edit_name]' and add your notes.  You are encouraged to cite
  references including field guides and scientific papers.  Short quotes from
  references are fine, but please don't make extensive quotes without obtaining
  permission from the original author.

how_projects:  >
  *Projects* - Projects are a way for a group of "Users":#user to work together
  to create a set of work that they want to keep out of the public eye until
  they are ready to publish it.  The original purpose was to support university
  classes where there was a desire to keep a more controlled environment while
  the class was going.
  \n\n
  Anyone can create a new project by clicking on
  '"[:app_list_projects]":/project/list_projects' in the left-hand panel and
  then clicking on '[:list_projects_add_project]'.  The person who creates the
  project is always a member and an administrator for that project.  An
  administrator for a project can add new members by clicking the
  '[:show_project_add_members]' link at the top of a project's 'Show Project'
  page.  Administrators can also make other users administrators for the
  project by going to one of the '[:add_members_change_status]' links available
  on the 'Show Project' or 'Add Members' pages.  Any User can send requests to
  the admins for a project.  These requests are emailed to the admins and
  contain a link for changing that user's status.
  \n\n
  Currently the primary focus of projects is writing
  "Descriptions":#description for various species.  Note, however, that anyone
  can now create new descriptions for a species (see "Describing
  Species":#describing_species) by clicking on
  '[:show_name_create_description]' at the top of the 'Show Name' page.
  Descriptions that are created for a project are visible only to members of
  that project until they are published, and editable only by the owner of the
  description and project administrators.  When a description is published it
  will become the official description if no official description exists yet.

how_maps:  >
  *Working with Maps* - Currently there are three types of maps available on
  [:app_title]: Occurrence Maps (e.g., "Occurrence map for
  **__Craterellus cornucopioides__**":/name/map/284), Location Maps (e.g.,
  "Salt Point State Park":/location/show_location/4) and the
  "[:map_locations_global_map]":/location/map_locations.
  \n\n
  To see an occurrence map for a particular "Name":#name, go to the page for
  that name (e.g., enter the name in the search bar, select '[:NAMES]'), and
  click '[:app_search]', then click '[:show_name_distribution_map]' at the
  top of the page.
  \n\n
  "Users":#user are encouraged to add to the occurrence map for a name.  The
  easiest way is to create a new "Observation":#observation using an already
  defined "Location":#location.  Note, however, that auto-completion for the
  '[:WHERE]' field will list all matching locations whether they are
  defined or not.
  \n\n
  You can also explicitly choose not to have an observation show up on the
  occurrence map.  This allows you to record observations of mushrooms in
  places like mushroom fairs, old photos or other places where you may not know
  where the mushroom was actually collected.  When creating or editing an
  observation there is a checkbox labeled
  '[:form_observations_is_collection_location]'.  By default it is checked.  If
  you uncheck it, that observation will not appear in any occurrence maps.

how_defining_locations:  >
  *Defining Undefined Locations* - Many "Observations":#observation have been
  reported from undefined "Locations":#location.  These observations will not
  appear in our "occurrence maps":#maps.  An excellent, easy way for
  "Users":#user to help out if they have a little spare time is to locate and
  defined these undefined locations.
  \n\n
  When browsing through observations, defined location names will be followed
  by a link labeled '[:click_for_map]'.  Undefined location names will be
  followed by a link labeled '[:SEARCH]'.  If you click the link for an
  undefined location, it will show a list of observations reported for that
  location.  The resulting page will include two links at the top of the page:
  '[:list_observations_location_define]' and '[:list_observations_location_merge]'.  Clicking on
  '[:list_observations_location_define]' will present a form which you can use to create that
  location.  Clicking on 'Merge With a Defined Location' will present you with
  a list of similar locations which have already been defined.  Clicking on any
  of these locations will perform the merge.
  \n\n
  You can also see a list of all locations in use by clicking on
  '"[:app_list_locations]":/location/list_locations' in the left-hand panel.
  This page lists both the defined locations (first column, sorted
  alphabetically) and the undefined locations (second column, sorted by the
  number of observations reported from that location).  In some cases the same
  location has been given multiple names (e.g., 'Point Reyes National Seashore'
  and 'Pt Reyes Park').  You can merge an undefined location with a defined
  location by clicking on '[:list_place_names_merge]' next to the undefined
  location (see above).
  \n\n
  When defining a new location, the first thing to do is to review its name.
  Mushroom Observer tries to enforce a set of "rules":/location/help.
  \n\n
  In theory it is possible for the same location to be defined more than once
  (presumably by different users).  If this happens, you can request a merge by
  editing one of the two locations and changing its name to be exactly the same
  as the other's.  This will not have any immediate effect, but it will display
  a warning message, and an email will be sent to the site administrators with
  the details.  Merging defined locations is restricted since it can cause
  significant data loss.

how_creating_species_lists:  >
  *Creating Species Lists* - To create a "Species List":#species_list, click
  '"[:app_create_list]":/species_list/create_species_list' in the left-hand
  panel.  Fill out the various fields.  In the 'Write-In Species' field, you
  should give each species a "Name":#name on a line by itself.  When you go to
  create the list, each line is checked to see if there is a match in the
  database.  If there is no matching name, you will be asked if you want to add
  the unknown names to the database.  This gives you a chance to catch and fix
  typos as well as giving you a simple way to add missing names.  Each name
  given in the 'Write-In Species' field (or loaded from a file) will be used to
  create a completely new "Observation":#observation.  The
  '[:form_species_lists_list_notes]' are only shown when the entire species
  list is shown.  Use '[:form_species_lists_member_notes]' to indicate text you
  would like to add to each new observation.
  \n\n
  There are several methods of collecting a set of existing observations into a
  new list.  In the simplest method, first create an empty species list, then
  go to each of the observations you want to add and select
  '[:show_observation_manage_species_lists]'.  This will give you the
  opportunity to add that observation to any species list you own.  (Note, you
  can add anyone's observations to a species list you own.)
  \n\n
  In another method, you may select '[:app_create_list]' directly from any
  index of observations or names.  For example, you may use the search bar at
  the top of the page or the
  '"[:app_advanced_search]":/observer/advanced_search_form' feature to request
  all observations from Michigan.  When it shows you the first page of results,
  click '[:app_create_list]' (in the left-hand panel), and it will give you
  a list of all the matching names to choose from in the new species list form.
  \n\n
  Lastly, when you are viewing an existing species list, you may click
  '[:species_list_show_clone_list]' or '[:species_list_show_set_source]' at the
  top of the page.  '[:species_list_show_clone_list]' will take you directly to
  a new species list form, with all the information of the existing list
  already filled in.  '[:species_list_show_set_source]' will copy that species
  list's names to the clipboard.  The next time you click
  '[:app_create_list]', the new species list form will give you this list of
  names to choose from (unless you show another observation or name index in
  the meantime).

################################################################################

# HOW TO USE PAGE (GLOSSARY)

# Note: Glossary terms should appear in alphabetical order.
how_glossary_body:  >
  #(#comment)       [:how_comment]\n
  #(#image)         [:how_image]\n
  #(#license)       [:how_license]\n
  #(#location)      [:how_location]\n
  #(#name)          [:how_name]\n
  #(#observation)   [:how_observation]\n
  #(#proposed_name) [:how_proposed_name]\n
  #(#description)   [:how_description]\n
  #(#species_list)  [:how_species_list]\n
  #(#user)          [:how_user]\n
  #(#vote)          [:how_vote]\n

how_comment:  >
  *Comment* - Comments are the standard way to discuss an
  "Observation":#observation or its associated "Images":#image.  Each comment
  is owned by a particular "User":#user.  A comment may only be edited or
  deleted by the owner or a site administrator.  You can look up all comments
  that have been made about your observations by clicking on
  '"[:show_user_comments_for_you]":/comment/show_comments_for_user' in the
  left-hand panel.

how_contribution:  >
  *Contribution* - A number or score that measures the quantity and quality of
  contributions a "User":#user has made to [:app_title].  Click
  '[:app_your_summary]' to see a break-down of your own contribution.  You
  earn points for every "Observation":#observation, "Image":#image,
  "Comment":#comment, etc. you have posted.  "Describing
  Species":#describing_species and "Defining Locations":defining_locations are
  some of the most important contributions a user can make.  (See "How To
  Help":/observer/how_to_help for a list of other ways to help out.)
  Currently, contribution is used only in weighting your "Votes":#vote when
  voting on "Proposed Names":#proposed_names for observations.

how_description:  >
  *Species Description* - A collection of text describing a "Name":#name.
  Every name automatically gets one official description that everyone in the
  community is allowed to read and modify.  Additional descriptions may be
  created by any "User":#user, including project members.  The owner of a
  description may choose any level of read or write permissions, and can
  control who is given authorship credit.  Since descriptions, especially the
  official one, are often collaborative efforts, modifications by a user are
  subject to community review, and past versions are kept to facilitate this
  process.  The content of a description includes a set list of sections,
  including things like '[:form_names_gen_desc]', '[:form_names_diag_desc]',
  '[:form_names_look_alikes]', '[:form_names_refs]' and other notes.

how_image:  >
  *Image* - A photograph or illustration of one or more mushroom species.
  Images are associated with one or more "Observations":#observation.  A given
  Image is owned by a particular "User":#user who may or may not be the
  copyright holder.  Only the owner or a site administrator can remove an image
  or edit the associated information.  All images in the site are required to
  be released under one of the "Creative Commons
  licenses":http://creativecommons.org.  If you dispute the given copyright or
  the licensing of an image you are the copyright holder of, send mail to the
  "webmaster":/observer/ask_webmaster_question.

how_license:  >
  *License* - "Images":#image on [:app_title] are posted with an explicit
  license.  The current options are the "Creative Commons Attribution, Share
  Alike License":http://creativecommons.org/licenses/by-sa/3.0/ and the
  "Creative Commons Attribution, Non-Commercial, Share Alike
  License":http://creativecommons.org/licenses/by-nc-sa/3.0/.  The primary
  difference is whether the image can be used in any potentially commercial
  setting.  One of the side effects of selecting the non-commercial license is
  that your image cannot be used on "Wikipedia":http://wikipedia.org.  The
  license can be set on a per image basis.  The looser, Wikipedia compatible
  license is the default for new "Users":#user.  However, you can select the
  non-commercial license to be your default by selecting it on your
  '"[:app_preferences]":/account/prefs' page and clicking on
  '[:SAVE_CHANGES]'.

how_location:  >
  *Location* - A rectangular region enclosing a given location, as defined by
  the northern, southern, eastern and western boundaries.  In addition to the
  position, locations can also include a minimum and maximum elevation along
  with various notes.  Note that the elevations should be in meters not feet.
  A location is not considered to be owned by a particular "User":#user.  Any
  user may change or define any location, but all of a user's changes are
  subject to review by the community.  To help with this review process, copies
  of the previous versions are kept.

how_name:  >
  *Name* - A name for some group of mushrooms.  Most commonly this is the name
  of a species, but it can be any taxon (genus, family, variety, etc.).  Names
  can also refer to groups that are not officially recognized scientific names
  such as common names or functional groups like Gasteromyces.  A name is *not*
  considered to be owned by a particular "User":#user.  Any user may change any
  name, but all changes are subject to review by the community.  To help with
  this review process, copies of previous versions are kept.  Names can have an
  acknowledged author.  The author is normally only given for scientific names.
  The author should follow the standard practice of listing the person who
  first correctly published the name.  In the case of names at or below the
  species level, the author may also include the person who transfered the
  species to the current genus, e.g., (Singer) Jenkins.

how_observation:  >
  *Observation* - A record of a single mushroom species at a particular time
  and "Location":#location.  Typically associated with one or more
  "Names":#name (see "Proposed Name":#proposed_name below) and some number of
  "Images":#image.  Each observation is owned by a "User":#user, and can only
  be edited or deleted by that user or a site administrator.  However, any user
  may post "Comments":#comment about any observation.  Observations can also be
  included in one or more "Species Lists:#species_list.

how_proposed_name:  >
  *Proposed Name* - A "Name":#name as proposed for a given
  "Observation":#observation.  Any number of names may be proposed for a single
  observation by members of the community.  No special treatment is given to
  any member's name.  Community consensus is arrived at through the process of
  "voting":#voting.  Each proposed name for an observation is owned by a single
  "User":#user.  However, even the user who proposed the name cannot
  necessarily modify or delete a name once other members of the community have
  cast "Votes":#vote for or against it.  Fortunately you may always propose
  additional names.  There is never any sort of penalty associated with
  proposing incorrect names.

how_species_list:  >
  *Species List* - A list of "Observations":#observation (not "Names":#name).
  Includes a date, a "Location":#location and a title for the list.  A given
  species list is owned by a particular "User":#user.  Only the owner or a site
  administrator can change or delete a species list.  There are no strict rules
  for how species lists should be used.  This is an area that is likely to
  change in the future as the community comes up with clearer ideas for how
  they should be used.

how_user:  >
  *User* - An account on [:app_title].  You are required to provide a
  valid email address when you first create an account.  This allows the system
  to stop automated programs from creating bogus accounts.  It also provides a
  way for other users to get in touch with you.  However, your email address
  will never be revealed unless you request an email be sent to another user
  and then only to that user.  If you are concerned about having your email
  address in our database, once you have verified your account, you can go to
  the '"[:app_preferences]":/account/prefs' page and remove your address.

how_vote:  >
  *Vote* - One "User's":#user vote on a "Proposed Name":#proposed_name for a
  given "Observation":#observation.  Expresses a level of confidence or
  agreement with that name, with half the choices ("[min_pos_vote]" and up)
  being positive and half ("[min_neg_vote]" and below) being negative.  Votes
  are owned by that user, and can only be changed or deleted by the owner or a
  site administrator.

################################################################################

# LOCATION HELP PAGE

location_help_title:  Locations in Mushroom Observer

location_help_intro:  >
  The Mushroom Observer provides two ways to represent the geographic location
  of an observation.  The simplest are latitude and longitude positions associated
  with the observation.  Please keep these accurate to within at least 300 meters
  (or about 1000 feet).  However, the more widely used method is a simple phrase
  describing the location.  For example, "Beebe Woods, Falmouth, Massachusetts, USA".
  The goal of these location names is to provide a consistent, reusable way of talking
  about where an observation was made without necessarily revealing a precise "spot".
  If you are comfortable provide more precise lat/longs for an observation, the
  location names are still useful for searches so you are encouraged to provide
  them as well.  The location names should, by default, go from the smallest
  contained area to the country name.  If you prefer to describe your locations
  as going from the largest (country) down to the smallest contained area, you can
  change your preference from the default, "Postal", to "Scientific" on your
  preference page.  There are cases such as
  "Great Smoky Mountains National Park, Blount Co., Tennessee, USA",
  where the area you are describing overlaps a number of counties, states or
  even countries.  In these cases, the country and other official political
  boundaries should come at the end as shown in the example.
  \n\n
  Originally, the Mushroom Observer was very loose about these location names,
  hoping that the users would create a reasonably consistent set of rules and
  correct each other.  After about four years and thousands of location names,
  we found that there were rules emerging, but they were not applied at all
  consistently and people were not tending to directly correct each other.
  Consequently, we have tried to codify these rules and when reasonable to provide
  warnings if you attempt to create a new location that violates these rules.
  It is not always possible to correct identify "bad" locations, so if you get
  some warnings, but after reviewing the location decide it should be "good",
  then simply resubmitting the form will force the name into the database.
  However, all new location names will get reviewed regularly and may get changed
  to better fit the consensus rules.  Below are some examples of "bad" and "good"
  location names followed by a more detailed explanation of the current rules.
  Each example is labeled with the following section that explains the example
  in more detail.  These rules are by no means set it stone and we encourage the
  discussion and revision of them.

location_help_example_help:  These are cases that are not detected automatically, so no warning would be given.
location_help_example_title:  Some examples
location_help_bad:  Bad
location_help_good:  Good
location_help_explanation:  Explanation
location_help_rules_title:  The Current "Rules"

location_help_rule_reversible:  >
  *Consistent and Reversible Order* - You can now ask for location names to appear in the reverse order from the default.
  Thus, you can see a location as either:
  \n\n
  Albion, California, USA
  \n\n
  or as
  \n\n
  USA, California, Albion
  \n\n
  You can change this on your Preferences page by selecting 'Postal' (the default)
  or 'Scientific' (the one that starts with the country).  When you input new location
  names it will of course also follow your preferred order.
  \n\n
  Roy Halling was the inspiration for this feature when he started putting in his
  locations starting with the country names and we got into a discussion about it.
  Apparently the standard practice in the scientific community is to start with the
  largest locale (typically a country) and work down to the smallest locale (a county,
  town or specific location).  From looking through all the locations that have been
  put into MO, it is clear that most people expect to put in the smallest location
  first and work up to the country.
  \n\n
  In order to enable this feature, I have had to require that the place names be
  easily and consistently reversible.  This means you must separate each section
  of the location with a ', ' (no period, no missing spaces, no double spaces).
  It also means that you should always enter the names in order of increasing size
  when you can.  There are some specific exceptions to this rule that are discussed
  below.

location_help_rule_countries:  >
  *Use Country Names* - As a further check when you enter an unfamiliar location, it will check to see that
  the largest locale has been previously entered for some other location.  This list
  currently consists of only countries, continents and the special location 'Unknown'.
  Since it does not include all possible countries, it is still possible to override
  the check by resubmitting the same name twice.  Such entries will be reviewed carefully
  to ensure that this list remains clean.  For now you should only enter country names
  as they are written in English.  For example, please use 'Germany' rather than
  'Deutschland'.  The goal for the moment is simply consistency.  However, the long
  term goal is to actually allow these names to be consistently translated based on
  the user's language selection.  Continents should only be used if the country is
  not known or there is no country.

location_help_rule_states:  >
  *Use State Names* - In the case of countries where I know the states, I also check for those as
  the next smallest area within a country.  At the moment I am checking this
  for Canada, Australia and USA.  The primary goal of this in the US at least
  is to ensure the uniqueness of the next element in the list.  In the US it
  is not unusual to have the same city or county name in more than one state.
  If there are other countries where this check would be useful, please let me
  know and include an exhaustive list of all states, provinces, territories etc.
  To increase the understandability to people from other parts of the world,
  state abbreviations (even extremely standard ones) are discouraged and will
  create a warning.  The one current exception is 'Washington DC'.  Many people
  are not aware of what the 'DC' stands for and would be unlikely to enter
  'Washington, District of Columbia'.  Note that in this case I have also
  removed the ', ' since that would cause 'USA, DC, Washington' when in
  'Scientific' mode.

location_help_rule_counties:  >
  *Counties OR Cities* - In the past, MO has encouraged the use of county names whenever they are
  known.  The new policy is that the county should only be included when it
  is the smallest political area the location is contained in or when the
  city or town name is ambiguous.  For example, what used to be described as
  "Berkeley, Alameda Co., California, USA" should now be given as just
  "Berkeley, California, USA".  This change is in part due to seeing what
  people actually do.  Generally people have been good about using county
  names in the case of public lands like parks and national forests where
  the county is the most obvious political boundary.  However, with cities
  and towns people often don't know what county a city or town is in.  In
  addition, the information is typically redundant for towns and cities in
  the US where they are almost always completely contained in county or they
  are independent of the counties and there are almost never two towns with
  same names in a state (there are exceptions though such as Goshen, Vermont).
  I've also found that many of the map services such as maps.google.com and
  maps.yahoo.com get confused if you include both the city and the county in
  the search string.
  \n\n
  That being said, there are also often areas that have a local name, but are
  not actually an incorporated city or town.  In these cases the county name
  is encouraged since the names cannot be assumed to be unique.  For example,
  "North Lakeport, Lake Co., California, USA".  Wikipedia has been the most
  helpful resource I've found for determining if a town is actually
  incorporated.

location_help_rule_near:  >
  *Use 'near'* - If there is a landmark or town near to the collection location, but the
  smallest political boundary is a county or country, then it is helpful to
  mention this using the word "near".  When used this way it should always be
  all lowercase.  For example,
  "Albis Mountain Range, near Zurich, Switzerland".  Looking through the old
  data, I found users used both "near" and "area" for this with "near" being
  more common.  This is also better because "area" sometimes gets used for
  place names such as "Day-Use Area" or "Rest Area".

location_help_rule_southern:  >
  *Use of 'Southern', 'Northern' etc.* - If there isn't a known a clear landmark or town near the collection
  location, it is fine to use compass directions such as 'Southern',
  'Northern', 'Southwestern' etc.  In these cases always use the '-ern'
  ending to indicate that it's descriptive.  However, these terms should be
  avoided if it creates ambiguity.  For example, "Western Australia" is the
  name of an official state in Australia, so it should only be used as such
  and should be followed by the country name.

location_help_rule_abbr:  >
  *Avoid Abbreviations (and Periods in General)* - Most abbreviations should be
  avoided since people apply them somewhat
  arbitrarily and inconsistently.  The following are examples of abbreviations
  that should definitely be avoided: Hwy, Mt, Mtn, CA, BC.  However, there are
  some specific examples, that should be used in preference to there spelled
  out versions.  These are:
  \n\n
  Co. for County\n
  Rd. for Road\n
  St. for Street\n
  Ave. for Avenue\n
  Blvd. for Boulevard\n
  USA for United States of America\n
  Washington DC for Washington, District of Columbia\n
  \n\n
  Periods in general should be avoided except for the above abbreviations.
  They should not be used at the end of country names or as separators.\n
  Finally, 'and' should be used rather than '&'.

location_help_rule_other:  >
  *Other Things to Avoid* - All lowercase - In general at least the leading letter of each area should
  be capitalized and when in doubt capitalize every leading letter.\n
  No lat/longs - There is now direct support for this for each observation.
  Do not include it in the name of a location.\n
  No habitat info - Habitat info should go in the notes for the observation.\n
  Parentheses and Braces - If you're tempted to use parentheses or braces, stop yourself
  and ask if this information should be in the notes for the observation or if there is a
  better way to describe the location.\n
  Avoid diacritics (eg é, ü etc.) - As mentioned when discussing country names, you should
  try to use the English version of a location name when possible and English does
  not include diacritics.  This is intended to encourage consistency and we are
  planning on providing proper support for other languages which will benefit from
  this consistency.  There are certainly cases where the a city or region is only
  know by a name that includes diacritics.  In these cases they should be used.
  A few simple web-searches should give you a good idea if there is a common English
  variation of a name (e.g., Montreal, Quebec for Montréal, Québec).

location_help_rule_good_habits:  >
  *Stuff You Are Encouraged to Do* - If you are creating a new name, take some time to figure out a good name.
  Searching within Mushroom Observer can be helpful.  If you don't find anything
  there, then look things up in Google Maps (http://maps.google.com) and Wikipedia (http://wikipedia.org).
  Also feel free to use the notes section of either an observation or a location
  to be more specific.

################################################################################

# ERROR MESSAGES

# ActiveRecord validation error messages.
validate_confirmation_mismatch:  "[Field] doesn't match confirmation."
validate_invalid:  Invalid [field].
validate_missing:  Missing [field].
validate_not_a_number:  "[Field] is not a number."
validate_not_in_range:  "[Field] is out of range."
validate_this_more_than_that:  "[That] should be greater than [this]."
validate_too_large:  "[Field] should be at most [max]."
validate_too_long:  "[Field] must be less than [max] characters long."
validate_too_long_or_short:  "[Field] must be [min] to [max] characters long."
validate_too_short:  "[Field] must be at least [min] characters long."
validate_too_small:  "[Field] should be at least [min]."
validate_too_small_or_large:  "[Field] should be between [min] and [max]."

# One-time-use error messages.
validate_image_content_type_images_only:  You can only upload [:images].
validate_image_file_missing:  Had problems uploading [:image].
validate_image_file_too_big:  We can't handle [:images] that big.  Please reduce it to less than [max] before uploading.
validate_image_md5_mismatch:  The MD5 sum did not come out right.  Please try uploading your image again.
validate_observation_future_time:  Time travel is not allowed, pick a date from the past.
validate_observation_thumb_image_id_invalid:  Unable to find a corresponding [:image] for thumbnail.
validate_observation_where_missing:  Please tell us where it was seen or collected.
validate_user_email_missing:  Please give us a valid email address so we can verify your [:account].
validate_user_login_taken:  Sorry, that login name is already taken.
validate_image_wrong_type:  The file you tried to upload is not recognized as an image.  It is of type '[type]'.

# These shouldn't need translating, but you are free to override if you need to.
validate_comment_object_type_too_long:  "[:validate_too_long(field=''object_type'',max=30)]"
validate_comment_summary_missing:  "[:validate_missing(field=:summary)]"
validate_comment_summary_too_long:  "[:validate_too_long(field=:summary,max=100)]"
validate_comment_user_missing:  "[:validate_missing(field=:user)]"
validate_image_content_type_too_long:  "[:validate_too_long(field=''content_type'',max=100)]"
validate_image_copyright_holder_too_long:  "[:validate_too_long(field=:copyright_holder,max=100)]"
validate_image_title_too_long:  "[:validate_too_long(field=:title,max=100)]"
validate_image_user_missing:  "[:validate_missing(field=:user)]"
validate_image_when_missing:  "[:validate_missing(field=:date)]"
validate_interest_object_type_too_long:  "[:validate_too_long(field=''object_type'',max=30)]"
validate_interest_user_missing:  "[:validate_missing(field=:user)]"
validate_location_name_too_long:  "[:validate_too_long(field=''name'',max=1024)]"
validate_location_east_out_of_bounds:  "[:validate_too_small_or_large(field=:longitude,min=-180,max=180)]"
validate_location_high_less_than_low:  "[:validate_this_more_than_that(this=:low,that=:high)]"
validate_location_north_less_than_south:  "[:validate_this_more_than_that(this=:south,that=:north)]"
validate_location_north_too_high:  "[:validate_too_large(field=:latitude,max=90)]"
validate_location_search_name_too_long:  "[:validate_too_long(field=''search_name'',max=200)]"
validate_location_south_too_low:  "[:validate_too_small(field=:latitude,min=-90)]"
validate_location_user_missing:  "[:validate_missing(field=:user)]"
validate_location_west_out_of_bounds:  "[:validate_too_small_or_large(field=:longitude,min=-180,max=180)]"
validate_name_author_too_long:  "[:validate_too_long(field=:authority,max=100)]"
validate_name_display_name_too_long:  "[:validate_too_long(field=''display_name'',max=100)]"
validate_name_observation_name_too_long:  "[:validate_too_long(field=''observation_name'',max=100)]"
validate_name_search_name_too_long:  "[:validate_too_long(field=''search_name'',max=100)]"
validate_name_text_name_too_long:  "[:validate_too_long(field=''text_name'',max=100)]"
validate_name_user_missing:  "[:validate_missing(field=:user)]"
validate_naming_name_missing:  "[:validate_missing(field=:name)]"
validate_naming_observation_missing:  "[:validate_missing(field=:observation)]"
validate_naming_reason_naming_missing:  "[:validate_missing(field=:naming)]"
validate_naming_reason_reason_invalid:  "[:validate_invalid(field=''reason_code'')]"
validate_naming_user_missing:  "[:validate_missing(field=:user)]"
validate_notification_user_missing:  "[:validate_missing(field=:user)]"
validate_observation_user_missing:  "[:validate_missing(field=:user)]"
validate_observation_when_missing:  "[:validate_missing(field=:date)]"
validate_observation_where_too_long:  "[:validate_too_long(field=:location,max=1024)]"
validate_project_admin_group_missing:  "[:validate_missing(field=:admin_group)]"
validate_project_title_missing:  "[:validate_missing(field=:title)]"
validate_project_title_too_long:  "[:validate_too_long(field=:title,max=100)]"
validate_project_user_group_missing:  Missing [:user_group].
validate_project_user_missing:  "[:validate_missing(field=:user)]"
validate_species_list_title_missing:  "[:validate_missing(field=:title)]"
validate_species_list_title_too_long:  "[:validate_too_long(field=:title,max=100)]"
validate_species_list_user_missing:  "[:validate_missing(field=:user)]"
validate_species_list_where_missing:  "[:validate_missing(field=:location)]"
validate_species_list_where_too_long:  "[:validate_too_long(field=:location,max=100)]"
validate_user_email_too_long:  "[:validate_too_long(field=:email_address,max=80)]"
validate_user_login_missing:  "[:validate_missing(field=:login_name)]"
validate_user_login_too_long:  "[:validate_too_long_or_short(field=:login_name,min=3,max=40)]"
validate_user_name_too_long:  "[:validate_too_long(field=:full_name,max=80)]"
validate_user_password_confirmation_missing:  "[:validate_missing(field=:password_confirmation)]"
validate_user_password_missing:  "[:validate_missing(field=:password)]"
validate_user_password_no_match:  "[:validate_confirmation_mismatch(field=:password)]"
validate_user_password_too_long:  "[:validate_too_long(field=:password,max=40)]"
validate_user_theme_too_long:  "[:validate_too_long(field=''theme_name'',max=40)]"
validate_vote_naming_missing:  "[:validate_missing(field=:naming)]"
validate_vote_user_missing:  "[:validate_missing(field=:user)]"
validate_vote_value_missing:  "[:validate_missing(field=:confidence_level)]"
validate_vote_value_not_integer:  "[:validate_not_a_number(field=:vote)]"
validate_vote_value_out_of_bounds:  "[:validate_not_in_range(field=:vote)]"

# Runtime error and success messages.
runtime_added:  "Successfully added [type]."
runtime_added_id:  "Successfully added [type] #[value]."
runtime_added_id_to:  "Successfully added [type] #[value] to [name]."
runtime_added_name:  "Successfully added [type] '[value]'."
runtime_added_name_to:  "Successfully added [type] '[value]' to [name]."
runtime_added_to:  "Successfully added [type] to [name]."
runtime_admin_only:  That operation is restricted to site admins.
runtime_already_exists:  "[Type] already exists: '[value]'"
runtime_already_used:  "[Type] is already in use: '[value]'"
runtime_created:  "Successfully created [type]."
runtime_created_id:  "Successfully created [type] #[value]."
runtime_created_name:  "Successfully created [type] '[value]'."
runtime_delivered_message:  Successfully delivered message.
runtime_delivered_question:  Successfully delivered question.
runtime_delivered_request:  Successfully delivered request.
runtime_destroyed:  "Successfully destroyed [type]."
runtime_destroyed_id:  "Successfully destroyed [type] #[value]."
runtime_destroyed_name:  "Successfully destroyed [type] '[value]'."
runtime_invalid:  "[Type] is invalid: '[value]'"
runtime_lat_long_error:  "Latitude and longitude must be floating point numbers between -90 and 90, and -180 and 180 respectively."
runtime_merge_success:  Successfully merged [type] [this] into [that].
runtime_missing:  Missing [field].
runtime_no_changes:  "No changes made."
runtime_no_create:  "Unable to create [type]."
runtime_no_create_id:  "Unable to create [type] #[value]."
runtime_no_create_name:  "Unable to create [type] '[value]'."
runtime_no_destroy:  "Unable to destroy [type]."
runtime_no_destroy_id:  "Unable to destroy [type] #[value]."
runtime_no_destroy_name:  "Unable to destroy [type] '[value]'."
runtime_no_match:  "Can't find [type]."
runtime_no_match_id:  "Can't find [type] #[value]."
runtime_no_match_name:  "Can't find [type] matching '[value]'."
runtime_no_matches:  "No matching [types] found."
runtime_no_matches_pattern:  "No [types] matching '[value]' found."
runtime_no_more:  There are no more [types].
runtime_no_objects:  There are no [types].
runtime_no_parse:  "Unable to parse: '[value]'"
runtime_no_save:  "Unable to save [type]."
runtime_no_update:  "Unable to update [type]."
runtime_no_update_id:  "Unable to update [type] #[value]."
runtime_no_update_name:  "Unable to update [type] '[value]'."
runtime_not_owner:  "You are not the owner of [type] '[value]'."
runtime_not_owner_id:  "You are not the owner of [type] #[value]."
runtime_removed:  "Successfully removed [type]."
runtime_removed_from:  "Successfully removed [type] from [name]."
runtime_removed_id:  "Successfully removed [type] #[value]."
runtime_removed_id_from:  "Successfully removed [type] #[value] from [name]."
runtime_removed_name:  "Successfully removed [type] '[value]'."
runtime_removed_name_from:  "Successfully removed [type] '[value]' from [name]."
runtime_updated:  "Successfully updated [type]."
runtime_updated_id:  "Successfully updated [type] #[value]."
runtime_updated_name:  "Successfully updated [type] '[value]'."
runtime_uploaded:  "Successfully uploaded [type]."
runtime_uploaded_id:  "Successfully uploaded [type] #[value]."
runtime_uploaded_name:  "Successfully uploaded [type] '[value]'."
runtime_user_hasnt_authored:  "[user] hasn't written any [types]."
runtime_user_hasnt_created:  "[user] hasn't created any [types]."
runtime_user_hasnt_edited:  "[user] hasn't edited any [types]."

# One-time-use messages.
runtime_dates_must_be_same_format:  If you give two dates, they must be the same format.
runtime_description_added_admin:  Gave admin permission to [name].
runtime_description_added_reader:  Gave view permission to [name].
runtime_description_added_writer:  Gave edit permission to [name].
runtime_description_copy_success:  Successfully copied the description.
runtime_description_merge_delete_denied:  You don't have permission to delete the old description.
runtime_description_merge_deleted:  "The old description was deleted: [old]"
runtime_description_merge_success:  Successfully merged the descriptions.
runtime_description_move_success:  Successfully moved the description.
runtime_description_private:  That description is private!
runtime_description_removed_admin:  Revoked admin permission for [name].
runtime_description_removed_reader:  Revoked view permission for [name].
runtime_description_removed_writer:  Revoked edit permission for [name].
runtime_destroy_description_not_admin:  Only a description's admins can delete that description.
runtime_duplicate_rank:  "Rank appears twice: '[rank]'"
runtime_image_updated_notes:  "Updated notes on image #[id]."
runtime_image_uploaded:  Uploaded image '[name]'.
runtime_index_no_at_location:  No [types] at [location].
runtime_index_no_by_rss_log:  No [types] have had any recent activity.
runtime_index_no_for_object:  No [types] for this object.
runtime_index_no_for_user:  No [types] for [user].
runtime_index_no_in_species_list:  No [types] in [name].
runtime_index_no_inside_observation:  Observation #[id] has no [types].
runtime_index_no_of_children:  There are no [types] for children of [name].
runtime_index_no_of_name:  There are no [types] of [name].
runtime_index_no_of_parents:  There are no [types] for parents of [name].
runtime_index_no_with:  There are no [types] with [attachments].
runtime_invalid_for_rank:  "Name is invalid for the rank [rank]: '[name]'"
runtime_invalid_rank:  "Ranks are out of order: '[line_rank]' is the same as or below '[rank]'"
runtime_location_merge_failed:  Failed to merge observation [name].
runtime_login_failed:  Login unsuccessful.
runtime_login_success:  Login successful.
runtime_name_in_use_with_notes:  The name '[name]' is already in use and [other] has notes.
runtime_no_conditions:  You didn't specify any conditions!
runtime_no_upload_image:  Had problems uploading image '[name]'.
runtime_object_deleted:  This object has been deleted.
runtime_object_not_in_index:  "Can't find [type] #[id] in the results of the current search or index."
runtime_pivotal_getting_token:  Couldn't get access token from Pivotal.
runtime_pivotal_getting_stories:  Couldn't get stories from Pivotal.
runtime_pivotal_parsing_story:  Error parsing one or more stories from Pivotal.  Ignored them.
runtime_prefs_password_no_match:  Password and confirmation did not match.
runtime_refine_search_expect_id:  "Invalid [type] in '[field]' -- expected a valid id."
runtime_refine_search_field_required:  "Missing required field '[field]'."
runtime_refine_search_invalid_rss_type:  "Invalid object type '[value]'."
runtime_refine_search_model_not_supported:  Sorry, '[:app_refine_search]' doesn't support [type] queries yet.
runtime_refine_search_object_not_found:  "Couldn't find [type] matching '[value]' in '[field]'."
runtime_search_has_expired:  Your query has expired, please try again.
runtime_show_observation_success:  Successfully changed vote.
runtime_unable_to_transfer_name:  Unable to transfer [name] to another synonym.

# These shouldn't need translating, but you are free to override if you need to.
runtime_ask_observation_question_success:  "[:runtime_delivered_question]"
runtime_ask_user_question_success:  "[:runtime_delivered_question]"
runtime_ask_webmaster_need_address:  "[:runtime_missing(field=:email_address)]"
runtime_ask_webmaster_need_content:  "[:runtime_missing(field=:comment)]"
runtime_ask_webmaster_success:  "[:runtime_delivered_message]"
runtime_commercial_inquiry_success:  "[:runtime_delivered_message]"
runtime_description_adjust_permissions_denied:  "[:runtime_description_must_be_admin]"
runtime_description_adjust_permissions_no_changes:  "[:runtime_no_changes]"
runtime_description_publish_denied:  "[:runtime_description_must_be_admin]"
runtime_destroy_description_success:  "[:runtime_destroyed(type=:description)]"
runtime_destroy_naming_denied:  "[:runtime_not_owner_id(type=:naming,value=id)]"
runtime_destroy_naming_failed:  "[:runtime_no_destroy_id(type=:naming,value=id)]"
runtime_destroy_naming_success:  "[:runtime_destroyed_id(type=:naming,value=id)]"
runtime_destroy_observation_denied:  "[:runtime_not_owner_id(type=:observation,value=id)]"
runtime_destroy_observation_failed:  "[:runtime_no_destroy_id(type=:observation,value=id)]"
runtime_destroy_observation_success:  "[:runtime_destroyed_id(type=:observation,value=id)]"
runtime_edit_location_description_no_change:  "[:runtime_no_changes]"
runtime_edit_location_description_success:  "[:runtime_updated_id(type=:location_description,value=id)]"
runtime_edit_location_no_change:  "[:runtime_no_changes]"
runtime_edit_location_success:  "[:runtime_updated_id(type=:location,value=id)]"
runtime_edit_name_description_no_change:  "[:runtime_no_changes]"
runtime_edit_name_description_success:  "[:runtime_updated_id(type=:name_description,value=id)]"
runtime_edit_name_merge_success:  "[:runtime_merge_success(type=:name,this=this,that=that)]"
runtime_edit_name_no_change:  "[:runtime_no_changes]"
runtime_edit_name_success:  "[:runtime_updated_name(type=:name,value=name)]"
runtime_edit_observation_success:  "[:runtime_updated_id(type=:observation,value=id)]"
runtime_edit_project_success:  "[:runtime_updated_id(type=:project,value=id)]"
runtime_email_new_password_failed:  "[:runtime_no_match_name(type=:user,value=user)]"
runtime_form_comments_create_success:  "[:runtime_created_id(type=:comment,value=id)]"
runtime_form_comments_destroy_failed:  "[:runtime_no_destroy_id(type=:comment,value=id)]"
runtime_form_comments_destroy_success:  "[:runtime_destroyed_id(type=:comment,value=id)]"
runtime_form_comments_edit_success:  "[:runtime_updated_id(type=:comment,value=id)]"
runtime_image_destroy_failed:  "[:runtime_no_destroy_id(type=:image,value=id)]"
runtime_image_destroy_success:  "[:runtime_destroyed_id(type=:image,value=id)]"
runtime_image_edit_success:  "[:runtime_updated_id(type=:image,value=id)]"
runtime_image_invalid_image:  "[:runtime_invalid(type=:image,value=name)]"
runtime_image_remove_success:  "[:runtime_removed_id(type=:image,value=id)]"
runtime_image_resize_denied:  "[:runtime_admin_only]"
runtime_image_reuse_invalid_id:  "[:runtime_no_match_id(type=:image,value=id)]"
runtime_image_reuse_success:  "[:runtime_added_id(type=:image,value=id)]"
runtime_image_uploaded_image:  "[:runtime_uploaded_name(type=:image,value=name)]"
runtime_invalid_classification:  "[:runtime_no_parse(value=text)]"
runtime_invalid_name:  "[:runtime_invalid(type=:name,value=name)]"
runtime_invalid_source_type:  "[:runtime_invalid(type=:source)]"
runtime_list_location_no_matches:  "[:runtime_no_matches(type=:location)]"
runtime_location_already_exists:  "[:runtime_already_exists(type=:location,value=name)]"
runtime_location_description_index_no_matches:  "[:runtime_no_matches(type=:location_description)]"
runtime_location_description_success:  "[:runtime_created_id(type=:location_description,value=id)]"
runtime_location_descriptions_by_author_error:  "[:runtime_user_hasnt_authored(type=:location_description)]"
runtime_location_descriptions_by_editor_error:  "[:runtime_user_hasnt_edited(type=:location_description)]"
runtime_location_merge_success:  "[:runtime_merge_success(type=:location,this=this,that=that)]"
runtime_location_success:  "[:runtime_created_id(type=:location,value=id)]"
runtime_map_locations_no_matches:  "[:runtime_no_matches_pattern(type=:location,value=pattern)]"
runtime_merge_locations_warning:  "[:runtime_merge_warning(type=:location)]"
runtime_merge_names_warning:  "[:runtime_merge_warning(type=:name)]"
runtime_name_already_used:  "[:runtime_already_used(type=:name,value=name)]"
runtime_name_create_already_exists:  "[:runtime_already_exists(type=:name,value=name)]"
runtime_name_deprecate_must_choose:  "[:runtime_missing(field=:preferred_name)]"
runtime_name_description_index_no_matches:  "[:runtime_no_matches(type=:name_description)]"
runtime_name_description_success:  "[:runtime_created_id(type=:name_description,value=id)]"
runtime_name_descriptions_by_author_error:  "[:runtime_user_hasnt_authored(type=:name_description)]"
runtime_name_descriptions_by_editor_error:  "[:runtime_user_hasnt_edited(type=:name_description)]"
runtime_name_index_no_matches:  "[:runtime_no_matches(type=:name)]"
runtime_names_by_editor_error:  "[:runtime_user_hasnt_edited(type=:name)]"
runtime_names_by_user_error:  "[:runtime_user_hasnt_created(type=:name)]"
runtime_naming_created:  "[:runtime_created(type=:naming)]"
runtime_naming_updated:  "[:runtime_updated(type=:naming)]"
runtime_no_more_search_objects:  "[:runtime_no_more]"
runtime_no_save_naming:  "[:runtime_no_save(type=:naming)]"
runtime_no_save_observation:  "[:runtime_no_save(type=:observation)]"
runtime_object_no_match:  "[:runtime_no_match_name(value=match)]"
runtime_observation_success:  "[:runtime_created_id(type=:observation,value=id)]"
runtime_prefs_success:  "[:runtime_updated(type=:preferences)]"
runtime_profile_invalid_image:  "[:runtime_invalid(type=:image,value=name)]"
runtime_profile_removed_image:  "[:runtime_removed_from(type=:image,name=:profile)]"
runtime_profile_success:  "[:runtime_updated(type=:profile)]"
runtime_profile_uploaded_image:  "[:runtime_uploaded_name(type=:image,value=name)]"
runtime_species_list_add_observation_success:  "[:runtime_added_id_to(type=:observation,value=id)]"
runtime_species_list_create_success:  "[:runtime_created_id(type=:species_list,value=id)]"
runtime_species_list_destroy_success:  "[:runtime_destroyed_id(type=:species_list,value=id)]"
runtime_species_list_edit_success:  "[:runtime_updated_id(type=:species_list,value=id)]"
runtime_species_list_remove_observation_success:  "[:runtime_removed_id_from(type=:observation,value=id)]"
runtime_unable_to_create_name:  "[:runtime_no_create_name(type=:name,value=name)]"
runtime_unable_to_save_changes:  "[:runtime_no_save(type=:changes)]"
runtime_unrecognized_rank:  "[:runtime_invalid(type=rank,value=rank)]"
runtime_user_bad_rank:  "[:runtime_invalid(type=rank,value=rank)]"

# Longer messages.
runtime_ask_webmaster_antispam:  >
  To cut down on robot spam, questions from unregistered users cannot contain
  'http:' or HTML markup.

runtime_create_draft_create_denied:  >
  You do not have permission to create a draft for the project [title].

runtime_create_naming_already_proposed:  >
  Someone has already proposed that name.  If you would like to comment on it,
  try posting a comment instead.

runtime_description_already_default:  >
  This description is already the default description!

runtime_description_foreign_read_wrong:  >
  Descriptions from other servers must be readable by the general public.

runtime_description_foreign_write_wrong:  >
  Descriptions from other servers must be read-only.

runtime_description_make_default_only_public:  >
  You are only allowed to make public descriptions the default. All users must
  be allowed at least to read it.

runtime_description_merge_conflict:  >
  There is a conflict.  Please merge the two descriptions by hand.  (Look at
  the text fields below.  Where there is a conflict both descriptions have
  been entered one on top of the other separated by a line.)  You may cancel
  the operation at any time without making any changes.  When you are finished,
  be sure to destroy the old description.

runtime_description_move_invalid_classification:  >
  The classification has incorrect syntax.  We can't save a new description
  with it like this, so we've temporarily blanked out the classification field
  until you correct it.

runtime_description_must_be_admin:  >
  You must be an admin for a description to use this feature.

runtime_description_permissions_fixed:  >
  This type of description has fixed permissions.

runtime_description_public_read_wrong:  >
  Public descriptions must be readable by the general public.

runtime_description_public_write_wrong:  >
  Public descriptions must be writable by the general public.

runtime_description_user_not_found:  >
  User or Group "[name]" not found!

runtime_destroy_naming_someone_else:  >
  Sorry, someone else has given this their strongest positive vote.  You are
  free to propose alternate names, but we can no longer let you delete this
  name.

runtime_edit_description_denied:  >
  You have not been given permission to edit this description.

runtime_edit_naming_someone_else:  >
  Sorry, someone else has given this a positive vote, so we had to create a new
  name proposal to accomodate your changes.

runtime_email_new_password_success:  >
  Password successfully changed.  New password has been sent to your email
  account.

runtime_form_names_misspelling_bad:  >
  The alternate spelling you entered is not recognized.

runtime_form_names_misspelling_same:  >
  Correct spelling and incorrect spelling are the same!

runtime_image_changed_your_image:  >
  Changed your profile image to image #[id].

runtime_image_move_failed:  >
  Something went wrong on the server and we failed to save image #[id].  Please
  try again.

runtime_image_process_failed:  >
  Something went wrong on the server and we failed to process image #[id].
  Please try again.

runtime_image_remove_denied:  >
  You do not have permission to remove images from this observation.

runtime_image_remove_missing:  >
  This observation doesn't have that image!

runtime_merge_warning:  >
  Because it can be destructive, only the admin can merge existing [types].
  An email requesting the proposed merge has been sent to the admins.

runtime_object_not_found:  >
  Sorry, the [type] you tried to display (id #[id]) no longer exists.  Someone
  has either deleted it or merged it into another.

runtime_profile_must_define:  >
  You must define this location before we can make it your primary location.
  Any other changes to your profile have been saved.

runtime_refine_search_bad_google_minus:  >
  Invalid search syntax in [name] at '[value]'.  Please only use the minus sign
  syntax at the beginning of the line.

runtime_reverify_already_verified:  >
  Your account is already verified!  Please log in.

runtime_reverify_sent:  >
  Another verification email was sent to your email account.

runtime_show_description_denied:  >
  You have not been given permission to see this description.

runtime_show_draft_denied:  >
  Permission denied: only project members can view drafts in progress.

runtime_signup_success:  >
  Signup successful.  Verification sent to your email account.

runtime_species_list_need_to_use_bulk:  >
  Synonyms can only be created from the [:name_bulk_title] page.

################################################################################

# DEBUGGING STUFF -- this doesn't need translating

# observer/recalc
observer_recalc_old_name:  "old_name: [name]"
observer_recalc_new_name:  "new_name: [name]"
observer_recalc_caught_error:  "Caught exception: [error]"

# observer/status
system_status_browser_status_size:  Browser status cache size
system_status_clear_caches:  Clear Caches
system_status_gc:  GC
system_status_textile_name_size:  Textile name cache size
system_status_title:  Server Status

################################################################################

# DISABLE SYNTAX CHECKER

# Don't translate this, just correct the order in which dates are given.
date_helper_order: [:day, :month, :year]

# These two use UNIX date format codes.  Ask MO developers for help if you
# aren't familiar with the syntax.
date_helper_date_formats:
  default: "%Y-%m-%d"
  short: "%e %b"
  long: "%e %B, %Y"

date_helper_time_formats:
  default: "%a, %d %b %Y %H:%M:%S %z"
  short: "%d %b, %H:%M"
  long: "%d %B, %Y %H:%M"

# Added at the end of date if not using a 24 hours system.
date_helper_am: am
date_helper_pm: pm

# How to render a number.
number_helper_separator: ","  # Between integer part and fraction.
number_helper_delimiter: "."  # Between each group of thousands.

# How to render a list.
array_connector: 'et'           # Word between final two items.
array_skip_last_comma: 'false'  # Include comma between final two items?

# Month and day names.  Be careful not to change spacing or delete any lines.
date_helper_month_names:
  -
    -
  - Janvier
  - Février
  - Mars
  - Avril
  - Mai
  - Juin
  - Juillet
  - Août
  - Septembre
  - Octobre
  - Novembre
  - Décembre

date_helper_abbr_month_names:
  -
    -
  - Jan
  - Fev
  - Mar
  - Avr
  - Mai
  - Jui
  - Jul
  - Aoû
  - Sep
  - Oct
  - Nov
  - Déc

date_helper_day_names:
  - Dimanche
  - Lundi
  - Mardi
  - Mercredi
  - Jeudi
  - Vendredi
  - Samedi

date_helper_abbr_day_names:
  - Dim
  - Lun
  - Mar
  - Mer
  - Jeu
  - Ven
  - Sam


################################################################################

# Extra/unnecessary translations: