Re: Gettext 0.11.5: directories and #lines in generated PO files

[Akim Demaille]

| Why does the recommendation in the gettext manual (node:
| po/POTFILES.in) not work for you?
|
|     When a C file is automatically generated by a tool, like
|     `flex' or `bison', that doesn't introduce translatable strings
|     by itself, it is recommended to list in `po/POTFILES.in' the
|     real source file (ending in `.l' in the case of `flex', or in
|     `.y' in the case of `bison'), not the generated C file.
| 

It does work: that's what I've always been doing up to now; I did not
report a bug here.  It's just that I was thinking of when Bison will
be translating the error messages, and I was also ``obeying'' the
warnings:

/usr/bin/xgettext --default-domain=bison --directory=.. \
  --add-comments=TRANSLATORS: --keyword=_ --keyword=N_ \
  --files-from=./POTFILES.in \
  --copyright-holder='Free Software Foundation, Inc.'
/usr/bin/xgettext: warning: file `src/parse-gram.y' extension `y' is unknown; 
will try C

But you are right, this is not the case yet, using the source file is
fine.  I can reverse my change.  But I was just reporting a
suggestion.  Never mind.