diff --git a/config/locales/en.yml b/config/locales/en.yml index 5f84d4b3..023bfc74 100644 --- a/config/locales/en.yml +++ b/config/locales/en.yml @@ -95,9 +95,8 @@ en: action: Action actions: Actions actions_midsentence: - one: action - other: actions - zero: actions + one: actions + other: action add: Add ajaxError: There was an error retrieving from server back: Back @@ -109,9 +108,8 @@ en: contribute: Contribute create: Create days_midsentence: - one: day - other: days - zero: days + one: days + other: day deferred: deferred description: Description drag_handle: DRAG @@ -130,9 +128,8 @@ en: none: None not_available_abbr: n/a note: - one: 1 note - other: "%{count} notes" - zero: no notes + one: no notes + other: 1 note notes: Notes numbered_step: Step %{number} ok: Ok @@ -204,7 +201,8 @@ en: some: Some errors occurred during import file_blank: File can't be blank invalid_csv: "Invalid CSV: could not read headers: %{e}" - save_error: "Could not save uploaded CSV (%{path_and_file}). Can Tracks write to the upload directory? %{e}" + save_error: "Could not save uploaded CSV (%{path_and_file}). Can Tracks write\ + \ to the upload directory? %{e}" map_title: Map fields to be imported header: Importing data submit: Import @@ -215,21 +213,29 @@ en: projects_count: "%{count} Projects imported" todos_count: "%{count} Todos imported" yaml_disabled: "YAML loading is disabled" - yaml_warning: "%{warning}: all your current data will be destroyed before importing the YAML file, so if you have access to the database, we strongly recommend backing up the database right now in case that anything goes wrong." - paste_field: "Paste the contents of the YAML file you exported into the text box below:" + yaml_warning: "%{warning}: all your current data will be destroyed before importing\ + \ the YAML file, so if you have access to the database, we strongly recommend\ + \ backing up the database right now in case that anything goes wrong." + paste_field: "Paste the contents of the YAML file you exported into the text\ + \ box below:" warning: Beware export: page_title: Tracks::Export title: Exporting data format_header: "You can choose between the following formats:" yaml_description: "%{yaml}: Best for exporting data." - yaml_link_description: YAML file containing all your actions, contexts, projects, tags and notes - yaml_experimental: "Please note that importing YAML files is currently supported only in experimentally. Do not rely on it for backing up critical data." - csv_description: "%{csv}: Best for importing into spreadsheet or data analysis software" - csv_actions_description: CSV file containing all of your actions, with named contexts and projects + yaml_link_description: YAML file containing all your actions, contexts, projects, + tags and notes + yaml_experimental: "Please note that importing YAML files is currently supported\ + \ only in experimentally. Do not rely on it for backing up critical data." + csv_description: "%{csv}: Best for importing into spreadsheet or data analysis\ + \ software" + csv_actions_description: CSV file containing all of your actions, with named + contexts and projects csv_notes_description: CSV file containing all your notes xml_description: "%{xml}: Best for importing or repurposing the data" - xml_link_description: XML file containing all your actions, contexts, projects, tags and notes + xml_link_description: XML file containing all your actions, contexts, projects, + tags and notes download_link: Download link yaml_link_title: YAML file csv_actions_title: CSV file (actions, contexts and projects) @@ -310,13 +316,11 @@ en: other: almost %{count} years half_a_minute: half a minute less_than_x_minutes: - one: less than a minute - other: less than %{count} minutes - zero: less than 1 minute + one: less than 1 minute + other: less than a minute less_than_x_seconds: one: less than 1 second - other: less than %{count} seconds - zero: less than 1 second + other: less than 1 second over_x_years: one: over 1 year other: over %{count} years @@ -407,52 +411,81 @@ en: integrations: sections: automatic_email: Automatically Email Yourself Upcoming Actions - message_gateway: Integrate Tracks with an email server to be able to send an action through email to Tracks + message_gateway: Integrate Tracks with an email server to be able to send an + action through email to Tracks mailgun: Send emails to Tracks with Mailgun email_rich: Rich Todo Message email format opensearch_description: Search in Tracks title: Integrations - intro: "Tracks can be integrated with a number of other tools... whatever it takes to help you get things done! This page has information on setting up some of these. Not all of these are applicable to all platforms, and some require more technical knowledge than others. See also %{documentation_link}" + intro: "Tracks can be integrated with a number of other tools… whatever it takes\ + \ to help you get things done! This page has information on setting up some\ + \ of these. Not all of these are applicable to all platforms, and some require\ + \ more technical knowledge than others. See also %{documentation_link}" developer_documentation_link: developer documentation for Tracks contents_header: "Contents:" - add_your_own: Do you have one of your own to add? %{tell_us_link} and we may include it on this page in a future versions of Tracks. + add_your_own: Do you have one of your own to add? %{tell_us_link} and we may include + it on this page in a future versions of Tracks. tell_us_link_text: Tell us about it in our issue queue - cron_1: If you enter the following entry to your crontab, you will receive email every day around 5 AM with a list of the upcoming actions which are due within the next 7 days. - cron_2: You can of course use other text %{feeds_link} – why not email a list of next actions in a particular project to a group of colleagues who are working on the project? + cron_1: If you enter the following entry to your crontab, you will receive email + every day around 5 AM with a list of the upcoming actions which are due within + the next 7 days. + cron_2: You can of course use other text %{feeds_link} – why not email a list + of next actions in a particular project to a group of colleagues who are working + on the project? cron_email_subject: Tracks actions due in the next 7 days feeds_link_text: feeds provided by Tracks message_gateway: - description: 'If Tracks is running on the same server as your mail server, you can use the integrated mail handler built into Tracks. Steps to set it up:' - rich_api_tip: 'You can also use the Rich Todo API to send in tasks like "do laundry @ Home" or "Call Bill > project X". The subject of the message will fill description, context, and project, while the body will populate the tasks''s note.' - configuration: "You may need to configure your %{site_yml} to tell the message gateway to look at the %{to_name} field or %{from_name} field to lookup Tracks' user from the email address in that field." - one_user_configuration: "You can also send all email to a specific Tracks user. Configure mail_dispatch in site.yml to %{single_user_value} and pass the login of the user in the pipe command: %{code}" + description: 'If Tracks is running on the same server as your mail server, you + can use the integrated mail handler built into Tracks. Steps to set it up:' + rich_api_tip: 'You can also use the Rich Todo API to send in tasks like "do + laundry @ Home" or "Call Bill > project X". The subject of the message will + fill description, context, and project, while the body will populate the tasks''s + note.' + configuration: "You may need to configure your %{site_yml} to tell the message\ + \ gateway to look at the %{to_name} field or %{from_name} field to lookup\ + \ Tracks' user from the email address in that field." + one_user_configuration: "You can also send all email to a specific Tracks user.\ + \ Configure mail_dispatch in site.yml to %{single_user_value} and pass the\ + \ login of the user in the pipe command: %{code}" instructions: - '1': 'Go to %{preferences_link} and set your "%{sms_email_name}" and "%{sms_context_name}" for todos sent in via email (which could come from an SMS message)' - '2': In sendmail/qmail/postfix/whatever, set up an email address alias to pipe messages to %{command} + '1': 'Go to %{preferences_link} and set your "%{sms_email_name}" and "%{sms_context_name}" + for todos sent in via email (which could come from an SMS message)' + '2': In sendmail/qmail/postfix/whatever, set up an email address alias to + pipe messages to %{command} '3': Send an email to your newly configured address! mailgun: - description: If you want to email tasks to Tracks, but cannot run a mailserver on the same host, you could use the %{mailgun_link} support built in to Tracks. - conditions: For this to work your Tracks server will need to be reachable from the internet, so that Mailgun can POST data to it. - gateway_instructions: All the comments about the email format from the section above apply to the Mailgun handling, as the data is processed the same way + description: If you want to email tasks to Tracks, but cannot run a mailserver + on the same host, you could use the %{mailgun_link} support built in to Tracks. + conditions: For this to work your Tracks server will need to be reachable from + the internet, so that Mailgun can POST data to it. + gateway_instructions: All the comments about the email format from the section + above apply to the Mailgun handling, as the data is processed the same way instructions: '1': Go to %{mailgun_link} and register for a free account. '2': "Go to 'Routes' in the Mailgun control panel, and add a new route:" 2a: "'Filter expression' should be set to 'catch_all()'" - 2b: "'Action' should be 'forward(\"http://mytracksserver.example.com/mailgun/mime\")'" - '3': 'Go to %{preferences_link} and enter your incoming Mailgun email address (e.g. tracks@user.mailgun.com) in the "%{sms_email_name}" box.' + 2b: "'Action' should be 'forward(\"http://mytracksserver.example.com/mailgun/mime\"\ + )'" + '3': 'Go to %{preferences_link} and enter your incoming Mailgun email address + (e.g. tracks@user.mailgun.com) in the "%{sms_email_name}" box.' '4': 'Select a default context for emails to be put in with "%{sms_context_name}"' '5': "Add your Mailgun API key (not the Public API key) to the Tracks 'site.yml'" - '6': "Update the mailmap in 'site.yml' to define which senders can send emails to which incoming addresses. For example, to send emails from your work and home email accounts to your Tracks Mailgun route, set it up like this: %{code}" + '6': "Update the mailmap in 'site.yml' to define which senders can send emails\ + \ to which incoming addresses. For example, to send emails from your work\ + \ and home email accounts to your Tracks Mailgun route, set it up like this:\ + \ %{code}" email_rich: description: "For both of the above methods, the follow format can be used:" fields_title: "The fields are:" symbol_title: Symbol meaning_title: Meaning - fields_instruction: All symbols are optional, and text up to the first symbol (or end of string) is used as the description of the todo + fields_instruction: All symbols are optional, and text up to the first symbol + (or end of string) is used as the description of the todo field_descriptions: context: The context to place the Todo in project: The project to place the Todo in - due_date: The due date for the Todo (may be 2 digits for day, 4 digits for month-day, or 6 digits for year-month-day) + due_date: The due date for the Todo (may be 2 digits for day, 4 digits for + month-day, or 6 digits for year-month-day) tag: A tag to apply to the Todo – may be used multiple times star: Flag to star the Todo example_names: @@ -464,11 +497,14 @@ en: '2': tag2 help: title: Help - usage: 'You can find information on the usage in the %{manual_link} in the project GitHub wiki.' + usage: 'You can find information on the usage in the %{manual_link} in the project + GitHub wiki.' manual_link_text: User manual - bugs: 'If you encounter a bug or have a feature request, please report it in the %{issue_link}.' + bugs: 'If you encounter a bug or have a feature request, please report it in the + %{issue_link}.' issue_link_text: issue queue - contribute: 'We gladly welcome all contributions to Tracks. Check the %{contribute_link} for further information. You can also come discuss with the community:' + contribute: 'We gladly welcome all contributions to Tracks. Check the %{contribute_link} + for further information. You can also come discuss with the community:' contribute_link_text: project website mailing_list_link_text: Mailing list irc_bullet: '%{irc_link} (also available in %{matrix_link})' @@ -1283,12 +1319,10 @@ en: multi_page_html: Displaying %{model} %{from} - %{to} of %{count} in total single_page: - one: Displaying 1 %{model} - other: Displaying all %{count} %{model} - zero: No %{model} found + one: No %{model} found + other: Displaying 1 %{model} single_page_html: - one: Displaying 1 %{model} - other: Displaying all %{count} %{model} - zero: No %{model} found + one: No %{model} found + other: Displaying 1 %{model} page_gap: "…" previous_label: "← Previous"