[Privoxy-devel] Documentation problems

Lee ler762 at gmail.com
Tue Oct 30 17:56:38 UTC 2018


On 10/30/18, Fabian Keil <fk at fabiankeil.de> wrote:
> Lee <ler762 at gmail.com> wrote:
>
>> On 10/30/18, Fabian Keil <fk at fabiankeil.de> wrote:
>> > Lee <ler762 at gmail.com> wrote:
>> >
>> >> On 10/29/18, Fabian Keil <fk at fabiankeil.de> wrote:
>> >> > Lee <ler762 at gmail.com> wrote:
>> >> >
>> >> >> On 10/16/18, Roland Rosenfeld <roland at spinnaker.de> wrote:
>> >> >
>> >> >> > - Replace 06_8bit_manual.patch by a new patch, that only changes
>> >> >> >   preserve-sdata to #t in the HTML section.
>> >> >> > - Append --preserve-entities yes to TIDY options in
>> >> >> > GNUmakefile.in.
>> >> >> > - Change all ISO-8859-1 chars in doc/source/p-authors.sgml to
>> >> >> > SGML
>> >> >> >   entities
>> >> >>
>> >> >> I can make all those changes in git
>> >> >
>> >> > Documentation building is now somewhat differently broken on my
>> >> > system.
>> >> >
>> >> > Links contain plain &'s instead of entities:
>> >> >
>> >> > diff --git a/doc/webserver/developer-manual/git.html
>> >> > b/doc/webserver/developer-manual/git.html
>> >> > index 9efdbdcf..8ce1276c 100644
>> >> > --- a/doc/webserver/developer-manual/git.html
>> >> > +++ b/doc/webserver/developer-manual/git.html
>> >> > @@ -78,8 +78,8 @@
>> >> >          </li>
>> >> >          <li>
>> >> >            <p>Note that near a major public release, we get more
>> >> > cautious.
>> >> > There is always the possibility to submit a
>> >> > -          patch to the <a
>> >> > href="https://sourceforge.net/tracker/?atid=311118&group_id=11118&func=browse"
>> >> >
>> >> > -          target="_top">patch tracker</a> instead.</p>
>> >> > +          patch to the <a
>> >> > href="https://sourceforge.net/tracker/?atid=311118&group_id=11118&func=browse"
>> >> > target=
>> >> > +          "_top">patch tracker</a> instead.</p>
>> >> >          </li>
>> >> >        </ul>
>> >> >      </div>
>> >> >
>> >>
>> >> Can you try doing a 'make clean && make distclean' before rebuilding
>> >> the docs -- without 'make dok-tidy' ?
>> >
>> > Doesn't help:
>>
>> It was worth a shot.
>> Staying with simple.. snippet from GNUmakefile showing how docbook
>> stuff is built:
>> W3M_DUMP   = w3m -I ISO-8859 -O ASCII -dump
>> W3M_DUMP_UTF8 = w3m -I ISO-8859 -O UTF-8 -dump
>> # docbook output is ISO-8859 (which is a superset of ascii)
>> JADECAT    =
>> JADEBIN    = jade
>>   -- my debian system has openjade
>> DB         = $(JADEBIN) $(JADECAT) -ihtml -t sgml  -D.. -d ldp.dsl\#html
>> DB_TXT     = $(JADEBIN) $(JADECAT) -ihtml -t sgml  -D.. -d ldp.dsl\#print
>
> I have:
>    133	W3M_DUMP   = w3m -I ISO-8859 -O ASCII -dump
>    134	W3M_DUMP_UTF8 = w3m -I ISO-8859 -O UTF-8 -dump
>    135	# docbook output is ISO-8859 (which is a superset of ascii)
>    136	JADECAT    =  -c /usr/local/share/sgml/docbook/2.4.1/docbook.cat -c
> /usr/local/share/sgml/docbook/3.0/docbook.cat -c
> /usr/local/share/sgml/docbook/3.1/docbook.cat

That's .. interesting.  Can you still build the docs if you cut
JADECAT down to just
  -c /usr/local/share/sgml/docbook/3.1/docbook.cat

>    137	JADEBIN    = jade
>    138	DB         = $(JADEBIN) $(JADECAT) -ihtml -t sgml  -D.. -d
> ldp.dsl\#html
>    139	DB_TXT     = $(JADEBIN) $(JADECAT) -ihtml -t sgml  -D.. -d
> ldp.dsl\#print
>
>> $ which jade
>> /usr/bin/jade
>> $ ls -l /usr/bin/jade
>> lrwxrwxrwx 1 root None 12 May 31  2017 /usr/bin/jade -> openjade.exe
>> $ which openjade
>> /usr/bin/openjade
>
> fk at t520 ~ $which jade
> /usr/local/bin/jade
>
>> $ openjade --version
>> openjade:I: "OpenJade" version "1.4devel"
>> openjade:I: "OpenSP" version "1.5.2"
>
> fk at t520 ~ $jade -v
> jade:I: Jade version "1.2.1"
> jade:I: SP version "1.3.4"
>
>> yours?  And are you still on FreeBSD or have you switched to something
>> else?
>
> I switched to ElectroBSD which is based on FreeBSD.

A quick search doesn't get me much that I understand; are there
OpenJade & OpenSP packages for ElectroBSD?  Might be worth trying
newer software if using only the 3.1 docbook catalog doesn't fix it

Lee


More information about the Privoxy-devel mailing list