Tools for manipulating message catalogs

[Kee Hinckley]

In article <1991Apr15.170901.18836 at dg-rtp.dg.com> eliot at dg-rtp.dg.com writes:
>are horrendous.  Suppose you have a new executable and new catalog that you
>have built using one of these tools that generates message numbers
>automatically.  You HOPE that the numbers on existing messages haven't been
>accidentally changed, but unless you build another tool to verify that, you
>don't know.  You're all set to ship, complete with translated catalogs in

How about if I add a feature to the gencat which checks to see if the
message numbers have change incompabibly? And if so it issues a warning?
I think it's doable, and I've pretty much been convinced it's useful.

>Something just occurred to me:  how about if the automatic numbering tool
>knew enough about the source archiving system (SCCS, RCS, or whatever) so
>that it could compare the latest version of the catalog against all previous
>versions, to make sure that no incompatibilities were being introduced?  This
This'll get me for replying before reading everything.  Anyway, you could
do it there, but I think doing it with the message catalog iself would
be sufficient (and certainly easier).

-- 
Alfalfa Software, Inc.          |       Poste:  The EMail for Unix
nazgul at alfalfa.com              |       Send Anything... Anywhere
617/646-7703 (voice/fax)        |       info at alfalfa.com

I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.