1*00b67f09SDavid van MoolenbroekCopyright (C) 2004 Internet Systems Consortium, Inc. ("ISC") 2*00b67f09SDavid van MoolenbroekCopyright (C) 2000, 2001 Internet Software Consortium. 3*00b67f09SDavid van MoolenbroekSee COPYRIGHT in the source root or http://isc.org/copyright.html for terms. 4*00b67f09SDavid van Moolenbroek 5*00b67f09SDavid van MoolenbroekThe BIND v9 ARM master document is now kept in DocBook XML format. 6*00b67f09SDavid van Moolenbroek 7*00b67f09SDavid van MoolenbroekVersion: Id: README-SGML,v 1.17 2004/03/05 05:04:43 marka Exp 8*00b67f09SDavid van Moolenbroek 9*00b67f09SDavid van MoolenbroekThe entire ARM is in the single file: 10*00b67f09SDavid van Moolenbroek 11*00b67f09SDavid van Moolenbroek Bv9ARM-book.xml 12*00b67f09SDavid van Moolenbroek 13*00b67f09SDavid van MoolenbroekAll of the other documents - HTML, PDF, etc - are generated from this 14*00b67f09SDavid van Moolenbroekmaster source. 15*00b67f09SDavid van Moolenbroek 16*00b67f09SDavid van MoolenbroekThis file attempts to describe what tools are necessary for the 17*00b67f09SDavid van Moolenbroekmaintenance of this document as well as the generation of the 18*00b67f09SDavid van Moolenbroekalternate formats of this document. 19*00b67f09SDavid van Moolenbroek 20*00b67f09SDavid van MoolenbroekThis file will also spend a very little time describing the XML and 21*00b67f09SDavid van MoolenbroekSGML headers so you can understand a bit what you may need to do to be 22*00b67f09SDavid van Moolenbroekable to work with this document in any fashion other than simply 23*00b67f09SDavid van Moolenbroekediting it. 24*00b67f09SDavid van Moolenbroek 25*00b67f09SDavid van MoolenbroekWe will spend almost no time on the actual tags and how to write an 26*00b67f09SDavid van MoolenbroekXML DocBook compliant document. If you are at all familiar with SGML 27*00b67f09SDavid van Moolenbroekor HTML it will be very evident. You only need to know what the tags 28*00b67f09SDavid van Moolenbroekare and how to use them. You can find a good resource either for this 29*00b67f09SDavid van Moolenbroekeither online or in printed form: 30*00b67f09SDavid van Moolenbroek 31*00b67f09SDavid van Moolenbroek DocBook: The Definitive Guide 32*00b67f09SDavid van Moolenbroek By Norman Walsh and Leonard Muellner 33*00b67f09SDavid van Moolenbroek ISBN: 156592-580-7 34*00b67f09SDavid van Moolenbroek 1st Edition, October 1999 35*00b67f09SDavid van Moolenbroek Copyright (C) 1999 by O'Reilly & Associates, Inc. All rights reserved. 36*00b67f09SDavid van Moolenbroek 37*00b67f09SDavid van MoolenbroekThe book is available online in HTML format: 38*00b67f09SDavid van Moolenbroek 39*00b67f09SDavid van Moolenbroek http://docbook.org/ 40*00b67f09SDavid van Moolenbroek 41*00b67f09SDavid van Moolenbroekand buried in: 42*00b67f09SDavid van Moolenbroek 43*00b67f09SDavid van Moolenbroek http://www.nwalsh.com/docbook/defguide/index.html 44*00b67f09SDavid van Moolenbroek 45*00b67f09SDavid van MoolenbroekA lot of useful stuff is at NWalsh's site in general. You may also 46*00b67f09SDavid van Moolenbroekwant to look at: 47*00b67f09SDavid van Moolenbroek 48*00b67f09SDavid van Moolenbroek http://www.xml.com/ 49*00b67f09SDavid van Moolenbroek 50*00b67f09SDavid van MoolenbroekThe BIND v9 ARM is based on the XML 4.0 DocBook DTD. Every XML and 51*00b67f09SDavid van MoolenbroekSGML document begins with a prefix that tells where to find the file 52*00b67f09SDavid van Moolenbroekthat describes the meaning and structure of the tags used in the rest 53*00b67f09SDavid van Moolenbroekof the document. 54*00b67f09SDavid van Moolenbroek 55*00b67f09SDavid van MoolenbroekFor our XML DocBook 4.0 based document this prefix looks like this: 56*00b67f09SDavid van Moolenbroek 57*00b67f09SDavid van Moolenbroek <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.0//EN" 58*00b67f09SDavid van Moolenbroek "/usr/local/share/xml/dtd/docbook/docbookx.dtd"> 59*00b67f09SDavid van Moolenbroek 60*00b67f09SDavid van MoolenbroekThis "DOCTYPE" statement has three parts, of which we are only using 61*00b67f09SDavid van Moolenbroektwo: 62*00b67f09SDavid van Moolenbroek 63*00b67f09SDavid van Moolenbroeko The highest level term that represents this document (in this case 64*00b67f09SDavid van Moolenbroek it is "book" 65*00b67f09SDavid van Moolenbroek 66*00b67f09SDavid van Moolenbroeko The identifier that tells us which DTD to use. This identifier has 67*00b67f09SDavid van Moolenbroek two parts, the "Formal Public Identifier" (or FPI) and the system 68*00b67f09SDavid van Moolenbroek identifier. In SGML you can have either a FPI or a SYSTEM identifier 69*00b67f09SDavid van Moolenbroek but you have to have at least one of them. In XML you have to have a 70*00b67f09SDavid van Moolenbroek SYSTEM identifier. 71*00b67f09SDavid van Moolenbroek 72*00b67f09SDavid van MoolenbroekFP & SYSTEM identifiers - These are names/lookups for the actual 73*00b67f09SDavid van MoolenbroekDTD. The FPI is a globally unique name that should, on a properly 74*00b67f09SDavid van Moolenbroekconfigured system, tell you exactly what DTD to use. The SYSTEM 75*00b67f09SDavid van Moolenbroekidentifier gives an absolute location for the DTD. In XML these are 76*00b67f09SDavid van Moolenbroeksupposed to be properly formatted URL's. 77*00b67f09SDavid van Moolenbroek 78*00b67f09SDavid van MoolenbroekSGML has these things called "catalogs" that are files that map FPI's 79*00b67f09SDavid van Moolenbroekin to actual files. A "catalog" can also be used to remap a SYSTEM 80*00b67f09SDavid van Moolenbroekidentifier so you can say something like: "http://www.oasis.org/foo" 81*00b67f09SDavid van Moolenbroekis actually "/usr/local/share/xml/foo.dtd" 82*00b67f09SDavid van Moolenbroek 83*00b67f09SDavid van MoolenbroekWhen you use various SGML/XML tools they need to be configured to look 84*00b67f09SDavid van Moolenbroekat the same "catalog" files so that as you move from tool to tool they 85*00b67f09SDavid van Moolenbroekall refer to the same DTD for the same document. 86*00b67f09SDavid van Moolenbroek 87*00b67f09SDavid van MoolenbroekWe will be spending most of our configuration time making sure our 88*00b67f09SDavid van Moolenbroektools use the same "catalog" files and that we have the same DTD's 89*00b67f09SDavid van Moolenbroekinstalled on our machines. XML's requirement of the SYSTEM identifier 90*00b67f09SDavid van Moolenbroekover the FPI will probably lead to more problems as it does not 91*00b67f09SDavid van Moolenbroekguarantee that everyone is using the same DTD. 92*00b67f09SDavid van Moolenbroek 93*00b67f09SDavid van MoolenbroekI did my initial work with the "sgmltools" the XML 4.0 DocBook DTD and 94*00b67f09SDavid van Moolenbroek"jade" or "openjade." 95*00b67f09SDavid van Moolenbroek 96*00b67f09SDavid van MoolenbroekYou can get the 4.0 XML DocBook DTD from: 97*00b67f09SDavid van Moolenbroek 98*00b67f09SDavid van Moolenbroek http://www.docbook.org/xml/4.0/ 99*00b67f09SDavid van Moolenbroek 100*00b67f09SDavid van Moolenbroek(download the .zip file.) NOTE: We will eventually be changing the 101*00b67f09SDavid van MoolenbroekSYSTEM identifier to the recommended value of: 102*00b67f09SDavid van Moolenbroek 103*00b67f09SDavid van Moolenbroek http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd 104*00b67f09SDavid van Moolenbroek 105*00b67f09SDavid van MoolenbroekNOTE: Under FreeBSD this is the package: 106*00b67f09SDavid van Moolenbroek 107*00b67f09SDavid van Moolenbroek /usr/ports/textproc/docbook-xml 108*00b67f09SDavid van Moolenbroek 109*00b67f09SDavid van MoolenbroekNetBSD instructions are coming soon. 110*00b67f09SDavid van Moolenbroek 111*00b67f09SDavid van MoolenbroekWith packages listed below installed under FreeBSD the "catalog" file 112*00b67f09SDavid van Moolenbroekthat all the tools refer to at least one is in: 113*00b67f09SDavid van Moolenbroek 114*00b67f09SDavid van Moolenbroek /usr/local/share/sgml/catalog 115*00b67f09SDavid van Moolenbroek 116*00b67f09SDavid van MoolenbroekIn order for our SYSTEM identifier for the XML DocBook dtd to be found 117*00b67f09SDavid van MoolenbroekI create a new catalog file at the top of the XML directory created on 118*00b67f09SDavid van MoolenbroekFreeBSD: 119*00b67f09SDavid van Moolenbroek 120*00b67f09SDavid van Moolenbroek /usr/local/share/xml/catalog 121*00b67f09SDavid van Moolenbroek 122*00b67f09SDavid van MoolenbroekThis file has one line: 123*00b67f09SDavid van Moolenbroek 124*00b67f09SDavid van Moolenbroek SYSTEM "http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd" "/usr/local/share/xml/dtd/docbook/docbookx.dtd" 125*00b67f09SDavid van Moolenbroek 126*00b67f09SDavid van MoolenbroekThen in the main "catalog" I have it include this XML catalog: 127*00b67f09SDavid van Moolenbroek 128*00b67f09SDavid van Moolenbroek CATALOG "/usr/local/share/xml/catalog" 129*00b67f09SDavid van Moolenbroek 130*00b67f09SDavid van Moolenbroek 131*00b67f09SDavid van MoolenbroekOn your systems you need to replace "/usr/local/share" with your 132*00b67f09SDavid van Moolenbroekprefix root (probably /usr/pkg under NetBSD.) 133*00b67f09SDavid van Moolenbroek 134*00b67f09SDavid van MoolenbroekNOTE: The URL used above is supposed to the be the proper one for this 135*00b67f09SDavid van MoolenbroekXML DocBook DTD... but there is nothing at that URL so you really do 136*00b67f09SDavid van Moolenbroekneed the "SYSTEM" identifier mapping in your catalog (or make the 137*00b67f09SDavid van MoolenbroekSYSTEM identifier in your document refer to the real location of the 138*00b67f09SDavid van Moolenbroekfile on your local system.) 139*00b67f09SDavid van Moolenbroek 140*00b67f09SDavid van MoolenbroekHOW TO VALIDATE A DOCUMENT: 141*00b67f09SDavid van Moolenbroek 142*00b67f09SDavid van MoolenbroekI use the sgmltools "nsgmls" document validator. Since we are using 143*00b67f09SDavid van MoolenbroekXML we need to use the XML declarations, which are installed as part 144*00b67f09SDavid van Moolenbroekof the modular DSSL style sheets: 145*00b67f09SDavid van Moolenbroek 146*00b67f09SDavid van Moolenbroek nsgmls -sv /usr/local/share/sgml/docbook/dsssl/modular/dtds/decls/xml.dcl \ 147*00b67f09SDavid van Moolenbroek Bv9ARM-book.xml 148*00b67f09SDavid van Moolenbroek 149*00b67f09SDavid van MoolenbroekA convenient shell script "validate.sh" is now generated by configure 150*00b67f09SDavid van Moolenbroekto invoke the above command with the correct system-dependent paths. 151*00b67f09SDavid van Moolenbroek 152*00b67f09SDavid van MoolenbroekThe SGML tools can be found at: 153*00b67f09SDavid van Moolenbroek 154*00b67f09SDavid van Moolenbroek ftp://ftp.us.sgmltools.org/pub/SGMLtools/v2.0/source/ \ 155*00b67f09SDavid van Moolenbroek ftp://ftp.nllgg.nl/pub/SGMLtools/v2.0/source/ 156*00b67f09SDavid van Moolenbroek 157*00b67f09SDavid van MoolenbroekFreeBSD package for these is: 158*00b67f09SDavid van Moolenbroek 159*00b67f09SDavid van Moolenbroek /usr/ports/textproc/sgmltools 160*00b67f09SDavid van Moolenbroek 161*00b67f09SDavid van MoolenbroekHOW TO RENDER A DOCUMENT AS HTML or TeX: 162*00b67f09SDavid van Moolenbroek 163*00b67f09SDavid van Moolenbroeko Generate html doc with: 164*00b67f09SDavid van Moolenbroek 165*00b67f09SDavid van Moolenbroek openjade -v -d ./nominum-docbook-html.dsl \ 166*00b67f09SDavid van Moolenbroek -t sgml \ 167*00b67f09SDavid van Moolenbroek /usr/local/share/sgml/docbook/dsssl/modular/dtds/decls/xml.dcl \ 168*00b67f09SDavid van Moolenbroek Bv9ARM-book.xml 169*00b67f09SDavid van Moolenbroek 170*00b67f09SDavid van MoolenbroekA convenient shell script "genhtml.sh" is now generated by configure to 171*00b67f09SDavid van Moolenbroekinvoke the above command with the correct system-dependent paths. 172*00b67f09SDavid van Moolenbroek 173*00b67f09SDavid van MoolenbroekOn NetBSD there is no port for "openjade" however "jade" does still 174*00b67f09SDavid van Moolenbroekwork. However you need to specify the "catalog" file to use for style 175*00b67f09SDavid van Moolenbroeksheets on the command line AND you need to have a default "catalog" 176*00b67f09SDavid van Moolenbroekmapping where to find various DTDs. It seems that "jade" installed out 177*00b67f09SDavid van Moolenbroekof the box on NetBSD does not use a globally defined "catalog" file 178*00b67f09SDavid van Moolenbroekfor mapping PUBLIC identifiers in to SYSTEM identifiers. 179*00b67f09SDavid van Moolenbroek 180*00b67f09SDavid van MoolenbroekSo you need to have a "catalog" file in your current working directory 181*00b67f09SDavid van Moolenbroekthat has in it this: (these are probably more entries than you need!) 182*00b67f09SDavid van Moolenbroek 183*00b67f09SDavid van Moolenbroek CATALOG "/usr/pkg/share/sgml/iso8879/catalog" 184*00b67f09SDavid van Moolenbroek CATALOG "/usr/pkg/share/sgml/docbook/2.4.1/catalog" 185*00b67f09SDavid van Moolenbroek CATALOG "/usr/pkg/share/sgml/docbook/3.0/catalog" 186*00b67f09SDavid van Moolenbroek CATALOG "/usr/pkg/share/sgml/docbook/3.1/catalog" 187*00b67f09SDavid van Moolenbroek CATALOG "/usr/pkg/share/sgml/jade/catalog" 188*00b67f09SDavid van Moolenbroek CATALOG "/usr/local/share/xml/catalog" 189*00b67f09SDavid van Moolenbroek 190*00b67f09SDavid van Moolenbroek(These would all be "/usr/local" on FreeBSD) 191*00b67f09SDavid van Moolenbroek 192*00b67f09SDavid van MoolenbroekSo the command for jade on NetBSD will look like this: 193*00b67f09SDavid van Moolenbroek 194*00b67f09SDavid van Moolenbroekjade -v -c /usr/pkg/share/sgml/catalog -t sgml \ 195*00b67f09SDavid van Moolenbroek -d ./nominum-docbook-html.dsl \ 196*00b67f09SDavid van Moolenbroek /usr/pkg/share/sgml/docbook/dsssl/modular/dtds/decls/xml.dcl \ 197*00b67f09SDavid van Moolenbroek ./Bv9ARM-book.xml 198*00b67f09SDavid van Moolenbroek 199*00b67f09SDavid van MoolenbroekFurthermore, since the style sheet subset we define has in it a hard 200*00b67f09SDavid van Moolenbroekcoded path to the style sheet is based, it is actually generated by 201*00b67f09SDavid van Moolenbroekconfigure from a .in file so that it will contain the correct 202*00b67f09SDavid van Moolenbroeksystem-dependent path: where on FreeBSD the second line reads: 203*00b67f09SDavid van Moolenbroek 204*00b67f09SDavid van Moolenbroek <!ENTITY dbstyle SYSTEM "/usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl" CDATA DSSSL> 205*00b67f09SDavid van Moolenbroek 206*00b67f09SDavid van MoolenbroekOn NetBSD it needs to read: 207*00b67f09SDavid van Moolenbroek 208*00b67f09SDavid van Moolenbroek <!ENTITY dbstyle SYSTEM "/usr/pkg/share/sgml/docbook/dsssl/modular/html/docbook.dsl" CDATA DSSSL> 209*00b67f09SDavid van Moolenbroek 210*00b67f09SDavid van MoolenbroekNOTE: This is usually solved by having this style sheet modification 211*00b67f09SDavid van Moolenbroekbe installed in a system directory and have it reference the style 212*00b67f09SDavid van Moolenbroeksheet it is based on via a relative path. 213*00b67f09SDavid van Moolenbroek 214*00b67f09SDavid van Moolenbroeko Generate TeX documentation: 215*00b67f09SDavid van Moolenbroek 216*00b67f09SDavid van Moolenbroekopenjade -d ./nominum-docbook-print.dsl -t tex -v \ 217*00b67f09SDavid van Moolenbroek /usr/local/share/sgml/docbook/dsssl/modular/dtds/decls/xml.dcl \ 218*00b67f09SDavid van Moolenbroek Bv9ARM-book.xml 219*00b67f09SDavid van Moolenbroek 220*00b67f09SDavid van MoolenbroekIf you have "jade" installed instead of "openjade" then use that as 221*00b67f09SDavid van Moolenbroekthe command. There is little difference, openjade has some bug fixes 222*00b67f09SDavid van Moolenbroekand is in more active development. 223*00b67f09SDavid van Moolenbroek 224*00b67f09SDavid van MoolenbroekTo convert the resulting TeX file in to a DVI file you need to do: 225*00b67f09SDavid van Moolenbroek 226*00b67f09SDavid van Moolenbroek tex "&jadetex" Bv9ARM-book.tex 227*00b67f09SDavid van Moolenbroek 228*00b67f09SDavid van MoolenbroekYou can also directly generate the pdf file via: 229*00b67f09SDavid van Moolenbroek 230*00b67f09SDavid van Moolenbroek pdftex "&pdfjadetex" Bv9ARM-book.tex 231*00b67f09SDavid van Moolenbroek 232*00b67f09SDavid van MoolenbroekThe scripts "genpdf.sh" and "gendvi." have been added to simply 233*00b67f09SDavid van Moolenbroekgenerating the PDF and DVI output. These substitute the correct paths 234*00b67f09SDavid van Moolenbroekof NetBSD & FreeBSD. You still need to have TeX, jadeTeX, and pdfTeX 235*00b67f09SDavid van Moolenbroekinstalled and configured properly for these to work. 236*00b67f09SDavid van Moolenbroek 237*00b67f09SDavid van MoolenbroekYou will need to up both the "pool_size" and "hash_extra" variables in 238*00b67f09SDavid van Moolenbroekyour texmf.cnf file and regenerate them. See below. 239*00b67f09SDavid van Moolenbroek 240*00b67f09SDavid van MoolenbroekYou can see that I am using a DSSSL style sheet for DocBook. Actually 241*00b67f09SDavid van Moolenbroektwo different ones - one for rendering html, and one for 'print' 242*00b67f09SDavid van Moolenbroekmedia. 243*00b67f09SDavid van Moolenbroek 244*00b67f09SDavid van MoolenbroekNOTE: For HTML we are using a Nominum DSSSL style instead of the 245*00b67f09SDavid van Moolenbroekdefault one (all it does is change the chunking to the chapter level 246*00b67f09SDavid van Moolenbroekand makes the files end with ".html" instead of ".htm" so far.) If you 247*00b67f09SDavid van Moolenbroekwant to use the plain jane DSSSL style sheet replace the: 248*00b67f09SDavid van Moolenbroek 249*00b67f09SDavid van Moolenbroek -d ./nominum-docbook-html.dsl 250*00b67f09SDavid van Moolenbroek 251*00b67f09SDavid van Moolenbroekwith 252*00b67f09SDavid van Moolenbroek 253*00b67f09SDavid van Moolenbroek -d /usr/local/share/sgml/docbook/dsssl/modular/html/docbook.dsl 254*00b67f09SDavid van Moolenbroek 255*00b67f09SDavid van MoolenbroekThis style sheet will attempt to reference the one above. 256*00b67f09SDavid van Moolenbroek 257*00b67f09SDavid van MoolenbroekI am currently working on fixing these up so that it works the same on 258*00b67f09SDavid van Moolenbroekour various systems. The main trick is knowing which DTD's and DSSSL 259*00b67f09SDavid van Moolenbroekstylesheets you have installed, installing the right ones, and 260*00b67f09SDavid van Moolenbroekconfiguring a CATALOG that refers to them in the same way. We will 261*00b67f09SDavid van Moolenbroekprobably end up putting our CATALOG's in the same place and then we 262*00b67f09SDavid van Moolenbroekshould be able to generate and validate our documents with a minimal 263*00b67f09SDavid van Moolenbroeknumber of command line arguments. 264*00b67f09SDavid van Moolenbroek 265*00b67f09SDavid van MoolenbroekWhen running these commands you will get a lot of messages about a 266*00b67f09SDavid van Moolenbroekbunch of general entities not being defined and having no default 267*00b67f09SDavid van Moolenbroekentity. You can ignore those for now. 268*00b67f09SDavid van Moolenbroek 269*00b67f09SDavid van MoolenbroekAlso with the style sheets we have and jade as it is you will get 270*00b67f09SDavid van Moolenbroekmessages about "xref to title" being unsupported. You can ignore these 271*00b67f09SDavid van Moolenbroekfor now as well. 272*00b67f09SDavid van Moolenbroek 273*00b67f09SDavid van Moolenbroek=== Getting the various tools installed on FreeBSD 274*00b67f09SDavid van Moolenbroek(NetBSD coming soon..) 275*00b67f09SDavid van Moolenbroek 276*00b67f09SDavid van Moolenbroeko On freebsd you need to install the following packages: 277*00b67f09SDavid van Moolenbroek o print/teTeX 278*00b67f09SDavid van Moolenbroek o textproc/openjade 279*00b67f09SDavid van Moolenbroek o textproc/docbook 280*00b67f09SDavid van Moolenbroek o textproc/docbook-xml 281*00b67f09SDavid van Moolenbroek o textproc/dsssl-docbook-modular 282*00b67f09SDavid van Moolenbroek o textproc/dtd-catalogs 283*00b67f09SDavid van Moolenbroek 284*00b67f09SDavid van Moolenbroeko on freebsd you need to make some entities visible to the docbook xml 285*00b67f09SDavid van Moolenbroek dtd by making a symlink (can probably be done with a catalog too) 286*00b67f09SDavid van Moolenbroek ln -s /usr/local/share/xml/entity /usr/local/share/xml/dtd/docbook/ent 287*00b67f09SDavid van Moolenbroek 288*00b67f09SDavid van Moolenbroeko you may need to edit /usr/local/share/sgml/catalog and add the line: 289*00b67f09SDavid van Moolenbroek 290*00b67f09SDavid van Moolenbroek CATALOG "/usr/local/share/sgml/openjade/catalog" 291*00b67f09SDavid van Moolenbroek 292*00b67f09SDavid van Moolenbroeko add "hugelatex," Enlarge pool sizes, install the jadetex TeX driver 293*00b67f09SDavid van Moolenbroek file. 294*00b67f09SDavid van Moolenbroek 295*00b67f09SDavid van Moolenbroek cd /usr/local/share/texmf/web2c/ 296*00b67f09SDavid van Moolenbroek sudo cp texmf.cnf texmf.cnf.bak 297*00b67f09SDavid van Moolenbroek 298*00b67f09SDavid van Moolenbroek o edit the lines in texmf.cnf with these keys to these values: 299*00b67f09SDavid van Moolenbroek 300*00b67f09SDavid van Moolenbroek main_memory = 1100000 301*00b67f09SDavid van Moolenbroek hash_extra = 15000 302*00b67f09SDavid van Moolenbroek pool_size = 500000 303*00b67f09SDavid van Moolenbroek string_vacancies = 45000 304*00b67f09SDavid van Moolenbroek max_strings = 55000 305*00b67f09SDavid van Moolenbroek pool_free = 47500 306*00b67f09SDavid van Moolenbroek nest_size = 500 307*00b67f09SDavid van Moolenbroek param_size = 1500 308*00b67f09SDavid van Moolenbroek save_size = 5000 309*00b67f09SDavid van Moolenbroek stack_size = 1500 310*00b67f09SDavid van Moolenbroek 311*00b67f09SDavid van Moolenbroek sudo tex -ini -progname=hugelatex -fmt=hugelatex latex.ltx 312*00b67f09SDavid van Moolenbroek sudo texconfig init 313*00b67f09SDavid van Moolenbroek sudo texhash 314*00b67f09SDavid van Moolenbroek 315*00b67f09SDavid van Moolenbroek o For the jadetex macros you will need I recommend you get a more 316*00b67f09SDavid van Moolenbroek current version than what is packaged with openjade or jade. 317*00b67f09SDavid van Moolenbroek 318*00b67f09SDavid van Moolenbroek Checkout http://www.tug.org/applications/jadetex/ 319*00b67f09SDavid van Moolenbroek 320*00b67f09SDavid van Moolenbroek Unzip the file you get from there (should be jadetex-2.20 or 321*00b67f09SDavid van Moolenbroek newer.) 322*00b67f09SDavid van Moolenbroek 323*00b67f09SDavid van Moolenbroek In the directory you unzip: 324*00b67f09SDavid van Moolenbroek 325*00b67f09SDavid van Moolenbroek sudo make install 326*00b67f09SDavid van Moolenbroek sudo texhash 327*00b67f09SDavid van Moolenbroek 328*00b67f09SDavid van Moolenbroek NOTE: In the most uptodate "ports" for FreeBSD, jadetext is 2.20+ 329*00b67f09SDavid van Moolenbroek so on this platform you should be set as of 2001.01.08. 330