| Commit message (Collapse) | Author |
|---|
|
I forgot to add the new --chm option to it yesterday, and also I've
just noticed that it still describes --html as XHTML only, which
hasn't been true for years.
|
|
fonts is difficult.
[originally from svn r7281]
|
|
conceptually const but not declared as such. Halibut is now back to
the practically-speaking-pointless but rather satisfying status of
having no global writable data whatsoever :-)
[originally from svn r5476]
[this svn revision also touched charset,filter,timber]
|
|
character sets.
(Also make libcharset `return_in_enum' values saner.)
[originally from svn r5341]
[this svn revision also touched charset,filter,timber]
|
|
- After discussion with Simon, change the default input charset back to ASCII,
rather than trying to work it out from the locale, for the sake of promoting
.but file portability.
- Add a new command-line option "--input-charset=csname", which overrides the
ASCII default for all input files (since there's no other way to use a
non-ASCII-compatible input file).
- Output a warning if -Cinput-charset:foo is specified that it has no effect.
- Update the docs to match all this. Also try to clarify some other things in
this area that caught me out.
[originally from svn r5332]
|
|
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]
|
|
[originally from svn r4055]
|
|
[originally from svn r4026]
|
|
[originally from svn r1800]
|
