From b406858f472ce8af858c5c985fdea9311bf86173 Mon Sep 17 00:00:00 2001 From: Michael Smith Date: Mon, 20 Mar 2006 06:48:59 +0000 Subject: [PATCH] Checkpointing. Still have a way to go on reworking this. --- xsl/common/refentry.xsl | 155 +++++++++++++++++++++++----------------- 1 file changed, 90 insertions(+), 65 deletions(-) diff --git a/xsl/common/refentry.xsl b/xsl/common/refentry.xsl index e499f98cd..3e45c8eda 100644 --- a/xsl/common/refentry.xsl +++ b/xsl/common/refentry.xsl @@ -61,24 +61,25 @@ part of a "book" of some kind. Therefore, it is sometimes necessary to embed "context" information in output for each refentry. - However, one problem is that mark up that context information in - different ways. Often (usually), it is not actually part fo the - content of the refentry itself, but instead part of its - parent element's content. And even then, DocBook provides a variety of - elements that users might potentially use to mark up the same kind of - information. One user might use the productnumber element - to mark up version information about a particular product, while - another might use the releaseinfo element. + However, one problem is that different users mark up that + context information in different ways. Often (usually), it is not + actually part of the content of the refentry itself, + but instead part of its parent element's content. And even then, + DocBook provides a variety of elements that users might + potentially use to mark up the same kind of information. One user + might use the productnumber element to mark up version + information about a particular product, while another might use + the releaseinfo element. Taking all that in mind, the - get.refentry.info function tries to gather data - from a refentry element and its parent element in an - intelligent and user-configurable way. + get.refentry.info function tries to gather + metadata from a refentry element and its parent element + in an intelligent and user-configurable way. The get.refentry.info is actually just - sort of a "driver" function; it calls other function that do that - actual data collection, the returns the data as a set. + sort of a "driver" function; it calls other function that do the + actual data collection, then returns the data as a set. The manpages stylesheets are an application of these APIs. @@ -108,7 +109,7 @@ prefs - A node containing users preferences (from global + A node containing user preferences (from global stylesheet parameters) @@ -262,8 +263,18 @@ - 3 - 1 + + Note: Missing manvolnum. + + + Note: Found funcsynopsis. Setting section number to 3. + 3 + + + 1 + + + @@ -328,6 +339,8 @@ + Note: Found date in + + Note: Found date in + + + + @@ -353,6 +372,7 @@ + Note: Missing date. Generating localized date. @@ -504,7 +524,7 @@ - + Warn: Missing "source" metadata. No fallback found; leaving empty. @@ -575,57 +595,62 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + Note: Missing class="source" data on refmeta/refmiscinfo + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Note: Missing "source name" metadata. + + - + -- 2.40.0