[docs] xmldocs - docelic modified 12 files

docs at icdevgroup.org docs at icdevgroup.org
Tue Jan 24 11:06:47 EST 2006


User:      docelic
Date:      2006-01-24 16:06:47 GMT
Modified:  .        Makefile TODO
Modified:  docbook  literals.ent olinkdb-c.xml olinkdb-nc.xml
Modified:  glossary catalog configuration database
Modified:  refs     Catalog Database LANG export.tag
Log:
* Properly define WHATSNEW as part of build process
* Add 'optimization' guide to build process

(The above two should make the build routine clean once again. For the past
week or two running make was a really ugly experience due to slight omissions
in build rules).

* Various other text fixes

Revision  Changes    Path
1.83      +1 -1      xmldocs/Makefile


rev 1.83, prev_rev 1.82
Index: Makefile
===================================================================
RCS file: /var/cvs/xmldocs/Makefile,v
retrieving revision 1.82
retrieving revision 1.83
diff -u -r1.82 -r1.83
--- Makefile	8 Jan 2006 20:54:53 -0000	1.82
+++ Makefile	24 Jan 2006 16:06:47 -0000	1.83
@@ -13,7 +13,7 @@
 #############################################################
 # Base definitions
 SYMBOL_TYPES= pragmas vars tags confs filters orderchecks
-GUIDES      = iccattut programming-style upgrade faq index optimization search xmldocs
+GUIDES      = iccattut programming-style upgrade faq index optimization search xmldocs WHATSNEW
 HOWTOS      = howtos
 GLOSSARY    = glossary
 ALL_DOCS    = $(GLOSSARY) $(HOWTOS) $(GUIDES) $(SYMBOL_TYPES)



1.80      +1 -0      xmldocs/TODO


rev 1.80, prev_rev 1.79
Index: TODO
===================================================================
RCS file: /var/cvs/xmldocs/TODO,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -r1.79 -r1.80
--- TODO	21 Dec 2005 15:39:46 -0000	1.79
+++ TODO	24 Jan 2006 16:06:47 -0000	1.80
@@ -1,4 +1,5 @@
 on xmldocs, link to icdevgroup.org base site
+in iccattut, s/item-field/item-param/ at least on some places. 
 
 Outstanding:
 =======



1.29      +1 -1      xmldocs/docbook/literals.ent


rev 1.29, prev_rev 1.28
Index: literals.ent
===================================================================
RCS file: /var/cvs/xmldocs/docbook/literals.ent,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- literals.ent	19 Nov 2005 22:37:40 -0000	1.28
+++ literals.ent	24 Jan 2006 16:06:47 -0000	1.29
@@ -1,6 +1,6 @@
 
 <!-- first IC release shipping with xmldocs -->
-<!ENTITY first-xmldocs-release "5.6">
+<!ENTITY first-xmldocs-release "5.4">
 
 <!-- GENERAL ENTITIES -->
 <!ENTITY GNU "<ulink url='http://www.gnu.org'>GNU</ulink>">



1.17      +11 -4     xmldocs/docbook/olinkdb-c.xml


rev 1.17, prev_rev 1.16
Index: olinkdb-c.xml
===================================================================
RCS file: /var/cvs/xmldocs/docbook/olinkdb-c.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- olinkdb-c.xml	8 Jan 2006 20:54:54 -0000	1.16
+++ olinkdb-c.xml	24 Jan 2006 16:06:47 -0000	1.17
@@ -15,7 +15,8 @@
 	<!ENTITY confs SYSTEM "../tmp/confs-c.db"> 
 	<!ENTITY filters SYSTEM "../tmp/filters-c.db"> 
 	<!ENTITY orderchecks SYSTEM "../tmp/orderchecks-c.db"> 
-	<!ENTITY whatsnew SYSTEM "../tmp/whatsnew-c.db"> 
+	<!ENTITY whatsnew SYSTEM "../tmp/WHATSNEW-c.db"> 
+	<!ENTITY optimization SYSTEM "../tmp/optimization-c.db"> 
 ]>
 
 <targetset>
@@ -104,9 +105,15 @@
 				</document>
 			</dir>
 
-			<dir name='whatsnew'>
-				<document targetdoc="whatsnew">
-				&whatsnew;
+			<dir name='WHATSNEW'>
+				<document targetdoc="WHATSNEW">
+				&WHATSNEW;
+				</document>
+			</dir>
+
+			<dir name='optimization'>
+				<document targetdoc="optimization">
+				&optimization;
 				</document>
 			</dir>
 



1.18      +4 -2      xmldocs/docbook/olinkdb-nc.xml


rev 1.18, prev_rev 1.17
Index: olinkdb-nc.xml
===================================================================
RCS file: /var/cvs/xmldocs/docbook/olinkdb-nc.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- olinkdb-nc.xml	8 Jan 2006 20:54:54 -0000	1.17
+++ olinkdb-nc.xml	24 Jan 2006 16:06:47 -0000	1.18
@@ -15,7 +15,8 @@
 	<!ENTITY confs SYSTEM "../tmp/confs-nc.db"> 
 	<!ENTITY filters SYSTEM "../tmp/filters-nc.db"> 
 	<!ENTITY orderchecks SYSTEM "../tmp/orderchecks-nc.db"> 
-	<!ENTITY whatsnew SYSTEM "../tmp/whatsnew-nc.db"> 
+	<!ENTITY whatsnew SYSTEM "../tmp/WHATSNEW-nc.db"> 
+	<!ENTITY optimization SYSTEM "../tmp/optimization-nc.db"> 
 ]>
 
 <targetset>
@@ -39,7 +40,8 @@
 			<document targetdoc="confs" baseuri="confs.html"> &confs; </document>
 			<document targetdoc="filters" baseuri="filters.html"> &filters; </document>
 			<document targetdoc="orderchecks" baseuri="orderchecks.html"> &orderchecks; </document>
-			<document targetdoc="whatsnew" baseuri="whatsnew.html"> &whatsnew; </document>
+			<document targetdoc="WHATSNEW" baseuri="WHATSNEW.html"> &whatsnew; </document>
+			<document targetdoc="optimization" baseuri="optimization.html"> &optimization; </document>
 		</dir>
 	</sitemap>
 



1.3       +18 -0     xmldocs/glossary/catalog


rev 1.3, prev_rev 1.2
Index: catalog
===================================================================
RCS file: /var/cvs/xmldocs/glossary/catalog,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- catalog	15 Dec 2004 14:24:00 -0000	1.2
+++ catalog	24 Jan 2006 16:06:47 -0000	1.3
@@ -0,0 +1,18 @@
+A catalog is the basic functional unit in &IC;. A catalog is to &IC; what
+a web site is to a Web server.
+</para><para>
+Catalogs to configure and offer on the &IC; server are defined in the
+global configuration file, &gcf; (or some of the files it includes, of course,
+depending on the actual file layout). The definition directive is called
+&conf-Catalog;. The directive  you should use to register a catalog is
+&mdash; incidentally &mdash; &conf-Catalog;.
+</para><para>
+Each catalog directory (specified as one of &conf-Catalog; parameters) must
+have the file &ccf; in it. For the mandatory directives that need to be
+present in the file, see &conf-Catalog; reference page.
+</para><para>
+For the general syntax accepted in configuration files, see
+&glos-configuration; glossary entry.
+</para><para>
+For the list of available configuration directives, see
+<olink targetdoc='confs' />.



1.5       +77 -16    xmldocs/glossary/configuration


rev 1.5, prev_rev 1.4
Index: configuration
===================================================================
RCS file: /var/cvs/xmldocs/glossary/configuration,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- configuration	27 Aug 2005 03:26:13 -0000	1.4
+++ configuration	24 Jan 2006 16:06:47 -0000	1.5
@@ -4,20 +4,31 @@
 The other &mdash; catalog part, is specified in each catalog's
 &glos-CATROOT;/&ccf;, and has no effect on other catalogs.
 </para><para>
-Configuration directives are normally specified with the directive as the
+Each configuration directive is accessible on global or catalog level,
+or both. There's a special field named "<literal>DIRECTIVE TYPE</literal>"
+present in each directive's reference page, where you can look this up.
+Keep in mind, however, that the directives on
+global and catalog level don't have to be parsed by the same code &mdash;
+in fact, they're mostly parsed by related but different code blocks.
+</para>
+
+<section>
+<title>Configuration directives and syntax</title>
+<para>
+Configuration directives are normally specified with the directive name as the
 first word on the line, with its value or values following. Capitalization
-of the directive name is not significant (although it helps readability and
-consistency). Additionally, any leading and trailing whitespace is removed
-("stripped") before processing. Here's an example:
+of the directive name is not significant, but it helps readability and
+consistency. Additionally, any leading and trailing whitespace is removed
+("stripped") before processing. Here's a simple example:
 <programlisting>
-DirectiveName <replaceable>value</replaceable>
+<replaceable>DirectiveName</replaceable> <replaceable>value</replaceable>
 </programlisting>
 </para><para>
 Besides specifying directive values inline, one can conveniently use
 the following syntax to obtain value from external files:
 
 <programlisting>
-DirectiveName &lt;<replaceable>include_filename</replaceable>
+<replaceable>DirectiveName</replaceable> &lt;<replaceable>include_filename</replaceable>
 </programlisting>
 
 <note><para>
@@ -28,7 +39,7 @@
 </para></note>
 
 Files included from &gcf; are relative to &glos-ICROOT;. Files included
-from &ccf; are relative to specific &glos-CATROOT;.
+from &ccf; are relative to specific catalog's &glos-CATROOT;.
 
 </para><para>
 So-called "here document" syntax is supported as well. You can use it to
@@ -39,9 +50,8 @@
 is a hypothetical directive using a here document:
 
 <programlisting>
-DirectiveName &lt;&lt;EOD<replaceable>
-    setting1
-    setting2
+<replaceable>DirectiveName</replaceable> &lt;&lt;EOD<replaceable>
+    setting1 setting2
     setting3</replaceable>
 EOD
 </programlisting>
@@ -50,12 +60,12 @@
 </para><para>
 The above is equivalent to:
 <programlisting>
-DirectiveName <replaceable>setting1 setting2 setting3</replaceable>
+<replaceable>DirectiveName</replaceable> <replaceable>setting1 setting2 setting3</replaceable>
 </programlisting>
 
 </para><para>
 Other configuration files can also be included from the current one.
-For example, common settings can be set in one file:
+For example, common settings can be defined in a single file:
 
 <programlisting>
 include common.cfg
@@ -67,10 +77,18 @@
 include usertag/*
 </programlisting>
 
-</para><para>
-In addition,
-<literal>ifdef/endif</literal> and <literal>ifndef/endif</literal> pairs
-can be used:
+</para>
+</section>
+
+<section>
+<title>Parsing rules</title>
+
+<section>
+<title>Conditional blocks</title>
+
+<para>
+The familiar <literal>ifdef/endif</literal> and <literal>ifndef/endif</literal>
+pairs can be used to affect configuration processing:
 
 <programlisting>
 Variable ORDERS_TO email_address
@@ -99,3 +117,46 @@
   MailOrderTo  webmaster@&def-domain;
 endif
 </programlisting>
+
+</para>
+</section>
+
+<section>
+<title>Variables and expansion</title>
+<para>
+&IC;, of course, offers a way to define variables. Variables defined
+in your &gcf; or &ccf; can be referenced from both configuration files
+themselves and the usual &IC; pages later, when the catalog is running.
+</para><para>
+Variables are defined using the &conf-Variable; directive (reading its
+short reference now would be a good idea). The usual way to expand
+a variable to it's value is to use the
+<literal>__<replaceable>VARIABLE_NAME</replaceable>__</literal> notation.
+This notation, however, is by default not enabled in RHS 
+("Right-Hand Side") values in configuration files. To enable it, use the
+&conf-ParseVariables; directive which immediately affects the way 
+&IC; parses variables in config files. Here's an example to clarify
+what we're talking about:
+<programlisting>
+# Let's define two variables
+Variable   SERVER_NAME  &def-hostname;
+Variable   CGI_URL      /cgi-bin/ic/tutorial
+
+# Let's make VendURL directive be a combination of __SERVER_NAME__ and __CGI_URL__
+VendURL  http://__SERVER_NAME____CGI_URL__
+
+# To your surprise, after the above, VendURL would literally contain
+# "http://__SERVER_NAME____CGI_URL__". This is not what we want, so
+# we need to enable ParseVariables to achieve the desired effect:
+ParseVariables Yes
+VendURL  http://__SERVER_NAME____CGI_URL__
+ParseVariables No
+
+# VendURL now contains "http://&def-hostname;/cgi-bin/ic/tutorial"
+</programlisting>
+</para>
+</section>
+
+</section>
+<para>
+



1.5       +37 -27    xmldocs/glossary/database


rev 1.5, prev_rev 1.4
Index: database
===================================================================
RCS file: /var/cvs/xmldocs/glossary/database,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- database	19 Nov 2005 22:37:40 -0000	1.4
+++ database	24 Jan 2006 16:06:47 -0000	1.5
@@ -1,4 +1,4 @@
-In general, databases contain some information, usually in tabular format,
+In general, databases contain information, usually in tabular format,
 where columns define the names and types of contained data, and rows
 represent <emphasis>entries</emphasis> &mdash; database
 <emphasis>records</emphasis>.
@@ -28,11 +28,12 @@
 </emphasis>
 </para><para>
 &IC; works with &GDBM;, DB_File, SQL, LDAP and in-memory types of databases. 
-Regardless of the type, each database must be registered with &IC; before it's
+Regardless of type or other characteristics, each database must be registered
+with &IC; before it's
 ready to be used, and this is achieved using the &conf-Database; configuration
 directive. Pay special attention to the fact that &conf-Database; is both
 catalog and global directive, indicating that you can share databases 
-among catalogs.
+between catalogs.
 </para><para>
 Three parameters needed to complete the &conf-Database; specification are
 an arbitrary database name, text source file with initial content, and the
@@ -50,9 +51,11 @@
 <filename class='directory'>products/</filename> subdirectory of your
 &glos-CATROOT;. The &conf-ProductDir; directive controls the exact location.
 </para><para>
-The ASCII files can have
-<literal>^M</literal> (carriage return) characters, but must have a
-newline character at the end of the line to work. <emphasis role='bold'>
+The ASCII files can contain carriage return
+(<literal>^M</literal>) characters even in data fields, but must have a
+newline character (<literal>^N</literal>) at the end of line to properly
+separate records.
+<emphasis role='bold'>
 Mac users uploading files must use ascii mode, not binary mode</emphasis>.
 </para>
 <para>
@@ -61,7 +64,7 @@
 single TAB only)</emphasis>. Due to the nature of TABs, TAB-delimited files
 look messy and unaligned when viewed in a text editor. Do not try to fix these;
 better use the <command>te</command> utility that comes as part of the 
-&IC; distribution to edit files more conveniently.
+&IC; distribution to edit such files more conveniently.
 </para>
 Format examples:
 <itemizedlist>
@@ -120,7 +123,8 @@
 <section>
 	<title>SQL Databases</title>
 <para>
-As hinted above, you do not need to use an external SQL database. If you only
+As hinted above, you do not need to use an external &glos-SQL; database.
+If you only
 have a small data set, you could use Interchange's internal databases.
 This is a tremendous gain for small and quick setups, or &IC; evaluation.
 However, some functions (order management, for example) will be slower
@@ -143,14 +147,15 @@
 </note>
 
 <para>
-If you plan on using Interchange Admin UI, you should make the additional 
-effort of also configuring SQL databases and switching databases to it.
-Admin UI provides easy import routines for text files that should
-replace traditional FTP text-file uploads.
-</para><para>
+If you plan on using Interchange Admin UI, you <emphasis>should</emphasis>
+make an additional 
+effort of configuring and using SQL databases to achieve its full potential.
 Using SQL also makes your data sets easily available for integration with
 other applications.
 </para><para>
+In any case, Admin UI provides easy import routines for text files that should
+replace traditional FTP text-file uploads.
+</para><para>
 Speaking of the source files' behavior, if a file named
 <filename><replaceable>table</replaceable>.sql</filename> is present
 in the same directory as
@@ -170,8 +175,8 @@
 If there are any
 <literal>COLUMN_DEF</literal> specifications present in &gcf;, &ccf; or
 <filename>products/<replaceable>table</replaceable>.sql</filename>,
-they will be used in table specification (which is recommended for clean
-and correct database
+they will be used to create SQL table specification
+(which is recommended for clean and correct database
 layout). If there aren't any, however, then the key (first field in the text
 file, by default) will be created with the type <literal>char(16)</literal>,
 and all other fields will be created as <literal>char(128)</literal>. This is 
@@ -185,7 +190,8 @@
 "database" and "table" simply mean a "table" in &IC; parlance)
 is created, the text source file will be imported into it.
 For this step to succeed, data typing must be user-configured. In other words,
-if <literal>none</literal> is placed in a field, and the field in question
+if say, word "<literal>none</literal>" is placed in a field while the field
+in question
 is defined to be of numeric type, database import will not succeed;
 consequently, the problematic catalog won't configure successfully 
 (it will be skipped) and it won't be available when &IC; starts up.
@@ -203,7 +209,8 @@
 appropriate database text source file is checked for being newer than the
 actual DB file itself.
 When it happens that it is, the database table is re-imported
-from the text source file.
+from the text source file <emphasis>on the fly</emphasis>, and the routine
+proceeds as usual.
 </para>
 <note>
 <title>Database updates</title>
@@ -217,7 +224,7 @@
 but by default, changes in text files will trigger a 
 rewrite of DBM or DB_File databases. This might lead to unexpected problems
 if you edit databases from &IC; and don't sync <emphasis>files</emphasis>
-with the databases first, or have a larger data sets
+to databases first, or have a larger data sets
 (say, over a few thousand records) which take noticeable time to get
 re-imported.
 </para>
@@ -314,8 +321,8 @@
 	referred to as a database. The only time the term database refers to
 	something different is when describing the concept as it relates to
 	SQL, where a database contains a series of tables. While &IC;
-	cannot create SQL databases, it can drop and create tables with that
-	database if given the proper permissions.
+	cannot create SQL databases, it can drop and create tables within
+	databases if given the proper permissions.
 	</para>
 </listitem>
 </itemizedlist>
@@ -323,7 +330,8 @@
 
 <para>
 	&IC; uses one mandatory database, which is referred to as the
-	<database>products</database> database. In the supplied catalog, the
+	<database>products</database> database. In the supplied demo catalog
+	(and in the most of real-world solutions as well), the primary
 	database is directly called <literal>products</literal> 
 	and the ASCII source is kept in the file <filename>products.txt</filename>
 	This is also the default file for searching contents with
@@ -332,8 +340,8 @@
 
 <note>
 <para>
-	Interchange also has a two of standard, but optional, databases that
-	are <emphasis role='bold'>in fixed formats</emphasis>:
+	Interchange also has two but optional databases that
+	are given <emphasis role='bold'>in special, fixed formats</emphasis>:
 	</para>
 	<itemizedlist>
 <listitem>
@@ -390,8 +398,8 @@
 	<para>
 		It is important to adjust the &conf-PriceField; and &conf-DescriptionField;
 		directives appropriately if you change the default field names, or 
-		&IC; tags such as <tag>item-price</tag> or <tag>item-description</tag>
-		won't work.
+		&IC; tags such as &tag-price;, &tag-description;, <tag>item-price</tag> or
+		<tag>item-description</tag> won't work.
 	</para>
 	<para>
 		For each product entry in the text source file, the product code must
@@ -407,14 +415,16 @@
 	<para>
 		The columns in text source files should be separated by one of the
 		approved delimiting
-		schemes (TAB, PIPE, or CSV), and are case-sensitive in some cases. If
+		schemes (TAB, PIPE, or CSV), and are case-sensitive according to the
+		underlying database &mdash; be consistent in field names to avoid
+		trouble. If
 		the case of the "description" or "price" fields have been modified,
 		the &conf-PriceField; and &conf-DescriptionField; directives must be
 		adjusted appropriately.
 	</para>
 	<note>
 		<para>
-		CSV format is not recommended as the scheme for the products
+		CSV format is not recommended for the <database>products</database>
 		database. It is much slower than TAB- or PIPE-delimited files, and
 		dramatically reduces search engine functionality. No field-specific
 		searches are possible. Using CSV for any small database that will not



1.5       +3 -1      xmldocs/refs/Catalog


rev 1.5, prev_rev 1.4
Index: Catalog
===================================================================
RCS file: /var/cvs/xmldocs/refs/Catalog,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- Catalog	9 Jun 2005 12:02:43 -0000	1.4
+++ Catalog	24 Jan 2006 16:06:47 -0000	1.5
@@ -59,8 +59,10 @@
 If the &ccf; file, expected in the catalog base directory, is not found, or is
 unreadable by the &IC; server, somewhat misguiding error message will be reported.
 Namely, instead of the appropriate permissions-problem message, the mandatory
-&conf-MailOrderTo; directive will be reported undefined.
+&conf-VendURL; directive will be reported undefined.
 __END__
+(Did I do this right? Now that MailOrderTo isn't mandatory anymore, 
+error will be about VendURL? Check that out.)
 
 __NAME__ example: Registering a catalog
 <programlisting>



1.3       +5 -3      xmldocs/refs/Database


rev 1.3, prev_rev 1.2
Index: Database
===================================================================
RCS file: /var/cvs/xmldocs/refs/Database,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- Database	18 Dec 2005 11:32:11 -0000	1.2
+++ Database	24 Jan 2006 16:06:47 -0000	1.3
@@ -13,13 +13,15 @@
 __END__
 
 __NAME__ description
+</para><para>
 The directive registers a database table for use with &IC;. 
-<arg choice='plain'>name</arg> specifies an arbitrary name &mdash; name
+<literal>name</literal> specifies an arbitrary name &mdash; name
 that will be used to refer to the table within &IC;. Names can be composed
 of alphanumeric characters including underscore, and we recommend they're in
 all lower- or upper-case.
-<arg choice='plain'>source_file</arg> specifies the initial database
-source file, and <arg choice='plain'>type</arg> specifies its format.
+</para><para>
+<literal>source_file</literal> specifies the initial database
+source file, and <literal>type</literal> specifies its format.
 </para><para>
 For more about &IC; and databases, and supported formats, see &glos-database;
 glossary entry.



1.2       +22 -23    xmldocs/refs/LANG


rev 1.2, prev_rev 1.1
Index: LANG
===================================================================
RCS file: /var/cvs/xmldocs/refs/LANG,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- LANG	2 Feb 2005 11:35:58 -0000	1.1
+++ LANG	24 Jan 2006 16:06:47 -0000	1.2
@@ -1,36 +1,35 @@
-
 __NAME__ purpose
+contains the current locale for language (localization) display
 __END__
 
-
 __NAME__ synopsis
-<group choice='req'>
-	<arg choice='plain'><replaceable></replaceable></arg>
-</group>
-__END__
-
-
-__NAME__ default
-<literal></literal>
+<literal>@@LANG@@</literal>
 __END__
 
-
-__NAME__ description
-__END__
-
-
-__NAME__ notes
-__END__
-
-
 __NAME__ see also
 __END__
 
-
-__NAME__ missing
-More complete information
+__NAME__ description
+This variable contains the current &glos-locale; for language
+localization and display.
+The variable is not set in the configuration files, but is
+manipulated by the Interchange daemon while it is runnning.
+</para><para>
+If you want to define &glos-catalog; default language, set the
+<varname>MV_LANG</varname> variable.
 __END__
 
 
-__NAME__ example: 
+__NAME__ example: Reading value of LANG
+Add the following to a test Interchange page:
+<programlisting><![CDATA[
+Currency: @@LANG@@
+]]></programlisting>
+__END__
+
+__NAME__ example: Defining default language for a catalog
+Put the following in &ccf;:
+<programlisting>
+Variable MV_LANG fr_FR
+</programlisting>
 __END__



1.3       +2 -2      xmldocs/refs/export.tag


rev 1.3, prev_rev 1.2
Index: export.tag
===================================================================
RCS file: /var/cvs/xmldocs/refs/export.tag,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- export.tag	18 Dec 2005 12:51:12 -0000	1.2
+++ export.tag	24 Jan 2006 16:06:47 -0000	1.3
@@ -13,10 +13,10 @@
 	</group>
 	</entry>
 	<entry>
-	<!-- POS -->
+	Yes
 	</entry>
 	<entry>
-	<!-- REQ -->
+	Yes
 	</entry>
 	<entry>
 	<!-- DFL -->








More information about the docs mailing list