no-wrap again (Re: [xliff-tools] PO overview for XLIFF mapping guide)

[Karl Eichwalder]

Bruno Haible <bruno at clisp.org> writes:

> This is not true, IMO.
>   - The effects of  /* xgettext: no-wrap */  are not documented in the
>     manual.

Yeah, that's the cause of the trouble - it is not your fault since you
inherited gettext.

>   - The vast majority of terminal-based programs do no line-wrapping on
>     strings retrieved through gettext(). If your assumption was true,
>     most strings should carry the 'no-wrap' attribute. They don't.

Yes, things changed quite a bit during the last years.  To avoid
continued confusion, let's get rid of the no-wrap flag in source code.

> Really, 'no-wrap' is only an indicator for the tools when creating a PO file.
> If a programmer wants to tell something to the translator, he uses plain
> comments like
>
>      /* TRANSLATORS: Please make the translation fit in 79 columns,
>         assuming a monospaced font. */

Yeah, this feature surface later.

-- 
Key fingerprint = B2A3 AF2F CFC8 40B1 67EA  475A 5903 A21B 06EB 882E