How important is the CREATION code in the ispell stuff used by abiword? I
ask, because I think I can get SuSE's hash file to work via runtime loading
with a small-moderate change (I'll have to change loading and change access
method to one array) but it'll sacrifice the code used to create hashfiles.
External ispell tools should still be able to create files that would work
with abiword.
To get SuSE's hash files to work, the macro MAXSTRINGCHAR needs to made
dynamic based on a field in hashheader. That means every array will have
to be made into a dynmic array (malloc'd pointer) or set to the highest
possible value (theoreticly, 0xFFFFu)
--=20
Please cc all mailing list replies to me, also.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
* http://benham.net/index.html <gecko@benham.net> <>< *
* -------------------- * -----------------------------------------------*
* Debian Developer, Debian Project Secretary, Debian Webmaster *
* <gecko@debian.org> <secretary@debian.org> <lintian-maint@debian.org> *
* <webmaster@debian.org> <gecko@fortunet.com> <webmaster@spi-inc.org> *
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--nYySOmuH/HDX6pKp
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GNUPG v0.4.3 (GNU/Linux)
Comment: For info finger gcrypt@ftp.guug.de
iD8DBQE3MTYObbwt//gBAIoRAfRYAKCEEU29dQ08Q3jpbNI4668W3Gb8ngCgqM2X
B8dOb5ttspDCBYYpBujXLOA=
=G0xF
-----END PGP SIGNATURE-----
--nYySOmuH/HDX6pKp--