[reproducible-website] 01/02: berlin 2016: gettext: fix formatting

Fri Mar 17 15:08:21 UTC 2017

This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch master
in repository reproducible-website.

commit 76de168ab227f990999db8a03b4ffd4bda2c6ac6
Author: Holger Levsen <holger at layer-acht.org>
Date:   Fri Mar 17 16:00:43 2017 +0100

    berlin 2016: gettext: fix formatting
    
    Signed-off-by: Holger Levsen <holger at layer-acht.org>
---
 _events/berlin2016/Gettext.md | 30 ------------------------------
 _events/berlin2016/agenda.md  |  2 +-
 _events/berlin2016/gettext.md | 28 ++++++++++++++++++++++++++++
 3 files changed, 29 insertions(+), 31 deletions(-)

diff --git a/_events/berlin2016/Gettext.md b/_events/berlin2016/Gettext.md
deleted file mode 100644
index f6925a4..0000000
--- a/_events/berlin2016/Gettext.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-layout: event_detail
-title: Gettext
-event: berlin2016
-order: 150
-permalink: /events/berlin2016/Gettext/
----
-
-The problem is that timestamps end up in binaries because of Gettext ([[http://savannah.gnu.org/bugs/?49654][bug 49654]] discusses this issue).  The timestamps originate with =xgettext=, which writes them into the header of =.pot= (the template for translations, extracted from source code strings).  =msgmerge= preserves these timestamps when merging actual translations (=.po= files) with translation templates (=.pot= file).  =msgfmt= preserves timestamps when it builds a binary =.mo= fil [...]
-
-If =.pot= files were generated and included by upstream developers there would be no problem, but that’s not always the case.  Some argue that =.pot= files should not be part of the source tree, because they are generated artifacts.  This means that they might be generated at build time, introducing build time timestamps.
-
-The POT creation date is useful for translators because it tells them whether the entire file needs to be reviewed (relative to the =.po= file).  Hence, it is debatable whether it should be avoided to introduce it in the first place (by patching =xgettext=), or if it should just be excluded from the generated =.mo= files.  Having the date in the binary =.mo= files is useful for recovering =.po= files from an =.mo= using =msgunfmt=, so removing it completely from =.mo= files may not be de [...]
-
-Debian implemented a patch to make xgettext respect =SOURCE_DATE_EPOCH=, but it was rejected by the former maintainer.  We came up with an alternative approach: instead of using =SOURCE_DATE_EPOCH= for translation templates (which may be inaccurate) compute the latest modification time for all source files and use /that/ in the timestamp (instead of the current time).  A patch has been prepared already.
-
-In addition, we are preparing patches for other approaches such as omitting the timestamp header from the =.mo= files.  Upstream can then pick from one of the possible solutions.
-
-/////////////////////////////
-
-Post event email update (12/16/2016):
-    
-For info:
-
-The maintainers of gettext have applied the patches we sent to remove timestamps from the
-output of gettext generated .mo files.
-
-See http://git.savannah.gnu.org/cgit/gettext.git/commit/?id=d13f165b83701dffc14f7151419e0c00c00c0d1b
-
--
diff --git a/_events/berlin2016/agenda.md b/_events/berlin2016/agenda.md
index 7a282d6..38d72df 100644
--- a/_events/berlin2016/agenda.md
+++ b/_events/berlin2016/agenda.md
@@ -65,7 +65,7 @@ Day 2
      -   **[Defining Reproducible Builds I]({{ "/events/berlin2016/reproduciblebuildsdefinition/" | prepend: site.baseurl }})**
      -   **[User policies]({{ "/events/berlin2016/userpolicies/" | prepend: site.baseurl }})**
      -   **[Test infrastructure]({{ "/events/berlin2016/testinfrastructure/" | prepend: site.baseurl }})**
-     -   **Gettext https://pad.riseup.net/p/reproduciblebuildsII-Gettext**
+     -   **[Gettext]({{ "/events/berlin2016/gettext/" | prepend: site.baseurl }})**
 
 *    11.45 Break
 *    12.30 Skill Share
diff --git a/_events/berlin2016/gettext.md b/_events/berlin2016/gettext.md
new file mode 100644
index 0000000..b1d108c
--- /dev/null
+++ b/_events/berlin2016/gettext.md
@@ -0,0 +1,28 @@
+---
+layout: event_detail
+title: Gettext
+event: berlin2016
+order: 150
+permalink: /events/berlin2016/Gettext/
+---
+
+The problem is that timestamps end up in binaries because of [Gettext bug 49654](http://savannah.gnu.org/bugs/?49654).  The timestamps originate with `xgettext`, which writes them into the header of `.pot` (the template for translations, extracted from source code strings).  `msgmerge` preserves these timestamps when merging actual translations (`.po` files) with translation templates (`.pot` file).  `msgfmt` preserves timestamps when it builds a binary `.mo` file from a `.po` file.  The [...]
+
+If `.pot` files were generated and included by upstream developers there would be no problem, but that’s not always the case.  Some argue that `.pot` files should not be part of the source tree, because they are generated artifacts.  This means that they might be generated at build time, introducing build time timestamps.
+
+The POT creation date is useful for translators because it tells them whether the entire file needs to be reviewed (relative to the `.po` file).  Hence, it is debatable whether it should be avoided to introduce it in the first place (by patching `xgettext`), or if it should just be excluded from the generated `.mo` files.  Having the date in the binary `.mo` files is useful for recovering `.po` files from an `.mo` using `msgunfmt`, so removing it completely from `.mo` files may not be de [...]
+
+Debian implemented a patch to make xgettext respect `SOURCE_DATE_EPOCH`, but it was rejected by the former maintainer.  We came up with an alternative approach: instead of using `SOURCE_DATE_EPOCH` for translation templates (which may be inaccurate) compute the latest modification time for all source files and use /that/ in the timestamp (instead of the current time).  A patch has been prepared already.
+
+In addition, we are preparing patches for other approaches such as omitting the timestamp header from the `.mo` files.  Upstream can then pick from one of the possible solutions.
+
+----
+
+Post event email update (12/16/2016):
+    
+The maintainers of gettext have applied the patches we sent to remove timestamps from the
+output of gettext generated .mo files.
+
+See [http://git.savannah.gnu.org/cgit/gettext.git/commit/?id`d13f165b83701dffc14f7151419e0c00c00c0d1b](http://git.savannah.gnu.org/cgit/gettext.git/commit/?id`d13f165b83701dffc14f7151419e0c00c00c0d1b)
+
+-

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/reproducible-website.git

