halibut/.cvsignore, branch master My halibut tree Remove .cvsignore files on all active branches. 2004-11-16T15:29:14+00:00 Simon Tatham anakin@pobox.com 2004-11-16T15:29:14+00:00 765f04a95ddec81a89734749071cc41a0f784e21 [originally from svn r4788] [this svn revision also touched bmbm,caltrap,charset,enigma,filter,fonts,golem,grunge,html,lj,local,misc,polyhedra,putty,putty-website,putty-wishlist,puzzles,pycee,sdlgames,svn-tools,timber,tweak] 
[originally from svn r4788]
[this svn revision also touched bmbm,caltrap,charset,enigma,filter,fonts,golem,grunge,html,lj,local,misc,polyhedra,putty,putty-website,putty-wishlist,puzzles,pycee,sdlgames,svn-tools,timber,tweak]
Initial work on PS and PDF output. Because these two backends share 2004-04-13T13:17:48+00:00 Simon Tatham anakin@pobox.com 2004-04-13T13:17:48+00:00 ddd7bf5b8a173f375cf3de92a4493c0b80cc2de3 an enormous amount of preprocessing and differ only in their final output form, I've introduced a new type of layer called a `pre-backend' (bk_paper.c is one). This takes all the information passed to a normal backend and returns an arbitrary void *, which is cached by the front end and passed on to any backend(s) which state a desire for the output of that particular pre-backend. Thus, all the page layout is done only once, and the PS and PDF backends process the same data structures into two output files. Note that these backends are _very_ unfinished; all sorts of vital things such as section numbers, list markers, and title formatting are missing, the paragraph justification doesn't quite work, and advanced stuff like indexes and PDF interactive features haven't even been started. But this basic framework generates valid output files and is a good starting point, so I'm checking it in. [originally from svn r4058] 
an enormous amount of preprocessing and differ only in their final
output form, I've introduced a new type of layer called a
`pre-backend' (bk_paper.c is one). This takes all the information
passed to a normal backend and returns an arbitrary void *, which is
cached by the front end and passed on to any backend(s) which state
a desire for the output of that particular pre-backend. Thus, all
the page layout is done only once, and the PS and PDF backends
process the same data structures into two output files.
Note that these backends are _very_ unfinished; all sorts of vital
things such as section numbers, list markers, and title formatting
are missing, the paragraph justification doesn't quite work, and
advanced stuff like indexes and PDF interactive features haven't
even been started. But this basic framework generates valid output
files and is a good starting point, so I'm checking it in.

[originally from svn r4058]
Why hadn't I got round to creating a .cvsignore in the main source 2004-04-09T18:17:26+00:00 Simon Tatham anakin@pobox.com 2004-04-09T18:17:26+00:00 a4782d9b40772389c3131a2f3c75009c2dd42ba3 directory before? Silly me. [originally from svn r4048] 
directory before? Silly me.

[originally from svn r4048]