[docs] xmldocs - docelic modified 8 files
docs at icdevgroup.org
docs at icdevgroup.org
Mon Oct 18 05:58:09 EDT 2004
User: docelic
Date: 2004-10-18 09:58:09 GMT
Modified: docbook catalog.xml literals.ent
Modified: refs capture_page cgi css delete_cart get-url
Modified: no_locale_parse
Log:
- Weeding out <glossterm>s and replacing with entities pointing to glossary
entries.
On a side note, usage of <olink> instead of <glossterm linkend=> for linking
will make display in non-html versions a little poor. For example, in
.ps format it would display "NAME [http://ur.../]" which is OK when
<olinks> are used for their intended purpose, but not for glossary.
This, however, is not a problem since we link everything over entities,
so once I get <glossterm linkend=>s working properly, we'll simply do
something like s/olink/glossterm linkend/g on the entities.
Revision Changes Path
1.7 +2 -2 xmldocs/docbook/catalog.xml
rev 1.7, prev_rev 1.6
Index: catalog.xml
===================================================================
RCS file: /var/cvs/xmldocs/docbook/catalog.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- catalog.xml 30 Sep 2004 09:39:09 -0000 1.6
+++ catalog.xml 18 Oct 2004 09:58:08 -0000 1.7
@@ -7,8 +7,8 @@
<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
<public publicId="-//OASIS//DTD DocBook-Interchange XML V4.2//EN"
- uri="../docbook/docbookxi.dtd"/>
-
+ uri="../docbook/docbookxi.dtd"/>
+
<system systemId="xmldocs.css" uri="xmldocs.css" />
</catalog>
1.8 +2 -0 xmldocs/docbook/literals.ent
rev 1.8, prev_rev 1.7
Index: literals.ent
===================================================================
RCS file: /var/cvs/xmldocs/docbook/literals.ent,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- literals.ent 18 Oct 2004 09:33:51 -0000 1.7
+++ literals.ent 18 Oct 2004 09:58:08 -0000 1.8
@@ -71,10 +71,12 @@
<!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 "<olink targetdoc='glossary' targetptr='umask'>Umask</olink>">
<!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 EASIER CONSTRUCT TAG PARAMETERS LIST -->
1.6 +2 -4 xmldocs/refs/capture_page
rev 1.6, prev_rev 1.5
Index: capture_page
===================================================================
RCS file: /var/cvs/xmldocs/refs/capture_page,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- capture_page 18 Oct 2004 09:33:52 -0000 1.5
+++ capture_page 18 Oct 2004 09:58:08 -0000 1.6
@@ -66,10 +66,8 @@
__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
-<glossterm linkend='jobs'>Interchange jobs</glossterm> but, of course, nothing
-enforces this.
+and writes contents to disk. This is usually called from &jobs; but of
+course, nothing enforces this.
</para><para>
The tag is able to reproduce both standard and search results pages.
<!-- XXX link 'search results' -->
1.2 +2 -2 xmldocs/refs/cgi
rev 1.2, prev_rev 1.1
Index: cgi
===================================================================
RCS file: /var/cvs/xmldocs/refs/cgi,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- cgi 16 Oct 2004 13:23:10 -0000 1.1
+++ cgi 18 Oct 2004 09:58:08 -0000 1.2
@@ -75,8 +75,8 @@
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 <glossterm linkend='GET'>GET
-</glossterm> parameters, such as <literal>pagename?foo=bar</literal>,
+For instance, if you invoke the page with &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.
1.6 +1 -2 xmldocs/refs/css
rev 1.6, prev_rev 1.5
Index: css
===================================================================
RCS file: /var/cvs/xmldocs/refs/css,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- css 18 Oct 2004 09:33:52 -0000 1.5
+++ css 18 Oct 2004 09:58:09 -0000 1.6
@@ -108,8 +108,7 @@
<entry></entry>
<entry>
Regenerate the file on a timed basis? Default unit are minutes,
- but you can pass any standard
- <glossterm linkend='interval'>Interchange interval</glossterm>.
+ but you can pass any standard &interval;.
</entry>
</row>
1.5 +2 -3 xmldocs/refs/delete_cart
rev 1.5, prev_rev 1.4
Index: delete_cart
===================================================================
RCS file: /var/cvs/xmldocs/refs/delete_cart,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- delete_cart 16 Oct 2004 21:11:00 -0000 1.4
+++ delete_cart 18 Oct 2004 09:58:09 -0000 1.5
@@ -22,9 +22,8 @@
__NAME__ description
-This tag deletes a shopping cart from the
-<glossterm linkend="userdb">UserDB</glossterm>. This is basically the
-same as
+This tag deletes a shopping cart from the &userdb;.
+This is basically the same as
<code>[userdb function=delete_cart
nickname=<replaceable>CART_NAME</replaceable>]</code>.
__END__
1.3 +2 -3 xmldocs/refs/get-url
rev 1.3, prev_rev 1.2
Index: get-url
===================================================================
RCS file: /var/cvs/xmldocs/refs/get-url,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- get-url 6 Oct 2004 20:50:16 -0000 1.2
+++ get-url 18 Oct 2004 09:58:09 -0000 1.3
@@ -53,8 +53,7 @@
<entry></entry><entry></entry>
<entry></entry>
<entry>
- <glossterm linkend='cgi-var'>Interchange CGI variables</glossterm>
- to pass. If you want to use this, the form
+ &cgi-vars; 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
@@ -96,7 +95,7 @@
<entry></entry><entry></entry>
<entry>No timeout</entry>
<entry>Set timeout for the operation. Timeout can be specified
- as a valid <glossterm linkend="interval">Interchange interval</glossterm>
+ as a valid &interval;
(such as "3 min").</entry>
</row>
__END__
1.4 +1 -2 xmldocs/refs/no_locale_parse
rev 1.4, prev_rev 1.3
Index: no_locale_parse
===================================================================
RCS file: /var/cvs/xmldocs/refs/no_locale_parse,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- no_locale_parse 16 Oct 2004 18:13:47 -0000 1.3
+++ no_locale_parse 18 Oct 2004 09:58:09 -0000 1.4
@@ -20,8 +20,7 @@
This &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
-<glossterm linkend='ic-run-mode'>PreFork</glossterm> mode.
+It could also have some side effects in Interchange &prefork;
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.
More information about the docs
mailing list