From: Konrad Bajor - Magellan Net <konrad.bajor@ma...> - 2002-09-24 15:47:13
I've problem with my htDig.
The engine htsearch change some characters (for example: ³ -> ³=
I don't know while htsearch change characters like =B3 to ³
Is it possible to set same variable in the system?
According to Konrad Bajor - Magellan Net:
> I've problem with my htDig.
> The engine htsearch change some characters (for example: ³ -> &sup=
> I don't know while htsearch change characters like =B3 to ³
> Is it possible to set same variable in the system?
I assume you're running one of the 3.2 beta releases or snapshots,
rather than the 3.1.6 stable release.
The problem is that htsearch 3.2 converts all characters between 160 and
255 back to SGML entities for ISO-8859-1 characters, which is obviously
wrong when your documents are encoded in a different character set.
The fix will be to add a translate_latin1 attribute to disable these
translations in the htcommon/HtSGMLCodec.cc constructor. For now, the
only quick fix is to modify this constructor not to do these translations.
The HtSGMLCodec class is new to 3.2, which is why 3.1.6 doesn't have
this problem. 3.1.6 doesn't translate the accented characters back to
SGML entities. So, if you don't need the fancy new features of 3.2.0b4,
then I recommend sticking to the 3.1.6 stable release. If you need 3.2,
then you need to hack the HtSGMLCodec constructor.
Gilles R. Detillieux E-mail: <grdetil@...>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/
Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada)
Get latest updates about Open Source Projects, Conferences and News.