[interchange-docs] xmldocs - docelic modified 20 files

docs at icdevgroup.org docs at icdevgroup.org
Thu Oct 19 15:29:56 EDT 2006


User:      docelic
Date:      2006-10-19 19:29:56 GMT
Modified:  .        TODO
Modified:  docbook  literals.ent
Modified:  glossary ActionMap
Modified:  refs     AccumulateCode ActionMap AddDirective AdminUser
Modified:           AliasTable AsciiTrack AutoModifier AutoVariable
Modified:           Autoload Capability CartTrigger CartTriggerQuantity
Modified:           Catalog CatalogUser CategoryField CheckHTML
Modified:           ChildLife
Log:
docbook/literals.ent: Added entity ≥ - "glossary entry"
refs/*: simplified synopsis line, improved wording and linking

Revision  Changes    Path
1.97      +3 -0      xmldocs/TODO


rev 1.97, prev_rev 1.96
Index: TODO
===================================================================
RCS file: /var/cvs/xmldocs/TODO,v
retrieving revision 1.96
retrieving revision 1.97
diff -u -r1.96 -r1.97
--- TODO	28 Sep 2006 16:34:55 -0000	1.96
+++ TODO	19 Oct 2006 19:29:54 -0000	1.97
@@ -1,3 +1,5 @@
+- swish breaks description if it contains "
+- order counter, Session->{mv_order_number}, cronjob -0001, or file da-te.counter, or session_id.time
 - in iccattut, s/item-field/item-param/ at least on some places. 
 - Make xmldocs tarball in ftp autoupdated
 - Change -latest to version number in tarball download
@@ -11,6 +13,7 @@
 - make See Also only go two or three levels recursively. Currently we do it
   until the "chain" ends, which results in having many unrelated options
   listed under See Also.
+- in search.xml replace mv_ listitems with sections so they're listed in TOC
 
 Outstanding:
 =======



1.40      +1 -0      xmldocs/docbook/literals.ent


rev 1.40, prev_rev 1.39
Index: literals.ent
===================================================================
RCS file: /var/cvs/xmldocs/docbook/literals.ent,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- literals.ent	12 Oct 2006 13:46:53 -0000	1.39
+++ literals.ent	19 Oct 2006 19:29:54 -0000	1.40
@@ -107,6 +107,7 @@
 <!ENTITY TAB_DELIMITED_NOTICE "You might notice that the fields names and
 values above are not properly aligned. This is an unfortunate nature of
 &glos-tab-delimited; files.">
+<!ENTITY GE "glossary entry">
 
 <!-- GLOSSARY LINKS ARE AUTOMATIC -->
 



1.6       +19 -2     xmldocs/glossary/ActionMap


rev 1.6, prev_rev 1.5
Index: ActionMap
===================================================================
RCS file: /var/cvs/xmldocs/glossary/ActionMap,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- ActionMap	19 Nov 2005 22:37:40 -0000	1.5
+++ ActionMap	19 Oct 2006 19:29:54 -0000	1.6
@@ -1,10 +1,27 @@
-The standard process action has a number of associated FormAction settings. Besides using Perl, Interchange tags may be used in an action, though they are not nearly as efficient.
+&IC; allows you to create "virtual catalog pages" by associating 
+code (such as &PERL; subroutines) with parts of an URL. This can be
+used for anything from implementing one-click serches and orders
+to displaying on-the-fly data.
+</para><para>
+On every &glos-catalog; access, the leading part of a requested page path
+(URL) is taken and checked if it represents
+a valid <emphasis>action</emphasis>.
+If it does, the action name itself is removed from the
+path and invoked with the rest of the arguments provided in the URL.
+</para><para>
 
 Some of the predefined actions (which you might recognize from special
 page names that you access in your catalog) are:
 <itemizedlist>
 <listitem><para>
-<literal>process</literal> - Perform a processing function
+<literal>process</literal> - Generic form processing function.
+
+<!-- 
+Besides using Perl, Interchange tags may be used in an action, though they are not nearly as efficient.
+^^- only process or all actions?
+
+pointers to all variables it honors.
+-->
 </para></listitem>
 <listitem><para>
 <literal>order</literal>  -  Order items



1.5       +2 -0      xmldocs/refs/AccumulateCode


rev 1.5, prev_rev 1.4
Index: AccumulateCode
===================================================================
RCS file: /var/cvs/xmldocs/refs/AccumulateCode,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- AccumulateCode	12 Oct 2006 13:51:35 -0000	1.4
+++ AccumulateCode	19 Oct 2006 19:29:54 -0000	1.5
@@ -14,6 +14,7 @@
 __NAME__ description
 The directive instructs &IC; to fetch code blocks "on-demand" from the
 &conf-CodeRepository; instead of starting up with everything.
+It helps speed up &IC; startup time and reduce memory footprint.
 </para><para>
 So, at runtime, when particular functionality is needed but is not
 yet present in the running &IC; installation, it is copied from 
@@ -26,6 +27,7 @@
 again).
 </para><para>
 Over time, as you access pages and routines, a full set of tags
+used by a &glos-catalog;
 will be copied to the accumulated directory, and you will then be
 able to turn &conf-AccumulateCode; off.
 (In fact, &conf-AccumulateCode; is recommended for development and should 



1.5       +2 -6      xmldocs/refs/ActionMap


rev 1.5, prev_rev 1.4
Index: ActionMap
===================================================================
RCS file: /var/cvs/xmldocs/refs/ActionMap,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- ActionMap	12 Oct 2006 13:51:35 -0000	1.4
+++ ActionMap	19 Oct 2006 19:29:54 -0000	1.5
@@ -17,12 +17,8 @@
 
 
 __NAME__ description
-The directive allows the definition of Interchange &glos-ActionMap;s, whose
+The directive allows definition of Interchange &glos-ActionMap;s, whose
 contents are usually &PERL; subroutines.
-</para><para>
-The leading part of the incoming page path is taken and checked if it represents
-a valid action. If it does, the action name itself will be stripped from the
-path, and the appropriate action will be called with the rest of the argument.
 __END__
 
 __NAME__ notes
@@ -42,7 +38,7 @@
 __END__
 
 __NAME__ missing
-In the example, I provided some erroneous comment.
+In the example, I provided some erroneous comment (the part about [area].. equal to [page]...
 Also fix description and add synopsis
 __END__
 



1.5       +3 -4      xmldocs/refs/AddDirective


rev 1.5, prev_rev 1.4
Index: AddDirective
===================================================================
RCS file: /var/cvs/xmldocs/refs/AddDirective,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- AddDirective	12 Oct 2006 13:51:35 -0000	1.4
+++ AddDirective	19 Oct 2006 19:29:54 -0000	1.5
@@ -14,11 +14,10 @@
 __NAME__ description
 This directive allows you to extend the set of regular
 &glos-configuration;
-directives accepted in each &ccf; with your custom ones. The added 
+directives accepted in each &ccf;. The added 
 directives are then treated the same as the existing "built-ins".
 </para><para>
-Three standard arguments can be specified, just as you can see in 
-<filename>lib/Vend/Config.pm</filename>: the 
+Three standard arguments can be specified: the 
 <literal>directive_name</literal>, 
 <literal>parse_function_name</literal> and
 <literal>default_value</literal>.
@@ -36,7 +35,7 @@
 The file <filename>lib/Vend/Config.pm</filename> contains all the default 
 parser functions, which are recognized by the mandatory prefix
 <literal>parse_</literal>. (You do not, however, include
-<literal>parse_</literal> in the <literal>parse_function_name</literal>.
+<literal>parse_</literal> in the <literal>parse_function_name</literal>.)
 </para><para>
 The <literal>default_value</literal> does not have to be specified.
 </para><para>



1.3       +1 -3      xmldocs/refs/AdminUser


rev 1.3, prev_rev 1.2
Index: AdminUser
===================================================================
RCS file: /var/cvs/xmldocs/refs/AdminUser,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- AdminUser	12 Oct 2006 13:51:35 -0000	1.2
+++ AdminUser	19 Oct 2006 19:29:54 -0000	1.3
@@ -10,8 +10,6 @@
 __END__
 
 __NAME__ missing
-everything
+everything, see Util.pm
 __END__
 
-
-See Util.pm 



1.3       +1 -1      xmldocs/refs/AliasTable


rev 1.3, prev_rev 1.2
Index: AliasTable
===================================================================
RCS file: /var/cvs/xmldocs/refs/AliasTable,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- AliasTable	12 Oct 2006 13:51:35 -0000	1.2
+++ AliasTable	19 Oct 2006 19:29:54 -0000	1.3
@@ -43,7 +43,7 @@
 back to the index page.
 </para><para>
 To minimize the chance of confusion, you can download properly composed
-<ulink url="files/various/alias.txt">alias.txt</ulink>.
+example file <ulink url="files/various/alias.txt">alias.txt</ulink>.
 __END__
 
 



1.4       +2 -1      xmldocs/refs/AsciiTrack


rev 1.4, prev_rev 1.3
Index: AsciiTrack
===================================================================
RCS file: /var/cvs/xmldocs/refs/AsciiTrack,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- AsciiTrack	12 Oct 2006 13:51:35 -0000	1.3
+++ AsciiTrack	19 Oct 2006 19:29:54 -0000	1.4
@@ -4,7 +4,7 @@
 
 
 __NAME__ synopsis
-<arg choice='plain'>filename</arg>
+<arg choice='plain'><replaceable>filename</replaceable></arg>
 __END__
 
 
@@ -23,6 +23,7 @@
 
 __NAME__ missing
 Route is not set to supplant, route IS supplant, right?!
+Link to route discussion
 __END__
 
 __NAME__ example: Setting AsciiTrack



1.8       +27 -70    xmldocs/refs/AutoModifier


rev 1.8, prev_rev 1.7
Index: AutoModifier
===================================================================
RCS file: /var/cvs/xmldocs/refs/AutoModifier,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- AutoModifier	12 Oct 2006 13:51:35 -0000	1.7
+++ AutoModifier	19 Oct 2006 19:29:54 -0000	1.8
@@ -4,9 +4,9 @@
 
 
 __NAME__ missing
-fix examples (split to three)
 improve description based on syntax seen in examples
 in the examples, explain mv_sku lookup, not clear now
+incorporate NAME=table:column syntax in synopsis
 __END__
 
 
@@ -16,16 +16,19 @@
 
 __NAME__ synopsis
 <arg choice='plain' rep='repeat'>
-	<arg choice='opt'>table</arg>
+	<arg choice='opt'><replaceable>table</replaceable>:</arg>
 	<replaceable>column</replaceable>
-	<arg choice='opt'>key</arg>
+	<arg choice='opt'>:<replaceable>key</replaceable></arg>
 </arg>
 __END__
 
 
 __NAME__ description
 The directive specifies names of the product &glos-attribute;s 
-which should be automatically loaded from a database column.
+which should be automatically loaded from database columns.
+Table, column and key identifiers belonging to a single specification
+are separated by a colon (<literal>:</literal>), while multiple specifications
+are separated by whitespace.
 </para><para>
 In other words, 
 when an item is added to the shopping cart using &IC;'s routines, the
@@ -34,54 +37,23 @@
 </para><para>
 This facility will often be employed in determining product
 &glos-price;, &glos-discount;, &glos-tax;, &glos-shipping; amd 
-other custom attributes. In other words, these attributes will probably
+other custom attributes; these attributes will probably
 be used in custom &PERL; code that will scan the electronic
-&glos-cart; contents and perform some decisions.
+&glos-cart; contents and perform some decisions. For example, by defining
+database columns <database class='field'>heavy</database> and
+<database class='field'>downloadable</database>, you will be
+able to perform decisions
+based on <code>$item-&gt;{heavy}</code> and
+<code>$item-&gt;{downloadable}</code> (but there are more access methods,
+see the &gloss-attribute; &GE;.
+__END__
+
+
 <!--
-</para><para>
-There are several forms of the specification. The simplest is
-a field with no table specification:
-</para>
-<programlisting>
-AutoModifier heavy
-</programlisting>
-<para>
 This one has a bit of "magic" associated. To account for matrix-option
 products, the various product tables are searched, for both the item
 code and the base SKU associated with the item.
-</para><para>
-You can also rename the attribute to something different than the
-field:
-</para>
-<programlisting>
-	AutoModifier heavy=heavy_item
-</programlisting>
-<para>
-This would place the contents of the "heavy_item" field in the
-"heavy" attribute.
-</para><para>
-If you want to use a non-products table to load the modifier, you
-specify it in the usual Interchange colon-separated syntax:
-</para>
-<programlisting>
-	AutoModifier extra:heavy
-</programlisting>
-<para>
-This would look in the <database>extra</database> table for the
-"heavy" field.
-</para><para>
-You can also specify that another attribute holds the key for
-the modifier:
-</para>
-<programlisting>
-	AutoModifier extra:heavy:category
-</programlisting>
-<para>
-This would look in the <database>extra</database> table for the
-"heavy" field, using the "category" attribute in the item as
-the key.
 -->
-__END__
 
 __NAME__ notes
 This can useful when doing shipping calculations or in embedded
@@ -100,38 +72,23 @@
 <database class='field'>heavy</database> and 
 <database class='field'>downloadable</database> columns defined in your 
 <database>products</database> database.
-</para><para>
-Example: to set the heavy attribute from the 
-<database class='table'>inventory</database> table with the same
-key as the product code, do:
-<programlisting>
-AutoModifier inventory:heavy
-</programlisting>
-</para><para>
-Example: to set the heavy attribute from the <database
-class='field'>heavy</database> field in the <database
-class='table'>inventory</database> table with the same key as the product
-code, do:
+__END__
+
+__NAME__ example: set attribute 'heavy' from inventory table
 <programlisting>
 AutoModifier inventory:heavy
 </programlisting>
-</para><para>
-Example: to set the "weighty" attribute from the <database
-class='field'>heavy</database> field in the <database
-class='table'>inventory</database> table with the same key as the product
-code, do:
+__END__
+
+__NAME__ example: set attribute 'weighty' from inventory table, column 'heavy'
 <programlisting>
 AutoModifier weighty=inventory:heavy
 </programlisting>
-</para><para>
-Example: to set the heavy attribute from the <database
-class='field'>heavy</database> field in the <database
-class='table'>inventory</database> table with the the 
-base SKU for a variant, do:
+__END__
+
+__NAME__ example: set attribute 'heavy' from inventory table, with a different SKU
 <programlisting>
 AutoModifier inventory:heavy:mv_sku
 </programlisting>
-
 __END__
 
-TODO Fix example section



1.4       +9 -7      xmldocs/refs/AutoVariable


rev 1.4, prev_rev 1.3
Index: AutoVariable
===================================================================
RCS file: /var/cvs/xmldocs/refs/AutoVariable,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- AutoVariable	12 Oct 2006 13:51:35 -0000	1.3
+++ AutoVariable	19 Oct 2006 19:29:54 -0000	1.4
@@ -14,7 +14,7 @@
 __NAME__ description
 Specify list of &glos-configuration; directives that are to be automatically
 created as variable/value pairs. This allows you to conveniently
-write say, <code>__<replaceable>DIRECTIVENAME</replaceable>__</code> and 
+write say, <code>__<replaceable>DIRECTIVENAME</replaceable>__</code>, and 
 retrieve the corresponding configuration directive's value.
 </para><para>
 The above example, however, only works for scalar values. Since &IC; 
@@ -31,25 +31,27 @@
 indices/keys is translated properly.
 __END__
 
-__NAME__ example: Enabling AutoVariable
+__NAME__ example: Enabling configuration directives through Variable space
 Put the following in &ccf;:
 <programlisting>
-# The following two are present to form a standalone example
-SafeUntrap sort
-SysLog command /usr/bin/logger
+VendURL     http://&def-hostname;/cgi-bin/ic/catalog
+SecureURL   https://&def-hostname;/cgi-bin/ic/catalog
+MailOrderTo root@&def-domain;
+SafeUntrap  sort
+SysLog      command  /usr/bin/logger
 
 AutoVariable VendURL SecureURL MailOrderTo SafeUnutrap SysLog
 </programlisting>
 __END__
 
-__NAME__ example: Display a scalar value
+__NAME__ example: Displaying a scalar value
 Put the following on a page:
 <programlisting>
 Orders are e-mailed to: __MailOrderTo__
 </programlisting>
 __END__
 
-__NAME__ example: Display an array value
+__NAME__ example: Displaying an array value
 Put the following on a page:
 <programlisting>
 First SafeUntrap value is: __SafeUntrap_0__



1.3       +3 -2      xmldocs/refs/Autoload


rev 1.3, prev_rev 1.2
Index: Autoload
===================================================================
RCS file: /var/cvs/xmldocs/refs/Autoload,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Autoload	12 Oct 2006 13:51:35 -0000	1.2
+++ Autoload	19 Oct 2006 19:29:54 -0000	1.3
@@ -53,7 +53,7 @@
 submitting a &glos-HTML; form. At that point, <mv>mv_nextpage</mv>
 contains the name of the page to display next, of course.
 </para><para>
-The following would redirect accesses from
+The following would redirect all accesses from
 directory <filename class='directory'>public/</filename> to
 directory <filename class='directory'>private/</filename>:
 <programlisting><![CDATA[
@@ -66,7 +66,8 @@
 &glos-configuration; directives (global and catalog) are "re-instantiated",
 and valid for the current page. This particularly convenient feature
 allows us to change (modify, add or delete) configuration directives
-as we see fit, without worrying about them being persistent, and consequently,
+as we see fit on a per-page basis,
+without worrying about them being persistent, and consequently,
 even without the need to re-set them back to original values.
 </para><para>
 The following example (put in &ccf;) displays a different flypage for



1.4       +13 -8     xmldocs/refs/Capability


rev 1.4, prev_rev 1.3
Index: Capability
===================================================================
RCS file: /var/cvs/xmldocs/refs/Capability,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- Capability	21 May 2005 11:09:24 -0000	1.3
+++ Capability	19 Oct 2006 19:29:54 -0000	1.4
@@ -7,12 +7,10 @@
 __END__
 
 __NAME__ synopsis
-<group choice='req'>
-	<arg choice='plain' rep='repeat'>
-		<replaceable>type</replaceable>
-		<replaceable>type-specific value</replaceable>
-	</arg>
-</group>
+<arg choice='plain' rep='repeat'>
+	<replaceable>type</replaceable>
+	<replaceable>type-specific-value</replaceable>
+</arg>
 __END__
 
 
@@ -31,9 +29,16 @@
 <literal>module</literal> .
 __END__
 
-__NAME__ example: Testing for existence of Archive::Zip Perl module
+__NAME__ example: Testing for existence of two Perl modules
 <programlisting>
-Capability module Archive::Zip
+Capability module Archive::Zip module Set::Crontab
+</programlisting>
+__END__
+
+__NAME__ example: Testing for existence of two Perl modules
+<programlisting>
+Capability module LWP
+Capability module Safe
 </programlisting>
 __END__
 



1.2       +1 -3      xmldocs/refs/CartTrigger


rev 1.2, prev_rev 1.1
Index: CartTrigger
===================================================================
RCS file: /var/cvs/xmldocs/refs/CartTrigger,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- CartTrigger	14 Dec 2005 23:10:59 -0000	1.1
+++ CartTrigger	19 Oct 2006 19:29:54 -0000	1.2
@@ -12,9 +12,7 @@
 __END__
 
 __NAME__ synopsis
-<group choice='req'>
-	<arg choice='plain' rep='repeat'><replaceable>subroutine_name</replaceable></arg>
-</group>
+<arg choice='plain' rep='repeat'><replaceable>subroutine_name</replaceable></arg>
 __END__
 
 



1.2       +2 -4      xmldocs/refs/CartTriggerQuantity


rev 1.2, prev_rev 1.1
Index: CartTriggerQuantity
===================================================================
RCS file: /var/cvs/xmldocs/refs/CartTriggerQuantity,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- CartTriggerQuantity	14 Dec 2005 23:10:59 -0000	1.1
+++ CartTriggerQuantity	19 Oct 2006 19:29:54 -0000	1.2
@@ -8,10 +8,8 @@
 __END__
 
 __NAME__ synopsis
-<group choice='req'>
-	<arg choice='plain'>0</arg>
-	<arg choice='plain'>1</arg>
-</group>
+<arg choice='plain'>No</arg>
+<arg choice='plain'>Yes</arg>
 __END__
 
 



1.7       +8 -5      xmldocs/refs/Catalog


rev 1.7, prev_rev 1.6
Index: Catalog
===================================================================
RCS file: /var/cvs/xmldocs/refs/Catalog,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- Catalog	28 Jan 2006 13:45:52 -0000	1.6
+++ Catalog	19 Oct 2006 19:29:54 -0000	1.7
@@ -77,7 +77,7 @@
 Catalog simple1 /home/catalogs/simple1 www.company1.com/cgi-bin/ic/simple
 Catalog simple2 /home/catalogs/simple2 www.company2.com/cgi-bin/ic/simple
 </programlisting>
-Make sure to read the &conf-FullUrl; directive reference before just
+Make sure to read the &conf-FullUrl; directive reference page before just
 including it in your &glos-configuration;.
 __END__
 
@@ -101,8 +101,11 @@
 </programlisting>
 __END__
 
-TODO: Can catalog.cfg override cat-specific directives set in interchange.cfg ?
-TODO: How if catalog names supported regexps, so you could do like:
-      Catalog \S+  directive ErrorFile /var/log/interchange/$1-error.log
-      
+
+__NAME__ missing
+Can catalog.cfg override cat-specific directives set in interchange.cfg ?
+How if catalog names supported regexps, so you could do like: Catalog \S+  directive ErrorFile /var/log/interchange/$1-error.log
+List all possible hash keys used with Catalog
+Remove from NOTES line about undefined VendURL if we fixed the error msg
+ __END__
 



1.2       +1 -3      xmldocs/refs/CatalogUser


rev 1.2, prev_rev 1.1
Index: CatalogUser
===================================================================
RCS file: /var/cvs/xmldocs/refs/CatalogUser,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- CatalogUser	27 Jul 2005 17:19:13 -0000	1.1
+++ CatalogUser	19 Oct 2006 19:29:54 -0000	1.2
@@ -4,9 +4,7 @@
 
 
 __NAME__ synopsis
-<group choice='req' rep='repeat'>
-	<arg choice='plain'><replaceable>catalog_name username</replaceable></arg>
-</group>
+<arg choice='plain'><replaceable>catalog_name username</replaceable></arg>
 __END__
 
 



1.2       +1 -3      xmldocs/refs/CategoryField


rev 1.2, prev_rev 1.1
Index: CategoryField
===================================================================
RCS file: /var/cvs/xmldocs/refs/CategoryField,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- CategoryField	22 May 2005 10:21:28 -0000	1.1
+++ CategoryField	19 Oct 2006 19:29:54 -0000	1.2
@@ -4,9 +4,7 @@
 
 
 __NAME__ synopsis
-<group choice='req'>
-	<arg choice='plain'><replaceable>field_name</replaceable></arg>
-</group>
+<arg choice='plain'><replaceable>field_name</replaceable></arg>
 __END__
 
 



1.6       +2 -4      xmldocs/refs/CheckHTML


rev 1.6, prev_rev 1.5
Index: CheckHTML
===================================================================
RCS file: /var/cvs/xmldocs/refs/CheckHTML,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- CheckHTML	19 Nov 2005 22:37:41 -0000	1.5
+++ CheckHTML	19 Oct 2006 19:29:54 -0000	1.6
@@ -4,14 +4,12 @@
 
 
 __NAME__ missing
-Doesn't work, fix the code?
+Doesn't work, fix the code, remove this line :)
 __END__
 
 
 __NAME__ synopsis
-<group choice='req'>
-	<arg choice='plain'><replaceable>program name and arguments</replaceable></arg>
-</group>
+<arg choice='plain'><replaceable>program_name_and_arguments</replaceable></arg>
 __END__
 
 



1.3       +1 -3      xmldocs/refs/ChildLife


rev 1.3, prev_rev 1.2
Index: ChildLife
===================================================================
RCS file: /var/cvs/xmldocs/refs/ChildLife,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ChildLife	29 May 2005 11:19:33 -0000	1.2
+++ ChildLife	19 Oct 2006 19:29:54 -0000	1.3
@@ -9,9 +9,7 @@
 
 
 __NAME__ synopsis
-<group choice='req'>
-	<arg choice='plain'><replaceable>interval</replaceable></arg>
-</group>
+<arg choice='plain'><replaceable>interval</replaceable></arg>
 __END__
 
 








More information about the docs mailing list