W3C home > Mailing lists > Public > www-html@w3.org > April 2003

Re: Getting <l> right (Was: Unicode line and paragraph separators)

From: Mikko Rantalainen <mira@cc.jyu.fi>
Date: Mon, 07 Apr 2003 01:39:30 +0300
Message-ID: <3E90ACA2.7000405@cc.jyu.fi>
To: www-html@w3.org

Toby A Inkster / 2003-04-06 15:30:
> What about:
> <h1>
>   Here&nbsp;Is&nbsp;A&nbsp;Very&nbsp;Long&nbsp;Heading 
>   And&nbsp;I&nbsp;Want&nbsp;To&nbsp;Choose&nbsp;Where&nbsp;The&nbsp;Line&nbsp;Breaks
> </h1>
> Of course, this way yo'll give yourself all sorts of problems dealing with 
> different browser window widths -- just as you would have with <br /> or <l /> 
> -- it's simply not a good idea to specify hard and fast line breaks for purely 
> presentational reasons such as this.

As I see it, l(ine) should describe where logical line starts and ends. 
For example, poems are usually formatted in certain way where lines 
sometime have meanings itself. Proper usage would be to wrap each line 
of poem inside a l(ine) element. I think the default rendering should 
allow wrapping of text but it should indent wrapped lines in the way you 
sometimes see in poems or source code listings.

> <p>
>   Here is a paragraph <l>that contans a line</l> and some other stuff.
> </p>
> Could be rendered in either of the following ways:
>   Here is a paragraph
>   that contans a line
>   and some other stuff.
>   Here 
>   is a
>   para-
>   graph
>   that contans a line
>   and 
>   some
>   other
>   stuff.

I think the default rendering should be

   is a
     a line

Also, if the source had something like
<p>Here's some sample text<l/>with a line inside.
the default visual rendering should be

   Here's some sample text

   with a line inside.

Which could(?) be expressed with a CSS rule like

l { display: block; min-height: 1em; }

This would prevent the abuse to use l element instead of missing br.

Received on Sunday, 6 April 2003 18:39:02 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:06:03 UTC