summaryrefslogtreecommitdiffstats
path: root/regress/usr.bin/mandoc/mdoc/Rs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* In HTML output, avoid printing a newline right after <pre>schwarze2020-10-161-1/+0
| | | | | | | | and right before </pre> because that resulted in vertical whitespace not requested by the manual page author. Formatting bug reported by Aman Verma <amanraoverma plus vim at gmail dot com> on discuss@.
* Introduce the concept of nodes that are semantically transparent:schwarze2020-02-274-2/+81
| | | | | | | | | | | | | | they are skipped when looking for previous or following high-level macros. Examples include roff(7) .ft, .ll, and .ta, mdoc(7) .Sm and .Tg, and man(7) .DT and .PD. Use this concept for a variety of improved decisions in various validators and formatters. While here, * remove a few const qualifiers on struct arguments that caused trouble; * get rid of some more Yoda notation in the vicinity; * and apply some other stylistic improvements in the vicinity. I found this class of issues while considering .Tg patches from kn@.
* adapt to new <p> output logic (html.c rev. 1.131)schwarze2019-09-031-6/+4
|
* Wrap .Sh/.SH sections and .Ss/.SS subsections in HTML <section> elementsschwarze2019-03-011-0/+2
| | | | | | as recommended for accessibility by the HTML 5 standard. Triggered by a similar, but slightly different suggestion from Laura Morales <lauretas at mail dot com>.
* Remove the HTML title= attributes which harmed accessibility andschwarze2019-01-111-9/+8
| | | | | | | violated the principle of separation of content and presentation. Instead, implement the tooltips purely in CSS. Thanks to John Gardner <gardnerjohng at gmail dot com> for suggesting most of the styling in the new ::before rules.
* Represent mdoc(7) .Pp (and .sp, and some SYNOPSIS and .Rs features)schwarze2019-01-075-2/+112
| | | | | | | | | | | | | | | | | | | by the <p> HTML element and use the html_fillmode() mechanism for .Bd -unfilled, just like it was done for man(7) earlier, finally getting rid both of the horrible <div class="Pp"></div> hack and of the worst HTML syntax violations caused by nested displays. Care is needed because in some situations, paragraphs have to remain open across several subsequent macros, whereas in other situations, they must get closed together with a block containing them. Some implementation details include: * Always close paragraphs before emitting HTML flow content. * Let html_close_paragraph() also close <pre> for extra safety. * Drop the old, now unused function print_paragraph(). * Minor adjustments in the top-level man(7) node formatter for symmetry. * Bugfix: .Ss heads suspend no-fill mode, even though .Ss doesn't end it. * Bugfix: give up on .Op semantic markup for now, see the comment.
* Messages of the -Wbase level now print STYLE:. Since thisschwarze2017-07-0422-43/+39
| | | | | | | | causes horrible churn anyway, profit of the opportunity to stop excessive testing, such that this is hopefully the last instance of such churn. Consistently use OpenBSD RCS tags, blank .Os, blank fourth .TH argument, and Mdocdate like everywhere else. Use -Ios=OpenBSD for platform-independent predictable output.
* cope with changes in BASE messagesschwarze2017-06-253-6/+9
|
* churn related to the new style message about RCS idsschwarze2017-06-173-0/+3
|
* churn caused by the new Mdocdate messages, no easy way to avoid this :(schwarze2017-06-113-0/+3
|
* In markdown, autolinks are dangerous. Different compilers disagreeschwarze2017-03-111-2/+2
| | | | | | | | | | | with respect to what constitutes a valid autolink, and if a compiler deems an autolink invalid, the input turns into an unintended and potentially harmful raw HTML tag. So, never write autolinks. Instead of <link>, write [link](link). Instead of <addr>, write [addr](mailto:addr). Issue pointed out by bentley@, who also agrees with the general direction of the change.
* Now that markdown output is tested for almost everything, test allschwarze2017-03-081-2/+1
| | | | | | input files in -T markdown output mode by default and only mark those files with SKIP_MARKDOWN that are not to be tested. Much easier to read, and almost minus 40 lines of Makefile code.
* URIs need different escaping; reported by reyk@schwarze2017-03-061-2/+2
|
* first batch of -T markdown testsschwarze2017-03-056-1/+133
|
* Use typographic quotes rather than '"' for .Rs %T (no change for -Tasciischwarze2017-02-175-1/+65
| | | | | | | | | | output, of course). Patch from bentley@ in November 2014. This can be committed now because groff merged Anthony's patch yesterday. Simply committing myself because asking Anthony to go search for his two-year-old patch and have him discover that it had accumulated an average of (felt) two or three conflicts per line by now would have been mean, even if hilarious.
* discard .Rs head arguments and improve .Rs diagnosticsschwarze2015-02-047-3/+73
|
* inevitable churn caused by the section title changeschwarze2014-08-263-3/+3
|
* no need to delete any content from .Rs blocks,schwarze2014-07-074-14/+28
| | | | and downgrade the related message from ERROR to WARNING
* Using macros in .Sh header lines, or having .Sm off or .Bk -words openschwarze2014-04-152-2/+14
| | | | | | | | | while processing .Sh, is not at all recommended, but it's not strictly a syntax violation either, and in any case, mandoc must not die in an assertion. I broke this in rev. 1.124. Crash found while trying to read the (rather broken) original 4.3BSD-Reno od(1) manual page.
* Test .%C; supported by mandoc, will soon be supported by the groff port, too.schwarze2013-08-082-10/+8
|
* Polish -Tman .Rs support.schwarze2012-07-111-3/+1
| | | | All mdoc(7) macros are now supported by -Tman.
* fix position and formatting of %Uschwarze2012-07-113-2/+66
|
* Complete overhaul of the mandoc(1) test suite.schwarze2011-11-175-4/+7
| | | | | | | | | | | | | | | * Test the recently introduced -Tman output mode, too. * Specify date and OS arguments in all tests. * Remove the kludge of sed(1)ing away the page footer lines. * New make(1) variables SKIP_TMAN, SKIP_GROFF. * Drop obsolete, clumsy make(1) variable GROFF_TARGETS. * Delete obsolete mdoc/Bl/E*.sh error reporting tests. * Silence char/N/basic. * New targets: - ascii, ascii-clean - to run -Tascii tests only - tman, tman-clean - to run the new -Tman tests only - obj-clean - maintainer only, needed before groff-clean and groff - groff-clean - maintainer only, affects checked-in files
* more tests found in my other treeschwarze2011-02-063-3/+24
|
* Now that we don't have groff in base any longer, check in the desired output,schwarze2010-12-041-0/+13
| | | | such that the regression suite does not depend on ports.
* major update of the mandoc test suite:schwarze2010-07-011-1/+1
| | | | | * add various new and extend a few existing tests * stop using Mdocdate to ease syncing with NetBSD
* Add the first batch of mandoc(1) regression tests, testing for a few bugsschwarze2009-10-282-0/+26
fixed in 1.9.9 and some older, rather subtle issues in list displays. Directory layout and naming scheme was chosen such that later inclusion of tests for -man and -Thtml will not force us to rename everything, even though the layout might still seem a bit sparse right now. More tests will slowly be added while investigating and fixing issues.