Re: DOCBOOK-APPS: Re: Onechunk problem

[Dennis Grace <dgrace at us dot ibm dot com>]

Thanks again, Norm.

Yeah, I figured I was missing something. I downloaded the latest version of
chunk common and tried it, but I got an error because the new chunk.xsl
contains an include:

      <xsl:include href="manifest.xsl"/>

for a file I didn't have. It didn't have any affect on my output, but I
don't like error messages, so I retrieved manifest.xsl and installed it.
Now I'm getting an error that reads:

      runtime error chunk.xsl line 386 element if
      unregistered variable generate.manifest

So which file contains the variable?

Also, while I was downloading the new files, I thought I should go ahead
and get all the latest versions of the other associated files, so I
downloaded the latest versions of chunker.xsl and chunk-common.xsl. This
turned out to be a mistake. Every version of chunk-common.xsl after version
1.19 contains calls to a bunch of templates I don't have (href.target.uri
and trim.common.uri.paths). Where are those templates located?

Maybe I should just download 1.50.EXP, eh?

Thanks.

Dennis Grace

Information Developer
IBM Linux Technology Center
(512) 838-3937  T/L 678-3937  cell: (512)-296-7830
dgrace@us.ibm.com

Oh god comma I abhor self-consciousness.




|---------+---------------------------->
|         |           Norman Walsh     |
|         |           <ndw@nwalsh.com> |
|         |           Sent by: Norman  |
|         |           Walsh            |
|         |           <ndw@mercury>    |
|         |                            |
|         |                            |
|         |           05/16/02 05:59 AM|
|         |                            |
|---------+---------------------------->
  >--------------------------------------------------------------------------------------------------------------|
  |                                                                                                              |
  |       To:       Dennis Grace/Austin/IBM@IBMUS                                                                |
  |       cc:       docbook-apps@lists.oasis-open.org, Norman Walsh <ndw%mercury@pok.ibm.com>, Michael Smith     |
  |        <smith@xml-doc.org>, veillard@redhat.com                                                              |
  |       Subject:  DOCBOOK-APPS: Re: Onechunk problem                                                           |
  |                                                                                                              |
  |                                                                                                              |
  >--------------------------------------------------------------------------------------------------------------|



/ "Dennis Grace" <dgrace@us.ibm.com> was heard to say:
| Okay, so now, what exactly does this new version of onechunk do? It looks
| like it just passes everything off to chunk.xsl. What is the onechunk
param
| supposed to do?

Sorry, you need to get the new chunk.xsl as well. The onechunk
parameter is really all that matters now. The chunk.xsl stylesheet
makes sure that if onechunk is set, only the root chunk gets written
to a separate file.

My attempt to use apply-imports from onechunk.xsl wasn't working
because ultimately it was calling the code in chunk.xsl even when what
I really wanted to do was call the code *imported* by chunk.xsl.
Hence, I moved the parameter logic up a level.

| Another thing that confuses me: I wasn't having this problem with 1.49. I
| had, admittedly, made a slight modification to the 1.49 onechunk.xsl file
| sheet. I had changed the include from chunk-common.xsl to chunk.xsl.  I
| notice that in the transition from 1.49 to 1.50.0, you changed the
includes
| and imports from
|
|       <xsl:import href="autoidx.xsl"/>
|       <xsl:include href="chunk.xsl"/>
|       <xsl:include href="chunker.xsl"/>
|
| to
|
|       <xsl:import href="chunk.xsl"/>

Hmm. Yes, the old way avoids the nasty double-apply-imports problem.

| So, being a stubborn old ex-Navy tech, I fell back on old troubleshooting
| methods. I swapped back to the earlier version (1.5) of onechunk.xsl and
| replaced the import with the includes and imports as they were in version
| 1.1 (with the exception, as shown above, of including chunk.xsl vice
| chunk-common.xsl). That worked.
|
| Any idea why that worked? Why were the include and import statements
| changed?

Because chunker got percolated up the stack, it's now included by
docbook.xsl. And chunk.xsl now imports docbook.xsl. Overall, this
simplifies things for many other customization layers, I just blew it
and failed to regression test onechunk.xsl, I guess. Mea culpa.

                                        Be seeing you,
                                          norm

--
Norman Walsh <ndw@nwalsh.com>      | When you can measure what you are
http://www.oasis-open.org/docbook/ | speaking about, and express it in
Chair, DocBook Technical Committee | numbers, you know something about
                                   | it; but when you cannot measure
                                   | it, when you cannot express it in
                                   | numbers, your knowledge is of a
                                   | meager and unsatisfactory kind: it
                                   | may be the beginning of knowledge,
                                   | but you have scarcely, in your
                                   | thoughts, advanced to the stage of
                                   | science.--William Thompson, Lord
                                   | Kelvin