point to README on Git server

4 files changed, 99 insertions, 51 deletions

diff --git a/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.md b/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.md
index 8825c7f..3ac4683 100644
--- a/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.md
+++ b/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.md
@@ -220,9 +220,9 @@ and property-based testing for libedn.
 [cbindgen-crate]: https://github.com/eqrion/cbindgen
 [syn-crate]: https://github.com/dtolnay/syn
 [rust-ffi]: https://blog.eqrion.net/future-directions-for-cbindgen/
-[x-bindgen-repo]: https://git.euandreh.xyz/x-bindgen/
-[libedn-repo]: https://git.euandreh.xyz/libedn/
-[parsecc-repo]: https://git.euandreh.xyz/parsecc/
+[x-bindgen-repo]: https://git.euandreh.xyz/x-bindgen/about
+[libedn-repo]: https://git.euandreh.xyz/libedn/about
+[parsecc-repo]: https://git.euandreh.xyz/parsecc/about
 
 ## Conclusion
 
diff --git a/locale/eo/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po b/locale/eo/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po
index 546041b..557a8fb 100644
--- a/locale/eo/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po
+++ b/locale/eo/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po
@@ -291,22 +291,6 @@ msgid ""
 msgstr ""
 
 msgid ""
-"I've started a fork of cbindgen: "
-"[x-bindgen](https://git.euandreh.xyz/x-bindgen/). Right now it is just a "
-"copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code "
-"from it, and add a IR emitting code instead."
-msgstr ""
-
-msgid ""
-"When starting working on x-bindgen, I realized I didn't know what to look "
-"for in a header file, as I haven't written any C code in many years. So as I"
-" was writing [libedn](https://git.euandreh.xyz/libedn/), I didn't know how "
-"to build a good C API to expose. So I tried porting the code to C, and right"
-" now I'm working on building a *good* C API for a JSON parser using parser "
-"combinators: [ParsecC](https://git.euandreh.xyz/parsecc/)."
-msgstr ""
-
-msgid ""
 "After \"finishing\" ParsecC I'll have a good notion of what a good C API is,"
 " and I'll have a better direction towards how to expose code from libedn to "
 "other languages, and work on x-bindgen then."
@@ -344,6 +328,38 @@ msgid ""
 " [1      :parent 0        1 true]]\n"
 msgstr ""
 
+msgid ""
+"I've started a fork of cbindgen: "
+"[x-bindgen](https://git.euandreh.xyz/x-bindgen/about). Right now it is just "
+"a copy of cbindgen verbatim, and I plan to remove all C and C++ emitting "
+"code from it, and add a IR emitting code instead."
+msgstr ""
+
+msgid ""
+"When starting working on x-bindgen, I realized I didn't know what to look "
+"for in a header file, as I haven't written any C code in many years. So as I"
+" was writing [libedn](https://git.euandreh.xyz/libedn/about), I didn't know "
+"how to build a good C API to expose. So I tried porting the code to C, and "
+"right now I'm working on building a *good* C API for a JSON parser using "
+"parser combinators: [ParsecC](https://git.euandreh.xyz/parsecc/about)."
+msgstr ""
+
+#~ msgid ""
+#~ "I've started a fork of cbindgen: "
+#~ "[x-bindgen](https://git.euandreh.xyz/x-bindgen/). Right now it is just a "
+#~ "copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code "
+#~ "from it, and add a IR emitting code instead."
+#~ msgstr ""
+
+#~ msgid ""
+#~ "When starting working on x-bindgen, I realized I didn't know what to look "
+#~ "for in a header file, as I haven't written any C code in many years. So as I"
+#~ " was writing [libedn](https://git.euandreh.xyz/libedn/), I didn't know how "
+#~ "to build a good C API to expose. So I tried porting the code to C, and right"
+#~ " now I'm working on building a *good* C API for a JSON parser using parser "
+#~ "combinators: [ParsecC](https://git.euandreh.xyz/parsecc/)."
+#~ msgstr ""
+
 #~ msgid ""
 #~ "[[person :likes  \"pizza\" 0 true]\n"
 #~ " [0      :parent null    0 true]\n"
diff --git a/locale/fr/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po b/locale/fr/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po
index 546041b..557a8fb 100644
--- a/locale/fr/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po
+++ b/locale/fr/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po
@@ -291,22 +291,6 @@ msgid ""
 msgstr ""
 
 msgid ""
-"I've started a fork of cbindgen: "
-"[x-bindgen](https://git.euandreh.xyz/x-bindgen/). Right now it is just a "
-"copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code "
-"from it, and add a IR emitting code instead."
-msgstr ""
-
-msgid ""
-"When starting working on x-bindgen, I realized I didn't know what to look "
-"for in a header file, as I haven't written any C code in many years. So as I"
-" was writing [libedn](https://git.euandreh.xyz/libedn/), I didn't know how "
-"to build a good C API to expose. So I tried porting the code to C, and right"
-" now I'm working on building a *good* C API for a JSON parser using parser "
-"combinators: [ParsecC](https://git.euandreh.xyz/parsecc/)."
-msgstr ""
-
-msgid ""
 "After \"finishing\" ParsecC I'll have a good notion of what a good C API is,"
 " and I'll have a better direction towards how to expose code from libedn to "
 "other languages, and work on x-bindgen then."
@@ -344,6 +328,38 @@ msgid ""
 " [1      :parent 0        1 true]]\n"
 msgstr ""
 
+msgid ""
+"I've started a fork of cbindgen: "
+"[x-bindgen](https://git.euandreh.xyz/x-bindgen/about). Right now it is just "
+"a copy of cbindgen verbatim, and I plan to remove all C and C++ emitting "
+"code from it, and add a IR emitting code instead."
+msgstr ""
+
+msgid ""
+"When starting working on x-bindgen, I realized I didn't know what to look "
+"for in a header file, as I haven't written any C code in many years. So as I"
+" was writing [libedn](https://git.euandreh.xyz/libedn/about), I didn't know "
+"how to build a good C API to expose. So I tried porting the code to C, and "
+"right now I'm working on building a *good* C API for a JSON parser using "
+"parser combinators: [ParsecC](https://git.euandreh.xyz/parsecc/about)."
+msgstr ""
+
+#~ msgid ""
+#~ "I've started a fork of cbindgen: "
+#~ "[x-bindgen](https://git.euandreh.xyz/x-bindgen/). Right now it is just a "
+#~ "copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code "
+#~ "from it, and add a IR emitting code instead."
+#~ msgstr ""
+
+#~ msgid ""
+#~ "When starting working on x-bindgen, I realized I didn't know what to look "
+#~ "for in a header file, as I haven't written any C code in many years. So as I"
+#~ " was writing [libedn](https://git.euandreh.xyz/libedn/), I didn't know how "
+#~ "to build a good C API to expose. So I tried porting the code to C, and right"
+#~ " now I'm working on building a *good* C API for a JSON parser using parser "
+#~ "combinators: [ParsecC](https://git.euandreh.xyz/parsecc/)."
+#~ msgstr ""
+
 #~ msgid ""
 #~ "[[person :likes  \"pizza\" 0 true]\n"
 #~ " [0      :parent null    0 true]\n"
diff --git a/locale/pt/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po b/locale/pt/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po
index 546041b..557a8fb 100644
--- a/locale/pt/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po
+++ b/locale/pt/LC_MESSAGES/_articles/2020-11-12-durable-persistent-trees-and-parser-combinators-building-a-database.po
@@ -291,22 +291,6 @@ msgid ""
 msgstr ""
 
 msgid ""
-"I've started a fork of cbindgen: "
-"[x-bindgen](https://git.euandreh.xyz/x-bindgen/). Right now it is just a "
-"copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code "
-"from it, and add a IR emitting code instead."
-msgstr ""
-
-msgid ""
-"When starting working on x-bindgen, I realized I didn't know what to look "
-"for in a header file, as I haven't written any C code in many years. So as I"
-" was writing [libedn](https://git.euandreh.xyz/libedn/), I didn't know how "
-"to build a good C API to expose. So I tried porting the code to C, and right"
-" now I'm working on building a *good* C API for a JSON parser using parser "
-"combinators: [ParsecC](https://git.euandreh.xyz/parsecc/)."
-msgstr ""
-
-msgid ""
 "After \"finishing\" ParsecC I'll have a good notion of what a good C API is,"
 " and I'll have a better direction towards how to expose code from libedn to "
 "other languages, and work on x-bindgen then."
@@ -344,6 +328,38 @@ msgid ""
 " [1      :parent 0        1 true]]\n"
 msgstr ""
 
+msgid ""
+"I've started a fork of cbindgen: "
+"[x-bindgen](https://git.euandreh.xyz/x-bindgen/about). Right now it is just "
+"a copy of cbindgen verbatim, and I plan to remove all C and C++ emitting "
+"code from it, and add a IR emitting code instead."
+msgstr ""
+
+msgid ""
+"When starting working on x-bindgen, I realized I didn't know what to look "
+"for in a header file, as I haven't written any C code in many years. So as I"
+" was writing [libedn](https://git.euandreh.xyz/libedn/about), I didn't know "
+"how to build a good C API to expose. So I tried porting the code to C, and "
+"right now I'm working on building a *good* C API for a JSON parser using "
+"parser combinators: [ParsecC](https://git.euandreh.xyz/parsecc/about)."
+msgstr ""
+
+#~ msgid ""
+#~ "I've started a fork of cbindgen: "
+#~ "[x-bindgen](https://git.euandreh.xyz/x-bindgen/). Right now it is just a "
+#~ "copy of cbindgen verbatim, and I plan to remove all C and C++ emitting code "
+#~ "from it, and add a IR emitting code instead."
+#~ msgstr ""
+
+#~ msgid ""
+#~ "When starting working on x-bindgen, I realized I didn't know what to look "
+#~ "for in a header file, as I haven't written any C code in many years. So as I"
+#~ " was writing [libedn](https://git.euandreh.xyz/libedn/), I didn't know how "
+#~ "to build a good C API to expose. So I tried porting the code to C, and right"
+#~ " now I'm working on building a *good* C API for a JSON parser using parser "
+#~ "combinators: [ParsecC](https://git.euandreh.xyz/parsecc/)."
+#~ msgstr ""
+
 #~ msgid ""
 #~ "[[person :likes  \"pizza\" 0 true]\n"
 #~ " [0      :parent null    0 true]\n"