[interchange-docs] xmldocs - docelic modified 26 files

docs at icdevgroup.org docs at icdevgroup.org
Sun Sep 3 06:03:25 EDT 2006


User:      docelic
Date:      2006-09-03 10:03:24 GMT
Modified:  .        Makefile
Modified:  bin      generic-autogen
Modified:  docbook  html-nochunks.xsl olinkdb-c.xml
Modified:  guides   index.xml
Modified:  howtos   apache-rewrite-rules avoid-searches-in-href
Modified:           category-based-vat
Modified:           check-for-errors-in-form-submission
Modified:           control-access-to-certain-pages
Modified:           custom-sendmail-routine daemon-control
Modified:           expire-sessions find-dbconf-inconsistencies
Modified:           fix-failing-mysql-statements
Modified:           forcibly-adjust-quantity-of-ordered-item
Modified:           implement-banners log-files
Modified:           make-data-structure-modifiable
Modified:           modify-database-text-source-file-and-apply-changes
Modified:           mysql-based-sessions obtain-and-run-interchange
Modified:           override-admin-UI-page quantity-in-basket validate
Modified:           write-and-read-a-session
Log:
** Stefan, glossary is now chunked. Feel free to index it with Swish ;-)

- Makefile:
 add target for creating chunked (multi-html) version of glossary
 minor distclean target update

- bin/generic-autogen:
 adjust glossary doctype to article
 adjust howto entry syntax to simple section/title/para format
 minor improvements

- docbook/html-nochunks.xsl:
 docbook-related fix (suppress display of <refclass> element, like it
 was in older XSL stylesheets)

- docbook/olinkdb-c.html, guides/index.html:
 add chunked version of glossary

- howtos/*:
 adjust to new (simpler) format. First line in the file is
 HOW-TO item title, everything else is content for the HOW-TO item,
 with implicit <para> ... </para> surrounding the block.

Revision  Changes    Path
1.86      +3 -2      xmldocs/Makefile


rev 1.86, prev_rev 1.85
Index: Makefile
===================================================================
RCS file: /var/cvs/xmldocs/Makefile,v
retrieving revision 1.85
retrieving revision 1.86
diff -u -r1.85 -r1.86
--- Makefile	2 Sep 2006 22:21:47 -0000	1.85
+++ Makefile	3 Sep 2006 10:03:23 -0000	1.86
@@ -61,7 +61,8 @@
 symbols:  $(foreach doc,$(SYMBOL_TYPES),OUTPUT/$(doc).html  )      \
           $(foreach doc,$(SYMBOL_TYPES),OUTPUT/$(doc))
 
-glossary: $(foreach doc,$(GLOSSARY),OUTPUT/$(doc).html  )
+glossary: $(foreach doc,$(GLOSSARY),OUTPUT/$(doc).html  )          \
+          $(foreach doc,$(GLOSSARY),OUTPUT/$(doc))
 
 #############################################################
 # Skel
@@ -206,7 +207,7 @@
 distclean: clean clean-cache
 	-rm -rf $T
 	-rm -rf {refs,glossary,howtos}/*.xml
-	-rm -rf docbook/auto{refs,glossary,howtos}.ent
+	-rm -rf docbook/auto{refs,glossary,howtos,files}.ent
 look-clean:
 	-mv $T $T.temporary 2>/dev/null
 commit:



1.17      +26 -21    xmldocs/bin/generic-autogen


rev 1.17, prev_rev 1.16
Index: generic-autogen
===================================================================
RCS file: /var/cvs/xmldocs/bin/generic-autogen,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- generic-autogen	4 Jul 2006 22:24:42 -0000	1.16
+++ generic-autogen	3 Sep 2006 10:03:23 -0000	1.17
@@ -18,6 +18,7 @@
 my $invalid_file = "tmp/missing2";
 my @loaded;
 my $document;
+my $visible_name;
 my %sn = ( # short name
 	glossary => "glos",
 	howtos => "howto",
@@ -28,28 +29,29 @@
 );
 
 my %header = ( # item head
-	glossary => "<glossentry id=\"\$file\">
-<glossterm>\$visible_name</glossterm>
+	glossary => "<section id=\"\$file\">
+<title>\$visible_name</title>
 
-<glossdef><para>
-",
-	howtos => "<qandaentry>
-<question><para>
+<para>
 ",
+	howtos => "<section>
+<title>\$visible_name</title>
+
+<para>",
 );
 my %footer = ( # item tail
-	glossary => "\n</para>\n</glossdef>\n</glossentry>\n\n",
-	howtos => "\n</para>\n</answer>\n</qandaentry>\n\n",
+	glossary => "\n</para>\n</section>\n\n",
+	howtos => "\n</para>\n</section>\n\n",
 );
 
 # HEAD
 my $glossary = <<__ENDP__;
 <?xml version="1.0" standalone="no"?>
 
-<!DOCTYPE glossary PUBLIC "-//OASIS//DTD DocBook-Interchange XML V4.2//EN"
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook-Interchange XML V4.2//EN"
   "../docbook/docbookxi.dtd">
 
-<glossary>
+<article>
 	<title>Interchange Documentation: Glossary</title>
 
 __ENDP__
@@ -62,9 +64,6 @@
 <article id="howtos">
 	<title>Interchange Documentation: HOW-TO Collection</title>
 
-<qandadiv>
-	<title>HOW-TO Collection</title>
-
 __ENDP__
 
 # OPEN GLOSSARY ENTITIES
@@ -81,7 +80,12 @@
 	next if $file =~ /^\.|^CVS|\.xml$/;
 	open IN, "< $cat/$file" or die "Can't read-open $cat/$file ($!)\n";
 
-	( my $visible_name = $file ) =~ s/-/ /g;
+	if ( $cat eq 'howtos' ) {
+		$visible_name = <IN>;
+	} else {
+ 		( $visible_name = $file ) =~ s/-/ /g;
+	}
+	
 	$items{$file} = [ prefix($cat, $file), <IN>, suffix($cat, $file) ];
 	$alphabet{ lc(substr($file, 0, 1)) }++;
 	push @loaded, $file;
@@ -112,17 +116,20 @@
 		next unless $alphabet{$letter}; # Next if no entries on that letter
 		print "Passed on $letter\n" if $verbose;
 
-		$document .= '<glossdiv id="' . uc($letter) . '"><title>' .
-			uc($letter) . '</title>' . "\n";
+		# Code that was doing separations by letter. (like A.. B..).
+		# This isn't applicable any more since we've switched to 
+		# doctype 'article' instead of 'glossary'.
+		#$document .= '<glossdiv id="' . uc($letter) . '"><title>' .
+		#	uc($letter) . '</title>' . "\n";
 
 		my @keys = sort grep {/^$letter/i} keys %items;
 		for my $key ( @keys ) {
 			print "FOUND KEY $key\n" if $verbose;
 			$document .= join "", @{ $items{$key} };
 		}
-		$document .= '</glossdiv>' . "\n";
+		#$document .= '</glossdiv>' . "\n";
 	}
-	$document .= '</glossary>';
+	$document .= '</article>';
 
 } elsif ( $cat eq 'howtos' ) {
 	$document = $howtos;
@@ -130,7 +137,7 @@
 		print "Processing $howto\n" if $verbose;
 		$document .= join "", @{ $items{$howto} };
 	}
-	$document .= '</qandadiv></article>';
+	$document .= '</article>';
 }
 
 
@@ -156,7 +163,6 @@
 
 sub prefix {
 	my ($cat, $file) = @_;
-	( my $visible_name = $file ) =~ s/-/ /g;
 	if ( $header{$cat} ) {
 		my $tmp = $header{$cat};
 		$tmp =~ s/(\$\w+)/$1/gee;
@@ -167,7 +173,6 @@
 
 sub suffix {
 	my ($cat, $file) = @_;
-	( my $visible_name = $file ) =~ s/-/ /g;
 	if ( $footer{$cat} ) {
 		my $tmp = $footer{$cat};
 		$tmp =~ s/(\$\w+)/$1/gee;



1.8       +1 -0      xmldocs/docbook/html-nochunks.xsl


rev 1.8, prev_rev 1.7
Index: html-nochunks.xsl
===================================================================
RCS file: /var/cvs/xmldocs/docbook/html-nochunks.xsl,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- html-nochunks.xsl	1 Sep 2005 23:12:38 -0000	1.7
+++ html-nochunks.xsl	3 Sep 2006 10:03:23 -0000	1.8
@@ -39,6 +39,7 @@
   </xsl:template>
 	
 	<xsl:param name="html.stylesheet">xmldocs.css</xsl:param>
+	<xsl:param name="refclass.suppress">1</xsl:param>
 	
 	<xsl:include href="common.xsl"/>
 	<xsl:include href="html-common.xsl"/>



1.20      +1 -1      xmldocs/docbook/olinkdb-c.xml


rev 1.20, prev_rev 1.19
Index: olinkdb-c.xml
===================================================================
RCS file: /var/cvs/xmldocs/docbook/olinkdb-c.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- olinkdb-c.xml	2 Sep 2006 22:21:47 -0000	1.19
+++ olinkdb-c.xml	3 Sep 2006 10:03:23 -0000	1.20
@@ -65,7 +65,7 @@
 				</document>
 			</dir>
 			
-			<dir name=''>
+			<dir name='glossary'>
 				<document targetdoc="glossary">
 				&glossary;
 				</document>



1.11      +1 -0      xmldocs/guides/index.xml


rev 1.11, prev_rev 1.10
Index: index.xml
===================================================================
RCS file: /var/cvs/xmldocs/guides/index.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- index.xml	4 May 2006 21:16:33 -0000	1.10
+++ index.xml	3 Sep 2006 10:03:23 -0000	1.11
@@ -164,6 +164,7 @@
 					<emphasis role='bold'>
 						Glossary
 					</emphasis><sbr/>
+					<ulink url="glossary/index.html">Multi-HTML</ulink> |
 					<ulink url="glossary.html">HTML</ulink>
 				</entry>
 



1.2       +0 -2      xmldocs/howtos/apache-rewrite-rules


rev 1.2, prev_rev 1.1
Index: apache-rewrite-rules
===================================================================
RCS file: /var/cvs/xmldocs/howtos/apache-rewrite-rules,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- apache-rewrite-rules	10 Jun 2006 23:44:56 -0000	1.1
+++ apache-rewrite-rules	3 Sep 2006 10:03:23 -0000	1.2
@@ -1,7 +1,5 @@
 Write Apache RewriteRule and RewriteCond directives to avoid cgi-bin/ in HTML links
-</para></question>
 
-<answer><para>
 The &APACHE; config file (or a corresponding vhost file) needs something
 like the following:
 </para><para>



1.2       +0 -2      xmldocs/howtos/avoid-searches-in-href


rev 1.2, prev_rev 1.1
Index: avoid-searches-in-href
===================================================================
RCS file: /var/cvs/xmldocs/howtos/avoid-searches-in-href,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- avoid-searches-in-href	10 Jun 2006 23:44:56 -0000	1.1
+++ avoid-searches-in-href	3 Sep 2006 10:03:23 -0000	1.2
@@ -1,7 +1,5 @@
 Avoid search strings in a href specification
-</para></question>
 
-<answer><para>
 Basically, you should never embed searches in a &glos-HTML; href specification.
 In other words, you should never do something like:
 <programlisting>



1.2       +0 -2      xmldocs/howtos/category-based-vat


rev 1.2, prev_rev 1.1
Index: category-based-vat
===================================================================
RCS file: /var/cvs/xmldocs/howtos/category-based-vat,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- category-based-vat	15 Aug 2006 20:22:02 -0000	1.1
+++ category-based-vat	3 Sep 2006 10:03:23 -0000	1.2
@@ -1,7 +1,5 @@
 Use Category-dependent Tax Rates
-</para></question>
 
-<answer><para>
 Many european countries use product category-dependent tax rates.
 The question is, how to implement this in &IC;.
 </para><para>



1.2       +0 -2      xmldocs/howtos/check-for-errors-in-form-submission


rev 1.2, prev_rev 1.1
Index: check-for-errors-in-form-submission
===================================================================
RCS file: /var/cvs/xmldocs/howtos/check-for-errors-in-form-submission,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- check-for-errors-in-form-submission	15 Aug 2006 20:22:02 -0000	1.1
+++ check-for-errors-in-form-submission	3 Sep 2006 10:03:23 -0000	1.2
@@ -1,7 +1,5 @@
 Check for Errors in Form Submission
-</para></question>
 
-<answer><para>
 <!-- 
 
 (Below is as of 4.03, the equivalent in 4.02 is



1.2       +0 -2      xmldocs/howtos/control-access-to-certain-pages


rev 1.2, prev_rev 1.1
Index: control-access-to-certain-pages
===================================================================
RCS file: /var/cvs/xmldocs/howtos/control-access-to-certain-pages,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- control-access-to-certain-pages	3 Aug 2006 21:58:40 -0000	1.1
+++ control-access-to-certain-pages	3 Sep 2006 10:03:24 -0000	1.2
@@ -1,7 +1,5 @@
 Control Access to Certain Pages
-</para></question>
 
-<answer><para>
 There's a built-in &IC; way to control user access to pages served
 from the &conf-PageDir; directories.
 </para><para>



1.7       +0 -2      xmldocs/howtos/custom-sendmail-routine


rev 1.7, prev_rev 1.6
Index: custom-sendmail-routine
===================================================================
RCS file: /var/cvs/xmldocs/howtos/custom-sendmail-routine,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- custom-sendmail-routine	17 Sep 2005 21:24:01 -0000	1.6
+++ custom-sendmail-routine	3 Sep 2006 10:03:24 -0000	1.7
@@ -1,7 +1,5 @@
 Define Custom Sendmail Routine
-</para></question>
 
-<answer><para>
 Someone <ulink url="http://www.icdevgroup.org/pipermail/interchange-users/2004-July/039811.html">
 was wondering</ulink> how to optimize the order processing on a busy site.
 It was observed that about once in every ten times, the



1.8       +0 -2      xmldocs/howtos/daemon-control


rev 1.8, prev_rev 1.7
Index: daemon-control
===================================================================
RCS file: /var/cvs/xmldocs/howtos/daemon-control,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- daemon-control	4 Jul 2006 22:24:42 -0000	1.7
+++ daemon-control	3 Sep 2006 10:03:24 -0000	1.8
@@ -1,7 +1,5 @@
 Control Interchange Daemon Process
-</para></question>
 
-<answer><para>
 Knowing how to manage the Interchange daemon is one of the very basic
 administration tasks.
 </para><para>



1.2       +0 -2      xmldocs/howtos/expire-sessions


rev 1.2, prev_rev 1.1
Index: expire-sessions
===================================================================
RCS file: /var/cvs/xmldocs/howtos/expire-sessions,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- expire-sessions	5 Jul 2006 14:03:30 -0000	1.1
+++ expire-sessions	3 Sep 2006 10:03:24 -0000	1.2
@@ -1,6 +1,4 @@
 Expire user sessions
-</para></question>
 
-<answer><para>
 See the &glos-expire; glossary entry.
 



1.2       +0 -2      xmldocs/howtos/find-dbconf-inconsistencies


rev 1.2, prev_rev 1.1
Index: find-dbconf-inconsistencies
===================================================================
RCS file: /var/cvs/xmldocs/howtos/find-dbconf-inconsistencies,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- find-dbconf-inconsistencies	10 Jun 2006 23:44:56 -0000	1.1
+++ find-dbconf-inconsistencies	3 Sep 2006 10:03:24 -0000	1.2
@@ -1,7 +1,5 @@
 Find database definition inconsistencies for various database types defined under dbconf/ directory
-</para></question>
 
-<answer><para>
 Here's a script that can help you find inconsistencies in database definition
 files. (All files should essentially have the same definition, even if they
 differ in database-specific syntax).



1.2       +0 -2      xmldocs/howtos/fix-failing-mysql-statements


rev 1.2, prev_rev 1.1
Index: fix-failing-mysql-statements
===================================================================
RCS file: /var/cvs/xmldocs/howtos/fix-failing-mysql-statements,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- fix-failing-mysql-statements	10 Jun 2006 23:44:56 -0000	1.1
+++ fix-failing-mysql-statements	3 Sep 2006 10:03:24 -0000	1.2
@@ -1,7 +1,5 @@
 Fix constantly failing MySQL statements
-</para></question>
 
-<answer><para>
 One possible cause for the failing &MYSQL; statements is the too-low
 timeout value. Try increasing the timeout to say, 50 minutes, by inserting
 the following in <filename>my.cnf</filename>:



1.2       +0 -2      xmldocs/howtos/forcibly-adjust-quantity-of-ordered-item


rev 1.2, prev_rev 1.1
Index: forcibly-adjust-quantity-of-ordered-item
===================================================================
RCS file: /var/cvs/xmldocs/howtos/forcibly-adjust-quantity-of-ordered-item,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- forcibly-adjust-quantity-of-ordered-item	3 Aug 2006 21:58:40 -0000	1.1
+++ forcibly-adjust-quantity-of-ordered-item	3 Sep 2006 10:03:24 -0000	1.2
@@ -1,7 +1,5 @@
 Forcibly Adjust Quantity of Ordered Item
-</para></question>
 
-<answer><para>
 Since your stock may be limited, you could want to stop users from 
 ordering more items than you have.
 </para><para>



1.7       +0 -2      xmldocs/howtos/implement-banners


rev 1.7, prev_rev 1.6
Index: implement-banners
===================================================================
RCS file: /var/cvs/xmldocs/howtos/implement-banners,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- implement-banners	17 Sep 2005 21:24:01 -0000	1.6
+++ implement-banners	3 Sep 2006 10:03:24 -0000	1.7
@@ -1,7 +1,5 @@
 Implement Banner Ads
-</para></question>
 
-<answer><para>
 	Banner display in &IC; is implemented using the <tag>banner</tag> tag.
 	There are two terms which need to be understood first:
 </para>



1.4       +0 -2      xmldocs/howtos/log-files


rev 1.4, prev_rev 1.3
Index: log-files
===================================================================
RCS file: /var/cvs/xmldocs/howtos/log-files,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- log-files	17 Sep 2005 21:24:01 -0000	1.3
+++ log-files	3 Sep 2006 10:03:24 -0000	1.4
@@ -1,7 +1,5 @@
 Setup and monitor log files
-</para></question>
 
-<answer><para>
 	To monitor all relevant log files at once, first adjust the
 	neccessary config files, restart the daemons, and issue<sbr/>
 	<userinput>tail -f /var/log/{apache,interchange}/*log</userinput>.



1.4       +0 -2      xmldocs/howtos/make-data-structure-modifiable


rev 1.4, prev_rev 1.3
Index: make-data-structure-modifiable
===================================================================
RCS file: /var/cvs/xmldocs/howtos/make-data-structure-modifiable,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- make-data-structure-modifiable	16 Aug 2006 14:35:04 -0000	1.3
+++ make-data-structure-modifiable	3 Sep 2006 10:03:24 -0000	1.4
@@ -1,7 +1,5 @@
 Make Perl Hash Seemingly Modifiable
-</para></question>
 
-<answer><para>
 Sometimes you want to make a data structure modifiable, without having the
 changes permanently override original values. To do so, we can use &PERL;'s
 <classname>Tie::ShadowHash</classname> module.



1.2       +0 -2      xmldocs/howtos/modify-database-text-source-file-and-apply-changes


rev 1.2, prev_rev 1.1
Index: modify-database-text-source-file-and-apply-changes
===================================================================
RCS file: /var/cvs/xmldocs/howtos/modify-database-text-source-file-and-apply-changes,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- modify-database-text-source-file-and-apply-changes	3 Aug 2006 21:58:40 -0000	1.1
+++ modify-database-text-source-file-and-apply-changes	3 Sep 2006 10:03:24 -0000	1.2
@@ -1,7 +1,5 @@
 Modify Database Text Source File and Apply Changes
-</para></question>
 
-<answer><para>
 With some kind of a DBM &glos-database;, this should be automatic. Changes
 to the text source file will be detected on first client access to the
 specific database; &IC; will then re-read the text source file and override



1.2       +0 -2      xmldocs/howtos/mysql-based-sessions


rev 1.2, prev_rev 1.1
Index: mysql-based-sessions
===================================================================
RCS file: /var/cvs/xmldocs/howtos/mysql-based-sessions,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- mysql-based-sessions	10 Jun 2006 23:44:56 -0000	1.1
+++ mysql-based-sessions	3 Sep 2006 10:03:24 -0000	1.2
@@ -1,7 +1,5 @@
 Implement MySQL-based sessions
-</para></question>
 
-<answer><para>
 As you might know, &IC; can use databases to store users' &glos-session;
 data (instead of the usual files). Corresponding &ccf; definition might
 look like this:



1.6       +0 -2      xmldocs/howtos/obtain-and-run-interchange


rev 1.6, prev_rev 1.5
Index: obtain-and-run-interchange
===================================================================
RCS file: /var/cvs/xmldocs/howtos/obtain-and-run-interchange,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- obtain-and-run-interchange	10 Jun 2006 23:44:56 -0000	1.5
+++ obtain-and-run-interchange	3 Sep 2006 10:03:24 -0000	1.6
@@ -1,7 +1,5 @@
 Obtain and Run Interchange
-</para></question>
 
-<answer><para>
 &IC; is free of charge, and is distributed under the GNU
 General Public License.  This means that individuals and organizations,
 both commercial and non-commercial, may use &IC; without charge. If



1.2       +0 -2      xmldocs/howtos/override-admin-UI-page


rev 1.2, prev_rev 1.1
Index: override-admin-UI-page
===================================================================
RCS file: /var/cvs/xmldocs/howtos/override-admin-UI-page,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- override-admin-UI-page	3 Aug 2006 21:58:40 -0000	1.1
+++ override-admin-UI-page	3 Sep 2006 10:03:24 -0000	1.2
@@ -1,7 +1,5 @@
 Override page from Admin UI with catalog's custom version
-</para></question>
 
-<answer><para>
 At any time, you can copy pages from
 the <filename class='directory'>lib/UI/pages/admin/</filename> directory
 into the <filename class='directory'>pages/admin/</filename> directory



1.7       +0 -3      xmldocs/howtos/quantity-in-basket


rev 1.7, prev_rev 1.6
Index: quantity-in-basket
===================================================================
RCS file: /var/cvs/xmldocs/howtos/quantity-in-basket,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- quantity-in-basket	17 Sep 2005 21:24:01 -0000	1.6
+++ quantity-in-basket	3 Sep 2006 10:03:24 -0000	1.7
@@ -1,8 +1,5 @@
 Provide Item Quantity Fields in the Basket Page
-</para></question>
 
-<answer>
-	<para>
 	On your &IC; pages, you should provide some kind of an &glos-HTML; form
 	if you want to receive any data from the client. We will use the 
 	<filename>pages/ord/basket.html</filename> page from the



1.6       +0 -2      xmldocs/howtos/validate


rev 1.6, prev_rev 1.5
Index: validate
===================================================================
RCS file: /var/cvs/xmldocs/howtos/validate,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- validate	17 Sep 2005 21:24:02 -0000	1.5
+++ validate	3 Sep 2006 10:03:24 -0000	1.6
@@ -1,7 +1,5 @@
 Validate Interchange-produced Markup
-</para></question>
 
-<answer><para>
 	Validate pages at W3C using &css-validator; or &markup-validator;.
 </para><para>
 	&IC; does not output any &glos-CSS; on its own, so the CSS validation outcome



1.2       +0 -2      xmldocs/howtos/write-and-read-a-session


rev 1.2, prev_rev 1.1
Index: write-and-read-a-session
===================================================================
RCS file: /var/cvs/xmldocs/howtos/write-and-read-a-session,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- write-and-read-a-session	3 Aug 2006 21:58:40 -0000	1.1
+++ write-and-read-a-session	3 Sep 2006 10:03:24 -0000	1.2
@@ -1,7 +1,5 @@
 Write and read a session
-</para></question>
 
-<answer><para>
 If you are going to save a &glos-session; and
 do something specific with it, do it explicitly by saving to 
 a separate, named file:








More information about the docs mailing list