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

[Jan Nieuwenhuizen]

Bruno Haible <address@hidden> writes:

> 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.

Ok.

> 2) On the C/C++ side, hardly any package uses the gcc/g++ extension,
> for portability reasons.

Ok, but hardly any other gettextized package already uses C/C++
together with GUILE.  GNU especially promotes using GUILE as a C/C++
extention language, and in this case, xgettext grokking multi line
C/C++ strings would help a lot.

> Your Lilypond 1.4.10 C++ sources don't use
> this g++ extension, and use  /** ... */  for literate programming.

Ah, but 1.4.10 in ancient.  In the development series (1.5.61 at the
time of writing), we've even more seen the light, and do:

ENTER_DESCRIPTION(Grace_beam_engraver,
/* descr */       "Handles Beam_requests by engraving Beams.  If omitted, then 
notes will
be printed with flags instead of beams. Only engraves beams when we
are at grace points in time.
",
/* creats*/       "Beam",
/* acks  */       "stem-interface rest-interface",
/* reads */       "beamMelismaBusy subdivideBeams",
/* write */       "");

It would be very good if we weren't forced to go snarfing all c++
code, just because of xgettext.  Snarfing is a pain, and not being
able to use M-x fill-paragraph is no fun either.

Maybe you can reconsider applying the patch (in some other form,
without the python part).  It would be a shame if we'd have to fork
xgettext to build the documentation.

> The mistake you are making is to process the Python source files
> in C++ mode.

Yes, indeed, that was silly, thanks.

Greetings,
Jan

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org