| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
| |
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]
|
| |
|
|
| |
[originally from svn r7051]
|
| |
|
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
| |
a range rather than a single year.
[originally from svn r7047]
|
| |
|
|
|
|
|
| |
hard-coding it. No practical gain, since the hard-coded entries were correct,
but aesthetically better.
[originally from svn r7046]
|
| |
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
| |
(which triggers err_infonodechar with fpos==NULL).
[originally from svn r7044]
|
| |
|
|
|
|
| |
use two encodings of the same font.
[originally from svn r7042]
|
| |
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
| |
any, I reckon.
[originally from svn r6994]
|
| |
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
| |
EN DASH, falling back to MINUS and then HYPHEN-MINUS. Make it so.
[originally from svn r6992]
|
| |
|
|
|
|
|
|
| |
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]
|
| |
|
|
| |
[originally from svn r6990]
|
| |
|
|
| |
[originally from svn r6989]
|
| |
|
|
|
|
| |
including testing some bug fixes it doesn't have yet.
[originally from svn r6988]
|
| |
|
|
|
|
| |
in Unicode, which we can't (reliably) in %%Title.
[originally from svn r6987]
|
| |
|
|
| |
[originally from svn r6985]
|
| |
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
| |
won't work properly.
[originally from svn r6982]
|
| |
|
|
|
|
|
| |
files. Halibut does not make use of this feature, but I hope that
one day it might.
[originally from svn r6980]
|
| |
|
|
| |
[originally from svn r6979]
|
| |
|
|
| |
[originally from svn r6977]
|
| |
|
|
| |
[originally from svn r6976]
|
| |
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
| |
fonts) may not be well handled, and may emit invalid PDF.
[originally from svn r6974]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
| |
values ever used are 15 and 7, so testing against 16 is silly.)
[originally from svn r6969]
[this svn revision also touched misc]
|
| |
|
|
| |
[originally from svn r6968]
|
| |
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
| |
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]
|
| |
|
|
| |
[originally from svn r6952]
|
| |
|
|
|
|
| |
the TODO list.
[originally from svn r6951]
|
| |
|
|
|
|
| |
Halibut's output 7-bit clean, which seems the best approach in PostScript.
[originally from svn r6950]
|
| |
|
|
| |
[originally from svn r6949]
|
| |
|
|
| |
[originally from svn r6938]
|
| |
|
|
|
|
| |
into its own function.
[originally from svn r6937]
|
| |
|
|
|
|
| |
silly, and eight isn't.
[originally from svn r6936]
|
| |
|
|
| |
[originally from svn r6931]
|
| |
|
|
|
|
| |
as recommended by the PDF spec.
[originally from svn r6923]
|
| |
|
|
| |
[originally from svn r6913]
|
| |
|
|
|
|
| |
Halibut uses.
[originally from svn r6912]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
a period specially _even_ if there's an \fB or similar escape
sequence before the period. Therefore, man_rdaddctrl() now doesn't
clear the QUOTE_INITCTRL flag just because it generated some text;
instead, its call sites clear the flag when the _type_ of generated
text is appropriate for this. This should remove an error from the
`lns' man page (utils/lns/lns.but), which was where I noticed the
problem.
[originally from svn r6871]
|
| |
|
|
|
|
|
|
|
| |
commit it. Add `-i' option to cstable, which causes charset names to
be output as CS_* constants where meaningful. (Doesn't apply to MBCS
base charsets, because CS_* constants identify _encodings_.)
[originally from svn r6728]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
commands, allowing the fixed words "Contents" and "Index" generated
in various output formats to be reconfigured into other languages.
[originally from svn r6724]
|
| |
|
|
|
|
| |
producing output on stdout even in -c mode.
[originally from svn r6707]
|