|
Subject: Re: DocBook print backend: lists and IDs From: marcusd@xxxxxxxxxxxxxxxxxxxxx (Marcus G. Daniels) Date: 26 May 1998 10:51:45 -0700 |
>>>>> "NW" == Norman Walsh <ndw@xxxxxxxxxx> writes:
NW> I can't think of any way to solve this problem without creating a
NW> special case for each possible element that might occur first in a
NW> list item (which is almost all block elements).
I essentially did that: the node is always processed, but the node
content is ignored in listitem context.
(define (skip-content)
(make sequence
(process-node-list (children (current-node)))))
(element (listitem programlisting) (skip-content))
(element (listitem screen) (skip-content))
(element (listitem synopsis) (skip-content))
(element (listitem funcsynopsis) (skip-content))
(element (listitem literallayout) (skip-content))
(element (listitem address) (skip-content))
(element (listitem para) (skip-content))
(element (listitem formalpara) (skip-content))
NW> Unfortunately FUNCSYNOPSIS isn't a verbatim environment. And,
NW> while I haven't tried your modification, by inspection I don't
NW> think that it would work.
That wasn't the fix, just another change. It looked like it was
an oversight to not handle that case.
NW> As near as I can tell, a FUNCSYNOPSIS
NW> (for example) _inside_ the first paragraph of a list item would
NW> get skipped. But I could be wrong.
Wouldn't the FUNCSYNOPSIS be a child of the paragraph?
DSSSList info and archive: http://www.mulberrytech.com/dsssl/dssslist
| Current Thread |
|---|
|
| <- Previous | Index | Next -> |
|---|---|---|
| Re: DocBook print backend: lists an, Norman Walsh | Thread | Graphic Size Problem - Resolution, Chuck Darney |
| Re: DocBook print backend: lists an, Norman Walsh | Date | Graphic Size Problem - Resolution, Chuck Darney |
| Month |