Chet Ramey wrote:
> I'm not sure why \r at the beginning and end of a message bothers
> translators
They don't really. So if the \r must be there, leave it in. It's
just that in general: the fewer control characters in a string, the
better. Less clutter, less room for error.
(What I'd really
Chet Ramey <[EMAIL PROTECTED]> wrote:
> The idea is that malloc/free can be called at any time, by any piece
> of code, regardless of the state of the terminal: raw, canonical,
> whatever. The intent is that the cursor be placed at column 0 both
> before and after printing the message, so it stand
Benno Schulenberg wrote:
> Hi,
>
> In the POT file for bash-3.2 there is one msgid that contains two
> \r characters. Are these carriage returns necessary? If not, it
> would be better to remove them, as they are awkward for translators
> and are causing a mild indigestion on Launchpad at the
Hi,
In the POT file for bash-3.2 there is one msgid that contains two
\r characters. Are these carriage returns necessary? If not, it
would be better to remove them, as they are awkward for translators
and are causing a mild indigestion on Launchpad at the moment
(which is Launchpad's fault,
