Differences

This shows you the differences between two versions of the page.

--- g2:choosing_next [2008/08/15 11:54] – fgm
+++ g2:choosing_next [2023/05/27 15:24] (current) – fgm
@@ Line 1: / Line 1: @@
 ====== Warning ======
-This is a work-in-progress page for NancyDru and fgm to update http://drupal.org/node/266511 and will be updated there once finished. In the meantime, please refere to http://drupal.org/node/266511 instead.
+This is a 2008 work-in-progress page for NancyDru, fgm and eafarris, to update http://drupal.org/node/266511 but never completed at the time. In 2011, update [[g2/choosing|Choosing a glossary module]] instead.
 ====== Features checklist ======
@@ Line 15: / Line 15: @@
 <table border="1">
   <col align="left" span="2" />
-  <col align="center" span="4" />
+  <col align="center" span="6" />
   <tr>
     <th colspan="2">Feature</th>
     <th colspan="2"><a href="http://drupal.org/project/glossary">Glossary</a></th>
     <th colspan="2"><a href="http://drupal.org/project/g2">G2</a></th>
+    <th colspan="2"><a href="http://drupal.org/project/glossify">Glossify</a></th>
     </tr>
   <tr>
-    <th colspan="6"><h4>Drupal-related</h4></th>
+    <th colspan="8"><h4>Drupal-related</h4></th>
     </tr>
   <tr>
@@ Line 28: / Line 29: @@
     <td>Storage</td>
     <td colspan="2">Terms</td>
+    <td colspan="2">Nodes</td>
     <td colspan="2">Nodes</td>
     </tr>
@@ Line 34: / Line 36: @@
     <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>Drupal core</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>Drupal core</td>
@@ Line 43: / Line 47: @@
     <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>port announced</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>&nbsp;</td>
     </tr>
   <tr>
@@ Line 50: / Line 56: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>Dev</td>
+    <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>Release</td>
     </tr>
   <tr>
@@ Line 57: / Line 65: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" />
     <td>Dev</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>&nbsp;</td>
     </tr>
   <tr>
@@ Line 64: / Line 74: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>Release</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>&nbsp;</td>
     </tr>
   <tr>
@@ Line 69: / Line 81: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>Dev</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>&nbsp;</td>
     <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
@@ Line 76: / Line 90: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>CVS</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>&nbsp;</td>
     <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
@@ Line 83: / Line 99: @@
     <td colspan="2"><a href="http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/glossary/README.txt?view=markup">README.txt</a></td>
     <td colspan="2"><a href="http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/g2/README.txt?view=markup">README.txt</a></td>
+    <td colspan="2"><a href="http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/glossify/README.TXT?view=markup&pathrev=DRUPAL-6--1">README.TXT</a></td>
     </tr>
-  <tr>
+  <tr><!-- Additional documentation -->
     <td colspan="2"><a href="http://drupal.org/node/196880">Handbook</a></td>
     <td colspan="2"><a href="http://wiki.audean.com/g2/start">Wiki</a><br />
+    <td colspan="2">&nbsp;</td>
     </tr>
   <tr>
@@ Line 94: / Line 112: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>Entry selectors</td>
+    <td colspan="2"><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     </tr>
   <tr>
-    <th colspan="6"><h4>Services provided</h4></th>
+    <th colspan="8"><h4>Services provided</h4></th>
     </tr>
   <tr>
     <td colspan="2">Glossaries per site</td>
     <td colspan="2">Multiple</td>
+    <td colspan="2">Single</td>
     <td colspan="2">Single</td>
     </tr>
@@ Line 110: / Line 130: @@
     <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>Drupal core</td>
     </tr>
   <tr>
@@ Line 115: / Line 137: @@
     <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>Drupal core</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>Drupal core</td>
@@ Line 122: / Line 146: @@
     <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>Entries <em>are</em> terms already</td>
+    <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>Drupal core</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>Drupal core</td>
@@ Line 129: / Line 155: @@
     <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>Drupal core</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>Drupal core</td>
@@ Line 138: / Line 166: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>CCK</td>
     </tr>
   <tr>
@@ Line 146: / Line 176: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>Views</td>
     </tr>
   <tr>
@@ Line 153: / Line 185: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>Views</td>
     </tr>
   <tr>
@@ Line 160: / Line 194: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>Views</td>
     </tr>
   <tr>
@@ Line 167: / Line 203: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>Views</td>
     </tr>
   <tr>
     <td>Search glossary</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
     <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
@@ Line 181: / Line 221: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>Views</td>
     </tr>
   <tr>
@@ Line 188: / Line 230: @@
     <td>&nbsp;</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
     </tr>
@@ Line 195: / Line 239: @@
     <td>&nbsp;</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
     </tr>
@@ Line 202: / Line 248: @@
     <td>&nbsp;</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
     </tr>
@@ Line 209: / Line 257: @@
     <td>&nbsp;</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
     </tr>
@@ Line 216: / Line 266: @@
     <td>&nbsp;</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
     </tr>
   <tr>
-    <td colspan="6">Security</td>
+    <th colspan="8"><h4>Security</h4></th>
     </tr>
   <tr>
     <td colspan="2">Drupal core</td>
+    <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>&nbsp;</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>&nbsp;</td>
@@ Line 234: / Line 288: @@
     <td>&nbsp;</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
     </tr>
@@ Line 241: / Line 297: @@
     <td>&nbsp;</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
     </tr>
@@ Line 247: / Line 305: @@
     <td colspan="2">Automatic</td>
     <td colspan="2">Manual</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>&nbsp;</td>
     </tr>
   <tr>
@@ Line 252: / Line 312: @@
     <td colspan="2">Automatic</td>
     <td colspan="2">&lt;dfn&gt; elements</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>&nbsp;</td>
     </tr>
   <tr>
-    <th colspan="6">Performance</th>
+    <th colspan="8"><h4>Performance</h4></th>
     </tr>
   <tr>
@@ Line 260: / Line 322: @@
     <td colspan="2">O(n)</td>
     <td colspan="2">O(1)</td>
+    <td colspan="2">O(n)</td>
     </tr>
   <tr>
     <td colspan="2">Speed on small glossaries</td>
     <td colspan="2">Faster</td>
+    <td colspan="2">Slower</td>
     <td colspan="2">Slower</td>
     </tr>
@@ Line 270: / Line 334: @@
     <td colspan="2">Slower with size</td>
     <td colspan="2">Remains constant</td>
+    <td colspan="2">Slower with size</td>
     </tr>
   <tr>
@@ Line 276: / Line 341: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>Drupal core</td>
     <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>Drupal core</td>
@@ Line 282: / Line 349: @@
     <td>Node overview</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
     <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
@@ Line 292: / Line 361: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>Drupal core</td>
     </tr>
   <tr>
@@ Line 298: / Line 369: @@
     <td>&nbsp;</td>
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
+    <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
     <td>&nbsp;</td>
     </tr>
@@ Line 306: / Line 379: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>&nbsp;</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>Drupal core</td>
     </tr>
   <tr>
@@ Line 313: / Line 388: @@
     <td><img src="http://drupal.org/misc/watchdog-ok.png" alt="Yes" /></td>
     <td>Except D5 branch</td>
+    <td><img src="http://drupal.org/misc/watchdog-error.png" alt="No" /></td>
+    <td>&nbsp;</td>
     </tr>
   </table>
@@ Line 325: / Line 402: @@
 <table border="1">
   <col align="left" width="10%" />
-  <col align="left" span="2" width="45%" />
+  <col align="left" span="3" width="30%" />
   <tr>
     <th>Criteria</th>
     <th>Glossary</th>
     <th>G2 Glossary</th>
+    <th>Glossify</th>
     </tr>
   <tr>
@@ Line 346: / Line 424: @@
       <p>This allows access control, attachment uploads, commenting, content tagging, revision control, and integration will the vast number of node-related modules.</p>
       <p>Extensibility is directly available from core for G2 content through the extensive core hook system for nodes. Control is available at the individual field level, and includes editor-only information, which is required in publishing situations.</p>
+      </td>
+    <td>
+      <p>Glossify uses Node to store its terms.</p>
+      <p>This allows the wide range of contributed modules to add functionality to terms: Adding fields via <a href="http://drupal.org/project/cck">CCK</a>, defining views with <a href="http://drupal.org/project/views">Views</a>, access control, image handling, tagging via taxonomy, etc.</p>
+      <p>Extensibility is directly available from Drupal core for all glossify entries. Everything that can happen to a node in Drupal can happen to a glossify entry.</p>
       </td>
   <tr>
@@ Line 356: / Line 439: @@
       <p>G2 is optimized for large glossaries, not small ones. As such, its requirements do not increase with the number of entries.</p>
       <p>At the time of its creation (4.7), supporting a 5000 terms dictionary with glossary.module on a shared hosting plan, was causing severe load issues.</p>
+      </td>
+    <td>
+      <p>Glossify is not optimized for speed. In fact, for large sites, it's probably a bad idea.</p>
       </td>
     </tr>
@@ Line 362: / Line 448: @@
     <td>The ability to handle multiple vocabularies as glossaries gives Glossary additional flexibility</td>
     <td>G2 is designed around a single glossary by site: multiple glossaries were not necessary to the initial sponsor. More generally, sites maintaining a large glossary are typically centered around it, and won't maintain more than one per site.</td>
-    </tr>
+    <td>
+      <p>While glossify is designed around a single vocabulary (content type), it does allow multiple content types to hold its entries.</p>
+      </td>
+  </tr>
   <tr>
     <td>Community</td>
     <td>Glossary has largely been designed by its users. Many, if not most, of its features have been added and refined by the input of the community.</td>
     <td>G2 has been developed for the specific need of one user and shared afterwards. Its original feature set was designed around that need, and has only been expanded and modified by community input afterwards.</td>
+    <td>
+      <p>Glossify was designed for a sole purpose by a sole author, and shared afterwards. Expansion and modification of this module will happen via the Drupal community.</p>
+      </td>
     </tr>
   <tr>
@@ Line 376: / Line 468: @@
       There have been performance efforts to make sure it runs fast even with large glossaries.
       Community support is available, and commercial-level support is available from its maintainer.</td>
+    <td>
+      <p>Glossify is feature complete for its original intention and installation. Modifications to the module are outside of its original scope, but welcomed by the maintainer.</p>
+      </td>
     </tr>
   <tr>
@@ Line 381: / Line 476: @@
     <td>Automatic maintenance reduces the need for administrator intervention.</td>
     <td>Any large glossary will use all available initials from the onset, so administrator intervention is not needed past the initial module configuration, and the processing cost of maintaining it afterwards is useless system load.</td>
+    <td>
+      <p>Glossify does not provide an alphabar.</p>
+      </td>
     </tr>
   <tr>
@@ Line 392: / Line 490: @@
       <p>A translation template is provided except for Drupal 5.</p>
       <p>The base URL for the glossary pages is admin-defined, thus allowing for translation and module masking.</p>
+      </td>
+    <td>
+      <p>As glossify entries are simply nodes, glossify relies on Drupal core for i18n and translation services.</p>
       </td>
     </tr>
@@ Line 402: / Line 503: @@
       <p>The G2 filter only applies its matching patterns to &lt;dfn&gt; elements in the input.</p>
       <p>The terms are wrapped in a valid XHTML link with a title attribute, bearing a G2-specific class to enable pure CSS themeing</p>
+      </td>
+    <td>
+      <p>Glossify currently supports three types of presentation of terms:</p>
+      <ul>
+        <li>Terms are linked to their entries when used in content.
+        <li>Terms and entries can be shown as hovertips (requires the <a href="http://drupal.org/project/hovertip">hovertip module</a>).
+        <li>Terms and entries can be shown in a "Reference" section under the node body. This section is exposed to Drupal themeing.
+      </ul>
+      <p>The entries themselves are fully exposed as nodes to the Drupal theme system, and lists can be made via the <a href="http://drupal.org/project/views">views module</a>.</p>
       </td>
     </tr>
@@ Line 408: / Line 518: @@
     <td>Terms link to the entire glossary or the individual term, depending on which option the administrator chose.</td>
     <td>Terms link to the G2 page for the term, which may be either a disambiguation page or the single destination page, depending on whether homonyms exist or not and whether administrators enable the direct link on single matches.</p>
+    <td>
+      <p>Terms are linked to the individual term.</p>
+      </td>
   <tr>
     <td>Glossary display</td>
@@ Line 414: / Line 527: @@
        <p>In addition to the individual term pages, G2 includes initial pages, customizable disambiguation (homonyms) pages and a customizable main page.</p>
       <p>The main page, may be either a node reference for simplicity or a function name, for easier maintenance in the site module. When not customized, it displays an alphabar on top, identical to the one in the alphabar feature block.</p>
+      </td>
+    <td>
+      <p>Glossify does not supply a display for the entire glossary. Site administrators and designers can use the <a href="http://drupal.org/project/views">views module</a> to create such a display. </p>
       </td>
     </tr>
   </table>
 </html>
@@ Line 424: / Line 539: @@
 <h3><a name="common-glossary-features">Common features</a></h3>
-<p>Both modules work as a Drupal input filter applying to content depending on its input format. These filters are cacheable for performance reasons.
+<p>Glossary and G2 modules work as a Drupal input filter applying to content depending on its input format. These filters are cacheable for performance reasons. Glossify does not provide an input filter. Rather, glossify marks up content on output.
-<p>Since the modules filter content, the first time a piece of content is shown, there will be a small delay while the filtering is done. The filtered content is then cached, so the next time, the filtering is unnecessary and the delay does not occur.</p>
+<p>Since the glossary and G2 filter content, the first time a piece of content is shown, there will be a small delay while the filtering is done. The filtered content is then cached, so the next time, the filtering is unnecessary and the delay does not occur. Glossify does not filter, so there is no delay when the content is submitted. Glossify's delay is incurred when content is viewed.</p>
 </html>
@@ Line 448: / Line 563: @@
       </ul>
     </li>
+  <li>Single glossary: multiple glossaries were not necessary to OSInet, which funded development</li>
+  <li>Optimization for large glossaries: this is the need expressed by OSInet, which funded development, to support its 5000+ term glossary of computing, for which glossary.module, even when coupled with flexinode or early CCK to bind blob content to terms, was not really efficient enough</li>
+  <li>Using custom node type (g2_entry in g2.module) allows large definitions, with the complete drupal feature set for nodes. At the time of Drupal 4.7, neither flexinode not CCK were a reasonable choice for a generic module</li>
+  <li>Manual alphabar maintenance: large glossaries will most of the time use all available initials, so the processing cost of maintaining it is not justifiable</li>
   </ul>
 </html>
 ====== Glossary advocacy ======
@@ Line 483: / Line 600: @@
 <p>Within the glossary display, each term may be followed by a link that will initiate a search for the term, if the search module is enabled. For those who have the proper permission, there will also be a link to edit the term itself.</p>
 <p>The type of glossary indicator that is used is specified for each input format, so, for example, "Filtered HTML" may use a superscript type of indicator, while "Full HTML" may use a hovertip. Additionally, each input format also selects which vocabularies are to be used. So one may, again for example, specify that "Filtered HTML" filter for Bible verses, while "Full HTML" filters for technical terms.</p>
+<p>Using terms (glossary.module) allows definitions to be bound to custom nodes instead of being nodes on their own</p>
 </html>
+====== Glossify advocacy ======
+<html>
+<h3><a name="glossify-advocacy">Glossify advocacy</a></h3>
+<p>Glossify aims at simplicity. Its code is small, its options are few, and its job is straightforward. Glossify looks at content before it is output, finding and marking up any content that is a title of another piece of content, and links the title to the entry. It does not provide an input filter, nor does it generate a landing page of entries.</p>
+<p>Since glossify uses nodes as its entries, the vast customization that Drupal core and contrib offers to nodes are available to glossify entries. They are not limited to entry and definition pairs, but can include other fields via the Content Construction Kit. Lists and blocks can be created with Views. Entries can be classified with taxonomy; they can be themed with PHPtemplate or other theming options.</p>
+<p>Glossify has options to limit the content types used for entries and the content types it will look through, and has three different display options for showing what terms have been referenced in the content:</p>
+<ul>
+<li>The title can simply be linked to the entry. This is wiki-like. The link includes a class for styling via CSS.
+<li>The entry can be shown via a hovertip, if the appropriate module is available. These can be themed via Drupal's theming mechanism.
+<li>A "referenced terms" area can appear underneath the main content. This section is available for theming via Drupal's theming mechanism.
+</ul>
+</html>