Re: [bug-gettext] .twjr=awk support

[Karl Berry]

Hi Daiki,

    In such cases, I guess we could let people write other file names
    explicitly without using glob, or adopt the !-patterns from git.

What I was think was that the ideal would be specifying (somehow)
something like

foo.cpp option-list-specific-to-foo.cpp
*.cpp   option-list-for-all-other-cpp

But I don't argue that this is critical.  

    I am not sure if there will be any configuration aspects other than
    files.  

I guess.  xgettext takes an awful lot of options, that's all I was
thinking.

    Do you have anything particular in mind?

Nope ...

    If only per-file options are sufficient, I would propose to name the
    file as POTFILES.opts, so it looks clear that the file complements
    POTFILES.in.

Going down that road, I like that name.

    I suppose you mean to pass the per-file options
    through XGETTEXT_OPTIONS?

That could work, or I was thinking of adding some new variable.

My basic problem, as it stands, is that I don't think xgettext supports
taking files both from --files-from and individually, and associating
particular options with a particular file or group of files.  Does it?
As in:

xgettext ... --files-from=whatever.lst ... 
  --language=awk a.twjr b.twjr \
  --language=perl c.weirdperl d.weirdperl ... 

Which would use the default language specs for the files in whatever.lst,
but force {a,b}.twjr to be treated as awk, and {c,d}.weirdperl
to be treated as Perl.

However the files+options data is specified, whether Makevars or
POTFILES.opts or something else, isn't that what eventually has to end
up happening?  Either that or multiple xgettext calls with
--join-existing, right?

Anyway, whatever makes sense to you is the way to go, I'm sure :).

Thanks,
Karl