From: "Anthony J. Bentley" <anthony@anjbe.name> To: discuss@mandoc.bsd.lv Subject: Re: mandoc HTML output: minor issues Date: Tue, 29 Aug 2017 02:47:12 -0600 [thread overview] Message-ID: <17497.1503996432@cathet.us> (raw) In-Reply-To: <CAM9P35sU4hTE7LTvhU91TvRLAgD+BSksPchDSkJt+61yw0E_Lg@mail.gmail.com> Hi Jackson, Jackson Pauls writes: > 1. Duplicate IDs (invalid HTML). E.g. dash.1 gets two elements with > id="HISTSIZE": Indeed a problem with mandoc(1), which should not generate duplicate IDs in HTML output. > 2. Broken in-page links. E.g. in dash.1, there is an <h2> with > id="White_Space_Splitting_(Field_Splitting)", but the link to that > heading is missing the bit in parentheses > (href="#White_Space_Splitting"): This is a problem with the manual; if it names a section it should refer to the section by that name. > 3. In babel.1, for the -: flag, the colon appears outside the .Fl element: > ... > 21 .Op Fl i Ar input-type | Fl : Qo Ar SMILES-string Qc Problem with the manual. Should be Op Fl i Ar input-type | Fl \&: Qo Ar SMILES-string Qc > 4. Running v.Nu (https://validator.github.io/validator/) on a > collection of HTML files generated by mandoc picks up duplicate IDs, > and a bunch of other issues: > * unescaped characters in href attributes (%, "), > * unescaped characters in URL fragments (\, {, }, #, ^, [, ], <, |), > * <div>s appearing inside <pre>s, and > * mismatches between column count in <colgroup> and table rows. > I can gather a bunch of examples if of interest. Please do. mandoc(1) could use some improvement when it comes to producing valid HTML. -- Anthony J. Bentley -- To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
next prev parent reply other threads:[~2017-08-29 8:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-08-25 9:52 Jackson Pauls 2017-08-29 8:47 ` Anthony J. Bentley [this message] 2017-08-29 15:56 ` Jackson Pauls
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=17497.1503996432@cathet.us \ --to=anthony@anjbe.name \ --cc=discuss@mandoc.bsd.lv \ --subject='Re: mandoc HTML output: minor issues' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).