X-Git-Url: https://git.stg.codes/stg.git/blobdiff_plain/793149f04ce52bf75dc4efb7b83a3f8ed30d1fff..35ec793690104efdd610964d255302a0310a2daf:/doc/xslt/params/nominal.image.width.xml diff --git a/doc/xslt/params/nominal.image.width.xml b/doc/xslt/params/nominal.image.width.xml deleted file mode 100644 index bfa989a2..00000000 --- a/doc/xslt/params/nominal.image.width.xml +++ /dev/null @@ -1,43 +0,0 @@ - - -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. - - -