Re: Tags inside themselves??
Murray Maloney <murray@sco.COM>
Date: Tue, 13 Sep 94 11:00:41 EDT
Message-id: <9409131051.aa26341@dali.scocan.sco.COM>
Reply-To: murray@sco.COM
Originator: html-wg@oclc.org
Sender: html-wg@oclc.org
Precedence: bulk
From: Murray Maloney <murray@sco.COM>
To: Multiple recipients of list <html-wg@oclc.org>
Subject: Re: Tags inside themselves??
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: HTML Working Group (Private)
Hi,
This mail was sent directly to me and was not distributed to html-wg.
I am assuming that Stan would have no issue with my reposting it
and replying...
>
> >> >
> >> >The HTML DTD Reference (Level 2) states that BLOCKQUOTE tags are allowed
> >> >in BLOCKQUOTE tags (pg 6-2) but nesting of BLOCKQUOTEs and possible
> rendering is not discussed.
> >
> >Seriously though. It is perfectly normal to expect that a quote
> >would include a quote. Certainly this is no less true of block-quotes.
> >Rendering of block quotes could follow the following rules (or not):
> >
> > - initial block quote is indented by 2-5 spaces,
> > possibly right-indented by 2-5 spaces,
> > possibly delimited by double quotes,
> > and possibly rendered in a distinguishing typeface
> >
> > - first nested block quote is indented an additional 2-5 spaces,
> > possibly right-indented by 2-5 spaces,
> > possibly delimited by single open and close quotes,
> > and possibly rendered in a distinguishing typeface
> >
> > - subsequent nested block quotes indented additional 2-5 spaces,
> > possibly delimited by alternating double and single quotes,
> > and possibly rendered in a distinguishing typeface
> >
> > Murray
>
> Murray, this is fine with me, too. I was just wanting to make sure since the
> surrounding discussion did not say anything about the possible rendering of
> such.
Ya, we have been a bit reluctant to include formatting advice
on the basis that browser implementors should be free to
determine formatting characteristics on their own and
that Braille and audio readers would not follow our advice anyway.
>
> >> At the time I drafted the DTD, I got this idea that it would be neat
> >> to be able to select a range of text in one browser, and paste it into
> >> an editor, which would mark it up like:
> >>
> >> <BLOCKQUOTE>
> >> ...selected text...
> >> <address>author/url of selected text</address>
> >> <BLOCKQUOTE>
> >>
> >> Dan
>
> I'm sorry, Dan, but I don't understand your example. If I am drafting an
> original document and copy text from another document as you describe (nice
> idea, IMO) into a BLOCKQUOTE structure, it would only be nested if I dropped
> it into an existing BLOCKQUOTE structure. Is that the problem you were
> referring to? Allowing the ADDRESS within the BLOCKQUOTE is also fine from
> what I can see.
There's a very old (and very bad) short story that goes like this:
<BLOCKQUOTE>
It was a dark and stormy night. The boys and girls
were all huddled around the stove when the Captain
said "I'll tell you a story that my first Captain told me"
<BLOCKQUOTE>
It was a dark and stormy night. The boys and girls
were all huddled around the stove when the Captain
said "I'll tell you a story that my first Captain told me"
<BLOCKQUOTE>
It was a dark and stormy night. The boys and girls
were all huddled around the stove when the Captain
said "I'll tell you a story that my first Captain told me"
<BLOCKQUOTE>
It was a dark and stormy night. The boys and girls
were all huddled around the stove when the Captain
said "I'll tell you a story that my first Captain told me"
</BLOCKQUOTE>
</BLOCKQUOTE>
</BLOCKQUOTE>
You get the point.
</BLOCKQUOTE>
>
> Stan Newton
> Newton Computing Solutions
>