update lua class doc.

[ardour-manual-diverged] / _manual / 11_working-with-plugins.html

diff --git a/_manual/11_working-with-plugins.html b/_manual/11_working-with-plugins.html
index 09256dac165166a746d92cd5ccac0afbce1abae3..ae054adaec5e6b041a2bd62841ebdaf29ee4727b 100644 (file)
--- a/_manual/11_working-with-plugins.html
+++ b/_manual/11_working-with-plugins.html
@@ -5,7 +5,7 @@ title: Working With Plugins
 
 
 
-<p>Plugins are bits of software that get loaded by Ardour in order to:</p>
+<p><dfn>Plugins</dfn> are bits of software that get loaded by Ardour in order to:</p>
 <ul>
   <li>Create various audio or MIDI effects
   </li>
@@ -16,7 +16,7 @@ title: Working With Plugins
 <p>Ardour does not come with any built-in signal processors of its own
 (other than volume faders) and it also generally doesn't ship with any
 plugins. They are written by 3rd parties, though we do provide <a href="/working-with-plugins/getting-plugins/">some
-  information on how to get them.</a>.
+  information on how to get them</a>.
 </p>
 
 <p>
@@ -24,24 +24,30 @@ Ardour supports a variety of different plugin standards:
 </p>
 <dl class="narrower-table">
 
-  <dt>LADSPA</dt>
-  <dd>An early, simple, lightweight plugin API, audio effects only,
+  <dt><abbr title="Linux Audio Developers' Simple Plugin API">LADSPA</abbr></dt>
+  <dd>An early, simple, lightweight plugin <abbr title="Application
+  Programming Interface">API</abbr>, audio effects only,
   plugins have no editors/GUI of their own (Ardour provides one, however).</dd>
-
-  <dt>LV2</dt>
-  <dd>An extensible, full-featured plugin API, audio and MIDI, plugins can provide their own editors/GUIs</dd>
-
-  <dt>AudioUnit</dt>
+  <dt><abbr title="LADSPA Version 2">LV2</abbr></dt>
+  <dd>An extensible, full-featured plugin API, audio and <abbr
+  title="Musical Instrument Digital Interface">MIDI</abbr>, plugins can provide their
+  own  <abbr title="Graphical User Interface">GUI</abbr>s</dd>
+  <dt><abbr title="Audio Unit">AU</abbr></dt>
   <dd>OS X only, full featured, audio and MIDI, plugins can provide their own GUI</dd>
 
-  <dt>Linux VST</dt>
-  <dd>Plugins using Steinberg's VST plugin standard but compiled specifically for Linux</dd>
+  <dt><abbr title="Virtual Studio Technology">VST</abbr></dt>
+  <dd>Plugins using Steinberg's VST plugin standard. Varies by platform:
+    <dl>
+    <dt>on Linux</dt><dd>(native) Linux VST plugins fully supported (VST2.4)</dd>
+    <dt>on Windows</dt><dd>(native) Windows VST plugins fully supported (VST2.4)</dd>
+    <dt>on OS X</dt><dd>Not supported, unless you use a VST&lt;&gt;AU
+    bridge plugin. Similar to Apple's Logic DAW.</dd>
+  </dl>
+  </dd>
 
-  <dt>Windows VST</dt>
-  <dd>Plugins using Steinberg's VST plugin standard but compiled for
-  Windows. <em>Support for this plugin format is not available in
-  regular builds of
-  Ardour. <a href="/working-with-plugins/windows-vst-support">Read
+  <dt>Windows VST Plugins on Linux</dt>
+  <dd>VST plugins for Windows, but being used on Linux. <em>Not
+  supported by normal builds of Ardour. <a href="/working-with-plugins/windows-vst-support">Read
   more...</a></em>
   </dd>
 </dl>
@@ -49,10 +55,10 @@ Ardour supports a variety of different plugin standards:
 <h2>Adding/Removing/Copying Plugins</h2>
 
 <p>Within Ardour, plugins are just another type
-of <code>Processor</code> and so the techniques for
+of <dfn>Processor</dfn> and so the techniques for
 adding/removing/copying/moving processors apply to plugins as
 well. These techniques are covered on
-the <a href="/working-with-plugins/the-processor-box">Processor
+the <a href="/working-with-plugins/processor-box">Processor
 Box</a> page.</p>
 
 {% children %}