syntax
\n\n-<![\"[ref]\"](\"pic/manual.png\")
blockdef name=\"tagname\" [option=\"option1 [option2 ...]\" ] [global] [expand]>
\n- ... <use block> ...
\n-</blockdef>
\n+<BLOCK NAME=\"blockname\" [GLOBAL] [EXPAND]>
\n+text block
\n+</BLOCK>
\n
\n
\n-<blockdef name=\"tagname\" [option=\"option1 [option2 ...]\" ] [global] [expand]>
\n- ... <use block> ...
\n-</blockdef>
\n+<BLOCK NAME=\"blockname\" [GLOBAL] [EXPAND]>
\n+text block
\n+</BLOCK>
\n
\n
\n- <alttext name=\"logo.gif\" text=\"Company logo\">
\n+<blockdef name=\"tagname\" [option=\"option1 [option2 ...]\" ] [global] [expand]>
\n+ ... <use block> ...
\n+</blockdef>
\n
\n- this line: <img src=\"logo.gif\">
\n- becomes this after processing: <img src=\"logo.gif\" alt=\"Company logo\">
\n-
\n- this line: <img src=\"../image/logo.gif\">
\n- will also have an ALT attribute appended to it
\n-
\n- this line: <img src=\"logo.gif\" alt=\"Click here for more information!\">
\n- remains unchanged.
\n
\n BLOCK and /BLOCK are used to create block macros, which\n are similar in use to SET macros, but can be\n multi-line definitions.\n
\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -1,51 +1,43 @@\n [HTP]\n *\b**\b**\b**\b**\b**\b* h\bht\btp\bp o\bon\bn-\b-l\bli\bin\bne\be r\bre\bef\bfe\ber\bre\ben\bnc\bce\be :\b: B\bBL\bLO\bOC\bCK\bK,\b, /\b/B\bBL\bLO\bOC\bCK\bK *\b**\b**\b**\b**\b**\b*\n _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs *\b**\b**\b**\b**\b* s\bsy\byn\bnt\bta\bax\bx *\b**\b**\b**\b**\b*\n-\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\ba_\bl_\bt_\bt_\be_\bx_\bt name=\"logo.gif\" text=\"Company\n-\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be logo\">\n-\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl\n-\u00a0 _\bU_\bs_\ba_\bg_\be \u00a0 this line: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg src=\"logo.gif\">\n-\u00a0 HTP Tags \u00a0 becomes this after processing: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg\n-\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT src=\"logo.gif\" alt=\"Company logo\">\n-\u00a0 [>] _\bB_\bL_\bO_\bC_\bK\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF \u00a0 this line: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg src=\"../image/logo.gif\">\n-\u00a0 \u00a0 _\bD_\bE_\bF \u00a0 will also have an ALT attribute appended to it\n-\u00a0 \u00a0 _\bF_\bI_\bL_\bE\n-\u00a0 \u00a0 _\bI_\bF \u00a0 this line: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg src=\"logo.gif\" alt=\"Click\n-\u00a0 \u00a0 _\bI_\bN_\bC here for more information!\">\n-\u00a0 \u00a0 _\bI_\bM_\bG \u00a0 remains unchanged.\n-\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n-\u00a0 \u00a0 _\bO_\bP_\bT B\bBL\bLO\bOC\bCK\bK a\ban\bnd\bd /\b/B\bBL\bLO\bOC\bCK\bK are used to create block macros,\n-\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT which are similar in use to _\bS_\bE_\bT macros, but can be\n-\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE multi-line definitions.\n-\u00a0 \u00a0 _\bS_\bE_\bT Any text and formatting may be set inside the\n-\u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF block. You can use any htp or user defined metatag\n-\u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT including _\bF_\bI_\bL_\bE_\b _\bI_\bN_\bC_\bL_\bU_\bD_\bE. The metatags won't be\n-\u00a0 \u00a0 _\bU_\bS_\bE_\b,_\b _\b$ expanded before the block is USEd except if you\n-\u00a0 \u00a0 _\bW_\bH_\bI_\bL_\bE give the _\bE_\bX_\bP_\bA_\bN_\bD parameter.\n-\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b- The block macro is dereferenced (expanded) with the\n-\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by _\bU_\bS_\bE_\b _\bt_\ba_\bg_\b _\bo_\br_\b _\bt_\bh_\be_\b _\b'_\b$_\b'_\b _\bo_\bp_\be_\br_\ba_\bt_\bo_\br. See the notes on the\n-\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt _\bU_\bS_\bE tag on how to pass parameters to a block macro.\n+\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bb_\bl_\bo_\bc_\bk_\bd_\be_\bf name=\"tagname\" [option=\"option1\n+\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be [option2 ...]\" ] [global] [expand]>\n+\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl \u00a0 ... <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bu_\bs_\be block>\u00a0...\n+\u00a0 _\bU_\bs_\ba_\bg_\be <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bb_\bl_\bo_\bc_\bk_\bd_\be_\bf>\n+\u00a0 HTP Tags\n+\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n+\u00a0 [>] _\bB_\bL_\bO_\bC_\bK B\bBL\bLO\bOC\bCK\bK a\ban\bnd\bd /\b/B\bBL\bLO\bOC\bCK\bK are used to create block macros,\n+\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF which are similar in use to _\bS_\bE_\bT macros, but can be\n+\u00a0 \u00a0 _\bD_\bE_\bF multi-line definitions.\n+\u00a0 \u00a0 _\bF_\bI_\bL_\bE Any text and formatting may be set inside the\n+\u00a0 \u00a0 _\bI_\bF block. You can use any htp or user defined metatag\n+\u00a0 \u00a0 _\bI_\bN_\bC including _\bF_\bI_\bL_\bE_\b _\bI_\bN_\bC_\bL_\bU_\bD_\bE. The metatags won't be\n+\u00a0 \u00a0 _\bI_\bM_\bG expanded before the block is USEd except if you\n+\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL give the _\bE_\bX_\bP_\bA_\bN_\bD parameter.\n+\u00a0 \u00a0 _\bO_\bP_\bT The block macro is dereferenced (expanded) with the\n+\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT _\bU_\bS_\bE_\b _\bt_\ba_\bg_\b _\bo_\br_\b _\bt_\bh_\be_\b _\b'_\b$_\b'_\b _\bo_\bp_\be_\br_\ba_\bt_\bo_\br. See the notes on the\n+\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE _\bU_\bS_\bE tag on how to pass parameters to a block macro.\n+\u00a0 \u00a0 _\bS_\bE_\bT\n+\u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF\n+\u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT\n+\u00a0 \u00a0 _\bU_\bS_\bE_\b,_\b _\b$\n+\u00a0 \u00a0 _\bW_\bH_\bI_\bL_\bE\n+\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b-\n+\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by\n+\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt\n \u00a0 _\bB_\bu_\bg_\bs\n \n \n \n \n \n \n \n-\n-\n-\n-\n-\n-\n-\n-\n \n \n \n \n \u00a0 _\bp_\ba_\bg_\be_\b _\bs_\bo_\bu_\br_\bc_\be\n \u00a0 _\bh_\bt_\bp_\b _\bp_\br_\bo_\bj_\be_\bc_\bt\n \u00a0 _\bh_\bt_\bp_\b _\bh_\bo_\bm_\be_\bp_\ba_\bg_\be\n"}]}, {"source1": "./usr/share/doc/htp/blockdef.html", "source2": "./usr/share/doc/htp/blockdef.html", "unified_diff": "@@ -114,36 +114,31 @@\n Bugs\n- <alttext name=\"logo.gif\" text=\"Company logo\">
\n-
\n- this line: <img src=\"logo.gif\">
\n- becomes this after processing: <img src=\"logo.gif\" alt=\"Company logo\">
\n-
\n- this line: <img src=\"../image/logo.gif\">
\n- will also have an ALT attribute appended to it
\n-
\n- this line: <img src=\"logo.gif\" alt=\"Click here for more information!\">
\n- remains unchanged.
\n+<!--- This comment doesn't appear in the HTML file --->
\n
For example:
\n\n-<!--- comment --->
\n+ <def name=\"centered\">
\n+ <p align=center>
\n+ </def>
\n
\n+ <centered>
\n+ This text is centered.
\n
\n All block metatags have the implicit option
\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -1,43 +1,36 @@\n [HTP]\n *\b**\b**\b**\b**\b**\b* h\bht\btp\bp o\bon\bn-\b-l\bli\bin\bne\be r\bre\bef\bfe\ber\bre\ben\bnc\bce\be :\b: B\bBL\bLO\bOC\bCK\bKD\bDE\bEF\bF,\b, /\b/B\bBL\bLO\bOC\bCK\bKD\bDE\bEF\bF *\b**\b**\b**\b**\b**\b*\n _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs *\b**\b**\b**\b**\b* s\bsy\byn\bnt\bta\bax\bx *\b**\b**\b**\b**\b*\n-\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\ba_\bl_\bt_\bt_\be_\bx_\bt name=\"logo.gif\" text=\"Company\n-\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be logo\">\n-\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl\n-\u00a0 _\bU_\bs_\ba_\bg_\be \u00a0 this line: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg src=\"logo.gif\">\n-\u00a0 HTP Tags \u00a0 becomes this after processing: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg\n-\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT src=\"logo.gif\" alt=\"Company logo\">\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK\n-\u00a0 [>] _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF \u00a0 this line: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg src=\"../image/logo.gif\">\n-\u00a0 \u00a0 _\bD_\bE_\bF \u00a0 will also have an ALT attribute appended to it\n-\u00a0 \u00a0 _\bF_\bI_\bL_\bE\n-\u00a0 \u00a0 _\bI_\bF \u00a0 this line: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg src=\"logo.gif\" alt=\"Click\n-\u00a0 \u00a0 _\bI_\bN_\bC here for more information!\">\n-\u00a0 \u00a0 _\bI_\bM_\bG \u00a0 remains unchanged.\n-\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n-\u00a0 \u00a0 _\bO_\bP_\bT B\bBL\bLO\bOC\bCK\bKD\bDE\bEF\bF creates block _\bm_\be_\bt_\ba_\bt_\ba_\bg_\bs, which is a fancy\n-\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT way of saying it creates new block tags. A block\n-\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE tag is a tag that takes a whole block as additional\n-\u00a0 \u00a0 _\bS_\bE_\bT parameter. This block is surrounded by
\n+\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bd_\be_\bf>\n+\u00a0 \u00a0 _\bO_\bP_\bT\n+\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT \u00a0 \u00a0 \n This is a simple comment that is not included in the output. This is useful\n when commenting metatags, since the metatags do not appear the output either.\n Example:\n \n Note that these comments should not include < or >, that is you\n should not use it to comment out htp code. For that purpose use something\n like this:\n Make sure that the variable is never defined and xyz should be the\n reason why you don't want to include this block \n synopsis
\n \n-<!--- This comment doesn't appear in the HTML file --->
\n+ <blockdef name=\"section\" option=\"title\">
\n+ <h1><use title></h1>
\n+ <p class=\"section\">
\n+ <use block>
\n+ </p>
\n+ </blockdef>
\n+
\n+ <section title=\"My Section\">
\n+ This is a fancy section.
\n+ </section>
\n \n-<IF [NOT] conditional>
\n- block #1
\n-[
\n-<ELSEIF [NOT] conditional>
\n- block #2
\n-...
\n-]
\n-[
\n-<ELSE>
\n- block #3
\n-]
\n-</IF>
\n+ <def name=\"centered\">
\n+ <p align=center>
\n+ </def>
\n
\n+ <centered>
\n+ This text is centered.
\n
\n+\u00a0 \u00a0 _\bI_\bF \u00a0 \u00a0 \u00a0<_\b[_\b[_\br_\be_\bf_\b]_\b]_\bu_\bs_\be block>\n+\u00a0 \u00a0 _\bI_\bN_\bC \u00a0 \u00a0
\n+\u00a0 \u00a0 _\bI_\bM_\bG \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bb_\bl_\bo_\bc_\bk_\bd_\be_\bf>\n+\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL\n+\u00a0 \u00a0 _\bO_\bP_\bT \u00a0\n+\u00a0 [>] _\b<_\b!_\b-_\b-_\b- \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bd_\be_\bf>\n+\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by\n+\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt \u00a0 \u00a0
\n-<!--- This comment doesn't appear in the HTML file --->
\n+<if disabled_because_xyz>
\n+ ...
\n+</if>
\n
\n DEF creates metatags, which is a\n fancy way of saying it creates new tags. The mechanism is very similar to\n BLOCK macros, except that the USE\n tag is not used to expand them. Instead, they are expanded by their own name.\n For example:\n
\n\n-<IF [NOT] conditional>
\n- block #1
\n-[
\n-<ELSEIF [NOT] conditional>
\n- block #2
\n-...
\n-]
\n-[
\n-<ELSE>
\n- block #3
\n-]
\n-</IF>
\n+ <def name=\"centered\">
\n+ <p align=center>
\n+ </def>
\n
\n+ <centered>
\n+ This text is centered.
\n
\n Some metatags will require an opening and closing tag (comparable to\n
\n- <IF name=\"Jim\">...</IF>
\n+<file execute=\"command-line\" (output=\"filename\" | redirect) [noerror]>
\n+<file include=\"includefilename\" [parameters ...]>
\n+<file name>
\n+<file [ name=\"filename\" ] size[ = (byte|kbyte|mbyte|gbyte) ] [precision=n]>
\n+<file [ name=\"filename\" ] time[ =\"format\" ]>
\n+<file [ name=\"filename\" ] date[ =\"format\" ]>
\n+<file search=\"searchpath\">
\n+<file template=\"templatefilename\">
\n+
\n
You should really use BLOCKDEF, though,\n as it will check for matching end tag. It is not that slower.
\n\n Options can be passed to a metatag, which can then expand as if it were\n a SET macro. Option names are parameterized with\n the OPTION attribute. Multiple options can be listed by separating their\n name with a space (which therefore requires they be surrounded by quotes.)\n
\n\n- <FILE INCLUDE=\"include.hti\" name=\"Jim Nelson\" email=\"jnelson@crl.com\">
\n- This tag will fail: <USE name>
\n+ <EM>File \"<FILE NAME>\" last updated <FILE TIME>, <FILE DATE></EM>
\n
\n htp will do very specific checking of parameters when a metatag is\n invoked. htp assumes that all parameter options to the metatag are\n optional. This is why the HEADERIMG definition uses IF to verify the\n SIZE option is defined before expanding it in the block. If a\n parameter is required, simply expand it without first checking. When\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -1,50 +1,54 @@\n [HTP]\n *\b**\b**\b**\b**\b**\b* h\bht\btp\bp o\bon\bn-\b-l\bli\bin\bne\be r\bre\bef\bfe\ber\bre\ben\bnc\bce\be :\b: D\bDE\bEF\bF,\b, /\b/D\bDE\bEF\bF *\b**\b**\b**\b**\b**\b*\n _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs *\b**\b**\b**\b**\b* s\bsy\byn\bnt\bta\bax\bx *\b**\b**\b**\b**\b*\n-\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn \n-\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n-\u00a0 _\bU_\bs_\ba_\bg_\be D\bDE\bEF\bF creates _\bm_\be_\bt_\ba_\bt_\ba_\bg_\bs, which is a fancy way of\n-\u00a0 HTP Tags saying it creates new tags. The mechanism is very\n-\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT similar to _\bB_\bL_\bO_\bC_\bK macros, except that the _\bU_\bS_\bE tag is\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK not used to expand them. Instead, they are expanded\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF by their own name. For example:\n-\u00a0 [>] _\bD_\bE_\bF <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bF [NOT] conditional>\n-\u00a0 \u00a0 _\bF_\bI_\bL_\bE \u00a0 \u00a0 block #1\n-\u00a0 \u00a0 _\bI_\bF [\n-\u00a0 \u00a0 _\bI_\bN_\bC \n+\u00a0 \u00a0 _\bI_\bN_\bC \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bd_\be_\bf>\n+\u00a0 \u00a0 _\bI_\bM_\bG\n+\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL \u00a0 \u00a0 However, if the block tag is marked with the \n When block a and block b are defined in lines 2-7 the contents of a\n are taken literally, however, the contents for b are already expanded\n so the macro \n As with all HTML, these tags do not have to be on their own line, so the\n following is perfectly acceptable:\n \n \n To include information about another file, such as an archive file or\n graphic image, specify its name with the NAME attribute followed by the\n type of information to be displayed:\n \n For file size information, the value BYTE, KBYTE, etc. dictates how the\n information is displayed. In anything other than byte format, the information\n is displayed in floating-point notation. The amount of precision (the number\n of digits to the right of the decimal point) can be set with the optional\n PRECISION attribute. The default precision is zero (0), which means no\n@@ -198,15 +178,16 @@\n \n Additional parameters can be set in the FILE INCLUDE tag, which are\n interpreted as macros that are \"passed\" to the included file. The macros\n are available only to the include file (and any macros or included files it\n holds). After the file is completely included, the macros are no longer\n available. So:\n \n Macros named \"name\" and \"email\" are set, and available inside the included\n file. They are not available, however, past the tag (which is why the\n second statement will fail.)\n \n expand\n modifier it is expanded immediately. This is useful if you want to\n store something in a block macro, that depends on the current value of\n another macro. This other macro may no longer have the correct value\n when the macro is expanded. Here is some code that demonstrate when\n the htp tags are expanded: \n- 1. <IF [NOT] conditional>
\n- 2. block #1
\n- 3. [
\n- 4. <ELSEIF [NOT] conditional>
\n- 5. block #2
\n- 6. ...
\n- 7. ]
\n- 8. [
\n- 9. <ELSE>
\n-10. block #3
\n-11. ]
\n-12. </IF>
\n+ 1. <DEF NAME=\"HEADERIMG\" OPTION=\"SRC TITLE SIZE\">
\n+ 2. <IF size>
\n+ 3. <FONT SIZE=${size}>
\n+ 4. </IF>
\n+ 5. <IMG SRC=pics/${src}>
\n+ 6. <USE title>
\n+ 7. <IF size>
\n+ 8. </FONT>
\n+ 9. </IF>
\n+10. </DEF>
\n+11.
\n+12. <HEADERIMG SRC=\"logo.gif\" SIZE=\"+2\" TITLE=\"A title\">
\n 13.
\n+14. <HEADERIMG SRC=\"logo.gif\" TITLE=\"Normal sized title\">
\n+15.
\n+16. This will fail:
\n+17. <HEADERIMG SRC=\"logo.gif\" ALT=\"Our logo\" TITLE=\"Another title\">
\n+18.
\n+19. Instead, use * like this:
\n+20. <DEF NAME=\"MYIMG\" OPTION=\"SRC *\">
\n+21. <IMG SRC=\"pics/${src}\" $*>
\n+22. </DEF>
\n+23.
\n+24. <MYIMG SRC=\"logo.gif\" ALT=\"Our logo\">
\n \n- <IF name=\"Jim\">...</IF>
\n+ <EM>File \"<FILE NAME>\" last updated <FILE TIME>, <FILE DATE></EM>
\n time is evaluated. So a is expanded when it\n is used, while the contents of b are already expanded.\n \n- <IF name=\"Jim\">...</IF>
\n+ <EM>File \"<FILE NAME>\" last updated <FILE TIME>, <FILE DATE></EM>
\n NAME, TIME, SIZE
\n \n- <imageurl url=\"http://my.domain.org/\" path=\"/var/www/my.domain/\">
\n- <imageurl url=\"other.domain.org/\" path=\"/var/www/other.domain/\">
\n+<img src=\"filename\" ...>
\n
\n- For this line: <img src=\"logo.gif\">
\n- the local filename \"logo.gif\" will be used to determine image dimensions
\n- (no URL replacement).
\n-
\n- For this line: <img src=\"http://my.domain.org/logo.gif\">
\n- the local filename \"/var/www/my.domain/logo.gif\" will be used.
\n-
\n- But for this line: <img src=\"http://other.domain.org/logo.gif\">
\n- the local file cannot be found (no prefix match), so the image dimensions
\n- will not be added.
\n-
\n- Order is important; last IMAGEURL tag takes precedence:
\n- <imageurl url=\"/\" path=\"/var/www/htdocs/\">
\n- <imageurl url=\"/test/\" path=\"/var/www/test/\">
\n-
\n- <img src=\"/image.gif\"> and <img src=\"/test/image.gif\"> are mapped to
\n- /var/www/htdocs/image.gif and /var/www/test/image.gif, resp.
\n- If the order of the imageurl lines would be swapped, the second
\n- image would be mapped to /var/www/htdocs/test/image.gif.
\n \n- <INC i=\"1\" j=\"-1\">
\n+<imageurl url=\"imageurl\" [ path=\"path/in/local/filesystem\" ]>
\n+
\n TEMPLATE
\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -17,55 +17,23 @@\n \u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL purpose. The output file's name, the current date\n \u00a0 \u00a0 _\bO_\bP_\bT and time, and the contents of another file may be\n \u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT included. Another file's time, date, or size may be\n \u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE added to the output file as well.\n \u00a0 \u00a0 _\bS_\bE_\bT As with all HTML, these tags do not have to be on\n \u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF their own line, so the following is perfectly\n \u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT acceptable:\n-\u00a0 \u00a0 _\bU_\bS_\bE_\b,_\b _\b$ \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bF name=\"Jim\">...<_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bI_\bF>\n-\u00a0 \u00a0 _\bW_\bH_\bI_\bL_\bE *\b**\b**\b**\b* N\bNA\bAM\bME\bE,\b, T\bTI\bIM\bME\bE,\b, S\bSI\bIZ\bZE\bE *\b**\b**\b**\b*\n-\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b- To include information about another file, such as\n-\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by an archive file or graphic image, specify its name\n-\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt with the NAME attribute followed by the type of\n-\u00a0 _\bB_\bu_\bg_\bs information to be displayed:\n- \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\ba_\bg_\be_\bu_\br_\bl url=\"http://my.domain.org/\n- \" path=\"/var/www/my.domain/\">\n- \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\ba_\bg_\be_\bu_\br_\bl url=\"other.domain.org/\" path=\"/\n- var/www/other.domain/\">\n+\u00a0 \u00a0 _\bU_\bS_\bE_\b,_\b _\b$ \u00a0 \u00a0 File \"<_\b[_\b[_\br_\be_\bf_\b]_\b]_\bF_\bI_\bL_\bE NAME>\" last updated <_\b[\n+\u00a0 \u00a0 _\bW_\bH_\bI_\bL_\bE _\b[_\br_\be_\bf_\b]_\b]_\bF_\bI_\bL_\bE TIME>, <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bF_\bI_\bL_\bE DATE>\n+\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b- *\b**\b**\b**\b* N\bNA\bAM\bME\bE,\b, T\bTI\bIM\bME\bE,\b, S\bSI\bIZ\bZE\bE *\b**\b**\b**\b*\n+\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by To include information about another file, such as\n+\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt an archive file or graphic image, specify its name\n+\u00a0 _\bB_\bu_\bg_\bs with the NAME attribute followed by the type of\n+ information to be displayed:\n+ <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg src=\"filename\" ...>\n \n- \u00a0 For this line: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg src=\"logo.gif\">\n- \u00a0 the local filename \"logo.gif\" will be used to\n- determine image dimensions\n- \u00a0 (no URL replacement).\n-\n- \u00a0 For this line: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg src=\"http://\n- my.domain.org/logo.gif\">\n- \u00a0 the local filename \"/var/www/my.domain/logo.gif\"\n- will be used.\n-\n- \u00a0 But for this line: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg src=\"http://\n- other.domain.org/logo.gif\">\n- \u00a0 the local file cannot be found (no prefix match),\n- so the image dimensions\n- \u00a0 will not be added.\n-\n- \u00a0 Order is important; last IMAGEURL tag takes\n- precedence:\n- \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\ba_\bg_\be_\bu_\br_\bl url=\"/\" path=\"/var/www/htdocs/\">\n- \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\ba_\bg_\be_\bu_\br_\bl url=\"/test/\" path=\"/var/www/\n- test/\">\n-\n- \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg src=\"/image.gif\">\u00a0and <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg\n- src=\"/test/image.gif\">\u00a0are mapped to\n- \u00a0 /var/www/htdocs/image.gif and /var/www/test/\n- image.gif, resp.\n- \u00a0 If the order of the imageurl lines would be\n- swapped, the second\n- \u00a0 image would be mapped to /var/www/htdocs/test/\n- image.gif.\n For file size information, the value BYTE, KBYTE,\n etc. dictates how the information is displayed. In\n anything other than byte format, the information is\n displayed in floating-point notation. The amount of\n precision (the number of digits to the right of the\n decimal point) can be set with the optional\n PRECISION attribute. The default precision is zero\n@@ -96,15 +64,17 @@\n Additional parameters can be set in the FILE\n INCLUDE tag, which are interpreted as macros that\n are \"passed\" to the included file. The macros are\n available only to the include file (and any macros\n or included files it holds). After the file is\n completely included, the macros are no longer\n available. So:\n- \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bN_\bC i=\"1\" j=\"-1\">\n+ <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\ba_\bg_\be_\bu_\br_\bl url=\"imageurl\" [ path=\"path/in/\n+ local/filesystem\" ]>\n+\n Macros named \"name\" and \"email\" are set, and\n available inside the included file. They are not\n available, however, past the tag (which is why the\n second statement will fail.)\n *\b**\b**\b**\b* T\bTE\bEM\bMP\bPL\bLA\bAT\bTE\bE *\b**\b**\b**\b*\n A template file is nothing more than a default\n include file, one that is included once the input\n"}]}, {"source1": "./usr/share/doc/htp/if.html", "source2": "./usr/share/doc/htp/if.html", "unified_diff": "@@ -114,62 +114,31 @@\n Bugs
\n- <def name=\"bigfont\">
\n- <font size=\"+4\">
\n- </def>
\n+<imageurl url=\"imageurl\" [ path=\"path/in/local/filesystem\" ]>
\n
\n- <def name=\"/bigfont\">
\n- </font>
\n- </def>
\n-
\n- <bigfont>Some large text</bigfont>
\n
\"Conditional\" is either a \"compare\" or \"is defined\" operation. A\n compare operator is a test of the value of a macro against a literal\n string:\n
\n- <DEF NAME=\"HEADERIMG\" OPTION=\"SRC TITLE SIZE\">
\n- <IF size>
\n- <FONT SIZE=${size}>
\n- </IF>
\n- <IMG SRC=pics/${src}>
\n- <USE title>
\n- <IF size>
\n- </FONT>
\n- </IF>
\n- </DEF>
\n-
\n- <HEADERIMG SRC=\"logo.gif\" SIZE=\"+2\" TITLE=\"A title\">
\n-
\n- <HEADERIMG SRC=\"logo.gif\" TITLE=\"Normal sized title\">
\n-
\n- This will fail:
\n- <HEADERIMG SRC=\"logo.gif\" ALT=\"Our logo\" TITLE=\"Another title\">
\n-
\n- Instead, use * like this:
\n- <DEF NAME=\"MYIMG\" OPTION=\"SRC *\">
\n- <IMG SRC=\"pics/${src}\" $*>
\n- </DEF>
\n-
\n- <MYIMG SRC=\"logo.gif\" ALT=\"Our logo\">
\n+ <IF name=\"Jim\">...</IF>
\n
\n and a defined operator is a test of a macro's existance:\n
\n
\n- <FILE INCLUDE=\"include.hti\" name=\"Jim Nelson\" email=\"jnelson@crl.com\">
\n- This tag will fail: <USE name>
\n+ <INC i=\"1\" j=\"-1\">
\n
\n If the NOT tag is present in the IF markup, the evaluation of the\n conditional is reversed. The first IF or ELSEIF condition that\n evaluates to true is chosen. If none of the conditions is true the\n ELSE block is taken if it is present. A conditional block\n must be closed with the /IF tag. IF tags can be nested.\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -1,71 +1,36 @@\n [HTP]\n *\b**\b**\b**\b**\b**\b* h\bht\btp\bp o\bon\bn-\b-l\bli\bin\bne\be r\bre\bef\bfe\ber\bre\ben\bnc\bce\be :\b: I\bIF\bF,\b, E\bEL\bLS\bSE\bEI\bIF\bF,\b, E\bEL\bLS\bSE\bE,\b, /\b/I\bIF\bF *\b**\b**\b**\b**\b**\b*\n _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs *\b**\b**\b**\b**\b* s\bsy\byn\bnt\bta\bax\bx *\b**\b**\b**\b**\b*\n-\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bd_\be_\bf name=\"bigfont\">\n-\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be \u00a0 \u00a0 \n-\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bd_\be_\bf>\n-\u00a0 _\bU_\bs_\ba_\bg_\be\n-\u00a0 HTP Tags \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bd_\be_\bf name=\"/bigfont\">\n-\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT \u00a0 \u00a0 \n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bd_\be_\bf>\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF\n-\u00a0 \u00a0 _\bD_\bE_\bF \u00a0
\n- <IF name>...</IF>
\n+<INC macroname1=\"increment1\" [macroname2=\"increment2\" ... ] [GLOBAL]>
\n+
\n
\n IMAGEURL tells htp, where to find images on the local\n file system. declares an URL replacement that is used for\n size lookups in any IMG tag. This definitions\n takes effect only if the IMGXY option is\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -1,36 +1,38 @@\n [HTP]\n *\b**\b**\b**\b**\b**\b* h\bht\btp\bp o\bon\bn-\b-l\bli\bin\bne\be r\bre\bef\bfe\ber\bre\ben\bnc\bce\be :\b: I\bIM\bMA\bAG\bGE\bEU\bUR\bRL\bL *\b**\b**\b**\b**\b**\b*\n _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs *\b**\b**\b**\b**\b* s\bsy\byn\bnt\bta\bax\bx *\b**\b**\b**\b**\b*\n-\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bF name>...<_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bI_\bF>\n-\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n-\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl I\bIM\bMA\bAG\bGE\bEU\bUR\bRL\bL tells htp, where to find images on the\n-\u00a0 _\bU_\bs_\ba_\bg_\be local file system. declares an URL replacement that\n-\u00a0 HTP Tags is used for size lookups in any _\bI_\bM_\bG tag. This\n-\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT definitions takes effect only if the _\bI_\bM_\bG_\bX_\bY option\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK is enabled. Beacause htp can't lookup files in the\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF world wide web you have to map absolute image URLs\n-\u00a0 \u00a0 _\bD_\bE_\bF to a directory in the local file system.\n-\u00a0 \u00a0 _\bF_\bI_\bL_\bE When an IMG tag is encountered where htp has to\n-\u00a0 \u00a0 _\bI_\bF insert width and height the defined URL\n-\u00a0 \u00a0 _\bI_\bN_\bC replacements will be taken into account (later\n-\u00a0 \u00a0 _\bI_\bM_\bG definitions take precedence to earlier): For each\n-\u00a0 [>] _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL defined imageurl it checks (case-insensitive) if it\n-\u00a0 \u00a0 _\bO_\bP_\bT is a prefix of the image's SRC attribute. If it\n-\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT matches this prefix is replaced by the given PATH.\n-\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE If no IMAGEURL matches the SRC is considered as\n-\u00a0 \u00a0 _\bS_\bE_\bT relative link and looked up in the current\n-\u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF directory.\n-\u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT For example:\n-\u00a0 \u00a0 _\bU_\bS_\bE_\b,_\b _\b$ \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bN_\bC i=\"1\" j=\"-1\">\n-\u00a0 \u00a0 _\bW_\bH_\bI_\bL_\bE If IMAGEURL is specified with a URL but no PATH\n-\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b- attribute, it is treated as an undefine, and is\n-\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by removed.\n-\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt Since you usually need the url mapping for a number\n-\u00a0 _\bB_\bu_\bg_\bs of images used throughout a set of documents,\n+\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bN_\bC macroname1=\"increment1\"\n+\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be [macroname2=\"increment2\" ... ] [GLOBAL]>\n+\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl\n+\u00a0 _\bU_\bs_\ba_\bg_\be *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n+\u00a0 HTP Tags I\bIM\bMA\bAG\bGE\bEU\bUR\bRL\bL tells htp, where to find images on the\n+\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT local file system. declares an URL replacement that\n+\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK is used for size lookups in any _\bI_\bM_\bG tag. This\n+\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF definitions takes effect only if the _\bI_\bM_\bG_\bX_\bY option\n+\u00a0 \u00a0 _\bD_\bE_\bF is enabled. Beacause htp can't lookup files in the\n+\u00a0 \u00a0 _\bF_\bI_\bL_\bE world wide web you have to map absolute image URLs\n+\u00a0 \u00a0 _\bI_\bF to a directory in the local file system.\n+\u00a0 \u00a0 _\bI_\bN_\bC When an IMG tag is encountered where htp has to\n+\u00a0 \u00a0 _\bI_\bM_\bG insert width and height the defined URL\n+\u00a0 [>] _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL replacements will be taken into account (later\n+\u00a0 \u00a0 _\bO_\bP_\bT definitions take precedence to earlier): For each\n+\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT defined imageurl it checks (case-insensitive) if it\n+\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE is a prefix of the image's SRC attribute. If it\n+\u00a0 \u00a0 _\bS_\bE_\bT matches this prefix is replaced by the given PATH.\n+\u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF If no IMAGEURL matches the SRC is considered as\n+\u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT relative link and looked up in the current\n+\u00a0 \u00a0 _\bU_\bS_\bE_\b,_\b _\b$ directory.\n+\u00a0 \u00a0 _\bW_\bH_\bI_\bL_\bE For example:\n+\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b- \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bN_\bC i=\"1\" j=\"-1\">\n+\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by If IMAGEURL is specified with a URL but no PATH\n+\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt attribute, it is treated as an undefine, and is\n+\u00a0 _\bB_\bu_\bg_\bs removed.\n+ Since you usually need the url mapping for a number\n+ of images used throughout a set of documents,\n IMAGEURL is most appropriately put into an _\bi_\bn_\bc_\bl_\bu_\bd_\be\n _\bf_\bi_\bl_\be or the _\bh_\bt_\bp_\b._\bd_\be_\bf file.\n In addition to WIDTH and HEIGHT, htp can also\n (semi-)automatically add an _\bA_\bL_\bT_\b _\bt_\be_\bx_\bt attribute to\n _\bI_\bM_\bG tags.\n \n \n"}]}, {"source1": "./usr/share/doc/htp/img.html", "source2": "./usr/share/doc/htp/img.html", "unified_diff": "@@ -114,15 +114,16 @@\n Bugs
\n- <IF name=\"Jim\">...</IF>
\n+<imageurl url=\"imageurl\" [ path=\"path/in/local/filesystem\" ]>
\n+
\n
img is a standard HTML tag. htp can add the specified\n image's width and height to the tag automatically. This has the advantage\n of not having to determine each image's size manually, which is especially\n useful if the image may change frequently.
\nhtp adds this information with the WIDTH and HEIGHT markup\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -1,36 +1,38 @@\n [HTP]\n *\b**\b**\b**\b**\b**\b* h\bht\btp\bp o\bon\bn-\b-l\bli\bin\bne\be r\bre\bef\bfe\ber\bre\ben\bnc\bce\be :\b: I\bIM\bMG\bG *\b**\b**\b**\b**\b**\b*\n _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs *\b**\b**\b**\b**\b* s\bsy\byn\bnt\bta\bax\bx *\b**\b**\b**\b**\b*\n-\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bF name=\"Jim\">...<_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bI_\bF>\n-\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n-\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl i\bim\bmg\bg is a standard HTML tag. htp can add the\n-\u00a0 _\bU_\bs_\ba_\bg_\be specified image's width and height to the tag\n-\u00a0 HTP Tags automatically. This has the advantage of not having\n-\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT to determine each image's size manually, which is\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK especially useful if the image may change\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF frequently.\n-\u00a0 \u00a0 _\bD_\bE_\bF htp adds this information with the WIDTH and HEIGHT\n-\u00a0 \u00a0 _\bF_\bI_\bL_\bE markup attributes. If htp detects these attributes\n-\u00a0 \u00a0 _\bI_\bF are already present in the tag, it will n\bno\bot\bt modify\n-\u00a0 \u00a0 _\bI_\bN_\bC the values. If htp cannot find the image file, it\n-\u00a0 [>] _\bI_\bM_\bG will issue a warning but not halt processing.\n-\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL At this time, GIF (Graphic Interchange Format), PNG\n-\u00a0 \u00a0 _\bO_\bP_\bT (Portable Network Graphics), and JFIF (JPEG File\n-\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT Interchange Format) are supported.\n-\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE The _\bI_\bM_\bG_\bX_\bY_\b _\ba_\bn_\bd_\b _\bN_\bO_\bI_\bM_\bG_\bX_\bY options control whether or\n-\u00a0 \u00a0 _\bS_\bE_\bT not htp actually adds this information as it\n-\u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF executes.\n-\u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT Since htp is able to lookup files only in the local\n-\u00a0 \u00a0 _\bU_\bS_\bE_\b,_\b _\b$ filesystem, the _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL tag may be used to map\n-\u00a0 \u00a0 _\bW_\bH_\bI_\bL_\bE URLs to local files.\n-\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b- htp can also add default ALT text to IMG tags using\n-\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by _\bA_\bL_\bT_\bT_\bE_\bX_\bT.\n-\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt\n-\u00a0 _\bB_\bu_\bg_\bs\n+\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\ba_\bg_\be_\bu_\br_\bl url=\"imageurl\" [ path=\"path/in/\n+\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be local/filesystem\" ]>\n+\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl\n+\u00a0 _\bU_\bs_\ba_\bg_\be *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n+\u00a0 HTP Tags i\bim\bmg\bg is a standard HTML tag. htp can add the\n+\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT specified image's width and height to the tag\n+\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK automatically. This has the advantage of not having\n+\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF to determine each image's size manually, which is\n+\u00a0 \u00a0 _\bD_\bE_\bF especially useful if the image may change\n+\u00a0 \u00a0 _\bF_\bI_\bL_\bE frequently.\n+\u00a0 \u00a0 _\bI_\bF htp adds this information with the WIDTH and HEIGHT\n+\u00a0 \u00a0 _\bI_\bN_\bC markup attributes. If htp detects these attributes\n+\u00a0 [>] _\bI_\bM_\bG are already present in the tag, it will n\bno\bot\bt modify\n+\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL the values. If htp cannot find the image file, it\n+\u00a0 \u00a0 _\bO_\bP_\bT will issue a warning but not halt processing.\n+\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT At this time, GIF (Graphic Interchange Format), PNG\n+\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE (Portable Network Graphics), and JFIF (JPEG File\n+\u00a0 \u00a0 _\bS_\bE_\bT Interchange Format) are supported.\n+\u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF The _\bI_\bM_\bG_\bX_\bY_\b _\ba_\bn_\bd_\b _\bN_\bO_\bI_\bM_\bG_\bX_\bY options control whether or\n+\u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT not htp actually adds this information as it\n+\u00a0 \u00a0 _\bU_\bS_\bE_\b,_\b _\b$ executes.\n+\u00a0 \u00a0 _\bW_\bH_\bI_\bL_\bE Since htp is able to lookup files only in the local\n+\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b- filesystem, the _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL tag may be used to map\n+\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by URLs to local files.\n+\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt htp can also add default ALT text to IMG tags using\n+\u00a0 _\bB_\bu_\bg_\bs _\bA_\bL_\bT_\bT_\bE_\bX_\bT.\n+\n+\n \n \n \n \n \n \n \n"}]}, {"source1": "./usr/share/doc/htp/inc.html", "source2": "./usr/share/doc/htp/inc.html", "unified_diff": "@@ -114,16 +114,15 @@\n Bugs
\n- <FILE INCLUDE=\"include.hti\" name=\"Jim Nelson\" email=\"jnelson@crl.com\">
\n- This tag will fail: <USE name>
\n+ <IF name=\"Jim\">...</IF>
\n
\n The \"increment\" is anything that evaluates to a integer. It can be a\n literal string or a macro preceeded by the '$'-operator. The\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -1,38 +1,36 @@\n [HTP]\n *\b**\b**\b**\b**\b**\b* h\bht\btp\bp o\bon\bn-\b-l\bli\bin\bne\be r\bre\bef\bfe\ber\bre\ben\bnc\bce\be :\b: I\bIN\bNC\bC *\b**\b**\b**\b**\b**\b*\n _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs *\b**\b**\b**\b**\b* s\bsy\byn\bnt\bta\bax\bx *\b**\b**\b**\b**\b*\n-\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bF_\bI_\bL_\bE INCLUDE=\"include.hti\" name=\"Jim\n-\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be Nelson\" email=\"jnelson@crl.com\">\n-\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl \u00a0 \u00a0 This tag will fail: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bU_\bS_\bE name>\n-\u00a0 _\bU_\bs_\ba_\bg_\be *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n-\u00a0 HTP Tags The I\bIN\bNC\bC can be used for incrementing/decrementing a\n-\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT variable or for variable addition. The basic form\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK is shown above.\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF The \"increment\" is anything that evaluates to a\n-\u00a0 \u00a0 _\bD_\bE_\bF integer. It can be a literal string or a macro\n-\u00a0 \u00a0 _\bF_\bI_\bL_\bE preceeded by the '$'-operator. The macroname must\n-\u00a0 \u00a0 _\bI_\bF be the name of a defined macro that contains an\n-\u00a0 [>] _\bI_\bN_\bC integer. If the increment is ommitted it defaults\n-\u00a0 \u00a0 _\bI_\bM_\bG to 1. The effect of this operation is that the\n-\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL macro is redefined to contain the sum of its\n-\u00a0 \u00a0 _\bO_\bP_\bT previous value and its increment.\n-\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT To increment or decrement a variable you can use\n-\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE this form:\n-\u00a0 \u00a0 _\bS_\bE_\bT \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bN_\bC i=\"1\" j=\"-1\">\n-\u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF Note that INC doesn't check if the strings really\n-\u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT denote integers. It may give weired results when\n-\u00a0 \u00a0 _\bU_\bS_\bE_\b,_\b _\b$ used on arbitrary strings. The integer values are\n-\u00a0 \u00a0 _\bW_\bH_\bI_\bL_\bE limited to the range -2^31..2^31.\n-\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b- Note further that htp wasn't designed to do\n-\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by extensive calculations. The INC tag is useful in\n-\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt conjunction with WHILE to iterate over the defined\n-\u00a0 _\bB_\bu_\bg_\bs blocks.\n-\n-\n+\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bF name=\"Jim\">...<_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bI_\bF>\n+\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n+\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl The I\bIN\bNC\bC can be used for incrementing/decrementing a\n+\u00a0 _\bU_\bs_\ba_\bg_\be variable or for variable addition. The basic form\n+\u00a0 HTP Tags is shown above.\n+\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT The \"increment\" is anything that evaluates to a\n+\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK integer. It can be a literal string or a macro\n+\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF preceeded by the '$'-operator. The macroname must\n+\u00a0 \u00a0 _\bD_\bE_\bF be the name of a defined macro that contains an\n+\u00a0 \u00a0 _\bF_\bI_\bL_\bE integer. If the increment is ommitted it defaults\n+\u00a0 \u00a0 _\bI_\bF to 1. The effect of this operation is that the\n+\u00a0 [>] _\bI_\bN_\bC macro is redefined to contain the sum of its\n+\u00a0 \u00a0 _\bI_\bM_\bG previous value and its increment.\n+\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL To increment or decrement a variable you can use\n+\u00a0 \u00a0 _\bO_\bP_\bT this form:\n+\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bN_\bC i=\"1\" j=\"-1\">\n+\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE Note that INC doesn't check if the strings really\n+\u00a0 \u00a0 _\bS_\bE_\bT denote integers. It may give weired results when\n+\u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF used on arbitrary strings. The integer values are\n+\u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT limited to the range -2^31..2^31.\n+\u00a0 \u00a0 _\bU_\bS_\bE_\b,_\b _\b$ Note further that htp wasn't designed to do\n+\u00a0 \u00a0 _\bW_\bH_\bI_\bL_\bE extensive calculations. The INC tag is useful in\n+\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b- conjunction with WHILE to iterate over the defined\n+\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by blocks.\n+\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt\n+\u00a0 _\bB_\bu_\bg_\bs\n \n \n \n \n \n \n \n"}]}, {"source1": "./usr/share/doc/htp/metatag.html", "source2": "./usr/share/doc/htp/metatag.html", "unified_diff": "@@ -88,18 +88,22 @@\n
Metatags are defined with the def and blockdef tags and\n undefined with the undef tag.
\n As an example we show how to define a tag that builds a\n fancy horizontal rule out of several images.\n
\n\n- 1. <OUTPUT FILE=\"outputfilename\" [APPEND] [EXPAND]>
\n- 2. text block
\n- 3. </OUTPUT>
\n- 4.
\n+ 1. <OPT (IMGXY|NOIMGXY)>
\n+ 2. <OPT (QUIET|VERBOSE)>
\n+ 3. <OPT (DEPEND|NODEPEND)>
\n+ 4. <OPT (PRECIOUS|NOPRECIOUS)>
\n+ 5. <OPT (CONDENSE|SEMICONDENSE|NOCONDENSE)>
\n+ 6. <OPT DELIM=(HTML|SQUARE|CURLY)>
\n+ 7. <OPT (XML|XML=FALSE)>
\n+ 8.
\n
In line 1 of the above example a new tag named imghr is defined.\n The html code which implements this rule is following in lines 2-8.\n between the def and\n /def tags. You don't have to understand this\n html code, but you should understand that this is just pure html to\n draw the fancy rule. Every time you write <imghr>\n@@ -109,39 +113,44 @@\n file.
Often you want to define tags that have an opening and a closing\n variant. For this purpose you should use the blockdef tag. When htp\n encounters a blockdef tag it will automatically search for the\n matching closing tag and put everything between these tags in a block\n macro named block. Here is an example for this.
\n- 1. <SET macroname1=\"macrovalue1\" [macroname2=\"macrovalue2\" ...] [GLOBAL]>
\n- 2.
\n+ 1. <blockdef name=\"bolditalic\">
\n+ 2. <b><i>
\n+ 3. <use block>
\n+ 4. </i></b>
\n+ 5. </blockdef>
\n+ 6.
\n+ 7. This is <bolditalic>bold and italic</bolditalic>
\n
More sophisticated tags accept parameters. The\n option parameter lets multiple metatag parameters be\n named and expanded inside the def or\n blockdef block:
\n- 1. <unset macroname>
\n- 2. <unset macroname1 macroname2 ... >
\n- 3.
\n+ 1. <def name=\"sharedimg\" option=\"name alt\">
\n+ 2. <img src=\"/home/sharedimages/${name}\" alt=\"${alt}\">;
\n+ 3. </def>
\n+ 4.
\n+ 5. <sharedimg name=\"bubble.gif\" alt=\"Bubble image\">
\n
When you are using templates, the html should only be written by\n the template file. The normal htp files should just define macros\n that are used later in the template. So you may want to write block\n tags that just save the block in a macro for later use. Although this\n is possible with htp it is quite tricky, so here we present the way to\n do this:
\n\n- 1. <use macroname [parameters ...] [noexpand]>
\n- 2. <... $macroname ...>
\n- 3. <... ${macroname} ...>
\n- 4.
\n+ 1. <QUOTE TAG [ATTRIBUTE=VALUE ...]>
\n+ 2.
\n
This defines a block macro named section. This macro uses a\n counter sect-ctr that enumerates the sections. It is\n increased for every section (line 3) and then the block macro name is\n build from this counter. So the first section is stored in block\n sect-1, the second in sect-2 and so on. The global flag\n in line 4 tells htp that these macros should be defined globally\n@@ -160,18 +169,21 @@\n contents of block to be expanded twice. If you omit it, it would be\n expanded when defining the sect-1 macro and when using it later in the\n template. Generally it is a good idea to use noexpand whenever you\n use expand in a block around it.
To close this example we show how to expand the\n sect-${sect-ctr} blocks in the template:
\n- 1. <WHILE [NOT] conditional>
\n- 2. block
\n- 3. </WHILE>
\n- 4.
\n+ 1. <file include=\"header.hti\">
\n+ 2. <set sect-ctr=\"1\">
\n+ 3. <while sect-${sect-ctr}>
\n+ 4. <use sect-${sect-ctr}>
\n+ 5. <inc sect-ctr>
\n+ 6. </while>
\n+ 7. <file include=\"footer.hti\">
\n
\n The while tag in line 3 checks whether\n the macro sect-${sect-ctr} is defined. If it is defined the body is\n evaluated, which expands the macro and increases sect-ctr. Afterwards\n the while condition is checked again to check for sect-2 macro. This\n repeats until sect-${sect-ctr} is not defined.\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -9,19 +9,22 @@\n \u00a0 \u00a0 _\bT_\be_\bm_\bp_\bl_\ba_\bt_\be_\bs functionality.\n \u00a0 \u00a0 _\bF_\bi_\bl_\be_\bs Metatags are defined with the _\b[_\b[_\br_\be_\bf_\b]_\b]_\bd_\be_\bf and _\b[\n \u00a0 [>] _\bM_\be_\bt_\ba_\bt_\ba_\bg_\bs _\b[_\br_\be_\bf_\b]_\b]_\bb_\bl_\bo_\bc_\bk_\bd_\be_\bf tags and undefined with the _\b[\n \u00a0 _\bU_\bs_\ba_\bg_\be _\b[_\br_\be_\bf_\b]_\b]_\bu_\bn_\bd_\be_\bf tag.\n \u00a0 _\bH_\bT_\bP_\b _\bT_\ba_\bg_\bs As an example we show how to define a tag that\n \u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by builds a fancy horizontal rule out of several\n \u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt images.\n-\u00a0 _\bB_\bu_\bg_\bs \u00a01. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bO_\bU_\bT_\bP_\bU_\bT FILE=\"outputfilename\" [APPEND]\n- [EXPAND]>\n- \u00a02. text block\n- \u00a03. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bO_\bU_\bT_\bP_\bU_\bT>\n- \u00a04.\n+\u00a0 _\bB_\bu_\bg_\bs \u00a01. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bO_\bP_\bT (IMGXY|NOIMGXY)>\n+ \u00a02. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bO_\bP_\bT (QUIET|VERBOSE)>\n+ \u00a03. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bO_\bP_\bT (DEPEND|NODEPEND)>\n+ \u00a04. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bO_\bP_\bT (PRECIOUS|NOPRECIOUS)>\n+ \u00a05. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bO_\bP_\bT (CONDENSE|SEMICONDENSE|NOCONDENSE)>\n+ \u00a06. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bO_\bP_\bT DELIM=(HTML|SQUARE|CURLY)>\n+ \u00a07. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bO_\bP_\bT (XML|XML=FALSE)>\n+ \u00a08.\n In line 1 of the above example a new tag named\n imghr is defined. The html code which implements\n this rule is following in lines 2-8. between the _\b[\n _\b[_\br_\be_\bf_\b]_\b]_\bd_\be_\bf_\b _\ba_\bn_\bd_\b _\b/_\bd_\be_\bf tags. You don't have to\n understand this html code, but you should\n understand that this is just pure html to draw the\n fancy rule. Every time you write
\n- <blockdef name=\"bolditalic\">
\n- <b><i>
\n- <use block>
\n- </i></b>
\n- </blockdef>
\n+ <def name=\"sharedimg\" option=\"name alt\">
\n+ <img src=\"/home/sharedimages/${name}\" alt=\"${alt}\">;
\n+ </def>
\n
\n- This is <bolditalic>bold and italic</bolditalic>
\n+ <sharedimg name=\"bubble.gif\" alt=\"Bubble image\">
\n
\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -1,25 +1,25 @@\n [HTP]\n *\b**\b**\b**\b**\b**\b* h\bht\btp\bp o\bon\bn-\b-l\bli\bin\bne\be r\bre\bef\bfe\ber\bre\ben\bnc\bce\be :\b: O\bOP\bPT\bT *\b**\b**\b**\b**\b**\b*\n _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs *\b**\b**\b**\b**\b* s\bsy\byn\bnt\bta\bax\bx *\b**\b**\b**\b**\b*\n-\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bb_\bl_\bo_\bc_\bk_\bd_\be_\bf name=\"bolditalic\">\n-\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be \u00a0 \u00a0 \n-\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bu_\bs_\be block>\n-\u00a0 _\bU_\bs_\ba_\bg_\be \u00a0 \u00a0 \n-\u00a0 HTP Tags \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bb_\bl_\bo_\bc_\bk_\bd_\be_\bf>\n-\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK \u00a0 This is
\n-<SET macroname1=\"macrovalue1\" [macroname2=\"macrovalue2\" ...] [GLOBAL]>
\n+<OUTPUT FILE=\"outputfilename\" [APPEND] [EXPAND]>
\n+text block
\n+</OUTPUT>
\n
\n
The OUTPUT tag can be used to create auxillary\n files besides the main HTML file. The text between this tag and the\n corresponding </OUTPUT> tag is written to output file.
\nNormally the outputfile is cleared before writing to it, but you\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -1,27 +1,27 @@\n [HTP]\n *\b**\b**\b**\b**\b**\b* h\bht\btp\bp o\bon\bn-\b-l\bli\bin\bne\be r\bre\bef\bfe\ber\bre\ben\bnc\bce\be :\b: O\bOU\bUT\bTP\bPU\bUT\bT *\b**\b**\b**\b**\b**\b*\n _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs *\b**\b**\b**\b**\b* s\bsy\byn\bnt\bta\bax\bx *\b**\b**\b**\b**\b*\n-\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bS_\bE_\bT macroname1=\"macrovalue1\"\n-\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be [macroname2=\"macrovalue2\" ...] [GLOBAL]>\n-\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl\n-\u00a0 _\bU_\bs_\ba_\bg_\be *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n-\u00a0 HTP Tags The O\bOU\bUT\bTP\bPU\bUT\bT tag can be used to create auxillary\n-\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT files besides the main HTML file. The text between\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK this tag and the corresponding tag is\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF written to output file.\n-\u00a0 \u00a0 _\bD_\bE_\bF Normally the outputfile is cleared before writing\n-\u00a0 \u00a0 _\bF_\bI_\bL_\bE to it, but you can use the APPEND attribute to\n-\u00a0 \u00a0 _\bI_\bF extend an existing file. The text written to the\n-\u00a0 \u00a0 _\bI_\bN_\bC file is normally not expanded, i.e. all tags inside\n-\u00a0 \u00a0 _\bI_\bM_\bG this block are not executed but written unmodified\n-\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL to the file. However, you can use the _\bE_\bX_\bP_\bA_\bN_\bD\n-\u00a0 \u00a0 _\bO_\bP_\bT attribute to override this behaviour.\n-\u00a0 [>] _\bO_\bU_\bT_\bP_\bU_\bT\n-\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE\n+\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bO_\bU_\bT_\bP_\bU_\bT FILE=\"outputfilename\" [APPEND]\n+\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be [EXPAND]>\n+\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl text block\n+\u00a0 _\bU_\bs_\ba_\bg_\be <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bO_\bU_\bT_\bP_\bU_\bT>\n+\u00a0 HTP Tags\n+\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n+\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK The O\bOU\bUT\bTP\bPU\bUT\bT tag can be used to create auxillary\n+\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF files besides the main HTML file. The text between\n+\u00a0 \u00a0 _\bD_\bE_\bF this tag and the corresponding tag is\n+\u00a0 \u00a0 _\bF_\bI_\bL_\bE written to output file.\n+\u00a0 \u00a0 _\bI_\bF Normally the outputfile is cleared before writing\n+\u00a0 \u00a0 _\bI_\bN_\bC to it, but you can use the APPEND attribute to\n+\u00a0 \u00a0 _\bI_\bM_\bG extend an existing file. The text written to the\n+\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL file is normally not expanded, i.e. all tags inside\n+\u00a0 \u00a0 _\bO_\bP_\bT this block are not executed but written unmodified\n+\u00a0 [>] _\bO_\bU_\bT_\bP_\bU_\bT to the file. However, you can use the _\bE_\bX_\bP_\bA_\bN_\bD\n+\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE attribute to override this behaviour.\n \u00a0 \u00a0 _\bS_\bE_\bT\n \u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF\n \u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT\n \u00a0 \u00a0 _\bU_\bS_\bE_\b,_\b _\b$\n \u00a0 \u00a0 _\bW_\bH_\bI_\bL_\bE\n \u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b-\n \u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by\n@@ -30,14 +30,16 @@\n \n \n \n \n \n \n \n+\n+\n \n \n \u00a0 _\bp_\ba_\bg_\be_\b _\bs_\bo_\bu_\br_\bc_\be\n \u00a0 _\bh_\bt_\bp_\b _\bp_\br_\bo_\bj_\be_\bc_\bt\n \u00a0 _\bh_\bt_\bp_\b _\bh_\bo_\bm_\be_\bp_\ba_\bg_\be\n hosted by\n _\bS_\bo_\bu_\br_\bc_\be_\bf_\bo_\br_\bg_\be\n"}]}, {"source1": "./usr/share/doc/htp/set.html", "source2": "./usr/share/doc/htp/set.html", "unified_diff": "@@ -114,31 +114,24 @@\n Bugs
\n- <def name=\"sharedimg\" option=\"name alt\">
\n- <img src=\"/home/sharedimages/${name}\" alt=\"${alt}\">;
\n- </def>
\n+<SET macroname1=\"macrovalue1\" [macroname2=\"macrovalue2\" ...] [GLOBAL]>
\n
\n- <sharedimg name=\"bubble.gif\" alt=\"Bubble image\">
\n
\n- <set sect-ctr=\"0\">
\n- <blockdef name=\"section\">
\n- <inc sect-ctr>
\n- <block name=\"sect-${sect-ctr}\" expand global>
\n- <use block noexpand>
\n- </block>
\n- </blockdef>
\n+<UNDEF tagname>
\n+<UNDEF tagname1 tagname2 ... >
\n+
\n
\n The macro \"emailaddr\" can then be expanded later. The \n USE tag is used to expand the macro outside a tag (i.e., into the regular\n text). If the macro needs to be expanded inside a markup tag, use the\n '$' operator.\n
\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -1,44 +1,36 @@\n [HTP]\n *\b**\b**\b**\b**\b**\b* h\bht\btp\bp o\bon\bn-\b-l\bli\bin\bne\be r\bre\bef\bfe\ber\bre\ben\bnc\bce\be :\b: S\bSE\bET\bT *\b**\b**\b**\b**\b**\b*\n _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs *\b**\b**\b**\b**\b* s\bsy\byn\bnt\bta\bax\bx *\b**\b**\b**\b**\b*\n-\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bd_\be_\bf name=\"sharedimg\" option=\"name alt\">\n-\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bm_\bg src=\"/home/sharedimages/${name}\"\n-\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl alt=\"${alt}\">;\n-\u00a0 _\bU_\bs_\ba_\bg_\be \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bd_\be_\bf>\n-\u00a0 HTP Tags\n-\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT \u00a0
\n- <set sect-ctr=\"0\">
\n- <blockdef name=\"section\">
\n- <inc sect-ctr>
\n- <block name=\"sect-${sect-ctr}\" expand global>
\n- <use block noexpand>
\n- </block>
\n- </blockdef>
\n+<unset macroname>
\n+<unset macroname1 macroname2 ... >
\n+
\n
UNDEF removes a metatag definition. Metatags\n created by DEF and
\n For example:\n
\n-<a href=\"mailto:$email\">mailto hyperlink</a>
\n-<a href=\"http://$domain/~${username}/\">another hyperlink</a>
\n+<WHILE [NOT] conditional>
\n+ block
\n+</WHILE>
\n+
\n
\n More than one macro may be removed in the same tag:\n
\n- <unset email_addr home_url login_name>
\n+<block stuff>
\n+ <a href=$email>send email</a>
\n+</block>
\n+
\n+<set morestuff=$email>
\n+
\n+This works: <use stuff email=\"jnelson@crl.com\">
\n+But this fails: <use email>
\n+And this fails: <use morestuff email=\"jnelson@crl.com\">
\n
\n
\n-<file include=\"header.hti\">
\n- <set sect-ctr=\"1\">
\n- <while sect-${sect-ctr}>
\n- <use sect-${sect-ctr}>
\n- <inc sect-ctr>
\n- </while>
\n-<file include=\"footer.hti\">
\n+<WHILE [NOT] conditional>
\n+ block
\n+</WHILE>
\n+
\n
If you USE a block macro the value of expanded block macros will\n@@ -138,18 +135,23 @@\n attribute to prevent further expansion.
\n USE will accept additional parameters, which are \"local\" macros\n for the expanded macro. This is only valid for
\n- 1. <WHILE [NOT] conditional>
\n- 2. block
\n- 3. </WHILE>
\n+ 1. <block stuff>
\n+ 2. <a href=$email>send email</a>
\n+ 3. </block>
\n 4.
\n+ 5. <set morestuff=$email>
\n+ 6.
\n+ 7. This works: <use stuff email=\"jnelson@crl.com\">
\n+ 8. But this fails: <use email>
\n+ 9. And this fails: <use morestuff email=\"jnelson@crl.com\">
\n
\n (See below for a description of the '$' operator.) The example on\n line 7 works because \"stuff\" has been declared as a block macro, and\n the tag is passing the \"email\" macro to the \"stuff\" macro. Line 8\n fails because the \"email\" macro is unavailable once the block macro is\n completely expanded, and cannot be passed to a SET macro.\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -1,36 +1,40 @@\n [HTP]\n *\b**\b**\b**\b**\b**\b* h\bht\btp\bp o\bon\bn-\b-l\bli\bin\bne\be r\bre\bef\bfe\ber\bre\ben\bnc\bce\be :\b: U\bUS\bSE\bE,\b, $\b$ *\b**\b**\b**\b**\b**\b*\n _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs *\b**\b**\b**\b**\b* s\bsy\byn\bnt\bta\bax\bx *\b**\b**\b**\b**\b*\n-\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bf_\bi_\bl_\be include=\"header.hti\">\n-\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bs_\be_\bt sect-ctr=\"1\">\n-\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bw_\bh_\bi_\bl_\be sect-${sect-ctr}>\n-\u00a0 _\bU_\bs_\ba_\bg_\be \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bu_\bs_\be sect-${sect-ctr}>\n-\u00a0 HTP Tags \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bi_\bn_\bc sect-ctr>\n-\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bw_\bh_\bi_\bl_\be>\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bf_\bi_\bl_\be include=\"footer.hti\">\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n-\u00a0 \u00a0 _\bD_\bE_\bF U\bUS\bSE\bE will expand macros that have been previously\n-\u00a0 \u00a0 _\bF_\bI_\bL_\bE declared with either _\bS_\bE_\bT or _\bB_\bL_\bO_\bC_\bK. USE can only be\n-\u00a0 \u00a0 _\bI_\bF used outside of other markup tags.\n-\u00a0 \u00a0 _\bI_\bN_\bC If you USE a block macro the value of expanded\n-\u00a0 \u00a0 _\bI_\bM_\bG block macros will be further parsed by htp. This is\n-\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL maybe not what you want, for example, if the use is\n-\u00a0 \u00a0 _\bO_\bP_\bT inside a block which _\be_\bx_\bp_\ba_\bn_\bd_\bs itself. You can use\n-\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT the noexpand attribute to prevent further\n-\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE expansion.\n-\u00a0 \u00a0 _\bS_\bE_\bT USE will accept additional parameters, which are\n-\u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF \"local\" macros for the expanded macro. This is only\n-\u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT valid for _\bB_\bL_\bO_\bC_\bK macros. Macros created using _\bS_\bE_\bT\n-\u00a0 [>] _\bU_\bS_\bE_\b,_\b _\b$ cannot have parameters passed. For example:\n-\u00a0 \u00a0 _\bW_\bH_\bI_\bL_\bE \u00a01. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bW_\bH_\bI_\bL_\bE [NOT] conditional>\n-\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b- \u00a02. \u00a0 \u00a0 block\n-\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by \u00a03. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bW_\bH_\bI_\bL_\bE>\n-\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt \u00a04.\n-\u00a0 _\bB_\bu_\bg_\bs (See below for a description of the '$' operator.)\n+\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bW_\bH_\bI_\bL_\bE [NOT] conditional>\n+\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be \u00a0 \u00a0 block\n+\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bW_\bH_\bI_\bL_\bE>\n+\u00a0 _\bU_\bs_\ba_\bg_\be\n+\u00a0 HTP Tags *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n+\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT U\bUS\bSE\bE will expand macros that have been previously\n+\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK declared with either _\bS_\bE_\bT or _\bB_\bL_\bO_\bC_\bK. USE can only be\n+\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF used outside of other markup tags.\n+\u00a0 \u00a0 _\bD_\bE_\bF If you USE a block macro the value of expanded\n+\u00a0 \u00a0 _\bF_\bI_\bL_\bE block macros will be further parsed by htp. This is\n+\u00a0 \u00a0 _\bI_\bF maybe not what you want, for example, if the use is\n+\u00a0 \u00a0 _\bI_\bN_\bC inside a block which _\be_\bx_\bp_\ba_\bn_\bd_\bs itself. You can use\n+\u00a0 \u00a0 _\bI_\bM_\bG the noexpand attribute to prevent further\n+\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL expansion.\n+\u00a0 \u00a0 _\bO_\bP_\bT USE will accept additional parameters, which are\n+\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT \"local\" macros for the expanded macro. This is only\n+\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE valid for _\bB_\bL_\bO_\bC_\bK macros. Macros created using _\bS_\bE_\bT\n+\u00a0 \u00a0 _\bS_\bE_\bT cannot have parameters passed. For example:\n+\u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF \u00a01. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bb_\bl_\bo_\bc_\bk stuff>\n+\u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT \u00a02. \u00a0 send email\n+\u00a0 [>] _\bU_\bS_\bE_\b,_\b _\b$ \u00a03. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bb_\bl_\bo_\bc_\bk>\n+\u00a0 \u00a0 _\bW_\bH_\bI_\bL_\bE \u00a04.\n+\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b- \u00a05. <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bs_\be_\bt morestuff=$email>\n+\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by \u00a06.\n+\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt \u00a07. This works: \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bu_\bs_\be stuff\n+\u00a0 _\bB_\bu_\bg_\bs email=\"jnelson@crl.com\">\n+ \u00a08. But this fails: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bu_\bs_\be email>\n+ \u00a09. And this fails: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bu_\bs_\be morestuff\n+ email=\"jnelson@crl.com\">\n+ (See below for a description of the '$' operator.)\n The example on line 7 works because \"stuff\" has\n been declared as a block macro, and the tag is\n passing the \"email\" macro to the \"stuff\" macro.\n Line 8 fails because the \"email\" macro is\n unavailable once the block macro is completely\n expanded, and cannot be passed to a SET macro.\n Note that the \"email\" macro is available to other\n"}]}, {"source1": "./usr/share/doc/htp/while.html", "source2": "./usr/share/doc/htp/while.html", "unified_diff": "@@ -114,15 +114,23 @@\n Bugs
\n- <unset email_addr home_url login_name>
\n+<block stuff>
\n+ <a href=$email>send email</a>
\n+</block>
\n+
\n+<set morestuff=$email>
\n+
\n+This works: <use stuff email=\"jnelson@crl.com\">
\n+But this fails: <use email>
\n+And this fails: <use morestuff email=\"jnelson@crl.com\">
\n
\n \"Conditional\" is either a \"compare\" or \"is defined\" operation.\n A compare operator is a test of the value of a macro against a literal string.\n", "details": [{"source1": "html2text {}", "source2": "html2text {}", "unified_diff": "@@ -1,36 +1,46 @@\n [HTP]\n *\b**\b**\b**\b**\b**\b* h\bht\btp\bp o\bon\bn-\b-l\bli\bin\bne\be r\bre\bef\bfe\ber\bre\ben\bnc\bce\be :\b: W\bWH\bHI\bIL\bLE\bE *\b**\b**\b**\b**\b**\b*\n _\bT_\ba_\bb_\bl_\be_\b _\bo_\bf_\b _\bC_\bo_\bn_\bt_\be_\bn_\bt_\bs *\b**\b**\b**\b**\b* s\bsy\byn\bnt\bta\bax\bx *\b**\b**\b**\b**\b*\n-\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bu_\bn_\bs_\be_\bt email_addr home_url login_name>\n-\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n-\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl W\bWH\bHI\bIL\bLE\bE is the building block for repeated\n-\u00a0 _\bU_\bs_\ba_\bg_\be processing. The basic form is shown above.\n-\u00a0 HTP Tags \"Conditional\" is either a \"compare\" or \"is defined\"\n-\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT operation. A compare operator is a test of the\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK value of a macro against a literal string. If the\n-\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF NOT tag is present in the WHILE markup, the\n-\u00a0 \u00a0 _\bD_\bE_\bF evaluation of the conditional is reversed:\n-\u00a0 \u00a0 _\bF_\bI_\bL_\bE \u00a0 \u00a0 <${tagName} ${attrName}=${value$ctr}>\n-\u00a0 \u00a0 _\bI_\bF Just as with _\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bF you can also check for a\n-\u00a0 \u00a0 _\bI_\bN_\bC macro's existance:\n-\u00a0 \u00a0 _\bI_\bM_\bG \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bW_\bH_\bI_\bL_\bE sect-$i>\n-\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL \u00a0 \u00a0 ...\n-\u00a0 \u00a0 _\bO_\bP_\bT \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bN_\bC i>\n-\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bW_\bH_\bI_\bL_\bE>\n-\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE If the condition is true, the block is evaluated\n-\u00a0 \u00a0 _\bS_\bE_\bT and afterwards the WHILE tag is evaluated again. If\n-\u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF the '$'-operator is used in the WHILE tag it is\n-\u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT also reevaluated on each iteration.\n-\u00a0 \u00a0 _\bU_\bS_\bE_\b,_\b _\b$ A loop block m\bmu\bus\bst\bt be closed with the /WHILE tag.\n-\u00a0 [>] _\bW_\bH_\bI_\bL_\bE\n-\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b-\n-\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by\n-\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt\n-\u00a0 _\bB_\bu_\bg_\bs\n+\u00a0 _\bI_\bn_\bt_\br_\bo_\bd_\bu_\bc_\bt_\bi_\bo_\bn <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bb_\bl_\bo_\bc_\bk stuff>\n+\u00a0 _\bL_\bi_\bc_\be_\bn_\bs_\be \u00a0 send email\n+\u00a0 _\bT_\bu_\bt_\bo_\br_\bi_\ba_\bl <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bb_\bl_\bo_\bc_\bk>\n+\u00a0 _\bU_\bs_\ba_\bg_\be\n+\u00a0 HTP Tags <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bs_\be_\bt morestuff=$email>\n+\u00a0 \u00a0 _\bA_\bL_\bT_\bT_\bE_\bX_\bT\n+\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK This works: \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bu_\bs_\be stuff\n+\u00a0 \u00a0 _\bB_\bL_\bO_\bC_\bK_\bD_\bE_\bF email=\"jnelson@crl.com\">\n+\u00a0 \u00a0 _\bD_\bE_\bF But this fails: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bu_\bs_\be email>\n+\u00a0 \u00a0 _\bF_\bI_\bL_\bE And this fails: <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bu_\bs_\be morestuff\n+\u00a0 \u00a0 _\bI_\bF email=\"jnelson@crl.com\">\n+\u00a0 \u00a0 _\bI_\bN_\bC *\b**\b**\b**\b**\b* s\bsy\byn\bno\bop\bps\bsi\bis\bs *\b**\b**\b**\b**\b*\n+\u00a0 \u00a0 _\bI_\bM_\bG W\bWH\bHI\bIL\bLE\bE is the building block for repeated\n+\u00a0 \u00a0 _\bI_\bM_\bA_\bG_\bE_\bU_\bR_\bL processing. The basic form is shown above.\n+\u00a0 \u00a0 _\bO_\bP_\bT \"Conditional\" is either a \"compare\" or \"is defined\"\n+\u00a0 \u00a0 _\bO_\bU_\bT_\bP_\bU_\bT operation. A compare operator is a test of the\n+\u00a0 \u00a0 _\bQ_\bU_\bO_\bT_\bE value of a macro against a literal string. If the\n+\u00a0 \u00a0 _\bS_\bE_\bT NOT tag is present in the WHILE markup, the\n+\u00a0 \u00a0 _\bU_\bN_\bD_\bE_\bF evaluation of the conditional is reversed:\n+\u00a0 \u00a0 _\bU_\bN_\bS_\bE_\bT \u00a0 \u00a0 <${tagName} ${attrName}=${value$ctr}>\n+\u00a0 \u00a0 _\bU_\bS_\bE_\b,_\b _\b$ Just as with _\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bF you can also check for a\n+\u00a0 [>] _\bW_\bH_\bI_\bL_\bE macro's existance:\n+\u00a0 \u00a0 _\b<_\b!_\b-_\b-_\b- \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bW_\bH_\bI_\bL_\bE sect-$i>\n+\u00a0 _\bH_\bi_\bs_\bt_\bo_\br_\by \u00a0 \u00a0 ...\n+\u00a0 _\bW_\bi_\bs_\bh_\b _\bl_\bi_\bs_\bt \u00a0 \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\bI_\bN_\bC i>\n+\u00a0 _\bB_\bu_\bg_\bs \u00a0 <_\b[_\b[_\br_\be_\bf_\b]_\b]_\b/_\bW_\bH_\bI_\bL_\bE>\n+ If the condition is true, the block is evaluated\n+ and afterwards the WHILE tag is evaluated again. If\n+ the '$'-operator is used in the WHILE tag it is\n+ also reevaluated on each iteration.\n+ A loop block m\bmu\bus\bst\bt be closed with the /WHILE tag.\n+\n+\n+\n+\n+\n \n \n \n \n \n \n \n"}]}]}]}]}]}