summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/shade/README
diff options
context:
space:
mode:
authorManuel Pégourié-Gonnard <mpg@elzevir.fr>2009-07-15 01:13:04 +0000
committerManuel Pégourié-Gonnard <mpg@elzevir.fr>2009-07-15 01:13:04 +0000
commite2abceca35f10da35aa6711162768d389e554987 (patch)
tree21b403172c10290850cba1c1fbb9ffe5b1707f37 /Master/texmf-dist/doc/generic/shade/README
parent181c66eec8ef64814280c5d11c6e4f92edc6c12d (diff)
Undo rev 14242, 14243, 14256, 14257: apparently our Perl for windows doesn't
support the open pragma. (OOPS: commited more than I wanted to. Also added files from the generic package 'shade'. This package was 'added' in r14213.) git-svn-id: svn://tug.org/texlive/trunk@14264 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/generic/shade/README')
-rw-r--r--Master/texmf-dist/doc/generic/shade/README20
1 files changed, 20 insertions, 0 deletions
diff --git a/Master/texmf-dist/doc/generic/shade/README b/Master/texmf-dist/doc/generic/shade/README
new file mode 100644
index 00000000000..a8ca869f8cf
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/shade/README
@@ -0,0 +1,20 @@
+A `frequently asked question' is that for possibilites to produce
+shaded boxes.
+
+Since the answers usually (just as recently) point either to PostScript
+\special's and PiCTeX it seems that a `simpler' and easier to use version
+is not readily available --- though I did not check this.
+
+A small and simple approach to shaded boxes is the use of a special font
+providing shaded rectangles, and some macros which automatically compose the
+desired box from these characters.
+
+Since, of course, the finest shading can be achieved by using single pixels
+for the pattern, the best shading pattern is *device dependent*.
+Furthermore, one generally defined shading pattern would imply the danger,
+that - because of rounding errors - at the boundaries (between two of the
+characters) `lines' would occur, and that the pattern would not look completely
+uniform. Consequently, since different fonts are to be used for different
+printers, the dvi file is *device dependent* in this sense, too, though the
+code - both for the macros and for the metafont description - is device
+independent.