Re: [Groff] Preprocessor

[Werner LEMBERG]

> > Which name of the preprocessor do you suggest?
> 
> The name space for command names is a limited and precious resource
> and we have to be careful to name it.  Though I once suggested
> 'gpreconv' in the previous discussion, I don't know about
> traditional or tacit principles on naming a command, if there are.

AFAIK, there aren't.  See my suggestion below.

> BTW, how will you join my preprocessor to the Groff source tree?

Just literally, without integration, so that other people can look at
it.

BTW, have you signed papers for copyright assignment to the FSF?  If
not, please do so (otherwise I can't use your code); details can be
found at

  http://www.gnu.org/software/gcc/fsf-forms/assignment-instructions.html

> My interest is that 'I18N' directive should be determined by the
> 'configure' script.

Definitely, but it isn't urgent IMHO.  Do you have a test handy to be
included into a4local.m4?  Maybe from another package?

> And more, it needs some mechanism to have a translation table
> between MIME encoding names and OS-specific encoding names.  I have
> no idea how to implement that.  (Thus the current version have an
> empty table for this translation.)

Are there so many OS-specific encodings?  Isn't it possible to have
static tables for that?

> Then I will write a postprosessor.  It may share the source code
> (and binary) with the preprocessor, i.e., check argv[0] and change
> the behavior.  (I found that we have to determine the names:-)

I was told that relying on argv[0] is against the GNU coding
standards, so please use a command line option instead.  If we have
just one program for both in and out conversion, I suggest `groconv'
as the program name.


    Werner