Index: external-projects.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/external-projects.sgml,v
retrieving revision 1.13
diff -c -r1.13 external-projects.sgml
*** external-projects.sgml	16 Sep 2006 00:30:13 -0000	1.13
--- external-projects.sgml	17 Nov 2006 22:49:08 -0000
***************
*** 117,123 ****
       <listitem>
        <para>
         A <application>Tcl</> interface.
!        <ulink url="http://gborg.postgresql.org/project/pgtclng/projdisplay.php">Website.</ulink>
        </para>
       </listitem>
      </varlistentry>
--- 117,123 ----
       <listitem>
        <para>
         A <application>Tcl</> interface.
!        <ulink url="http://pgfoundry.org/projects/pgtclng">Website.</ulink>
        </para>
       </listitem>
      </varlistentry>
***************
*** 135,140 ****
--- 135,252 ----
     </para>
  
   </sect1>
+ 
+  <sect1 id="external-pl">
+   <title>Externally Developed Procedural Languages</title>
+ 
+   <indexterm>
+    <primary>Procedural Languages</primary>
+   </indexterm>
+ 
+   <para>
+    <productname>PostgreSQL</productname> includes several procedural languages 
+    with the base distribution, including plpgsql, plperl, pltcl, plpython. 
+    However just as there are many programming languages, there are many procedural
+    languages that are developed and maintained outside of the core PostgreSQL 
+    distribution. Often times this can be due to licensing issues or build 
+    requirements, so the exclusion of these languages should not be taken as a 
+    sign of deficiency, but rather each language should be evaluated for use on 
+    its own merits. 
+   </para>
+ 
+   <para>
+    Known external procedural languages:
+
+     <varlistentry>
+      <term>PL/J</term>
+      <listitem>
+       <para>
+        PL/J is a Java Stored Procedure Server for PostgreSQL.
+        <ulink url="http://plj.codehaus.org/">Project Website.</ulink>
+       </para>
+      </listitem>
+     </varlistentry>
+
+     <varlistentry>
+      <term>PL/Java</term>
+      <listitem>
+       <para>
+        PL/Java is a <application>Java</> based procedural language. 
+        <ulink url="http://pljava.projects.postgresql.org/">Project Website.</ulink>
+        <ulink url="http://www.initd.org/">Website.</ulink>
+       </para>
+      </listitem>
+     </varlistentry>
+
+     <varlistentry>
+      <term>PL/mono</term>
+      <listitem>
+       <para>
+        PL/mono is a procedural language designed to use the embedded mono 
+        runtime. It aims to support writing functions in <application>C#</a>
+        or any other language that supports <application>.Net</>.         
+        <ulink url="http://gborg.postgresql.org/project/plmono/projdisplay.php">Project Website.</ulink>
+       </para>
+      </listitem>
+     </varlistentry>
+ 
+     <varlistentry>
+      <term>PL/PHP</term>
+      <listitem>
+       <para>
+        PL/PHP is a <application>PHP</> based procedural language.
+        <ulink url="http://www.commandprompt.com/community/plphp/">Project Website.</ulink>
+       </para>
+      </listitem>
+     </varlistentry>
+ 
+     <varlistentry>
+      <term>PL/R</term>
+      <listitem>
+       <para>
+        PL/R enables you to write functions and triggers in the 
+        <ulink url="http://www.r-project.org/">R programming language</a>. 
+ 	   <ulink url="http://www.joeconway.com/plr/">Project Website.</ulink>
+       </para>
+      </listitem>
+     </varlistentry>
+ 
+     <varlistentry>
+      <term>PL/Ruby</term>
+      <listitem>
+       <para>
+        PL/Ruby is a <application>Ruby</> based procedural language. 
+        <ulink url="http://raa.ruby-lang.org/project/pl-ruby">Project Website.</ulink>
+       </para>
+      </listitem>
+     </varlistentry>
+ 
+     <varlistentry>
+      <term>PL/Scheme</term>
+      <listitem>
+       <para>
+        PL/Scheme is a procedural language based on the <application>Scheme</>
+         scheme programming language. 
+        <ulink url="http://plscheme.projects.postgresql.org/">Project Website.</ulink>
+       </para>
+      </listitem>
+     </varlistentry>
+
+    <variablelist>
+     <varlistentry>
+      <term>PL/sh</term>
+      <listitem>
+       <para>
+        PL/sh allows you to write stored procedures in a shell of your choice.
+        <ulink url="http://plsh.projects.postgresql.org/">Project Website.</ulink>
+       </para>
+      </listitem>
+     </varlistentry>
+    </variablelist>
+    </para>
+ 
+  </sect1>
+ 
   
   <sect1 id="external-extensions">
   <title>Extensions</title>
***************
*** 152,161 ****
     in that directory contains a summary. They include conversion tools,
     full-text indexing, <acronym>XML</> tools, and additional data types
     and indexing methods. Other extensions are developed independently,
!    like <application>PostGIS</>. Even <application>PostgreSQL</>
!    replication solutions are developed externally. For example,
!    <application>Slony-I</> is a popular master/slave replication solution
!    that is developed independently from the core project.
    </para>
  
    <para>
--- 264,275 ----
     in that directory contains a summary. They include conversion tools,
     full-text indexing, <acronym>XML</> tools, and additional data types
     and indexing methods. Other extensions are developed independently,
!    like <application><ulink url="http://www.postgis.org/">PostGIS</ulink></>. 
!    Even <productname>PostgreSQL</> replication solutions are developed 
!    externally. For example, <application>
!    <ulink url="http://www.slony.info">Slony-I</ulink></> is a popular 
!    master/slave replication solution that is developed independently from 
!    the core project.
    </para>
  
    <para>
Index: xplang.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/xplang.sgml,v
retrieving revision 1.31
diff -c -r1.31 xplang.sgml
*** xplang.sgml	16 Sep 2006 00:30:16 -0000	1.31
--- xplang.sgml	17 Nov 2006 22:49:10 -0000
***************
*** 31,45 ****
     <application>PL/Tcl</application> (<xref linkend="pltcl">),
     <application>PL/Perl</application> (<xref linkend="plperl">), and
     <application>PL/Python</application> (<xref linkend="plpython">).
-    Other languages can be defined by users.
-    The basics of developing a new procedural language are covered in <xref
-    linkend="plhandler">.
-   </para>
- 
-   <para>
     There are additional procedural languages available that are not
     included in the core distribution. <xref linkend="external-projects">
!    has information about finding them.
    </para>
  
    <sect1 id="xplang-install">
--- 31,41 ----
     <application>PL/Tcl</application> (<xref linkend="pltcl">),
     <application>PL/Perl</application> (<xref linkend="plperl">), and
     <application>PL/Python</application> (<xref linkend="plpython">).
     There are additional procedural languages available that are not
     included in the core distribution. <xref linkend="external-projects">
!    has information about finding them. In addition other languages can 
!    be defined by users; the basics of developing a new procedural 
!    language are covered in <xref linkend="plhandler">.
    </para>
  
    <sect1 id="xplang-install">