No, but the enconding i'm using is iso-latin1 which is the default.
The non-ascii characters are all in iso-latin1, not html entities.
I'm using the same configuration file I used for 3.1.0b1 and things
worked fine in 3.1.0b1
Do you have non-latil words in debug output?
./htdig -isvvv
-Original Message-
From: Nuno Grilo [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: 4 ëèñòîïàäà 1998 ð. 21:33
Subject: Re: htdig: [Patch] non english text parser broken
On Wed, 4 Nov 1998, Geoff Hutchison wrote:
At 9:08 AM -0500 11/4/98, Vadim Chekan wrote:
I
On Thu, 5 Nov 1998, Vadim Chekan wrote:
-Original Message-
From: Nuno Grilo [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Date: 4 ëèñòîïàäà 1998 ð. 21:33
Subject: Re: htdig: [Patch] non english text parser broken
On Wed, 4 Nov 1998, Geoff Hutchison wrote
On Wed, 4 Nov 1998, Geoff Hutchison wrote:
At 9:08 AM -0500 11/4/98, Vadim Chekan wrote:
I found a bug in current (3.1.0.b2) release: I can't index text cyrillic
files. This is because of declare "char" instead of "unsigned char".
Function "isalpha" doesn't work with char127.
Is this
