From 3fd24182bee64ea2252aa494e5930c9c9924d1d2 Mon Sep 17 00:00:00 2001 From: mguetlein Date: Thu, 9 Dec 2010 16:39:22 +0100 Subject: add significance tests to reports, some more report modifications --- docbook-xsl-1.76.1/params/nominal.image.width.xml | 43 +++++++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 docbook-xsl-1.76.1/params/nominal.image.width.xml (limited to 'docbook-xsl-1.76.1/params/nominal.image.width.xml') diff --git a/docbook-xsl-1.76.1/params/nominal.image.width.xml b/docbook-xsl-1.76.1/params/nominal.image.width.xml new file mode 100644 index 0000000..bfa989a --- /dev/null +++ b/docbook-xsl-1.76.1/params/nominal.image.width.xml @@ -0,0 +1,43 @@ + + +nominal.image.width +length + + +nominal.image.width +The nominal image width + + + + + + + + +Description + +Graphic widths expressed as a percentage are problematic. In the +following discussion, we speak of width and contentwidth, but +the same issues apply to depth and contentdepth. + +A width of 50% means "half of the available space for the image." +That's fine. But note that in HTML, this is a dynamic property and +the image size will vary if the browser window is resized. + +A contentwidth of 50% means "half of the actual image width". +But what does that mean if the stylesheets cannot assess the image's +actual size? Treating this as a width of 50% is one possibility, but +it produces behavior (dynamic scaling) that seems entirely out of +character with the meaning. + +Instead, the stylesheets define a +nominal.image.width and convert percentages to +actual values based on that nominal size. + + + -- cgit v1.2.3