On Fri, Jun 15, 2007 at 01:51:12PM +0200, Javier Fernández-Sanguino Peña wrote: > On Wed, Jun 13, 2007 at 11:03:57AM +0200, Bill Allombert wrote: > > On Tue, Jun 12, 2007 at 04:24:35PM +0200, Christian Perrier wrote: > > > > > If you have read so far, please find the POT file in attachment. > > > > > > > > All strings (except the last) end with "\\n". Should this be "\n" > > > > instead? > > > > > > > > > Let's ask Bill. I suspect that some reason needs this double escaping > > > to be needed, though. > > > > Yes, su-to-root is a shell script, so I am using gettext(1) and not > > gettext(3). > > Why is the "usage:" msgid mix both \n and \\n. Is this correct?
It is: the shell allows embedded newline inside strings, and gettext convert them to \n. I simply do not like embedded newline at end of strings. This is how it is done: transl 'usage: %s [-X] [-p <user>] -c <command> -c command: command to execute as a string (mandatory) -p <user>: user to switch to (default: root) -X: command is a X11 program\n' "$0" >&2 Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
