Re: [docbook-apps] Some issues regarding the manpages stylesheet

[Costin Stroie <cstroie@bitdefender.com>]

On Thu, 4 Aug 2005, Michael Smith wrote:

>> 3. When <screen>...</screen> is used, before '.nf' and after '.fi' there
>> are empty lines. These lines ARE NOT IGNORED by groff.
>
> No need to shout :) I am aware of that one already. I decided to
> deal with it by making a change that "normalizes" line space
> around output of Screen and other such DocBook elements ("verbatim
> environments" in DocBook ling).  You can try it out by testing
> with the latest snapshot:
>
>  http://docbook.sourceforge.net/snapshot/
>
> If you try that and find that it is not giving you the output
> you'd expect, please post another message here describing what you
> think the output should look like.

Sorry for shouting. I will keep the silence from now on.

Regarding the '<screen>' and the current snapshot, it got worse. There is 
one space before the '.sp' request (before the '.nf') that makes '.sp' not 
to be at the beginning of the line. This is the output:

.SH "EXAMPLES"
.PP
  .sp
.nf
screen_contents_here
.fi

In fact, my concern is about not accepting empty lines. One '.sp' before 
and one after the block are welcome. I use to remove the empty lines with 
'sed' and this is why I think those spaces should be created with something 
else (such as '.sp') not just empty lines.

<one hour later>
I have found this behavior appears if the 'screen' element is inside a 
'para' element. If the 'para' begins after the 'screen' the '.sp' request 
is in proper position.

Somehow, in the template 'mixed-block', the loop is called one time before 
the 'screen' element (which is the first child of the 'para') and outputs 
one ' ' character on the blank line reserved for '.sp'.


Something else. I really need to place the output files in corresponding 
directories and I think I will try to make the patch. No promise, though.

I have adapted the html templates to output the COPYRIGHT (no shouting) 
section, based on the 'copyright' element. This and the AUTHORS section 
should be enabled and disabled with some parameters, since they are 
automatically generated.

The question is how could I (or we) submit those patches?

-- 
Costin STROIE
Linux Technical Writer
Data Security Division
SOFTWIN
-------------------------------
e-mail: cstroie@bitdefender.com
tel: (+402) 1 233 07 80
fax: (+402) 1 233 07 63
gsm: (+40) 722 46 23 79
Bucharest, ROMANIA
-------------------------------
www.softwin.ro
www.bitdefender.com


-- 
This message was scanned for spam and viruses by BitDefender.
For more information please visit http://www.bitdefender.com/