lynx-dev
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV blockquote behavior

From: Foteos Macrides
Subject: Re: LYNX-DEV blockquote behavior
Date: Sat, 18 Jan 1997 22:50:25 -0500 (EST) 
Subir Grewal <address@hidden> wrote:
>On Fri, 17 Jan 1997, Carl Hansen wrote:
>
>:Nested BLOCKQUOTE seems a perfectly reasonable structure in English
>:and should be supported by lynx IMO.
>:
>:Here's an example comparing two browsers:
>:http://www.berkeleynetcentral.com/DrPseudocryptonym/destroytosave.html
>
>DrPseudocyptonym needs a rap on his knuckles (just kidding), because the
>example you gave should have been of the form:
>
><html>
><blockquote>Some blockquoted text</blockquote>
><cite>Above lines from the keyboard of Subir Grewal</cite>
></html>
>
>which would have delineated the character of the last line as a citation,
>clearly for the previous blockquote, and which Lynx renders as:
>
>
>     Some blockquoted text
>     
>   Above lines from the keyboard of Subir Grewal
>
>Where "Above...Grewal" is underlined.  You might have been more successful
>if you'd have found a piece of quoted text that itself contains a
>quotation.  Even then, working with the examples provided by type-setting,
>I'd say it would probably be better to set off the quotation within a
>quotation by using <Q> or just double quotes.  Very few books will cotain
>more than one indentation for quotations, I personally do not recall
>reading a book which used such a layout (and hell they've been at it for a
>few hundred years).
>
>I really don't think Lynx needs to handle nested blockquotes as you
>suggest it should.  Whether the author expects nested blockquotes to be
>acceptable structural markup is an interesting question, the DTD permits
>it.  It might be wise to have Lynx think of all nested blockquotes as <Q>s
>but if people are using BLOCKQUOTE where they should be using CITE or
>simply to get more indentation, that would be counter-productive. 

        The intent in HTML/3.0 was to use CREDIT blocks within BQ
(a.k.a., BLOCKQUOTE) blocks, and Q tags for nested quotes within
the overall block, all of which is supported in Lynx.

        There was a design flaw in Lynx's style handling for
ADDRESS, BLOCKQUOTE/BQ, and a number of other block-level elements,
in that if they were nested without other block-level elements
interposed, you didn't get the newline separations between them.
That's improved now.

                                Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;
reply via email to
[Prev in Thread] Current Thread [Next in Thread]