aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.md9
-rw-r--r--locale/eo/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po53
-rw-r--r--locale/fr/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po53
-rw-r--r--locale/pt/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po53
-rw-r--r--scripts/spelling/international.txt1
5 files changed, 116 insertions, 53 deletions
diff --git a/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.md b/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.md
index 0eff520..e9d1b6b 100644
--- a/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.md
+++ b/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.md
@@ -80,7 +80,7 @@ existing workflow for source code and documentation.
I like to keep a [`TODOs.org`][todos-org] file at the repository top-level, with
two relevant sections: "tasks" and "bugs". Then when building the documentation
I'll just [generate an HTML file from it][org-mode-to-html], and
-[publish][published-todos] it alonside the static website. All that is done on
+[publish][published-todos] it alongside the static website. All that is done on
the main branch.
Any issues discussions are done in the mailing list, and a reference to a
@@ -94,11 +94,10 @@ For the other 1%, having Fossil's "[tickets][fossil-tickets]" could be an
alternative, but you may not want to migrate your project to Fossil to get those
niceties.
-Even though I keep a `TODOs.org` file on the main branch, you may pick any name
-you like, or use a dedicated branch just for that, split tasks and bugs into
-different files, or have one file for each.
+Even though I keep a `TODOs.org` file on the main branch, you can have a `tasks`
+ branch with a `task-n.md` file for each task, or any other way you like.
-These tools are familliar enough that you can adjust it to fit your workflow.
+These tools are familiar enough that you can adjust it to fit your workflow.
[todos-org]: https://git.euandreh.xyz/mediator/tree/TODOs.org
[org-mode-to-html]: https://git.euandreh.xyz/mediator/tree/scripts/build-site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14
diff --git a/locale/eo/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po b/locale/eo/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po
index 60a17ab..753e3fc 100644
--- a/locale/eo/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po
+++ b/locale/eo/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po
@@ -116,17 +116,6 @@ msgid ""
msgstr ""
msgid ""
-"I like to keep a "
-"[`TODOs.org`](https://git.euandreh.xyz/mediator/tree/TODOs.org) file at the "
-"repository top-level, with two relevant sections: \"tasks\" and \"bugs\". "
-"Then when building the documentation I'll just [generate an HTML file from "
-"it](https://git.euandreh.xyz/mediator/tree/scripts/build-"
-"site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14), and "
-"[publish](https://mediator.euandreh.xyz/tasks-and-bugs.html) it alonside the"
-" static website. All that is done on the main branch."
-msgstr ""
-
-msgid ""
"Any issues discussions are done in the mailing list, and a reference to a "
"discussion could be added to the ticket itself later on. External "
"contributors can file tickets by sending a patch."
@@ -144,12 +133,44 @@ msgid ""
msgstr ""
msgid ""
-"Even though I keep a `TODOs.org` file on the main branch, you may pick any "
-"name you like, or use a dedicated branch just for that, split tasks and bugs"
-" into different files, or have one file for each."
+"I like to keep a "
+"[`TODOs.org`](https://git.euandreh.xyz/mediator/tree/TODOs.org) file at the "
+"repository top-level, with two relevant sections: \"tasks\" and \"bugs\". "
+"Then when building the documentation I'll just [generate an HTML file from "
+"it](https://git.euandreh.xyz/mediator/tree/scripts/build-"
+"site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14), and "
+"[publish](https://mediator.euandreh.xyz/tasks-and-bugs.html) it alongside "
+"the static website. All that is done on the main branch."
+msgstr ""
+
+msgid ""
+"Even though I keep a `TODOs.org` file on the main branch, you can have a "
+"`tasks` branch with a `task-n.md` file for each task, or any other way you "
+"like."
msgstr ""
msgid ""
-"These tools are familliar enough that you can adjust it to fit your "
-"workflow."
+"These tools are familiar enough that you can adjust it to fit your workflow."
msgstr ""
+
+#~ msgid ""
+#~ "I like to keep a "
+#~ "[`TODOs.org`](https://git.euandreh.xyz/mediator/tree/TODOs.org) file at the "
+#~ "repository top-level, with two relevant sections: \"tasks\" and \"bugs\". "
+#~ "Then when building the documentation I'll just [generate an HTML file from "
+#~ "it](https://git.euandreh.xyz/mediator/tree/scripts/build-"
+#~ "site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14), and "
+#~ "[publish](https://mediator.euandreh.xyz/tasks-and-bugs.html) it alonside the"
+#~ " static website. All that is done on the main branch."
+#~ msgstr ""
+
+#~ msgid ""
+#~ "Even though I keep a `TODOs.org` file on the main branch, you may pick any "
+#~ "name you like, or use a dedicated branch just for that, split tasks and bugs"
+#~ " into different files, or have one file for each."
+#~ msgstr ""
+
+#~ msgid ""
+#~ "These tools are familliar enough that you can adjust it to fit your "
+#~ "workflow."
+#~ msgstr ""
diff --git a/locale/fr/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po b/locale/fr/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po
index 60a17ab..753e3fc 100644
--- a/locale/fr/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po
+++ b/locale/fr/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po
@@ -116,17 +116,6 @@ msgid ""
msgstr ""
msgid ""
-"I like to keep a "
-"[`TODOs.org`](https://git.euandreh.xyz/mediator/tree/TODOs.org) file at the "
-"repository top-level, with two relevant sections: \"tasks\" and \"bugs\". "
-"Then when building the documentation I'll just [generate an HTML file from "
-"it](https://git.euandreh.xyz/mediator/tree/scripts/build-"
-"site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14), and "
-"[publish](https://mediator.euandreh.xyz/tasks-and-bugs.html) it alonside the"
-" static website. All that is done on the main branch."
-msgstr ""
-
-msgid ""
"Any issues discussions are done in the mailing list, and a reference to a "
"discussion could be added to the ticket itself later on. External "
"contributors can file tickets by sending a patch."
@@ -144,12 +133,44 @@ msgid ""
msgstr ""
msgid ""
-"Even though I keep a `TODOs.org` file on the main branch, you may pick any "
-"name you like, or use a dedicated branch just for that, split tasks and bugs"
-" into different files, or have one file for each."
+"I like to keep a "
+"[`TODOs.org`](https://git.euandreh.xyz/mediator/tree/TODOs.org) file at the "
+"repository top-level, with two relevant sections: \"tasks\" and \"bugs\". "
+"Then when building the documentation I'll just [generate an HTML file from "
+"it](https://git.euandreh.xyz/mediator/tree/scripts/build-"
+"site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14), and "
+"[publish](https://mediator.euandreh.xyz/tasks-and-bugs.html) it alongside "
+"the static website. All that is done on the main branch."
+msgstr ""
+
+msgid ""
+"Even though I keep a `TODOs.org` file on the main branch, you can have a "
+"`tasks` branch with a `task-n.md` file for each task, or any other way you "
+"like."
msgstr ""
msgid ""
-"These tools are familliar enough that you can adjust it to fit your "
-"workflow."
+"These tools are familiar enough that you can adjust it to fit your workflow."
msgstr ""
+
+#~ msgid ""
+#~ "I like to keep a "
+#~ "[`TODOs.org`](https://git.euandreh.xyz/mediator/tree/TODOs.org) file at the "
+#~ "repository top-level, with two relevant sections: \"tasks\" and \"bugs\". "
+#~ "Then when building the documentation I'll just [generate an HTML file from "
+#~ "it](https://git.euandreh.xyz/mediator/tree/scripts/build-"
+#~ "site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14), and "
+#~ "[publish](https://mediator.euandreh.xyz/tasks-and-bugs.html) it alonside the"
+#~ " static website. All that is done on the main branch."
+#~ msgstr ""
+
+#~ msgid ""
+#~ "Even though I keep a `TODOs.org` file on the main branch, you may pick any "
+#~ "name you like, or use a dedicated branch just for that, split tasks and bugs"
+#~ " into different files, or have one file for each."
+#~ msgstr ""
+
+#~ msgid ""
+#~ "These tools are familliar enough that you can adjust it to fit your "
+#~ "workflow."
+#~ msgstr ""
diff --git a/locale/pt/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po b/locale/pt/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po
index 60a17ab..753e3fc 100644
--- a/locale/pt/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po
+++ b/locale/pt/LC_MESSAGES/_articles/2020-09-06-diy-an-offline-bug-tracker-with-text-files-git-and-email.po
@@ -116,17 +116,6 @@ msgid ""
msgstr ""
msgid ""
-"I like to keep a "
-"[`TODOs.org`](https://git.euandreh.xyz/mediator/tree/TODOs.org) file at the "
-"repository top-level, with two relevant sections: \"tasks\" and \"bugs\". "
-"Then when building the documentation I'll just [generate an HTML file from "
-"it](https://git.euandreh.xyz/mediator/tree/scripts/build-"
-"site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14), and "
-"[publish](https://mediator.euandreh.xyz/tasks-and-bugs.html) it alonside the"
-" static website. All that is done on the main branch."
-msgstr ""
-
-msgid ""
"Any issues discussions are done in the mailing list, and a reference to a "
"discussion could be added to the ticket itself later on. External "
"contributors can file tickets by sending a patch."
@@ -144,12 +133,44 @@ msgid ""
msgstr ""
msgid ""
-"Even though I keep a `TODOs.org` file on the main branch, you may pick any "
-"name you like, or use a dedicated branch just for that, split tasks and bugs"
-" into different files, or have one file for each."
+"I like to keep a "
+"[`TODOs.org`](https://git.euandreh.xyz/mediator/tree/TODOs.org) file at the "
+"repository top-level, with two relevant sections: \"tasks\" and \"bugs\". "
+"Then when building the documentation I'll just [generate an HTML file from "
+"it](https://git.euandreh.xyz/mediator/tree/scripts/build-"
+"site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14), and "
+"[publish](https://mediator.euandreh.xyz/tasks-and-bugs.html) it alongside "
+"the static website. All that is done on the main branch."
+msgstr ""
+
+msgid ""
+"Even though I keep a `TODOs.org` file on the main branch, you can have a "
+"`tasks` branch with a `task-n.md` file for each task, or any other way you "
+"like."
msgstr ""
msgid ""
-"These tools are familliar enough that you can adjust it to fit your "
-"workflow."
+"These tools are familiar enough that you can adjust it to fit your workflow."
msgstr ""
+
+#~ msgid ""
+#~ "I like to keep a "
+#~ "[`TODOs.org`](https://git.euandreh.xyz/mediator/tree/TODOs.org) file at the "
+#~ "repository top-level, with two relevant sections: \"tasks\" and \"bugs\". "
+#~ "Then when building the documentation I'll just [generate an HTML file from "
+#~ "it](https://git.euandreh.xyz/mediator/tree/scripts/build-"
+#~ "site.sh?id=db4a727bc24b54b50158827b34502de21dbf8948#n14), and "
+#~ "[publish](https://mediator.euandreh.xyz/tasks-and-bugs.html) it alonside the"
+#~ " static website. All that is done on the main branch."
+#~ msgstr ""
+
+#~ msgid ""
+#~ "Even though I keep a `TODOs.org` file on the main branch, you may pick any "
+#~ "name you like, or use a dedicated branch just for that, split tasks and bugs"
+#~ " into different files, or have one file for each."
+#~ msgstr ""
+
+#~ msgid ""
+#~ "These tools are familliar enough that you can adjust it to fit your "
+#~ "workflow."
+#~ msgstr ""
diff --git a/scripts/spelling/international.txt b/scripts/spelling/international.txt
index 10be311..4b5bc4d 100644
--- a/scripts/spelling/international.txt
+++ b/scripts/spelling/international.txt
@@ -25,6 +25,7 @@ CLI
Cantrill
Clojure
CouchDB
+DIY
DVCS
Datomic
EuAndreh