Paul,
I didn't realize the xpointer construct was unofficial.
That said, it's working very nicely in xmllint, so unless/until xmllint
or an equivalent is using an official means of doing this, I'll keep
trucking along.
Kate. Sorry my suggestion doesn't work for you.
Thanks,
Dick
---------------------------------
XML Press
XML for Technical Communicators
http://xmlpress.net
(970) 231-3624
>
Original Message-----
> From: Grosso, Paul [mailto:pgrosso@ptc.com]
> Sent: Monday, July 26, 2010 2:03 PM
> To: Richard Hamilton; Kate.Wringe@sybase.com
> Cc: DocBook Technical Committee; docbook@lists.oasis-open.org
> Subject: [docbook-tc] RE: [docbook] Sections and topics
>
>
> There is no currently registered [1] "xpointer" xpointer
> scheme. Did you mean to say "xpath1" or something like that
> or are you recommending use of something unofficial that may
> not be supported in general?
>
> paul
>
>
> [1] http://www.w3.org/2005/04/xpointer-schemes/
>
>
> >
Original Message-----
> > From: Richard Hamilton [mailto:rlhamilton@frii.com]
> > Sent: Monday, 2010 July 26 14:52
> > To: Kate.Wringe@sybase.com
> > Cc: DocBook Technical Committee; docbook@lists.oasis-open.org
> > Subject: Re: [docbook] Sections and topics
> >
> > Kate,
> >
> > I think there may be a solution that does not require a
> change to the
> > schema.
> >
> > I presume the toc becomes bloated because everything ends up getting
> > pushed down an extra level. If that's the case, try the following:
> >
> >
> >
> > This snippet throws away the section wrapper, promotes the
> title to be
> > the chapter title, and then pulls in everything after the
> title inside
> > the section. I've used it when I needed to turn a chapter into an
> > appendix or when I've needed to insert something (e.g., a
> graphic) and
> > didn't want to touch the source.
> >
> > You need to be cautious about the content; it's not hard to end up
> with
> > a file that won't parse, but it might be worth a try.
> >
> > Hope that helps.
> > Dick Hamilton
> > ---------------------------------
> > XML Press
> > XML for Technical Communicators
> > http://xmlpress.net
> > (970) 231-3624
> >
> > >
> > > Hello,
> > >
> > > Here's the problem that I am increasingly running into: We have a
> > > in one book that we want to reuse as a