From a683c3d7e9fac38ec713f23fb6b9d2c7143aea82 Mon Sep 17 00:00:00 2001 From: Karl Berry Date: Sat, 23 May 2009 00:23:51 +0000 Subject: move english latex doc out of texmf-doc git-svn-id: svn://tug.org/texlive/trunk@13412 c570f23f-e606-0410-a88d-b1316a301751 --- Master/texmf-dist/doc/latex/webguide/README | 23 + Master/texmf-dist/doc/latex/webguide/expeg.6 | 228 ++++++ Master/texmf-dist/doc/latex/webguide/expeg6.mps | 228 ++++++ Master/texmf-dist/doc/latex/webguide/webguide.css | 60 ++ Master/texmf-dist/doc/latex/webguide/webguide.html | 874 +++++++++++++++++++++ Master/texmf-dist/doc/latex/webguide/webguide.pdf | Bin 0 -> 170365 bytes .../texmf-dist/doc/latex/webguide/webguide.ps.gz | Bin 0 -> 133652 bytes Master/texmf-dist/doc/latex/webguide/webguide.tex | 615 +++++++++++++++ .../texmf-dist/doc/latex/webguide/webguide0x.gif | Bin 0 -> 4993 bytes 9 files changed, 2028 insertions(+) create mode 100644 Master/texmf-dist/doc/latex/webguide/README create mode 100644 Master/texmf-dist/doc/latex/webguide/expeg.6 create mode 100644 Master/texmf-dist/doc/latex/webguide/expeg6.mps create mode 100644 Master/texmf-dist/doc/latex/webguide/webguide.css create mode 100644 Master/texmf-dist/doc/latex/webguide/webguide.html create mode 100644 Master/texmf-dist/doc/latex/webguide/webguide.pdf create mode 100644 Master/texmf-dist/doc/latex/webguide/webguide.ps.gz create mode 100644 Master/texmf-dist/doc/latex/webguide/webguide.tex create mode 100644 Master/texmf-dist/doc/latex/webguide/webguide0x.gif (limited to 'Master/texmf-dist/doc/latex/webguide') diff --git a/Master/texmf-dist/doc/latex/webguide/README b/Master/texmf-dist/doc/latex/webguide/README new file mode 100644 index 00000000000..f4ac6757e65 --- /dev/null +++ b/Master/texmf-dist/doc/latex/webguide/README @@ -0,0 +1,23 @@ + webguide is a "Brief Guide to LaTeX Tools for Web Publishing". +For a much more detailed guide see: Michel Goossens and Sebastian Rahtz +(with Eitan Gurari, Ross Moore, and Robert Sutor), "The LaTeX Web +Companion --- Integrating TeX, HTML, and XML", Addison Wesley, 1999, +(ISBN 0-201-43311-7). As an example of capabilities webguide includes a +LaTeX source file together with PostScript, PDF, and HTML versions all +generated automatically from the single source. + + You should find the following files: +o README (this file) +o webguide.tex --- Source file +o expeg.6 --- MetaPost generated EPS file +o expeg6.mps --- copy of expeg.6 +o webguide.ps --- PostScript version of webguide.tex generated by latex + and dvips +o webguide.pdf --- PDF version of webguide.tex generated by pdflatex +o webguide.html --- HTML version of webguide.tex generated by TeX4ht +o webguide.css --- file generated by TeX4ht +o webguide0x.gif --- file generated by TeX4ht + +Peter Wilson +February 2000 +peter.r.wilson@boeing.com diff --git a/Master/texmf-dist/doc/latex/webguide/expeg.6 b/Master/texmf-dist/doc/latex/webguide/expeg.6 new file mode 100644 index 00000000000..52439977599 --- /dev/null +++ b/Master/texmf-dist/doc/latex/webguide/expeg.6 @@ -0,0 +1,228 @@ +%!PS +%%BoundingBox: -1 -1 274 159 +%%Creator: MetaPost +%%CreationDate: 1999.12.08:1516 +%%Pages: 1 +%*Font: cmr10 9.96265 9.96265 28:e000000d4238007e4fbc4 +%%EndProlog +%%Page: 1 1 + 0 0.5 dtransform truncate idtransform setlinewidth pop [] 0 setdash + 1 setlinejoin 10 setmiterlimit +newpath 0 106.29904 moveto +63.84018 106.29904 lineto +63.84018 120.47224 lineto +0 120.47224 lineto + closepath stroke +2.83464 109.92639 moveto +(man) cmr10 9.96265 fshow +21.37624 109.92639 moveto +(ufacturer) cmr10 9.96265 fshow +newpath 95.76027 141.73206 moveto +158.12236 141.73206 lineto +158.12236 155.90526 lineto +95.76027 155.90526 lineto + closepath stroke + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth 1 setlinecap +newpath 152.45308 141.73206 moveto +152.45308 155.90526 lineto stroke +104.63104 145.41476 moveto +(STRING) cmr10 9.96265 fshow + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 190.04245 106.29904 moveto +253.88263 106.29904 lineto +253.88263 120.47224 lineto +190.04245 120.47224 lineto + closepath stroke +200.36848 109.92639 moveto +(car) cmr10 9.96265 fshow + 0 0.3985 dtransform truncate idtransform setlinewidth pop 0 setlinecap +newpath 214.27739 110.1256 moveto +217.26628 110.1256 lineto stroke +217.26628 109.92639 moveto +(mo) cmr10 9.96265 fshow +230.82658 109.92639 moveto +(del) cmr10 9.96265 fshow + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 190.04245 70.86603 moveto +253.88263 70.86603 lineto +253.88263 85.03923 lineto +190.04245 85.03923 lineto + closepath stroke +215.30693 75.80788 moveto +(car) cmr10 9.96265 fshow +newpath 95.76027 35.43301 moveto +158.12236 35.43301 lineto +158.12236 49.60622 lineto +95.76027 49.60622 lineto + closepath stroke + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth 1 setlinecap +newpath 152.45308 35.43301 moveto +152.45308 49.60622 lineto stroke +100.6183 39.11572 moveto +(INTEGER) cmr10 9.96265 fshow + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 95.76027 0 moveto +158.12236 0 lineto +158.12236 14.1732 lineto +95.76027 14.1732 lineto + closepath stroke + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth +newpath 152.45308 0 moveto +152.45308 14.1732 lineto stroke +104.63104 3.68271 moveto +(STRING) cmr10 9.96265 fshow +newpath 31.92009 120.47224 moveto +31.92009 148.81866 lineto stroke + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 31.92009 148.81866 moveto +90.09087 148.81866 lineto stroke +newpath 95.76021 148.81866 moveto +95.76021 149.5705 95.4615 150.29144 94.92992 150.82301 curveto +94.39835 151.3546 93.6774 151.6533 92.92557 151.6533 curveto +92.17374 151.6533 91.45279 151.3546 90.92122 150.82301 curveto +90.38963 150.29144 90.09093 149.5705 90.09093 148.81866 curveto +90.09093 148.06683 90.38963 147.34589 90.92122 146.81432 curveto +91.45279 146.28273 92.17374 145.98402 92.92557 145.98402 curveto +93.6774 145.98402 94.39835 146.28273 94.92992 146.81432 curveto +95.4615 147.34589 95.76021 148.06683 95.76021 148.81866 curveto closepath + stroke +34.02008 150.91866 moveto +(*name) cmr10 9.96265 fshow + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth +newpath 221.96254 120.47224 moveto +221.96254 148.81866 lineto stroke + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 221.96254 148.81866 moveto +163.79176 148.81866 lineto stroke +newpath 163.7917 148.81866 moveto +163.7917 149.5705 163.493 150.29144 162.96141 150.82301 curveto +162.42984 151.3546 161.7089 151.6533 160.95706 151.6533 curveto +160.20523 151.6533 159.48428 151.3546 158.95271 150.82301 curveto +158.42113 150.29144 158.12242 149.5705 158.12242 148.81866 curveto +158.12242 148.06683 158.42113 147.34589 158.95271 146.81432 curveto +159.48428 146.28273 160.20523 145.98402 160.95706 145.98402 curveto +161.7089 145.98402 162.42984 146.28273 162.96141 146.81432 curveto +163.493 147.34589 163.7917 148.06683 163.7917 148.81866 curveto closepath + stroke +191.63495 150.91866 moveto +(*name) cmr10 9.96265 fshow +newpath 190.04245 113.38565 moveto +69.50941 113.38565 lineto stroke +newpath 69.50945 113.38565 moveto +69.50945 114.13748 69.21074 114.85843 68.67915 115.39 curveto +68.14758 115.92159 67.42664 116.22029 66.6748 116.22029 curveto +65.92297 116.22029 65.20203 115.92159 64.67046 115.39 curveto +64.13887 114.85843 63.84016 114.13748 63.84016 113.38565 curveto +63.84016 112.63382 64.13887 111.91287 64.67046 111.3813 curveto +65.20203 110.84972 65.92297 110.55101 66.6748 110.55101 curveto +67.42664 110.55101 68.14758 110.84972 68.67915 111.3813 curveto +69.21074 111.91287 69.50945 112.63382 69.50945 113.38565 curveto closepath + stroke +150.59355 117.42284 moveto +(made) cmr10 9.96265 fshow + 0 0.3985 dtransform truncate idtransform setlinewidth pop 0 setlinecap +newpath 174.43755 117.62204 moveto +177.42635 117.62204 lineto stroke +177.42635 117.42284 moveto +(b) cmr10 9.96265 fshow +182.68436 117.42284 moveto +(y) cmr10 9.96265 fshow + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth 1 setlinecap +newpath 221.96254 85.03923 moveto +221.96254 100.62985 lineto stroke + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 224.79718 103.46445 moveto +224.79718 104.21628 224.49847 104.93723 223.96689 105.4688 curveto +223.43532 106.00038 222.71437 106.29909 221.96254 106.29909 curveto +221.21071 106.29909 220.48976 106.00038 219.95819 105.4688 curveto +219.4266 104.93723 219.1279 104.21628 219.1279 103.46445 curveto +219.1279 102.71262 219.4266 101.99167 219.95819 101.4601 curveto +220.48976 100.92851 221.21071 100.6298 221.96254 100.6298 curveto +222.71437 100.6298 223.43532 100.92851 223.96689 101.4601 curveto +224.49847 101.99167 224.79718 102.71262 224.79718 103.46445 curveto closepath + stroke +224.06253 89.07642 moveto +(mo) cmr10 9.96265 fshow +237.62283 89.07642 moveto +(del) cmr10 9.96265 fshow + 0 0.3985 dtransform truncate idtransform setlinewidth pop 0 setlinecap +newpath 250.95064 89.27562 moveto +253.93944 89.27562 lineto stroke +253.93944 89.07642 moveto +(t) cmr10 9.96265 fshow +257.53712 89.07642 moveto +(yp) cmr10 9.96265 fshow +268.60674 89.07642 moveto +(e) cmr10 9.96265 fshow + 0 0.5 dtransform truncate idtransform setlinewidth pop 1 setlinecap +newpath 190.04245 77.95264 moveto +31.92009 77.95264 lineto stroke + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth +newpath 31.92009 77.95264 moveto +31.92009 100.62985 lineto stroke + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 34.75473 103.46423 moveto +34.75473 104.21606 34.45602 104.93701 33.92444 105.46858 curveto +33.39287 106.00017 32.67192 106.29887 31.92009 106.29887 curveto +31.16826 106.29887 30.44731 106.00017 29.91574 105.46858 curveto +29.38416 104.93701 29.08545 104.21606 29.08545 103.46423 curveto +29.08545 102.7124 29.38416 101.99146 29.91574 101.45988 curveto +30.44731 100.9283 31.16826 100.6296 31.92009 100.6296 curveto +32.67192 100.6296 33.39287 100.9283 33.92444 101.45988 curveto +34.45602 101.99146 34.75473 102.7124 34.75473 103.46423 curveto closepath + stroke +112.81847 82.54333 moveto +(\(DER\)) cmr10 9.96265 fshow +145.61217 82.54333 moveto +(*made) cmr10 9.96265 fshow + 0 0.3985 dtransform truncate idtransform setlinewidth pop 0 setlinecap +newpath 174.43747 82.74254 moveto +177.42627 82.74254 lineto stroke +177.42627 82.54333 moveto +(b) cmr10 9.96265 fshow +182.68437 82.54333 moveto +(y) cmr10 9.96265 fshow + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth 1 setlinecap +newpath 211.32219 70.86603 moveto +211.32219 42.51962 lineto stroke + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 211.32219 42.51962 moveto +163.79173 42.51962 lineto stroke +newpath 163.79169 42.51962 moveto +163.79169 43.27145 163.49298 43.9924 162.9614 44.52397 curveto +162.42982 45.05556 161.70888 45.35426 160.95705 45.35426 curveto +160.20522 45.35426 159.48427 45.05556 158.9527 44.52397 curveto +158.42111 43.9924 158.1224 43.27145 158.1224 42.51962 curveto +158.1224 41.76779 158.42111 41.04684 158.9527 40.51527 curveto +159.48427 39.98369 160.20522 39.68498 160.95705 39.68498 curveto +161.70888 39.68498 162.42982 39.98369 162.9614 40.51527 curveto +163.49298 41.04684 163.79169 41.76779 163.79169 42.51962 curveto closepath + stroke +190.9297 46.55681 moveto +(y) cmr10 9.96265 fshow +195.911 46.55681 moveto +(ear) cmr10 9.96265 fshow + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth +newpath 232.60289 70.86603 moveto +232.60289 7.08661 lineto stroke + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 232.60289 7.08661 moveto +163.79114 7.08661 lineto stroke +newpath 163.79138 7.08661 moveto +163.79138 7.83844 163.49268 8.55939 162.96109 9.09096 curveto +162.42952 9.62254 161.70857 9.92125 160.95674 9.92125 curveto +160.20491 9.92125 159.48396 9.62254 158.9524 9.09096 curveto +158.4208 8.55939 158.1221 7.83844 158.1221 7.08661 curveto +158.1221 6.33478 158.4208 5.61383 158.9524 5.08226 curveto +159.48396 4.55067 160.20491 4.25197 160.95674 4.25197 curveto +161.70857 4.25197 162.42952 4.55067 162.96109 5.08226 curveto +163.49268 5.61383 163.79138 6.33478 163.79138 7.08661 curveto closepath stroke +188.6431 9.1866 moveto +(*serial) cmr10 9.96265 fshow + 0 0.3985 dtransform truncate idtransform setlinewidth pop 0 setlinecap +newpath 216.9979 9.3858 moveto +219.9867 9.3858 lineto stroke +219.9867 9.1866 moveto +(no) cmr10 9.96265 fshow +showpage +%%EOF diff --git a/Master/texmf-dist/doc/latex/webguide/expeg6.mps b/Master/texmf-dist/doc/latex/webguide/expeg6.mps new file mode 100644 index 00000000000..52439977599 --- /dev/null +++ b/Master/texmf-dist/doc/latex/webguide/expeg6.mps @@ -0,0 +1,228 @@ +%!PS +%%BoundingBox: -1 -1 274 159 +%%Creator: MetaPost +%%CreationDate: 1999.12.08:1516 +%%Pages: 1 +%*Font: cmr10 9.96265 9.96265 28:e000000d4238007e4fbc4 +%%EndProlog +%%Page: 1 1 + 0 0.5 dtransform truncate idtransform setlinewidth pop [] 0 setdash + 1 setlinejoin 10 setmiterlimit +newpath 0 106.29904 moveto +63.84018 106.29904 lineto +63.84018 120.47224 lineto +0 120.47224 lineto + closepath stroke +2.83464 109.92639 moveto +(man) cmr10 9.96265 fshow +21.37624 109.92639 moveto +(ufacturer) cmr10 9.96265 fshow +newpath 95.76027 141.73206 moveto +158.12236 141.73206 lineto +158.12236 155.90526 lineto +95.76027 155.90526 lineto + closepath stroke + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth 1 setlinecap +newpath 152.45308 141.73206 moveto +152.45308 155.90526 lineto stroke +104.63104 145.41476 moveto +(STRING) cmr10 9.96265 fshow + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 190.04245 106.29904 moveto +253.88263 106.29904 lineto +253.88263 120.47224 lineto +190.04245 120.47224 lineto + closepath stroke +200.36848 109.92639 moveto +(car) cmr10 9.96265 fshow + 0 0.3985 dtransform truncate idtransform setlinewidth pop 0 setlinecap +newpath 214.27739 110.1256 moveto +217.26628 110.1256 lineto stroke +217.26628 109.92639 moveto +(mo) cmr10 9.96265 fshow +230.82658 109.92639 moveto +(del) cmr10 9.96265 fshow + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 190.04245 70.86603 moveto +253.88263 70.86603 lineto +253.88263 85.03923 lineto +190.04245 85.03923 lineto + closepath stroke +215.30693 75.80788 moveto +(car) cmr10 9.96265 fshow +newpath 95.76027 35.43301 moveto +158.12236 35.43301 lineto +158.12236 49.60622 lineto +95.76027 49.60622 lineto + closepath stroke + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth 1 setlinecap +newpath 152.45308 35.43301 moveto +152.45308 49.60622 lineto stroke +100.6183 39.11572 moveto +(INTEGER) cmr10 9.96265 fshow + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 95.76027 0 moveto +158.12236 0 lineto +158.12236 14.1732 lineto +95.76027 14.1732 lineto + closepath stroke + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth +newpath 152.45308 0 moveto +152.45308 14.1732 lineto stroke +104.63104 3.68271 moveto +(STRING) cmr10 9.96265 fshow +newpath 31.92009 120.47224 moveto +31.92009 148.81866 lineto stroke + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 31.92009 148.81866 moveto +90.09087 148.81866 lineto stroke +newpath 95.76021 148.81866 moveto +95.76021 149.5705 95.4615 150.29144 94.92992 150.82301 curveto +94.39835 151.3546 93.6774 151.6533 92.92557 151.6533 curveto +92.17374 151.6533 91.45279 151.3546 90.92122 150.82301 curveto +90.38963 150.29144 90.09093 149.5705 90.09093 148.81866 curveto +90.09093 148.06683 90.38963 147.34589 90.92122 146.81432 curveto +91.45279 146.28273 92.17374 145.98402 92.92557 145.98402 curveto +93.6774 145.98402 94.39835 146.28273 94.92992 146.81432 curveto +95.4615 147.34589 95.76021 148.06683 95.76021 148.81866 curveto closepath + stroke +34.02008 150.91866 moveto +(*name) cmr10 9.96265 fshow + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth +newpath 221.96254 120.47224 moveto +221.96254 148.81866 lineto stroke + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 221.96254 148.81866 moveto +163.79176 148.81866 lineto stroke +newpath 163.7917 148.81866 moveto +163.7917 149.5705 163.493 150.29144 162.96141 150.82301 curveto +162.42984 151.3546 161.7089 151.6533 160.95706 151.6533 curveto +160.20523 151.6533 159.48428 151.3546 158.95271 150.82301 curveto +158.42113 150.29144 158.12242 149.5705 158.12242 148.81866 curveto +158.12242 148.06683 158.42113 147.34589 158.95271 146.81432 curveto +159.48428 146.28273 160.20523 145.98402 160.95706 145.98402 curveto +161.7089 145.98402 162.42984 146.28273 162.96141 146.81432 curveto +163.493 147.34589 163.7917 148.06683 163.7917 148.81866 curveto closepath + stroke +191.63495 150.91866 moveto +(*name) cmr10 9.96265 fshow +newpath 190.04245 113.38565 moveto +69.50941 113.38565 lineto stroke +newpath 69.50945 113.38565 moveto +69.50945 114.13748 69.21074 114.85843 68.67915 115.39 curveto +68.14758 115.92159 67.42664 116.22029 66.6748 116.22029 curveto +65.92297 116.22029 65.20203 115.92159 64.67046 115.39 curveto +64.13887 114.85843 63.84016 114.13748 63.84016 113.38565 curveto +63.84016 112.63382 64.13887 111.91287 64.67046 111.3813 curveto +65.20203 110.84972 65.92297 110.55101 66.6748 110.55101 curveto +67.42664 110.55101 68.14758 110.84972 68.67915 111.3813 curveto +69.21074 111.91287 69.50945 112.63382 69.50945 113.38565 curveto closepath + stroke +150.59355 117.42284 moveto +(made) cmr10 9.96265 fshow + 0 0.3985 dtransform truncate idtransform setlinewidth pop 0 setlinecap +newpath 174.43755 117.62204 moveto +177.42635 117.62204 lineto stroke +177.42635 117.42284 moveto +(b) cmr10 9.96265 fshow +182.68436 117.42284 moveto +(y) cmr10 9.96265 fshow + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth 1 setlinecap +newpath 221.96254 85.03923 moveto +221.96254 100.62985 lineto stroke + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 224.79718 103.46445 moveto +224.79718 104.21628 224.49847 104.93723 223.96689 105.4688 curveto +223.43532 106.00038 222.71437 106.29909 221.96254 106.29909 curveto +221.21071 106.29909 220.48976 106.00038 219.95819 105.4688 curveto +219.4266 104.93723 219.1279 104.21628 219.1279 103.46445 curveto +219.1279 102.71262 219.4266 101.99167 219.95819 101.4601 curveto +220.48976 100.92851 221.21071 100.6298 221.96254 100.6298 curveto +222.71437 100.6298 223.43532 100.92851 223.96689 101.4601 curveto +224.49847 101.99167 224.79718 102.71262 224.79718 103.46445 curveto closepath + stroke +224.06253 89.07642 moveto +(mo) cmr10 9.96265 fshow +237.62283 89.07642 moveto +(del) cmr10 9.96265 fshow + 0 0.3985 dtransform truncate idtransform setlinewidth pop 0 setlinecap +newpath 250.95064 89.27562 moveto +253.93944 89.27562 lineto stroke +253.93944 89.07642 moveto +(t) cmr10 9.96265 fshow +257.53712 89.07642 moveto +(yp) cmr10 9.96265 fshow +268.60674 89.07642 moveto +(e) cmr10 9.96265 fshow + 0 0.5 dtransform truncate idtransform setlinewidth pop 1 setlinecap +newpath 190.04245 77.95264 moveto +31.92009 77.95264 lineto stroke + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth +newpath 31.92009 77.95264 moveto +31.92009 100.62985 lineto stroke + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 34.75473 103.46423 moveto +34.75473 104.21606 34.45602 104.93701 33.92444 105.46858 curveto +33.39287 106.00017 32.67192 106.29887 31.92009 106.29887 curveto +31.16826 106.29887 30.44731 106.00017 29.91574 105.46858 curveto +29.38416 104.93701 29.08545 104.21606 29.08545 103.46423 curveto +29.08545 102.7124 29.38416 101.99146 29.91574 101.45988 curveto +30.44731 100.9283 31.16826 100.6296 31.92009 100.6296 curveto +32.67192 100.6296 33.39287 100.9283 33.92444 101.45988 curveto +34.45602 101.99146 34.75473 102.7124 34.75473 103.46423 curveto closepath + stroke +112.81847 82.54333 moveto +(\(DER\)) cmr10 9.96265 fshow +145.61217 82.54333 moveto +(*made) cmr10 9.96265 fshow + 0 0.3985 dtransform truncate idtransform setlinewidth pop 0 setlinecap +newpath 174.43747 82.74254 moveto +177.42627 82.74254 lineto stroke +177.42627 82.54333 moveto +(b) cmr10 9.96265 fshow +182.68437 82.54333 moveto +(y) cmr10 9.96265 fshow + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth 1 setlinecap +newpath 211.32219 70.86603 moveto +211.32219 42.51962 lineto stroke + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 211.32219 42.51962 moveto +163.79173 42.51962 lineto stroke +newpath 163.79169 42.51962 moveto +163.79169 43.27145 163.49298 43.9924 162.9614 44.52397 curveto +162.42982 45.05556 161.70888 45.35426 160.95705 45.35426 curveto +160.20522 45.35426 159.48427 45.05556 158.9527 44.52397 curveto +158.42111 43.9924 158.1224 43.27145 158.1224 42.51962 curveto +158.1224 41.76779 158.42111 41.04684 158.9527 40.51527 curveto +159.48427 39.98369 160.20522 39.68498 160.95705 39.68498 curveto +161.70888 39.68498 162.42982 39.98369 162.9614 40.51527 curveto +163.49298 41.04684 163.79169 41.76779 163.79169 42.51962 curveto closepath + stroke +190.9297 46.55681 moveto +(y) cmr10 9.96265 fshow +195.911 46.55681 moveto +(ear) cmr10 9.96265 fshow + 0.5 0 dtransform exch truncate exch idtransform pop setlinewidth +newpath 232.60289 70.86603 moveto +232.60289 7.08661 lineto stroke + 0 0.5 dtransform truncate idtransform setlinewidth pop +newpath 232.60289 7.08661 moveto +163.79114 7.08661 lineto stroke +newpath 163.79138 7.08661 moveto +163.79138 7.83844 163.49268 8.55939 162.96109 9.09096 curveto +162.42952 9.62254 161.70857 9.92125 160.95674 9.92125 curveto +160.20491 9.92125 159.48396 9.62254 158.9524 9.09096 curveto +158.4208 8.55939 158.1221 7.83844 158.1221 7.08661 curveto +158.1221 6.33478 158.4208 5.61383 158.9524 5.08226 curveto +159.48396 4.55067 160.20491 4.25197 160.95674 4.25197 curveto +161.70857 4.25197 162.42952 4.55067 162.96109 5.08226 curveto +163.49268 5.61383 163.79138 6.33478 163.79138 7.08661 curveto closepath stroke +188.6431 9.1866 moveto +(*serial) cmr10 9.96265 fshow + 0 0.3985 dtransform truncate idtransform setlinewidth pop 0 setlinecap +newpath 216.9979 9.3858 moveto +219.9867 9.3858 lineto stroke +219.9867 9.1866 moveto +(no) cmr10 9.96265 fshow +showpage +%%EOF diff --git a/Master/texmf-dist/doc/latex/webguide/webguide.css b/Master/texmf-dist/doc/latex/webguide/webguide.css new file mode 100644 index 00000000000..a952808a737 --- /dev/null +++ b/Master/texmf-dist/doc/latex/webguide/webguide.css @@ -0,0 +1,60 @@ + +/* start css.sty */ +.cmr-10{font-size:90%;} +.cmr-10--109{font-size:99%;} +.cmr-17{font-size:154%;} +.cmr-12{font-size:109%;} +.cmsy-8{font-size:72%;} +.cmtt-12{font-size:109%;font-family: monospace;} +.cmsy-10--109{font-size:99%;} +.cmtt-10--109{font-size:99%;font-family: monospace;} +.cmbx-10{font-size:90%; font-weight: bold;} +.cmcsc-10--109{font-size:99%;} +.cmss-10--109{font-size:99%; font-family: sans-serif;} +.cmti-10--109{font-size:99%; font-style: italic;} +.small-caps{font-variant: small-caps; } +p.noindent { text-indent: 0em } +p.nopar { text-indent: 0em; } +p.indent{ text-indent: 1.5em } +a img { border-top: 0; border-left: 0; border-right: 0; } +center { margin-top:1em; margin-bottom:1em; } +td center { margin-top:0em; margin-bottom:0em; } +.Canvas { position:relative; } +div.displaymath{text-align:center;} +img.mathdisplay, div.displaymath, img.par-mathdisplay, div.par-displaymath { margin-top: 1em; margin-bottom: 1em; } +center img.mathdisplay, td img.mathdisplay, center img.par-mathdisplay, td img.par-mathdisplay { margin-top: 0; margin-bottom:0 ; } +div.displaymath{text-align:center;} +.obeylines-h,.obeylines-v {white-space: nowrap; } +.underline{ text-decoration:underline; } +.overline{ text-decoration:overline; } +span.pmatrix img{vertical-align:middle;} +div.center {text-align: center;} +div.center div {text-align: left;} +div.flushright {text-align: right;} +div.flushright div {text-align: left;} +div.flushleft {text-align: left;} +div.td00{ margin-left:0; margin-right:0; } +div.td01{ margin-left:0; margin-right:5; } +div.td10{ margin-left:5; margin-right:0; } +div.td11{ margin-left:5; margin-right:5; } +.hline hr, .cline hr{ height : 1px; } +li p.indent, li p.indent{ text-indent: 0em } +div.newtheorem { margin-bottom: 2em; margin-top: 2em;} +span.footnotetext{ font-size:75%; font-style:italic; } +span.TEX {letter-spacing: -0.125em; } +span.TEX span.E{ position:relative;top:0.5ex;left:-0.0417em;} +a span.TEX span.E {text-decoration: none; } +span.LATEX span.A{ position:relative; top:-0.5ex; left:-0.4em; font-size:85%;} +span.LATEX span.TEX{ position:relative; left: -0.4em; } +.marginpar {width:20%; float:right; text-align:left; margin-left:1em; margin-top:0.5em; font-size:85%; text-decoration:underline;} +.equation td{text-align:center; } +td.equation { margin-top:1em; margin-bottom:1em; } +p.bibitem { text-indent: -2em; margin-left: 2em; } +h1.partHead{text-align: center} +.paragraphHead, .likeparagraphHead { margin-top:2em; font-weight: bold;} +.subparagraphHead, .likesubparagraphHead { font-weight: bold;} +.quote {margin-bottom:0.25em; margin-top:0.25em; margin-left:1em; } +.caption td.id{font-weight: bold; white-space: nowrap; } +h2.titleHead{text-align:center;} +div.maketitle{ margin-bottom: 2em; } +/* end css.sty */ diff --git a/Master/texmf-dist/doc/latex/webguide/webguide.html b/Master/texmf-dist/doc/latex/webguide/webguide.html new file mode 100644 index 00000000000..c1fd9f281b0 --- /dev/null +++ b/Master/texmf-dist/doc/latex/webguide/webguide.html @@ -0,0 +1,874 @@ + + + +A Brief Guide to LaTeX{} Tools for Web Publishing
+ +

A Brief Guide to LaTeX Tools for Web Publishing

+
Peter R. Wilson* +
peter.r.wilson@boeing.com
+
+
11 March 2000
+ +
*With helpful critiques by Eitan Gurari (gurari@cis.ohio-state.edu) and David Wilson + (davidw@utopiatype.com.au).
+
+Abstract
+

This document provides a brief guide to converting LaTeX documents to forms more + suitable for dissemination via the Web. +

+

Contents

+
+
1 Introduction +
 1.1 URLs +
 1.2 Disclaimer +
2 PDF +
 2.1 From PostScript to PDF +
 2.2 From DVI to PDF +
 2.3 From LaTeX to PDF +
 2.4 Fonts +
 2.5 MetaPost +
3 HTML +
 3.1 Self-parsing systems +
 3.2 TeX-based parsing system +
4 Examples + +
+

List of Figures

+
1 Metapost illustration of an EXPRESS-G diagram
+
+ +

1 Introduction

+

Publishing on the Web has rapidly achieved significant importance, for example, the International +Organization for Standardization (ISO) is moving towards electronic forms of International +Standard documents that are suitable for publishing on the Web, and in particular, documents +as PDF or HTML files rather than their traditional request for camera-ready paper +copy. +

Documents written using LaTeX [Lam94] tagging can be easily converted to PostScript, PDF +and HTML, all from the single electronic source. This guide briefly notes some of the ways that +this can be accomplished. Most of the programs and systems mentioned here are described in +more detail in [GR99]. +

I have made no attempt to design this document for Web publication. The typographical rules +for printing on paper are well founded, having been developed over hundreds of years. +Display on computer screens is a very different matter and requires a different set of +rules, most of which, as yet, are either in a state of flux or unavailable. For LaTeXers +who are interested in this topic I suggest a look at D. P. Story's work on AcroTeX ( +http://www.math.uakron.edu/~dpstory/acrotex.html). Further, for the example conversions I +have used only the minimal tool options necessary. Many of the tools have extensive capabilities +which are well documented in their accompanying user manuals; these should be consulted for +further information. +

1.1 URLs

+

I have tried to provide URLs for the programs and systems mentioned here. Most LaTeX-related +software is available from the Comprehensive TeX Archive Network (CTAN). There are three +sites, ftp://ctan.tug.org/tex-archive in the USA, ftp://ftp.tex.ac.uk/tex-archive in +the UK, and ftp://ftp.dante.de/tex-archive in Germany, as well as several mirror sites. +Usefully, the CTAN sites (but not necessarily a mirror site) supports on-the-fly zipping of files and +entire directories, which makes downloading a group of files less tedious than having to get them +one-by-one. Below, I have used ftp://ctan.tug.org/tex-archive to stand for any of the three +CTAN sites. +

1.2 Disclaimer

+

Nothing that is said in this document is meant to imply any endorsement or recommendation, +either positive or negative, concerning any systems or programs mentioned herein. +

Many of the systems or programs are `free' in the sense that they are either public domain or +their licences are roughly equivalent to the GNU Public License. Others are either commercial or +have more restricitive licenses or may require payment. Where known, programs and systems that +are not `free' are noted. + +

2 PDF

+

The traditional output from a LaTeX (e.g., *.tex) file is a `device independent' *.dvi file. The *.dvi +file is then processed further to convert it to a format suitable for printing on a particular printing +device. In the vast majority of cases the final printable format has been PostScript, +obtained by running the *.dvi file through a program like dvips, to generate a *.ps +file. +

PostScript was developed by Adobe Systems. The Portable Document Format (PDF) has +since also been developed by Adobe, and seems to be overtaking PostScript as the format of +choice for printing, and especially for display via the Web. +

DVI and PDF are somewhat similar in that they both describe where (electronic) ink is to be +put on (electronic) paper. PostScript also does this but at the same time it is a complete +programming language. This means that it is inherently more difficult, time consuming, and +computer intensive, to process PostScript than either DVI or PDF. This is probably the reason +behind the popularity of PDF on the Web. +

There are now several methods of producing a PDF (e.g., *.pdf) file from *.tex. These +include: +

+

2.1 From PostScript to PDF

+

There are basically two routes to getting from PostScript to PDF. The first of these is to use +Acrobat software from Adobe Systems, which essentially means the commercial Distiller +program. Distiller can read in a PostScript file and output a PDF file where the visual results +of printing the two files are identical. This, or any other, PDF file can be viewed and/or printed +via the charge-free Acrobat Reader program. Note that when using Reader the `fit to +paper' option may alter the page layout, for example by changing the height of the text +block. +

The second route is to use a non-Adobe converter program, like Ghostscript which runs on +nearly all operating systems and which is obtainable from http://www.cs.wisc.edu/~ghost. +The Ghostscript distribution comes with a script called ps2pdf which performs the conversion. +The distribution also provides the popular Ghostview program, which is a viewer for both +PostScript and PDF files. +

Another converter program, which does have some licensing conditions that may not be suitable +for all users, is PStill; it is available from http://www.this.net/~frank/pstill.html. + +

2.2 From DVI to PDF

+

Mark Wicks' dvipdfm program ( http://odo.kettering.edu/dvipdfm) converts a *.dvi file to a +*.pdf file. The program is used in the same manner as dvips and provides similar +capabilities. +

PostScript illustrations are handled in one of two ways. Simple PostScript generated by +the METAPOST program [Hob92] is included natively. Any other PostScript file is first +converted to PDF by using an external program like Ghostscript and then inserted +into the output file. Illustrations in PDF, PNG and JPEG formats require no external +aids. +

dvipdfm is written in C but there are some binaries for Linux systems. +

2.3 From LaTeX to PDF

+

The pdfLaTeX program being developed by Hàn Thê Thành is a modified version of TeX that +generates *.pdf instead of *.dvi output files. pdfLaTeX is distributed with many of the free LaTeX +distributions, and is also obtainable from ftp://ftp.cstug.cz/pub/tex/local/cstug/thanh, +although it may be better to try ftp://ctan.tug.org/tex-archive/systems/pdftex. +

Running pdfLaTeX is very similar to running LaTeX, but some minor changes are required to +the *.tex file. For example: 
+ %  example.tex   example latex file
+ \documentclass[...]{...}
+ \newif\ifpdf
+ \ifx\pdfoutput\undefined
+   \pdffalse
+ \else
+   \pdftrue
+ \fi
+ 
+ \ifpdf
+   \pdfoutput=1
+ %  \usepackage[pdftex]{graphicx}  % uncomment if using graphicx
+ %  \usepackage[pdftex]{hyperref}  % uncomment if using hyperref
+ \else
+ %  \usepackage{graphicx}  % uncomment if using graphicx
+ %  \usepackage{hyperref}  % uncomment if using hyperref
+ \fi
+ ....
+
+
+

Running + +
latex example +
will produce example.dvi, while running +
pdflatex example +
will produce example.pdf. It is thus very easy to generate both *.dvi and *.pdf from the same +LaTeX source file. +

pdflatex will handle graphics files in the following formats: PDF, PNG, JPEG and TIFF, but +notice that (Encapsulated) PostScript is missing from this list. However, it can handle directly the +simple Encapsulated PostScript output by METAPOST [Hob92]. It does, though, expect +METAPOST files to have a .mps extension. To include PostScript from other sources it is necessary +to convert the PostScript to PDF. +

pdftex, and hence pdflatex, has some extra primitive commands that are not available in +TeX itself specifically for accessing aspects of the PDF format, for example to create hypertext +links, bookmarks or article threads. Consult the manual for details. +

Independently of pdflatex the hyperref package ( +ftp://ctan.tug.org/tex-archive/macros/latex/contrib/supported/hyperref) extends the +functionality of the LaTeX cross-referencing commands to include hypertext links, and also ad hoc +hypertext links to, for example, external documents and URLs. +

2.4 Fonts

+

The normal fonts used with LaTeX are the Computer Modern family developed by Knuth using +METAFONT [Knu86]. All METAFONT fonts are in the form of bitmaps, which is unfortunate when it +comes to PDF. Typically, PDF will only use one size of each font for a document, and will scale +this if different font sizes are required. This normally works well as fonts used with PDF are +typically `Type 1' fonts (e.g., PostScript fonts) which are designed to be scaleable. Bitmap +fonts look terrible when scaled or printed at a resolution that they were not designed +for. +

In other words, expect bad results if you generate a PDF file with the original Computer +Modern fonts. +

Perhaps the easiest method of dealing with this is to use the most common PostScript fonts, +namely Times, Courier and Helvetica. All that is necessary is to add \usepackage{times} to the +document's preamble. +

Alternatively, if you need to use the CM fonts, perhaps because a lot of mathematics is +involved, many LaTeX distributions include Type 1 versions of the CM fonts. If you don't have +them they can be found at ftp://ctan.tug.org/tex-archive/fonts/cm/ps-type1/bluesky +and at ftp://ctan.tug.org/tex-archive/fonts/amsfonts/ps-type1 for the AMS +fonts. +

Goossens et al. provide useful and general information on installing and using different fonts +with LaTeX [GMS94], while for the fontophile, Alan Hoenig [Hoe98] delves much more deeply into +the installation of PostScript fonts. +

TeX doesn't care about the particular shape of any glyph, nor how it is constructed or +represented, it only cares about the space occupied by each character (i.e., the *.tfm files). It is +the DVI processor that needs to know in detail about the fonts in a document. So, the DVI + +processor has to be told to use Type 1 CM PostScript fonts. The following is for the +dvips program. For convenience, let $TEXMF stand for the root of the texmf tree (e.g., +/usr/teTeX/texmf). +

dvips looks in the $TEXMF/dvips/base/psfonts.map to see if it can use any PostScript fonts. +This file starts off something like: 
+ bchb8r CHarterBT-Bold "TeXBase1Encoding ReEncodeFont" <8r.enc <bchb8a.pfb
+ ...
+
+
To get dvips to use Type 1 versions of the CM fonts, additional lines must be added to +psfonts.map giving similar information about the fonts. The specification for CM fonts is simpler +and consists of lines like: 
+ cmb10 CMB10 <cmb10.pfb
+ cmbsy10 CMBSY10 <cmbsy10.pfb
+ ...
+
+
In the version of teTeX that I use, this information is in files bsr.map, bsr-interpolated.map, +cmcyr.map, hoekwater.map, and pl.map, all in directory $TEXMF/dvips/config. +

These files can either be copied by hand to the psfonts.map file in $TEXMF/dvips/base or in a +modern teTeX distribution (which should also have all the CM Type 1 font data) it is easiest to do +the following: +

+

Another more general method is to edit the file config.ps in directory $TEXMF/dvips/config and +at the appropriate place (which should be marked, but in any case after the line p psfonts.map) +add lines like: 
+ p +bsr.map
+ p +bsr-interpolated.map
+ ...
+
+
+ +

Another option when using dvips which avoids all of the above, is to call it with options, +like: +
dvips -Pamz -Pcmz -Ppdf -j0 [other options] filename +
and then use your prefered *.ps to *.pdf conversion process. +

2.5 MetaPost

+

John Hobby's METAPOST [Hob92] is a language based drawing program based on Knuth's +METAFONT [Knu86]. METAFONT was principally designed for creating fonts, and generates +bitmapped output, while METAPOST is principally for drawing general line illustrations and its +output is a particularly simple form of Encapsulated PostScript. + + +

+ +PIC +
Figure 1: Metapost illustration of an EXPRESS-G diagram
+ + +
+ This is not the place to describe METAPOST, but it can generate several output files, one for +each drawing, from a single input file called, say, fred.mp. The output files have a numeric +extension correspond to the number of the drawing. So, for example, it may generate files fred.1, +fred.2 and fred.3. For a document that is to be processed via LaTeX these files can be included as +is. However, for processing through pdfLaTeX, the files must have a .mps extension; for example +fred1.mps, fred2.mps and fred3.mps. +

Figure 1 is a METAPOST illustration that is included in this document by the code: +
+ \begin{figure}
+ \centering
+ \ifpdf
+   \includegraphics{expeg6.mps}
+ \else
+   \includegraphics{expeg.6}
+ \fi
+ \caption{Metapost illustration of an \textsc{express-g} diagram}
+   \label{fig:mp}
+ \end{figure}
+
+
where expeg6.mps is a copy of expeg.6, to cater for processing by either LaTeX or pdfLaTeX. +Actually, the following will also work: 
+ \begin{figure}
+ \centering
+ \includegraphics{expeg6.mps}
+ \caption{Metapost illustration of an \textsc{express-g} diagram}
+   \label{fig:mp}
+ \end{figure}
+
+
+

The figure demonstrates part of the capabilities of the expressg METAPOST package ( +ftp://ctan.tug.org/tex-archive/graphics/metapost/contrib/macros/expressg) for +drawing diagrams consisting of boxes, lines and annotations, such as flowcharts or ER +diagrams. +

3 HTML

+ +

There are a number of systems that convert a LaTeX tagged document into an HTML tagged +document. These can be divided into two classes: +

    +
  1. Systems that parse the *.tex file themselves. +
    2. +
  2. Systems that use TeX as the file parser.
+

There are several that do their own parsing, but only one that I know of that uses TeX as the +parser. +

TeX is a macro language and the meaning of existing commands can be changed on the +fly, and also new commands can be defined on the fly [Knu84]. As perhaps the most +extreme example of this is David Carlisle's xii.tex TeX code, which is obtainable as +ftp://ctan.tug.org/tex-archive/macros/plain/contrib/xii.tex: 
+ \let~\catcode~`76~`A13~`F1~`j00~`P2jdefA71F~`7113jdefPALLF
+ PA''FwPA;;FPAZZFLaLPA//71F71iPAHHFLPAzzFenPASSFthP;A$$FevP
+ A@@FfPARR717273F737271P;ADDFRgniPAWW71FPATTFvePA**FstRsamP
+ AGGFRruoPAqq71.72.F717271PAYY7172F727171PA??Fi*LmPA&&71jfi
+ Fjfi71PAVVFjbigskipRPWGAUU71727374 75,76Fjpar71727375Djifx
+ :76jelse&U76jfiPLAKK7172F71l7271PAXX71FVLnOSeL71SLRyadR@oL
+ RrhC?yLRurtKFeLPFovPgaTLtReRomL;PABB71 72,73:Fjif.73.jelse
+ B73:jfiXF71PU71 72,73:PWs;AMM71F71diPAJJFRdriPAQQFRsreLPAI
+ I71Fo71dPA!!FRgiePBt'el@ lTLqdrYmu.Q.,Ke;vz vzLqpip.Q.,tz;
+ ;Lql.IrsZ.eap,qn.i. i.eLlMaesLdRcna,;!;h htLqm.MRasZ.ilk,%
+ s$;z zLqs'.ansZ.Ymi,/sx ;LYegseZRyal,@i;@ TLRlogdLrDsW,@;G
+ LcYlaDLbJsW,SWXJW ree @rzchLhzsW,;WERcesInW qt.'oL.Rtrul;e
+ doTsW,Wk;Rri@stW aHAHHFndZPpqar.tridgeLinZpe.LtYer.W,:jbye
+
+
If you run this through TeX (not LaTeX) I'm sure you will be surprised at the result. +

There is inevitably a problem when converting from LaTeX to HTML for a document that +includes figures/illustrations or anything more than the most simple mathematical typesetting as, +basically, HTML provides no support. Typically, mathematics and illustrations, are converted to a +picture format and then inserted into the HTML document as graphics, usually with a very poor +appearance. +

However, for mathematics the situation is starting to change because of the advent of +MathML ( http://www.w3.org/TR/MathML2). In particular the Milestone 13 release of Mozilla ( +http://www.mozilla.org/binaries.html) is a MathML-enabled browser. Some examples, +generated by TeX4ht, are available at http://www.maths.ox.ac.uk/~gartside/mozSuccess. +

All the systems generate HTML tagged documents, with the particular tagging `style' set by +the system. It is advantageous to use a converter which either by default generates your desired +style, or which can be modified in some manner to do so. + +

3.1 Self-parsing systems

+

The self-parsing systems incorporate their own parsers for the TeX language. In essence, this +means that they `know' the meaning of common TeX commands, but probably not all possible +commands. It is advantageous to use a system that can be extended to deal with commands that +were not anticipated by the author. +

The only system I am familiar with in this class is Peter Wilson's ltx2x program ( +ftp://ctan.tug.org/tex-archive/support/ltx2x). This program works by replacing known +LaTeX commands, and their arguments, by user-specified text strings [Wil96]. It is unable to +handle anything more than very simple mathematics and ignores any pictures. The user-specified +command texts are kept in a simple command-table file. Within limits, new LaTeX commands +and environments may be specified within a command-table file and the command texts modified. +The ltx2x program has been used to `detex' (i.e., remove all LaTeX commands) files, +convert to HTML, and convert to SGML. It cannot convert to XML due to a yet to be +resolved technical problem in dealing with end of paragraph tags. The program is written +in C and so requires a C compiler for installation. The system can be extended via +some C programming, in which case the flex and bison programs are also required. +There is no chance that ltx2x would ever make any sense whatsoever of xii.tex on +page 10. +

Perhaps the most venerable system is the LaTeX2HTML system +( http://www-texdev.mpce.mq.edu.au/l2h/docs/manual or +ftp://ctan.tug.org/tex-archive/support/latex2html), originally by Nikos Drakos +and now maintained by Ross Moore and others. This system is written using Perl ( +ftp://ftp.uu.net/languages/perl). It also requires a database management system such as the +Unix DBM or NDBM, or the GNU GDBM system. Further, it requires Ghostscript and the +netpbm library of graphics utilities ( ftp://ftp.x.org/contrib/utilities). To extend or +change the default conversion style requires, I think, some Perl programming. A fuller description +and examples are given in [GR99]. +

Another converter is the TtH program by Ian Hutchinson ( http://hutchinson.belmont.ma.us/tth) +which is cost-free for non-commercial use; commercial use in this case is roughly by anyone who gets +paid while using it (but see http://hutchinson.belmont.ma.us/tth/tth-commercial/email.html +for the actual wording). There is also another version, TeX2HTML ( http://www.tex2html.com) +which is the `commercial GOLD version of the freeware Tth by Ian Hutchinson'. These programs +run on the usual range of operating systems. An example of the output from TtH is given +in [GR99]. +

3.2 TeX-based parsing system

+

Eitan Gurari's TeX4ht system appears to be unique in that it uses TeX as the +parser for the LaTeX document and instead effectively takes the *.dvi file as its +starting point for conversion to HTML. That is, it does not have to understand TeX +code and can, in fact, convert David Carlise's xii.tex (page 10) to HTML. The system + +is available from http://www.cis.ohio-state.edu/~gurari/TeX4ht/mn.html. It +consists of two C programs, one package file, and a set of *.4ht configuration files, one +for each of the typical LaTeX classes and packages. It also requires ImageMagick ( +http://www.wizards.dupont.com/cristy/www/archives.html) for handling illustrations and +non-simple mathematics. Simply speaking, the system is extended by writing new *.4ht file(s) and +its output modified by writing simple *.cfg file(s) that override the *.4ht file(s). At the moment, +the best and most detailed description is given in [GR99]. +

By default, TeX4ht can generate a non-tagged file or a file tagged with either HTML3.2 or +HTML4.0. By writing appropriate *.cfg files it can be made to generate XML tagged files. The +system comes with a script called htlatex which controls the conversion process from LaTeX; +there is also the httex script for converting a TeX document. For instance, to convert the earlier +example LaTeX file, example.tex (page 3), to an HTML4.0 tagged document, it is enough to +run: +
htlatex example +
which will then output example.html. Similarly, to convert xii.tex just run: +
httex xii. +

4 Examples

+

Hopefully, you should find several versions of this document, all of which have been generated +from a single source file. These are: +

+

The HTML version uses the GIF file webguide0x.gif for the illustration; the file is automatically +generated by tex4ht using the ImageMagick convert program. The quality of the picture in the +viewed document depends on the particular viewer; different versions of Netscape, for example, +may display and print the diagram with very different rendering qualities. I asked TeX4ht to +generate this particular figure at 180dpi instead of the default 110dpi to improve the +quality. +

References

+ +

+[GMS94]   Michel Goossens, Frank Mittelbach, and Alexander Samarin. The LaTeX + Companion. Addison-Wesley Publishing Company, 1994. +

+[GR99]    Michel Goossens and Sebastion Rahtz. The LaTeX Web Companion - Integrating + TeX, HTML, and XML. Addison-Wesley Publishing Company, 1999. (with Eitan + Gurari, Ross Moore, and Robert Sutor). +

+[Hob92]    John Hobby. ‘A User’s Manual for MetaPost’. Technical Report 162, AT&T Bell + Laboratories, Murray Hill, NJ, 1992. +

+[Hoe98]    Alan Hoenig. TeX Unbound - LaTeX and TeX Strategies for Fonts, Graphics, & + More. Oxford University Press, 1998. +

+[Knu84]    Donald E. Knuth. The TeXbook. Addison-Wesley Publishing Company, 1984. +

+[Knu86]    Donald E. Knuth. The METAFONTbook. Addison-Wesley Publishing Company, + 1986. +

+[Lam94]    Leslie Lamport. LaTeX: A Document Preparation System. Addison-Wesley + Publishing Company, second edition, 1994. +

+[Wil96]    Peter R. Wilson. ltx2x: A LaTeX to X Auto-tagger. NIST Report NISTIR, June + 1996. +

+ + + + + + diff --git a/Master/texmf-dist/doc/latex/webguide/webguide.pdf b/Master/texmf-dist/doc/latex/webguide/webguide.pdf new file mode 100644 index 00000000000..ffdca467fa7 Binary files /dev/null and b/Master/texmf-dist/doc/latex/webguide/webguide.pdf differ diff --git a/Master/texmf-dist/doc/latex/webguide/webguide.ps.gz b/Master/texmf-dist/doc/latex/webguide/webguide.ps.gz new file mode 100644 index 00000000000..02f64e75d0b Binary files /dev/null and b/Master/texmf-dist/doc/latex/webguide/webguide.ps.gz differ diff --git a/Master/texmf-dist/doc/latex/webguide/webguide.tex b/Master/texmf-dist/doc/latex/webguide/webguide.tex new file mode 100644 index 00000000000..4b22433386e --- /dev/null +++ b/Master/texmf-dist/doc/latex/webguide/webguide.tex @@ -0,0 +1,615 @@ +% webguide.tex Guide to LaTeX, STEP and the Web, etc + +\documentclass[11pt]{article} + +% a11pream.tex generic preamble +\usepackage{url} +%\usepackage{ltx2html} +\setlength{\textheight}{8.0in} +\setlength{\textwidth}{6.0in} +\setlength{\oddsidemargin}{0.25in} +\setlength{\evensidemargin}{0.25in} +\setlength{\marginparwidth}{0.6in} +\setcounter{secnumdepth}{4} +\setcounter{tocdepth}{4} + +%% \usepackage{times} + +\newif\ifpdf +\ifx\pdfoutput\undefined + \pdffalse +\else + \pdftrue +\fi + +\ifpdf + \pdfoutput=1 + \usepackage[pdftex]{graphicx} +\else + \usepackage{graphicx} +\fi + +\newcommand{\file}[1]{\textsf{#1}} +\newcommand{\program}[1]{\texttt{#1}} +\newcommand{\package}[1]{\texttt{#1}} +\newcommand{\mpost}{\textsc{MetaPost}} +\newcommand{\mfont}{\textsc{metafont}} +\newcommand{\Han}{H\`{a}n Th\^{e} Th\`{a}nh} +\newcommand{\tex}{TeX} +\newcommand{\latex}{LaTeX} + +\title{A Brief Guide to \latex{} Tools for Web Publishing} +\author{Peter R. Wilson\thanks{With helpful critiques by +Eitan Gurari (\texttt{gurari@cis.ohio-state.edu}) and +David Wilson (\texttt{davidw@utopiatype.com.au}).} \\ + \texttt{peter.r.wilson@boeing.com}} +\date{11 March 2000} + +\begin{document} +\pagestyle{headings} +\pagenumbering{roman} +\maketitle +\begin{abstract} +This document provides a brief guide to converting \latex{} documents +to forms more suitable for dissemination via the Web. +\end{abstract} +\tableofcontents +\listoffigures +\clearpage +\pagenumbering{arabic} + +\section{Introduction} + + Publishing on the Web has rapidly achieved significant importance, +for example, the International Organization for Standardization (ISO) +is moving towards electronic forms of International Standard documents +that are suitable for publishing on the Web, and in particular, documents +as PDF or HTML files rather than their traditional request for camera-ready +paper copy. + + Documents written using \latex~\cite{LAMPORT94} tagging can be +easily converted to +PostScript, PDF and HTML, all from the single electronic source. This +guide briefly notes some of the ways that this can be accomplished. + Most of the programs and systems mentioned here are described in more +detail in~\cite{GOOSSENS99}. + + I have made no attempt to design this document for Web publication. The +typographical rules for printing on paper are well founded, having been +developed over hundreds of years. Display on computer screens is a +very different matter and requires a different set of rules, most of which, +as yet, are either in a state of flux or unavailable. For LaTeXers who +are interested in this topic I suggest a look at D.~P.~Story's work on +AcroTeX (\url{http://www.math.uakron.edu/~dpstory/acrotex.html}). Further, +for the example conversions I have used only the minimal tool options +necessary. Many of the tools have extensive capabilities which are well +documented in their accompanying user manuals; these should be consulted for +further information. + + +\subsection{URLs} + + I have tried to provide URLs for the programs and systems mentioned +here. Most \latex-related software is available from the Comprehensive +TeX Archive Network (CTAN). There are three sites, +\url{ftp://ctan.tug.org/tex-archive} in the USA, +\url{ftp://ftp.tex.ac.uk/tex-archive} in the UK, and +\url{ftp://ftp.dante.de/tex-archive} in Germany, as well as several mirror +sites. Usefully, the CTAN sites (but not necessarily a mirror site) supports +on-the-fly zipping of files and entire directories, which makes downloading +a group of files less tedious than having to get them one-by-one. Below, +I have used \url{ftp://ctan.tug.org/tex-archive} to stand for any of +the three CTAN sites. + + +\subsection{Disclaimer} + + Nothing that is said in this document is meant to imply any endorsement +or recommendation, either +positive or negative, concerning any systems or programs mentioned herein. + + Many of the systems or programs are `free' in the sense that they are +either public domain or their licences are roughly equivalent to the GNU +Public License. +Others are either commercial or have more restricitive +licenses or may require payment. Where known, programs and systems that are +not `free' are noted. + +\section{PDF} + + The traditional output from a \latex{} (e.g., \file{*.tex}) file is +a `device independent' \file{*.dvi} file. The \file{*.dvi} file is then processed further to convert +it to a format suitable for printing on a particular printing device. +In the vast majority of cases the final printable format +has been PostScript, obtained by running the \file{*.dvi} file through a +program like \program{dvips}, to generate a \file{*.ps} file. + + PostScript was developed by Adobe Systems. The Portable Document +Format (PDF) has since also been developed by Adobe, and seems to be +overtaking PostScript as the format of choice for printing, and especially +for display via the Web. + + DVI and PDF are somewhat similar in that they both describe where +(electronic) ink is to be put on (electronic) paper. PostScript also +does this but at the same time it is a complete programming language. +This means that it is inherently more difficult, time consuming, and computer +intensive, to process PostScript than either DVI or PDF. This is probably +the reason behind the popularity of PDF on the Web. + + There are now several methods of producing a PDF (e.g., \file{*.pdf}) +file from \file{*.tex}. These include: +\begin{itemize} +\item Converting from PostScript to PDF; + from \file{*.ps} to \file{*.pdf}. +\item Generate PDF from the device independent file; + from \file{*.dvi} to \file{*.pdf} +\item Generate PDF directly from the \latex{} source; + from \file{*.tex} to \file{*.pdf}. +\end{itemize} + + +\subsection{From PostScript to PDF} + + There are basically two routes to getting from PostScript to PDF. The +first of these is to use Acrobat software from Adobe Systems, which +essentially means the commercial \program{Distiller} program. +\program{Distiller} can read in a PostScript file and output a PDF file +where the visual results of printing the two files are identical. This, +or any other, PDF file can be viewed and/or printed via the charge-free +Acrobat \program{Reader} program. Note that when using \program{Reader} +the `fit to paper' option may alter the page layout, for example by changing +the height of the text block. + + + The second route is to use a non-Adobe converter program, +like \program{Ghostscript} which runs on nearly all operating systems and +which is obtainable from +\url{http://www.cs.wisc.edu/~ghost}. The \program{Ghostscript} distribution +comes with a script called \program{ps2pdf} which performs the conversion. +The distribution also provides the popular \program{Ghostview} program, +which is a viewer for both PostScript and PDF files. + + Another +converter program, which does have some licensing conditions that may not +be suitable for all users, is \program{PStill}; it is available from +\url{http://www.this.net/~frank/pstill.html}. + +\subsection{From DVI to PDF} + + Mark Wicks' \program{dvipdfm} program +(\url{http://odo.kettering.edu/dvipdfm}) converts a \file{*.dvi} file to a +\file{*.pdf} file. The program is used in the same manner as \program{dvips} +and provides similar capabilities. + + PostScript illustrations are handled in one of two ways. Simple PostScript +generated by the \mpost{} program~\cite{HOBBY92} is included natively. +Any other PostScript file is first converted to PDF by using an external +program like \program{Ghostscript} and then inserted +into the output file. Illustrations in PDF, PNG and JPEG formats require +no external aids. + + \program{dvipdfm} is written in C but there are some binaries for Linux +systems. + + +\subsection{From LaTeX to PDF} + + The \program{pdfLaTeX} program being developed by \Han{} is a modified +version of \tex{} that generates \file{*.pdf} instead of \file{*.dvi} output +files. \program{pdfLaTeX} is distributed with many of the free \latex{} +distributions, and is also obtainable from +\url{ftp://ftp.cstug.cz/pub/tex/local/cstug/thanh}, although it may be +better to try \url{ftp://ctan.tug.org/tex-archive/systems/pdftex}. + + Running \program{pdfLaTeX} is very similar to running \latex, but some +minor changes are required to the \file{*.tex} file. For example: \label{code:example} +\begin{verbatim} +% example.tex example latex file +\documentclass[...]{...} +\newif\ifpdf +\ifx\pdfoutput\undefined + \pdffalse +\else + \pdftrue +\fi + +\ifpdf + \pdfoutput=1 +% \usepackage[pdftex]{graphicx} % uncomment if using graphicx +% \usepackage[pdftex]{hyperref} % uncomment if using hyperref +\else +% \usepackage{graphicx} % uncomment if using graphicx +% \usepackage{hyperref} % uncomment if using hyperref +\fi +.... +\end{verbatim} + +Running \\ +\texttt{latex example} \\ +will produce \file{example.dvi}, while running \\ +\texttt{pdflatex example} \\ +will produce \file{example.pdf}. It is thus very easy to generate both +\file{*.dvi} and \file{*.pdf} from the same \latex{} source file. + + \program{pdflatex} will handle graphics files in the following formats: +PDF, PNG, JPEG and TIFF, but notice that (Encapsulated) PostScript is +missing from this list. However, it can handle directly the simple +Encapsulated PostScript output by \mpost~\cite{HOBBY92}. +It does, though, expect \mpost{} files to have a \file{.mps} extension. +To include PostScript from other sources it is necessary to convert the +PostScript to PDF. + + \program{pdftex}, and hence \program{pdflatex}, has some extra +primitive commands +that are not available in \tex{} itself specifically for accessing aspects +of the PDF format, for example to create hypertext links, bookmarks or +article threads. Consult the manual for details. + + Independently of \program{pdflatex} the \package{hyperref} package +(\url{ftp://ctan.tug.org/tex-archive/macros/latex/contrib/supported/hyperref}) +extends the functionality of the \latex{} cross-referencing commands to +include hypertext links, and also ad hoc hypertext links to, for example, +external documents and URLs. + +\subsection{Fonts} + + The normal fonts used with \latex{} are the Computer Modern family +developed by Knuth using \mfont~\cite{KNUTH86b}. +All \mfont{} fonts are in the form of +bitmaps, which is unfortunate when it comes to PDF. Typically, PDF will +only use one size of each font for a document, and will scale this if +different font sizes are required. This normally works well as fonts +used with PDF are typically `Type~1' fonts (e.g., PostScript fonts) +which are designed to be scaleable. Bitmap fonts look terrible when scaled +or printed at a resolution that they were not designed for. + + In other words, expect bad results if you generate a PDF file with +the original Computer Modern fonts. + + Perhaps the easiest method of dealing with this is to use the most common +PostScript fonts, namely Times, Courier and Helvetica. All that is +necessary is to add \verb|\usepackage{times}| to the document's preamble. + + Alternatively, if you need to use the CM fonts, perhaps because a lot +of mathematics is involved, many \latex{} distributions include +Type~1 versions of the CM fonts. If you don't have them they can be found at +\url{ftp://ctan.tug.org/tex-archive/fonts/cm/ps-type1/bluesky} and +at \url{ftp://ctan.tug.org/tex-archive/fonts/amsfonts/ps-type1} for the AMS fonts. + + Goossens \textit{et al.} provide useful and general information +on installing and using different fonts with \latex~\cite{GOOSSENS94}, +while for the fontophile, Alan Hoenig~\cite{HOENIG98} delves much +more deeply into the installation of PostScript fonts. + + \tex{} doesn't care about the particular shape of any glyph, nor how it +is constructed or represented, it only cares about the space occupied by +each character (i.e., the \file{*.tfm} files). +It is the DVI processor that needs to know in detail +about the fonts in a document. So, the DVI processor has to be told to +use Type~1 CM PostScript fonts. +The following is for the \program{dvips} program. +For convenience, let \path{$TEXMF} stand for the root of the +\path{texmf} tree (e.g., \path{/usr/teTeX/texmf}). + + \program{dvips} looks in the \path{$TEXMF/dvips/base/psfonts.map} +to see if it can use any PostScript fonts. This file starts off something +like: +\begin{verbatim} +bchb8r CHarterBT-Bold "TeXBase1Encoding ReEncodeFont" <8r.enc