discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: Re: Sx quoting and Header
Date: Mon, 27 Dec 2010 01:36:30 +0100	[thread overview]
Message-ID: <20101227003630.GO23914@iris.usta.de> (raw)
In-Reply-To: <4D17D7F9.2070904@bsd.lv>

Hi Kristaps,

Kristaps Dzonsons wrote on Mon, Dec 27, 2010 at 02:04:09AM +0200:

> To assuage the trauma of dealing with -T[x]html, I've a patch on hand

OK, so i'm not committing.

> that stashes the mdoc_validate.c concatenated `Sh' string (see
> post_sh()) into a mdoc_sh structure.  This buffer is then pumped
> right into html_idcat(), removing all those stupid loops over
> children.
> 
> The neat part about this is that, if I add a sorted list among
> these, I can do the same in `Sx' and add a check that makes sure
> `Sx' links actually go somewhere AND that sections/subsections/etc.
> aren't duplicates.  It's only little bits of code, but since this
> isn't checked by nroff, I'll post it here for a relevancy check
> before it goes in.

I think that plan does make sense.
Of course, all this should only cause warnings, not errors.

Not sure whether a duplicate section or subsection, or a subsection
with the same name as a section, warrants a warning, though.
I guess a warning is only needed when a reference is ambiguous.
Thus, the list nodes should probably contain a flag with the values
OK, DUPE, WARNED, and when a DUPE gets referenced, a warning should
be issued and the flag advanced to WARNED.

> Note, if I haven't ever explained myself, that the hex encoding is
> just to get around the fact that IDs are case-insensitive, while
> -mdoc is case-sensitive (NAME != name)...

Hm.  In mdoc(7), it could actually happen that we might get
both a `ds' and a `Ds' section.  So yes, properly dealing with
case appears to be relevant.

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2010-12-27  0:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-25 15:22 Thomas Klausner
2010-12-26 23:30 ` Ingo Schwarze
2010-12-27  0:04   ` Kristaps Dzonsons
2010-12-27  0:36     ` Ingo Schwarze [this message]
2010-12-27  8:39       ` Kristaps Dzonsons
     [not found]   ` <20101227132623.GA285025@medusa.sis.pasteur.fr>
2010-12-27 21:57     ` Ingo Schwarze
2010-12-27  0:08 ` Ingo Schwarze

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=20101227003630.GO23914@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mdocml.bsd.lv \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).