Re: [docbook-apps] ooclass

["Bob Stayton" <bobs@sagehill.net>]

Hi Mauritz,
Yes, for Java I suppose it would be a dot in a synopsis.  For the other 
language modes?

That oddity is a bug, I think.  The ooclass element has been in the 
%tech.char.class; parameter entity for some time, so it permitted inline. 
When I put one in a para, the stylesheet reports that no template matches. 
So there should be a template with no mode to handle it in such cases.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Mauritz Jeanson" <mj@johanneberg.com>
To: "'Bob Stayton'" <bobs@sagehill.net>; "'Johnson, Eric'" 
<Eric.Johnson@iona.com>; <docbook-apps@lists.oasis-open.org>
Sent: Wednesday, December 06, 2006 11:57 AM
Subject: RE: [docbook-apps] ooclass


>> -----Original Message-----
>> From: Bob Stayton
>>
>> I think this is probably a bug.  In fo/synop.xsl, there are
>> many cases where an element checks its preceding sibling and
>> adds a space or punctuation if necessary.  It sounds like
>> this combination is currently not accounted for.
>
>
> The fix (#1603790) for this is to use a space between package name and 
> class
> name. But that looks odd. Shouldn't it be a dot instead, so that a fully
> qualified class name is shown in the output?
>
> Another oddity is that even though several elements can be parents of
> <ooclass>, the stylesheets only handle the case when the parent is
> <classsynopsis>. On the other hand, I guess that there are few uses for
> <ooclass> outside of <classynopsis> anyway. Maybe the schema allows
> <ooclass> in too many places?
>
> /MJ
>
>
>
>