Index: openacs-4/packages/acs-content-repository/www/doc/guide/revisions.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/guide/revisions.adp,v
diff -u -r1.4.2.2 -r1.4.2.3
--- openacs-4/packages/acs-content-repository/www/doc/guide/revisions.adp	13 Jul 2023 12:47:28 -0000	1.4.2.2
+++ openacs-4/packages/acs-content-repository/www/doc/guide/revisions.adp	2 Sep 2024 09:40:20 -0000	1.4.2.3
@@ -4,6 +4,10 @@
 <property name="doc(title)">Content Repository Developer Guide: Creating Content
 Revisions</property>
 <master>
+<style>
+div.sect2 > div.itemizedlist > ul.itemizedlist > li.listitem {margin-top: 16px;}
+div.sect3 > div.itemizedlist > ul.itemizedlist > li.listitem {margin-top: 6px;}
+</style>              
 <h2>Creating Content Revisions</h2>
 <strong>
 <a href="/doc">ACS Documentation</a> : <a href="../index">Content Repository</a> : Developer Guide</strong>
@@ -25,14 +29,12 @@
 <kbd>content_revision.new</kbd> function. The only parameters
 required to create the revision are a title, a content item ID, and
 some text:</p>
-<pre>
-revision_id := content_revision.new( 
+<pre>revision_id := content_revision.new( 
     title   =&gt; 'A Revision',
     item_id =&gt; :item_id,
     text    =&gt; 'Once upon a time Goldilocks crossed the street.
                 Here comes a car...uh oh!  The End'
-);
-</pre>
+);</pre>
 <p>The <kbd>item_id</kbd> parameter is ID of the content item with
 which the revision is associated.</p>
 <p>The <kbd>content_item.new</kbd> function accepts a number of
@@ -43,8 +45,7 @@
 Instead of the <kbd>text</kbd> parameter, this function can be
 called with a <kbd>data</kbd> parameter, in which <kbd>data</kbd>
 is a blob:</p>
-<pre>
-revision_id := content_revision.new(
+<pre>revision_id := content_revision.new(
     title         =&gt; 'A Revision',
     description   =&gt; 'A Description of a revision',
     mime_type     =&gt; 'text/html',
@@ -54,8 +55,7 @@
     creation_date =&gt; sysdate,
     creation_user =&gt; :user_id,
     creation_ip   =&gt; :ip_address
-);
-</pre>
+);</pre>
 <h3>Insert additional attributes</h3>
 <p>Given that there is no way (AFAIK) to pass variable parameters
 to a PL/SQL function, there is no way to make
@@ -82,42 +82,34 @@
 <kbd>content_type.create_attribute</kbd>. The trigger makes it
 possible to create complete revisions with a single insert
 statement:</p>
-<pre>
-insert into cr_revisionsx (
+<pre>insert into cr_revisionsx (
   item_id, revision_id, title
 ) values (
   18, 19, 'All About Revisions'
-);
-</pre>
+);</pre>
 <p>Because a special trigger is generated for each content type
 that includes insert statements for all inherited tables, revisions
 with extended attributes may be created in the same fashion:</p>
-<pre>
-insert into cr_imagesx (
+<pre>insert into cr_imagesx (
   item_id, revision_id, title, height, width
 ) values (
   18, 19, 'A Nice Drawing', 300, 400
-);
-</pre>
+);</pre>
 <h3>Inserting content via file or text upload</h3>
 <h3>Selecting a live revision</h3>
 <p>The live revision of a content item can be obtained with the
 <kbd>content_item.get_live_revision</kbd> function:</p>
-<pre>
-live_revision_id := content_item.get_live_revision(
+<pre>live_revision_id := content_item.get_live_revision(
     item_id =&gt; :item_id
-);
-</pre>
+);</pre>
 <p>The <kbd>item_id</kbd> identifies the content item with which
 the revision is associated.</p>
 <p>Likewise, the most recent revision of a content item can be
 obtained with the <kbd>content_item.get_latest_revision</kbd>
 function:</p>
-<pre>
-latest_revision_id := content_item.get_latest_revision(
+<pre>latest_revision_id := content_item.get_latest_revision(
     item_id =&gt; :item_id
-);
-</pre>
+);</pre>
 <hr>
 <a href="mailto:karlg\@arsdigita.com">karlg\@arsdigita.com</a>
 <p>Last Modified: $&zwnj;Id: revisions.html,v 1.2 2017/08/07 23:47:47