Re: "_(" and "N_(" convenience macros not being recognized

[Bruno Haible]

David Bruce wrote:
> > the place where you specify the xgettext options is the variable
> > XGETTEXT_OPTIONS in po/Makevars.
> 
> I take it XGETTEXT_OPTIONS gets set when 'gettextize' is run?

gettextize creates a template for 'po/Makevars', which the user who
ran gettextize then fills in.

> Where the gettext manual describes the shorthand method of marking
> translatable strings(1), perhaps there should be a sentence stating
> that these shorthands depend on XGETTEXT_OPTIONS being set accordingly
> ... I would not have figured this out on my own.

Thank you for this remark. We need your feedback about the doc. I'm
applying this:


2009-06-11  Bruno Haible  <address@hidden>

        * gettext.texi (Mark Keywords): Add cross-section references.
        Reported by David Bruce <address@hidden>.

diff -u -r1.164 gettext.texi
--- gettext.texi        1 May 2009 22:47:01 -0000       1.164
+++ gettext.texi        11 Jun 2009 18:45:50 -0000
@@ -2239,7 +2239,9 @@
 that take it at another argument position.  It is even possible to make
 the marked argument position depend on the total number of arguments of
 the function call; this is useful in C++.  All this is achieved using
address@hidden's @samp{--keyword} option.
address@hidden's @samp{--keyword} option.  How to pass such an option
+to @code{xgettext}, assuming that @code{gettextize} is used, is described
+in @ref{po/Makevars} and @ref{AM_XGETTEXT_OPTION}.
 
 Note also that long strings can be split across lines, into multiple
 adjacent string tokens.  Automatic string concatenation is performed