aboutsummaryrefslogtreecommitdiffstatshomepage
Commit message (Collapse)AuthorAgeFilesLines
* Allow the five man(7) font macros to concatenate their line arguments,Ingo Schwarze2014-11-033-10/+31
| | | | | | | the same way the mdoc(7) macros marked MDOC_JOIN do it. In -Thtml, this removes bogus <br/> when the font macros are used in no-fill mode; issue found by jsg@ in the Xcursor(3) SYNOPSIS. As a bonus, this slightly reduces the size of the syntax tree.
* Use struct buf in libroff, it is very natural thereIngo Schwarze2014-11-013-173/+169
| | | | | | and reduces the number of arguments of many functions. While here, sprinkle some KNF. No functional change.
* Refactor, no functional change: Remove the parse point from struct buf.Ingo Schwarze2014-11-013-53/+48
| | | | | | Some functions need multiple parse points, some none at all, and it varies whether any of them need to be passed around. So better pass them as a separate argument, and only when needed.
* fix a typo causing crashes in Unicode string length measurementIngo Schwarze2014-11-011-2/+2
|
* Major bugsquashing with respect to -offset and -width:Ingo Schwarze2014-10-305-110/+62
| | | | | | | | | 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@.
* add -K to usage() and wrap nicely; from jmc@Ingo Schwarze2014-10-301-3/+3
|
* fix a macro error in previous; from jmc@Ingo Schwarze2014-10-301-3/+3
|
* Some fine tuning of console rendering of named special characters.Ingo Schwarze2014-10-291-20/+20
| | | | | | 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
* In terminal output, unify handling of Unicode and numbered characterIngo Schwarze2014-10-294-51/+78
| | | | | | | | | | | 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.
* In -Tascii mode, print "<?>" only for Unicode escapes of unknownIngo Schwarze2014-10-282-13/+7
| | | | | | representation, not for character escapes with unknown names. According to groff, the latter produce no output, and we now warn about them.
* Make the character table available to libroff so it can check theIngo Schwarze2014-10-2819-107/+113
| | | | | | | | 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.
* stricter parsing of Unicode escape namesIngo Schwarze2014-10-281-15/+19
|
* Tighten Unicode escape name parsing.Ingo Schwarze2014-10-282-14/+14
| | | | | Accept only 0xXXXX, 0xYXXXX, 0x10XXXX with Y != 0. This simplifies mchars_num2uc().
* Refine -Tascii rendering of Unicode characters, mostly to better agreeIngo Schwarze2014-10-282-130/+130
| | | | | | | | | 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.
* Support overstriking by backspace in PostScript and PDF output.Ingo Schwarze2014-10-271-16/+62
| | | | | | | | | 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.
* Handle output encoding for unicode, numbered and named escape sequencesIngo Schwarze2014-10-271-23/+11
| | | | | | | | 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
* Fix a regression in term.c rev. 1.229 reported by bentley@:Ingo Schwarze2014-10-274-16/+15
| | | | | | | | | | 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.
* KNF: indentation and sort variables by size; no functional changeIngo Schwarze2014-10-261-5/+4
|
* Grrr, patch(1) merged the new function to the wrong place in this file.Ingo Schwarze2014-10-261-78/+78
| | | | Resync with OpenBSD. No code change.
* In -Tascii mode, provide approximations even for some Unicode escapeIngo Schwarze2014-10-264-7/+32
| | | | | | | | 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.
* Improve -Tascii output for Unicode escape sequences: For the first 512Ingo Schwarze2014-10-265-75/+139
| | | | | | | | | | | | 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.
* With the current architecture, we can't support inline equationsIngo Schwarze2014-10-251-2/+3
| | | | | | | 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>.
* Fix a NULL pointer dereference reportedIngo Schwarze2014-10-251-2/+4
| | | | | by Theo Buehler <theo at math dot ethz dot ch> on tech at openbsd: Do not attempt to parse empty equations.
* Report arguments to .EQ as an error, and simplify the code:Ingo Schwarze2014-10-254-41/+17
| | | | | | | * drop trivial wrapper function roff_openeqn() * drop unused first arg of function eqn_alloc() * drop usused member "name" of struct eqn_node While here, sync to OpenBSD by killing some trailing blanks.
* integrate preconv(1) into mandoc(1);Ingo Schwarze2014-10-2510-569/+192
| | | | enhances functionality and reduces code and docs by more than 300 lines
* some new tasksIngo Schwarze2014-10-251-2/+13
|
* Protect the roff parser from dividing by zero. ok schwarze@Kristaps Dzonsons2014-10-203-16/+29
|
* improve documentation of .Fa, .Va, and .Vt;Ingo Schwarze2014-10-201-10/+22
| | | | inspired by a discussion with matthew@
* correct the spacing after in-line equationsIngo Schwarze2014-10-204-8/+10
| | | | | that start at the beginning of an input line but end before the end of an input line
* correctly parse spacing around in-line equationsIngo Schwarze2014-10-201-6/+37
| | | | | at the beginning and at the end of input lines; issue reported by kristaps@
* correct spacing *after* inline equations (much simpler than expected)Ingo Schwarze2014-10-202-2/+6
|
* correct spacing before inline equationsIngo Schwarze2014-10-205-16/+16
|
* show the {MDOC,MAN}_EQN node, it contains interesting information,Ingo Schwarze2014-10-201-11/+13
| | | | | in particular line and column numbers and flags; but hide the uninteresting EQN_ROOT box
* plug file descriptor leaks on read or write failure;Ingo Schwarze2014-10-182-16/+15
| | | | hinted at by Steffen Nurpmeso <sdaoden at yandex dot com>.
* oops, don't escape the first token of inline equationsIngo Schwarze2014-10-161-3/+3
|
* Implement in-line equations, much needed by Xenocara manuals.Ingo Schwarze2014-10-166-93/+107
| | | | | | | | Put the steering into the roff parser rather than into the mdoc parser such that it works for all macro languages and on both text and macro lines. Line breaks and blank characters generated before and after in-line equations are not perfect yet, but let's do one thing at a time.
* even if a table has zero columns, do not segfault in the formatter;Ingo Schwarze2014-10-142-4/+4
| | | | bug reported by bentley@
* annotate for difficulty, and some minor cleanupIngo Schwarze2014-10-141-9/+99
|
* bentley@ suggests Unicode table borders;Ingo Schwarze2014-10-141-3/+4
| | | | while here, remove the note about sox(1), it works now
* Rudimentary implementation of the e, x, and z table layout modifiersIngo Schwarze2014-10-147-19/+99
| | | | | | | to equalize, maximize, and ignore the width of columns. Does not yet take vertical rulers into account, and does not do line breaks within table cells. Considerably improves the lftp(1) manual; issue noticed by sthen@.
* implement font modifiers in table layoutsIngo Schwarze2014-10-132-27/+44
|
* Properly scale string length measurements for PostScript and PDF output;Ingo Schwarze2014-10-131-3/+7
| | | | | this doesn't change anything for ASCII and UTF-8. Problem reported by bentley@.
* Stricter syntax checking of Unicode character names:Ingo Schwarze2014-10-131-13/+12
| | | | | | | Require exactly 4, 5 or 6 hex digits and allow nothing else. This avoids mishandling stuff like \[ua] and \C'uA' as Unicode and also fixes underlining in eqn(7) -Thtml output which uses \[ul]. Problem found and semantics suggested by kristaps@.
* sync with OpenBSD:Ingo Schwarze2014-10-131-2/+3
| | | | | check sorting of .Xr's case-insensitively; no idea why this was different here
* Do not warn about declarations of functions returning function pointers,Ingo Schwarze2014-10-131-4/+6
| | | | getting rid of a false positive noticed by bentley@.
* Clarify: SEE ALSO sections are sorted case insensitively.Ingo Schwarze2014-10-131-3/+3
| | | | Patch from bentley@, ok jmc@.
* add missing entry for .ll to the dispatch table;Ingo Schwarze2014-10-121-1/+2
| | | | patch from Martin <Natano at natano dot net>, thanks
* bugfix: do not parse quoted strings for tokens; fixes glFrustum(3)Ingo Schwarze2014-10-121-1/+11
|
* Improve error handling in the eqn(7) parser.Ingo Schwarze2014-10-125-122/+125
| | | | | | | | | | | | | | | | | | | Get rid of the first fatal error, MANDOCERR_EQNSYNT. In eqn(7), there is no need to be bug-compatible with groff, so there is no need to abondon the whole equation in case of a syntax error. In particular: * Skip "back", "delim", "down", "fwd", "gfont", "gsize", "left", "right", "size", and "up" without arguments. * Skip "gsize" and "size" with a non-numeric argument. * Skip closing delimiters that are not open. * Skip "above" outside piles. * For diacritic marks and binary operators without a left operand, default to an empty box. * Let piles and matrices take one argument rather than insisting on a braced list. Let HTML output handle that, too. * When rewinding, if the root box is guaranteed to match the termination condition, no error handling is needed.
* major upgrade to eqn(7) terminal output;Ingo Schwarze2014-10-121-18/+65
| | | | | column vectors ("piles") and matrices are not yet pretty, but everything else is now more or less readable
generated by cgit v1.2.3-56-ge451 (git 2.39.0) at 2024-07-01 14:44:12 +0000