Michael Smith [Sat, 29 Oct 2005 09:12:59 +0000 (09:12 +0000)]
Changed check for *info child in id.warning template from using
contains() to using ends-with() -- because contains() will match
informal* elements (informaltable, etc) too -- not just *info
elements.
Also added check to make sure that *info element matched actually
has a title (because some *info elements may not -- title is not a
required child of *info elements).
And FWIW, I don't think it is too aggressive to have the default
behavior be to have the stylesheets emit notification messages
about ID-less titled objects. If it were the default to have it
not emit those, most users would probably never take the time to
turn it on, including the users who it is most meant to benefit
(those who don't yet know why they ought to be putting IDs on
their titled objects).
Norman Walsh [Fri, 28 Oct 2005 12:35:15 +0000 (12:35 +0000)]
New parameter: id.warnings. If non-zero, warnings are generated for titled objects that don't have titles. True by default; I wonder if this will be too aggressive?
Norman Walsh [Thu, 27 Oct 2005 13:47:55 +0000 (13:47 +0000)]
Map info elements to the right *info element when stripping NS. Set xml:base on external references rather than directly changing @fileref. Map xml:id to id.
Norman Walsh [Thu, 27 Oct 2005 13:46:46 +0000 (13:46 +0000)]
If the keep.relative.image.uris parameter is true, don't use the absolute URI (as calculated from xml:base) in the img src attribute, us the value the author specified. Note that we still have to calculate the absolute filename for use in the image intrinsics extension.
Michael Smith [Thu, 20 Oct 2005 13:48:49 +0000 (13:48 +0000)]
First shot at implementing table support in the manpages
stylesheet. This works well as-is for normal span-less tables. It
even works for tables with colspans. But it does not yet even
attempt to do anything for rowspans. It will take more work to
add rowspan handling that. Not sure if it's worth the work, really.
Note: This table support is implemented by do a first pass to
process each table using the templates in the HTML stylesheet
(which we import). We don't override any of the <row> or <tr> or
<entry> or <td>, etc., table-markup templates, but we do override
the block and inline templates for whatever the child content of
the <entry> and <td> instances. So we end up with a node that has
"hybrid" output -- with table rows and cells marked up with HTML
<tr> and <td> tags, with with the <td> child content marked up in
roff.
So we use exsl:node-set on that node and make a second-pass
through all of it to replace the <tr> and <td> parts with tbl(1)
macros. Voila -- the end result is properly marked up tbl/roff
output for the table.
One nice thing about doing it this is that it supports both CALS
and HTML table markup, without needing any conditional logic to
deal with CALS separately. Because the first pass causes both the
CALS and HTML source markup to be "normalized" into HTML.
Michael Smith [Mon, 17 Oct 2005 04:40:46 +0000 (04:40 +0000)]
Problem:
In a PDF generated with Passivetex, every itemizedlist (bulleted
list) has a linebreak after the bullet and before the listem
contents. That bullet should not be there.
Cause:
Design problem in Passivetex
Fix:
Added a fix that works around the problem by not wrapping the
listem output in an <fo:block> if passivetex.extensions=1. Closes
#1328348.
Affects:
Only affects output if passivetex.extensions=1. Otherwise,
follows previous code path, so behavior is exactly the same.
Michael Smith [Thu, 13 Oct 2005 01:11:51 +0000 (01:11 +0000)]
These test files were apparently designed to expect external index
files that get generated by the DSSSL build. But the XSL build
does not generate them, and, when it finds them missing, the build
breaks. So, commented out the DSSSL stuff and added <index/>
instances. If you want to test these files with DSSSL output, you
will need to uncomment the entity refs at the end.
Michael Smith [Thu, 13 Oct 2005 00:13:16 +0000 (00:13 +0000)]
Added some more tests for exposing handling of linebreaks after
programlisting start tag and before programlisting end tag. Also,
wrapped this refentry in a book instead of an article.
Michael Smith [Wed, 12 Oct 2005 14:58:42 +0000 (14:58 +0000)]
This is a standalone "utility" stylesheet (it's not imported by
and of the drivers). Its purpose is to transform all instances of
DocBook-specific "insert file" markup (e.g., <textdata
fileref="foo.txt) with Xinclude instances. It is mainly intended
as an alternative to the DocBook XSLT Java insertfile() extension.
Michael Smith [Wed, 12 Oct 2005 14:50:13 +0000 (14:50 +0000)]
Revised and added stuff for testing the
textdata/imagedata/inlinegraphic markup for inserting external
text files, and rendering callout bugs in the inserted text.
Michael Smith [Tue, 11 Oct 2005 08:59:08 +0000 (08:59 +0000)]
Use just "Revision" and "Date" RCS keywords, instead of $Id (because
$Id adds the RCS filename, RCS author name, and RCS "state", none
of which it seems like we really need in Releaseinfo).
Norman Walsh [Thu, 6 Oct 2005 16:27:40 +0000 (16:27 +0000)]
Move the stripns code to a common location; update @fileref and @entityref attributes in an attempt to handle the fact that the base URI gets mangled by the stripping copy.
Michael Smith [Wed, 5 Oct 2005 07:00:57 +0000 (07:00 +0000)]
Problem::
Number generated for Synopfragref output, but no number generated
in Synopfragment output.
Cause::
manpages stylesheets import the HTML stylesheets. manpages
stylesheets do not include a Synopfragref template, so they were
just picking up the HTML one. However, the manpages stylesheet
did have a Synopfragment template, which overrode the HTML one.
Problem is that the manpages Synopfragment was not complete.
Fix::
Correctly "ported" Synopfragment template from HTML stylesheets
and added manpages-specific character markup and features. As a
result of these changes, in the output now:
- correct numbers a generated for Synopfragment output
- Synopfragref contentes are italicized, as they should be
- Synopfragment output is output with a hanging indent (similar
to the hanging indent used for Cmysynopsis output)
- for cases where there are a group of Synopfragments together,
a line of vertical space is generated only before first, and
suppressed before subsequent ones.
Closes #599439. Thanks to Dennis Grace for reporting the problem
(long, long ago) and for submitting a patch (which was used as-is
but neverthelesss provided some insights).
Cause::
Some other fix made around the time of v1.68.0 introduced a
regression in behavior for cases where an Arg is preceded by an
Sbr. The Sbr produces a line break as expected, but the line break
is followed by a space and then the contents of the following Arg.
Fix::
The code for processing Args now checks to see if the first
preceding sibling of the Arg is an Sbr. If so, it does not output
the additional space; otherwise, it outputs the space.
Michael Smith [Mon, 3 Oct 2005 08:09:45 +0000 (08:09 +0000)]
Reverted previous change and added DIFFTAG check. Problem was not
in cvs2cl invocation; error occurred because no value was found
for DIFFTAG; in that case, we just want to skip generating
LatestChanges.
Michael Smith [Thu, 29 Sep 2005 15:00:45 +0000 (15:00 +0000)]
Generate localized title for Refsynopsisdiv if no appropriate
Title descendant found in source. Closes #1212398. This change
makes behavior for the Synopsis title consistent with the behavior
of HTML and manpages output.
Also, added xsl:use-attribute-sets="normal.para.spacing" to block
generated for Cmdsynopsis output. Previously, that block had no
spacing at all specified, which resulted it being crammed up to
closely to the Synopsis head.
projects / docbook-dsssl / log