-
Importing data
+
<%= I18n.t "data.import.header" %>
-
Please upload your CSV file
+ <%= I18n.t "data.import.upload_csv" %>
<%= form_tag csv_map_data_path, :id => 'upload_form', multipart: true do %>
- Import to:
+ <%= I18n.t "data.import.target_field" %>
<%= select_tag(:import_to, options_for_select([['Projects', 'projects'], ['Todos', 'todos']], 1) ) %>
<%= file_field_tag :file %>
- <%= submit_tag "Upload", :id => "upload_form_submit" %>
+ <%= submit_tag I18n.t("data.import.upload"), :id => "upload_form_submit" %>
<% end %>
diff --git a/app/views/data/index.de.html.erb b/app/views/data/index.de.html.erb
deleted file mode 100644
index fa2140ee..00000000
--- a/app/views/data/index.de.html.erb
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
Daten exportieren
-
Sie können zwischen den folgenden Formaten wählen:
-
- YAML: Für den Daten-Import bevorzugt.Bitte beachten Sie, dass der YAML-Import zur Zeit noch experimentelle Funktionalität darstellt. Nutzen Sie diese Option also nicht. um kritische Daten zu sichern.
- CSV: Am besten für den Export in eine Tabellen-Kalkulation oder ähnliche Auswertungs-Software geeignet
- XML: Am besten für den Daten-Import oder automatische Weiterverarbeitung
-
-
-
-
-
- Beschreibung
- Download link
-
-
- YAML-Datei mit all Ihren Aktionen, Umgebungen, Projekten, Tags und Notizen
- <%= link_to "YAML Datei", :controller => 'data', :action => 'yaml_export' %>
-
-
- CSV-Datei mit all Ihren Aktionen, benannten Umgebungen und Projekten
- <%= link_to "CSV Dile (Aktionen, Umgebungen und Projekte)", :controller => 'data', :action => 'csv_actions' %>
-
-
- CSV-Datei mit all Ihren Notizen
- <%= link_to "CSV Datei (nur Notizen)", :controller => 'data', :action => 'csv_notes' %>
-
-
- XML-Datei mit all Ihren Aktionen, Umgebungen, Projekten, Tags und Notizen
- <%= link_to "XML file (actions only)", :controller => 'data', :action => 'xml_export' %>
-
-
-
-
diff --git a/app/views/data/index.en.html.erb b/app/views/data/index.en.html.erb
deleted file mode 100644
index 59052c3f..00000000
--- a/app/views/data/index.en.html.erb
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
Exporting data
-
You can choose between the following formats:
-
- YAML: Best for exporting data. Please note that importing YAML files is currently supported only in experimentally. Do not rely on it for backing up critical data.
- CSV: Best for importing into spreadsheet or data analysis software
- XML: Best for importing or repurposing the data
-
-
-
-
-
- Description
- Download link
-
-
- YAML file containing all your actions, contexts, projects, tags and notes
- <%= link_to "YAML file", data_yaml_export_path %>
-
-
- CSV file containing all of your actions, with named contexts and projects
- <%= link_to "CSV file (actions, contexts and projects)", data_csv_actions_path %>
-
-
- CSV file containing all your notes
- <%= link_to "CSV file (notes only)", data_csv_notes_path %>
-
-
- XML file containing all your actions, contexts, projects, tags and notes
- <%= link_to "XML file (actions only)", data_xml_export_path %>
-
-
-
-
diff --git a/app/views/data/index.es.html.erb b/app/views/data/index.es.html.erb
deleted file mode 100644
index 84455349..00000000
--- a/app/views/data/index.es.html.erb
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
Exportar datos
-
Puede escoger entre los siguientes formatos:
-
- YAML: Mejor formato para exportar datos. Por favor tenga en cuenta que la importación de ficheros YAML actualmente esta soportada de forma experimental. No confíe en este formato para hacer copias de seguridad de datos importantes.
- CSV: Mejor formato para importar en una hoja de cálculo o en programas de análisis de datos.
- XML: Mejor formato para transformar los datos a otro formato
-
-
-
-
-
- Descripción
- Enlace de descarga
-
-
- Fichero YAML con todas sus acciones, contextos, proyectos, etiquetas y notas
- <%= link_to "Fichero YAML", data_yaml_export_path %>
-
-
- Fichero CSV con todas sus acciones, con contextos por nombre y proyectos
- <%= link_to "Fichero CSV (acciones, contextos y proyectos)", data_csv_actions_path %>
-
-
- Fichero CSV con todas sus notas
- <%= link_to "Fichero CSV (sólo notas)", data_csv_notes_path %>
-
-
- Fichero XML con todas sus acciones, contextos, proyectos, etiquetas y notas
- <%= link_to "Fichero XML", data_xml_export_path %>
-
-
-
-
diff --git a/app/views/data/index.html.erb b/app/views/data/index.html.erb
new file mode 100644
index 00000000..879e3bb8
--- /dev/null
+++ b/app/views/data/index.html.erb
@@ -0,0 +1,36 @@
+
+
+
+
<%= I18n.t "data.export.title" %>
+
<%= I18n.t "data.export.format_header" %>
+
+ <%= raw I18n.t "data.export.yaml_description", yaml: "" + I18n.t("data.yaml") + " " %><%= I18n.t "data.export.yaml_experimental" %>
+ <%= raw I18n.t "data.export.csv_description", csv: "" + I18n.t("data.csv") + " " %>
+ <%= raw I18n.t "data.export.xml_description", xml: "" + I18n.t("data.xml") + " " %>
+
+
+
+
+
+ <%= I18n.t "common.description" %>
+ <%= I18n.t "data.export.download_link" %>
+
+
+ <%= I18n.t "data.export.yaml_link_description" %>
+ <%= link_to I18n.t("data.export.yaml_link_title"), data_yaml_export_path %>
+
+
+ <%= I18n.t "data.export.csv_actions_description" %>
+ <%= link_to I18n.t("data.export.csv_actions_title"), data_csv_actions_path %>
+
+
+ <%= I18n.t "data.export.csv_notes_description" %>
+ <%= link_to I18n.t("data.export.csv_notes_title"), data_csv_notes_path %>
+
+
+ <%= I18n.t "data.export.xml_link_description" %>
+ <%= link_to I18n.t('data.export.xml_link_title'), data_xml_export_path %>
+
+
+
+
diff --git a/app/views/data/yaml_form.de.html.erb b/app/views/data/yaml_form.de.html.erb
deleted file mode 100644
index a1827241..00000000
--- a/app/views/data/yaml_form.de.html.erb
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
-
Vorsicht : vor dem Import der YAML Datei werden alle Daten in Ihrer Datenbank gelöscht.
- Falls Sie entsprechenden Zugriff auf Ihre Datenbank haben, empfiehlt es sich, ein Backup anzulegen,
- bevor Sie fortfahren.
-
-
Fügen Sie den Inhalt der kopierten YAML Datei in das untenstehende Formular ein:
-
-
- <%= form_for :import, @import, :url => {:controller => 'data', :action => 'yaml_import'} do |f| %>
- <%= f.text_area :yaml %>
-
- <% end %>
-
-
-
diff --git a/app/views/data/yaml_form.en.html.erb b/app/views/data/yaml_form.en.html.erb
deleted file mode 100644
index c7f04165..00000000
--- a/app/views/data/yaml_form.en.html.erb
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
-
Beware : 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 the contents of the YAML file you exported into the text box below:
-
-
- <%= form_for :import, @import, :url => {:controller => 'data', :action => 'yaml_import'} do |f| %>
- <%= f.text_area :yaml %>
-
- <% end %>
-
-
-
diff --git a/app/views/data/yaml_form.html.erb b/app/views/data/yaml_form.html.erb
new file mode 100644
index 00000000..62e43fc0
--- /dev/null
+++ b/app/views/data/yaml_form.html.erb
@@ -0,0 +1,14 @@
+
+
+
+
<%= raw I18n.t "data.import.yaml_warning", warning: '' + I18n.t('data.import.warning') + ' ' %>
+
<%= I18n.t "data.import.paste_field" %>
+
+
+ <%= form_for :import, @import, :url => {:controller => 'data', :action => 'yaml_import'} do |f| %>
+ <%= f.text_area :yaml %>
+
+ <% end %>
+
+
+
diff --git a/app/views/data/yaml_import.html.erb b/app/views/data/yaml_import.html.erb
index fff0144e..15a77c95 100644
--- a/app/views/data/yaml_import.html.erb
+++ b/app/views/data/yaml_import.html.erb
@@ -1,5 +1,5 @@
<% if !(@errmessage == '') %>
-
<%= t('data.import_errors') %>:
<%= @errmessage %>
+
<%= t('data.import.errors.some') %>:
<%= @errmessage %>
<% else %>
-
<%= t('data.import_successful') %>
+
<%= t('data.import.successful') %>
<% end %>
diff --git a/app/views/integrations/index.de.html.erb b/app/views/integrations/index.de.html.erb
deleted file mode 100644
index 1255e8a5..00000000
--- a/app/views/integrations/index.de.html.erb
+++ /dev/null
@@ -1,51 +0,0 @@
-<% has_contexts = !current_user.contexts.empty? -%>
-
Integration
-
Tracks kann mit verschiedenen Werkzeugen zusammenarbeiten...
- was immer Sie brauchen, um Ihre Aufgaben zu erledigen!
- Auf dieser Seite finden Sie Informationen, um einige dieser Werkzeuge einzurichten.
- Diese Beispiele sind nicht unbedingt auf Ihre Umgebung anwendbar oder bedürfen mehr
- technisches Wissen als andere.
- Weitere Informationen finden Sie in der <%= link_to "Entwickler Documentation der Tracks' REST API", url_for(:action => 'rest_api') %> (englisch).
-
Inhalt:
-
-
Sie haben weitere Beispiele?
- Berichten Sie uns
- in unserem Tipps&Tricks Forum , damit wir es für die nächsten Versionen berücksichtigen können.
-
-
-
-
Automatically Email Yourself Upcoming Actions
-
-
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.
-
-
-
-
You can of course use other text <%= link_to 'feeds provided by Tracks', feeds_path %> -- why not email a list of next actions in a particular project to a group of colleagues who are working on the project?
-
-
-
Integrated email/SMS receiver
-
- 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:
-
-
-
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.
-
-
- You may need to configure your site.yml to tell the message gateway to look at the to: field or from: field to
- lookup Tracks' user from the email address in that field.
-
You can also send all email to a specific Tracks user. Configure mail_dispatch in site.yml to single_user and pass the login of the user:
-
TRACKS_MAIL_RECEIVER=<%=current_user.login%> /PATH/TO/TRACKS/bin/rails r -e production 'MessageGateway.receive(STDIN.read)'
-
diff --git a/app/views/integrations/index.en.html.erb b/app/views/integrations/index.en.html.erb
deleted file mode 100644
index b61350cf..00000000
--- a/app/views/integrations/index.en.html.erb
+++ /dev/null
@@ -1,119 +0,0 @@
-<% has_contexts = !current_user.contexts.empty? -%>
-
Integrations
-
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 <%= link_to "developer documentation for Tracks' REST API", url_for(:action => 'rest_api') %>.
-
Contents:
-
-
Do you have one of your own to add?
- Tell us about
- it in our Tips and Tricks forum and we may include it on this page in a future versions of Tracks.
-
-
-
-
Automatically Email Yourself Upcoming Actions
-
-
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.
-
-
-
-
You can of course use other text <%= link_to 'feeds provided by Tracks', feeds_path %> -- why not email a list of next actions in a particular project to a group of colleagues who are working on the project?
-
-
-
Integrated email/SMS receiver
-
- 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:
-
-
-
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.
-
-
- You may need to configure your site.yml to tell the message gateway to look at the to: field or from: field to
- lookup Tracks' user from the email address in that field.
-
You can also send all email to a specific Tracks user. Configure mail_dispatch in site.yml to single_user and pass the login of the user:
-
TRACKS_MAIL_RECEIVER=<%=current_user.login%> /PATH/TO/TRACKS/bin/rails r -e production 'MessageGateway.receive(STDIN.read)'
-
-
-
-
Send emails to Tracks with Mailgun
-
-If you want to email tasks to Tracks, but cannot run a mailserver on the same host,
-you could use the Mailgun support built in to Tracks.
-
-
-For this to work your Tracks server will need to be reachable from the internet, so
-that Mailgun can POST data to it.
-
-
-
All the comments about the email format from the section above apply to the
-Mailgun handling, as the data is processed the same way
-
-
-
Rich Todo Message Format
-
For both of the above methods, the follow format can be used:
-
my awesome todo @context ~project <131012 >131009 #tag1 #tag2 *
-
The fields are:
-
-
- Symbol Meaning
-
-
- @ The context to place the Todo in
-
-
- ~ The project to place the Todo in
-
-
- < The due date for the Todo (may be 2 digits for day, 4 digits for month-day, or 6 digits for year-month-day)
-
-
- > The due date for the Todo (may be 2 digits for day, 4 digits for month-day, or 6 digits for year-month-day)
-
-
- # A tag to apply to the Todo - may be used multiple times
-
-
- * Flag to star the Todo
-
-
-
All symbols are optional, and text up to the first symbol (or end of string) is used as the description of the todo
diff --git a/app/views/integrations/index.html.erb b/app/views/integrations/index.html.erb
new file mode 100644
index 00000000..d619d323
--- /dev/null
+++ b/app/views/integrations/index.html.erb
@@ -0,0 +1,85 @@
+<% has_contexts = !current_user.contexts.empty? -%>
+
<%= I18n.t 'integrations.title' %>
+
<%= raw I18n.t 'integrations.intro', documentation_link: link_to(I18n.t('integrations.developer_documentation_link'), url_for(:action => 'rest_api')) %>
+
<%= I18n.t 'integrations.contents_header' %>
+
+
<%= raw I18n.t 'integrations.add_your_own', tell_us_link: link_to(I18n.t('integrations.tell_us_link_text'), 'https://github.com/TracksApp/tracks/issues') %>
+
+
+
<%= I18n.t 'integrations.sections.automatic_email' %>
+
+
<%= I18n.t 'integrations.cron_1' %>
+
+
+
+
<%= raw I18n.t 'integrations.cron_2', feeds_link: link_to(I18n.t('integrations.feeds_link_text'), feeds_path) %>
+
+
+
<%= I18n.t 'integrations.sections.message_gateway' %>
+
<%= I18n.t 'integrations.message_gateway.description' %>
+
+
<%= I18n.t 'integrations.message_gateway.rich_api_tip' %>
+
<%= raw I18n.t 'integrations.message_gateway.configuration', site_yml: 'site.yml ', to_name: 'to: ', from_name: 'from: ' %>
+
<%= raw I18n.t 'integrations.message_gateway.one_user_configuration', single_user_var_name: 'single_user ', code: "
TRACKS_MAIL_RECEIVER=" + current_user.login + " /PATH/TO/TRACKS/bin/rails r -e production 'MessageGateway.receive(STDIN.read)' " %>
+
+
+
<%= I18n.t 'integrations.sections.mailgun' %>
+
<%= raw I18n.t 'integrations.mailgun.description', mailgun_link: link_to('Mailgun', 'http://www.mailgun.com/') %>
+
<%= I18n.t 'integrations.mailgun.conditions' %>
+
+
<%= I18n.t 'integrations.mailgun.gateway_instructions' %>
+
+
+
<%= I18n.t 'integrations.sections.email_rich' %>
+
<%= I18n.t 'integrations.email_rich.description' %>
+
<%= I18n.t 'integrations.example_names.todo' %> @<%= I18n.t 'integrations.example_names.context' %> ~<%= I18n.t 'integrations.example_names.project' %> <131012 >131009 #<%= I18n.t 'integrations.example_names.tag.1' %> #<%= I18n.t 'integrations.example_names.tag.2' %> *
+
<%= I18n.t 'integrations.email_rich.fields_title' %>
+
+
+ <%= I18n.t 'integrations.email_rich.symbol_title' %> <%= I18n.t 'integrations.email_rich.meaning_title' %>
+
+
+ @ <%= I18n.t 'integrations.email_rich.field_descriptions.context' %>
+
+
+ ~ <%= I18n.t 'integrations.email_rich.field_descriptions.project' %>
+
+
+ < <%= I18n.t 'integrations.email_rich.field_descriptions.due_date' %>
+
+
+ > <%= I18n.t 'integrations.email_rich.field_descriptions.due_date' %>
+
+
+ # <%= I18n.t 'integrations.email_rich.field_descriptions.tag' %>
+
+
+ * <%= I18n.t 'integrations.email_rich.field_descriptions.star' %>
+
+
+
<%= I18n.t 'integrations.email_rich.fields_instruction' %>
diff --git a/app/views/integrations/index.nl.html.erb b/app/views/integrations/index.nl.html.erb
deleted file mode 100644
index dfacaecb..00000000
--- a/app/views/integrations/index.nl.html.erb
+++ /dev/null
@@ -1,52 +0,0 @@
-<% has_contexts = !current_user.contexts.empty? -%>
-
Integratie
-
Tracks kan met een aantal tools worden geïntegreerd...
- Alles om je te helpen om dingen gedaan te krijgen!
- Deze pagina heeft informatie over het tot stand brengen van sommige integratievormen.
- Deze voorbeelden zijn niet altijd voor alle platformen van toepassing en
- sommige voorbeelden vragen meer technische kennis dan anderen
- Zie ook <%= link_to "de documentatie voor ontwikkelaars met Tracks' REST API", url_for(:action => 'rest_api') %>.
-
Inhoud:
-
-
Heb je een tip om hier toe te voegen?
- Vertel ons er over in onze
- Tips and Tricks forum en misschien voegen we jouw tip toe op deze pagina in een toekomstige versie van Tracks.
-
-
-
-
Email jezelf automatisch de acties met een aflopende deadline
-
-
Als je de volgende regel toevoegd aan jouw crontab, dat ontvang je een e-mail op elke dag rond 05:00 met een lijst met acties waarvan de deadline afloopt binnen de komende 7 dagen.
-
-
-
-
Uiteraard kan je ook een andere <%= link_to 'text feed gebruiken die Tracks biedt', feeds_path %> -- bijvoorbeeld een email met een lijst van acties voor een specifiek project naar een groep collega's die werken aan dat project?
-
-
-
Integreer Tracks met een email server om een actie via email naar Tracks te sturen
-
- Als Tracks draait op dezelfde server als jouw mailserver, dan kan je de geïntegreerde mail handler gebruiken van Tracks. Om dit in te stellen:
-
-
-
Je kan ook de Rich Todo API gebruiken om acties te maken zoals "do laundry @ Home"
- of "Call Bill > project X". Het onderwerp van het bericht zal de bijschrijving van de actie vullen,
- de context, en het project, terwijl de body van het bericht de notities van de actie zal vullen.
-
-
- Het kan nodig zijn om jouw site.yml te configureren om de message gateway te laten kijken naar het to: veld of het from: veld om
- de Tracks-gebruiker op te zoeken met het emailadres uit dat veld.
-
Je kan ook alle email naar een specifieke Tracks gebruiker sturen. Stel mail_dispatch in site.yml in op single_user en geeft de login van de gebruiker door:
-
TRACKS_MAIL_RECEIVER=<%=current_user.login%> /PATH/TO/TRACKS/bin/rails r -e production 'MessageGateway.receive(STDIN.read)'
-
diff --git a/app/views/preferences/_date_and_time.html.erb b/app/views/preferences/_date_and_time.html.erb
index ba108cc6..3cd58db6 100644
--- a/app/views/preferences/_date_and_time.html.erb
+++ b/app/views/preferences/_date_and_time.html.erb
@@ -1,8 +1,8 @@
<%= pref_with_text_field('prefs', 'date_format') %>
-
This will result in: <%= l(Time.zone.today, :format => current_user.prefs.date_format) %>
+
<%= I18n.t('preferences.result_in') %> <%= l(Time.zone.today, :format => current_user.prefs.date_format) %>
-Or pick one of the following:
+<%= I18n.t('preferences.pick_one') %>
<% [:default, :short, :long, :longer].each do |format| %>
@@ -14,9 +14,9 @@ Or pick one of the following:
<%= pref_with_text_field('prefs', 'title_date_format') %>
-This will result in: <%= l(Time.zone.today, :format => current_user.prefs.title_date_format) %>
+<%= I18n.t('preferences.result_in') %> <%= l(Time.zone.today, :format => current_user.prefs.title_date_format) %>
-Or pick one of the following:
+<%= I18n.t('preferences.pick_one') %>
<% [:default, :short, :long, :longer].each do |format| %>
diff --git a/config/locales/de.yml b/config/locales/de.yml
index 785ca755..38fafd83 100644
--- a/config/locales/de.yml
+++ b/config/locales/de.yml
@@ -193,10 +193,46 @@ de:
view_link: 'View context: %{name}'
visible_contexts: Sichtbare Kontexte
data:
- import_destination_invalid: Invalid import destination
- import_errors: Beim Import sind Fehler aufgetreten.
- import_successful: Import war erfolgreich.
- invalid_import_destination: Invalid import destination
+ import:
+ errors:
+ invalid_destination: "Invalid import destination: %{e}"
+ some: Beim Import sind Fehler aufgetreten.
+ 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}"
+ map_title: Map fields to be imported
+ header: Importing data
+ submit: Importieren
+ successful: Import war erfolgreich.
+ target_field: "Import to:"
+ upload: Upload
+ upload_csv: Please upload your CSV file
+ projects_count: "%{count} Projects imported"
+ todos_count: "%{count} Todos imported"
+ yaml_disabled: "YAML loading is disabled"
+ yaml_warning: "%{warning}: vor dem Import der YAML Datei werden alle Daten in Ihrer Datenbank gelöscht. Falls Sie entsprechenden Zugriff auf Ihre Datenbank haben, empfiehlt es sich, ein Backup anzulegen, bevor Sie fortfahren."
+ paste_field: "Fügen Sie den Inhalt der kopierten YAML Datei in das untenstehende Formular ein:"
+ warning: Vorsicht
+ export:
+ page_title: Tracks::Export
+ title: Daten exportieren
+ format_header: "Sie können zwischen den folgenden Formaten wählen:"
+ yaml_description: "%{yaml}: Für den Daten-Import bevorzugt."
+ yaml_link_description: YAML-Datei mit all Ihren Aktionen, Umgebungen, Projekten, Tags und Notizen
+ yaml_experimental: "Bitte beachten Sie, dass der YAML-Import zur Zeit noch experimentelle Funktionalität darstellt. Nutzen Sie diese Option also nicht. um kritische Daten zu sichern."
+ csv_description: "%{csv}: Am besten für den Export in eine Tabellen-Kalkulation oder ähnliche Auswertungs-Software geeignet"
+ csv_actions_description: CSV-Datei mit all Ihren Aktionen, benannten Umgebungen und Projekten
+ csv_notes_description: CSV-Datei mit all Ihren Notizen
+ xml_description: "%{xml}: Am besten für den Daten-Import oder automatische Weiterverarbeitung"
+ xml_link_description: XML-Datei mit all Ihren Aktionen, Umgebungen, Projekten, Tags und Notizen
+ download_link: Download link
+ yaml_link_title: YAML Datei
+ csv_actions_title: CSV Dile (Aktionen, Umgebungen und Projekte)
+ csv_notes_title: CSV Datei (nur Notizen)
+ xml_link_title: XML file (actions only)
+ yaml: YAML
+ csv: CSV
+ xml: XML
date:
abbr_day_names:
- So
@@ -362,7 +398,64 @@ de:
submit: Сохранить %{model}
update: Обновить %{model}
integrations:
+ sections:
+ automatic_email: Anstehende Aufgaben automatisch sich via E-Mail zusenden lassen
+ message_gateway: Tracks mit einem Mail-Server integrieren, um Aufgaben via E-Mail zu erstellen
+ mailgun: Send emails to Tracks with Mailgun
+ email_rich: Rich Todo Message email format
opensearch_description: In Tracks suchen
+ opensearch_description: Hae Tracksista
+ title: Integration
+ intro: "Tracks kann mit verschiedenen Werkzeugen zusammenarbeiten... was immer Sie brauchen, um Ihre Aufgaben zu erledigen! Auf dieser Seite finden Sie Informationen, um einige dieser Werkzeuge einzurichten. Diese Beispiele sind nicht unbedingt auf Ihre Umgebung anwendbar oder bedürfen mehr technisches Wissen als andere. Weitere Informationen finden Sie in der %{documentation_link} (englisch)."
+ developer_documentation_link: "Entwickler Documentation der Tracks' REST API"
+ contents_header: "Inhalt:"
+ add_your_own: Sie haben weitere Beispiele? %{tell_us_link}, damit wir es für die nächsten Versionen berücksichtigen können.
+ tell_us_link_text: Berichten Sie uns in unserem 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_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_var_name} and pass the login of the user: %{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}
+ 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
+ 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.domain.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}"
+ 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
+ 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)
+ tag: A tag to apply to the Todo – may be used multiple times
+ star: Flag to star the Todo
+ example_names:
+ todo: my awesome todo
+ context: context
+ project: project
+ tag:
+ 1: tag1
+ 2: tag2
help:
title: Help
usage: 'You can find information on the usage in the %{manual_link} in the project GitHub wiki.'
diff --git a/config/locales/en.yml b/config/locales/en.yml
index a890eb35..3ef5187a 100644
--- a/config/locales/en.yml
+++ b/config/locales/en.yml
@@ -21,6 +21,7 @@ en:
sms_context: Default email context
sms_email: From email
staleness_starts: Start of staleness
+ theme: Theme
time_zone: Time zone
title_date_format: Title date format
verbose_action_descriptors: Show descriptors (context, project) of actions
@@ -42,9 +43,11 @@ en:
tags: Tags
user:
auth_type: Auth type
+ created_at: Created at
display_name: Display name
email: Email address
first_name: First name
+ last_login_at: Last login at
last_name: Last name
login: Login
open_id_url: OpenID URL
@@ -195,10 +198,46 @@ en:
view_link: 'View context: %{name}'
visible_contexts: Visible contexts
data:
- import_destination_invalid: Invalid import destination
- import_errors: Some errors occurred during import
- import_successful: Import was successful.
- invalid_import_destination: Invalid import destination
+ import:
+ errors:
+ invalid_destination: "Invalid import destination: %{e}"
+ 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}"
+ map_title: Map fields to be imported
+ header: Importing data
+ submit: Import
+ successful: Import was successful.
+ target_field: "Import to:"
+ upload: Upload
+ upload_csv: Please upload your CSV file
+ 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:"
+ 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
+ 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
+ download_link: Download link
+ yaml_link_title: YAML file
+ csv_actions_title: CSV file (actions, contexts and projects)
+ csv_notes_title: CSV file (notes only)
+ xml_link_title: XML file (actions only)
+ yaml: YAML
+ csv: CSV
+ xml: XML
date:
abbr_day_names:
- Sun
@@ -366,7 +405,63 @@ en:
submit: Save %{model}
update: Update %{model}
integrations:
- opensearch_description: Search in Tracks
+ 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
+ mailgun: Send emails to Tracks with Mailgun
+ email_rich: Rich Todo Message email format
+ opensearch_description: Hae Tracksista
+ 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}"
+ 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.
+ 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_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_var_name} and pass the login of the user: %{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}
+ 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
+ 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.domain.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}"
+ 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
+ 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)
+ tag: A tag to apply to the Todo – may be used multiple times
+ star: Flag to star the Todo
+ example_names:
+ todo: my awesome todo
+ context: context
+ project: project
+ tag:
+ 1: tag1
+ 2: tag2
help:
title: Help
usage: 'You can find information on the usage in the %{manual_link} in the project GitHub wiki.'
@@ -566,9 +661,11 @@ en:
page_title: TRACKS::Preferences
page_title_edit: TRACKS::Edit Preferences
password_changed: You password has been changed, please log on again.
+ pick_one: 'Or pick one of the following:'
remove_introduction: You can remove your user account here. Note that this is
irreversible and will remove all your data! After removal you will be logged
out.
+ result_in: 'This will result in: '
show_number_completed: Show %{number} completed items
sms_context_none: None
staleness_starts_after: Staleness starts after %{days} days
diff --git a/config/locales/es.yml b/config/locales/es.yml
index 91e4102a..d832b127 100644
--- a/config/locales/es.yml
+++ b/config/locales/es.yml
@@ -191,10 +191,46 @@ es:
view_link: 'View context: %{name}'
visible_contexts: Contextos visible
data:
- import_destination_invalid: Invalid import destination
- import_errors: Han ocurrido algunos errores durante la importación
- import_successful: Importación se realizó correctamente.
- invalid_import_destination: Invalid import destination
+ import:
+ errors:
+ invalid_destination: "Invalid import destination: %{e}"
+ some: Han ocurrido algunos errores durante la importación
+ 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}"
+ map_title: Map fields to be imported
+ header: Importing data
+ submit: Import
+ successful: Importación se realizó correctamente.
+ target_field: "Import to:"
+ upload: Upload
+ upload_csv: Please upload your CSV file
+ 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:"
+ warning: Beware
+ export:
+ page_title: Tracks::Export
+ title: Exportar datos
+ format_header: "Puede escoger entre los siguientes formatos:"
+ yaml_description: "%{yaml}: Mejor formato para exportar datos."
+ yaml_link_description: Fichero YAML con todas sus acciones, contextos, proyectos, etiquetas y notas
+ yaml_experimental: "Por favor tenga en cuenta que la importación de ficheros YAML actualmente esta soportada de forma experimental. No confíe en este formato para hacer copias de seguridad de datos importantes."
+ csv_description: "%{csv}: Mejor formato para importar en una hoja de cálculo o en programas de análisis de datos."
+ csv_actions_description: Fichero CSV con todas sus acciones, con contextos por nombre y proyectos
+ csv_notes_description: Fichero CSV con todas sus notas
+ xml_description: "%{xml}: Mejor formato para transformar los datos a otro formato"
+ xml_link_description: Fichero XML con todas sus acciones, contextos, proyectos, etiquetas y notas
+ download_link: Enlace de descarga
+ yaml_link_title: Fichero YAML
+ csv_actions_title: Fichero CSV (acciones, contextos y proyectos)
+ csv_notes_title: Fichero CSV (sólo notas)
+ xml_link_title: Fichero XML
+ yaml: YAML
+ csv: CSV
+ xml: XML
date:
abbr_day_names:
- Dom
diff --git a/config/locales/fi.yml b/config/locales/fi.yml
index 7323c1da..f47ae100 100644
--- a/config/locales/fi.yml
+++ b/config/locales/fi.yml
@@ -48,6 +48,7 @@ fi:
login: Login
open_id_url: OpenID-URL
password: Salasana
+ created_at: Luotu
errors:
full_messages:
format: "%{attribute} %{message}"
diff --git a/config/locales/nl.yml b/config/locales/nl.yml
index cbdb6ac2..f40cabcf 100644
--- a/config/locales/nl.yml
+++ b/config/locales/nl.yml
@@ -356,7 +356,63 @@ nl:
submit: Bewaar %{model}
update: Bijwerken %{model}
integrations:
+ sections:
+ automatic_email: Email jezelf automatisch de acties met een aflopende deadline
+ message_gateway: Integreer Tracks met een email server om een actie via email naar Tracks te sturen
+ mailgun: Send emails to Tracks with Mailgun
+ email_rich: Rich Todo Message email format
opensearch_description: Zoek in Tracks
+ title: Integratie
+ intro: "Tracks kan met een aantal tools worden geïntegreerd... Alles om je te helpen om dingen gedaan te krijgen! Deze pagina heeft informatie over het tot stand brengen van sommige integratievormen. Deze voorbeelden zijn niet altijd voor alle platformen van toepassing en sommige voorbeelden vragen meer technische kennis dan anderen Zie ook %{documentation_link}."
+ developer_documentation_link: "de documentatie voor ontwikkelaars met Tracks' REST API"
+ contents_header: "Inhoud:"
+ add_your_own: Heb je een tip om hier toe te voegen? %{tell_us_link} en misschien voegen we jouw tip toe op deze pagina in een toekomstige versie van Tracks.
+ tell_us_link_text: Vertel ons er over in onze issue queue
+ cron_1: Als je de volgende regel toevoegd aan jouw crontab, dat ontvang je een e-mail op elke dag rond 05:00 met een lijst met acties waarvan de deadline afloopt binnen de komende 7 dagen.
+ cron_2: "Uiteraard kan je ook een andere %{feeds_link} – bijvoorbeeld een email met een lijst van acties voor een specifiek project naar een groep collega's die werken aan dat project?"
+ cron_email_subject: Tracks actions due in the next 7 days
+ feeds_link_text: text feed gebruiken die Tracks biedt
+ message_gateway:
+ description: 'Als Tracks draait op dezelfde server als jouw mailserver, dan kan je de geïntegreerde mail handler gebruiken van Tracks. Om dit in te stellen:'
+ rich_api_tip: 'Je kan ook de Rich Todo API gebruiken om acties te maken zoals "do laundry @ Home" of "Call Bill > project X". Het onderwerp van het bericht zal de bijschrijving van de actie vullen, de context, en het project, terwijl de body van het bericht de notities van de actie zal vullen.'
+ configuration: "Het kan nodig zijn om jouw %{site_yml} te configureren om de message gateway te laten kijken naar het %{to_name} veld of het %{from_name} veld om de Tracks-gebruiker op te zoeken met het emailadres uit dat veld."
+ one_user_configuration: "Je kan ook alle email naar een specifieke Tracks gebruiker sturen. Stel mail_dispatch in site.yml in op %{single_user_var_name} en geeft de login van de gebruiker door: %{code}"
+ instructions:
+ 1: 'Ga naar %{preferences_link} en stel in "%{sms_email_name}" en "%{sms_context_name}" voor acties die verzonden zijn via email (die bijv. komen via een SMS message)'
+ 2: In sendmail/qmail/postfix/whatever, stel een email address alias in om berichten door te sturen naar %{command}
+ 3: Verstuur een email naar het net geconfigureerde e-mail adres!
+ 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
+ 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.domain.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}"
+ 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
+ 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)
+ tag: A tag to apply to the Todo – may be used multiple times
+ star: Flag to star the Todo
+ example_names:
+ todo: my awesome todo
+ context: context
+ project: project
+ tag:
+ 1: tag1
+ 2: tag2
help:
title: Help
usage: 'You can find information on the usage in the %{manual_link} in the project GitHub wiki.'