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

[Michael Smith <smith@xml-doc.org>]

Costin Stroie <cstroie@bitdefender.com> writes:

> 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:

OK, that is definitely a bug. I can fix the pretty easily.

But please e-mail me (off-list) one or more of your DocBook XML
source documents, if possible. I will add them to the set of
documents I test with. If I can test with the same document, it
makes it much easier to troubleshoot problems.

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

Yep. The space before the defintely .sp should not be there. And
the .sp should probably not be there either. I'm not sure why it
is being generated. That is why it would help to have your source
to test with.

I could just have the stylesheet automatically remove any .sp
instance that occurs immediately after a .PP when there is only
spaces or linebreaks between the two.

> 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.

What empty lines? I don't see any empty lines in the example
output abobe.

> <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.

Again, it is hard to know exactly what markup you are describing
without seeing your source. Are you saying that you have something
like the following?

 <para>
   <screen>Some text here...

> 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'.

hmm, that does sound like a bug. I will need to look at it.

> 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.

A patch would be great.

> 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?

Upload them here:

  https://sourceforge.net/tracker/?func=add&group_id=21935&atid=516914

Choose "Patch" for Category

  --Mike

-- 
Michael Smith
http://sideshowbarker.net/

smime.p7s