Re: [PATCH/RFC v3 2/7] gettext: Add a Gettext interface for shell scripts

From: Johannes Sixt <j.sixt@viscovery.net>
Date: Jun 2, 2010, 09:38 UTC
Message-ID: <4C0626A8.50105@viscovery.net>
In-Reply-To: <AANLkTim-z6JYmyvl5QWycPV9orsUu8qLg2ZVFP6ZeVLC@mail.gmail.com>

Am 6/2/2010 10:53, schrieb Ævar Arnfjörð Bjarmason:

> That hack doesn't work on bash ('\c' produces a space), maybe it
> doesn't work anywhere. Do you have a shell that doesn't support echo
> -n? What does it output there?

It's not just echo -n. You are dealing with text that is outside your control. There are implementations of echo that interpret backslash in the text (like \t, \n etc.). You are risking that they are treated as escape characters rather than printed as-are.

> I wouldn't be surprised if it did need to be changed to printf
> "%s". I'm just curious where it broke and how.

Actually, I don't know where -n does not work.

-- Hannes

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.