CVS log for epic5/include/translat.h

Request diff between arbitrary revisions

* Nix /save and pray nobody notices.
* Implement pmatch_* stuff in alias.c to use the unified symbol table.
* Commands, functions, and expandos now 100% integrated.  HUZZAH!
* Reimplement $get(set|command|function)s() to use the pmatch_* stuff.
* So they now pick up changes at runtime. HUZZAH!
* Allow built in /set to be conditionally added to the "set bucket"
* Don't put user-created /set's in the bucket
* Allow user to replace one user-created /sets but not builtin sets.
* Allow mangling of ALT_CHAR -- how did this ever get missed?
* Fix $currchans() so it works the way the documentation says it does.
* Fix some const correctness issues, introduce others. bleh.

Teach all the /set callbacks to take a (const void *).
This fixes a bad-c problem with /set!

Actually implement the code to use the translation stuff.  This means the
translation stuff is now functional.  THIS IS NOT DONE THE SAME WAY AS
IRCII DOES IT.

ircII implements translation on the output side of the equation, from which
our code has deviated significantly.  Upon reflection, the most common request
for translation was not for OUTPUT translation, but for SERVER translation.
Therefore, I have implemented translation's operations on the server side
of the equation instead of the server side.  If this ends up being the wrong
thing, I reserve the right to go back and "fix" this later.

Anyhow, the translation(s) in force will occur when data is recieved or
transmitted to the server, and not otherwise.  Feedback is appreciated.

Translation table support.  I pulled this from ircII-2.8.2.  Re-added by
incessant requests from russian users.  This adds /set translation and
/set translation_path.  The translation path is not hardcoded into the binary,
it is $IRCLIB/translation, where IRCLIB is determined at runtime.  You can
of course always /set it to whatever you want.  I am not making the
translation tables available with epic.  They are available in zillions of
places, and i'll probably create a tarfile that contains them.