![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Up to [cvsweb.bsd.lv] / mandoc / regress / man / RS
Up to [cvsweb.bsd.lv] / mandoc / regress / man / RS
Request diff between arbitrary revisions
Default branch: MAIN
Current tag: MAIN
Revision 1.3 / (download) - annotate - [select for diffs], Fri Oct 16 17:22:47 2020 UTC (3 years, 7 months ago) by schwarze
Branch: MAIN
CVS Tags: VERSION_1_14_6,
HEAD
Changes since 1.2: +6 -12 lines
Diff to previous 1.2 (colored)
In HTML output, avoid printing a newline right after <pre> 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@.
Revision 1.2 / (download) - annotate - [select for diffs], Tue Sep 3 18:19:42 2019 UTC (4 years, 9 months ago) by schwarze
Branch: MAIN
Changes since 1.1: +4 -6 lines
Diff to previous 1.1 (colored)
adapt to new <p> output logic (html.c rev. 1.260)
Revision 1.1 / (download) - annotate - [select for diffs], Sat Jan 5 20:04:50 2019 UTC (5 years, 4 months ago) by schwarze
Branch: MAIN
CVS Tags: VERSION_1_14_5
Slowly start doing more HTML output tests, in this case for the interaction of .nf and .RS, related to man_macro.c rev. 1.106. HTML regression testing is tricky because it is extremely prone to over-testing, i.e. unintentional testing for volatile formatting details which are irrelevant for deciding whether the HTML output is good or bad. Minor changes to the formatter - which is still heavily under development - might result in the necessity to repeatedly adjust many test cases. Then again, HTML syntax rules are so complicated that without regression testing, the risk is simply too high that later changes will re-introduce issues that were already fixed earlier. Let's just try to design the tests very carefully in such a way that the *.out_html files contain nothing that is likely to change, and defer testing in cases where the HTML output is not yet clean enough to allow designing tests in such a way.