<sect2 id="nsplugins">
<title>&Netscape; Plugins</title>

<sect3 id="nsplugins-intro">
<title>Introduction</title>

<para>As &Netscape;'s <application>Navigator</application> has been a web browsing standard for many years, so-called &Netscape; plugins have appeared that allow rich web content. Using those plugins, web sites can contain <acronym>PDF</acronym> files, flash animations, video, &etc; With &konqueror;, you can still use these plugins to take advantage of rich web content.</para>

<note><para>&Netscape; plugins should not be confused with &konqueror; plugins. The latter ones specifically extend &konqueror;'s functionality; they are normally not used to display rich web content.</para></note>

</sect3>

<sect3 id="nsplugins-scan">
<title>Scan</title>

<para>&konqueror; has to know where your &Netscape; plugins are installed. This can be in several places, &ie; you might have system-wide plugins in <filename class="directory">/opt/netscape/plugins</filename> and your personal plugins in <filename class="directory">$<envar>HOME</envar>/.netscape/plugins</filename>. However, &konqueror; will not automatically use the installed plugins: it first has to scan a list of folders. You can initiate the scan by clicking <guibutton>Scan for new plugins</guibutton>. Alternatively, you can enable <guilabel>Scan for new plugins at &kde; startup</guilabel> so &konqueror; will scan the appropriate folders every time &kde; starts up, to see whether new plugins have been installed.</para>

<note><para>Enabling <guilabel>Scan for new plugins at &kde; startup</guilabel> can considerably slow down the startup procedure, and is known to give difficulty on certain installations. Turn this option off if you experience problems.</para></note>

<para>To find plugins, &konqueror; will look in the folders specified in the <guilabel>Scan Folders</guilabel> frame. When you use this control module for the first time, this list will already be filled with reasonable paths that should work on most operating systems. If you need to provide a new path, click the <guibutton>New</guibutton> button; then you can either enter the new path in the text edit box to the left, or choose a folder using the file dialogue by clicking the <guibutton>New...</guibutton> button. As scanning the folders can take a little time, you might want to remove folders from the list where you know that no plugins are installed: do this by selecting a folder and clicking <guibutton>Remove</guibutton>. Using the <guibutton>Up</guibutton> and <guibutton>Down</guibutton> buttons you can change the order in which folders will be scanned by moving the selected folder up or down.</para>

<para>As usual, click <guibutton>Apply</guibutton> to save your changes permanently.</para>

</sect3>

<sect3 id="nsplugins-plugins">
<title>Plugins</title>

<para>In this tab, you can see a list of the &Netscape; plugins found by &konqueror;, displayed as a tree. Double click on a plugin to fold it out and you'll see that the different mime types this plugin can handle will be displayed as branches. Fold out a mime type to see its info.</para>

<para>This tab is mostly for informational purposes. The only configurable option is <guilabel>Use artsdsp to pipe plugin sound through aRts</guilabel>, which is enabled by default. Disable this if you wish plugins to use their own method for sounds, and you have configured &arts; in such a way that third-party applications can do so (for example, by having it exit when idle, or by having it use a custom sound device on modern soundcards which allow this.)</para>

</sect3>

<sect3 id="nsplugins-author">
<title>Section Author</title>

<para>This section written by: Jost Schenck <email>jost@schenck.de</email></para>

<para>Conversion to British English: Malcolm Hunter <email>malcolm.hunter@gmx.co.uk</email></para> 

</sect3>

</sect2>
