--- /srv/reproducible-results/rbuild-debian/r-b-build.PxNJ6bDA/b1/htp_1.19-8_armhf.changes
+++ /srv/reproducible-results/rbuild-debian/r-b-build.PxNJ6bDA/b2/htp_1.19-8_armhf.changes
├── Files
│ @@ -1,3 +1,3 @@
│  
│   b74e597d68bdac944b68e80be574ca4c 68700 debug optional htp-dbgsym_1.19-8_armhf.deb
│ - b9bc0e2a31aff6e5a374d297b0855a45 115508 web optional htp_1.19-8_armhf.deb
│ + 051d914f882b182336f941b4eff1fec6 115140 web optional htp_1.19-8_armhf.deb
├── htp_1.19-8_armhf.deb
│ ├── file list
│ │ @@ -1,3 +1,3 @@
│ │  -rw-r--r--   0        0        0        4 2020-06-14 23:21:19.000000 debian-binary
│ │ --rw-r--r--   0        0        0     3612 2020-06-14 23:21:19.000000 control.tar.xz
│ │ --rw-r--r--   0        0        0   111704 2020-06-14 23:21:19.000000 data.tar.xz
│ │ +-rw-r--r--   0        0        0     3616 2020-06-14 23:21:19.000000 control.tar.xz
│ │ +-rw-r--r--   0        0        0   111332 2020-06-14 23:21:19.000000 data.tar.xz
│ ├── control.tar.xz
│ │ ├── control.tar
│ │ │ ├── ./control
│ │ │ │ @@ -1,12 +1,12 @@
│ │ │ │  Package: htp
│ │ │ │  Version: 1.19-8
│ │ │ │  Architecture: armhf
│ │ │ │  Maintainer: Marcelo Soares Mota <motasmarcelo@gmail.com>
│ │ │ │ -Installed-Size: 637
│ │ │ │ +Installed-Size: 626
│ │ │ │  Depends: libc6 (>= 2.4)
│ │ │ │  Section: web
│ │ │ │  Priority: optional
│ │ │ │  Homepage: http://htp.sourceforge.net
│ │ │ │  Description: nice HTML pre-processor
│ │ │ │   htp is an HTML pre-processor. It is designed to be a flexible authoring tool
│ │ │ │   that can easily be integrated into the HTML design process.
│ │ │ ├── ./md5sums
│ │ │ │ ├── ./md5sums
│ │ │ │ │┄ Files differ
│ ├── data.tar.xz
│ │ ├── data.tar
│ │ │ ├── file list
│ │ │ │ @@ -1,27 +1,27 @@
│ │ │ │  drwxr-xr-x   0 root         (0) root         (0)        0 2020-06-14 23:21:19.000000 ./
│ │ │ │  drwxr-xr-x   0 root         (0) root         (0)        0 2020-06-14 23:21:19.000000 ./usr/
│ │ │ │  drwxr-xr-x   0 root         (0) root         (0)        0 2020-06-14 23:21:19.000000 ./usr/bin/
│ │ │ │  -rwxr-xr-x   0 root         (0) root         (0)    42560 2020-06-14 23:21:19.000000 ./usr/bin/htp
│ │ │ │  drwxr-xr-x   0 root         (0) root         (0)        0 2020-06-14 23:21:19.000000 ./usr/share/
│ │ │ │  drwxr-xr-x   0 root         (0) root         (0)        0 2020-06-14 23:21:19.000000 ./usr/share/doc/
│ │ │ │  drwxr-xr-x   0 root         (0) root         (0)        0 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)    10522 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/alttext.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)    10498 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/alttext.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     1418 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/alttext.htp
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)     8850 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/block.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)     9462 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/block.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      781 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/block.htp
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)    10895 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/blockdef.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)     8100 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/blockdef.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     1075 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/blockdef.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     4763 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/bugs.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      737 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/bugs.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     3273 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/changelog.Debian.gz
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)    15492 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/comment.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)    15070 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/comment.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      676 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/comment.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)    13083 2020-06-14 23:16:46.000000 ./usr/share/doc/htp/copyright
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)    21495 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/def.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)    17954 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/def.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     3601 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/def.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     8030 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/default.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     3149 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/default.htp
│ │ │ │  drwxr-xr-x   0 root         (0) root         (0)        0 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/examples/
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      536 2015-05-16 17:04:11.000000 ./usr/share/doc/htp/examples/Makefile.sub
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     2404 2015-05-16 17:04:11.000000 ./usr/share/doc/htp/examples/album.hti
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     1087 2015-05-16 17:04:11.000000 ./usr/share/doc/htp/examples/album.htt
│ │ │ │ @@ -34,43 +34,43 @@
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     1576 2015-05-16 17:04:11.000000 ./usr/share/doc/htp/examples/quine.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      604 2015-05-16 17:04:11.000000 ./usr/share/doc/htp/examples/section.def
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     1189 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/examples/section.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      918 2015-05-16 17:04:11.000000 ./usr/share/doc/htp/examples/section.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      375 2015-05-16 17:04:11.000000 ./usr/share/doc/htp/examples/section.htt
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)    13032 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/expand.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     3702 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/expand.htp
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)    16409 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/file.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)    15888 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/file.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     2490 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/file.htp.gz
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)    14293 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/history.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     3946 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/history.htp.gz
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     3911 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/hlhtp.pl
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      165 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/htp.def
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     4049 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/htp.htt
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)     9852 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/if.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)     9062 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/if.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      932 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/if.htp
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)     9443 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/imageurl.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)     9305 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/imageurl.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     2507 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/imageurl.htp
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)     9160 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/img.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)     8662 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/img.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     1168 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/img.htp
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)     8940 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/inc.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)     8760 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/inc.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     1092 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/inc.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     9881 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/include.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     1894 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/include.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     4874 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/index.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)       78 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/index.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     7733 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/intro.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     3489 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/intro.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)    10774 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/license.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      454 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/license.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     3782 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/macros.def
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     5088 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/macros.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      388 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/macros.htp
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)    17181 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/metatag.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)    13692 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/metatag.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     2439 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/metatag.htp.gz
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)     8471 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/opt.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)     7911 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/opt.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      608 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/opt.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     7809 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/options.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     3100 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/options.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     8130 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/output.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      695 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/output.htp
│ │ │ │  drwxr-xr-x   0 root         (0) root         (0)        0 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/pic/
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      171 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/pic/arrow.png
│ │ │ │ @@ -79,17 +79,17 @@
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)    25563 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/pic/logo.png
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      455 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/pic/manbig.png
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      491 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/pic/manual.png
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     1313 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/pic/poweredbyhtp.png
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      679 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/pic/sficon.png
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      492 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/pic/source.png
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      523 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/pphtp.pl
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)     9063 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/quote.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)     7856 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/quote.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      390 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/quote.htp
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)     9962 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/set.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)     8935 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/set.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     1200 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/set.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      500 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/styles.css
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)    27219 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/template.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     2235 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/template.htp.gz
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     1914 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/toc.def
│ │ │ │  drwxr-xr-x   0 root         (0) root         (0)        0 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/tut/
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      146 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/tut/footer.hti
│ │ │ │ @@ -104,21 +104,21 @@
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      191 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/tut/tut3.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      356 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/tut/tut3.htt
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      297 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/tut/tut4.htt
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)    10517 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/tutorial.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     3393 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/tutorial.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     8009 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/undef.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      460 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/undef.htp
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)     8967 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/unset.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)     9701 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/unset.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      658 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/unset.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     7681 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/usage.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     2959 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/usage.htp
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)    12255 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/use.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)    13599 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/use.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     3300 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/use.htp
│ │ │ │ --rw-r--r--   0 root         (0) root         (0)    10854 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/while.html
│ │ │ │ +-rw-r--r--   0 root         (0) root         (0)    10388 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/while.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      938 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/while.htp
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     5288 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/wishlist.html
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)     1311 2020-06-14 23:21:19.000000 ./usr/share/doc/htp/wishlist.htp
│ │ │ │  drwxr-xr-x   0 root         (0) root         (0)        0 2020-06-14 23:21:19.000000 ./usr/share/doc-base/
│ │ │ │  -rw-r--r--   0 root         (0) root         (0)      235 2020-06-14 17:36:12.000000 ./usr/share/doc-base/htp
│ │ │ │  drwxr-xr-x   0 root         (0) root         (0)        0 2020-06-14 23:21:19.000000 ./usr/share/lintian/
│ │ │ │  drwxr-xr-x   0 root         (0) root         (0)        0 2020-06-14 23:21:19.000000 ./usr/share/lintian/overrides/
│ │ │ ├── ./usr/share/doc/htp/alttext.html
│ │ │ │ @@ -114,15 +114,19 @@
│ │ │ │        <a class="noline" href="bugs.html">Bugs</a></td></tr>
│ │ │ │    </table>
│ │ │ │    </div>
│ │ │ │  </td>
│ │ │ │  <td bgcolor="#f0f0d0" rowspan="2" valign="top">
│ │ │ │  <h2>syntax</h2>
│ │ │ │    <p><code>
│ │ │ │ -<span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">blockdef</a> <span class="htp-attrib">name</span>=<span class="htp-string">"tagname"</span> <span class="ebnf">[</span><span class="htp-attrib">option</span>=<span class="htp-string">"option1 <span class="ebnf">[</span>option2 ...<span class="ebnf">]</span>"</span> <span class="ebnf">]</span> <span class="ebnf">[</span><span class="htp-attrib">global</span><span class="ebnf">]</span> <span class="ebnf">[</span><span class="htp-attrib">expand</span><span class="ebnf">]</span>&gt;</span><br>
│ │ │ │ +<span class="htp-tag">&lt;<a href="block.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">BLOCK</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"blockname"</span> <span class="ebnf">[</span><span class="htp-attrib">GLOBAL</span><span class="ebnf">]</span> <span class="ebnf">[</span><span class="htp-attrib">EXPAND</span><span class="ebnf">]</span>&gt;</span><br>
│ │ │ │ +text block<br>
│ │ │ │ +<span class="htp-tag">&lt;<a href="block.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/BLOCK</a>&gt;</span><br>
│ │ │ │ +<br>
│ │ │ │ +al] [expand]><br>
│ │ │ │  &nbsp; ... <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">block</span>&gt;</span>&nbsp;...<br>
│ │ │ │  <span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/blockdef</a>&gt;</span><br>
│ │ │ │  <br>
│ │ │ │  </code></p>
│ │ │ │  <h2>synopsis</h2>
│ │ │ │  <strong>ALTTEXT</strong> declares an ALT attribute for any <A
│ │ │ │  HREF="img.html">IMG</A> tag with a SRC matching the ALTTEXT NAME.
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,37 +1,40 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : ALTTEXT ******
│ │ │ │ │  Table_of_Contents            ***** syntax *****
│ │ │ │ │ - Introduction               <[[ref]]blockdef name="tagname" [option="option1
│ │ │ │ │ - License                    [option2 ...]" ] [global] [expand]>
│ │ │ │ │ - Tutorial                     ... <[[ref]]use block> ...
│ │ │ │ │ - Usage                      <[[ref]]/blockdef>
│ │ │ │ │ - HTP Tags
│ │ │ │ │ - [>] ALTTEXT                ***** synopsis *****
│ │ │ │ │ -    BLOCK                  ALTTEXT declares an ALT attribute for any IMG tag
│ │ │ │ │ -    BLOCKDEF               with a SRC matching the ALTTEXT NAME. Since
│ │ │ │ │ -    DEF                    relative paths can be used to point to the same
│ │ │ │ │ -    FILE                   image, only the filename is considered in all
│ │ │ │ │ -    IF                     comparisons.
│ │ │ │ │ -    INC                    When an IMG tag with a matching source is
│ │ │ │ │ -    IMG                    encountered, htp will add an ALT attribute only if
│ │ │ │ │ -    IMAGEURL               one is not already present. This allows for ALT
│ │ │ │ │ -    OPT                    text to be overridden on specific images and
│ │ │ │ │ -    OUTPUT                 default text on all others.
│ │ │ │ │ -    QUOTE                  For example:
│ │ │ │ │ -    SET                      <[[ref]]blockdef name="section" option="title">
│ │ │ │ │ -    UNDEF                     <h1><[[ref]]use title></h1>
│ │ │ │ │ -    UNSET                     <p class="section">
│ │ │ │ │ -    USE,_$                      <[[ref]]use block>
│ │ │ │ │ -    WHILE                     </p>
│ │ │ │ │ -    <!---                    <[[ref]]/blockdef>
│ │ │ │ │ - History
│ │ │ │ │ - Wish_list                    <section title="My Section">
│ │ │ │ │ - Bugs                           This is a fancy section.
│ │ │ │ │ + Introduction               <[[ref]]BLOCK NAME="blockname" [GLOBAL] [EXPAND]>
│ │ │ │ │ + License                    text block
│ │ │ │ │ + Tutorial                   <[[ref]]/BLOCK>
│ │ │ │ │ + Usage
│ │ │ │ │ + HTP Tags                   al] [expand]>
│ │ │ │ │ + [>] ALTTEXT                  ... <[[ref]]use block> ...
│ │ │ │ │ +    BLOCK                  <[[ref]]/blockdef>
│ │ │ │ │ +    BLOCKDEF
│ │ │ │ │ +    DEF                    ***** synopsis *****
│ │ │ │ │ +    FILE                   ALTTEXT declares an ALT attribute for any IMG tag
│ │ │ │ │ +    IF                     with a SRC matching the ALTTEXT NAME. Since
│ │ │ │ │ +    INC                    relative paths can be used to point to the same
│ │ │ │ │ +    IMG                    image, only the filename is considered in all
│ │ │ │ │ +    IMAGEURL               comparisons.
│ │ │ │ │ +    OPT                    When an IMG tag with a matching source is
│ │ │ │ │ +    OUTPUT                 encountered, htp will add an ALT attribute only if
│ │ │ │ │ +    QUOTE                  one is not already present. This allows for ALT
│ │ │ │ │ +    SET                    text to be overridden on specific images and
│ │ │ │ │ +    UNDEF                  default text on all others.
│ │ │ │ │ +    UNSET                  For example:
│ │ │ │ │ +    USE,_$                   <[[ref]]blockdef name="section" option="title">
│ │ │ │ │ +    WHILE                     <h1><[[ref]]use title></h1>
│ │ │ │ │ +    <!---                     <p class="section">
│ │ │ │ │ + History                         <[[ref]]use block>
│ │ │ │ │ + Wish_list                     </p>
│ │ │ │ │ + Bugs                         <[[ref]]/blockdef>
│ │ │ │ │ +
│ │ │ │ │ +                               <section title="My Section">
│ │ │ │ │ +                                 This is a fancy section.
│ │ │ │ │                                 </section>
│ │ │ │ │                               An ALTTEXT tag with a name but no text attribute
│ │ │ │ │                               removes any ALT mapping for this image. Successing
│ │ │ │ │                               IMG tags with a matching SRC name are not changed.
│ │ │ │ │                               Since this is useful for an image used throughout
│ │ │ │ │                               a set of documents, ALTTEXT is most appropriate in
│ │ │ │ │                               an include_file or a default_file.
│ │ │ ├── ./usr/share/doc/htp/block.html
│ │ │ │ @@ -114,18 +114,24 @@
│ │ │ │        <a class="noline" href="bugs.html">Bugs</a></td></tr>
│ │ │ │    </table>
│ │ │ │    </div>
│ │ │ │  </td>
│ │ │ │  <td bgcolor="#f0f0d0" rowspan="2" valign="top">
│ │ │ │  <h2>syntax</h2>
│ │ │ │    <p><code>
│ │ │ │ -<span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">blockdef</a> <span class="htp-attrib">name</span>=<span class="htp-string">"tagname"</span> <span class="ebnf">[</span><span class="htp-attrib">option</span>=<span class="htp-string">"option1 <span class="ebnf">[</span>option2 ...<span class="ebnf">]</span>"</span> <span class="ebnf">]</span> <span class="ebnf">[</span><span class="htp-attrib">global</span><span class="ebnf">]</span> <span class="ebnf">[</span><span class="htp-attrib">expand</span><span class="ebnf">]</span>&gt;</span><br>
│ │ │ │ -&nbsp; ... <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">block</span>&gt;</span>&nbsp;...<br>
│ │ │ │ -<span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/blockdef</a>&gt;</span><br>
│ │ │ │ +&nbsp; <span class="htp-tag">&lt;<a href="alttext.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">alttext</a> <span class="htp-attrib">name</span>=<span class="htp-string">"logo.gif"</span> <span class="htp-attrib">text</span>=<span class="htp-string">"Company logo"</span>&gt;</span><br>
│ │ │ │  <br>
│ │ │ │ +&nbsp; this line: <span class="htp-tag">&lt;<a href="img.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">img</a> <span class="htp-attrib">src</span>=<span class="htp-string">"logo.gif"</span>&gt;</span><br>
│ │ │ │ +&nbsp; becomes this after processing: <span class="htp-tag">&lt;<a href="img.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">img</a> <span class="htp-attrib">src</span>=<span class="htp-string">"logo.gif"</span> <span class="htp-attrib">alt</span>=<span class="htp-string">"Company logo"</span>&gt;</span><br>
│ │ │ │ +<br>
│ │ │ │ +&nbsp; this line: <span class="htp-tag">&lt;<a href="img.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">img</a> <span class="htp-attrib">src</span>=<span class="htp-string">"../image/logo.gif"</span>&gt;</span><br>
│ │ │ │ +&nbsp; will also have an ALT attribute appended to it<br>
│ │ │ │ +<br>
│ │ │ │ +&nbsp; this line: <span class="htp-tag">&lt;<a href="img.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">img</a> <span class="htp-attrib">src</span>=<span class="htp-string">"logo.gif"</span> <span class="htp-attrib">alt</span>=<span class="htp-string">"Click here for more information!"</span>&gt;</span><br>
│ │ │ │ +&nbsp; remains unchanged.<br>
│ │ │ │  </code></p>
│ │ │ │  <h2>synopsis</h2>
│ │ │ │  <P>
│ │ │ │  <STRONG>BLOCK and /BLOCK</STRONG> are used to create block macros, which
│ │ │ │  are similar in use to <A HREF="set.html">SET</A> macros, but can be
│ │ │ │  multi-line definitions.
│ │ │ │  </P>
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,32 +1,33 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : BLOCK, /BLOCK ******
│ │ │ │ │ -Table_of_Contents            ***** syntax *****
│ │ │ │ │ - Introduction               <[[ref]]blockdef name="tagname" [option="option1
│ │ │ │ │ - License                    [option2 ...]" ] [global] [expand]>
│ │ │ │ │ - Tutorial                     ... <[[ref]]use block> ...
│ │ │ │ │ - Usage                      <[[ref]]/blockdef>
│ │ │ │ │ +Table_of       ***** syntax *****
│ │ │ │ │ +Contents         <[[ref]]alttext name="logo.gif" text="Company logo">
│ │ │ │ │ + Introduction
│ │ │ │ │ + License        this line: <[[ref]]img src="logo.gif">
│ │ │ │ │ + Tutorial       becomes this after processing: <[[ref]]img src="logo.gif" alt="Company
│ │ │ │ │ + Usage        logo">
│ │ │ │ │   HTP Tags
│ │ │ │ │ -    ALTTEXT                ***** synopsis *****
│ │ │ │ │ - [>] BLOCK                  BLOCK and /BLOCK are used to create block macros,
│ │ │ │ │ -    BLOCKDEF               which are similar in use to SET macros, but can be
│ │ │ │ │ -    DEF                    multi-line definitions.
│ │ │ │ │ -    FILE                   Any text and formatting may be set inside the
│ │ │ │ │ -    IF                     block. You can use any htp or user defined metatag
│ │ │ │ │ -    INC                    including FILE_INCLUDE. The metatags won't be
│ │ │ │ │ -    IMG                    expanded before the block is USEd except if you
│ │ │ │ │ -    IMAGEURL               give the EXPAND parameter.
│ │ │ │ │ -    OPT                    The block macro is dereferenced (expanded) with
│ │ │ │ │ -    OUTPUT                 the USE_tag_or_the_'$'_operator. See the notes on
│ │ │ │ │ -    QUOTE                  the USE tag on how to pass parameters to a block
│ │ │ │ │ -    SET                    macro.
│ │ │ │ │ -    UNDEF
│ │ │ │ │ -    UNSET
│ │ │ │ │ -    USE,_$
│ │ │ │ │ +    ALTTEXT    this line: <[[ref]]img src="../image/logo.gif">
│ │ │ │ │ + [>] BLOCK      will also have an ALT attribute appended to it
│ │ │ │ │ +    BLOCKDEF
│ │ │ │ │ +    DEF        this line: <[[ref]]img src="logo.gif" alt="Click here for more
│ │ │ │ │ +    FILE     information!">
│ │ │ │ │ +    IF         remains unchanged.
│ │ │ │ │ +    INC      ***** synopsis *****
│ │ │ │ │ +    IMG      BLOCK and /BLOCK are used to create block macros, which are similar in
│ │ │ │ │ +    IMAGEURL use to SET macros, but can be multi-line definitions.
│ │ │ │ │ +    OPT      Any text and formatting may be set inside the block. You can use any htp
│ │ │ │ │ +    OUTPUT   or user defined metatag including FILE_INCLUDE. The metatags won't be
│ │ │ │ │ +    QUOTE    expanded before the block is USEd except if you give the EXPAND
│ │ │ │ │ +    SET      parameter.
│ │ │ │ │ +    UNDEF    The block macro is dereferenced (expanded) with the USE_tag_or_the_'$'
│ │ │ │ │ +    UNSET    operator. See the notes on the USE tag on how to pass parameters to a
│ │ │ │ │ +    USE,_$   block macro.
│ │ │ │ │      WHILE
│ │ │ │ │      <!---
│ │ │ │ │   History
│ │ │ │ │   Wish_list
│ │ │ │ │   Bugs
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │ @@ -36,22 +37,26 @@
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │ +
│ │ │ │ │ +
│ │ │ │ │ +
│ │ │ │ │   page_source
│ │ │ │ │   htp_project
│ │ │ │ │   htp_homepage
│ │ │ │ │  hosted by
│ │ │ │ │  Sourceforge
│ │ │ │ │ -HTML coding [Powered_by
│ │ │ │ │ +HTML coding
│ │ │ │ │ +[Powered_by
│ │ │ │ │  htp]
│ │ │ │ │       htp on-line reference / http://htp.sourceforge.net/ref/
│ │ │ │ │       Authors: Jim Nelson, Jochen_Hoenicke, Michael_Möller.
│ │ │ │ │       Maintainers: Jochen_Hoenicke.
│ │ │ │ │  Copyright © 1995–96 Jim Nelson.
│ │ │ │ │  Copyright © 2001–2014 Jochen_Hoenicke.
│ │ │ │ │ -Permission to reproduce and distribute this hypertext document granted
│ │ │ │ │ -according to terms described in the License_section.
│ │ │ │ │ +Permission to reproduce and distribute this hypertext document granted according to
│ │ │ │ │ +terms described in the License_section.
│ │ │ │ │  last updated Sat May 16, 2015
│ │ │ ├── ./usr/share/doc/htp/blockdef.html
│ │ │ │ @@ -114,44 +114,27 @@
│ │ │ │        <a class="noline" href="bugs.html">Bugs</a></td></tr>
│ │ │ │    </table>
│ │ │ │    </div>
│ │ │ │  </td>
│ │ │ │  <td bgcolor="#f0f0d0" rowspan="2" valign="top">
│ │ │ │  <h2>syntax</h2>
│ │ │ │    <p><code>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="alttext.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">alttext</a> <span class="htp-attrib">name</span>=<span class="htp-string">"logo.gif"</span> <span class="htp-attrib">text</span>=<span class="htp-string">"Company logo"</span>&gt;</span><br>
│ │ │ │ +<span class="comment">&lt;!--- comment ---&gt;</span><br>
│ │ │ │  <br>
│ │ │ │ -&nbsp; this line: <span class="htp-tag">&lt;<a href="img.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">img</a> <span class="htp-attrib">src</span>=<span class="htp-string">"logo.gif"</span>&gt;</span><br>
│ │ │ │ -&nbsp; becomes this after processing: <span class="htp-tag">&lt;<a href="img.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">img</a> <span class="htp-attrib">src</span>=<span class="htp-string">"logo.gif"</span> <span class="htp-attrib">alt</span>=<span class="htp-string">"Company logo"</span>&gt;</span><br>
│ │ │ │ -<br>
│ │ │ │ -&nbsp; this line: <span class="htp-tag">&lt;<a href="img.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">img</a> <span class="htp-attrib">src</span>=<span class="htp-string">"../image/logo.gif"</span>&gt;</span><br>
│ │ │ │ -&nbsp; will also have an ALT attribute appended to it<br>
│ │ │ │ -<br>
│ │ │ │ -&nbsp; this line: <span class="htp-tag">&lt;<a href="img.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">img</a> <span class="htp-attrib">src</span>=<span class="htp-string">"logo.gif"</span> <span class="htp-attrib">alt</span>=<span class="htp-string">"Click here for more information!"</span>&gt;</span><br>
│ │ │ │ -&nbsp; remains unchanged.<br>
│ │ │ │  </code></p>
│ │ │ │  <h2>synopsis</h2>
│ │ │ │  <strong>BLOCKDEF</strong> creates block <A
│ │ │ │  HREF="metatag.html">metatags</A>, which is a fancy way of saying it
│ │ │ │  creates new block tags.  A block tag is a tag that takes a whole block
│ │ │ │  as additional parameter.  This block is surrounded by &lt;tagname&gt; and
│ │ │ │  &lt;/tagname&gt;.  The contents of this block are automatically stored
│ │ │ │  in the block macro named BLOCK.
│ │ │ │  <P> For example:</P>
│ │ │ │    <p><code>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">blockdef</a> <span class="htp-attrib">name</span>=<span class="htp-string">"section"</span> <span class="htp-attrib">option</span>=<span class="htp-string">"title"</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp;<span class="htp-tag">&lt;h1&gt;</span><span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">title</span>&gt;</span><span class="htp-tag">&lt;/h1&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp;<span class="htp-tag">&lt;p <span class="htp-attrib">class</span>=<span class="htp-string">"section"</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; &nbsp;<span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">block</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp;<span class="htp-tag">&lt;/p&gt;</span><br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/blockdef</a>&gt;</span><br>
│ │ │ │ -<br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;section <span class="htp-attrib">title</span>=<span class="htp-string">"My Section"</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; This is a fancy section.<br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;/section&gt;</span><br>
│ │ │ │ +<span class="comment">&lt;!---  This comment doesn't appear in the HTML file ---&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <p>
│ │ │ │  All block metatags have the implicit option <a
│ │ │ │  href="expand.html">EXPAND</A>, which tells htp to expand the contents
│ │ │ │  of the block before the definition is expanded.
│ │ │ │  </p>
│ │ │ │  <p>
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,52 +1,37 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : BLOCKDEF, /BLOCKDEF ******
│ │ │ │ │ -Table_of       ***** syntax *****
│ │ │ │ │ -Contents         <[[ref]]alttext name="logo.gif" text="Company logo">
│ │ │ │ │ - Introduction
│ │ │ │ │ - License        this line: <[[ref]]img src="logo.gif">
│ │ │ │ │ - Tutorial       becomes this after processing: <[[ref]]img src="logo.gif" alt="Company
│ │ │ │ │ - Usage        logo">
│ │ │ │ │ - HTP Tags
│ │ │ │ │ -    ALTTEXT    this line: <[[ref]]img src="../image/logo.gif">
│ │ │ │ │ -    BLOCK      will also have an ALT attribute appended to it
│ │ │ │ │ - [>] BLOCKDEF
│ │ │ │ │ -    DEF        this line: <[[ref]]img src="logo.gif" alt="Click here for more
│ │ │ │ │ -    FILE     information!">
│ │ │ │ │ -    IF         remains unchanged.
│ │ │ │ │ -    INC      ***** synopsis *****
│ │ │ │ │ -    IMG      BLOCKDEF creates block metatags, which is a fancy way of saying it
│ │ │ │ │ -    IMAGEURL creates new block tags. A block tag is a tag that takes a whole block as
│ │ │ │ │ -    OPT      additional parameter. This block is surrounded by <tagname> and </
│ │ │ │ │ -    OUTPUT   tagname>. The contents of this block are automatically stored in the
│ │ │ │ │ -    QUOTE    block macro named BLOCK.
│ │ │ │ │ -    SET      For example:
│ │ │ │ │ -    UNDEF      <[[ref]]blockdef name="section" option="title">
│ │ │ │ │ -    UNSET       <h1><[[ref]]use title></h1>
│ │ │ │ │ -    USE,_$      <p class="section">
│ │ │ │ │ -    WHILE         <[[ref]]use block>
│ │ │ │ │ -    <!---       </p>
│ │ │ │ │ - History        <[[ref]]/blockdef>
│ │ │ │ │ +Table_of_Contents            ***** syntax *****
│ │ │ │ │ + Introduction               <!--- comment --->
│ │ │ │ │ + License
│ │ │ │ │ + Tutorial                   ***** synopsis *****
│ │ │ │ │ + Usage                      BLOCKDEF creates block metatags, which is a fancy
│ │ │ │ │ + HTP Tags                   way of saying it creates new block tags. A block
│ │ │ │ │ +    ALTTEXT                tag is a tag that takes a whole block as
│ │ │ │ │ +    BLOCK                  additional parameter. This block is surrounded by
│ │ │ │ │ + [>] BLOCKDEF               <tagname> and </tagname>. The contents of this
│ │ │ │ │ +    DEF                    block are automatically stored in the block macro
│ │ │ │ │ +    FILE                   named BLOCK.
│ │ │ │ │ +    IF                     For example:
│ │ │ │ │ +    INC                    <!--- This comment doesn't appear in the HTML file
│ │ │ │ │ +    IMG                    --->
│ │ │ │ │ +    IMAGEURL               All block metatags have the implicit option
│ │ │ │ │ +    OPT                    EXPAND, which tells htp to expand the contents of
│ │ │ │ │ +    OUTPUT                 the block before the definition is expanded.
│ │ │ │ │ +    QUOTE                  A more thorough discussion and more elaborate
│ │ │ │ │ +    SET                    examples are discussed in the metatag section.
│ │ │ │ │ +    UNDEF
│ │ │ │ │ +    UNSET
│ │ │ │ │ +    USE,_$
│ │ │ │ │ +    WHILE
│ │ │ │ │ +    <!---
│ │ │ │ │ + History
│ │ │ │ │   Wish_list
│ │ │ │ │ - Bugs           <section title="My Section">
│ │ │ │ │ -                   This is a fancy section.
│ │ │ │ │ -                 </section>
│ │ │ │ │ -               All block metatags have the implicit option EXPAND, which tells htp to
│ │ │ │ │ -               expand the contents of the block before the definition is expanded.
│ │ │ │ │ -               A more thorough discussion and more elaborate examples are discussed in
│ │ │ │ │ -               the metatag section.
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │ + Bugs
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │ @@ -56,18 +41,17 @@
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │   page_source
│ │ │ │ │   htp_project
│ │ │ │ │   htp_homepage
│ │ │ │ │  hosted by
│ │ │ │ │  Sourceforge
│ │ │ │ │ -HTML coding
│ │ │ │ │ -[Powered_by
│ │ │ │ │ +HTML coding [Powered_by
│ │ │ │ │  htp]
│ │ │ │ │       htp on-line reference / http://htp.sourceforge.net/ref/
│ │ │ │ │       Authors: Jim Nelson, Jochen_Hoenicke, Michael_Möller.
│ │ │ │ │       Maintainers: Jochen_Hoenicke.
│ │ │ │ │  Copyright © 1995–96 Jim Nelson.
│ │ │ │ │  Copyright © 2001–2014 Jochen_Hoenicke.
│ │ │ │ │ -Permission to reproduce and distribute this hypertext document granted according to
│ │ │ │ │ -terms described in the License_section.
│ │ │ │ │ +Permission to reproduce and distribute this hypertext document granted
│ │ │ │ │ +according to terms described in the License_section.
│ │ │ │ │  last updated Sat May 16, 2015
│ │ │ ├── ./usr/share/doc/htp/comment.html
│ │ │ │ @@ -125,19 +125,21 @@
│ │ │ │  <h2>synopsis</h2>
│ │ │ │  <p>
│ │ │ │  This is a simple comment that is not included in the output.  This is useful
│ │ │ │  when commenting metatags, since the metatags do not appear the output either.
│ │ │ │  Example:
│ │ │ │  </p>
│ │ │ │    <p><code>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="set.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">set</a> <span class="htp-attrib">time</span>=<span class="htp-string">"0"</span>&gt;</span><br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="block.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">block</a> <span class="htp-attrib">name</span>=<span class="htp-value">a</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; a is expanded at time <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">time</span>&gt;</span>.<br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="block.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/block</a>&gt;</span><br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="block.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">block</a> <span class="htp-attrib">name</span>=<span class="htp-value">b</span> <span class="htp-attrib">expand</span>&gt;</span><br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="def.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">def</a> <span class="htp-attrib">name</span>=<span class="htp-string">"centered"</span>&gt;</span><br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;p <span class="htp-attrib">align</span>=<span class="htp-value">center</span>&gt;</span><br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="def.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/def</a>&gt;</span><br>
│ │ │ │ +<br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;centered&gt;</span><br>
│ │ │ │ +&nbsp; &nbsp; This text is centered.<br>
│ │ │ │ +pand><br>
│ │ │ │  &nbsp; &nbsp; b is expanded at time <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">time</span>&gt;</span>.<br>
│ │ │ │  &nbsp; <span class="htp-tag">&lt;<a href="block.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/block</a>&gt;</span><br>
│ │ │ │  &nbsp; <span class="htp-tag">&lt;<a href="set.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">set</a> <span class="htp-attrib">time</span>=<span class="htp-string">"1"</span>&gt;</span><br>
│ │ │ │  &nbsp; <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">a</span>&gt;</span><br>
│ │ │ │  &nbsp; <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">b</span>&gt;</span><br>
│ │ │ │  &nbsp; contents of a: <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">a</span> <span class="htp-attrib">noexpand</span>&gt;</span><br>
│ │ │ │  &nbsp; contents of b: <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">b</span> <span class="htp-attrib">noexpand</span>&gt;</span><br>
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -6,33 +6,35 @@
│ │ │ │ │   Introduction [expand]>
│ │ │ │ │   License      <[[ref]]/def>
│ │ │ │ │   Tutorial
│ │ │ │ │   Usage        ***** synopsis *****
│ │ │ │ │   HTP Tags     This is a simple comment that is not included in the output. This is useful
│ │ │ │ │      ALTTEXT  when commenting metatags, since the metatags do not appear the output
│ │ │ │ │      BLOCK    either. Example:
│ │ │ │ │ -    BLOCKDEF   <[[ref]]set time="0">
│ │ │ │ │ -    DEF        <[[ref]]block name=a>
│ │ │ │ │ -    FILE         a is expanded at time <[[ref]]use time>.
│ │ │ │ │ -    IF         <[[ref]]/block>
│ │ │ │ │ -    INC        <[[ref]]block name=b expand>
│ │ │ │ │ -    IMG          b is expanded at time <[[ref]]use time>.
│ │ │ │ │ -    IMAGEURL   <[[ref]]/block>
│ │ │ │ │ -    OPT        <[[ref]]set time="1">
│ │ │ │ │ -    OUTPUT     <[[ref]]use a>
│ │ │ │ │ -    QUOTE      <[[ref]]use b>
│ │ │ │ │ -    SET        contents of a: <[[ref]]use a noexpand>
│ │ │ │ │ -    UNDEF      contents of b: <[[ref]]use b noexpand>
│ │ │ │ │ -    UNSET      <[[ref]]block name=c expand>
│ │ │ │ │ -    USE,_$       c is expanded at time <[[ref]]use time>; <[[ref]]use a>
│ │ │ │ │ -    WHILE      <[[ref]]/block>
│ │ │ │ │ - [>] <!---      <[[ref]]block name=d expand>
│ │ │ │ │ - History          d is expanded at time <[[ref]]use time>; <[[ref]]use a noexpand>
│ │ │ │ │ - Wish_list      <[[ref]]/block>
│ │ │ │ │ - Bugs           <[[ref]]block name=e>
│ │ │ │ │ +    BLOCKDEF     <[[ref]]def name="centered">
│ │ │ │ │ +    DEF          <p align=center>
│ │ │ │ │ +    FILE         <[[ref]]/def>
│ │ │ │ │ +    IF
│ │ │ │ │ +    INC          <centered>
│ │ │ │ │ +    IMG          This text is centered.
│ │ │ │ │ +    IMAGEURL pand>
│ │ │ │ │ +    OPT          b is expanded at time <[[ref]]use time>.
│ │ │ │ │ +    OUTPUT     <[[ref]]/block>
│ │ │ │ │ +    QUOTE      <[[ref]]set time="1">
│ │ │ │ │ +    SET        <[[ref]]use a>
│ │ │ │ │ +    UNDEF      <[[ref]]use b>
│ │ │ │ │ +    UNSET      contents of a: <[[ref]]use a noexpand>
│ │ │ │ │ +    USE,_$     contents of b: <[[ref]]use b noexpand>
│ │ │ │ │ +    WHILE      <[[ref]]block name=c expand>
│ │ │ │ │ + [>] <!---        c is expanded at time <[[ref]]use time>; <[[ref]]use a>
│ │ │ │ │ + History        <[[ref]]/block>
│ │ │ │ │ + Wish_list      <[[ref]]block name=d expand>
│ │ │ │ │ + Bugs             d is expanded at time <[[ref]]use time>; <[[ref]]use a noexpand>
│ │ │ │ │ +                 <[[ref]]/block>
│ │ │ │ │ +                 <[[ref]]block name=e>
│ │ │ │ │                     e is expanded at time <[[ref]]use time>; <[[ref]]use a noexpand>
│ │ │ │ │                   <[[ref]]/block>
│ │ │ │ │                   <[[ref]]set time="2">
│ │ │ │ │                   <[[ref]]block name=a>
│ │ │ │ │                     a is defined for the 2nd time <[[ref]]use time>.
│ │ │ │ │                   <[[ref]]/block>
│ │ │ │ │                   <[[ref]]use c>
│ │ │ ├── ./usr/share/doc/htp/def.html
│ │ │ │ @@ -114,17 +114,15 @@
│ │ │ │        <a class="noline" href="bugs.html">Bugs</a></td></tr>
│ │ │ │    </table>
│ │ │ │    </div>
│ │ │ │  </td>
│ │ │ │  <td bgcolor="#f0f0d0" rowspan="2" valign="top">
│ │ │ │  <h2>syntax</h2>
│ │ │ │    <p><code>
│ │ │ │ -<span class="htp-tag">&lt;<a href="def.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">def</a> <span class="htp-attrib">name</span>=<span class="htp-string">"tagname"</span> <span class="ebnf">[</span><span class="htp-attrib">option</span>=<span class="htp-string">"option1 <span class="ebnf">[</span>option2 ...<span class="ebnf">]</span>"</span> <span class="ebnf">]</span> <span class="ebnf">[</span><span class="htp-attrib">global</span><span class="ebnf">]</span> <span class="ebnf">[</span><span class="htp-attrib">expand</span><span class="ebnf">]</span>&gt;</span><br>
│ │ │ │ -<span class="htp-tag">&lt;<a href="def.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/def</a>&gt;</span><br>
│ │ │ │ -<br>
│ │ │ │ +<span class="comment">&lt;!---  This comment doesn't appear in the HTML file ---&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <h2>synopsis</h2>
│ │ │ │  <p>
│ │ │ │  <strong>DEF</strong> creates <a href="metatag.html">metatags</a>, which is a
│ │ │ │  fancy way of saying it creates new tags.  The mechanism is very similar to
│ │ │ │  <a href="block.html">BLOCK</a> macros, except that the <a href="use.html">USE</a>
│ │ │ │  tag is not used to expand them.  Instead, they are expanded by their own name.
│ │ │ │ @@ -181,38 +179,16 @@
│ │ │ │  <P>
│ │ │ │  Options can be passed to a metatag, which can then expand as if it were
│ │ │ │  a <A HREF="set.html">SET</A> macro.  Option names are parameterized with
│ │ │ │  the OPTION attribute.  Multiple options can be listed by separating their
│ │ │ │  name with a space (which therefore requires they be surrounded by quotes.)
│ │ │ │  </P>
│ │ │ │    <p><code>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="def.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">DEF</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"HEADERIMG"</span> <span class="htp-attrib">OPTION</span>=<span class="htp-string">"SRC TITLE SIZE"</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="if.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">IF</a> <span class="htp-attrib">size</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; &nbsp; &nbsp; <span class="htp-tag">&lt;FONT <span class="htp-attrib">SIZE</span>=<span class="htp-value"><span class="htp-macro">${size}</span></span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="if.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/IF</a>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="img.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">IMG</a> <span class="htp-attrib">SRC</span>=<span class="htp-value">pics/<span class="htp-macro">${src}</span></span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">USE</a> <span class="htp-attrib">title</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="if.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">IF</a> <span class="htp-attrib">size</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; &nbsp; &nbsp; <span class="htp-tag">&lt;/FONT&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="if.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/IF</a>&gt;</span><br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="def.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/DEF</a>&gt;</span><br>
│ │ │ │ -<br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;HEADERIMG <span class="htp-attrib">SRC</span>=<span class="htp-string">"logo.gif"</span> <span class="htp-attrib">SIZE</span>=<span class="htp-string">"+2"</span> <span class="htp-attrib">TITLE</span>=<span class="htp-string">"A title"</span>&gt;</span><br>
│ │ │ │ -<br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;HEADERIMG <span class="htp-attrib">SRC</span>=<span class="htp-string">"logo.gif"</span> <span class="htp-attrib">TITLE</span>=<span class="htp-string">"Normal sized title"</span>&gt;</span><br>
│ │ │ │ -<br>
│ │ │ │ -&nbsp; This will fail:<br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;HEADERIMG <span class="htp-attrib">SRC</span>=<span class="htp-string">"logo.gif"</span> <span class="htp-attrib">ALT</span>=<span class="htp-string">"Our logo"</span> <span class="htp-attrib">TITLE</span>=<span class="htp-string">"Another title"</span>&gt;</span><br>
│ │ │ │ -<br>
│ │ │ │ -&nbsp; Instead, use * like this:<br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="def.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">DEF</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"MYIMG"</span> <span class="htp-attrib">OPTION</span>=<span class="htp-string">"SRC *"</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="img.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">IMG</a> <span class="htp-attrib">SRC</span>=<span class="htp-string">"pics/<span class="htp-macro">${src}</span>"</span> <span class="htp-attrib"><span class="htp-macro">$*</span></span>&gt;</span><br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="def.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/DEF</a>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;MYIMG <span class="htp-attrib">SRC</span>=<span class="htp-string">"logo.gif"</span> <span class="htp-attrib">ALT</span>=<span class="htp-string">"Our logo"</span>&gt;</span><br>
│ │ │ │ +&nbsp; &nbsp; File image.gif <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"image.gif"</span> <span class="htp-attrib">SIZE</span>=<span class="htp-value">KBYTE</span>&gt;</span>&nbsp;kilobytes<br>
│ │ │ │ +&nbsp; &nbsp; Last modified <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"image.gif"</span> <span class="htp-attrib">TIME</span>&gt;</span>, <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"image.gif"</span> <span class="htp-attrib">DATE</span>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <P>
│ │ │ │  htp will do very specific checking of parameters when a metatag is
│ │ │ │  invoked.  htp assumes that all parameter options to the metatag are
│ │ │ │  optional.  This is why the HEADERIMG definition uses IF to verify the
│ │ │ │  SIZE option is defined before expanding it in the block.  If a
│ │ │ │  parameter is required, simply expand it without first checking.  When
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,41 +1,38 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : DEF, /DEF ******
│ │ │ │ │  Table_of       ***** syntax *****
│ │ │ │ │ -Contents       <[[ref]]def name="tagname" [option="option1 [option2 ...]" ] [global]
│ │ │ │ │ - Introduction [expand]>
│ │ │ │ │ - License      <[[ref]]/def>
│ │ │ │ │ - Tutorial
│ │ │ │ │ - Usage        ***** synopsis *****
│ │ │ │ │ - HTP Tags     DEF creates metatags, which is a fancy way of saying it creates new tags.
│ │ │ │ │ -    ALTTEXT  The mechanism is very similar to BLOCK macros, except that the USE tag is
│ │ │ │ │ -    BLOCK    not used to expand them. Instead, they are expanded by their own name. For
│ │ │ │ │ -    BLOCKDEF example:
│ │ │ │ │ - [>] DEF        <[[ref]]set time="0">
│ │ │ │ │ -    FILE       <[[ref]]block name=a>
│ │ │ │ │ -    IF           a is expanded at time <[[ref]]use time>.
│ │ │ │ │ +Contents       <!--- This comment doesn't appear in the HTML file --->
│ │ │ │ │ + Introduction ***** synopsis *****
│ │ │ │ │ + License      DEF creates metatags, which is a fancy way of saying it creates new tags.
│ │ │ │ │ + Tutorial     The mechanism is very similar to BLOCK macros, except that the USE tag is
│ │ │ │ │ + Usage        not used to expand them. Instead, they are expanded by their own name. For
│ │ │ │ │ + HTP Tags     example:
│ │ │ │ │ +    ALTTEXT    <[[ref]]set time="0">
│ │ │ │ │ +    BLOCK      <[[ref]]block name=a>
│ │ │ │ │ +    BLOCKDEF     a is expanded at time <[[ref]]use time>.
│ │ │ │ │ + [>] DEF        <[[ref]]/block>
│ │ │ │ │ +    FILE       <[[ref]]block name=b expand>
│ │ │ │ │ +    IF           b is expanded at time <[[ref]]use time>.
│ │ │ │ │      INC        <[[ref]]/block>
│ │ │ │ │ -    IMG        <[[ref]]block name=b expand>
│ │ │ │ │ -    IMAGEURL     b is expanded at time <[[ref]]use time>.
│ │ │ │ │ -    OPT        <[[ref]]/block>
│ │ │ │ │ -    OUTPUT     <[[ref]]set time="1">
│ │ │ │ │ -    QUOTE      <[[ref]]use a>
│ │ │ │ │ -    SET        <[[ref]]use b>
│ │ │ │ │ -    UNDEF      contents of a: <[[ref]]use a noexpand>
│ │ │ │ │ -    UNSET      contents of b: <[[ref]]use b noexpand>
│ │ │ │ │ -    USE,_$     <[[ref]]block name=c expand>
│ │ │ │ │ -    WHILE        c is expanded at time <[[ref]]use time>; <[[ref]]use a>
│ │ │ │ │ +    IMG        <[[ref]]set time="1">
│ │ │ │ │ +    IMAGEURL   <[[ref]]use a>
│ │ │ │ │ +    OPT        <[[ref]]use b>
│ │ │ │ │ +    OUTPUT     contents of a: <[[ref]]use a noexpand>
│ │ │ │ │ +    QUOTE      contents of b: <[[ref]]use b noexpand>
│ │ │ │ │ +    SET        <[[ref]]block name=c expand>
│ │ │ │ │ +    UNDEF        c is expanded at time <[[ref]]use time>; <[[ref]]use a>
│ │ │ │ │ +    UNSET      <[[ref]]/block>
│ │ │ │ │ +    USE,_$     <[[ref]]block name=d expand>
│ │ │ │ │ +    WHILE        d is expanded at time <[[ref]]use time>; <[[ref]]use a noexpand>
│ │ │ │ │      <!---      <[[ref]]/block>
│ │ │ │ │ - History        <[[ref]]block name=d expand>
│ │ │ │ │ - Wish_list        d is expanded at time <[[ref]]use time>; <[[ref]]use a noexpand>
│ │ │ │ │ + History        <[[ref]]block name=e>
│ │ │ │ │ + Wish_list        e is expanded at time <[[ref]]use time>; <[[ref]]use a noexpand>
│ │ │ │ │   Bugs           <[[ref]]/block>
│ │ │ │ │ -                 <[[ref]]block name=e>
│ │ │ │ │ -                   e is expanded at time <[[ref]]use time>; <[[ref]]use a noexpand>
│ │ │ │ │ -                 <[[ref]]/block>
│ │ │ │ │                   <[[ref]]set time="2">
│ │ │ │ │                   <[[ref]]block name=a>
│ │ │ │ │                     a is defined for the 2nd time <[[ref]]use time>.
│ │ │ │ │                   <[[ref]]/block>
│ │ │ │ │                   <[[ref]]use c>
│ │ │ │ │                   <[[ref]]use d>
│ │ │ │ │                   <[[ref]]use e>
│ │ │ │ │ @@ -54,38 +51,17 @@
│ │ │ │ │                 time>.
│ │ │ │ │                 You should really use BLOCKDEF, though, as it will check for matching end
│ │ │ │ │                 tag. It is not that slower.
│ │ │ │ │                 Options can be passed to a metatag, which can then expand as if it were a
│ │ │ │ │                 SET macro. Option names are parameterized with the OPTION attribute.
│ │ │ │ │                 Multiple options can be listed by separating their name with a space (which
│ │ │ │ │                 therefore requires they be surrounded by quotes.)
│ │ │ │ │ -                 <[[ref]]DEF NAME="HEADERIMG" OPTION="SRC TITLE SIZE">
│ │ │ │ │ -                   <[[ref]]IF size>
│ │ │ │ │ -                       <FONT SIZE=${size}>
│ │ │ │ │ -                   <[[ref]]/IF>
│ │ │ │ │ -                   <[[ref]]IMG SRC=pics/${src}>
│ │ │ │ │ -                   <[[ref]]USE title>
│ │ │ │ │ -                   <[[ref]]IF size>
│ │ │ │ │ -                       </FONT>
│ │ │ │ │ -                   <[[ref]]/IF>
│ │ │ │ │ -                 <[[ref]]/DEF>
│ │ │ │ │ -
│ │ │ │ │ -                 <HEADERIMG SRC="logo.gif" SIZE="+2" TITLE="A title">
│ │ │ │ │ -
│ │ │ │ │ -                 <HEADERIMG SRC="logo.gif" TITLE="Normal sized title">
│ │ │ │ │ -
│ │ │ │ │ -                 This will fail:
│ │ │ │ │ -                 <HEADERIMG SRC="logo.gif" ALT="Our logo" TITLE="Another title">
│ │ │ │ │ -
│ │ │ │ │ -                 Instead, use * like this:
│ │ │ │ │ -                 <[[ref]]DEF NAME="MYIMG" OPTION="SRC *">
│ │ │ │ │ -                   <[[ref]]IMG SRC="pics/${src}" $*>
│ │ │ │ │ -                 <[[ref]]/DEF>
│ │ │ │ │ -                  
│ │ │ │ │ -                 <MYIMG SRC="logo.gif" ALT="Our logo">
│ │ │ │ │ +                   File image.gif <[[ref]]FILE NAME="image.gif" SIZE=KBYTE> kilobytes
│ │ │ │ │ +                   Last modified <[[ref]]FILE NAME="image.gif" TIME>, <[[ref]]FILE
│ │ │ │ │ +               NAME="image.gif" DATE>
│ │ │ │ │                 htp will do very specific checking of parameters when a metatag is invoked.
│ │ │ │ │                 htp assumes that all parameter options to the metatag are optional. This is
│ │ │ │ │                 why the HEADERIMG definition uses IF to verify the SIZE option is defined
│ │ │ │ │                 before expanding it in the block. If a parameter is required, simply expand
│ │ │ │ │                 it without first checking. When htp expands the metatag and the macro is
│ │ │ │ │                 not defined, it will halt processing and complain with an error message and
│ │ │ │ │                 the required macro name. Normally htp will not allow parameters not listed
│ │ │ ├── ./usr/share/doc/htp/file.html
│ │ │ │ @@ -114,44 +114,50 @@
│ │ │ │        <a class="noline" href="bugs.html">Bugs</a></td></tr>
│ │ │ │    </table>
│ │ │ │    </div>
│ │ │ │  </td>
│ │ │ │  <td bgcolor="#f0f0d0" rowspan="2" valign="top">
│ │ │ │  <h2>syntax</h2>
│ │ │ │    <p><code>
│ │ │ │ -<span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="htp-attrib">execute</span>=<span class="htp-string">"command-line"</span> <span class="ebnf">(</span><span class="htp-attrib">output</span>=<span class="htp-string">"filename"</span> <span class="ebnf">|</span> <span class="htp-attrib">redirect</span><span class="ebnf">)</span> <span class="ebnf">[</span><span class="htp-attrib">noerror</span><span class="ebnf">]</span>&gt;</span><br>
│ │ │ │ -<span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="htp-attrib">include</span>=<span class="htp-string">"includefilename"</span> <span class="ebnf">[</span><span class="htp-attrib">parameters</span> <span class="htp-attrib">...</span><span class="ebnf">]</span>&gt;</span><br>
│ │ │ │ -<span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="htp-attrib">name</span>&gt;</span><br>
│ │ │ │ -<span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="ebnf">[</span> <span class="htp-attrib">name</span>=<span class="htp-string">"filename"</span> <span class="ebnf">]</span> <span class="htp-attrib">size</span><span class="ebnf">[</span> =<span class="htp-value"></span> <span class="ebnf">(</span><span class="htp-attrib">byte</span><span class="ebnf">|</span><span class="htp-attrib">kbyte</span><span class="ebnf">|</span><span class="htp-attrib">mbyte</span><span class="ebnf">|</span><span class="htp-attrib">gbyte</span><span class="ebnf">)</span> <span class="ebnf">]</span> <span class="ebnf">[</span><span class="htp-attrib">precision</span>=<span class="htp-value">n<span class="ebnf">]</span></span>&gt;</span><br>
│ │ │ │ -<span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="ebnf">[</span> <span class="htp-attrib">name</span>=<span class="htp-string">"filename"</span> <span class="ebnf">]</span> <span class="htp-attrib">time</span><span class="ebnf">[</span> =<span class="htp-string">"format"</span> <span class="ebnf">]</span>&gt;</span><br>
│ │ │ │ -<span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="ebnf">[</span> <span class="htp-attrib">name</span>=<span class="htp-string">"filename"</span> <span class="ebnf">]</span> <span class="htp-attrib">date</span><span class="ebnf">[</span> =<span class="htp-string">"format"</span> <span class="ebnf">]</span>&gt;</span><br>
│ │ │ │ -<span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="htp-attrib">search</span>=<span class="htp-string">"searchpath"</span>&gt;</span><br>
│ │ │ │ -<span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="htp-attrib">template</span>=<span class="htp-string">"templatefilename"</span>&gt;</span><br>
│ │ │ │ +&nbsp; &nbsp; a is expanded at time 1.<br>
│ │ │ │ +&nbsp; &nbsp; b is expanded at time 0.<br>
│ │ │ │ +&nbsp; contents of a: &nbsp; a is expanded at time <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">time</span>&gt;</span>.<br>
│ │ │ │ +&nbsp; contents of b: &nbsp; b is expanded at time 0.<br>
│ │ │ │ +&nbsp; &nbsp; c is expanded at time 1; &nbsp; a is expanded at time 1.<br>
│ │ │ │ +&nbsp; &nbsp; d is expanded at time 1; &nbsp; a is expanded at time 2.<br>
│ │ │ │ +&nbsp; &nbsp; e is expanded at time 2; &nbsp; a is defined for the 2nd time <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">time</span>&gt;</span>.<br>
│ │ │ │ +="logo.gif" ALT="Our logo" TITLE="Another title"><br>
│ │ │ │  <br>
│ │ │ │ +&nbsp; Instead, use * like this:<br>
│ │ │ │ +&nbsp; <span class="htp-tag">&lt;<a href="def.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">DEF</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"MYIMG"</span> <span class="htp-attrib">OPTION</span>=<span class="htp-string">"SRC *"</span>&gt;</span><br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="img.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">IMG</a> <span class="htp-attrib">SRC</span>=<span class="htp-string">"pics/<span class="htp-macro">${src}</span>"</span> <span class="htp-attrib"><span class="htp-macro">$*</span></span>&gt;</span><br>
│ │ │ │ +&nbsp; <span class="htp-tag">&lt;<a href="def.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/DEF</a>&gt;</span><br>
│ │ │ │ +&nbsp; &nbsp; <br>
│ │ │ │ +&nbsp; <span class="htp-tag">&lt;MYIMG <span class="htp-attrib">SRC</span>=<span class="htp-string">"logo.gif"</span> <span class="htp-attrib">ALT</span>=<span class="htp-string">"Our logo"</span>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <h2>synopsis</h2>
│ │ │ │  <STRONG>FILE</STRONG> has several optional parameters of differing purpose.
│ │ │ │  The output file's name, the current date and time, and the contents of
│ │ │ │  another file may be included.  Another file's time, date, or size may be
│ │ │ │  added to the output file as well.
│ │ │ │  <P>
│ │ │ │  As with all HTML, these tags do not have to be on their own line, so the
│ │ │ │  following is perfectly acceptable:
│ │ │ │    <p><code>
│ │ │ │ -<span class="htp-tag">&lt;<a href="img.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">img</a> <span class="htp-attrib">src</span>=<span class="htp-string">"filename"</span> <span class="htp-attrib">...</span>&gt;</span><br>
│ │ │ │ -<br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;EM&gt;</span>File "<span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">NAME</span>&gt;</span>" last updated <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">TIME</span>&gt;</span>, <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">DATE</span>&gt;</span><span class="htp-tag">&lt;/EM&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <P>
│ │ │ │  <h3><a name="name">NAME</a>, TIME, SIZE</h3>
│ │ │ │  <P>
│ │ │ │  To include information about another file, such as an archive file or
│ │ │ │  graphic image, specify its name with the NAME attribute followed by the
│ │ │ │  type of information to be displayed:
│ │ │ │    <p><code>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="if.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">IF</a> <span class="htp-attrib">name</span>=<span class="htp-string">"Jim"</span>&gt;</span>...<span class="htp-tag">&lt;<a href="if.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/IF</a>&gt;</span><br>
│ │ │ │ +&nbsp; &nbsp; File image.gif <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"image.gif"</span> <span class="htp-attrib">SIZE</span>=<span class="htp-value">KBYTE</span>&gt;</span>&nbsp;kilobytes<br>
│ │ │ │ +&nbsp; &nbsp; Last modified <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"image.gif"</span> <span class="htp-attrib">TIME</span>&gt;</span>, <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"image.gif"</span> <span class="htp-attrib">DATE</span>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <P>
│ │ │ │  For file size information, the value BYTE, KBYTE, etc. dictates how the
│ │ │ │  information is displayed.  In anything other than byte format, the information
│ │ │ │  is displayed in floating-point notation.  The amount of precision (the number
│ │ │ │  of digits to the right of the decimal point) can be set with the optional
│ │ │ │  PRECISION attribute.  The default precision is zero (0), which means no
│ │ │ │ @@ -180,15 +186,15 @@
│ │ │ │  <P>
│ │ │ │  Additional parameters can be set in the FILE INCLUDE tag, which are
│ │ │ │  interpreted as macros that are "passed" to the included file.  The macros
│ │ │ │  are available only to the include file (and any macros or included files it
│ │ │ │  holds).  After the file is completely included, the macros are no longer
│ │ │ │  available.  So:
│ │ │ │    <p><code>
│ │ │ │ -<span class="htp-tag">&lt;<a href="imageurl.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">imageurl</a> <span class="htp-attrib">url</span>=<span class="htp-string">"imageurl"</span> <span class="htp-attrib">[</span> <span class="htp-attrib">path</span>=<span class="htp-string">"path/in/local/filesystem"</span> <span class="htp-attrib">]</span>&gt;</span><br>
│ │ │ │ +<span class="htp-tag">&lt;<a href="img.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">img</a> <span class="htp-attrib">src</span>=<span class="htp-string">"filename"</span> <span class="htp-attrib">...</span>&gt;</span><br>
│ │ │ │  <br>
│ │ │ │  </code></p>
│ │ │ │  <P>
│ │ │ │  Macros named "name" and "email" are set, and available inside the included
│ │ │ │  file.  They are not available, however, past the tag (which is why the
│ │ │ │  second statement will fail.)
│ │ │ │  <P>
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,141 +1,112 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : FILE ******
│ │ │ │ │ -Table_of_Contents            ***** syntax *****
│ │ │ │ │ - Introduction               <[[ref]]file execute="command-line"
│ │ │ │ │ - License                    (output="filename" | redirect) [noerror]>
│ │ │ │ │ - Tutorial                   <[[ref]]file include="includefilename" [parameters
│ │ │ │ │ - Usage                      ...]>
│ │ │ │ │ - HTP Tags                   <[[ref]]file name>
│ │ │ │ │ -    ALTTEXT                <[[ref]]file [ name="filename" ] size[ =
│ │ │ │ │ -    BLOCK                  (byte|kbyte|mbyte|gbyte) ] [precision=n]>
│ │ │ │ │ -    BLOCKDEF               <[[ref]]file [ name="filename" ] time[ ="format"
│ │ │ │ │ -    DEF                    ]>
│ │ │ │ │ - [>] FILE                   <[[ref]]file [ name="filename" ] date[ ="format"
│ │ │ │ │ -    IF                     ]>
│ │ │ │ │ -    INC                    <[[ref]]file search="searchpath">
│ │ │ │ │ -    IMG                    <[[ref]]file template="templatefilename">
│ │ │ │ │ -    IMAGEURL
│ │ │ │ │ -    OPT                    ***** synopsis *****
│ │ │ │ │ -    OUTPUT                 FILE has several optional parameters of differing
│ │ │ │ │ -    QUOTE                  purpose. The output file's name, the current date
│ │ │ │ │ -    SET                    and time, and the contents of another file may be
│ │ │ │ │ -    UNDEF                  included. Another file's time, date, or size may
│ │ │ │ │ -    UNSET                  be added to the output file as well.
│ │ │ │ │ -    USE,_$                 As with all HTML, these tags do not have to be on
│ │ │ │ │ -    WHILE                  their own line, so the following is perfectly
│ │ │ │ │ -    <!---                  acceptable:
│ │ │ │ │ - History                    <[[ref]]img src="filename" ...>
│ │ │ │ │ - Wish_list
│ │ │ │ │ - Bugs                       **** NAME, TIME, SIZE ****
│ │ │ │ │ -                             To include information about another file, such as
│ │ │ │ │ -                             an archive file or graphic image, specify its name
│ │ │ │ │ -                             with the NAME attribute followed by the type of
│ │ │ │ │ -                             information to be displayed:
│ │ │ │ │ -                                 <[[ref]]IF name="Jim">...<[[ref]]/IF>
│ │ │ │ │ -                             For file size information, the value BYTE, KBYTE,
│ │ │ │ │ -                             etc. dictates how the information is displayed. In
│ │ │ │ │ -                             anything other than byte format, the information
│ │ │ │ │ -                             is displayed in floating-point notation. The
│ │ │ │ │ -                             amount of precision (the number of digits to the
│ │ │ │ │ -                             right of the decimal point) can be set with the
│ │ │ │ │ -                             optional PRECISION attribute. The default
│ │ │ │ │ -                             precision is zero (0), which means no fractional
│ │ │ │ │ -                             portion is displayed.
│ │ │ │ │ -                             At the request of many people, the TIME and DATE
│ │ │ │ │ -                             attributes will now accept formatting characters
│ │ │ │ │ -                             that are passed directly into the ANSI C library
│ │ │ │ │ -                             function. This allows for the time and date to be
│ │ │ │ │ -                             displayed in virtually any format. Users not
│ │ │ │ │ -                             wishing to mess around with this should stick to
│ │ │ │ │ -                             the default format, which is used if no formatting
│ │ │ │ │ -                             value is specified (i.e., just using 05:04:11 PM).
│ │ │ │ │ -                             Consult any C programmer's guide discussing the
│ │ │ │ │ -                             standard C library function strftime() for
│ │ │ │ │ -                             information on how to build a format string. If
│ │ │ │ │ -                             unsure, ask an experienced C programmer for help,
│ │ │ │ │ -                             or consider just sticking to the default
│ │ │ │ │ -                             formatting.
│ │ │ │ │ -                             **** INCLUDE ****
│ │ │ │ │ -                             INCLUDE files are pre-processed as any other file.
│ │ │ │ │ -                             The resulting text is incorporated into the HTML
│ │ │ │ │ -                             output as if the file had been copied into the
│ │ │ │ │ -                             source at the same location as the FILE markup
│ │ │ │ │ -                             tag.
│ │ │ │ │ -                             htp will automatically convert slashes and
│ │ │ │ │ -                             backslashes to match the operating system's
│ │ │ │ │ -                             directory separator.
│ │ │ │ │ -                             Additional parameters can be set in the FILE
│ │ │ │ │ -                             INCLUDE tag, which are interpreted as macros that
│ │ │ │ │ -                             are "passed" to the included file. The macros are
│ │ │ │ │ -                             available only to the include file (and any macros
│ │ │ │ │ -                             or included files it holds). After the file is
│ │ │ │ │ -                             completely included, the macros are no longer
│ │ │ │ │ -                             available. So:
│ │ │ │ │ -                             <[[ref]]imageurl url="imageurl" [ path="path/in/
│ │ │ │ │ -                             local/filesystem" ]>
│ │ │ │ │ -
│ │ │ │ │ -                             Macros named "name" and "email" are set, and
│ │ │ │ │ -                             available inside the included file. They are not
│ │ │ │ │ -                             available, however, past the tag (which is why the
│ │ │ │ │ -                             second statement will fail.)
│ │ │ │ │ -                             **** TEMPLATE ****
│ │ │ │ │ -                             A template file is nothing more than a default
│ │ │ │ │ -                             include file, one that is included once the input
│ │ │ │ │ -                             text has been completely processed. So, an input
│ │ │ │ │ -                             file can define many "standard" macros, which are
│ │ │ │ │ -                             then expanded by a template file to form a
│ │ │ │ │ -                             consistent page layout.
│ │ │ │ │ -                             The template file can be set many times, but only
│ │ │ │ │ -                             the last filename specified will be processed by
│ │ │ │ │ -                             htp. If multiple template files need to be
│ │ │ │ │ -                             included, specify one template file, and from that
│ │ │ │ │ -                             file use FILE INCLUDE to branch off.
│ │ │ │ │ -                             Template files are most useful when placed inside
│ │ │ │ │ -                             an htp default_file.
│ │ │ │ │ -                             **** SEARCH ****
│ │ │ │ │ -                             A search path can be specified, which is searched
│ │ │ │ │ -                             if an include file cannot be found. This is handy
│ │ │ │ │ -                             to keep a set of "common" include files that many
│ │ │ │ │ -                             documents in many directories may need to access.
│ │ │ │ │ -                             More than one directory can be specified in the
│ │ │ │ │ -                             search path, if they are separated by a semi-
│ │ │ │ │ -                             colon. Spaces should not precede or trail the
│ │ │ │ │ -                             search path string.
│ │ │ │ │ -                             When htp starts, the search path is clear. FILE
│ │ │ │ │ -                             SEARCH would be a handy command to use in an htp
│ │ │ │ │ -                             defaults_file.
│ │ │ │ │ -                             **** EXECUTE ****
│ │ │ │ │ -                             When FILE EXECUTE is used, htp will launch a
│ │ │ │ │ -                             program (as specified by the EXECUTE attribute)
│ │ │ │ │ -                             and include its output as if a FILE INCLUDE was
│ │ │ │ │ -                             performed on the file. Either the OUTPUT or
│ │ │ │ │ -                             REDIRECT attribute must also be included.
│ │ │ │ │ -                             OUTPUT specifies the file the command will
│ │ │ │ │ -                             produce. This is used if the program is either
│ │ │ │ │ -                             hard-coded to produce output to a particular file,
│ │ │ │ │ -                             or relies on one of its command-line arguments to
│ │ │ │ │ -                             determine where to place the output. The output
│ │ │ │ │ -                             file is deleted after its results have been
│ │ │ │ │ -                             imported into the output file.
│ │ │ │ │ -                             If the program produces output straight to
│ │ │ │ │ -                             standard output (as most UNIX and some DOS
│ │ │ │ │ -                             programs do), then the REDIRECT attribute can be
│ │ │ │ │ -                             used. In this case htp will take care of the
│ │ │ │ │ -                             redirection. Depending on the OS features it will
│ │ │ │ │ -                             either append a '>' and the name of a temporary
│ │ │ │ │ -                             file or it will use pipe mechanism to directly
│ │ │ │ │ -                             redirect without temporary files.
│ │ │ │ │ -                             htp will halt processing with an error if the
│ │ │ │ │ -                             executable exits with an error code of anything
│ │ │ │ │ -                             but zero (0). Some programs, however, do not
│ │ │ │ │ -                             specify an error code when exiting, so the exit
│ │ │ │ │ -                             code is undetermined. If htp should ignore the
│ │ │ │ │ -                             error code, specify the NOERROR attribute.
│ │ │ │ │ +Table_of       ***** syntax *****
│ │ │ │ │ +Contents           a is expanded at time 1.
│ │ │ │ │ + Introduction     b is expanded at time 0.
│ │ │ │ │ + License        contents of a:   a is expanded at time <[[ref]]use time>.
│ │ │ │ │ + Tutorial       contents of b:   b is expanded at time 0.
│ │ │ │ │ + Usage            c is expanded at time 1;   a is expanded at time 1.
│ │ │ │ │ + HTP Tags         d is expanded at time 1;   a is expanded at time 2.
│ │ │ │ │ +    ALTTEXT      e is expanded at time 2;   a is defined for the 2nd time <[[ref]]use
│ │ │ │ │ +    BLOCK    time>.
│ │ │ │ │ +    BLOCKDEF ="logo.gif" ALT="Our logo" TITLE="Another title">
│ │ │ │ │ +    DEF
│ │ │ │ │ + [>] FILE       Instead, use * like this:
│ │ │ │ │ +    IF         <[[ref]]DEF NAME="MYIMG" OPTION="SRC *">
│ │ │ │ │ +    INC          <[[ref]]IMG SRC="pics/${src}" $*>
│ │ │ │ │ +    IMG        <[[ref]]/DEF>
│ │ │ │ │ +    IMAGEURL    
│ │ │ │ │ +    OPT        <MYIMG SRC="logo.gif" ALT="Our logo">
│ │ │ │ │ +    OUTPUT   ***** synopsis *****
│ │ │ │ │ +    QUOTE    FILE has several optional parameters of differing purpose. The output
│ │ │ │ │ +    SET      file's name, the current date and time, and the contents of another file
│ │ │ │ │ +    UNDEF    may be included. Another file's time, date, or size may be added to the
│ │ │ │ │ +    UNSET    output file as well.
│ │ │ │ │ +    USE,_$   As with all HTML, these tags do not have to be on their own line, so the
│ │ │ │ │ +    WHILE    following is perfectly acceptable:
│ │ │ │ │ +    <!---        <EM>File "<[[ref]]FILE NAME>" last updated <[[ref]]FILE TIME>, <[
│ │ │ │ │ + History      [ref]]FILE DATE></EM>
│ │ │ │ │ + Wish_list    **** NAME, TIME, SIZE ****
│ │ │ │ │ + Bugs         To include information about another file, such as an archive file or
│ │ │ │ │ +               graphic image, specify its name with the NAME attribute followed by the
│ │ │ │ │ +               type of information to be displayed:
│ │ │ │ │ +                   File image.gif <[[ref]]FILE NAME="image.gif" SIZE=KBYTE> kilobytes
│ │ │ │ │ +                   Last modified <[[ref]]FILE NAME="image.gif" TIME>, <[[ref]]FILE
│ │ │ │ │ +               NAME="image.gif" DATE>
│ │ │ │ │ +               For file size information, the value BYTE, KBYTE, etc. dictates how the
│ │ │ │ │ +               information is displayed. In anything other than byte format, the
│ │ │ │ │ +               information is displayed in floating-point notation. The amount of
│ │ │ │ │ +               precision (the number of digits to the right of the decimal point) can be
│ │ │ │ │ +               set with the optional PRECISION attribute. The default precision is zero
│ │ │ │ │ +               (0), which means no fractional portion is displayed.
│ │ │ │ │ +               At the request of many people, the TIME and DATE attributes will now accept
│ │ │ │ │ +               formatting characters that are passed directly into the ANSI C library
│ │ │ │ │ +               function. This allows for the time and date to be displayed in virtually
│ │ │ │ │ +               any format. Users not wishing to mess around with this should stick to the
│ │ │ │ │ +               default format, which is used if no formatting value is specified (i.e.,
│ │ │ │ │ +               just using 05:04:11 PM).
│ │ │ │ │ +               Consult any C programmer's guide discussing the standard C library function
│ │ │ │ │ +               strftime() for information on how to build a format string. If unsure, ask
│ │ │ │ │ +               an experienced C programmer for help, or consider just sticking to the
│ │ │ │ │ +               default formatting.
│ │ │ │ │ +               **** INCLUDE ****
│ │ │ │ │ +               INCLUDE files are pre-processed as any other file. The resulting text is
│ │ │ │ │ +               incorporated into the HTML output as if the file had been copied into the
│ │ │ │ │ +               source at the same location as the FILE markup tag.
│ │ │ │ │ +               htp will automatically convert slashes and backslashes to match the
│ │ │ │ │ +               operating system's directory separator.
│ │ │ │ │ +               Additional parameters can be set in the FILE INCLUDE tag, which are
│ │ │ │ │ +               interpreted as macros that are "passed" to the included file. The macros
│ │ │ │ │ +               are available only to the include file (and any macros or included files it
│ │ │ │ │ +               holds). After the file is completely included, the macros are no longer
│ │ │ │ │ +               available. So:
│ │ │ │ │ +               <[[ref]]img src="filename" ...>
│ │ │ │ │ +
│ │ │ │ │ +               Macros named "name" and "email" are set, and available inside the included
│ │ │ │ │ +               file. They are not available, however, past the tag (which is why the
│ │ │ │ │ +               second statement will fail.)
│ │ │ │ │ +               **** TEMPLATE ****
│ │ │ │ │ +               A template file is nothing more than a default include file, one that is
│ │ │ │ │ +               included once the input text has been completely processed. So, an input
│ │ │ │ │ +               file can define many "standard" macros, which are then expanded by a
│ │ │ │ │ +               template file to form a consistent page layout.
│ │ │ │ │ +               The template file can be set many times, but only the last filename
│ │ │ │ │ +               specified will be processed by htp. If multiple template files need to be
│ │ │ │ │ +               included, specify one template file, and from that file use FILE INCLUDE to
│ │ │ │ │ +               branch off.
│ │ │ │ │ +               Template files are most useful when placed inside an htp default_file.
│ │ │ │ │ +               **** SEARCH ****
│ │ │ │ │ +               A search path can be specified, which is searched if an include file cannot
│ │ │ │ │ +               be found. This is handy to keep a set of "common" include files that many
│ │ │ │ │ +               documents in many directories may need to access. More than one directory
│ │ │ │ │ +               can be specified in the search path, if they are separated by a semi-colon.
│ │ │ │ │ +               Spaces should not precede or trail the search path string.
│ │ │ │ │ +               When htp starts, the search path is clear. FILE SEARCH would be a handy
│ │ │ │ │ +               command to use in an htp_defaults_file.
│ │ │ │ │ +               **** EXECUTE ****
│ │ │ │ │ +               When FILE EXECUTE is used, htp will launch a program (as specified by the
│ │ │ │ │ +               EXECUTE attribute) and include its output as if a FILE INCLUDE was
│ │ │ │ │ +               performed on the file. Either the OUTPUT or REDIRECT attribute must also be
│ │ │ │ │ +               included.
│ │ │ │ │ +               OUTPUT specifies the file the command will produce. This is used if the
│ │ │ │ │ +               program is either hard-coded to produce output to a particular file, or
│ │ │ │ │ +               relies on one of its command-line arguments to determine where to place the
│ │ │ │ │ +               output. The output file is deleted after its results have been imported
│ │ │ │ │ +               into the output file.
│ │ │ │ │ +               If the program produces output straight to standard output (as most UNIX
│ │ │ │ │ +               and some DOS programs do), then the REDIRECT attribute can be used. In this
│ │ │ │ │ +               case htp will take care of the redirection. Depending on the OS features it
│ │ │ │ │ +               will either append a '>' and the name of a temporary file or it will use
│ │ │ │ │ +               pipe mechanism to directly redirect without temporary files.
│ │ │ │ │ +               htp will halt processing with an error if the executable exits with an
│ │ │ │ │ +               error code of anything but zero (0). Some programs, however, do not specify
│ │ │ │ │ +               an error code when exiting, so the exit code is undetermined. If htp should
│ │ │ │ │ +               ignore the error code, specify the NOERROR attribute.
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │ @@ -153,17 +124,18 @@
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │   page_source
│ │ │ │ │   htp_project
│ │ │ │ │   htp_homepage
│ │ │ │ │  hosted by
│ │ │ │ │  Sourceforge
│ │ │ │ │ -HTML coding [Powered_by
│ │ │ │ │ +HTML coding
│ │ │ │ │ +[Powered_by
│ │ │ │ │  htp]
│ │ │ │ │       htp on-line reference / http://htp.sourceforge.net/ref/
│ │ │ │ │       Authors: Jim Nelson, Jochen_Hoenicke, Michael_Möller.
│ │ │ │ │       Maintainers: Jochen_Hoenicke.
│ │ │ │ │  Copyright © 1995–96 Jim Nelson.
│ │ │ │ │  Copyright © 2001–2014 Jochen_Hoenicke.
│ │ │ │ │ -Permission to reproduce and distribute this hypertext document granted
│ │ │ │ │ -according to terms described in the License_section.
│ │ │ │ │ +Permission to reproduce and distribute this hypertext document granted according to terms
│ │ │ │ │ +described in the License_section.
│ │ │ │ │  last updated Sat May 16, 2015
│ │ │ ├── ./usr/share/doc/htp/if.html
│ │ │ │ @@ -114,33 +114,32 @@
│ │ │ │        <a class="noline" href="bugs.html">Bugs</a></td></tr>
│ │ │ │    </table>
│ │ │ │    </div>
│ │ │ │  </td>
│ │ │ │  <td bgcolor="#f0f0d0" rowspan="2" valign="top">
│ │ │ │  <h2>syntax</h2>
│ │ │ │    <p><code>
│ │ │ │ -&nbsp; &nbsp; File image.gif <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"image.gif"</span> <span class="htp-attrib">SIZE</span>=<span class="htp-value">KBYTE</span>&gt;</span>&nbsp;kilobytes<br>
│ │ │ │ -&nbsp; &nbsp; Last modified <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"image.gif"</span> <span class="htp-attrib">TIME</span>&gt;</span>, <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"image.gif"</span> <span class="htp-attrib">DATE</span>&gt;</span><br>
│ │ │ │ +<span class="htp-tag">&lt;<a href="imageurl.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">imageurl</a> <span class="htp-attrib">url</span>=<span class="htp-string">"imageurl"</span> <span class="ebnf">[</span> <span class="htp-attrib">path</span>=<span class="htp-string">"path/in/local/filesystem"</span> <span class="ebnf">]</span>&gt;</span><br>
│ │ │ │ +<br>
│ │ │ │  </code></p>
│ │ │ │  <h2>synopsis</h2>
│ │ │ │  <STRONG>IF, NOT, ELSEIF, ELSE, and /IF</STRONG> are the building
│ │ │ │  blocks for conditional processing.  The basic form is shown above.
│ │ │ │  <P> "Conditional" is either a "compare" or "is defined" operation.  A
│ │ │ │  compare operator is a test of the value of a macro against a literal
│ │ │ │  string:
│ │ │ │    <p><code>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">INCLUDE</span>=<span class="htp-string">"include.hti"</span> <span class="htp-attrib">name</span>=<span class="htp-string">"Jim Nelson"</span> <span class="htp-attrib">email</span>=<span class="htp-string">"jnelson@crl.com"</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; This tag will fail: <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">USE</a> <span class="htp-attrib">name</span>&gt;</span><br>
│ │ │ │ +<span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">INC</a> <span class="htp-attrib">macroname1</span>=<span class="htp-string">"increment1"</span> <span class="htp-attrib">[macroname2</span>=<span class="htp-string">"increment2"</span> <span class="htp-attrib">...</span> <span class="htp-attrib">]</span> <span class="htp-attrib">[GLOBAL]</span>&gt;</span><br>
│ │ │ │ +<br>
│ │ │ │  </code></p>
│ │ │ │  <P>
│ │ │ │  and a defined operator is a test of a macro's existance:
│ │ │ │  <P>
│ │ │ │    <p><code>
│ │ │ │ -<span class="htp-tag">&lt;<a href="imageurl.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">imageurl</a> <span class="htp-attrib">url</span>=<span class="htp-string">"imageurl"</span> <span class="htp-attrib">[</span> <span class="htp-attrib">path</span>=<span class="htp-string">"path/in/local/filesystem"</span> <span class="htp-attrib">]</span>&gt;</span><br>
│ │ │ │ -<br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">INC</a> <span class="htp-attrib">i</span>=<span class="htp-string">"1"</span> <span class="htp-attrib">j</span>=<span class="htp-string">"-1"</span>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <P>
│ │ │ │  If the NOT tag is present in the IF markup, the evaluation of the
│ │ │ │  conditional is reversed.  The first IF or ELSEIF condition that
│ │ │ │  evaluates to true is chosen.  If none of the conditions is true the
│ │ │ │  ELSE block is taken if it is present.  A conditional block
│ │ │ │  <EM>must</EM> be closed with the /IF tag.  IF tags can be nested.
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,35 +1,34 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : IF, ELSEIF, ELSE, /IF ******
│ │ │ │ │ -Table_of       ***** syntax *****
│ │ │ │ │ -Contents           File image.gif <[[ref]]FILE NAME="image.gif" SIZE=KBYTE> kilobytes
│ │ │ │ │ - Introduction     Last modified <[[ref]]FILE NAME="image.gif" TIME>, <[[ref]]FILE
│ │ │ │ │ - License      NAME="image.gif" DATE>
│ │ │ │ │ - Tutorial     ***** synopsis *****
│ │ │ │ │ - Usage        IF, NOT, ELSEIF, ELSE, and /IF are the building blocks for conditional
│ │ │ │ │ - HTP Tags     processing. The basic form is shown above.
│ │ │ │ │ -    ALTTEXT  "Conditional" is either a "compare" or "is defined" operation. A compare
│ │ │ │ │ -    BLOCK    operator is a test of the value of a macro against a literal string:
│ │ │ │ │ -    BLOCKDEF     <[[ref]]FILE INCLUDE="include.hti" name="Jim Nelson"
│ │ │ │ │ -    DEF      email="jnelson@crl.com">
│ │ │ │ │ -    FILE         This tag will fail: <[[ref]]USE name>
│ │ │ │ │ - [>] IF       and a defined operator is a test of a macro's existance:
│ │ │ │ │ -    INC      <[[ref]]imageurl url="imageurl" [ path="path/in/local/filesystem" ]>
│ │ │ │ │ +Table_of_Contents            ***** syntax *****
│ │ │ │ │ + Introduction               <[[ref]]imageurl url="imageurl" [ path="path/in/
│ │ │ │ │ + License                    local/filesystem" ]>
│ │ │ │ │ + Tutorial
│ │ │ │ │ + Usage                      ***** synopsis *****
│ │ │ │ │ + HTP Tags                   IF, NOT, ELSEIF, ELSE, and /IF are the building
│ │ │ │ │ +    ALTTEXT                blocks for conditional processing. The basic form
│ │ │ │ │ +    BLOCK                  is shown above.
│ │ │ │ │ +    BLOCKDEF               "Conditional" is either a "compare" or "is
│ │ │ │ │ +    DEF                    defined" operation. A compare operator is a test
│ │ │ │ │ +    FILE                   of the value of a macro against a literal string:
│ │ │ │ │ + [>] IF                     <[[ref]]INC macroname1="increment1"
│ │ │ │ │ +    INC                    [macroname2="increment2" ... ] [GLOBAL]>
│ │ │ │ │      IMG
│ │ │ │ │ -    IMAGEURL If the NOT tag is present in the IF markup, the evaluation of the
│ │ │ │ │ -    OPT      conditional is reversed. The first IF or ELSEIF condition that evaluates
│ │ │ │ │ -    OUTPUT   to true is chosen. If none of the conditions is true the ELSE block is
│ │ │ │ │ -    QUOTE    taken if it is present. A conditional block must be closed with the /IF
│ │ │ │ │ -    SET      tag. IF tags can be nested.
│ │ │ │ │ -    UNDEF
│ │ │ │ │ -    UNSET
│ │ │ │ │ -    USE,_$
│ │ │ │ │ -    WHILE
│ │ │ │ │ -    <!---
│ │ │ │ │ +    IMAGEURL               and a defined operator is a test of a macro's
│ │ │ │ │ +    OPT                    existance:
│ │ │ │ │ +    OUTPUT                     <[[ref]]INC i="1" j="-1">
│ │ │ │ │ +    QUOTE                  If the NOT tag is present in the IF markup, the
│ │ │ │ │ +    SET                    evaluation of the conditional is reversed. The
│ │ │ │ │ +    UNDEF                  first IF or ELSEIF condition that evaluates to
│ │ │ │ │ +    UNSET                  true is chosen. If none of the conditions is true
│ │ │ │ │ +    USE,_$                 the ELSE block is taken if it is present. A
│ │ │ │ │ +    WHILE                  conditional block must be closed with the /IF tag.
│ │ │ │ │ +    <!---                  IF tags can be nested.
│ │ │ │ │   History
│ │ │ │ │   Wish_list
│ │ │ │ │   Bugs
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │ @@ -37,23 +36,27 @@
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │ +
│ │ │ │ │ +
│ │ │ │ │ +
│ │ │ │ │ +
│ │ │ │ │ +
│ │ │ │ │   page_source
│ │ │ │ │   htp_project
│ │ │ │ │   htp_homepage
│ │ │ │ │  hosted by
│ │ │ │ │  Sourceforge
│ │ │ │ │ -HTML coding
│ │ │ │ │ -[Powered_by
│ │ │ │ │ +HTML coding [Powered_by
│ │ │ │ │  htp]
│ │ │ │ │       htp on-line reference / http://htp.sourceforge.net/ref/
│ │ │ │ │       Authors: Jim Nelson, Jochen_Hoenicke, Michael_Möller.
│ │ │ │ │       Maintainers: Jochen_Hoenicke.
│ │ │ │ │  Copyright © 1995–96 Jim Nelson.
│ │ │ │ │  Copyright © 2001–2014 Jochen_Hoenicke.
│ │ │ │ │ -Permission to reproduce and distribute this hypertext document granted according to
│ │ │ │ │ -terms described in the License_section.
│ │ │ │ │ +Permission to reproduce and distribute this hypertext document granted
│ │ │ │ │ +according to terms described in the License_section.
│ │ │ │ │  last updated Sat May 16, 2015
│ │ │ ├── ./usr/share/doc/htp/imageurl.html
│ │ │ │ @@ -137,16 +137,15 @@
│ │ │ │  checks (case-insensitive) if it is a prefix of the image's SRC
│ │ │ │  attribute. If it matches this prefix is replaced by the given PATH.
│ │ │ │  If no IMAGEURL matches the SRC is considered as relative link and
│ │ │ │  looked up in the current directory.</P>
│ │ │ │  <P>
│ │ │ │  For example:</P>
│ │ │ │    <p><code>
│ │ │ │ -<span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">INC</a> <span class="htp-attrib">macroname1</span>=<span class="htp-string">"increment1"</span> <span class="htp-attrib">[macroname2</span>=<span class="htp-string">"increment2"</span> <span class="htp-attrib">...</span> <span class="htp-attrib">]</span> <span class="htp-attrib">[GLOBAL]</span>&gt;</span><br>
│ │ │ │ -<br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">INC</a> <span class="htp-attrib">i</span>=<span class="htp-string">"1"</span> <span class="htp-attrib">j</span>=<span class="htp-string">"-1"</span>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <P>
│ │ │ │  If IMAGEURL is specified with a URL but no PATH attribute, it is treated as
│ │ │ │  an undefine, and is removed.</P>
│ │ │ │  <P>
│ │ │ │  Since you usually need the url mapping for a number of images used throughout
│ │ │ │  a set of documents, IMAGEURL is most appropriately put into an
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -20,20 +20,18 @@
│ │ │ │ │      OUTPUT                 defined imageurl it checks (case-insensitive) if
│ │ │ │ │      QUOTE                  it is a prefix of the image's SRC attribute. If it
│ │ │ │ │      SET                    matches this prefix is replaced by the given PATH.
│ │ │ │ │      UNDEF                  If no IMAGEURL matches the SRC is considered as
│ │ │ │ │      UNSET                  relative link and looked up in the current
│ │ │ │ │      USE,_$                 directory.
│ │ │ │ │      WHILE                  For example:
│ │ │ │ │ -    <!---                  <[[ref]]INC macroname1="increment1"
│ │ │ │ │ - History                    [macroname2="increment2" ... ] [GLOBAL]>
│ │ │ │ │ - Wish_list
│ │ │ │ │ - Bugs                       If IMAGEURL is specified with a URL but no PATH
│ │ │ │ │ -                             attribute, it is treated as an undefine, and is
│ │ │ │ │ -                             removed.
│ │ │ │ │ +    <!---                      <[[ref]]INC i="1" j="-1">
│ │ │ │ │ + History                    If IMAGEURL is specified with a URL but no PATH
│ │ │ │ │ + Wish_list                  attribute, it is treated as an undefine, and is
│ │ │ │ │ + Bugs                       removed.
│ │ │ │ │                               Since you usually need the url mapping for a
│ │ │ │ │                               number of images used throughout a set of
│ │ │ │ │                               documents, IMAGEURL is most appropriately put into
│ │ │ │ │                               an include_file or the htp.def file.
│ │ │ │ │                               In addition to WIDTH and HEIGHT, htp can also
│ │ │ │ │                               (semi-)automatically add an ALT_text attribute to
│ │ │ │ │                               IMG tags.
│ │ │ ├── ./usr/share/doc/htp/img.html
│ │ │ │ @@ -114,16 +114,16 @@
│ │ │ │        <a class="noline" href="bugs.html">Bugs</a></td></tr>
│ │ │ │    </table>
│ │ │ │    </div>
│ │ │ │  </td>
│ │ │ │  <td bgcolor="#f0f0d0" rowspan="2" valign="top">
│ │ │ │  <h2>syntax</h2>
│ │ │ │    <p><code>
│ │ │ │ -&nbsp; &nbsp; File image.gif <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"image.gif"</span> <span class="htp-attrib">SIZE</span>=<span class="htp-value">KBYTE</span>&gt;</span>&nbsp;kilobytes<br>
│ │ │ │ -&nbsp; &nbsp; Last modified <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"image.gif"</span> <span class="htp-attrib">TIME</span>&gt;</span>, <span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">FILE</a> <span class="htp-attrib">NAME</span>=<span class="htp-string">"image.gif"</span> <span class="htp-attrib">DATE</span>&gt;</span><br>
│ │ │ │ +<span class="htp-tag">&lt;<a href="imageurl.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">imageurl</a> <span class="htp-attrib">url</span>=<span class="htp-string">"imageurl"</span> <span class="ebnf">[</span> <span class="htp-attrib">path</span>=<span class="htp-string">"path/in/local/filesystem"</span> <span class="ebnf">]</span>&gt;</span><br>
│ │ │ │ +<br>
│ │ │ │  </code></p>
│ │ │ │  <h2>synopsis</h2>
│ │ │ │  <P> <STRONG>img</STRONG> is a standard HTML tag.  htp can add the specified
│ │ │ │  image's width and height to the tag automatically.  This has the advantage
│ │ │ │  of not having to determine each image's size manually, which is especially
│ │ │ │  useful if the image may change frequently. </P>
│ │ │ │  <P> htp adds this information with the WIDTH and HEIGHT markup
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,38 +1,46 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : IMG ******
│ │ │ │ │ -Table_of       ***** syntax *****
│ │ │ │ │ -Contents           File image.gif <[[ref]]FILE NAME="image.gif" SIZE=KBYTE> kilobytes
│ │ │ │ │ - Introduction     Last modified <[[ref]]FILE NAME="image.gif" TIME>, <[[ref]]FILE
│ │ │ │ │ - License      NAME="image.gif" DATE>
│ │ │ │ │ - Tutorial     ***** synopsis *****
│ │ │ │ │ - Usage        img is a standard HTML tag. htp can add the specified image's width and
│ │ │ │ │ - HTP Tags     height to the tag automatically. This has the advantage of not having to
│ │ │ │ │ -    ALTTEXT  determine each image's size manually, which is especially useful if the
│ │ │ │ │ -    BLOCK    image may change frequently.
│ │ │ │ │ -    BLOCKDEF htp adds this information with the WIDTH and HEIGHT markup attributes. If
│ │ │ │ │ -    DEF      htp detects these attributes are already present in the tag, it will not
│ │ │ │ │ -    FILE     modify the values. If htp cannot find the image file, it will issue a
│ │ │ │ │ -    IF       warning but not halt processing.
│ │ │ │ │ -    INC      At this time, GIF (Graphic Interchange Format), PNG (Portable Network
│ │ │ │ │ - [>] IMG      Graphics), and JFIF (JPEG File Interchange Format) are supported.
│ │ │ │ │ -    IMAGEURL The IMGXY_and_NOIMGXY options control whether or not htp actually adds
│ │ │ │ │ -    OPT      this information as it executes.
│ │ │ │ │ -    OUTPUT   Since htp is able to lookup files only in the local filesystem, the
│ │ │ │ │ -    QUOTE    IMAGEURL tag may be used to map URLs to local files.
│ │ │ │ │ -    SET      htp can also add default ALT text to IMG tags using ALTTEXT.
│ │ │ │ │ -    UNDEF
│ │ │ │ │ -    UNSET
│ │ │ │ │ -    USE,_$
│ │ │ │ │ -    WHILE
│ │ │ │ │ -    <!---
│ │ │ │ │ - History
│ │ │ │ │ - Wish_list
│ │ │ │ │ - Bugs
│ │ │ │ │ +Table_of_Contents            ***** syntax *****
│ │ │ │ │ + Introduction               <[[ref]]imageurl url="imageurl" [ path="path/in/
│ │ │ │ │ + License                    local/filesystem" ]>
│ │ │ │ │ + Tutorial
│ │ │ │ │ + Usage                      ***** synopsis *****
│ │ │ │ │ + HTP Tags                   img is a standard HTML tag. htp can add the
│ │ │ │ │ +    ALTTEXT                specified image's width and height to the tag
│ │ │ │ │ +    BLOCK                  automatically. This has the advantage of not
│ │ │ │ │ +    BLOCKDEF               having to determine each image's size manually,
│ │ │ │ │ +    DEF                    which is especially useful if the image may change
│ │ │ │ │ +    FILE                   frequently.
│ │ │ │ │ +    IF                     htp adds this information with the WIDTH and
│ │ │ │ │ +    INC                    HEIGHT markup attributes. If htp detects these
│ │ │ │ │ + [>] IMG                    attributes are already present in the tag, it will
│ │ │ │ │ +    IMAGEURL               not modify the values. If htp cannot find the
│ │ │ │ │ +    OPT                    image file, it will issue a warning but not halt
│ │ │ │ │ +    OUTPUT                 processing.
│ │ │ │ │ +    QUOTE                  At this time, GIF (Graphic Interchange Format),
│ │ │ │ │ +    SET                    PNG (Portable Network Graphics), and JFIF (JPEG
│ │ │ │ │ +    UNDEF                  File Interchange Format) are supported.
│ │ │ │ │ +    UNSET                  The IMGXY_and_NOIMGXY options control whether or
│ │ │ │ │ +    USE,_$                 not htp actually adds this information as it
│ │ │ │ │ +    WHILE                  executes.
│ │ │ │ │ +    <!---                  Since htp is able to lookup files only in the
│ │ │ │ │ + History                    local filesystem, the IMAGEURL tag may be used to
│ │ │ │ │ + Wish_list                  map URLs to local files.
│ │ │ │ │ + Bugs                       htp can also add default ALT text to IMG tags
│ │ │ │ │ +                             using ALTTEXT.
│ │ │ │ │ +
│ │ │ │ │ +
│ │ │ │ │ +
│ │ │ │ │ +
│ │ │ │ │ +
│ │ │ │ │ +
│ │ │ │ │ +
│ │ │ │ │ +
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │ @@ -42,18 +50,17 @@
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │   page_source
│ │ │ │ │   htp_project
│ │ │ │ │   htp_homepage
│ │ │ │ │  hosted by
│ │ │ │ │  Sourceforge
│ │ │ │ │ -HTML coding
│ │ │ │ │ -[Powered_by
│ │ │ │ │ +HTML coding [Powered_by
│ │ │ │ │  htp]
│ │ │ │ │       htp on-line reference / http://htp.sourceforge.net/ref/
│ │ │ │ │       Authors: Jim Nelson, Jochen_Hoenicke, Michael_Möller.
│ │ │ │ │       Maintainers: Jochen_Hoenicke.
│ │ │ │ │  Copyright © 1995–96 Jim Nelson.
│ │ │ │ │  Copyright © 2001–2014 Jochen_Hoenicke.
│ │ │ │ │ -Permission to reproduce and distribute this hypertext document granted according to
│ │ │ │ │ -terms described in the License_section.
│ │ │ │ │ +Permission to reproduce and distribute this hypertext document granted
│ │ │ │ │ +according to terms described in the License_section.
│ │ │ │ │  last updated Sat May 16, 2015
│ │ │ ├── ./usr/share/doc/htp/inc.html
│ │ │ │ @@ -114,16 +114,15 @@
│ │ │ │        <a class="noline" href="bugs.html">Bugs</a></td></tr>
│ │ │ │    </table>
│ │ │ │    </div>
│ │ │ │  </td>
│ │ │ │  <td bgcolor="#f0f0d0" rowspan="2" valign="top">
│ │ │ │  <h2>syntax</h2>
│ │ │ │    <p><code>
│ │ │ │ -<span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">INC</a> <span class="htp-attrib">macroname1</span>=<span class="htp-string">"increment1"</span> <span class="ebnf">[</span><span class="htp-attrib">macroname2</span>=<span class="htp-string">"increment2"</span> <span class="htp-attrib">...</span> <span class="ebnf">]</span> <span class="ebnf">[</span><span class="htp-attrib">GLOBAL</span><span class="ebnf">]</span>&gt;</span><br>
│ │ │ │ -<br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="if.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">IF</a> <span class="htp-attrib">name</span>&gt;</span>...<span class="htp-tag">&lt;<a href="if.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/IF</a>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <h2>synopsis</h2>
│ │ │ │  The <STRONG>INC</STRONG> can be used for incrementing/decrementing a
│ │ │ │  variable or for variable addition.  The basic form is shown above.
│ │ │ │  <P>
│ │ │ │  The "increment" is anything that evaluates to a integer.  It can be a
│ │ │ │  literal string or a macro preceeded by the '$'-operator.  The
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,39 +1,37 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : INC ******
│ │ │ │ │  Table_of_Contents            ***** syntax *****
│ │ │ │ │ - Introduction               <[[ref]]INC macroname1="increment1"
│ │ │ │ │ - License                    [macroname2="increment2" ... ] [GLOBAL]>
│ │ │ │ │ - Tutorial
│ │ │ │ │ - Usage                      ***** synopsis *****
│ │ │ │ │ - HTP Tags                   The INC can be used for incrementing/decrementing
│ │ │ │ │ -    ALTTEXT                a variable or for variable addition. The basic
│ │ │ │ │ -    BLOCK                  form is shown above.
│ │ │ │ │ -    BLOCKDEF               The "increment" is anything that evaluates to a
│ │ │ │ │ -    DEF                    integer. It can be a literal string or a macro
│ │ │ │ │ -    FILE                   preceeded by the '$'-operator. The macroname must
│ │ │ │ │ -    IF                     be the name of a defined macro that contains an
│ │ │ │ │ - [>] INC                    integer. If the increment is ommitted it defaults
│ │ │ │ │ -    IMG                    to 1. The effect of this operation is that the
│ │ │ │ │ -    IMAGEURL               macro is redefined to contain the sum of its
│ │ │ │ │ -    OPT                    previous value and its increment.
│ │ │ │ │ -    OUTPUT                 To increment or decrement a variable you can use
│ │ │ │ │ -    QUOTE                  this form:
│ │ │ │ │ -    SET                        <[[ref]]INC i="1" j="-1">
│ │ │ │ │ -    UNDEF                  Note that INC doesn't check if the strings really
│ │ │ │ │ -    UNSET                  denote integers. It may give weired results when
│ │ │ │ │ -    USE,_$                 used on arbitrary strings. The integer values are
│ │ │ │ │ -    WHILE                  limited to the range -2^31..2^31.
│ │ │ │ │ -    <!---                  Note further that htp wasn't designed to do
│ │ │ │ │ - History                    extensive calculations. The INC tag is useful in
│ │ │ │ │ - Wish_list                  conjunction with WHILE to iterate over the defined
│ │ │ │ │ - Bugs                       blocks.
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │ + Introduction                   <[[ref]]IF name>...<[[ref]]/IF>
│ │ │ │ │ + License                    ***** synopsis *****
│ │ │ │ │ + Tutorial                   The INC can be used for incrementing/decrementing
│ │ │ │ │ + Usage                      a variable or for variable addition. The basic
│ │ │ │ │ + HTP Tags                   form is shown above.
│ │ │ │ │ +    ALTTEXT                The "increment" is anything that evaluates to a
│ │ │ │ │ +    BLOCK                  integer. It can be a literal string or a macro
│ │ │ │ │ +    BLOCKDEF               preceeded by the '$'-operator. The macroname must
│ │ │ │ │ +    DEF                    be the name of a defined macro that contains an
│ │ │ │ │ +    FILE                   integer. If the increment is ommitted it defaults
│ │ │ │ │ +    IF                     to 1. The effect of this operation is that the
│ │ │ │ │ + [>] INC                    macro is redefined to contain the sum of its
│ │ │ │ │ +    IMG                    previous value and its increment.
│ │ │ │ │ +    IMAGEURL               To increment or decrement a variable you can use
│ │ │ │ │ +    OPT                    this form:
│ │ │ │ │ +    OUTPUT                     <[[ref]]INC i="1" j="-1">
│ │ │ │ │ +    QUOTE                  Note that INC doesn't check if the strings really
│ │ │ │ │ +    SET                    denote integers. It may give weired results when
│ │ │ │ │ +    UNDEF                  used on arbitrary strings. The integer values are
│ │ │ │ │ +    UNSET                  limited to the range -2^31..2^31.
│ │ │ │ │ +    USE,_$                 Note further that htp wasn't designed to do
│ │ │ │ │ +    WHILE                  extensive calculations. The INC tag is useful in
│ │ │ │ │ +    <!---                  conjunction with WHILE to iterate over the defined
│ │ │ │ │ + History                    blocks.
│ │ │ │ │ + Wish_list
│ │ │ │ │ + Bugs
│ │ │ ├── ./usr/share/doc/htp/metatag.html
│ │ │ │ @@ -113,46 +113,36 @@
│ │ │ │  file</a>.  </p>
│ │ │ │  <P> Often you want to define tags that have an opening and a closing
│ │ │ │  variant.  For this purpose you should use the <a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10"><code>blockdef</code></a> tag.  When htp
│ │ │ │  encounters a blockdef tag it will automatically search for the
│ │ │ │  matching closing tag and put everything between these tags in a block
│ │ │ │  macro named <code>block</code>.  Here is an example for this.  </P>
│ │ │ │    <p><code>
│ │ │ │ -<font size="-2">&nbsp;1. </font>&nbsp; <span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">blockdef</a> <span class="htp-attrib">name</span>=<span class="htp-string">"bolditalic"</span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;2. </font>&nbsp; &nbsp; <span class="htp-tag">&lt;b&gt;</span><span class="htp-tag">&lt;i&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;3. </font>&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">block</span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;4. </font>&nbsp; &nbsp; <span class="htp-tag">&lt;/i&gt;</span><span class="htp-tag">&lt;/b&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;5. </font>&nbsp; <span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/blockdef</a>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;6. </font><br>
│ │ │ │ -<font size="-2">&nbsp;7. </font>&nbsp; This is <span class="htp-tag">&lt;bolditalic&gt;</span>bold and italic<span class="htp-tag">&lt;/bolditalic&gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;1. </font><span class="htp-tag">&lt;<a href="quote.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">QUOTE</a> <span class="htp-attrib">TAG</span> <span class="htp-attrib">[ATTRIBUTE</span>=<span class="htp-value">VALUE</span> <span class="htp-attrib">...]</span>&gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;2. </font><br>
│ │ │ │  </code></p>
│ │ │ │  <h2>Using parameters</h2>
│ │ │ │  <p> More sophisticated tags accept parameters.  The
│ │ │ │  <code>option</code> parameter lets multiple metatag parameters be
│ │ │ │  named and expanded inside the <code>def</code> or
│ │ │ │  <code>blockdef</code> block: </p>
│ │ │ │    <p><code>
│ │ │ │ -<font size="-2">&nbsp;1. </font><span class="htp-tag">&lt;<a href="quote.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">QUOTE</a> <span class="htp-attrib">TAG</span> <span class="htp-attrib">[ATTRIBUTE</span>=<span class="htp-value">VALUE</span> <span class="htp-attrib">...]</span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;2. </font><br>
│ │ │ │ +<font size="-2">&nbsp;1. </font><span class="htp-tag">&lt;<a href="undef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">UNDEF</a> <span class="htp-attrib">tagname</span>&gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;2. </font><span class="htp-tag">&lt;<a href="undef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">UNDEF</a> <span class="htp-attrib">tagname1</span> <span class="htp-attrib">tagname2</span> <span class="htp-attrib">...</span> &gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;3. </font><br>
│ │ │ │  </code></p>
│ │ │ │  <h2>Saving blocks for later</h2>
│ │ │ │  <p>When you are using templates, the html should only be written by
│ │ │ │  the template file.  The normal htp files should just define macros
│ │ │ │  that are used later in the template.  So you may want to write block
│ │ │ │  tags that just save the block in a macro for later use.  Although this
│ │ │ │  is possible with htp it is quite tricky, so here we present the way to
│ │ │ │  do this:</p>
│ │ │ │    <p><code>
│ │ │ │ -<font size="-2">&nbsp;1. </font>&nbsp; <span class="htp-tag">&lt;<a href="set.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">set</a> <span class="htp-attrib">sect-ctr</span>=<span class="htp-string">"0"</span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;2. </font>&nbsp; <span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">blockdef</a> <span class="htp-attrib">name</span>=<span class="htp-string">"section"</span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;3. </font>&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">inc</a> <span class="htp-attrib">sect-ctr</span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;4. </font>&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="block.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">block</a> <span class="htp-attrib">name</span>=<span class="htp-string">"sect-<span class="htp-macro">${sect-ctr}</span>"</span> <span class="htp-attrib">expand</span> <span class="htp-attrib">global</span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;5. </font>&nbsp; &nbsp; &nbsp; <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">block</span> <span class="htp-attrib">noexpand</span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;6. </font>&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="block.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/block</a>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;7. </font>&nbsp; <span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/blockdef</a>&gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;1. </font>&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="set.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">SET</a> <span class="htp-attrib">emailaddr</span>=<span class="htp-string">"jnelson@crl.com"</span>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <p> This defines a block macro named section.  This macro uses a
│ │ │ │  counter <code>sect-ctr</code> that enumerates the sections.  It is
│ │ │ │  increased for every section (line 3) and then the block macro name is
│ │ │ │  build from this counter.  So the first section is stored in block
│ │ │ │  sect-1, the second in sect-2 and so on.  The <a href="expand.html#global" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10"><code>global</code></a> flag
│ │ │ │  in line 4 tells htp that these macros should be defined globally
│ │ │ │ @@ -171,21 +161,15 @@
│ │ │ │  contents of block to be expanded twice.  If you omit it, it would be
│ │ │ │  expanded when defining the sect-1 macro and when using it later in the
│ │ │ │  template.  Generally it is a good idea to use noexpand whenever you
│ │ │ │  use expand in a block around it.</p>
│ │ │ │  <p>To close this example we show how to expand the
│ │ │ │  <code>sect-${sect-ctr}</code> blocks in the template:</p>
│ │ │ │    <p><code>
│ │ │ │ -<font size="-2">&nbsp;1. </font><span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="htp-attrib">include</span>=<span class="htp-string">"header.hti"</span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;2. </font>&nbsp; <span class="htp-tag">&lt;<a href="set.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">set</a> <span class="htp-attrib">sect-ctr</span>=<span class="htp-string">"1"</span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;3. </font>&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">while</a> <span class="htp-attrib">sect-<span class="htp-macro">${sect-ctr}</span></span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;4. </font>&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">sect-<span class="htp-macro">${sect-ctr}</span></span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;5. </font>&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">inc</a> <span class="htp-attrib">sect-ctr</span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;6. </font>&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/while</a>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;7. </font><span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="htp-attrib">include</span>=<span class="htp-string">"footer.hti"</span>&gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;1. </font>&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="unset.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">unset</a> <span class="htp-attrib">email_addr</span> <span class="htp-attrib">home_url</span> <span class="htp-attrib">login_name</span>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <p>
│ │ │ │  The <a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">while</a> tag in line 3 checks whether
│ │ │ │  the macro sect-${sect-ctr} is defined.  If it is defined the body is
│ │ │ │  evaluated, which expands the macro and increases sect-ctr.  Afterwards
│ │ │ │  the while condition is checked again to check for sect-2 macro.  This
│ │ │ │  repeats until sect-${sect-ctr} is not defined.
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,133 +1,122 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : Metatags ******
│ │ │ │ │ -Table_of        ***** Programming your own tags *****
│ │ │ │ │ -Contents        Metatags allow for defining your own HTML-like tags. When you
│ │ │ │ │ - Introduction  define a metatag you have to provide the HTML code which it
│ │ │ │ │ - License       abbreviates. In fact metatags are just like block macros, but
│ │ │ │ │ - Tutorial      they have a nicer syntax. With metatags you can expand htp's
│ │ │ │ │ -    Macros    functionality.
│ │ │ │ │ -    Including Metatags are defined with the [[ref]]def and [[ref]]blockdef
│ │ │ │ │ -    Templates tags and undefined with the [[ref]]undef tag.
│ │ │ │ │ -    Files     As an example we show how to define a tag that builds a fancy
│ │ │ │ │ - [>] Metatags  horizontal rule out of several images.
│ │ │ │ │ - Usage          1.<[[ref]]OPT (IMGXY|NOIMGXY)>
│ │ │ │ │ - HTP_Tags       2.<[[ref]]OPT (QUIET|VERBOSE)>
│ │ │ │ │ - History        3.<[[ref]]OPT (DEPEND|NODEPEND)>
│ │ │ │ │ - Wish_list      4.<[[ref]]OPT (PRECIOUS|NOPRECIOUS)>
│ │ │ │ │ - Bugs           5.<[[ref]]OPT (CONDENSE|SEMICONDENSE|NOCONDENSE)>
│ │ │ │ │ -                 6.<[[ref]]OPT DELIM=(HTML|SQUARE|CURLY)>
│ │ │ │ │ -                 7.<[[ref]]OPT (XML|XML=FALSE)>
│ │ │ │ │ -                 8.
│ │ │ │ │ -                In line 1 of the above example a new tag named imghr is
│ │ │ │ │ -                defined. The html code which implements this rule is following
│ │ │ │ │ -                in lines 2-8. between the [[ref]]def_and_/def tags. You don't
│ │ │ │ │ -                have to understand this html code, but you should understand
│ │ │ │ │ -                that this is just pure html to draw the fancy rule. Every time
│ │ │ │ │ -                you write <imghr> as in line 12 htp will replace this tag with
│ │ │ │ │ -                the corresponding html code. To make metatags available to all
│ │ │ │ │ -                htp documents in your project, place them in a common [
│ │ │ │ │ -                [ref]]include_file.
│ │ │ │ │ -                Often you want to define tags that have an opening and a
│ │ │ │ │ -                closing variant. For this purpose you should use the [
│ │ │ │ │ -                [ref]]blockdef tag. When htp encounters a blockdef tag it will
│ │ │ │ │ -                automatically search for the matching closing tag and put
│ │ │ │ │ -                everything between these tags in a block macro named block.
│ │ │ │ │ -                Here is an example for this.
│ │ │ │ │ -                 1.  <[[ref]]blockdef name="bolditalic">
│ │ │ │ │ -                 2.    <b><i>
│ │ │ │ │ -                 3.    <[[ref]]use block>
│ │ │ │ │ -                 4.    </i></b>
│ │ │ │ │ -                 5.  <[[ref]]/blockdef>
│ │ │ │ │ -                 6.
│ │ │ │ │ -                 7.  This is <bolditalic>bold and italic</bolditalic>
│ │ │ │ │ -                ***** Using parameters *****
│ │ │ │ │ -                More sophisticated tags accept parameters. The option
│ │ │ │ │ -                parameter lets multiple metatag parameters be named and
│ │ │ │ │ -                expanded inside the def or blockdef block:
│ │ │ │ │ -                 1.<[[ref]]QUOTE TAG [ATTRIBUTE=VALUE ...]>
│ │ │ │ │ -                 2.
│ │ │ │ │ -                ***** Saving blocks for later *****
│ │ │ │ │ -                When you are using templates, the html should only be written
│ │ │ │ │ -                by the template file. The normal htp files should just define
│ │ │ │ │ -                macros that are used later in the template. So you may want to
│ │ │ │ │ -                write block tags that just save the block in a macro for later
│ │ │ │ │ -                use. Although this is possible with htp it is quite tricky, so
│ │ │ │ │ -                here we present the way to do this:
│ │ │ │ │ -                 1.  <[[ref]]set sect-ctr="0">
│ │ │ │ │ -                 2.  <[[ref]]blockdef name="section">
│ │ │ │ │ -                 3.    <[[ref]]inc sect-ctr>
│ │ │ │ │ -                 4.    <[[ref]]block name="sect-${sect-ctr}" expand global>
│ │ │ │ │ -                 5.      <[[ref]]use block noexpand>
│ │ │ │ │ -                 6.    <[[ref]]/block>
│ │ │ │ │ -                 7.  <[[ref]]/blockdef>
│ │ │ │ │ -                This defines a block macro named section. This macro uses a
│ │ │ │ │ -                counter sect-ctr that enumerates the sections. It is increased
│ │ │ │ │ -                for every section (line 3) and then the block macro name is
│ │ │ │ │ -                build from this counter. So the first section is stored in
│ │ │ │ │ -                block sect-1, the second in sect-2 and so on. The [
│ │ │ │ │ -                [ref]]global flag in line 4 tells htp that these macros should
│ │ │ │ │ -                be defined globally for the remaining run. Otherwise they
│ │ │ │ │ -                would be forgotten at the end of the section macro.
│ │ │ │ │ -                The tricky part is the [[ref]]expand and noexpand flags in
│ │ │ │ │ -                line 4 and 5. Normally when you define a block macro the code
│ │ │ │ │ -                between the start and end tag is literally copied into the
│ │ │ │ │ -                macro value. The expansion takes place when the macro is used.
│ │ │ │ │ -                In this case that doesn't make sense; all macros sect-1, sect-
│ │ │ │ │ -                2 and so on would just contain the same value, namely <use
│ │ │ │ │ -                block> and block wouldn't be defined anymore when the macros
│ │ │ │ │ -                are finally expanded. Therefore we use expand to expand the
│ │ │ │ │ -                use tag already when sect-1 is defined.
│ │ │ │ │ -                The noexpand attribute of the [[ref]]use tag is just the
│ │ │ │ │ -                opposite and prevents the contents of block to be expanded
│ │ │ │ │ -                twice. If you omit it, it would be expanded when defining the
│ │ │ │ │ -                sect-1 macro and when using it later in the template.
│ │ │ │ │ -                Generally it is a good idea to use noexpand whenever you use
│ │ │ │ │ -                expand in a block around it.
│ │ │ │ │ -                To close this example we show how to expand the sect-${sect-
│ │ │ │ │ -                ctr} blocks in the template:
│ │ │ │ │ -                 1.<[[ref]]file include="header.hti">
│ │ │ │ │ -                 2.  <[[ref]]set sect-ctr="1">
│ │ │ │ │ -                 3.  <[[ref]]while sect-${sect-ctr}>
│ │ │ │ │ -                 4.    <[[ref]]use sect-${sect-ctr}>
│ │ │ │ │ -                 5.    <[[ref]]inc sect-ctr>
│ │ │ │ │ -                 6.  <[[ref]]/while>
│ │ │ │ │ -                 7.<[[ref]]file include="footer.hti">
│ │ │ │ │ -                The [[ref]]while tag in line 3 checks whether the macro sect-$
│ │ │ │ │ -                {sect-ctr} is defined. If it is defined the body is evaluated,
│ │ │ │ │ -                which expands the macro and increases sect-ctr. Afterwards the
│ │ │ │ │ -                while condition is checked again to check for sect-2 macro.
│ │ │ │ │ -                This repeats until sect-${sect-ctr} is not defined.
│ │ │ │ │ -                ***** Conclusions *****
│ │ │ │ │ -                This closes our short htp tutorial. I hope you did enjoy it
│ │ │ │ │ -                and see the advantages of using htp for your own projects.
│ │ │ │ │ -                Please give us some feedback about this tutorial. What can be
│ │ │ │ │ -                improved?
│ │ │ │ │ -                There is more documentation in this manual, see the [
│ │ │ │ │ -                [ref]]Usage chapter or browse the documentations for the htp
│ │ │ │ │ -                tags. If you're looking for examples, in case you haven't
│ │ │ │ │ -                already noticed yourself, there is a link to the source code
│ │ │ │ │ -                on the left, where you can get the source code for every page
│ │ │ │ │ -                on this site.
│ │ │ │ │ +Table_of_Contents       ***** Programming your own tags *****
│ │ │ │ │ + Introduction          Metatags allow for defining your own HTML-like tags.
│ │ │ │ │ + License               When you define a metatag you have to provide the HTML
│ │ │ │ │ + Tutorial              code which it abbreviates. In fact metatags are just
│ │ │ │ │ +    Macros            like block macros, but they have a nicer syntax. With
│ │ │ │ │ +    Including         metatags you can expand htp's functionality.
│ │ │ │ │ +    Templates         Metatags are defined with the [[ref]]def and [
│ │ │ │ │ +    Files             [ref]]blockdef tags and undefined with the [[ref]]undef
│ │ │ │ │ + [>] Metatags          tag.
│ │ │ │ │ + Usage                 As an example we show how to define a tag that builds a
│ │ │ │ │ + HTP_Tags              fancy horizontal rule out of several images.
│ │ │ │ │ + History                1.<[[ref]]OPT (IMGXY|NOIMGXY)>
│ │ │ │ │ + Wish_list              2.<[[ref]]OPT (QUIET|VERBOSE)>
│ │ │ │ │ + Bugs                   3.<[[ref]]OPT (DEPEND|NODEPEND)>
│ │ │ │ │ +                         4.<[[ref]]OPT (PRECIOUS|NOPRECIOUS)>
│ │ │ │ │ +                         5.<[[ref]]OPT (CONDENSE|SEMICONDENSE|NOCONDENSE)>
│ │ │ │ │ +                         6.<[[ref]]OPT DELIM=(HTML|SQUARE|CURLY)>
│ │ │ │ │ +                         7.<[[ref]]OPT (XML|XML=FALSE)>
│ │ │ │ │ +                         8.
│ │ │ │ │ +                        In line 1 of the above example a new tag named imghr is
│ │ │ │ │ +                        defined. The html code which implements this rule is
│ │ │ │ │ +                        following in lines 2-8. between the [[ref]]def_and_/def
│ │ │ │ │ +                        tags. You don't have to understand this html code, but
│ │ │ │ │ +                        you should understand that this is just pure html to
│ │ │ │ │ +                        draw the fancy rule. Every time you write <imghr> as in
│ │ │ │ │ +                        line 12 htp will replace this tag with the
│ │ │ │ │ +                        corresponding html code. To make metatags available to
│ │ │ │ │ +                        all htp documents in your project, place them in a
│ │ │ │ │ +                        common [[ref]]include_file.
│ │ │ │ │ +                        Often you want to define tags that have an opening and
│ │ │ │ │ +                        a closing variant. For this purpose you should use the
│ │ │ │ │ +                        [[ref]]blockdef tag. When htp encounters a blockdef tag
│ │ │ │ │ +                        it will automatically search for the matching closing
│ │ │ │ │ +                        tag and put everything between these tags in a block
│ │ │ │ │ +                        macro named block. Here is an example for this.
│ │ │ │ │ +                         1.<[[ref]]QUOTE TAG [ATTRIBUTE=VALUE ...]>
│ │ │ │ │ +                         2.
│ │ │ │ │ +                        ***** Using parameters *****
│ │ │ │ │ +                        More sophisticated tags accept parameters. The option
│ │ │ │ │ +                        parameter lets multiple metatag parameters be named and
│ │ │ │ │ +                        expanded inside the def or blockdef block:
│ │ │ │ │ +                         1.<[[ref]]UNDEF tagname>
│ │ │ │ │ +                         2.<[[ref]]UNDEF tagname1 tagname2 ... >
│ │ │ │ │ +                         3.
│ │ │ │ │ +                        ***** Saving blocks for later *****
│ │ │ │ │ +                        When you are using templates, the html should only be
│ │ │ │ │ +                        written by the template file. The normal htp files
│ │ │ │ │ +                        should just define macros that are used later in the
│ │ │ │ │ +                        template. So you may want to write block tags that just
│ │ │ │ │ +                        save the block in a macro for later use. Although this
│ │ │ │ │ +                        is possible with htp it is quite tricky, so here we
│ │ │ │ │ +                        present the way to do this:
│ │ │ │ │ +                         1.    <[[ref]]SET emailaddr="jnelson@crl.com">
│ │ │ │ │ +                        This defines a block macro named section. This macro
│ │ │ │ │ +                        uses a counter sect-ctr that enumerates the sections.
│ │ │ │ │ +                        It is increased for every section (line 3) and then the
│ │ │ │ │ +                        block macro name is build from this counter. So the
│ │ │ │ │ +                        first section is stored in block sect-1, the second in
│ │ │ │ │ +                        sect-2 and so on. The [[ref]]global flag in line 4
│ │ │ │ │ +                        tells htp that these macros should be defined globally
│ │ │ │ │ +                        for the remaining run. Otherwise they would be
│ │ │ │ │ +                        forgotten at the end of the section macro.
│ │ │ │ │ +                        The tricky part is the [[ref]]expand and noexpand flags
│ │ │ │ │ +                        in line 4 and 5. Normally when you define a block macro
│ │ │ │ │ +                        the code between the start and end tag is literally
│ │ │ │ │ +                        copied into the macro value. The expansion takes place
│ │ │ │ │ +                        when the macro is used. In this case that doesn't make
│ │ │ │ │ +                        sense; all macros sect-1, sect-2 and so on would just
│ │ │ │ │ +                        contain the same value, namely <use block> and block
│ │ │ │ │ +                        wouldn't be defined anymore when the macros are finally
│ │ │ │ │ +                        expanded. Therefore we use expand to expand the use tag
│ │ │ │ │ +                        already when sect-1 is defined.
│ │ │ │ │ +                        The noexpand attribute of the [[ref]]use tag is just
│ │ │ │ │ +                        the opposite and prevents the contents of block to be
│ │ │ │ │ +                        expanded twice. If you omit it, it would be expanded
│ │ │ │ │ +                        when defining the sect-1 macro and when using it later
│ │ │ │ │ +                        in the template. Generally it is a good idea to use
│ │ │ │ │ +                        noexpand whenever you use expand in a block around it.
│ │ │ │ │ +                        To close this example we show how to expand the sect-$
│ │ │ │ │ +                        {sect-ctr} blocks in the template:
│ │ │ │ │ +                         1.    <[[ref]]unset email_addr home_url login_name>
│ │ │ │ │ +                        The [[ref]]while tag in line 3 checks whether the macro
│ │ │ │ │ +                        sect-${sect-ctr} is defined. If it is defined the body
│ │ │ │ │ +                        is evaluated, which expands the macro and increases
│ │ │ │ │ +                        sect-ctr. Afterwards the while condition is checked
│ │ │ │ │ +                        again to check for sect-2 macro. This repeats until
│ │ │ │ │ +                        sect-${sect-ctr} is not defined.
│ │ │ │ │ +                        ***** Conclusions *****
│ │ │ │ │ +                        This closes our short htp tutorial. I hope you did
│ │ │ │ │ +                        enjoy it and see the advantages of using htp for your
│ │ │ │ │ +                        own projects. Please give us some feedback about this
│ │ │ │ │ +                        tutorial. What can be improved?
│ │ │ │ │ +                        There is more documentation in this manual, see the [
│ │ │ │ │ +                        [ref]]Usage chapter or browse the documentations for
│ │ │ │ │ +                        the htp tags. If you're looking for examples, in case
│ │ │ │ │ +                        you haven't already noticed yourself, there is a link
│ │ │ │ │ +                        to the source code on the left, where you can get the
│ │ │ │ │ +                        source code for every page on this site.
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │   page_source
│ │ │ │ │   htp_project
│ │ │ │ │   htp_homepage
│ │ │ │ │  hosted by
│ │ │ │ │  Sourceforge
│ │ │ │ │ -HTML coding
│ │ │ │ │ -[Powered_by
│ │ │ │ │ -htp]
│ │ │ │ │ +HTML coding [Powered
│ │ │ │ │ +by_htp]
│ │ │ │ │       htp on-line reference / http://htp.sourceforge.net/ref/
│ │ │ │ │       Authors: Jim Nelson, Jochen_Hoenicke, Michael_Möller.
│ │ │ │ │       Maintainers: Jochen_Hoenicke.
│ │ │ │ │  Copyright © 1995–96 Jim Nelson.
│ │ │ │ │  Copyright © 2001–2014 Jochen_Hoenicke.
│ │ │ │ │  Permission to reproduce and distribute this hypertext document granted
│ │ │ │ │  according to terms described in the License_section.
│ │ │ ├── ./usr/share/doc/htp/opt.html
│ │ │ │ @@ -114,21 +114,16 @@
│ │ │ │        <a class="noline" href="bugs.html">Bugs</a></td></tr>
│ │ │ │    </table>
│ │ │ │    </div>
│ │ │ │  </td>
│ │ │ │  <td bgcolor="#f0f0d0" rowspan="2" valign="top">
│ │ │ │  <h2>syntax</h2>
│ │ │ │    <p><code>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">blockdef</a> <span class="htp-attrib">name</span>=<span class="htp-string">"bolditalic"</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;b&gt;</span><span class="htp-tag">&lt;i&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">block</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;/i&gt;</span><span class="htp-tag">&lt;/b&gt;</span><br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/blockdef</a>&gt;</span><br>
│ │ │ │ +<span class="htp-tag">&lt;<a href="quote.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">QUOTE</a> <span class="htp-attrib">TAG</span> <span class="ebnf">[</span><span class="htp-attrib">ATTRIBUTE</span>=<span class="htp-value">VALUE</span> <span class="htp-attrib">...</span><span class="ebnf">]</span>&gt;</span><br>
│ │ │ │  <br>
│ │ │ │ -&nbsp; This is <span class="htp-tag">&lt;bolditalic&gt;</span>bold and italic<span class="htp-tag">&lt;/bolditalic&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <h2>synopsis</h2>
│ │ │ │  <STRONG>OPT</STRONG> is an htp tag that can be used to specify processing
│ │ │ │  options inside the actual document being processed.  The options are
│ │ │ │  used exactly as they would be on the command-line, although they are not
│ │ │ │  preceded by a &lsquo;-&rsquo; character.
│ │ │ │  <P>
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,23 +1,23 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : OPT ******
│ │ │ │ │  Table_of       ***** syntax *****
│ │ │ │ │ -Contents         <[[ref]]blockdef name="bolditalic">
│ │ │ │ │ - Introduction     <b><i>
│ │ │ │ │ - License          <[[ref]]use block>
│ │ │ │ │ - Tutorial         </i></b>
│ │ │ │ │ - Usage          <[[ref]]/blockdef>
│ │ │ │ │ - HTP Tags
│ │ │ │ │ -    ALTTEXT    This is <bolditalic>bold and italic</bolditalic>
│ │ │ │ │ -    BLOCK    ***** synopsis *****
│ │ │ │ │ -    BLOCKDEF OPT is an htp tag that can be used to specify processing options inside the
│ │ │ │ │ -    DEF      actual document being processed. The options are used exactly as they would be
│ │ │ │ │ -    FILE     on the command-line, although they are not preceded by a ‘-’ character.
│ │ │ │ │ -    IF       Click here for more_information_on_using_customization_options_with_htp.
│ │ │ │ │ +Contents       <[[ref]]QUOTE TAG [ATTRIBUTE=VALUE ...]>
│ │ │ │ │ + Introduction
│ │ │ │ │ + License      ***** synopsis *****
│ │ │ │ │ + Tutorial     OPT is an htp tag that can be used to specify processing options inside the
│ │ │ │ │ + Usage        actual document being processed. The options are used exactly as they would be
│ │ │ │ │ + HTP Tags     on the command-line, although they are not preceded by a ‘-’ character.
│ │ │ │ │ +    ALTTEXT  Click here for more_information_on_using_customization_options_with_htp.
│ │ │ │ │ +    BLOCK
│ │ │ │ │ +    BLOCKDEF
│ │ │ │ │ +    DEF
│ │ │ │ │ +    FILE
│ │ │ │ │ +    IF
│ │ │ │ │      INC
│ │ │ │ │      IMG
│ │ │ │ │      IMAGEURL
│ │ │ │ │   [>] OPT
│ │ │ │ │      OUTPUT
│ │ │ │ │      QUOTE
│ │ │ │ │      SET
│ │ │ │ │ @@ -25,19 +25,14 @@
│ │ │ │ │      UNSET
│ │ │ │ │      USE,_$
│ │ │ │ │      WHILE
│ │ │ │ │      <!---
│ │ │ │ │   History
│ │ │ │ │   Wish_list
│ │ │ │ │   Bugs
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │   page_source
│ │ │ │ │   htp_project
│ │ │ │ │   htp_homepage
│ │ │ │ │  hosted by
│ │ │ │ │  Sourceforge
│ │ │ │ │  HTML coding
│ │ │ │ │  [Powered_by
│ │ │ ├── ./usr/share/doc/htp/quote.html
│ │ │ │ @@ -114,21 +114,16 @@
│ │ │ │        <a class="noline" href="bugs.html">Bugs</a></td></tr>
│ │ │ │    </table>
│ │ │ │    </div>
│ │ │ │  </td>
│ │ │ │  <td bgcolor="#f0f0d0" rowspan="2" valign="top">
│ │ │ │  <h2>syntax</h2>
│ │ │ │    <p><code>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="set.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">set</a> <span class="htp-attrib">sect-ctr</span>=<span class="htp-string">"0"</span>&gt;</span><br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">blockdef</a> <span class="htp-attrib">name</span>=<span class="htp-string">"section"</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">inc</a> <span class="htp-attrib">sect-ctr</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="block.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">block</a> <span class="htp-attrib">name</span>=<span class="htp-string">"sect-<span class="htp-macro">${sect-ctr}</span>"</span> <span class="htp-attrib">expand</span> <span class="htp-attrib">global</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; &nbsp; <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">block</span> <span class="htp-attrib">noexpand</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="block.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/block</a>&gt;</span><br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="blockdef.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/blockdef</a>&gt;</span><br>
│ │ │ │ +<span class="htp-tag">&lt;<a href="quote.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">QUOTE</a> <span class="htp-attrib">TAG</span> <span class="ebnf">[</span><span class="htp-attrib">ATTRIBUTE</span>=<span class="htp-value">VALUE</span> <span class="htp-attrib">...</span><span class="ebnf">]</span>&gt;</span><br>
│ │ │ │ +<br>
│ │ │ │  </code></p>
│ │ │ │  <h2>synopsis</h2>
│ │ │ │  <STRONG>QUOTE</STRONG> is used to quote a macro that would otherwise
│ │ │ │  be interpreted by HTP.  It may be useful in conjunction with a
│ │ │ │  surrounding <a href="expand.html">EXPAND</a>ed block to prevent early
│ │ │ │  expansion of some contained blocks.  Note that '$' evaluation is still
│ │ │ │  done inside a quote block.
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,24 +1,24 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : QUOTE ******
│ │ │ │ │ -Table_of_Contents    ***** syntax *****
│ │ │ │ │ - Introduction         <[[ref]]set sect-ctr="0">
│ │ │ │ │ - License              <[[ref]]blockdef name="section">
│ │ │ │ │ - Tutorial               <[[ref]]inc sect-ctr>
│ │ │ │ │ - Usage                  <[[ref]]block name="sect-${sect-ctr}" expand global>
│ │ │ │ │ - HTP Tags                 <[[ref]]use block noexpand>
│ │ │ │ │ -    ALTTEXT            <[[ref]]/block>
│ │ │ │ │ -    BLOCK            <[[ref]]/blockdef>
│ │ │ │ │ -    BLOCKDEF       ***** synopsis *****
│ │ │ │ │ -    DEF            QUOTE is used to quote a macro that would otherwise be
│ │ │ │ │ -    FILE           interpreted by HTP. It may be useful in conjunction with a
│ │ │ │ │ -    IF             surrounding EXPANDed block to prevent early expansion of
│ │ │ │ │ -    INC            some contained blocks. Note that '$' evaluation is still
│ │ │ │ │ -    IMG            done inside a quote block.
│ │ │ │ │ +Table_of_Contents            ***** syntax *****
│ │ │ │ │ + Introduction               <[[ref]]QUOTE TAG [ATTRIBUTE=VALUE ...]>
│ │ │ │ │ + License
│ │ │ │ │ + Tutorial                   ***** synopsis *****
│ │ │ │ │ + Usage                      QUOTE is used to quote a macro that would
│ │ │ │ │ + HTP Tags                   otherwise be interpreted by HTP. It may be useful
│ │ │ │ │ +    ALTTEXT                in conjunction with a surrounding EXPANDed block
│ │ │ │ │ +    BLOCK                  to prevent early expansion of some contained
│ │ │ │ │ +    BLOCKDEF               blocks. Note that '$' evaluation is still done
│ │ │ │ │ +    DEF                    inside a quote block.
│ │ │ │ │ +    FILE
│ │ │ │ │ +    IF
│ │ │ │ │ +    INC
│ │ │ │ │ +    IMG
│ │ │ │ │      IMAGEURL
│ │ │ │ │      OPT
│ │ │ │ │      OUTPUT
│ │ │ │ │   [>] QUOTE
│ │ │ │ │      SET
│ │ │ │ │      UNDEF
│ │ │ │ │      UNSET
│ │ │ │ │ @@ -27,25 +27,21 @@
│ │ │ │ │      <!---
│ │ │ │ │   History
│ │ │ │ │   Wish_list
│ │ │ │ │   Bugs
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │ -
│ │ │ │ │   page_source
│ │ │ │ │   htp_project
│ │ │ │ │   htp_homepage
│ │ │ │ │  hosted by
│ │ │ │ │  Sourceforge
│ │ │ │ │ -HTML coding
│ │ │ │ │ -[Powered_by_htp]
│ │ │ │ │ +HTML coding [Powered_by
│ │ │ │ │ +htp]
│ │ │ │ │       htp on-line reference / http://htp.sourceforge.net/ref/
│ │ │ │ │       Authors: Jim Nelson, Jochen_Hoenicke, Michael_Möller.
│ │ │ │ │       Maintainers: Jochen_Hoenicke.
│ │ │ │ │  Copyright © 1995–96 Jim Nelson.
│ │ │ │ │  Copyright © 2001–2014 Jochen_Hoenicke.
│ │ │ │ │  Permission to reproduce and distribute this hypertext document granted
│ │ │ │ │  according to terms described in the License_section.
│ │ │ ├── ./usr/share/doc/htp/set.html
│ │ │ │ @@ -114,21 +114,17 @@
│ │ │ │        <a class="noline" href="bugs.html">Bugs</a></td></tr>
│ │ │ │    </table>
│ │ │ │    </div>
│ │ │ │  </td>
│ │ │ │  <td bgcolor="#f0f0d0" rowspan="2" valign="top">
│ │ │ │  <h2>syntax</h2>
│ │ │ │    <p><code>
│ │ │ │ -<span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="htp-attrib">include</span>=<span class="htp-string">"header.hti"</span>&gt;</span><br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="set.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">set</a> <span class="htp-attrib">sect-ctr</span>=<span class="htp-string">"1"</span>&gt;</span><br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">while</a> <span class="htp-attrib">sect-<span class="htp-macro">${sect-ctr}</span></span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">sect-<span class="htp-macro">${sect-ctr}</span></span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">inc</a> <span class="htp-attrib">sect-ctr</span>&gt;</span><br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/while</a>&gt;</span><br>
│ │ │ │ -<span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="htp-attrib">include</span>=<span class="htp-string">"footer.hti"</span>&gt;</span><br>
│ │ │ │ +<span class="htp-tag">&lt;<a href="unset.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">unset</a> <span class="htp-attrib">macroname</span>&gt;</span><br>
│ │ │ │ +<span class="htp-tag">&lt;<a href="unset.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">unset</a> <span class="htp-attrib">macroname1</span> <span class="htp-attrib">macroname2</span> <span class="htp-attrib">...</span> &gt;</span><br>
│ │ │ │ +<br>
│ │ │ │  </code></p>
│ │ │ │  <h2>synopsis</h2>
│ │ │ │  <STRONG>SET</STRONG> creates a macro definition that can later be expanded
│ │ │ │  anywhere in the HTML document.  To create a macro:
│ │ │ │    <p><code>
│ │ │ │  &nbsp; &nbsp; <span class="htp-tag">&lt;<a href="set.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">SET</a> <span class="htp-attrib">emailaddr</span>=<span class="htp-string">"jnelson@crl.com"</span>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,41 +1,37 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : SET ******
│ │ │ │ │  Table_of_Contents            ***** syntax *****
│ │ │ │ │ - Introduction               <[[ref]]file include="header.hti">
│ │ │ │ │ - License                      <[[ref]]set sect-ctr="1">
│ │ │ │ │ - Tutorial                     <[[ref]]while sect-${sect-ctr}>
│ │ │ │ │ - Usage                          <[[ref]]use sect-${sect-ctr}>
│ │ │ │ │ - HTP Tags                       <[[ref]]inc sect-ctr>
│ │ │ │ │ -    ALTTEXT                  <[[ref]]/while>
│ │ │ │ │ -    BLOCK                  <[[ref]]file include="footer.hti">
│ │ │ │ │ -    BLOCKDEF               ***** synopsis *****
│ │ │ │ │ -    DEF                    SET creates a macro definition that can later be
│ │ │ │ │ -    FILE                   expanded anywhere in the HTML document. To create
│ │ │ │ │ -    IF                     a macro:
│ │ │ │ │ -    INC                        <[[ref]]SET emailaddr="jnelson@crl.com">
│ │ │ │ │ -    IMG                    The macro "emailaddr" can then be expanded later.
│ │ │ │ │ -    IMAGEURL               The USE tag is used to expand the macro outside a
│ │ │ │ │ -    OPT                    tag (i.e., into the regular text). If the macro
│ │ │ │ │ -    OUTPUT                 needs to be expanded inside a markup tag, use the
│ │ │ │ │ -    QUOTE                  '$' operator.
│ │ │ │ │ - [>] SET                    Multiple macros can be declared in a single markup
│ │ │ │ │ -    UNDEF                  tag, as the second syntax line shows.
│ │ │ │ │ -    UNSET                  SET should only be used for a single line's worth
│ │ │ │ │ -    USE,_$                 of text. Multi-line macros can be defined with the
│ │ │ │ │ -    WHILE                  BLOCK tag. The BLOCK tag is also useful if the
│ │ │ │ │ -    <!---                  macro contains a quotation character and you don't
│ │ │ │ │ - History                    want to fool around with special escape
│ │ │ │ │ - Wish_list                  characters.
│ │ │ │ │ - Bugs                       Macros can be redefined by using another SET
│ │ │ │ │ -                             command with the same macro name. The prior
│ │ │ │ │ -                             definition will be destroyed, however. Also, the
│ │ │ │ │ -                             macro can be removed (destroyed) with the UNSET
│ │ │ │ │ -                             tag.
│ │ │ │ │ + Introduction               <[[ref]]unset macroname>
│ │ │ │ │ + License                    <[[ref]]unset macroname1 macroname2 ... >
│ │ │ │ │ + Tutorial
│ │ │ │ │ + Usage                      ***** synopsis *****
│ │ │ │ │ + HTP Tags                   SET creates a macro definition that can later be
│ │ │ │ │ +    ALTTEXT                expanded anywhere in the HTML document. To create
│ │ │ │ │ +    BLOCK                  a macro:
│ │ │ │ │ +    BLOCKDEF                   <[[ref]]SET emailaddr="jnelson@crl.com">
│ │ │ │ │ +    DEF                    The macro "emailaddr" can then be expanded later.
│ │ │ │ │ +    FILE                   The USE tag is used to expand the macro outside a
│ │ │ │ │ +    IF                     tag (i.e., into the regular text). If the macro
│ │ │ │ │ +    INC                    needs to be expanded inside a markup tag, use the
│ │ │ │ │ +    IMG                    '$' operator.
│ │ │ │ │ +    IMAGEURL               Multiple macros can be declared in a single markup
│ │ │ │ │ +    OPT                    tag, as the second syntax line shows.
│ │ │ │ │ +    OUTPUT                 SET should only be used for a single line's worth
│ │ │ │ │ +    QUOTE                  of text. Multi-line macros can be defined with the
│ │ │ │ │ + [>] SET                    BLOCK tag. The BLOCK tag is also useful if the
│ │ │ │ │ +    UNDEF                  macro contains a quotation character and you don't
│ │ │ │ │ +    UNSET                  want to fool around with special escape
│ │ │ │ │ +    USE,_$                 characters.
│ │ │ │ │ +    WHILE                  Macros can be redefined by using another SET
│ │ │ │ │ +    <!---                  command with the same macro name. The prior
│ │ │ │ │ + History                    definition will be destroyed, however. Also, the
│ │ │ │ │ + Wish_list                  macro can be removed (destroyed) with the UNSET
│ │ │ │ │ + Bugs                       tag.
│ │ │ ├── ./usr/share/doc/htp/unset.html
│ │ │ │ @@ -114,36 +114,37 @@
│ │ │ │        <a class="noline" href="bugs.html">Bugs</a></td></tr>
│ │ │ │    </table>
│ │ │ │    </div>
│ │ │ │  </td>
│ │ │ │  <td bgcolor="#f0f0d0" rowspan="2" valign="top">
│ │ │ │  <h2>syntax</h2>
│ │ │ │    <p><code>
│ │ │ │ -<span class="htp-tag">&lt;<a href="unset.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">unset</a> <span class="htp-attrib">macroname</span>&gt;</span><br>
│ │ │ │ -<span class="htp-tag">&lt;<a href="unset.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">unset</a> <span class="htp-attrib">macroname1</span> <span class="htp-attrib">macroname2</span> <span class="htp-attrib">...</span> &gt;</span><br>
│ │ │ │ -<br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="set.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">SET</a> <span class="htp-attrib">emailaddr</span>=<span class="htp-string">"jnelson@crl.com"</span>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <h2>synopsis</h2>
│ │ │ │  <STRONG>UNSET</STRONG> removes (or deletes) a macro and it's definition.
│ │ │ │  The macro is subsequently not available for use in the pre-processed files.
│ │ │ │  (Note that simply redefining the macro with another <A HREF="set.html">SET</A> or
│ │ │ │  <A HREF="block.html">BLOCK</A> definition with the same name is acceptable.  The
│ │ │ │  old macro definition will be removed automatically.)
│ │ │ │  <P>
│ │ │ │  For example:
│ │ │ │    <p><code>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="unset.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">unset</a> <span class="htp-attrib">email_addr</span>&gt;</span><br>
│ │ │ │ +<span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="htp-attrib">include</span>=<span class="htp-string">"header.hti"</span>&gt;</span><br>
│ │ │ │ +&nbsp; <span class="htp-tag">&lt;<a href="set.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">set</a> <span class="htp-attrib">sect-ctr</span>=<span class="htp-string">"1"</span>&gt;</span><br>
│ │ │ │ +&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">while</a> <span class="htp-attrib">sect-<span class="htp-macro">${sect-ctr}</span></span>&gt;</span><br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">sect-<span class="htp-macro">${sect-ctr}</span></span>&gt;</span><br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">inc</a> <span class="htp-attrib">sect-ctr</span>&gt;</span><br>
│ │ │ │ +&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/while</a>&gt;</span><br>
│ │ │ │ +<span class="htp-tag">&lt;<a href="file.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">file</a> <span class="htp-attrib">include</span>=<span class="htp-string">"footer.hti"</span>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <P>
│ │ │ │  More than one macro may be removed in the same tag:
│ │ │ │    <p><code>
│ │ │ │ -<span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">macroname</span> <span class="htp-attrib">[parameters</span> <span class="htp-attrib">...]</span> <span class="htp-attrib">[noexpand]</span>&gt;</span><br>
│ │ │ │ -<span class="htp-tag">&lt;... <span class="htp-attrib"><span class="htp-macro">$macroname</span></span> <span class="htp-attrib">...</span>&gt;</span><br>
│ │ │ │ -<span class="htp-tag">&lt;... <span class="htp-attrib"><span class="htp-macro">${macroname}</span></span> <span class="htp-attrib">...</span>&gt;</span><br>
│ │ │ │ -<br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="unset.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">unset</a> <span class="htp-attrib">email_addr</span> <span class="htp-attrib">home_url</span> <span class="htp-attrib">login_name</span>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <p>
│ │ │ │  </td>
│ │ │ │  </tr>
│ │ │ │  <tr>
│ │ │ │  <td width="20%" bgcolor="white" valign="bottom">
│ │ │ │   <table border="0" cellspacing="0" cellpadding="0" width="100%">
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,30 +1,30 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : UNSET ******
│ │ │ │ │ -Table_of_Contents            ***** syntax *****
│ │ │ │ │ - Introduction               <[[ref]]unset macroname>
│ │ │ │ │ - License                    <[[ref]]unset macroname1 macroname2 ... >
│ │ │ │ │ - Tutorial
│ │ │ │ │ - Usage                      ***** synopsis *****
│ │ │ │ │ - HTP Tags                   UNSET removes (or deletes) a macro and it's
│ │ │ │ │ -    ALTTEXT                definition. The macro is subsequently not
│ │ │ │ │ -    BLOCK                  available for use in the pre-processed files.
│ │ │ │ │ -    BLOCKDEF               (Note that simply redefining the macro with
│ │ │ │ │ -    DEF                    another SET or BLOCK definition with the same name
│ │ │ │ │ -    FILE                   is acceptable. The old macro definition will be
│ │ │ │ │ -    IF                     removed automatically.)
│ │ │ │ │ -    INC                    For example:
│ │ │ │ │ -    IMG                        <[[ref]]unset email_addr>
│ │ │ │ │ -    IMAGEURL               More than one macro may be removed in the same
│ │ │ │ │ -    OPT                    tag:
│ │ │ │ │ -    OUTPUT                 <[[ref]]use macroname [parameters ...] [noexpand]>
│ │ │ │ │ -    QUOTE                  <... $macroname ...>
│ │ │ │ │ -    SET                    <... ${macroname} ...>
│ │ │ │ │ -    UNDEF
│ │ │ │ │ +Table_of_Contents       ***** syntax *****
│ │ │ │ │ + Introduction              <[[ref]]SET emailaddr="jnelson@crl.com">
│ │ │ │ │ + License               ***** synopsis *****
│ │ │ │ │ + Tutorial              UNSET removes (or deletes) a macro and it's
│ │ │ │ │ + Usage                 definition. The macro is subsequently not available
│ │ │ │ │ + HTP Tags              for use in the pre-processed files. (Note that
│ │ │ │ │ +    ALTTEXT           simply redefining the macro with another SET or
│ │ │ │ │ +    BLOCK             BLOCK definition with the same name is acceptable.
│ │ │ │ │ +    BLOCKDEF          The old macro definition will be removed
│ │ │ │ │ +    DEF               automatically.)
│ │ │ │ │ +    FILE              For example:
│ │ │ │ │ +    IF                <[[ref]]file include="header.hti">
│ │ │ │ │ +    INC                 <[[ref]]set sect-ctr="1">
│ │ │ │ │ +    IMG                 <[[ref]]while sect-${sect-ctr}>
│ │ │ │ │ +    IMAGEURL              <[[ref]]use sect-${sect-ctr}>
│ │ │ │ │ +    OPT                   <[[ref]]inc sect-ctr>
│ │ │ │ │ +    OUTPUT              <[[ref]]/while>
│ │ │ │ │ +    QUOTE             <[[ref]]file include="footer.hti">
│ │ │ │ │ +    SET               More than one macro may be removed in the same tag:
│ │ │ │ │ +    UNDEF                 <[[ref]]unset email_addr home_url login_name>
│ │ │ │ │   [>] UNSET
│ │ │ │ │      USE,_$
│ │ │ │ │      WHILE
│ │ │ │ │      <!---
│ │ │ │ │   History
│ │ │ │ │   Wish_list
│ │ │ │ │   Bugs
│ │ │ │ │ @@ -42,16 +42,16 @@
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │   page_source
│ │ │ │ │   htp_project
│ │ │ │ │   htp_homepage
│ │ │ │ │  hosted by
│ │ │ │ │  Sourceforge
│ │ │ │ │ -HTML coding [Powered_by
│ │ │ │ │ -htp]
│ │ │ │ │ +HTML coding [Powered
│ │ │ │ │ +by_htp]
│ │ │ │ │       htp on-line reference / http://htp.sourceforge.net/ref/
│ │ │ │ │       Authors: Jim Nelson, Jochen_Hoenicke, Michael_Möller.
│ │ │ │ │       Maintainers: Jochen_Hoenicke.
│ │ │ │ │  Copyright © 1995–96 Jim Nelson.
│ │ │ │ │  Copyright © 2001–2014 Jochen_Hoenicke.
│ │ │ │ │  Permission to reproduce and distribute this hypertext document granted
│ │ │ │ │  according to terms described in the License_section.
│ │ │ ├── ./usr/share/doc/htp/use.html
│ │ │ │ @@ -135,18 +135,23 @@
│ │ │ │  attribute to prevent further expansion.  </p>
│ │ │ │  <p> USE will accept additional parameters, which are "local" macros
│ │ │ │  for the expanded macro.  This is only valid for <A
│ │ │ │  HREF="block.html">BLOCK</A> macros.  Macros created using <A
│ │ │ │  HREF="set.html">SET</A> cannot have parameters passed.  For
│ │ │ │  example:</p>
│ │ │ │    <p><code>
│ │ │ │ -<font size="-2">&nbsp;1. </font>&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">WHILE</a> <span class="htp-attrib">NOT</span> <span class="htp-attrib">i</span>=<span class="htp-string">"10"</span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;2. </font>&nbsp; &nbsp; ...<br>
│ │ │ │ -<font size="-2">&nbsp;3. </font>&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">INC</a> <span class="htp-attrib">i</span>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;4. </font>&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/WHILE</a>&gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;1. </font><span class="htp-tag">&lt;<a href="block.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">block</a> <span class="htp-attrib">stuff</span>&gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;2. </font>&nbsp; <span class="htp-tag">&lt;a <span class="htp-attrib">href</span>=<span class="htp-value"><span class="htp-macro">$email</span></span>&gt;</span>send email<span class="htp-tag">&lt;/a&gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;3. </font><span class="htp-tag">&lt;<a href="block.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/block</a>&gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;4. </font><br>
│ │ │ │ +<font size="-2">&nbsp;5. </font><span class="htp-tag">&lt;<a href="set.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">set</a> <span class="htp-attrib">morestuff</span>=<span class="htp-value"><span class="htp-macro">$email</span></span>&gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;6. </font><br>
│ │ │ │ +<font size="-2">&nbsp;7. </font>This works: &nbsp; &nbsp; <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">stuff</span> <span class="htp-attrib">email</span>=<span class="htp-string">"jnelson@crl.com"</span>&gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;8. </font>But this fails: <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">email</span>&gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;9. </font>And this fails: <span class="htp-tag">&lt;<a href="use.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">use</a> <span class="htp-attrib">morestuff</span> <span class="htp-attrib">email</span>=<span class="htp-string">"jnelson@crl.com"</span>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <P>
│ │ │ │  (See below for a description of the '$' operator.)  The example on
│ │ │ │  line 7 works because "stuff" has been declared as a block macro, and
│ │ │ │  the tag is passing the "email" macro to the "stuff" macro.  Line 8
│ │ │ │  fails because the "email" macro is unavailable once the block macro is
│ │ │ │  completely expanded, and cannot be passed to a SET macro.
│ │ │ │ @@ -157,19 +162,18 @@
│ │ │ │  Inside a markup tag, like <a href="img.html">IMG</a>, A (anchor), or
│ │ │ │  any other standard HTML or htp tag, the '$' operator must be used.
│ │ │ │  The '$' should be immediately followed by the macro name, which may or
│ │ │ │  may not be surrounded by curly braces.  When htp encounters this it
│ │ │ │  replaces the macro name by the contents of the macro without further
│ │ │ │  processing the contents.
│ │ │ │    <p><code>
│ │ │ │ -<font size="-2">&nbsp;1. </font>&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">WHILE</a> <span class="htp-attrib">sect-<span class="htp-macro">$i</span></span>&gt;</span><br>
│ │ │ │ +<font size="-2">&nbsp;1. </font>&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">WHILE</a> <span class="htp-attrib">NOT</span> <span class="htp-attrib">i</span>=<span class="htp-string">"10"</span>&gt;</span><br>
│ │ │ │  <font size="-2">&nbsp;2. </font>&nbsp; &nbsp; ...<br>
│ │ │ │  <font size="-2">&nbsp;3. </font>&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">INC</a> <span class="htp-attrib">i</span>&gt;</span><br>
│ │ │ │  <font size="-2">&nbsp;4. </font>&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/WHILE</a>&gt;</span><br>
│ │ │ │ -<font size="-2">&nbsp;5. </font>ref="http://$domain/~${username}/">another hyperlink<span class="htp-tag">&lt;/a&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <P>
│ │ │ │  The use of curly braces is encouraged, since it is more robust and
│ │ │ │  should never cause confusion with surrounding text.  If no curly
│ │ │ │  braces are used the macro name consists either of a single punctuation
│ │ │ │  character or the maximum sequence of letters, digits, &quot;-&quot;
│ │ │ │  and &quot;_&quot; that follows it.
│ │ │ │ @@ -183,15 +187,18 @@
│ │ │ │  delimiting the text as if it were additional markup attributes.
│ │ │ │  If the '$' macro is surrounded by other text (as in the two examples above),
│ │ │ │  quotation marks are not automatically supplied.
│ │ │ │  <P>
│ │ │ │  Note that a '$' macro can be placed anywhere in a markup tag and can
│ │ │ │  be nested.  This is valid:
│ │ │ │    <p><code>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<span class="htp-macro">${tagName}</span> <span class="htp-attrib"><span class="htp-macro">${attrName}</span></span>=<span class="htp-value"><span class="htp-macro">${value$ctr}</span></span>&gt;</span><br>
│ │ │ │ +&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">WHILE</a> <span class="htp-attrib">sect-<span class="htp-macro">$i</span></span>&gt;</span><br>
│ │ │ │ +&nbsp; &nbsp; ...<br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">INC</a> <span class="htp-attrib">i</span>&gt;</span><br>
│ │ │ │ +&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/WHILE</a>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <P> The tagName macro can contain any tag name, even a self-defined
│ │ │ │  metatag.  Note that <code>$ctr</code> is expanded before the valueX
│ │ │ │  macro is expanded, so assuming that ctr was set to 1 it will expand
│ │ │ │  value1.
│ │ │ │  <p>
│ │ │ │  </td>
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -1,73 +1,77 @@
│ │ │ │ │  
│ │ │ │ │  [HTP]
│ │ │ │ │  ****** htp on-line reference : USE, $ ******
│ │ │ │ │ -Table_of          ***** syntax *****
│ │ │ │ │ -Contents          <[[ref]]WHILE [NOT] conditional>
│ │ │ │ │ - Introduction        block
│ │ │ │ │ - License         <[[ref]]/WHILE>
│ │ │ │ │ +Table_of       ***** syntax *****
│ │ │ │ │ +Contents       <[[ref]]WHILE [NOT] conditional>
│ │ │ │ │ + Introduction     block
│ │ │ │ │ + License      <[[ref]]/WHILE>
│ │ │ │ │   Tutorial
│ │ │ │ │ - Usage           ***** synopsis *****
│ │ │ │ │ - HTP Tags        USE will expand macros that have been previously declared
│ │ │ │ │ -    ALTTEXT     with either SET or BLOCK. USE can only be used outside of
│ │ │ │ │ -    BLOCK       other markup tags.
│ │ │ │ │ -    BLOCKDEF    If you USE a block macro the value of expanded block macros
│ │ │ │ │ -    DEF         will be further parsed by htp. This is maybe not what you
│ │ │ │ │ -    FILE        want, for example, if the use is inside a block which
│ │ │ │ │ -    IF          expands itself. You can use the noexpand attribute to
│ │ │ │ │ -    INC         prevent further expansion.
│ │ │ │ │ -    IMG         USE will accept additional parameters, which are "local"
│ │ │ │ │ -    IMAGEURL    macros for the expanded macro. This is only valid for BLOCK
│ │ │ │ │ -    OPT         macros. Macros created using SET cannot have parameters
│ │ │ │ │ -    OUTPUT      passed. For example:
│ │ │ │ │ -    QUOTE        1.  <[[ref]]WHILE NOT i="10">
│ │ │ │ │ -    SET          2.    ...
│ │ │ │ │ -    UNDEF        3.    <[[ref]]INC i>
│ │ │ │ │ -    UNSET        4.  <[[ref]]/WHILE>
│ │ │ │ │ - [>] USE,_$      (See below for a description of the '$' operator.) The
│ │ │ │ │ -    WHILE       example on line 7 works because "stuff" has been declared as
│ │ │ │ │ -    <!---       a block macro, and the tag is passing the "email" macro to
│ │ │ │ │ - History         the "stuff" macro. Line 8 fails because the "email" macro is
│ │ │ │ │ - Wish_list       unavailable once the block macro is completely expanded, and
│ │ │ │ │ - Bugs            cannot be passed to a SET macro.
│ │ │ │ │ -                  Note that the "email" macro is available to other macros or
│ │ │ │ │ -                  included files called within the "stuff" block.
│ │ │ │ │ -                  Inside a markup tag, like IMG, A (anchor), or any other
│ │ │ │ │ -                  standard HTML or htp tag, the '$' operator must be used. The
│ │ │ │ │ -                  '$' should be immediately followed by the macro name, which
│ │ │ │ │ -                  may or may not be surrounded by curly braces. When htp
│ │ │ │ │ -                  encounters this it replaces the macro name by the contents
│ │ │ │ │ -                  of the macro without further processing the contents.
│ │ │ │ │ -                   1.  <[[ref]]WHILE sect-$i>
│ │ │ │ │ -                   2.    ...
│ │ │ │ │ -                   3.    <[[ref]]INC i>
│ │ │ │ │ -                   4.  <[[ref]]/WHILE>
│ │ │ │ │ -                   5.ref="http://$domain/~${username}/">another hyperlink</a>
│ │ │ │ │ -                  The use of curly braces is encouraged, since it is more
│ │ │ │ │ -                  robust and should never cause confusion with surrounding
│ │ │ │ │ -                  text. If no curly braces are used the macro name consists
│ │ │ │ │ -                  either of a single punctuation character or the maximum
│ │ │ │ │ -                  sequence of letters, digits, "-" and "_" that follows it.
│ │ │ │ │ -                  If a '$' character needs to be kept in the final output, and
│ │ │ │ │ -                  not interpreted as a macro name, it must be escaped by
│ │ │ │ │ -                  another '$' character. This is especially true for PHP code.
│ │ │ │ │ -                  If the '$' macro is the only text in the attribute's value,
│ │ │ │ │ -                  htp will automatically surround it with quotation marks to
│ │ │ │ │ -                  prevent spaces from delimiting the text as if it were
│ │ │ │ │ -                  additional markup attributes. If the '$' macro is surrounded
│ │ │ │ │ -                  by other text (as in the two examples above), quotation
│ │ │ │ │ -                  marks are not automatically supplied.
│ │ │ │ │ -                  Note that a '$' macro can be placed anywhere in a markup tag
│ │ │ │ │ -                  and can be nested. This is valid:
│ │ │ │ │ -                      <${tagName} ${attrName}=${value$ctr}>
│ │ │ │ │ -                  The tagName macro can contain any tag name, even a self-
│ │ │ │ │ -                  defined metatag. Note that $ctr is expanded before the
│ │ │ │ │ -                  valueX macro is expanded, so assuming that ctr was set to 1
│ │ │ │ │ -                  it will expand value1.
│ │ │ │ │ -
│ │ │ │ │ + Usage        ***** synopsis *****
│ │ │ │ │ + HTP Tags     USE will expand macros that have been previously declared with
│ │ │ │ │ +    ALTTEXT  either SET or BLOCK. USE can only be used outside of other markup
│ │ │ │ │ +    BLOCK    tags.
│ │ │ │ │ +    BLOCKDEF If you USE a block macro the value of expanded block macros will
│ │ │ │ │ +    DEF      be further parsed by htp. This is maybe not what you want, for
│ │ │ │ │ +    FILE     example, if the use is inside a block which expands itself. You
│ │ │ │ │ +    IF       can use the noexpand attribute to prevent further expansion.
│ │ │ │ │ +    INC      USE will accept additional parameters, which are "local" macros
│ │ │ │ │ +    IMG      for the expanded macro. This is only valid for BLOCK macros.
│ │ │ │ │ +    IMAGEURL Macros created using SET cannot have parameters passed. For
│ │ │ │ │ +    OPT      example:
│ │ │ │ │ +    OUTPUT    1.<[[ref]]block stuff>
│ │ │ │ │ +    QUOTE     2.  <a href=$email>send email</a>
│ │ │ │ │ +    SET       3.<[[ref]]/block>
│ │ │ │ │ +    UNDEF     4.
│ │ │ │ │ +    UNSET     5.<[[ref]]set morestuff=$email>
│ │ │ │ │ + [>] USE,_$    6.
│ │ │ │ │ +    WHILE     7.This works:     <[[ref]]use stuff email="jnelson@crl.com">
│ │ │ │ │ +    <!---     8.But this fails: <[[ref]]use email>
│ │ │ │ │ + History       9.And this fails: <[[ref]]use morestuff email="jnelson@crl.com">
│ │ │ │ │ + Wish_list    (See below for a description of the '$' operator.) The example on
│ │ │ │ │ + Bugs         line 7 works because "stuff" has been declared as a block macro,
│ │ │ │ │ +               and the tag is passing the "email" macro to the "stuff" macro.
│ │ │ │ │ +               Line 8 fails because the "email" macro is unavailable once the
│ │ │ │ │ +               block macro is completely expanded, and cannot be passed to a SET
│ │ │ │ │ +               macro.
│ │ │ │ │ +               Note that the "email" macro is available to other macros or
│ │ │ │ │ +               included files called within the "stuff" block.
│ │ │ │ │ +               Inside a markup tag, like IMG, A (anchor), or any other standard
│ │ │ │ │ +               HTML or htp tag, the '$' operator must be used. The '$' should be
│ │ │ │ │ +               immediately followed by the macro name, which may or may not be
│ │ │ │ │ +               surrounded by curly braces. When htp encounters this it replaces
│ │ │ │ │ +               the macro name by the contents of the macro without further
│ │ │ │ │ +               processing the contents.
│ │ │ │ │ +                1.  <[[ref]]WHILE NOT i="10">
│ │ │ │ │ +                2.    ...
│ │ │ │ │ +                3.    <[[ref]]INC i>
│ │ │ │ │ +                4.  <[[ref]]/WHILE>
│ │ │ │ │ +               The use of curly braces is encouraged, since it is more robust and
│ │ │ │ │ +               should never cause confusion with surrounding text. If no curly
│ │ │ │ │ +               braces are used the macro name consists either of a single
│ │ │ │ │ +               punctuation character or the maximum sequence of letters, digits,
│ │ │ │ │ +               "-" and "_" that follows it.
│ │ │ │ │ +               If a '$' character needs to be kept in the final output, and not
│ │ │ │ │ +               interpreted as a macro name, it must be escaped by another '$'
│ │ │ │ │ +               character. This is especially true for PHP code.
│ │ │ │ │ +               If the '$' macro is the only text in the attribute's value, htp
│ │ │ │ │ +               will automatically surround it with quotation marks to prevent
│ │ │ │ │ +               spaces from delimiting the text as if it were additional markup
│ │ │ │ │ +               attributes. If the '$' macro is surrounded by other text (as in
│ │ │ │ │ +               the two examples above), quotation marks are not automatically
│ │ │ │ │ +               supplied.
│ │ │ │ │ +               Note that a '$' macro can be placed anywhere in a markup tag and
│ │ │ │ │ +               can be nested. This is valid:
│ │ │ │ │ +                 <[[ref]]WHILE sect-$i>
│ │ │ │ │ +                   ...
│ │ │ │ │ +                   <[[ref]]INC i>
│ │ │ │ │ +                 <[[ref]]/WHILE>
│ │ │ │ │ +               The tagName macro can contain any tag name, even a self-defined
│ │ │ │ │ +               metatag. Note that $ctr is expanded before the valueX macro is
│ │ │ │ │ +               expanded, so assuming that ctr was set to 1 it will expand value1.
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │  
│ │ │ │ │ @@ -86,16 +90,17 @@
│ │ │ │ │  
│ │ │ │ │   page_source
│ │ │ │ │   htp_project
│ │ │ │ │   htp_homepage
│ │ │ │ │  hosted by
│ │ │ │ │  Sourceforge
│ │ │ │ │  HTML coding
│ │ │ │ │ -[Powered_by_htp]
│ │ │ │ │ +[Powered_by
│ │ │ │ │ +htp]
│ │ │ │ │       htp on-line reference / http://htp.sourceforge.net/ref/
│ │ │ │ │       Authors: Jim Nelson, Jochen_Hoenicke, Michael_Möller.
│ │ │ │ │       Maintainers: Jochen_Hoenicke.
│ │ │ │ │  Copyright © 1995–96 Jim Nelson.
│ │ │ │ │  Copyright © 2001–2014 Jochen_Hoenicke.
│ │ │ │ │ -Permission to reproduce and distribute this hypertext document granted
│ │ │ │ │ -according to terms described in the License_section.
│ │ │ │ │ +Permission to reproduce and distribute this hypertext document granted according
│ │ │ │ │ +to terms described in the License_section.
│ │ │ │ │  last updated Sat May 16, 2015
│ │ │ ├── ./usr/share/doc/htp/while.html
│ │ │ │ @@ -133,28 +133,24 @@
│ │ │ │  The basic form is shown above.
│ │ │ │  <P>
│ │ │ │  "Conditional" is either a "compare" or "is defined" operation.
│ │ │ │  A compare operator is a test of the value of a macro against a literal string.
│ │ │ │  If the NOT tag is present in the WHILE markup, the evaluation of the
│ │ │ │  conditional is reversed:
│ │ │ │    <p><code>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">WHILE</a> <span class="htp-attrib">NOT</span> <span class="htp-attrib">i</span>=<span class="htp-string">"10"</span>&gt;</span><br>
│ │ │ │ -&nbsp; &nbsp; ...<br>
│ │ │ │ -&nbsp; &nbsp; <span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">INC</a> <span class="htp-attrib">i</span>&gt;</span><br>
│ │ │ │ -&nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/WHILE</a>&gt;</span><br>
│ │ │ │ +&nbsp; &nbsp; <span class="htp-tag">&lt;<span class="htp-macro">${tagName}</span> <span class="htp-attrib"><span class="htp-macro">${attrName}</span></span>=<span class="htp-value"><span class="htp-macro">${value$ctr}</span></span>&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <P>
│ │ │ │  Just as with <a href="if.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">IF</a> you can also check for a
│ │ │ │  macro's existance:
│ │ │ │    <p><code>
│ │ │ │  &nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">WHILE</a> <span class="htp-attrib">sect-<span class="htp-macro">$i</span></span>&gt;</span><br>
│ │ │ │  &nbsp; &nbsp; ...<br>
│ │ │ │  &nbsp; &nbsp; <span class="htp-tag">&lt;<a href="inc.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">INC</a> <span class="htp-attrib">i</span>&gt;</span><br>
│ │ │ │  &nbsp; <span class="htp-tag">&lt;<a href="while.html" ><img src="pic/manual.png" border=0 alt="[ref]" width="10" height="10">/WHILE</a>&gt;</span><br>
│ │ │ │ -ref="http://$domain/~${username}/">another hyperlink<span class="htp-tag">&lt;/a&gt;</span><br>
│ │ │ │  </code></p>
│ │ │ │  <P>
│ │ │ │  If the condition is true, the block is evaluated and afterwards the
│ │ │ │  WHILE tag is evaluated again.  If the '$'-operator is used in the
│ │ │ │  WHILE tag it is also reevaluated on each iteration.
│ │ │ │  <P>
│ │ │ │  A loop block <EM>must</EM> be closed with the /WHILE tag.
│ │ │ │ ├── html2text {}
│ │ │ │ │ @@ -16,27 +16,23 @@
│ │ │ │ │      IF          WHILE is the building block for repeated processing. The
│ │ │ │ │      INC         basic form is shown above.
│ │ │ │ │      IMG         "Conditional" is either a "compare" or "is defined"
│ │ │ │ │      IMAGEURL    operation. A compare operator is a test of the value of a
│ │ │ │ │      OPT         macro against a literal string. If the NOT tag is present in
│ │ │ │ │      OUTPUT      the WHILE markup, the evaluation of the conditional is
│ │ │ │ │      QUOTE       reversed:
│ │ │ │ │ -    SET           <[[ref]]WHILE NOT i="10">
│ │ │ │ │ -    UNDEF           ...
│ │ │ │ │ -    UNSET           <[[ref]]INC i>
│ │ │ │ │ -    USE,_$        <[[ref]]/WHILE>
│ │ │ │ │ - [>] WHILE       Just as with [[ref]]IF you can also check for a macro's
│ │ │ │ │ -    <!---       existance:
│ │ │ │ │ - History           <[[ref]]WHILE sect-$i>
│ │ │ │ │ - Wish_list           ...
│ │ │ │ │ - Bugs                <[[ref]]INC i>
│ │ │ │ │ -                    <[[ref]]/WHILE>
│ │ │ │ │ -                  ref="http://$domain/~${username}/">another hyperlink</a>
│ │ │ │ │ -                  If the condition is true, the block is evaluated and
│ │ │ │ │ -                  afterwards the WHILE tag is evaluated again. If the '$'-
│ │ │ │ │ +    SET             <${tagName} ${attrName}=${value$ctr}>
│ │ │ │ │ +    UNDEF       Just as with [[ref]]IF you can also check for a macro's
│ │ │ │ │ +    UNSET       existance:
│ │ │ │ │ +    USE,_$        <[[ref]]WHILE sect-$i>
│ │ │ │ │ + [>] WHILE           ...
│ │ │ │ │ +    <!---           <[[ref]]INC i>
│ │ │ │ │ + History           <[[ref]]/WHILE>
│ │ │ │ │ + Wish_list       If the condition is true, the block is evaluated and
│ │ │ │ │ + Bugs            afterwards the WHILE tag is evaluated again. If the '$'-
│ │ │ │ │                    operator is used in the WHILE tag it is also reevaluated on
│ │ │ │ │                    each iteration.
│ │ │ │ │                    A loop block must be closed with the /WHILE tag.