Re: [PATCH] Poison gettext with the Ook language
From: Duy Nguyen <hidden>
Date: 2018-10-23 14:38:05
On Mon, Oct 22, 2018 at 10:23 PM SZEDER Gábor [off-list ref] wrote:
Once upon a time a GETTEXT_POISON build job failed on me, and the error message: error: # GETTEXT POISON # was not particularly useful. Ook wouldn't help with that...
Oook?
So I came up with the following couple of patches that implement a "scrambled" format that makes the poisoned output legible for humans but still gibberish for machine consumption (i.e. grep-ing the text part would still fail): error: U.n.a.b.l.e. .t.o. .c.r.e.a.t.e. .'./home/szeder/src/git/t/trash directory.t1404-update-ref-errors/.git/packed-refs...l.o.c.k.'.:. .File exists... I have been running GETTEXT_POISON builds with this series for some months now, but haven't submitted it yet, because I haven't decided yet whether including strings (paths, refs, etc.) in the output as they are is a feature or a flaw.
A feature to me. The only thing that got through and but should not be grep-able is strerror(). But that's orthogonal to this scrambling stuff.
And because it embarrassingly leaks every single translated string... :)
Easy to fix. I hope this means you have no more excuse to not push this forward ;-) -- Duy