| Commit message (Collapse) | Author | Age |
| ... | |
| |
|
|
|
|
|
|
|
| |
specify characters to 'confuse' is to just put them on the command
line in the system multibyte encoding! In a UTF-8 terminal environment
this may very well be the easiest thing.
[originally from svn r9584]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Unicode values (typically two of them), and it finds cases in which
the provided characters are all encoded as the same thing in different
charsets and prints those charsets. So if you encounter, for example,
some piece of text which has U+0153 LATIN SMALL LIGATURE OE where you
might have expected U+00A3 POUND SIGN, simply run 'confuse 153 a3' and
it'll tell you which character sets the sender and receiver of the
text might have got confused between.
[originally from svn r9581]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
| |
[originally from svn r9580]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
the standalone deflate utility modes, so you can redirect output to a
file and end up with correct data in that file.
[originally from svn r9552]
|
| |
|
|
|
|
|
|
|
| |
dynamic block in which the backward-distances Huffman table contains
no entries at all. (In this situation it's impossible to use the
distance table, and therefore the block must contain nothing but
Huffman-coded literals.)
[originally from svn r9550]
|
| |
|
|
|
|
| |
pass something that isn't necessarily an unsigned short.
[originally from svn r9493]
|
| |
|
|
|
|
|
|
|
|
| |
possible to specify an indent which is _overall_ negative, i.e.
intended to be off the left-hand side of the text file. There's no
nice way to handle this, but printing O(2^32) spaces in a while (n--)
loop is particularly bad. Fix the loop to read while (n-- > 0), so
that at least it doesn't get _that_ badly confused.
[originally from svn r9491]
|
| |
|
|
|
|
|
|
| |
and a long int. Spotted by Ubuntu 12.04's gcc, and probably would have
caused trouble on 64-bit machines.
[originally from svn r9489]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
on an uncompressed block.
[originally from svn r9482]
[r6972 == 37af901cfe63ed062306e3835751e9b8e089e252 in misc repository]
|
| |
|
|
| |
[originally from svn r9478]
|
| |
|
|
| |
[originally from svn r9476]
|
| |
|
|
|
|
|
| |
block headers. (Ubuntu 12.04's gcc spotted that nlen was unused, which
it shouldn't have been.)
[originally from svn r9475]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
converting a number! Oops. Now you can do things like
\cfg{text-list-indent}{-2}
\cfg{text-listitem-indent}{2}
to get your bullets placed in the left margin rather than indenting
the paragraphs of your list.
[originally from svn r9474]
|
| |
|
|
|
|
|
| |
tok_eop, to prevent Halibut tight-looping when a definition is the
last thing in a file.
[originally from svn r9419]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I had wrongly believed my TYPECHECK macro double-evaluated one of its
arguments and hence would cause side effects to happen twice. But in
fact I've just realised that although it double-_expands_ the
argument, it doesn't double-_evaluate_ it: the two expansions occur in
mutually exclusive branches of a ?:, and hence cannot both be
executed.
So I've removed the comment that says my macro is rubbish. My macro is
in fact great :-)
[originally from svn r9328]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
| |
[originally from svn r9327]
[r9326 == c72d4b413f024e3c50645caceaddbb65401fb06a in putty repository]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
| |
[originally from svn r9259]
|
| |
|
|
|
|
|
|
|
| |
work on Windows, because input files are never opened in binary
mode. Introduce a small piece of compensatory mechanism, which opens
files initially in binary mode and then reopens them as text if
they're determined not to match any binary file type. I hope.
[originally from svn r8889]
|
| |
|
|
|
|
| |
look less as if they're the _only_ config options.
[originally from svn r8842]
|
| |
|
|
| |
[originally from svn r8743]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"-" as a special file name meaning standard output. I've restricted
it to just those output formats which can predictably output only
one file, just for the sake of not having to faff too much with the
others.
Probably what I should have done for all of this would have been to
write a set of wrappers around fopen, fclose and everything in
between, and use them everywhere. Those wrappers would uniformly
detect "-" and convert it into stdin or stdout as appropriate, would
avoid fclosing those files for real when told to close them, and
would also be able to handle reading a little bit of data from the
start of a file and then pushing it all back even if the file were
not seekable (which would allow input.c to lose the ugly special
case whereby it can't currently read font files from standard
input).
[originally from svn r8729]
|
| |
|
|
|
|
| |
the special filename '-'.
[originally from svn r8728]
|
| |
|
|
|
|
|
|
| |
apparently this is preferred (it's what pod2man uses); cf Debian #496063,
#159872.
[originally from svn r8641]
[r8309 == 73e8c7d1b4ac77ec1b5acc700cb3af277a150bcf]
|
| |
|
|
|
|
|
| |
(via Colin in Debian bug#496063).
[originally from svn r8640]
[r8321 == 5e7a3a5b1bbaccb7ce7d61bb9bc4654924135dfb]
|
| |
|
|
|
|
|
| |
the list.
[originally from svn r8498]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
\cfg{paper-contents-margin}. Also correct the spelling of the
former.
[originally from svn r8424]
|
| |
|
|
|
|
| |
Watson.)
[originally from svn r8422]
|
| |
|
|
|
|
| |
Fix it.
[originally from svn r8421]
|
| |
|
|
|
|
|
|
|
| |
unsigned char. On platforms were char is signed, passing plain char won't
cut it. Make sure we case chars to unsigned char before passing them to
tolower().
[originally from svn r8404]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
| |
[originally from svn r8322]
[r8309 == 73e8c7d1b4ac77ec1b5acc700cb3af277a150bcf]
[r8321 == 5e7a3a5b1bbaccb7ce7d61bb9bc4654924135dfb]
|
| |
|
|
|
|
|
|
|
|
| |
contexts get output usefully in the face of UTF-8 *roff implementations.
Works on Debian-derived distributions (and hence along with r8309 should fix
#496063), but I'm slightly worried about portability as I've used a named
character "\(aq" which doesn't appear in the "classic" reference CS TR #54.
[originally from svn r8321]
[r8309 == 73e8c7d1b4ac77ec1b5acc700cb3af277a150bcf]
|
| |
|
|
| |
[originally from svn r8320]
|
| |
|
|
|
|
|
| |
to try to put them into an Info node name, so as to avoid the error
message when it fails.
[originally from svn r8313]
|
| |
|
|
|
|
| |
(Embarrassingly, this was showing up in inputs/test.but itself.)
[originally from svn r8312]
|
| |
|
|
|
|
|
| |
initialisers, so that gcc stops whining.
[originally from svn r8311]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
| |
[originally from svn r8310]
|
| |
|
|
|
|
|
|
|
|
| |
because otherwise UTF-8 versions of man(1) tend to turn them into
Unicode hyphen characters, with the result that if you cut and paste
sample command lines out of man pages in the obvious way then the
things that look like hyphens are not in fact the character that the
program in question would recognise as an option introducer.
[originally from svn r8309]
|
| |
|
|
|
|
|
| |
support for it.
[originally from svn r8151]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
| |
endings, remove \r from input lines.
[originally from svn r8113]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
unsigned int, after a correspondent mentioned that DJGPP produces a
very scary warning about integer promotion making use of the former
in va_arg non-portable. Whether or not that's standards-justifiable,
it's certainly the case that we were casting _to_ wchar_t from
unsigned int in all cases of this error actually being used, so the
simplest thing is just to transfer the number through va_arg as
unsigned.
[originally from svn r8112]
|
| |
|
|
|
|
| |
\cfg{html-section-shownumber}{n} undefined.
[originally from svn r7929]
|
| |
|
|
|
|
|
|
|
| |
both the back ends which currently support that, to leave out
chapter and section numbers totally in section headings. Can be
useful for publishing man pages (which don't normally want section
numbers) on the web.
[originally from svn r7892]
|
| |
|
|
|
|
| |
that can't be resolved (apart from warning about it).
[originally from svn r7800]
|
| |
|
|
| |
[originally from svn r7799]
|
| |
|
|
|
|
| |
'cmap' refers to a character off the end of the glyphIndexArray.
[originally from svn r7798]
|
| |
|
|
|
|
|
|
|
| |
output length to charset_{to,from}_unicode, permitting convenient
dry-running of conversions to determine the required output length
and/or test for the presence of difficult characters.
[originally from svn r7677]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
|
|
|
|
| |
_output_ length, not the input length. Adjust accordingly.
This has the side effect of working around what I believe to be a
bug in DJGPP's mbstowcs(), namely that if you give it a string which
exactly fits in the output length _without_ the trailing NUL, then
it will write n-1 characters of the string plus a NUL where I
believe it should write n characters of the string and no NUL.
[originally from svn r7622]
|
| |
|
|
|
| |
[originally from svn r7495]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
|
|
|
|
| |
used by GNU Emacs. This is likely to be useful for generating or
interpreting "coding:" entries in file local variables.
[originally from svn r7455]
[this svn revision also touched charset,filter,timber]
|
| |
|
|
| |
[originally from svn r7454]
|