Add all generated .po files

8 files changed, 547 insertions, 0 deletions

diff --git a/locale/eo/LC_MESSAGES/_tils/2020-08-12-simple-filename-timestamp.po b/locale/eo/LC_MESSAGES/_tils/2020-08-12-simple-filename-timestamp.po
new file mode 100644
index 0000000..774a2b4
--- /dev/null
+++ b/locale/eo/LC_MESSAGES/_tils/2020-08-12-simple-filename-timestamp.po
@@ -0,0 +1,35 @@
+#
+msgid ""
+msgstr ""
+
+msgid ""
+"title: Simple filename timestamp\n"
+"date: 2020-08-12\n"
+"layout: post\n"
+"lang: en\n"
+"ref: simple-filename-timestamp"
+msgstr ""
+
+msgid ""
+"When writing Jekyll posts or creating log files with dates on them, I "
+"usually struggle with finding a direct way of accomplishing that. There's a "
+"simple solution: `date -I`."
+msgstr ""
+
+msgid ""
+"Using this built-in GNU/Linux tool allows you to `touch $(date -I).md` to "
+"readily create a `2020-08-12.md` file."
+msgstr ""
+
+msgid ""
+"I always had to read `man date` or search the web over and over, and after "
+"doing this repeatedly it became clear that both `date -I` and `date -Is` "
+"(`s` here stands for seconds) are the thing that I'm looking for 95% of the "
+"time:"
+msgstr ""
+
+msgid ""
+"Both date formats are hierarchical, having the bigger time intervals to the "
+"left. This means that you can easily sort them (and even tab-complete them) "
+"with no extra effort or tool required."
+msgstr ""
diff --git a/locale/eo/LC_MESSAGES/_tils/2020-08-13-anchor-headers-and-code-lines-in-jekyll.po b/locale/eo/LC_MESSAGES/_tils/2020-08-13-anchor-headers-and-code-lines-in-jekyll.po
new file mode 100644
index 0000000..e5902b5
--- /dev/null
+++ b/locale/eo/LC_MESSAGES/_tils/2020-08-13-anchor-headers-and-code-lines-in-jekyll.po
@@ -0,0 +1,104 @@
+#
+msgid ""
+msgstr ""
+
+msgid ""
+"title: Anchor headers and code lines in Jekyll\n"
+"date: 2020-08-13\n"
+"layout: post\n"
+"lang: en\n"
+"ref: anchor-headers-and-code-lines-in-jekyll"
+msgstr ""
+
+msgid ""
+"The default Jekyll toolbox ([Jekyll](https://jekyllrb.com/), "
+"[kramdown](https://kramdown.gettalong.org/) and "
+"[rouge](http://rouge.jneen.net/)) doesn't provide with a configuration "
+"option to add anchors to headers and code blocks."
+msgstr ""
+
+msgid ""
+"The best way I found of doing this is by creating a simple Jekyll plugin, "
+"more specifically, a [Jekyll "
+"hook](https://jekyllrb.com/docs/plugins/hooks/). These allow you to jump in "
+"to the Jekyll build and add a processing stage before of after Jekyll "
+"performs something."
+msgstr ""
+
+msgid ""
+"All you have to do is add the code to `_plugins/my-jekyll-plugin-code.rb`, "
+"and Jekyll knows to pick it up and call your code on the appropriate time."
+msgstr ""
+
+msgid "Anchor on headers"
+msgstr ""
+
+msgid ""
+"Since I wanted to add anchors to headers in all documents, this Jekyll hook "
+"works on `:documents` after they have been transformed into HTML, the "
+"`:post_render` phase:"
+msgstr ""
+
+msgid ""
+"I've derived my implementations from two \"official\"[^official] hooks, "
+"[jemoji](https://github.com/jekyll/jemoji) and [jekyll-"
+"mentions](https://github.com/jekyll/jekyll-mentions)."
+msgstr ""
+
+msgid ""
+"[^official]: I don't know how official they are, I just assumed it because "
+"they live in the same organization inside GitHub that Jekyll does."
+msgstr ""
+
+msgid ""
+"All I did was to wrap the header tag inside an `<a>`, and set the `href` of "
+"that `<a>` to the existing id of the header. Before the hook the HTML looks "
+"like:"
+msgstr ""
+
+msgid "And after the hook should turn that into:"
+msgstr ""
+
+msgid ""
+"The used regexp tries to match only h1-h6 tags, and keep the rest of the "
+"HTML attributes untouched, since this isn't a general HTML parser, but the "
+"generated HTML is somewhat under your control. Use at your own risk because "
+"[you shouldn't parse HTML with "
+"regexps](https://stackoverflow.com/questions/1732348/regex-match-open-tags-"
+"except-xhtml-self-contained-tags/1732454#1732454). Also I used this strategy"
+" in my environment, where no other plugins are installed. I haven't "
+"considered how this approach may conflict with other Jekyll plugins."
+msgstr ""
+
+msgid ""
+"In the new anchor tag you can add your custom CSS class to style it as you "
+"wish."
+msgstr ""
+
+msgid "Anchor on code blocks"
+msgstr ""
+
+msgid ""
+"Adding anchors to code blocks needs a little bit of extra work, because line"
+" numbers themselves don't have preexisting ids, so we need to generate them "
+"without duplications between multiple code blocks in the same page."
+msgstr ""
+
+msgid ""
+"Similarly, this Jekyll hook also works on `:documents` in the `:post_render`"
+" phase:"
+msgstr ""
+
+msgid ""
+"This solution assumes the default Jekyll toolbox with code line numbers "
+"turned on in `_config.yml`:"
+msgstr ""
+
+msgid ""
+"The anchors go from B1-L1 to BN-LN, using the `code_block_counter` to track "
+"which code block we're in and don't duplicate anchor ids. Before the hook "
+"the HTML looks like:"
+msgstr ""
+
+msgid "Happy writing :)"
+msgstr ""
diff --git a/locale/eo/LC_MESSAGES/_tils/2020-08-14-browse-a-git-repository-at-a-specific-commit.po b/locale/eo/LC_MESSAGES/_tils/2020-08-14-browse-a-git-repository-at-a-specific-commit.po
new file mode 100644
index 0000000..5afa66e
--- /dev/null
+++ b/locale/eo/LC_MESSAGES/_tils/2020-08-14-browse-a-git-repository-at-a-specific-commit.po
@@ -0,0 +1,66 @@
+#
+msgid ""
+msgstr ""
+
+msgid ""
+"title: Browse a git repository at a specific commit\n"
+"date: 2020-08-14\n"
+"layout: post\n"
+"lang: en\n"
+"ref: browse-a-git-repository-at-a-specific-commit"
+msgstr ""
+
+msgid ""
+"I commonly use tools like `git log` together with `git show` when inspecting"
+" past changes in a repository:"
+msgstr ""
+
+msgid ""
+"But I also wanted to not only be able to look at the diff of a specific "
+"commit, but to browse the whole repository at that specific commit."
+msgstr ""
+
+msgid ""
+"I used to accomplish it the \"brute force\" way: clone the whole repository "
+"in another folder and checkout the commit there:"
+msgstr ""
+
+msgid ""
+"But git itself allows we to specific the directory of the checkout by using "
+"the `--work-tree` global git flag. This is what `man git` says about it:"
+msgstr ""
+
+msgid ""
+"So it allows us to set the desired path of the working tree. So if we want "
+"to copy the contents of the current working tree into `copy/`:"
+msgstr ""
+
+msgid ""
+"After that `copy/` will contain a replica of the code in HEAD. But to "
+"checkout a specific, we need some extra parameters:"
+msgstr ""
+
+msgid ""
+"There's an extra `-- .` at the end, which initially looks like we're sending"
+" Morse signals to git, but we're actually saying to `git-checkout` which sub"
+" directory of `<my-commit>` we want to look at. Which means we can do "
+"something like:"
+msgstr ""
+
+msgid ""
+"And with that `<dir>` will only contain what was inside `src/` at "
+"`<commit>`."
+msgstr ""
+
+msgid ""
+"After any of those checkouts, you have to `git reset .` to reset your "
+"current staging area back to what it was before the checkout."
+msgstr ""
+
+msgid "References:"
+msgstr ""
+
+msgid ""
+"[GIT: Checkout to a specific folder](https://stackoverflow.com/a/16493707) "
+"(StackOverflow)"
+msgstr ""
diff --git a/locale/eo/LC_MESSAGES/_tils/2020-08-16-search-in-git.po b/locale/eo/LC_MESSAGES/_tils/2020-08-16-search-in-git.po
new file mode 100644
index 0000000..ded01f2
--- /dev/null
+++ b/locale/eo/LC_MESSAGES/_tils/2020-08-16-search-in-git.po
@@ -0,0 +1,52 @@
+#
+msgid ""
+msgstr ""
+
+msgid ""
+"title: Search in git\n"
+"date: 2020-08-16\n"
+"layout: post\n"
+"lang: en\n"
+"ref: search-in-git"
+msgstr ""
+
+msgid "Here's a useful trio to know about to help you search things in git:"
+msgstr ""
+
+msgid "`git show <commit>`"
+msgstr ""
+
+msgid "`git log --grep='<regexp>'`"
+msgstr ""
+
+msgid "`git grep '<regexp>' [commit]`"
+msgstr ""
+
+msgid "1. `git show <commit>`"
+msgstr ""
+
+msgid "Show a specific commit and it's diff:"
+msgstr ""
+
+msgid "2. `git log --grep='<regexp>'`"
+msgstr ""
+
+msgid "Search through the commit messages:"
+msgstr ""
+
+msgid "3. `git grep '<regexp>' [commit]`"
+msgstr ""
+
+msgid "Search content in git history:"
+msgstr ""
+
+msgid ""
+"And if you find an occurrence of the regexp in a specific commit and you "
+"want to browse the repository in that point in time, you can [use git "
+"checkout for that][0]."
+msgstr ""
+
+msgid ""
+"[0]: {% link _tils/2020-08-14-browse-a-git-repository-at-a-specific-"
+"commit.md %}"
+msgstr ""
diff --git a/locale/eo/LC_MESSAGES/_tils/2020-08-28-grep-online-repositories.po b/locale/eo/LC_MESSAGES/_tils/2020-08-28-grep-online-repositories.po
new file mode 100644
index 0000000..04c099f
--- /dev/null
+++ b/locale/eo/LC_MESSAGES/_tils/2020-08-28-grep-online-repositories.po
@@ -0,0 +1,88 @@
+#
+msgid ""
+msgstr ""
+
+msgid ""
+"title: Grep online repositories\n"
+"date: 2020-08-28\n"
+"layout: post\n"
+"lang: en\n"
+"ref: grep-online-repositories"
+msgstr ""
+
+msgid ""
+"I often find interesting source code repositories online that I want to grep"
+" for some pattern but I can't, because either:"
+msgstr ""
+
+msgid ""
+"the repository is on [cgit](https://git.zx2c4.com/cgit/) or a similar code "
+"repository that doesn't allow search in files, or;"
+msgstr ""
+
+msgid ""
+"the search function is really bad, and doesn't allow me to use regular "
+"expressions for searching patterns in the code."
+msgstr ""
+
+msgid ""
+"Here's a simple script that allows you to overcome that problem easily:"
+msgstr ""
+
+msgid ""
+"It is a wrapper around `git grep` that downloads the repository when "
+"missing. Save in a file called `git-search`, make the file executable and "
+"add it to your path."
+msgstr ""
+
+msgid "Overview:"
+msgstr ""
+
+msgid "*lines 1~2*:"
+msgstr ""
+
+msgid ""
+"Bash shebang and the `set -eu` options to exit on error or undefined "
+"variables."
+msgstr ""
+
+msgid "*lines 4~30*:"
+msgstr ""
+
+msgid "Usage text to be printed when providing less arguments than expected."
+msgstr ""
+
+msgid "*line 33*:"
+msgstr ""
+
+msgid "Extract the repository name from the URL, removing trailing slashes."
+msgstr ""
+
+msgid "*lines 34~37*:"
+msgstr ""
+
+msgid "Download the repository when missing and go to the folder."
+msgstr ""
+
+msgid "*line 39*:"
+msgstr ""
+
+msgid "Make the variable `$@` contain the rest of the unused arguments."
+msgstr ""
+
+msgid "*line 40*:"
+msgstr ""
+
+msgid "Perform `git grep`, forwarding the remaining arguments from `$@`."
+msgstr ""
+
+msgid "Example output:"
+msgstr ""
+
+msgid ""
+"Subsequent greps on the same repository are faster because no download is "
+"needed."
+msgstr ""
+
+msgid "When no argument is provided, it prints the usage text:"
+msgstr ""
diff --git a/locale/eo/LC_MESSAGES/_tils/2020-09-04-send-emails-using-the-command-line-for-fun-and-profit.po b/locale/eo/LC_MESSAGES/_tils/2020-09-04-send-emails-using-the-command-line-for-fun-and-profit.po
new file mode 100644
index 0000000..7164578
--- /dev/null
+++ b/locale/eo/LC_MESSAGES/_tils/2020-09-04-send-emails-using-the-command-line-for-fun-and-profit.po
@@ -0,0 +1,56 @@
+#
+msgid ""
+msgstr ""
+
+msgid ""
+"title: Send emails using the command line for fun and profit!\n"
+"date: 2020-09-04\n"
+"layout: post\n"
+"lang: en\n"
+"ref: send-emails-using-the-command-line-for-fun-and-profit"
+msgstr ""
+
+msgid "Here are a few reasons why:"
+msgstr ""
+
+msgid ""
+"send yourself and other people notification of cronjobs, scripts runs, CI "
+"jobs, *etc.*"
+msgstr ""
+
+msgid "leverage the POSIX pipe `|`, and pipe emails away!"
+msgstr ""
+
+msgid "because you can."
+msgstr ""
+
+msgid "Reason 3 is the fun part, reasons 1 and 2 are the profit part."
+msgstr ""
+
+msgid ""
+"First [install and configure "
+"SSMTP](https://wiki.archlinux.org/index.php/SSMTP) for using, say, Gmail as "
+"the email server:"
+msgstr ""
+
+msgid ""
+"Now install [GNU Mailutils](https://mailutils.org/) (`sudo apt-get install "
+"mailutils` or the equivalent on your OS), and send yourself your first "
+"email:"
+msgstr ""
+
+msgid ""
+"And that's about it, you've got mail. Here are some more places where it "
+"might be applicable:"
+msgstr ""
+
+msgid "...and so on."
+msgstr ""
+
+msgid ""
+"You may consider adding a `alias mail='mail -aFrom:email@example.com'` so "
+"you don't keep re-entering the \"From: \" part."
+msgstr ""
+
+msgid "Send yourself some emails to see it working!"
+msgstr ""
diff --git a/locale/eo/LC_MESSAGES/_tils/2020-09-05-pull-requests-with-git-the-old-school-way.po b/locale/eo/LC_MESSAGES/_tils/2020-09-05-pull-requests-with-git-the-old-school-way.po
new file mode 100644
index 0000000..9ffff93
--- /dev/null
+++ b/locale/eo/LC_MESSAGES/_tils/2020-09-05-pull-requests-with-git-the-old-school-way.po
@@ -0,0 +1,107 @@
+#
+msgid ""
+msgstr ""
+
+msgid ""
+"title: Pull requests with Git, the old school way\n"
+"date: 2020-09-05\n"
+"layout: post\n"
+"lang: en\n"
+"ref: pull-requests-with-git-the-old-school-way"
+msgstr ""
+
+msgid ""
+"It might be news to you, as it was to me, that \"pull requests\" that you "
+"can create on a Git hosting provider's web UI[^pr-webui] like "
+"GitLab/Bitbucket/GitHub actually comes from Git itself: `git request-pull`."
+msgstr ""
+
+msgid ""
+"[^pr-webui]: And maybe even using the Git hosting provider's API from the "
+"command line!"
+msgstr ""
+
+msgid ""
+"At the very core, they accomplish the same thing: both the original and the "
+"web UI ones are ways for you to request the project maintainers to pull in "
+"your changes from your fork. It's like saying: \"hi there, I did some "
+"changes on my clone of the repository, what do you think about bringing "
+"those in?\"."
+msgstr ""
+
+msgid ""
+"The only difference is that you're working with only Git itself, so you're "
+"not tied to any Git hosting provider: you can send pull requests across them"
+" transparently! You could even use your own "
+"[cgit](https://git.zx2c4.com/cgit/about/) installation. No need to be locked"
+" in by any of them, putting the \"D\" back in \"DVCS\": it's a "
+"**distributed** version control system."
+msgstr ""
+
+msgid "`git request-pull` introduction"
+msgstr ""
+
+msgid "Here's the raw output of a `git request-pull`:"
+msgstr ""
+
+msgid ""
+"That very first line is saying: \"create me a pull request with only a "
+"single commit, defined by `HEAD`, and use the URL defined by `public-"
+"origin`\"."
+msgstr ""
+
+msgid ""
+"Here's a pitfall: you may try using your `origin` remote at first where I "
+"put `public-origin`, but that is many times pointing to something like "
+"`git@example.com`, or `git.example.com:repo.git` (check that with `git "
+"remote -v | grep origin`). On both cases those are addresses available for "
+"interaction via SSH, and it would be better if your pull requests used an "
+"address ready for public consumption."
+msgstr ""
+
+msgid ""
+"A simple solution for that is for you to add the `public-origin` alias as "
+"the HTTPS alternative to the SSH version:"
+msgstr ""
+
+msgid "Every Git hosting provider exposes repositories via HTTPS."
+msgstr ""
+
+msgid "Experiment it yourself, and get acquainted with the CLI."
+msgstr ""
+
+msgid "Delivering decentralized pull requests"
+msgstr ""
+
+msgid ""
+"Now that you can create the content of a pull request, you can just [deliver"
+" it][cli-email] to the interested parties email:"
+msgstr ""
+
+msgid ""
+"[cli-email]: {% link _tils/2020-09-04-send-emails-using-the-command-line-"
+"for-fun-and-profit.md %}"
+msgstr ""
+
+msgid "Conclusion"
+msgstr ""
+
+msgid ""
+"In practice, I've never used or seen anyone use pull requests this way: "
+"everybody is just [sending patches via "
+"email](https://drewdevault.com/2018/07/23/Git-is-already-distributed.html)."
+msgstr ""
+
+msgid ""
+"If you stop to think about this model, the problem of \"Git hosting "
+"providers becoming too centralized\" is a non-issue, and \"Git federation\" "
+"proposals are a less attractive as they may sound initially."
+msgstr ""
+
+msgid ""
+"Using Git this way is not scary or so weird as the first impression may "
+"suggest. It is actually how Git was designed to be used."
+msgstr ""
+
+msgid "Check `git help request-pull` for more info."
+msgstr ""
diff --git a/locale/eo/LC_MESSAGES/_tils/2020-10-11-search-changes-to-a-filename-pattern-in-git-history.po b/locale/eo/LC_MESSAGES/_tils/2020-10-11-search-changes-to-a-filename-pattern-in-git-history.po
new file mode 100644
index 0000000..5aed337
--- /dev/null
+++ b/locale/eo/LC_MESSAGES/_tils/2020-10-11-search-changes-to-a-filename-pattern-in-git-history.po
@@ -0,0 +1,39 @@
+#
+msgid ""
+msgstr ""
+
+msgid ""
+"title: Search changes to a filename pattern in Git history\n"
+"date: 2020-10-11\n"
+"layout: post\n"
+"lang: en\n"
+"ref: search-changes-to-a-filename-pattern-in-git-history"
+msgstr ""
+
+msgid ""
+"This is [yet][git-til-1] [another][git-til-2] [\"search in Git\"][git-til-3]"
+" TIL entry. You could say that Git has a unintuitive CLI, or that is it very"
+" powerful."
+msgstr ""
+
+msgid ""
+"I wanted to search for an old file that I new that was in the history of the"
+" repository, but was deleted some time ago. So I didn't really remember the "
+"name, only bits of it."
+msgstr ""
+
+msgid ""
+"I immediately went to the list of TILs I had written on searching in Git, "
+"but it wasn't readily obvious how to do it, so here it goes:"
+msgstr ""
+
+msgid ""
+"You could add globs before the pattern to match things on any directory, and"
+" add our `-p` friend to promptly see the diffs:"
+msgstr ""
+
+msgid ""
+"[git-til-1]: {% link _tils/2020-08-14-browse-a-git-repository-at-a-specific-"
+"commit.md %} [git-til-2]: {% link _tils/2020-08-16-search-in-git.md %} [git-"
+"til-3]: {% link _tils/2020-08-28-grep-online-repositories.md %}"
+msgstr ""