| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
| |
text fragments appear in the page graphics stream. Therefore, I
should take care to display the leaders _before_ the page number in
each contents entry.
[originally from svn r4105]
|
| |
|
|
|
|
|
|
|
|
|
| |
ustrfroma, utoa_dup and ufroma_dup now take a charset parameter, and
also have a variety of subtly distinct forms. Also, when a \cfg
directive is seen in the input file, the precise octet strings for
each parameter are kept in their original form as well as being
translated into Unicode, so that when they represent filenames they
can be used verbatim.
[originally from svn r4097]
|
| |
|
|
| |
[originally from svn r4084]
|
| |
|
|
|
|
|
|
| |
of the same font and position designations. Reduced the size of the
Halibut manual PDF to less than half what it started out as, and the
PS one to more like a third of its original size.
[originally from svn r4083]
|
| |
|
|
| |
[originally from svn r4080]
|
| |
|
|
|
|
| |
output files.
[originally from svn r4079]
|
| |
|
|
|
|
| |
should not also point to a page in the contents! :-)
[originally from svn r4078]
|
| |
|
|
| |
[originally from svn r4077]
|
| |
|
|
|
|
|
|
| |
basically usable, and certainly it entirely includes the level of
functionality which was provided by our ancestor Perl script. So I
think I'll stop coding frantically and have a rest!
[originally from svn r4074]
|
| |
|
|
|
|
|
| |
Funny, I thought that would be as hard again as the main index
processing, and it turned out to be nearly trivial.
[originally from svn r4073]
|
| |
|
|
|
|
| |
the fine details right.
[originally from svn r4072]
|
| |
|
|
|
|
| |
permanently bold. Fixed.
[originally from svn r4071]
|
| |
|
|
| |
[originally from svn r4070]
|
| |
|
|
| |
[originally from svn r4069]
|
| |
|
|
|
|
|
|
|
|
| |
correspond exactly to a source paragraph. Should allow me to create
multiple printed paragraphs from the same source paragraph (i.e. a
contents entry for each heading in addition to the heading itself),
and invent entirely new printed paragraphs of my own (e.g. for index
entries).
[originally from svn r4068]
|
| |
|
|
| |
[originally from svn r4067]
|
| |
|
|
| |
[originally from svn r4066]
|
| |
|
|
| |
[originally from svn r4065]
|
| |
|
|
|
|
|
|
| |
bonuses for breaking in particular places. (For example, it's
especially bad to break just after a heading, and especially good to
break just before one.)
[originally from svn r4064]
|
| |
|
|
| |
[originally from svn r4062]
|
| |
|
|
|
|
|
|
| |
font selection in headings, mentioning section numbers, bullets,
list item numbers, code paragraphs etc). The PS/PDF output now
actually looks like the document it's supposed to be :-)
[originally from svn r4061]
|
| |
|
|
|
|
|
| |
document, and references to external URLs for which acroread will
start a web browser.
[originally from svn r4060]
|
| |
|
|
|
|
|
| |
of semantics as to whether a `last' pointer pointed to the last
relevant thing in a list, or the one beyond that. Oops.
[originally from svn r4059]
|
|
|
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]
|
