| Age | Commit message (Collapse) | Author |
|---|
|
1. Support specifying the .Bd and .Bl -offset as a macro default width;
while here, simplify the code handling the same for .Bl -width.
2. Correct handling of .Bl -offset arguments: unlike .Bd -offset, the
arguments "left", "indent", and "indent-two" have no special meaning.
3. Fix the scaling of string length -offset and -width arguments in -Thtml.
Triggered by an incomplete documentation patch from bentley@.
|
|
would be the next stage of embiggening. restore 16k.
|
|
if one pipe stalls out. from a diff by Arne Becker.
(buffer size left alone for now)
|
|
|
|
main.c: add -K to usage() and wrap nicely
ok schwarze
|
|
of kristaps@' version of the preconv(1) utility into mandoc(1);
positive feedback from bentley@ and no concern raised when shown on tech@
|
|
Correct ASCII rendering: \(lb \(<> \(sd
Make ASCII rendering agree with groff, using backspace overstrike:
\(da \(ua \(dA \(uA \(fa \(c* \(c+ \(ib \(ip \(/_ \(pp \(is \(dd \(dg
|
|
escape sequences just like it was earlier implemented for -Thtml.
Do not let control characters other than ASCII 9 (horizontal tab)
propagate to the output, even though groff allows them; but that
really doesn't look like a great idea.
Let mchars_num2char() return int such that we can distinguish invalid \N
syntax from \N'0'. This also reduces the danger of signed char issues
popping up.
|
|
representation, not for character escapes with unknown names.
According to groff, the latter produce no output, and we now warn
about them.
|
|
validity of character escape names and warn about unknown ones.
This requires mchars_spec2cp() to report unknown names again.
Fortunately, that doesn't require changing the calling code because
according to groff, invalid character escapes should not produce
output anyway, and now that we warn about them, that's fine.
|
|
Accept only 0xXXXX, 0xYXXXX, 0x10XXXX with Y != 0.
This simplifies mchars_num2uc().
|
|
with groff, in particular in cases where groff uses backspace overstrike.
In two cases, agreement is impossible because groff clobbers the
previous line: \(*G \(*S
In a number of cases, groff rendering is so misleading that i chose
to render differently: \(Sd \(TP \(Tp \(Po \(ps \(sc \(r! \(r? \(de
While here, also correct the \(la and \(ra Unicode code points.
|
|
|
|
|
|
Of course, this is only a minor improvement; it would be much better
to support non-ASCII characters in these output modes, but that
would require major changes that i'm not going to work on right now.
The main reason for doing this is that it allows to get ASCII output
closer to groff.
|
|
in one common, safe way instead of three different ways. In particular,
* skip NUL, it is used to mean "no output desired"
* deny 0x01-0x1F and 0x7F-0x9F, print REPLACEMENT CHARACTER instead
* print 0x20-0x7E literally or name-encoded, as required
* print characters above 0x9F numerically
|
|
In UTF-8 output, do not print anything if mchars_spec2cp() returns 0.
In particular, this repairs handling of zero-width spaces (\&).
While here, let mchars_spec2cp() return 0xFFFD instead of -1
if the character is not found, simplifying the using code.
In HTML output, do not print obfuscated ASCII characters and
do not test for one-char escapes, mchars_spec2cp() already does that.
|
|
Prefer fopen("re") over fopen("r")+fcntl(F_SETFD)
ok otto@ millert@
|
|
sequences above codepoint 512 by doing a reverse lookup in the
existing mandoc_char(7) character table.
Again, groff isn't smart enough to do this and silently discards such
escape sequences without printing anything.
|
|
code points, provide ASCII approximations. This is already much better
than what groff does, which prints nothing for most code points.
A few minor fixes while here:
* Handle Unicode escape sequences in the ASCII range.
* In case of errors, use the REPLACEMENT CHARACTER U+FFFD for -Tutf8
and the string "<?>" for -Tascii output.
* Handle all one-character escape sequences in mchars_spec2{cp,str}()
and remove the workarounds on the higher level.
|
|
ok schwarze@
|
|
POLLHUP too. OK deraadt@
|
|
|
|
sort.c:295:35: warning: '&&' within '||' [-Wlogical-op-parentheses]
ok guenther@
|
|
equal NULL.
apprentice.c:645:13: warning: using the result of an assignment as a condition without parentheses [-Wparentheses]
With input and ok guenther@
|
|
inside tables, sorry. So don't even try to parse tbl(7) blocks for
eqn(7) delimiters.
Broken table layout found in glPixelMap(3) while investigating
a bug report by Theo Buehler <theo at math dot ethz dot ch>.
|
|
by Theo Buehler <theo at math dot ethz dot ch> on tech@:
Do not attempt to parse empty equations.
|
|
* drop trivial wrapper function roff_openeqn()
* drop unused first arg of function eqn_alloc()
* drop usused member "name" of struct eqn_node
|
|
|
|
OK florian@ henning@
|
|
So remove the call to setnetent(3) which is a no-op
here (except for consuming a file descriptor)
and the call sethostent(3) which is a no-op in general.
Also remove the misleading reference to networks(5) from the manual.
OK okan@ henning@
|
|
programs.
ok deraadt@ millert@
|
|
In particular, do not call getnetbyaddr(3), use gethostbyaddr(3) only.
Do not call setnetent(3) and the dummy sethostent(3).
OK henning@; and deraadt@ agrees with the general direction.
|
|
with our actual implementation, which also agrees with POSIX;
triggered by guenther@'s answer to a question from chrisz@;
ok chrisz@ guenther@
|
|
|
|
|
|
gap found by guenther@ following a question asked
by Frank Brodbeck <fab at split dash brain dot de>;
while here, sort escape sequences,
this part of the patch from Frank Brodbeck;
ok guenther@
|
|
ok bcook@
|
|
|
|
|
|
|
|
reported by justin mayes on misc@
ok deraadt@
|
|
|
|
|
|
|
|
|
|
|
|
removal suggested by daniel@; ok deraadt@
|
|
|
|
|
