diff options
| author | Jeffrey H. Kingston <jeff@it.usyd.edu.au> | 2010-09-14 20:36:35 +0000 |
|---|---|---|
| committer | Jeffrey H. Kingston <jeff@it.usyd.edu.au> | 2010-09-14 20:36:35 +0000 |
| commit | b10d39aec443165093f8f28bc6f940530b89cdaf (patch) | |
| tree | 63a1ef3b3f1d2562c498291cda341a2171a1fe1c /doc/user/fmt_setu | |
| parent | 2f4268e5e02216be53cd85816362191373512463 (diff) | |
| download | lout-b10d39aec443165093f8f28bc6f940530b89cdaf.tar.gz | |
Lout 3.21.
git-svn-id: http://svn.savannah.nongnu.org/svn/lout/trunk@11 9365b830-b601-4143-9ba8-b4a8e2c3339c
Diffstat (limited to 'doc/user/fmt_setu')
| -rw-r--r-- | doc/user/fmt_setu | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/doc/user/fmt_setu b/doc/user/fmt_setu index 6e1bb05..0f59b56 100644 --- a/doc/user/fmt_setu +++ b/doc/user/fmt_setu @@ -49,17 +49,15 @@ The remainder of this section is a tour through @Code {doc}, explaining the various parts and how to modify them. The first lines that actually do anything are these: @ID @OneRow @Code { -"@SysInclude { fontdefs }" "@SysInclude { langdefs }" "@SysInclude { bsf }" "@SysInclude { dsf }" "@SysInclude { docf }" } We already know that @Code "@SysInclude" causes Lout to read a file from -the Lout system include directory. Files @Code fontdefs and @Code langdefs -fontdefs.file @Index { @Code "fontdefs" file } +the Lout system include directory. File @Code langdefs langdefs.file @Index { @Code "langdefs" file } -tell Lout what fonts and languages there are. Files @Code "bsf" and +tells Lout what languages there are, and files @Code "bsf" and @Code "dsf" contain bsf.file @Index { @Code "bsf" file } dsf.file @Index { @Code "dsf" file } @@ -178,7 +176,8 @@ or all document types. The setup file ends with a comment identifying a spot where database declarations may database.dec @Index { database declarations, where to put } -be put, and one such declaration, for reference printing styles. +be put, and two such declarations, one for fonts and the other for +reference printing styles. @PP The setup files used with other packages, such as C and C++ program printing, diagrams, and graphs, are similar to the @Code { doc } setup file we |