summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* PDF outline headings, it turns out, should be encoded using eitherSimon Tatham2004-04-20
| | | | | | | | | | | | PDFDocEncoding or UTF-16BE. (The PDF specification's index is terribly bad; I looked under various obvious things such as `character set' and `string literal' with no success, and I didn't manage to find out what character set metadata string literals were intended to be interpreted in until I discovered from another source that the encoding was called PDFDocEncoding, and _then_ I was able to look that up in the index. They should have been using Halibut! :-) [originally from svn r4101]
* Text backend is now charset-enabled: the entire text file is builtSimon Tatham2004-04-20
| | | | | | | from the ground up in Unicode, and a single charset conversion pass is done over the data as it's output. [originally from svn r4100]
* Add some tests of input charset switching.Simon Tatham2004-04-20
| | | | [originally from svn r4099]
* Forgot to add *.ps and *.pdf to the `make clean' list!Simon Tatham2004-04-20
| | | | [originally from svn r4098]
* Infrastructure changes for character set support. ustrtoa,Simon Tatham2004-04-20
| | | | | | | | | | | 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]
* Support for \cfg{input-charset}. Input files can now be in ASCII,Simon Tatham2004-04-19
| | | | | | | 8859-*, UTF-8, or a variety of more fun encodings including various multibyte ones. [originally from svn r4095]
* Better robustness when backends encounter a Unicode character notSimon Tatham2004-04-19
| | | | | | representable in the output character set. [originally from svn r4094]
* Fix an oddity in PDFDocEncoding.Simon Tatham2004-04-18
| | | | | [originally from svn r4093] [this svn revision also touched charset,timber]
* Now that I've renamed the `test' program to `convcs', fix .cvsignore.Simon Tatham2004-04-17
| | | | | [originally from svn r4091] [this svn revision also touched charset,timber]
* `gcc -Wall' points out some signed/unsigned comparisons. Fixed.Simon Tatham2004-04-17
| | | | | [originally from svn r4090] [this svn revision also touched charset,timber]
* Now this is a top-level CVS module, it should have LICENCE andSimon Tatham2004-04-17
| | | | | | | MODULE files of its own. [originally from svn r4089] [this svn revision also touched charset,timber]
* Link libcharset into Halibut. (This involved faffing withSimon Tatham2004-04-17
| | | | | | | | | CVSROOT/modules, so anyone with a checked-out copy of Halibut will unfortunately need to do `cvs co' again.) [originally from svn r4088] [added anachronistic .gitmodules so that past revisions can be checked out] [this svn revision also touched charset,timber]
* In preparation for using libcharset in Halibut, I've addedSimon Tatham2004-04-17
| | | | | | | | | PDFDocEncoding to the SBCS list; this is a custom superset of ISO-8859-1 used in PDF files to store user-visible text that isn't printed on a page (such as metadata and the document outline). [originally from svn r4087] [this svn revision also touched charset,timber]
* Include libcharset into both the Timber and Halibut checkouts.Simon Tatham2004-04-17
| | | | | | | | | Unfortunately this means people will have to do `cvs co' again to get this update, but that appears to be the price I pay for being able to conveniently share a single source base in this way. [originally from svn r4086] [this svn revision also touched charset,timber]
* Add a TODO entry.Simon Tatham2004-04-16
| | | | [originally from svn r4084]
* Compacted PS and PDF output files by removing redundant reiterationsSimon Tatham2004-04-16
| | | | | | | | 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]
* Standardise on using double quotes in HTML attributes. It turns outSimon Tatham2004-04-15
| | | | | | | | that the GNOME help browser is perfectly happy with Halibut's HTML _except_ that it doesn't approve of single quotes in places such as <a href='here'>. [originally from svn r4082]
* Support the \W{...}\i\c{...} combination used in the NASM manual.Simon Tatham2004-04-15
| | | | | | | | Halibut is now capable of reading the old NASM manual with only minor modifications, and probably doing a much better job of formatting it than rdsrc.pl ever did. (Certainly much _faster_!) [originally from svn r4081]
* Prevent a tight loop. Oops.Simon Tatham2004-04-15
| | | | [originally from svn r4080]
* Put the document's version IDs into comments in the PS and PDFSimon Tatham2004-04-15
| | | | | | output files. [originally from svn r4079]
* Ahem. If an indexable term appears in a section heading, the indexSimon Tatham2004-04-15
| | | | | | should not also point to a page in the contents! :-) [originally from svn r4078]
* Administrivia: update a TODO and a .cvsignore.Simon Tatham2004-04-14
| | | | [originally from svn r4077]
* After printing out the PDF manual and reading it through, here's aSimon Tatham2004-04-14
| | | | | | | | collection of minor edits for clarity, and also quite a few intended to keep down the length of lines in code paragraphs (because Courier is not just a thoroughly ugly font but is also WAY TOO WIDE). [originally from svn r4076]
* ... oh, except that minimal documentation might be helpful.Simon Tatham2004-04-14
| | | | [originally from svn r4075]
* Display the page numbers on every page. Right. I think this is nowSimon Tatham2004-04-14
| | | | | | | | 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]
* And now the page numbers in the index are PDF cross-references too.Simon Tatham2004-04-14
| | | | | | | 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]
* Implemented an index. Good _grief_, that was hard work to get allSimon Tatham2004-04-14
| | | | | | the fine details right. [originally from svn r4072]
* Typo during restructuring caused all code paragraphs to beSimon Tatham2004-04-14
| | | | | | permanently bold. Fixed. [originally from svn r4071]
* The contents section now contains PDF cross-references.Simon Tatham2004-04-14
| | | | [originally from svn r4070]
* Support for a contents section.Simon Tatham2004-04-14
| | | | [originally from svn r4069]
* Restructuring to remove the requirement for a printed paragraph toSimon Tatham2004-04-14
| | | | | | | | | | 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]
* Implemented PDF outlines.Simon Tatham2004-04-14
| | | | [originally from svn r4067]
* Implemented horizontal rules.Simon Tatham2004-04-14
| | | | [originally from svn r4066]
* Implemented lines under chapter titles.Simon Tatham2004-04-13
| | | | [originally from svn r4065]
* Fine-tuned the page breaking algorithm by adding penalties andSimon Tatham2004-04-13
| | | | | | | | 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]
* I wrote the info backend _days_ ago. About time the manpage stoppedSimon Tatham2004-04-13
| | | | | | listing its absence as a bug :-) [originally from svn r4063]
* Fix the TODO comments up a bit.Simon Tatham2004-04-13
| | | | [originally from svn r4062]
* Implemented all the missing rendering features (such as differentSimon Tatham2004-04-13
| | | | | | | | 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]
* Implement PDF link annotations: both internal hyperlinks within theSimon Tatham2004-04-13
| | | | | | | document, and references to external URLs for which acroread will start a web browser. [originally from svn r4060]
* Aha, _that's_ why paragraphs weren't properly justified. ConfusionSimon Tatham2004-04-13
| | | | | | | 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]
* Initial work on PS and PDF output. Because these two backends shareSimon Tatham2004-04-13
| | | | | | | | | | | | | | | | | | | 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]
* Yikes! Stack trash I'd never noticed before. Oops.Simon Tatham2004-04-12
| | | | [originally from svn r4056]
* Forgot to mention the info backend in the command-line help. Oops.Simon Tatham2004-04-12
| | | | [originally from svn r4055]
* Forgot to mention the info backend in the man page.Simon Tatham2004-04-10
| | | | [originally from svn r4054]
* The Emacs and Jed info readers don't like my index format: Info menuSimon Tatham2004-04-10
| | | | | | | | | | | | | | | items of the form `* stuff: Section 1.2.' are parsed by standalone info as `Section 1.2' followed by a period, but are parsed by other readers as `Section 1' followed by a period and then some spare text. Therefore, I've changed strategy, and the index is now full of *Note cross-references rather than menu items. On the plus side, this means there are no longer any special characters which we can't tolerate in an index entry; on the minus side, my shiny new infrastructure for tracking the filepos of index entries is now rendered pointless. I'll leave it in, though, since it may come in handy again. [originally from svn r4053]
* Add documentation for the info backend.Simon Tatham2004-04-10
| | | | [originally from svn r4052]
* Info backend now takes care to avoid magic characters in node namesSimon Tatham2004-04-10
| | | | | | | | | | and index terms (the Info format doesn't like them). In the course of this I've had to introduce some infrastructure for carrying a filepos forward from the definition of every RHS index term so that a particular backend can provide a usefully localised report of which index term had a problem. [originally from svn r4051]
* It would probably help to add a test of the INFO-DIR-ENTRY mechanismSimon Tatham2004-04-09
| | | | | | to the test file. Ahem. [originally from svn r4050]
* Add a config directive to generate the INFO-DIR-ENTRY things thatSimon Tatham2004-04-09
| | | | | | appear to be used to automatically construct /usr/info/dir. [originally from svn r4049]
* Why hadn't I got round to creating a .cvsignore in the main sourceSimon Tatham2004-04-09
| | | | | | directory before? Silly me. [originally from svn r4048]
generated by cgit v1.1 at 2026-04-27 01:49:18 +0000