summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* When adding a new file, it helps to "svn add" it.Ben Harris2007-02-03
| | | | [originally from svn r7200]
* When loading a Type 1 font, remember to terminate the linked list we loadBen Harris2007-02-03
| | | | | | it into. [originally from svn r7199]
* Add support for using TrueType fonts, including embedding in PostScript butBen Harris2007-02-03
| | | | | | | not yet in PDF. There's a lot of cleaning up to be done, especially in the area of error, but I think it would be better committed gradually. [originally from svn r7198]
* Add an `Up' link to the HTML navigation bar of sufficiently deep documents.Jacob Nevins2007-01-31
| | | | | | | | (This doesn't affect any of the source texts I know about.) Also add <link rel="up">, even in the cases where it's just the same as <link rel="ToC">. (This does.) [originally from svn r7193]
* I haven't found any browsers that do anything disgusting withJacob Nevins2007-01-31
| | | | | | | \cfg{html-rellinks}, and it generally seems to be a Good Thing, so I've turned it on by default. (The lurkers support me in u2u.) [originally from svn r7188]
* Use consistent capitalisation for HTML tags.Jacob Nevins2007-01-28
| | | | [originally from svn r7178]
* Minimal support for <LINK REL="next"> etc machine-readable navigation links.Jacob Nevins2007-01-28
| | | | | | | | | | | | | Off by default for now, but I don't intend that it should stay this way; they seem useful and harmless. I just want to check a few more browsers to ensure they don't do anything obnoxious with them. So far I've only seen lynx and links do something with them (provide toolbars). iCab and some Mozilla derivatives/extensions are also alleged to do this; Opera is said to allow PgDn type browsing through the entire set of pages; and Mozilla is rumoured to use the "next" link for prefetching. [originally from svn r7177]
* Tweak the HTML Help output to enable Previous/Next navigation in the generatedJacob Nevins2007-01-28
| | | | | | | | | | | | | | | | CHM, and added the toolbar buttons for this. Also rationalised the other options a bit: - added Forward button (since we have Back); - removed Locate/Sync (since we have auto-sync enabled for the ToC); - removed Stop and Refresh (mostly a waste of space for help, but still available from the Options menu if users really want them); - enabled advanced facilities on the Search tab (search within results, etc). All this seems to have had no obvious ill effects (tested on Win98), although the resulting CHM file is slightly bigger (~3kbyte, <1%). [originally from svn r7176]
* Add support for PFB files. This seems to have caused me to completelyBen Harris2007-01-27
| | | | | | | | rewrite the Type 1 font support, and I'm sure the result is more complex than it needs to be, but it seems to work correctly, so I shouldn't complain. [originally from svn r7175]
* Duplicate fix of Kevin Lyles's bug from r7092.Simon Tatham2007-01-11
| | | | | [originally from svn r7093] [r7092 == c06e371f55b97576421588d21d809c02c637584b in puzzles repository]
* Update the TODO list to match the current state of the world.Ben Harris2007-01-07
| | | | [originally from svn r7070]
* Add a mechanism for disabling ligature substitution for an entire paragraphBen Harris2007-01-07
| | | | | | and apply it to code paragraphs. [originally from svn r7069]
* Our standard mapping for the first font should start at 0x20, not 0x21.Ben Harris2007-01-07
| | | | [originally from svn r7067]
* Support for getting ligature information from AFM files, which was theBen Harris2007-01-07
| | | | | | whole point of the glyph renumbering. [originally from svn r7066]
* Make ps_glyph_to_unicode() take a glyph index instead of a glyph name.Ben Harris2007-01-06
| | | | [originally from svn r7062]
* Overhaul of glyph-name handling in the paper backends. Before, we hadBen Harris2007-01-06
| | | | | | | | | | a separate dense array of glyph names for each font, and referenced glyphs by indicies into that array, which meant that the array had to be set up before we could generate any indices. Now we have an overall array of glyph names, and use the same glyph indicies for all fonts. Some arrays have had to turn into tree234s as a result. [originally from svn r7061]
* I've worked out why ligation was being (correctly) suppressed in codeBen Harris2007-01-06
| | | | | | | paragraphs and found some cases where it isn't. Add test cases for these to remind me to deal with them later. [originally from svn r7060]
* James should apparently have been removed from this file years ago. Fix that.Ben Harris2007-01-02
| | | | [originally from svn r7051]
* Fix the behaviour of constructions like \e{index \i{term}} -- the index tagJacob Nevins2007-01-01
| | | | | | | | | | | was causing emphasis to be broken (particularly noticeable in text-like backends). There are some instances of this in the PuTTY manual, for instance. Unfortunately, \k references in similar situations still aren't quite right, but fixing that will be more involved, and I haven't found any instances yet. [originally from svn r7049]
* Bump copyright dates, and change the one at the start of the manual to beBen Harris2007-01-01
| | | | | | a range rather than a single year. [originally from svn r7047]
* Generate ligature information from the standard AFM files rather thanBen Harris2007-01-01
| | | | | | | hard-coding it. No practical gain, since the hard-coded entries were correct, but aesthetically better. [originally from svn r7046]
* Initial ligature support. This adds support for emitting ligatures, and addsBen Harris2006-12-31
| | | | | | | | the "fi" and "fl" ligatures to the built-in fonts, but doesn't add support for reading ligature information from AFM files because that requires coping with forward references to glyph names, which is tricky. [originally from svn r7045]
* Fix segfault in info backend when invoked with inputs/test.butJacob Nevins2006-12-31
| | | | | | (which triggers err_infonodechar with fpos==NULL). [originally from svn r7044]
* Emit lots of odd characters so as to test the paper backends' ability toBen Harris2006-12-31
| | | | | | use two encodings of the same font. [originally from svn r7042]
* Tweak /OUT pdfmark generation -- PLRM suggests that constructing a largeBen Harris2006-12-12
| | | | | | | | executable array is likely to use lots of stack space, which might be bad on Level 1 interpreters, so use the same mechanism as for other pdfmarks and have a procedure that does nothing if pdfmark isn't defined. [originally from svn r6995]
* These HHP window dimensions seem to be rubbish. Better off withoutSimon Tatham2006-12-12
| | | | | | any, I reckon. [originally from svn r6994]
* Rough-and-ready line wrapping for PostScript, to keep us below the DSC-mandatedBen Harris2006-12-12
| | | | | | | | 255 characters per line (excluding newline characters). In fact, it tries to keep us below 80 characters so as to make the PostScript more readable (and demonstrate that it's working). [originally from svn r6993]
* Actually, the separator in the "NAME" section really ought to be anBen Harris2006-12-11
| | | | | | EN DASH, falling back to MINUS and then HYPHEN-MINUS. Make it so. [originally from svn r6992]
* Support for the MS HTML Help system in the HTML back end. As yet ISimon Tatham2006-12-11
| | | | | | | | don't know how to write out a .CHM directly, but I am at least able to have the HTML back end write out the three auxiliary files which enable a .CHM to be generated using the MS HTML Help compiler. [originally from svn r6991]
* Just noticed that Ben missed another PostScript/PDF inversion.Simon Tatham2006-12-11
| | | | [originally from svn r6990]
* Fix amusing cut-and-paste error in section keywords :-)Simon Tatham2006-12-11
| | | | [originally from svn r6989]
* Make the title a bit scarier to test the PostScript backend some more,Ben Harris2006-12-10
| | | | | | including testing some bug fixes it doesn't have yet. [originally from svn r6988]
* Explicitly set the title via pdfmark, since that allows us to putBen Harris2006-12-10
| | | | | | in Unicode, which we can't (reliably) in %%Title. [originally from svn r6987]
* Remove accidentally-committed deflate-debugging code.Ben Harris2006-12-10
| | | | [originally from svn r6985]
* Put all the pieces together: introduce a secondary test mode forSimon Tatham2006-12-09
| | | | | | | winhelp.c which uses all my new library code to import an arbitrary PNG and embed it into the test help file. [originally from svn r6984]
* Remember to initialise the bmp array for AFM fonts, or Unicode fallbacksBen Harris2006-12-09
| | | | | | won't work properly. [originally from svn r6982]
* Support, in the winhelp module only, for adding pictures to .HLPSimon Tatham2006-12-09
| | | | | | | files. Halibut does not make use of this feature, but I hope that one day it might. [originally from svn r6980]
* Update copyright dates.Ben Harris2006-12-09
| | | | [originally from svn r6979]
* Some documentation of Halibut's font-embedding support, now that it works.Ben Harris2006-12-09
| | | | [originally from svn r6977]
* This somehow got missed in my "put PDF before PostScript" sweep.Ben Harris2006-12-09
| | | | [originally from svn r6976]
* Mention PDF before PostScript everywhere, partly because PDF is theBen Harris2006-12-09
| | | | | | | | | dominant format for print-oriented documents, but mostly because it's hard to mention pdfmark without having mentioned PDF already. Also mention pdfmark. [originally from svn r6975]
* Correct embedding of Type 1 fonts in PDF. Error cases (e.g. invalid Type 1Ben Harris2006-12-09
| | | | | | fonts) may not be well handled, and may emit invalid PDF. [originally from svn r6974]
* I've just noticed some unacceptably long lines in code paragraphs inSimon Tatham2006-12-07
| | | | | | | | | | | | | | | the Halibut manual. They turn out to be \cfg directives with multiple braced sections after them. The obvious thing to do for legibility would be to wrap those sections by putting newlines between } and {, but that isn't legal in the Halibut syntax. Therefore, it is now :-) For paragraph types which don't have any body text (such as \cfg), we are now lenient about whitespace between multiple keywords. So I can fix the docs so they don't go over the limit, and be confident that the fixed version is still technically accurate. [originally from svn r6970]
* Fix typo in limit test in deflate_buildhuf(). (The only two limitSimon Tatham2006-12-07
| | | | | | | values ever used are 15 and 7, so testing against 16 is silly.) [originally from svn r6969] [this svn revision also touched misc]
* Specify the /Border of /ANN pdfmarks correctly.Ben Harris2006-12-07
| | | | [originally from svn r6968]
* Update deflate.c to include nearly all the changes I've been makingSimon Tatham2006-12-06
| | | | | | | | in the main version. The one missing thing is the fancy new LZ77 compressor in misc/libcode/lz77.c, in whose stability I'm not yet confident enough to consider it ready for prime-time. [originally from svn r6967]
* Distingush font files from other input by magic number rather than name.Ben Harris2006-12-05
| | | | | | | | This prevents one having Halibut files that begin "StartFontMetrics", "%!FontType1-", or "%!PS-AdobeFont-", but I doubt that will be a great hardship. [originally from svn r6960]
* Two of the bugs listed in the man page are out of date: Unicode andSimon Tatham2006-12-04
| | | | | | | | | character set support, and the HTML back end, have both been extensively revamped since that section was written, and I think neither of them is shoddy enough to warrant this sort of self-disparagement any more. [originally from svn r6959]
* Paging through the newly compressed PDF manual to make sure itSimon Tatham2006-12-04
| | | | | | | | worked, I happened to notice this typo. I think Wikipedia might have permanently removed my ability to read any document for any purpose without spotting at least one error in it. [originally from svn r6958]
* Tweak prologue so that it works correctly on interpreters that don't supportBen Harris2006-12-03
| | | | | | | pdfmark, specifically by having the dummy versions of "p", "x", and "u" pop their arguments rather than leaving them on the stack to cause trouble. [originally from svn r6956]
generated by cgit v1.1 at 2026-05-04 11:51:08 +0000