Re: [PATCH]: Allowing embedded newlines in strings.

[Bruno Haible]

Jan Nieuwenhuizen wrote:
> Below is a patch that optionally allows xgettext to grok strings that
> include raw (unescaped) newlines.  Although this is strictly not
> allowed for C/C++, gcc/g++ groks these strings, and we find them
> especially useful (in LilyPond) for mimicking in-line literate
> programming.

Thanks for the patch, but it will not be added because:
1) On the Python side, xgettext does already grok strings with embedded
newlines, since 0.11.1.
2) On the C/C++ side, hardly any package uses the gcc/g++ extension,
for portability reasons. Your Lilypond 1.4.10 C++ sources don't use
this g++ extension, and use  /** ... */  for literate programming.

The mistake you are making is to process the Python source files
in C++ mode. This way of course, you are encountering unnatural
xgettext behaviour on the Python sources. You can try to remove --lang=c++
from the xgettext command line, or read the node "Maintainers for other
Languages" of the gettext documentation.

Bruno