| Commit message (Collapse) | Author | Age |
| ... | |
| |
|
|
|
|
|
| |
objects and removing some surplus whitespace. This saves 40K in the Halibut
manual.
[originally from svn r6688]
|
| |
|
|
|
|
|
| |
so I don't have to press SPACE so much to get to the interesting part of the
file.
[originally from svn r6687]
|
| |
|
|
|
|
| |
a few K and a lot of calls to scalefont and setfont, which is probably good.
[originally from svn r6686]
|
| |
|
|
|
|
|
|
| |
technically incorrect, though it works perfectly well with xpdf. To do
it properly requires actually parsing the unencrypted part of a Type 1
font, which will be a bit tedious in C.
[originally from svn r6685]
|
| |
|
|
|
|
| |
fonts in PDF output.
[originally from svn r6684]
|
| |
|
|
|
|
| |
to embed /FirstChar, /LastChar, /Widths or (soon) /FontDescriptor for them.
[originally from svn r6683]
|
| |
|
|
| |
[originally from svn r6682]
|
| |
|
|
|
|
|
|
| |
loading AFM files, we recognise them by name, and we can't embed fonts in
the output (which is also invalid, though accepted by xpdf, in the PDF case).
Oh, and there's no documentation. Still, it's a start.
[originally from svn r6681]
|
| |
|
|
|
|
| |
to skip unused code points.
[originally from svn r6673]
|
| |
|
|
|
|
| |
of the document. This means that (e.g.) gv displays the title correctly.
[originally from svn r6672]
|
| |
|
|
|
|
|
| |
putting one in each page, put a single one in the top-level page tree node.
This saves us all a few kilobytes in the Halibut manual.
[originally from svn r6671]
|
| |
|
|
|
|
|
| |
accepted length of A4 paper in the PostScript/PDF world, so use it as
our default.
[originally from svn r6669]
|
| |
|
|
|
|
| |
existing instance. This saves outputting each font several times.
[originally from svn r6668]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
load font metrics dynamically, we're restricted to the fonts whose metrics
are compiled into Halibut. Font structures aren't reused when the same
font is specified twice, nor are unused fonts removed from the output.
Finally, the default configuration overflows lines in the manual, but this
would need a change to Halibut's grammar to fix.
Still, what's there works.
[originally from svn r6667]
|
| |
|
|
|
|
|
| |
good free licence. Abide by its terms even though I'm not sure Halibut
is a derived work in law.
[originally from svn r6666]
|
| |
|
|
| |
[originally from svn r6665]
|
| |
|
|
|
|
|
| |
the description from the name in the NAME section of a manpage. Halibut
can do that now, so make use of that ability.
[originally from svn r6664]
|
| |
|
|
| |
[originally from svn r6663]
|
| |
|
|
|
|
|
| |
string to the output. This incidentally fixes a bug whereby font changes
at the start of a line weren't resetting QUOTE_INITCTRL.
[originally from svn r6660]
|
| |
|
|
|
|
|
| |
its own function, since it's called so many times. Also call it in two places
I'd missed.
[originally from svn r6659]
|
| |
|
|
|
|
| |
works correctly inside macro arguments.
[originally from svn r6658]
|
| |
|
|
|
|
|
|
| |
beginning
to get ugly.
[originally from svn r6654]
|
| |
|
|
| |
[originally from svn r6653]
|
| |
|
|
|
|
|
|
|
| |
side-effect
that breaking spaces are now forces to be ASCII spaces in output, whatever output
charset is in force. I doubt this will inconvenience anyone.
[originally from svn r6652]
|
| |
|
|
|
|
|
| |
is processed by nroff, the rule is made up of \cfg{man-rule}
characters (same defaults as \cfg{text-rule}).
[originally from svn r6651]
|
| |
|
|
|
|
|
| |
and incidentally proper (single) quotation marks too. This reworks a lot of
man_convert, but I think the result is correct.
[originally from svn r6650]
|
| |
|
|
|
|
| |
backend.
[originally from svn r6649]
|
| |
|
|
|
|
| |
line-drawing function.
[originally from svn r6648]
|
| |
|
|
|
|
|
|
|
|
|
| |
where two SBCS code points mapped to a single Unicode point.
Changed so that by default it favours the lower SBCS code point.
On ixion, this highlighted ambiguities in CS_MAC_THAI, CS_MAC_SYMBOL, and
CS_VISCII. Guessed at a preference for the first two and added "sortpriority"
directives. (No idea about VISCII.)
[originally from svn r6641]
[this svn revision also touched charset,filter,putty,timber]
|
| |
|
|
|
| |
[originally from svn r6513]
[this svn revision also touched putty,putty-website,puzzles]
|
| |
|
|
|
|
|
|
| |
implementations of libcharset, since we've had at least one request for
it in PuTTY.
[originally from svn r6499]
[this svn revision also touched charset,filter,putty,timber]
|
| |
|
|
|
|
|
|
|
| |
genuinely portable form. (Thanks to IWJ for ideas.) While I'm here,
add a couple of explicit `unsigned' casts and U suffixes to prevent
more pedantic compilers from warning.
[originally from svn r6463]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
in future, add `-ansi -pedantic' to the Halibut default compile
options and fix the few resulting warnings (mostly signed/unsigned
char mismatches and commas at the ends of enums). The one remaining
warning I'm still seeing is `missing initializer' for the big table
in charset/iso2022.c, but I think the code genuinely is more
readable this way, and I haven't found a gcc option to disable that
specific warning.
[originally from svn r6458]
|
| |
|
|
| |
[originally from svn r6457]
|
| |
|
|
|
|
| |
by the use of a comma as a decimal separator.
[originally from svn r6456]
|
| |
|
|
|
|
|
|
| |
auto-type-checking DEPLANARISE and REPLANARISE macros have turned
out to only work in gcc, which is a shame.
[originally from svn r6455]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
| |
anything in it! In its current form it presents the portability
hazards of an empty structure and an empty source file. Therefore,
I'm removing it; if I ever have a clear idea of what a user style
mechanism ought to look like, it might make a reappearance, but
don't hold your breath.
[originally from svn r6453]
|
| |
|
|
|
|
|
|
| |
(Fixes a warning in iso2022.c. There are lots more.)
[originally from svn r6424]
[r6378 == 41e50e9f2e3e67da805c5d9037cc650f363e5279]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
what that's useful for but it seemed a pity not to do it) and
compound text.
I've completely removed the compound text implementation from
iso2022s.c in favour of using the more flexible iso2022.c, meaning
we can cope with nastiness such as DOCS.
This is largely untested: I've checked it on small examples as I
went along, but it lacks anything resembling a proper test suite.
[originally from svn r6378]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
I'm here, I've updated the URL to the Adobe Glyph List.
[originally from svn r6376]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
points out that it's perfectly possible to generate an empty
paragraph using legal Halibut syntax: a paragraph containing nothing
but a \#{...} comment will do the job, and is quite likely to happen
if you've commented out a load of Halibut code. Therefore, an empty
paragraph is now silently ignored rather than being an error
condition in itself; if you create an empty paragraph due to it
containing an unrecognised directive, then you'll get an error for
_that_ and only that.
[originally from svn r6361]
|
| |
|
|
|
|
|
| |
works (unlike our old one).
[originally from svn r6358]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6357]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6354]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6353]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RO data size in cns11643.o from 400k to 240k. Relies on there being
at most seven planes (7*94*94 <= 64k) and on the character set not
encoding any Unicode code point above U+40000; if either of these
becomes untrue later on we can always fall back to the previous
approach, or to somewhere between that and here.
The new version passes all the same tests as the old one did, and
generates the same output under the new `cstable -v'. I'm confident
that I haven't broken it.
[originally from svn r6351]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6350]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
point in every charset.
[originally from svn r6349]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6348]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r6347]
[this svn revision also touched charset,filter,timber]
|