For starters...
Before I pour though the code to find the answer, if anyone knows and can
quickly tell me...
#define COMPILEOPTIONS (MAGIC8BIT | MAGICCAPITALIZATION | MAGICMASKSET)
What effects do the options MAGIC8BIT, MAGICCAPITALIZATION and MAGICMASKSET
have on Abiword's matching and/or the hash sets? On first glance, *this*
is where the Debian hash sets die.. Abi is set to 0x0002 and Debian is set
to 0x0006
--=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
--VbJkn9YxBvnuCH5J
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GNUPG v0.4.3 (GNU/Linux)
Comment: For info finger gcrypt@ftp.guug.de
iD8DBQE3DmN9bbwt//gBAIoRAbLcAJ41IUoRSKx6I7Ry7URf5E3J5q+48QCgrkgC
Oo+7nmTGiTTR2Y1g7e+PSaA=
=C/Ng
-----END PGP SIGNATURE-----
--VbJkn9YxBvnuCH5J--