This is the mail archive of the
mailing list for the DocBook project.
Re: Line breaks
- To: docbook at lists dot oasis-open dot org
- Subject: Re: DOCBOOK: Line breaks
- From: Norman Walsh <ndw at nwalsh dot com>
- Date: Thu, 11 Nov 1999 15:50:36 -0500
- References: <firstname.lastname@example.org>
- Reply-To: docbook at lists dot oasis-open dot org
/ Bob Stayton <email@example.com> was heard to say:
| > From: Norman Walsh <firstname.lastname@example.org>
| > | <aside>Er..uhmm..I am asking these questions in the assumption
| > | that a request for including something like "newline"
| > | in DocBook would be a vain one - though "newline" is,
| > | is it not, structural information?<duck/></aside>
| > No, it's purely presentational. What semantic meaning does it
| > have? And how do you propose to implement your markup on a PDA
| > or speaking cell phone? At least with a variablelist, you can
| > identify the terms and imagine doing something else for limited
| > display environments.
| I'm certain you are not saying that all line breaks
| are purely presentational. After all, Docbook supplies
| <literallayout> and <programlisting> to preserve line
| breaks where they have semantic meaning, such as
| poetry and program code.
You're right, but arbitrary, random linebreaks are rarely more
And I'm not saying authors don't want to do it, but DocBook does
try to remain as structural as possible. For environments where
linebreaks are usually relevant (addresses, etc.) DocBook
provides things like literallayout.
To date, no one has presented a situation (except in
CommandSynopsis where we have <sbr>) that seemed to justify
adding an arbitrary linebreak element to DocBook.
Norman Walsh <email@example.com> | Things work out best for those who
http://www.oasis-open.org/docbook/ | make the best of the way things
Member, DocBook Editorial Board | work out.