From 0a132574dc09424d390453c9bdae53b062c91350 Mon Sep 17 00:00:00 2001 From: EuAndreh <eu@euandre.org> Date: Mon, 8 Feb 2021 19:54:22 -0300 Subject: point to README on Git server --- ...s-and-parser-combinators-building-a-database.po | 48 ++++++++++++++-------- 1 file changed, 32 insertions(+), 16 deletions(-) (limited to 'locale/fr/LC_MESSAGES/_articles') 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 @@ -290,22 +290,6 @@ msgid "" "compiler, which isn't actually worst, just less common and less accepted.\n" 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 " @@ -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" -- cgit v1.2.3