[interchange-docs] xmldocs - docelic modified 4 files

[docs at icdevgroup.org]

User:      docelic
Date:      2008-08-12 22:29:36 GMT
Modified:  docbook  literals.ent
Modified:  guides   install.xml programming-style.xml
Modified:  refs     backup-database.tag
Log:
* document backup-database's new force=1

Revision  Changes    Path
1.66                 xmldocs/docbook/literals.ent


rev 1.66, prev_rev 1.65
Index: literals.ent
===================================================================
RCS file: /var/cvs/xmldocs/docbook/literals.ent,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -r1.65 -r1.66
--- literals.ent	28 Jul 2008 08:37:08 -0000	1.65
+++ literals.ent	12 Aug 2008 22:29:36 -0000	1.66
@@ -1,7 +1,7 @@
 
 <!-- first IC release shipping with xmldocs -->
 <!ENTITY first-xmldocs-release "5.4">
-<!ENTITY PERL_VER_REQUIRED "5.6">
+<!ENTITY PERL_VER_REQUIRED "5.8">
 
 <!-- This is used for including paragraphs based on IC version
      they're generated for. Keep the list sorted like you see it. -->



1.13                 xmldocs/guides/install.xml


rev 1.13, prev_rev 1.12
Index: install.xml
===================================================================
RCS file: /var/cvs/xmldocs/guides/install.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- install.xml	8 Nov 2007 02:07:59 -0000	1.12
+++ install.xml	12 Aug 2008 22:29:36 -0000	1.13
@@ -110,6 +110,7 @@
 		platform. Chances are that the additional, non-standard modules required
 		by &IC; will also be available in your distribution.
 		</para>
+		<!--
 		<para>
 		You should run &IC; with a non-threaded Perl. Unfortunately, almost
 		all distributions compile a threaded version. This problem has caused,
@@ -127,6 +128,7 @@
 		of Perl that will be used to run &IC;. Pointers on how to make &IC;
 		use your custom Perl installation are given later in this guide.
 		</para>
+		-->
 		<para>
 		Interchange relies on a number of non-standard Perl modules.
 		Installing &IC; from the generic tarball will test for the required
@@ -184,7 +186,7 @@
 		</para>
 		<para>
 		&APACHE; is probably the most commonly used web server, but you might
-		be interested in lighter and more efficient alternatives such as
+		be interested in lighter and efficient alternatives such as
 		&MATHOPD;.
 		</para>
 		<para>



1.16                 xmldocs/guides/programming-style.xml


rev 1.16, prev_rev 1.15
Index: programming-style.xml
===================================================================
RCS file: /var/cvs/xmldocs/guides/programming-style.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- programming-style.xml	11 Jul 2008 08:20:34 -0000	1.15
+++ programming-style.xml	12 Aug 2008 22:29:36 -0000	1.16
@@ -205,12 +205,12 @@
 		With non-container tags, such as &lt;input&gt;, &lt;br&gt; or &lt;hr&gt;,
 		closing <literal>&gt;</literal> needs to be replaced with
 		<literal>/&gt;</literal>, but not unconditionally (&IC; must be able to
-		output both the usual, and XHTML variant).
+		output both the usual &gt; and and XHTML variant /&gt;).
 		In such constructs, you can use <varname>$Vend::Xtrailer</varname>
-		that's set to <literal>/</literal> if &conf-XHTML; is enabled, 
-		and we could eventually replace all "raw" calls like &lt;input&gt;
-		with &tag-formel;, &tag-widget; and other tags that will honor 
-		<varname>$Vend::Xtrailer</varname>.
+		that's automatically set to <literal>/</literal> if &conf-XHTML; is
+		enabled, and eventually you could replace your "raw" calls to tags
+		such as &lt;input&gt; with calls to Interchange tags &tag-formel;
+		or &tag-display; that will honor <varname>$Vend::Xtrailer</varname>.
 <programlisting><![CDATA[
 <form action="[process]">
   <input type="text"   name="city" value="[value city]" />
@@ -291,7 +291,7 @@
 		Do not break obviously "solid" blocks of code to multiple lines. To give
 		you an idea of what I am talking about, let's say you should not break
 		typical xmldocs regexps, such as <literal>/\$::Pragma->{(\w+?)}/</literal>
-		or <literal>/\$Vend::Cfg->{Pragma}{(\w+?)}/</literal>. (Impact: critical. Might prevent the <filename>bin/stattree</filename> script from detecting symbols)
+		or <literal>/\$Vend::Cfg->{Pragma}{(\w+?)}/</literal>. (Impact: important. Might prevent the <filename>bin/stattree</filename> script from detecting symbols)
 <programlisting><![CDATA[
 return if $::Pragma->{download};
 



1.6                  xmldocs/refs/backup-database.tag


rev 1.6, prev_rev 1.5
Index: backup-database.tag
===================================================================
RCS file: /var/cvs/xmldocs/refs/backup-database.tag,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- backup-database.tag	15 Jul 2008 12:19:39 -0000	1.5
+++ backup-database.tag	12 Aug 2008 22:29:36 -0000	1.6
@@ -24,6 +24,23 @@
 <row>
 
 	<entry>
+	force
+	</entry>
+	<entry>
+	</entry>
+	<entry>
+	</entry>
+	<entry>
+	&glos-false;
+	</entry>
+	<entry>
+	Force export even if &conf-NoExportExternal; would apply to this table?
+	</entry>
+
+</row> 
+<row>
+
+	<entry>
 	dir
 	</entry>
 	<entry>