Hi,> there a config attribute I'm missing?
Thanks for the info, Jim. I'm using htdig-3.2.0.
I followed the link you posted and indeed, it seems as though that "fix" isn't the best solution.
Is there any other way to get the em-dash to print instead of — in the search returns?
Thanks!
>I am guessing you are using a 3.2.x beta version of ht://Dig. The
translate_* attributes are not available in the 3.2.x branch. The
problem with the entity showing up in search results has been reported
previously. See
http://www.geocrawler.com/mail/msg.php3?msg_id=6835732&list=8822
A patch was submitted, but it seems there was a question as to whether
the proposed fix was really the best solution.
Jim
> 2. I see that there are configuration attributes for translate_latin1,
> translate_amp, and translate_lt_gt: false
>
> I thought translate_latin1: false might work, but I'm still getting
> the entity —
>
> printing out on the page instead of the em-dash in search results. Is
Title: Re: [htdig] Parsing search returns
- [htdig] Parsing search returns Adam Powell
- Re: [htdig] Parsing search returns Jim Cole
- Re: [htdig] Parsing search returns Geoff Hutchison
- Re: [htdig] Parsing search returns Adam Powell
- Re: [htdig] Parsing search returns Jim Cole

