[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: SV: [docbook] <simplesect> question
You are right. My solution is used only for fiction (where the phenomenon appears very frequently), and is based on roundtripping XML in MS-Word. Here you can easely see if something is wrong (unintended simpara followed by simpara). Best regards Henrik Ryom Senior Information Architect InfoFuture A/S www.infofuture.com ________________________________ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. > -----Oprindelig meddelelse----- > Fra: Peter Ring [mailto:PRI@magnus.dk] > Sendt: 7. marts 2006 13:15 > Til: docbook@lists.oasis-open.org > Emne: RE: [docbook] <simplesect> question > > The problem with > > section > simpara > para > simpara > para > > rather than > > section > simplesect > para > para > simplesect > para > para > > become apparent when you want to insert a new '1. para' in a > subdivision, even if you use it purely to get some whitespace > in the copy. > > At least in my case, a specific update of the text will > typically change a set of consecutive para's, i.e., a natural > subdivision, rather than individual para's. Indexterm's are > also typically related to a set of para's. > > > kind regards > Peter Ring > > > -----Original Message----- > > From: Henrik Ryom [mailto:hr@infofuture.com] > > Sent: 7. marts 2006 12:25 > > To: docbook@lists.oasis-open.org > > Subject: SV: [docbook] <simplesect> question > > > > > > > > > The graphical separation is an expression of a sematic > grouping of > > > content, i.e., it is appropriate to annotate each simplesect with > > > info meta-information. > > > > This is not necessarily true. The graphical separation may be an > > expression of just a break in the text (a pause). > > I have used simpara, together with a change in stylesheets (space > > before and no indentation) for this, as: > > > > simpara: Mmmm mmmm mmmmmmm mmmm mmmm mmmm mmmmm > > mm mmmmmm mmmmm mmm mmmm mmmmmm mmm mm > > mmm mmm mmmmmmm mmm. Mmmm mmmm mmmm mm > > mm mmmmmmm mmmm mmmmm mmmmm. > > para: Mmmm mmmmmm mmm mmm mmmm mmmmm mmmmm > > mmmmm mmm mmmm mmm mmm m. Mmmm mmmm mm > > mm mmmmmmmmmm mm mmmmmmm mmm mm. > > > > simpara: Mmmm mmmmmm mmm mmm mmmm mmmm mm mmmm > > mmmmm mmm mmmm mmm mmm m. Mmmm mmmm mm > > mm mmmmmmmmmm mm mmmmmmm mmm mm. > > para: Mmmm mmmm mmmmmmm mmmm mmmm mmmm mmm > > mmm mmm mmmmmmm mmm. Mmmm mmmm mmmm mm > > mm mmmmmmm mmmm mmmmm mmmmm. > > > > I admit this is not the best solution, because the allowed > content of > > para and simpara are not identical. Perhaps you could > supply para with > > an attribute expressing 'break/space-before'. > > > > Henrik Ryom > > Senior Information Architect > > InfoFuture A/S > > www.infofuture.com > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: docbook-unsubscribe@lists.oasis-open.org > > For additional commands, e-mail: docbook-help@lists.oasis-open.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: docbook-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: docbook-help@lists.oasis-open.org > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]