[docs] xmldocs - docelic modified 40 files
docs at icdevgroup.org
docs at icdevgroup.org
Tue Nov 9 18:16:18 EST 2004
User: docelic
Date: 2004-11-09 23:16:18 GMT
Modified: . TODO
Modified: bin generic-autogen refs-autogen
Modified: docbook docbookxi.dtd html-chunks.xsl html-nochunks.xsl
Modified: literals.ent
Modified: glossary ad cgi-var filter
Modified: refs HitCount SocketPerms banner button capture_page
Modified: cgi.tag css delete_cart download dynamic_variables
Modified: get-url image load_cart no_html_comment_embed
Modified: no_locale_parse save_cart values-space
Modified: refs/MV_MAILFROM description
Modified: refs/MV_SMTPHOST description
Modified: refs/area description
Modified: refs/env control
Modified: refs/safe_data description
Added: refs AllowGlobal CheckHTML ConfigAllAfter
Added: ConfigAllBefore DataTrace DebugFile DumpStructure
Removed: docbook autodefs.ent
Log:
Large commit.
Fixing entity names all accross written documentation (to adhere to
new scheme - &type-name;.
Added some TODO items.
Renamed autodefs to autorefs
Various other small tricks.
Revision Changes Path
1.45 +7 -0 xmldocs/TODO
rev 1.45, prev_rev 1.44
Index: TODO
===================================================================
RCS file: /var/cvs/xmldocs/TODO,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -r1.44 -r1.45
--- TODO 6 Nov 2004 18:24:36 -0000 1.44
+++ TODO 9 Nov 2004 23:16:16 -0000 1.45
@@ -1,4 +1,6 @@
+Interpolate/reparse are two options? adjust ROW_INTERPOLATE_0/1
+
Great stuff:
For each symbol: keep a list of other symbols IT uses
For example, if I knew that, I could have seen I need to set
@@ -7,6 +9,11 @@
ADD ROLES FOR OPERATING SYSTEMS/LINUX DISTRIBUTIONS. Documentation
from Debian package should directly have all proper paths and names.
+<Racke>I name three things that IC users often didn't acknowledge:
+ namespaces (CGI, Values, Scratch)
+ parsing order ([L], variables, lists) - interpolation
+ inventing syntax doesn't buy you anything
+ IC is _not_ a programming language
Ask ndw about including [NEW!] in titles in TOC.
1.5 +19 -1 xmldocs/bin/generic-autogen
rev 1.5, prev_rev 1.4
Index: generic-autogen
===================================================================
RCS file: /var/cvs/xmldocs/bin/generic-autogen,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- generic-autogen 1 Oct 2004 16:28:38 -0000 1.4
+++ generic-autogen 9 Nov 2004 23:16:16 -0000 1.5
@@ -11,9 +11,13 @@
my %items;
my %alphabet;
my $verbose = 0;
-my $cat = shift;
+my $cat = shift; $cat ||= "glossary";
my @loaded;
my $document;
+my %sn = ( # short name
+ glossary => "glos",
+ howtos => "howto",
+);
# HEAD
my $glossary = <<__ENDP__;
@@ -67,6 +71,10 @@
-->
__ENDP__
+# OPEN GLOSSARY ENTITIES
+open ENT, "> docbook/auto$cat.ent" or
+ die "Can't wropen docbook/$cat.ent ($!)\n";
+
# LOAD ITEMS
opendir DIR, $cat or die "Can't open $cat/ ($!)\n";
readdir DIR; readdir DIR;
@@ -77,7 +85,17 @@
$items{$file} = [ <IN> ];
$alphabet{ lc(substr($file, 0, 1)) }++;
push @loaded, $file;
+
+ my $lcfile = lc $file;
+
+ ##### Should be lowercase ****
+ ##### Uppercase is temporary only
+ print ENT <<ENDO;
+<!ENTITY $sn{$cat}-$lcfile "$file">
+<!ENTITY $sn{$cat}-$file "$file">
+ENDO
print "Added $file\n" if $verbose;
+
close IN or warn "Error closing $cat/$file ($!)\n";
}
closedir DIR or warn "Error closing $cat/ ($!)\n";
1.63 +4 -2 xmldocs/bin/refs-autogen
rev 1.63, prev_rev 1.62
Index: refs-autogen
===================================================================
RCS file: /var/cvs/xmldocs/bin/refs-autogen,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- refs-autogen 7 Nov 2004 14:53:07 -0000 1.62
+++ refs-autogen 9 Nov 2004 23:16:16 -0000 1.63
@@ -40,7 +40,7 @@
my $output_spec; # 'list' produces tag list, 'xml' produces real xml source
my $output_both; # Unconditionally override $output_spec
my $no_autodefs; # Generate autodefs.ent collection of entities by default
-my $autopath = "docbook/autodefs.ent";
+my $autopath = "docbook/autorefs.ent";
my %dups; # List of symbols names that are not unique
my @page_order = (qw/purpose default structure synopsis description online example notes bugs/, "symbol type", "source", "author", "copyright", "see also");
@@ -558,9 +558,11 @@
die "UNKNOWN $g\n";
}
+ ( my $prefix = $g ) =~ s/.+(tag|conf|var)$/$1/;
+
#<!ENTITY $_ "<olink targetdoc='${g}s' targetptr='$_'>$_</olink>">
print ATD <<ENDD;
-<!ENTITY $_ "<$tag>$_</$tag>">
+<!ENTITY ${prefix}-$_ "<$tag>$_</$tag>">
ENDD
}
}
1.18 +3 -1 xmldocs/docbook/docbookxi.dtd
rev 1.18, prev_rev 1.17
Index: docbookxi.dtd
===================================================================
RCS file: /var/cvs/xmldocs/docbook/docbookxi.dtd,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- docbookxi.dtd 18 Oct 2004 14:58:51 -0000 1.17
+++ docbookxi.dtd 9 Nov 2004 23:16:16 -0000 1.18
@@ -1,6 +1,8 @@
<!ENTITY % literals SYSTEM "literals.ent"> %literals;
-<!ENTITY % autodefs SYSTEM "autodefs.ent"> %autodefs;
+<!ENTITY % autodefs SYSTEM "autorefs.ent"> %autodefs;
+<!ENTITY % glossary SYSTEM "autoglossary.ent"> %glossary;
+<!ENTITY % howtos SYSTEM "autohowtos.ent"> %howtos;
<!-- Remove MsgSet -->
<!ENTITY % compound.class "procedure|sidebar">
1.9 +5 -2 xmldocs/docbook/html-chunks.xsl
rev 1.9, prev_rev 1.8
Index: html-chunks.xsl
===================================================================
RCS file: /var/cvs/xmldocs/docbook/html-chunks.xsl,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- html-chunks.xsl 3 Oct 2004 19:05:05 -0000 1.8
+++ html-chunks.xsl 9 Nov 2004 23:16:16 -0000 1.9
@@ -2,8 +2,8 @@
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
- <xsl:import
- href="/usr/share/xml/docbook/stylesheet/nwalsh/xhtml/chunk.xsl"/>
+ <xsl:import href="http://docbook.sourceforge.net/release/xsl/current/xhtml/chunk.xsl"/>
+ <!-- <xsl:import href="/usr/share/xml/docbook/stylesheet/nwalsh/xhtml/chunk.xsl"/> -->
<!-- This section here till I find out how to pick this
information from a catalog -->
@@ -40,6 +40,9 @@
<xsl:include href="common.xsl"/>
<xsl:include href="html-common.xsl"/>
+
+ <!-- Norman Walsh gave me a nice idea and code. Since chunked documents
+ need ../ prefix in relative links, add it with XSL. -->
</xsl:stylesheet>
1.5 +2 -2 xmldocs/docbook/html-nochunks.xsl
rev 1.5, prev_rev 1.4
Index: html-nochunks.xsl
===================================================================
RCS file: /var/cvs/xmldocs/docbook/html-nochunks.xsl,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- html-nochunks.xsl 8 Aug 2004 20:05:22 -0000 1.4
+++ html-nochunks.xsl 9 Nov 2004 23:16:16 -0000 1.5
@@ -5,8 +5,8 @@
xmlns:xi="http://www.w3.org/2003/XInclude"
version="1.0">
- <xsl:import
- href="/usr/share/xml/docbook/stylesheet/nwalsh/xhtml/docbook.xsl"/>
+ <xsl:import href="http://docbook.sourceforge.net/release/xsl/current/xhtml/docbook.xsl"/>
+ <!--<xsl:import href="/usr/share/xml/docbook/stylesheet/nwalsh/xhtml/docbook.xsl"/>-->
<!-- till we use catalog for this -->
<xsl:template name="user.footer.content" >
1.13 +11 -37 xmldocs/docbook/literals.ent
rev 1.13, prev_rev 1.12
Index: literals.ent
===================================================================
RCS file: /var/cvs/xmldocs/docbook/literals.ent,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- literals.ent 7 Nov 2004 14:53:07 -0000 1.12
+++ literals.ent 9 Nov 2004 23:16:16 -0000 1.13
@@ -51,36 +51,10 @@
<!ENTITY edl "Ed LaFrance">
+<!-- GLOSSARY LINKS ARE AUTOMATIC -->
-<!-- ENTITIES TO AVOID A LOT OF REPETITION, ESPECIALLY LINKING TO GLOSSARY -->
-<!ENTITY js "<olink targetdoc='glossary' targetptr='js'>JavaScript</olink>">
-<!ENTITY CSS "<olink targetdoc='glossary' targetptr='CSS'>CSS</olink>">
-<!ENTITY anchor "<olink targetdoc='glossary' targetptr='anchor'>Anchor</olink>">
-<!ENTITY HTML "<olink targetdoc='glossary' targetptr='HTML'>HTML</olink>">
-<!ENTITY img "<olink targetdoc='glossary' targetptr='img'>Img</olink>">
-<!ENTITY link "<olink targetdoc='glossary' targetptr='link'>Link</olink>">
-<!ENTITY pragma "<olink targetdoc='glossary' targetptr='pragma'>Pragma</olink>">
-<!ENTITY MIME "<olink targetdoc='glossary' targetptr='MIME'>MIME</olink>">
-<!ENTITY ITL "<olink targetdoc='glossary' targetptr='ITL'>ITL</olink>">
-<!ENTITY SMTP "<olink targetdoc='glossary' targetptr='SMTP'>SMTP</olink>">
-<!ENTITY interpolation "<olink targetdoc='glossary' targetptr='interpolation'>Interpolation</olink>">
-<!ENTITY interpolate "<olink targetdoc='glossary' targetptr='interpolation'>Interpolate</olink>">
-<!ENTITY epoch "<olink targetdoc='glossary' targetptr='epoch'>Epoch</olink>">
-<!ENTITY userdb "<olink targetdoc='glossary' targetptr='userdb'>UserDB</olink>">
-<!ENTITY weighted "<olink targetdoc='glossary' targetptr='weighted'>Weighted</olink>">
-<!ENTITY ad "<olink targetdoc='glossary' targetptr='ad'>Ad</olink>">
-<!ENTITY scratch "<olink targetdoc='glossary' targetptr='scratch'>Scratch</olink>">
-<!ENTITY jobs "<olink targetdoc='glossary' targetptr='jobs'>Jobs</olink>">
-<!ENTITY GET "<olink targetdoc='glossary' targetptr='GET'>GET</olink>">
-<!ENTITY interval "<olink targetdoc='glossary' targetptr='interval'>Interval</olink>">
-<!ENTITY cgi-var "<olink targetdoc='glossary' targetptr='cgi-var'>CGI Variable</olink>">
-<!ENTITY cgi-vars "<olink targetdoc='glossary' targetptr='cgi-var'>CGI Variables</olink>">
-<!ENTITY umask "<glossterm baseform='umask'>umask</glossterm>">
-<!ENTITY mode "<olink targetdoc='glossary' targetptr='mode'>Mode</olink>">
-<!ENTITY filter "<olink targetdoc='glossary' targetptr='filter'>Filter</olink>">
-<!ENTITY dereferencing "<olink targetdoc='glossary' targetptr='deref'>Dereferencing</olink>">
-<!ENTITY prefork "<olink targetdoc='glossary' targetptr='ic-run-mode'>PreFork</olink>">
+<!-- ENTITIES TO AVOID A LOT OF REPETITION -->
<!ENTITY gcf "<filename>interchange.cfg</filename>">
<!ENTITY ccf "<filename>catalog.cfg</filename>">
<!ENTITY gcfs "<filename>interchange.cfg</filename> or <filename>catalog.cfg</filename>">
@@ -101,7 +75,7 @@
</entry>
<entry></entry><entry></entry>
<entry>0</entry>
- <entry>&interpolate; input?</entry>
+ <entry>&glos-interpolation; input?</entry>
</row>
">
<!ENTITY ROW_INTERPOLATE_1 "
@@ -114,7 +88,7 @@
</entry>
<entry></entry><entry></entry>
<entry>1</entry>
- <entry>&interpolate; input?</entry>
+ <entry>&glos-interpolation; input?</entry>
</row>
">
<!ENTITY ROW_HIDE_0 "
@@ -145,7 +119,7 @@
<entry></entry><entry></entry>
<entry>None.</entry>
<entry>
- &filter; to apply.
+ &glos-filter; to apply.
</entry>
</row>
">
@@ -155,7 +129,7 @@
<entry></entry><entry></entry>
<entry>None.</entry>
<entry>
- Extra &HTML; attributes. Passed verbatim.
+ Extra &glos-HTML; attributes. Passed verbatim.
</entry>
</row>
">
@@ -173,7 +147,7 @@
</entry>
<entry></entry><entry></entry>
<entry></entry>
- <entry>The usual &HTML; attributes.</entry>
+ <entry>The usual &glos-HTML; attributes.</entry>
</row>
">
<!ENTITY ROW_HTML_ext "
@@ -192,7 +166,7 @@
</entry>
<entry></entry><entry></entry>
<entry></entry>
- <entry>The usual &HTML; attributes.</entry>
+ <entry>The usual &glos-HTML; attributes.</entry>
</row>
">
<!ENTITY ROW_CSS_std "
@@ -206,7 +180,7 @@
</entry>
<entry></entry><entry></entry>
<entry></entry>
- <entry>The usual &CSS; attributes.</entry>
+ <entry>The usual &glos-CSS; attributes.</entry>
</row>
">
<!ENTITY ROW_UMASK_none "
@@ -216,7 +190,7 @@
</entry>
<entry></entry><entry></entry>
<entry></entry>
- <entry>File creation &umask;.</entry>
+ <entry>File creation &glos-umask;.</entry>
</row>
">
<!ENTITY ROW_MODE_0644 "
@@ -227,7 +201,7 @@
<entry></entry><entry></entry>
<entry><literal>0644</literal></entry>
<entry>
- File creation &mode;.
+ File creation &glos-mode;.
</entry>
</row>
">
1.3 +1 -1 xmldocs/glossary/ad
rev 1.3, prev_rev 1.2
Index: ad
===================================================================
RCS file: /var/cvs/xmldocs/glossary/ad,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- ad 19 Oct 2004 22:38:11 -0000 1.2
+++ ad 9 Nov 2004 23:16:16 -0000 1.3
@@ -9,7 +9,7 @@
advertising and promotional purposes.
</para><para>
In &IC;, when "banner" or "ad" is used to describe the functionality of
-the &banner; tag, it does not neccesarily mean an image, since you can
+the &tag-banner; tag, it does not neccesarily mean an image, since you can
put anything in the content placeholder. In fact, banner examples from
<olink targetdoc='howtos' targetptr='implementbanners'/> HOW-TO use plain
text.
1.3 +3 -3 xmldocs/glossary/cgi-var
rev 1.3, prev_rev 1.2
Index: cgi-var
===================================================================
RCS file: /var/cvs/xmldocs/glossary/cgi-var,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- cgi-var 19 Oct 2004 22:38:11 -0000 1.2
+++ cgi-var 9 Nov 2004 23:16:16 -0000 1.3
@@ -23,11 +23,11 @@
"CGI variables".
</para>
<para>
-CGI variables in &IC; are accessible using the &cgi; tag, but
+CGI variables in &IC; are accessible using the &tag-cgi; tag, but
<emphasis role='bold'>only</emphasis>
on a page directly following the form submission. In other words, you can't
-use &cgi; to retrieve a variable submitted at arbitrary past time during
-an user session - that is possible only using &value;.
+use &tag-cgi; to retrieve a variable submitted at arbitrary past time during
+an user session - that is possible only using &tag-value;.
</para>
<para>
As CGI variables contain user-supplied data, they are obviously of
1.3 +1 -1 xmldocs/glossary/filter
rev 1.3, prev_rev 1.2
Index: filter
===================================================================
RCS file: /var/cvs/xmldocs/glossary/filter,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- filter 20 Oct 2004 15:44:35 -0000 1.2
+++ filter 9 Nov 2004 23:16:16 -0000 1.3
@@ -9,7 +9,7 @@
</para><para>
There are filters that trim the text to a specified maximum length,
substitute characters in strings, make user input display- or storage-safe,
-or even serve as &value; equivalents.
+or even serve as &tag-value; equivalents.
</para><para>
Using existing filters and creating new ones is very simple.
<!-- TODO: Pointer to filters.html -->
1.2 +1 -1 xmldocs/refs/HitCount
rev 1.2, prev_rev 1.1
Index: HitCount
===================================================================
RCS file: /var/cvs/xmldocs/refs/HitCount,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- HitCount 29 Oct 2004 23:21:17 -0000 1.1
+++ HitCount 9 Nov 2004 23:16:16 -0000 1.2
@@ -15,7 +15,7 @@
Specify whether the catalog counter file should be increased on every
access to the catalog.
</para><para>
-The counter filename will be <filename>hits.<replaceable>catalog_name</replaceable></filename>, placed in the <filename class='directory'>&ICROOT;/etc/</filename> directory.
+The counter filename will be <filename>hits.<replaceable>catalog_name</replaceable></filename>, placed in the <filename class='directory'>&glos-ICROOT;/etc/</filename> directory.
__END__
__NAME__ see also
1.2 +1 -1 xmldocs/refs/SocketPerms
rev 1.2, prev_rev 1.1
Index: SocketPerms
===================================================================
RCS file: /var/cvs/xmldocs/refs/SocketPerms,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- SocketPerms 30 Oct 2004 12:32:56 -0000 1.1
+++ SocketPerms 9 Nov 2004 23:16:16 -0000 1.2
@@ -15,7 +15,7 @@
__NAME__ description
-Specify permissions (&mode;) for the Interchange UNIX-domain socket.
+Specify permissions (&glos-mode;) for the Interchange UNIX-domain socket.
</para><para>
Prepend a starting <literal>0</literal> to indicate an octal value.
__END__
1.5 +10 -8 xmldocs/refs/banner
rev 1.5, prev_rev 1.4
Index: banner
===================================================================
RCS file: /var/cvs/xmldocs/refs/banner,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- banner 18 Oct 2004 09:33:52 -0000 1.4
+++ banner 9 Nov 2004 23:16:16 -0000 1.5
@@ -11,13 +11,13 @@
<entry>Yes</entry><entry></entry>
<entry><literal>default</literal></entry>
<entry>
- For a &weighted; banner display, this field specifies
+ For a &glos-weighted; banner display, this field specifies
category name; only database entries where the
<database class='field'>category</database>
field matches this value are taken as possible candidates for display.
In an unweighted display, this field specifies
- banner code; only one database entry with the matching value in the
- <database class='field'>code</database> field should exist.
+ banner code; of course, only one database entry with the matching value in
+ the <database class='field'>code</database> field should exist.
</entry>
</row>
<row>
@@ -26,7 +26,8 @@
</entry>
<entry></entry><entry></entry>
<entry><literal>banner</literal></entry>
- <entry>The banner table name. The default is reasonable and
+ <entry>
+ The banner table name. The default is reasonable and
rarely needs to be changed.</entry>
</row>
<row>
@@ -49,7 +50,8 @@
</entry>
<entry></entry><entry></entry>
<entry><literal>banner</literal></entry>
- <entry>Banner descriptor field. In other words, name of the column that will
+ <entry>
+ Banner descriptor field. In other words, name of the column that will
contain actual banner text to display. If a proper delimiter is used, and
the <arg choice='plain'>r_field</arg> column is true, this field may contain
multiple banner texts.
@@ -108,7 +110,7 @@
<entry></entry><entry></entry>
<entry>0</entry>
<entry>
- Use &weighted;
+ Use &glos-weighted;
banner system? In a weighted system, the database is expected
to contain multiple entries with the same
<database class='field'>category</database>, and then the banners are
@@ -139,12 +141,12 @@
__NAME__ description
&IC; has a built-in banner display system designed to show
-<glossterm linkend="ad">ads</glossterm> or other
+&glos-ad; or other
messages, according to optional categories and
<glossterm linkend="weighting_system">weighting</glossterm>.
All this functionality is accessible using the <tag>banner</tag> tag.
</para><para>
-The &weighted; system,
+The &glos-weighted; system,
if used, will pre-built banners in the directory
<filename class='directory'>Banners/*/</filename> under the catalog temporary
directory (this will happen when the banners are first requested after
1.7 +7 -7 xmldocs/refs/button
rev 1.7, prev_rev 1.6
Index: button
===================================================================
RCS file: /var/cvs/xmldocs/refs/button,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- button 28 Oct 2004 10:29:14 -0000 1.6
+++ button 9 Nov 2004 23:16:16 -0000 1.7
@@ -17,7 +17,7 @@
<entry>
Image file to use. If the value starts with <literal>http</literal>,
it is used <emphasis>as-is</emphasis>. Otherwise the tag makes sure the
- image file is reachable. Requires &js;.
+ image file is reachable. Requires &glos-js;.
</entry>
</row>
<row>
@@ -25,7 +25,7 @@
<entry>Yes</entry><entry></entry>
<entry></entry>
<entry>
- Button text. &scratch; variable
+ Button text. &glos-scratch; variable
of the same name is also created to
hold the code associated with the button.
</entry>
@@ -37,8 +37,8 @@
<entry>
Button text to show while the next page is being loaded.
If defined, this is used for the
- &scratch; variable name instead of the
- <arg choice='plain'>text</arg> argument value. Requires &js;.
+ &glos-scratch; variable name instead of the
+ <arg choice='plain'>text</arg> argument value. Requires &glos-js;.
</entry>
</row>
<row>
@@ -54,7 +54,7 @@
<entry>
Text for the "Yes/No" confirmation window that will show up before
the client's browser starts with form submission.
- Requires &js;.
+ Requires &glos-js;.
</entry>
</row>
<row>
@@ -79,7 +79,7 @@
<entry><arg choice='plain'>anchor</arg></entry>
<entry></entry><entry></entry>
<entry>Value of <arg choice='plain'>text</arg></entry>
- <entry>&HTML; &anchor; name.
+ <entry>&glos-HTML; &glos-anchor; name.
</entry>
</row>
<row>
@@ -105,7 +105,7 @@
Standard, text-only submit button is output in the form of
<![CDATA[<input type='submit' ...>]]>.
</para><para>
-&js; submit button can contain an image in place of the standard
+&glos-js; submit button can contain an image in place of the standard
button text and is output as a combination of
<![CDATA[<a href=...>]]> and
<![CDATA[<img src=...>]]> HTML tags.
1.7 +2 -2 xmldocs/refs/capture_page
rev 1.7, prev_rev 1.6
Index: capture_page
===================================================================
RCS file: /var/cvs/xmldocs/refs/capture_page,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- capture_page 18 Oct 2004 09:58:08 -0000 1.6
+++ capture_page 9 Nov 2004 23:16:16 -0000 1.7
@@ -66,7 +66,7 @@
__NAME__ description
This tag processes the page (as if the user visited it with the browser),
-and writes contents to disk. This is usually called from &jobs; but of
+and writes contents to disk. This is usually called from &glos-jobs; but of
course, nothing enforces this.
</para><para>
The tag is able to reproduce both standard and search results pages.
@@ -79,7 +79,7 @@
__NAME__ notes
-See the &umask; glossary entry.
+See the &glos-umask; glossary entry.
__END__
1.2 +2 -2 xmldocs/refs/cgi.tag
rev 1.2, prev_rev 1.1
Index: cgi.tag
===================================================================
RCS file: /var/cvs/xmldocs/refs/cgi.tag,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- cgi.tag 28 Oct 2004 19:41:19 -0000 1.1
+++ cgi.tag 9 Nov 2004 23:16:16 -0000 1.2
@@ -75,11 +75,11 @@
In other words, the CGI values are reset on each request and you can
only access the values directly submitted to the current page.
</para><para>
-For instance, if you invoke the page with &GET;
+For instance, if you invoke the page with &glos-GET;
parameters, such as <literal>pagename?foo=bar</literal>,
then the value of the <literal>foo</literal> CGI variable will be
accessible using <code>[cgi foo]</code> in
-&ITL; or <code>$CGI->{foo}</code> in embedded Perl.
+&glos-itl; or <code>$CGI->{foo}</code> in embedded Perl.
__END__
__NAME__ notes
1.8 +6 -6 xmldocs/refs/css
rev 1.8, prev_rev 1.7
Index: css
===================================================================
RCS file: /var/cvs/xmldocs/refs/css,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- css 28 Oct 2004 10:29:14 -0000 1.7
+++ css 9 Nov 2004 23:16:16 -0000 1.8
@@ -16,7 +16,7 @@
<entry>Yes</entry><entry>Yes</entry>
<entry></entry>
<entry>
- Name of the &CSS; file. The name will be forced to lowercase, and
+ Name of the &glos-CSS; file. The name will be forced to lowercase, and
the ".css" extension will be added unconditionally.
</entry>
</row>
@@ -62,7 +62,7 @@
<entry></entry><entry></entry>
<entry></entry>
<entry>
- Literal, in-place &CSS; definition. See <xref linkend="css_examples"/>.
+ Literal, in-place &glos-CSS; definition. See <xref linkend="css_examples"/>.
</entry>
</row>
<row>
@@ -72,7 +72,7 @@
<entry></entry><entry></entry>
<entry></entry>
<entry>
- The <arg choice='plain'>media</arg> attribute for the &link; &HTML; tag.
+ The <arg choice='plain'>media</arg> attribute for the &glos-link; &glos-HTML; tag.
For example, <literal>PRINT</literal>.
</entry>
</row>
@@ -108,7 +108,7 @@
<entry></entry>
<entry>
Regenerate the file on a timed basis? Default unit are minutes,
- but you can pass any standard &interval;.
+ but you can pass any standard &glos-interval;.
</entry>
</row>
@@ -116,7 +116,7 @@
__NAME__ description
-This tag builds a &CSS; file (from a <option>Variable</option> or other
+This tag builds a &glos-CSS; file (from a <option>Variable</option> or other
sources) and generates a link to it.
</para><para>
Note that if you're providing the <arg choice='plain'>literal</arg> argument,
@@ -144,7 +144,7 @@
<example>
<title>Using literal</title>
<para>
- You can either save your CSS in a &scratch;
+ You can either save your CSS in a &glos-scratch;
variable, or provide it
directly in-place. Here are both variants:
</para>
1.6 +1 -1 xmldocs/refs/delete_cart
rev 1.6, prev_rev 1.5
Index: delete_cart
===================================================================
RCS file: /var/cvs/xmldocs/refs/delete_cart,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- delete_cart 18 Oct 2004 09:58:09 -0000 1.5
+++ delete_cart 9 Nov 2004 23:16:16 -0000 1.6
@@ -22,7 +22,7 @@
__NAME__ description
-This tag deletes a shopping cart from the &userdb;.
+This tag deletes a shopping cart from the &glos-userdb;.
This is basically the same as
<code>[userdb function=delete_cart
nickname=<replaceable>CART_NAME</replaceable>]</code>.
1.5 +2 -2 xmldocs/refs/download
rev 1.5, prev_rev 1.4
Index: download
===================================================================
RCS file: /var/cvs/xmldocs/refs/download,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- download 16 Oct 2004 18:13:47 -0000 1.4
+++ download 9 Nov 2004 23:16:16 -0000 1.5
@@ -17,8 +17,8 @@
__NAME__ description
-The main function of this &pragma; is to prevent any
-&interpolation; of the output.
+The main function of this &glos-pragma; is to prevent any
+&glos-interpolation; of the output.
It helps to preserve the downloads intact if they
happen to contain constructs similar to
<literal>__<replaceable>VAR</replaceable>__</literal>
1.3 +1 -1 xmldocs/refs/dynamic_variables
rev 1.3, prev_rev 1.2
Index: dynamic_variables
===================================================================
RCS file: /var/cvs/xmldocs/refs/dynamic_variables,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- dynamic_variables 6 Oct 2004 20:50:16 -0000 1.2
+++ dynamic_variables 9 Nov 2004 23:16:16 -0000 1.3
@@ -17,7 +17,7 @@
__NAME__ description
-This &pragma; enables configuration directives (<option>Variable</option>s,
+This &glos-pragma; enables configuration directives (<option>Variable</option>s,
most notably) to be dynamically updated from system files and databases.
</para><para>
It only makes sense to use this in combination with the
1.4 +3 -3 xmldocs/refs/get-url
rev 1.4, prev_rev 1.3
Index: get-url
===================================================================
RCS file: /var/cvs/xmldocs/refs/get-url,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- get-url 18 Oct 2004 09:58:09 -0000 1.3
+++ get-url 9 Nov 2004 23:16:16 -0000 1.4
@@ -44,7 +44,7 @@
</entry>
<entry></entry><entry></entry>
<entry><literal>x-www-form-urlencoded</literal></entry>
- <entry>&MIME; content type.</entry>
+ <entry>&glos-MIME; content type.</entry>
</row>
<row>
<entry>
@@ -53,7 +53,7 @@
<entry></entry><entry></entry>
<entry></entry>
<entry>
- &cgi-vars; to pass. If you want to use this, the form
+ &glos-cgi-var; to pass. If you want to use this, the form
method should be <literal>POST</literal> or <literal>PUT</literal>.
The list can be ampersand-separated, like
<literal><![CDATA[fname=Brev&lname=Patterson&state=UT]]></literal>, and
@@ -95,7 +95,7 @@
<entry></entry><entry></entry>
<entry>No timeout</entry>
<entry>Set timeout for the operation. Timeout can be specified
- as a valid &interval;
+ as a valid &glos-interval;
(such as "3 min").</entry>
</row>
__END__
1.7 +62 -7 xmldocs/refs/image
rev 1.7, prev_rev 1.6
Index: image
===================================================================
RCS file: /var/cvs/xmldocs/refs/image,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- image 28 Oct 2004 10:29:14 -0000 1.6
+++ image 9 Nov 2004 23:16:16 -0000 1.7
@@ -1,3 +1,40 @@
+
+ By default, the width and height are maximum values. That is,
+ the image is expanded or contracted to fit the width and height
+ value while maintaining the aspect ratio of the image. Append an
+ exclamation point to the geometry to force the image size to
+ exactly the size you specify. For example, if you specify
+ 640x480! the image width is set to 640 pixels and height to 480.
+
+
+ If only the width is specified, the width assumes the value and
+ the height is chosen to maintain the aspect ratio of the image.
+ Similarly, if only the height is specified (e.g., -geometry
+ x256), the width is chosen to maintain the aspect ratio.
+
+
+ To specify a percentage width or height instead, append %. The
+ image size is multiplied by the width and height percentages to
+ obtain the final image dimensions. To increase the size of an
+ image, use a value greater than 100 (e.g. 125%). To decrease an
+ image's size, use a percentage less than 100.
+
+
+ Use @ to specify the maximum area in pixels of an image.
+
+
+ Use > to change the dimensions of the image only if its width or
+ height exceeds the geometry specification. < resizes the image
+ only if both of its dimensions are less than the geometry speci-
+ fication. For example, if you specify '640x480>' and the image
+ size is 256x256, the image size does not change. However, if the
+ image is 512x512 or 1024x1024, it is resized to 480x480.
+ Enclose the geometry specification in quotation marks to prevent
+ the < or > from being interpreted by your shell as a file redi-
+ rection.
+
+
+
__NAME__ purpose
general purpose tag for generating HTML <img> tags
__END__
@@ -69,7 +106,7 @@
<entry>
Only return the value of
<option>ImageDir</option> or <option>ImageDirSecure</option> config
- directives? This is primarily used in &js; code to discover the
+ directives? This is primarily used in &glos-js; code to discover the
appropriate path to prepend to image files.
</entry>
</row>
@@ -108,7 +145,7 @@
</entry>
<entry>
Use <classname>Image::Size</classname> Perl module to determine image
- dimensions and specify them in the &img; tag?
+ dimensions and specify them in the &glos-img; tag?
</entry>
</row>
<row>
@@ -123,23 +160,35 @@
</entry>
</row>
<row>
- <entry><arg choice='plain'>makesize</arg></entry>
+ <entry>
+ <group choice='opt'>
+ <arg choice='plain'>makesize</arg>
+ <arg choice='plain'>resize</arg>
+ <arg choice='plain'>geometry</arg>
+ </group>
+ </entry>
<entry></entry><entry></entry>
<entry>
</entry>
<entry>
If ImageMagick is installed, you can display an arbitrary size of
the image, creating it if necessary. This would create a subdirectory
- corresponding to the size, (i.e. 64x48) and copy the source image to it.
+ corresponding to the size, (i.e. "64x48") and copy the source image to it.
It would then use the <command>mogrify</command> command to resize.
This requires a writable image directory, of course.
If not found in the PATH,
the location of the <command>mogrify</command> can be defined with the
<varname>IMAGE_MOGRIFY</varname> variable.
- This would also temporarily set &umask; to 2 during the creation of files
+ This would also temporarily set &glos-umask; to 2 during the creation of files
and directories.
The value is specified as
- <literal><replaceable>A</replaceable>x<replaceable>B</replaceable></literal>.
+ <literal><replaceable>A</replaceable>x<replaceable>B</replaceable></literal>,
+ <literal><replaceable>A</replaceable></literal> or
+ <literal>x<replaceable>B</replaceable></literal>, followed by up to two
+ <literal>+- <replaceable>offset</replaceable></literal> specifications,
+ followed by none or one of <literal>%@!<></literal>.
+ For a complete syntax, see <command>mogrify</command>
+ <literal>-geometry</literal> parameter.
</entry>
</row>
<row>
@@ -173,7 +222,7 @@
Value of the <arg choice='plain'>alt</arg> attribute.
</entry>
<entry>
- Text to use for the &img;'s <arg choice='plain'>title</arg>
+ Text to use for the &glos-img;'s <arg choice='plain'>title</arg>
attribute. This is supported by newer browsers to provide things like
rollover tips.
</entry>
@@ -205,6 +254,12 @@
automatically pull product
descriptions from the database (for <arg choice='plain'>alt</arg> and
<arg choice='plain'>title</arg> attributes).
+__END__
+
+
+__NAME__ notes
+This tag makes a lot of assumptions about your setup, and sometimes it
+might not be the best tool for the job.
__END__
1.2 +2 -2 xmldocs/refs/load_cart
rev 1.2, prev_rev 1.1
Index: load_cart
===================================================================
RCS file: /var/cvs/xmldocs/refs/load_cart,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- load_cart 16 Oct 2004 21:53:36 -0000 1.1
+++ load_cart 9 Nov 2004 23:16:16 -0000 1.2
@@ -26,7 +26,7 @@
<entry>
Cart specification string. The string is colon-separated, and contains three
fields: the cart name, time of save, and type. Time of save is measured
- in seconds since the &epoch;. Type can be
+ in seconds since the &glos-epoch;. Type can be
<literal>c</literal> (cart) or <literal>r</literal> (recurring).
</entry>
</row>
@@ -35,7 +35,7 @@
__NAME__ description
-This tag loads a cart from the &userdb;.
+This tag loads a cart from the &glos-userdb;.
<emphasis role='bold'>The loaded cart will be merged with the current
one</emphasis>.
__END__
1.4 +2 -2 xmldocs/refs/no_html_comment_embed
rev 1.4, prev_rev 1.3
Index: no_html_comment_embed
===================================================================
RCS file: /var/cvs/xmldocs/refs/no_html_comment_embed,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- no_html_comment_embed 16 Oct 2004 18:13:47 -0000 1.3
+++ no_html_comment_embed 9 Nov 2004 23:16:16 -0000 1.4
@@ -17,7 +17,7 @@
__NAME__ description
-Many &HTML; editing applications do not support &ITL; directly, and some
+Many &glos-HTML; editing applications do not support &glos-itl; directly, and some
(thinking it doesn't belong to the page) ruin your work. This is
understandable to an extent, because some ITL tags (such as <tag>list</tag>)
appear in places that raise errors with HTML syntax checking algorithms.
@@ -38,7 +38,7 @@
]]>
</programlisting>
<para>
-Setting the <pragma>no_html_comment_embed</pragma> &pragma; instructs
+Setting the <pragma>no_html_comment_embed</pragma> &glos-pragma; instructs
Interchange
<emphasis role='bold'>not</emphasis> to parse and interpolate any HTML
comments. With this pragma enabled, the above example would not display
1.5 +2 -2 xmldocs/refs/no_locale_parse
rev 1.5, prev_rev 1.4
Index: no_locale_parse
===================================================================
RCS file: /var/cvs/xmldocs/refs/no_locale_parse,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- no_locale_parse 18 Oct 2004 09:58:09 -0000 1.4
+++ no_locale_parse 9 Nov 2004 23:16:16 -0000 1.5
@@ -17,10 +17,10 @@
__NAME__ description
-This &pragma; disables parsing of <tag>L</tag> and <tag>LC</tag> tags.
+This &glos-pragma; disables parsing of <tag>L</tag> and <tag>LC</tag> tags.
</para><para>
This is only used in the Admin UI and is not of interest to the general public.
-It could also have some side effects in Interchange &prefork;
+It could also have some side effects in Interchange &glos-ic-run-mode;
If you have enough traffic that you want to run in PreFork mode, you will
be wanting to move the Admin UI away from the customer-facing side anyway,
so this will not be a problem.
1.2 +2 -2 xmldocs/refs/save_cart
rev 1.2, prev_rev 1.1
Index: save_cart
===================================================================
RCS file: /var/cvs/xmldocs/refs/save_cart,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- save_cart 16 Oct 2004 21:53:36 -0000 1.1
+++ save_cart 9 Nov 2004 23:16:16 -0000 1.2
@@ -24,7 +24,7 @@
<entry>
Cart specification string. The string is colon-separated, and contains three
fields: the cart name, time of save, and type. Time of save is measured
- in seconds since the &epoch;. Type can be
+ in seconds since the &glos-epoch;. Type can be
<literal>c</literal> (cart) or <literal>r</literal> (recurring).
</entry>
</row>
@@ -41,7 +41,7 @@
__NAME__ description
-This tag saves current cart to &userdb;.
+This tag saves current cart to &glos-userdb;.
</para><para>
Note that the cart name does not have to be unique. If there are more carts
with the same nickname, an index will be added.
1.4 +1 -1 xmldocs/refs/values-space
rev 1.4, prev_rev 1.3
Index: values-space
===================================================================
RCS file: /var/cvs/xmldocs/refs/values-space,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- values-space 18 Oct 2004 09:33:52 -0000 1.3
+++ values-space 9 Nov 2004 23:16:16 -0000 1.4
@@ -18,7 +18,7 @@
<entry>
Copy all values from the current
namespace to the new one before switching to it?
- (&dereferencing; on nested data structures is
+ (&glos-deref; on nested data structures is
<emphasis role='bold'>not</emphasis> performed).
</entry>
</row>
1.1 xmldocs/refs/AllowGlobal
rev 1.1, prev_rev 1.0
Index: AllowGlobal
===================================================================
__NAME__ purpose
list catalogs that may define subroutines and tags which operate with full Interchange server permissions
__END__
__NAME__ missing
Fix value type in directive definition?
__END__
__NAME__ see also
__END__
__NAME__ synopsis
<group choice='req'>
<arg choice='plain' rep='repeat'><replaceable>catalog</replaceable></arg>
</group>
__END__
__NAME__ description
Specify catalogs that may define subroutines and tags that can operate with the full permissions of the &IC; server.
</para><para>
Don't use this directive unless the catalog user is completely trusted.
__END__
__NAME__ example
<example>
<title></title>
<programlisting>
AllowGlobal tutorial1 tutorial2
</programlisting>
</example>
__END__
1.1 xmldocs/refs/CheckHTML
rev 1.1, prev_rev 1.0
Index: CheckHTML
===================================================================
__NAME__ purpose
check the generated HTML code with an external program
__END__
__NAME__ missing
Doesn't work, fix the code?
__END__
__NAME__ synopsis
<group choice='req'>
<arg choice='plain'><replaceable>program name and arguments</replaceable></arg>
</group>
__END__
__NAME__ description
Defines the name of an external program which will be invoked
to check the generated page HTML code for correctness
(<command>/usr/bin/weblint</command>, for example).
</para><para>
Note that you need to put <code>[flag checkhtml]</code> on your page,
(or wrap only a block of HTML code to check in
<code>[tag flag checkhtml]...[/tag]</code>)
to trigger the actual invocation of the specified external command.
</para><para>
The output of the HTML checker program will be included in the
output page, so you might want to wrap it in HTML comments
(<!-- ... -->). Then you can check it out by viewing the HTML
page source in your browser.
</para><para>
If you want a quick way to enable or disable this feature, without
modifying each HTML page individually, put <code>__CHECK_HTML__</code>
on every page (or ideally, in a template). Then, to enable the
checker, define <code>Variable CHECK_HTML [flag checkhtml]</code> in
&gcf;. To disable it, leave the variable value empty.
__END__
__NAME__ notes
Leaving this directive enabled on a production server usually leads to
unneccesary performance degradation. The additional process spawn
(and the time it takes to complete) every time a page is visited is
very costly.
__END__
__NAME__ example
<example>
<title></title>
<programlisting>
CheckHTML /usr/local/bin/weblint -s -
</programlisting>
</example>
__END__
1.1 xmldocs/refs/ConfigAllAfter
rev 1.1, prev_rev 1.0
Index: ConfigAllAfter
===================================================================
__NAME__ purpose
config files to read as part of every catalog's configuration, after all its files are read in first
__END__
__NAME__ see also
__END__
__NAME__ synopsis
<group choice='req'>
<arg choice='plain' rep='repeat'><replaceable>config file</replaceable></arg>
</group>
__END__
__NAME__ description
Specify configuration files to read as a part of every catalog's configuration, after all other corresponding catalog config files are processed.
</para><para>
This is useful to catch user configuration errors, supply missing values,
or force your settings over user's configuration.
__END__
__NAME__ example
<example>
<title></title>
<programlisting>
ConfigAllAfter check_actions.cfg check_variables.cfg
</programlisting>
</example>
__END__
1.1 xmldocs/refs/ConfigAllBefore
rev 1.1, prev_rev 1.0
Index: ConfigAllBefore
===================================================================
__NAME__ purpose
config files to read as part of every catalog's configuration, before any of its files are read in
__END__
__NAME__ see also
ConfigAllAfter
__END__
__NAME__ synopsis
<group choice='req'>
<arg choice='plain' rep='repeat'><replaceable>config file</replaceable></arg>
</group>
__END__
__NAME__ description
Specify configuration files to read as a part of every catalog's configuration, before any other corresponding catalog config files are processed.
__END__
__NAME__ example
<example>
<title></title>
<programlisting>
ConfigAllBefore set_actions.cfg set_variables.cfg
</programlisting>
</example>
__END__
1.1 xmldocs/refs/DataTrace
rev 1.1, prev_rev 1.0
Index: DataTrace
===================================================================
__NAME__ purpose
trace DBI calls with variable granularity
__END__
__NAME__ synopsis
<group choice='req'>
<arg choice='plain'><replaceable>granularity</replaceable></arg>
</group>
__END__
__NAME__ description
Trace DBI calls with variable granularity.
As this tends to produce large ammounts of output, only use it if
there's a strong chance that your problem is related to DBI.
</para><para>
Setting of <literal>0</literal> disables tracing.<sbr/>
Setting of <literal>1</literal> traces DBI method calls with return values (or errors)<sbr/>
Setting of <literal>2</literal> traces as (1) plus the parameters used in method calls<sbr/>
Setting of <literal>3</literal> traces as (2) plus some high-level information from the driver, and some internal information from the DBI<sbr/>
Setting of <literal>4</literal> traces as (3) plus more detailed information from the driver. Also includes DBI mutex information when using threaded Perl<sbr/>
Setting of <literal>5</literal> traces as (4) plus more and more obscure information<sbr/>
</para><para>
Trace level of <literal>1</literal> is suitable in most situations.
__END__
__NAME__ see also
DebugFile, DEBUG
__END__
__NAME__ notes
Keep in mind that, since the trace output is directed to the debug file,
you need to have the <varname>DEBUG</varname> global variable
defined, and <option>DebugFile</option> properly set.
__END__
__NAME__ example
<example>
<title></title>
<programlisting>
Variable DEBUG 1
DebugFile /tmp/icdebug
DataTrace 1
</programlisting>
</example>
__END__
1.1 xmldocs/refs/DebugFile
rev 1.1, prev_rev 1.0
Index: DebugFile
===================================================================
__NAME__ purpose
specify Interchange debug output filename
__END__
__NAME__ missing
Link to script for managing logDebug statements (to be written first ;-)
__END__
__NAME__ synopsis
<group choice='req'>
<arg choice='plain'><replaceable>filename</replaceable></arg>
</group>
__END__
__NAME__ description
Specify the Interchange debug output file. If the filename is not absolute,
it is treated relative to the Interchange root directory (ICROOT).
</para><para>
When enabled, the debug file will gather output of the
<function>::logDebug()</function> Interchange statements and Perl warnings
(if they are enabled).
__END__
__NAME__ see also
DEBUG, DataTrace
__END__
__NAME__ notes
Keep in mind that
you need to have the <varname>DEBUG</varname> global variable
defined.
</para><para>
Also, as the <function>::logDebug()</function> statements are disabled
(commented)
by default in Interchange sources, you'll probably want to use a special
script for managing debug statements.
__END__
__NAME__ example
<example>
<title></title>
<programlisting>
Variable DEBUG 1
DebugFile /tmp/icdebug
</programlisting>
</example>
__END__
1.1 xmldocs/refs/DumpStructure
rev 1.1, prev_rev 1.0
Index: DumpStructure
===================================================================
__NAME__ purpose
dump Interchange server and catalog structure for each catalog
__END__
__NAME__ synopsis
<group choice='req'>
<arg choice='plain'>Yes</arg>
<arg choice='plain'>No</arg>
</group>
__END__
__NAME__ description
Instruct Interchange to dump the structure of catalogs and the Interchange server to files named <filename><replaceable>catalog_name</replaceable>.structure</filename>. Use this to see how directives have been set.
</para><para>
The catalog structure files are dumped relative to catalog roots (CATROOTs).
__END__
__NAME__ see also
DEBUG, DataTrace, DebugFile
__END__
__NAME__ example
<example>
<title></title>
<programlisting>
DumpStructure Yes
</programlisting>
</example>
__END__
1.5 +1 -1 xmldocs/refs/MV_MAILFROM/description
rev 1.5, prev_rev 1.4
Index: description
===================================================================
RCS file: /var/cvs/xmldocs/refs/MV_MAILFROM/description,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- description 6 Oct 2004 20:50:17 -0000 1.4
+++ description 9 Nov 2004 23:16:17 -0000 1.5
@@ -1,3 +1,3 @@
-If &SMTP; is used to send
+If &glos-SMTP; is used to send
mail from Interchange,
this variable specifies the default sender e-mail address.
1.5 +1 -1 xmldocs/refs/MV_SMTPHOST/description
rev 1.5, prev_rev 1.4
Index: description
===================================================================
RCS file: /var/cvs/xmldocs/refs/MV_SMTPHOST/description,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- description 6 Oct 2004 20:50:17 -0000 1.4
+++ description 9 Nov 2004 23:16:17 -0000 1.5
@@ -1,2 +1,2 @@
-If &SMTP; is used to send mail from Interchange,
+If &glos-SMTP; is used to send mail from Interchange,
this variable specifies the hostname to use.
1.4 +1 -1 xmldocs/refs/area/description
rev 1.4, prev_rev 1.3
Index: description
===================================================================
RCS file: /var/cvs/xmldocs/refs/area/description,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- description 6 Oct 2004 20:50:17 -0000 1.3
+++ description 9 Nov 2004 23:16:17 -0000 1.4
@@ -1,4 +1,4 @@
-The <tag>area</tag> tag expands to a proper hypertext URL &link; which
+The <tag>area</tag> tag expands to a proper hypertext URL &glos-link; which
preserves Interchange session information and arguments passed onto
the targeted page. The target page argument you supply is treated relatively
to the <filename class='directory'>pages/</filename> directory inside your
1.5 +1 -1 xmldocs/refs/env/control
rev 1.5, prev_rev 1.4
Index: control
===================================================================
RCS file: /var/cvs/xmldocs/refs/env/control,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- control 1 Oct 2004 21:04:41 -0000 1.4
+++ control 9 Nov 2004 23:16:17 -0000 1.5
@@ -1,3 +1,3 @@
purpose: provides read-only access to the HTTP environment variables
see also: var
-author: &edl;,, &ICDEVGROUP;
+author: &edl;, &ICDEVGROUP;
1.8 +1 -1 xmldocs/refs/safe_data/description
rev 1.8, prev_rev 1.7
Index: description
===================================================================
RCS file: /var/cvs/xmldocs/refs/safe_data/description,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- description 16 Oct 2004 18:13:47 -0000 1.7
+++ description 9 Nov 2004 23:16:17 -0000 1.8
@@ -1,4 +1,4 @@
-By default, Interchange does not allow data returned from the databases to be interpolated (all the [s are converted to an &HTML; entity (&#91;) and displayed literally). Setting this pragma eliminates the restriction and passes [s through for interpolation).
+By default, Interchange does not allow data returned from the databases to be interpolated (all the [s are converted to an &glos-HTML; entity (&#91;) and displayed literally). Setting this pragma eliminates the restriction and passes [s through for interpolation).
</para><para>
If you want to have tags in your database and display them in Interchange pages (to say, display <tag>page</tag> links for internal hyperlinks in your product descriptions), you need to enable this pragma.
Some things to consider, though:
More information about the docs
mailing list