Ann W. Harrison wrote:

> At 06:47 AM 10/27/2004, Jonathan Neve wrote:
>
> The first problem here is that once upon a time there was a way to
> manage error messages and add them easily. Now the tools are
> obsolete so adding an error message is hard.

And there were triggers to maintain the history, etc. The current method is
pure masochism, but it won to please CVS that can't give meaningful binary
diffs.

> A third problem is that the easy way to add an error message - use
> isc_$random and a text string - is a horrible violation of any
> standard of internationalization. We've got this message facility
> designed for translation - hard coding messages is a serious step
> backward.

Yes but given that we now have a half-baked solution, I really have
resistance to put error messages in the correct way.

> If we make it easier to add messages, the resistance to fixing
> ambiguous messages will go done. For now, it's just so much easier
> to use an imprecise but reasonably appropriate message that we can't
> fix
> the problem.

One convoluted solution I thought was to take the current messages database,
apply the tools to it and recreate the scripts by extracting the data. I
don't know if it will work as expected.

C.