Differences

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

--- g2:choosing [2011/01/12 13:39] – [Choosing a glossary-type module] fgm
+++ g2:choosing [2011/01/22 22:08] – G2 D7 now available fgm
@@ Line 3: / Line 3: @@
 ====== Choosing a glossary-type module ======
-G2 is not intended as a direct replacement for the glossary module already available with drupal for quite some time now. It was designed for slightly different needs, and this page is here to help you choose which module you should probably be using, or if you should really write your own. Lexicon has been evolved from glossary to accomodate yet another set of requirements, and glossify started with needs similar to glossary, but evolved to a much more diverse set of features; only those relevant to glossaries should be listed here.
+None of the glossary modules is intended as a plug-in replacement for the original glossary module already available with drupal since its humble beginnings. Each of the alternatives was designed for slightly different needs, and this page is here to help you choose which module you should probably be using, or if you should really write your own. Lexicon evolved from glossary to accomodate yet another set of requirements, and glossify started with needs similar to glossary, but evolved to a much more diverse set of features; only those relevant to glossaries should be listed here.
 Left-to-right order by date of creation. Empty cells means info not yet available. Please contribute !
@@ Line 11: / Line 11: @@
 ^ Feature                           ^  Glossary          ^  G2                          ^  Glossify   ^ Lexicon ^  Refactoring          ^
 ^ Drupal-related                    ^                    ^                              ^             ^         ^                       ^
-| Drupal 7.x                        |  No                |  No(t yet)                   |  No(t yet)  |  Yes    |  Yes                  |
+| Drupal 7.x                        |  No                |  Yes                         |  No(t yet)  |  Yes    |  Yes                  |
 | Drupal 6.x                        |  Yes               |  Yes                         |  Yes        |  Yes    |  No                   |
 | Drupal 5.x                        |  Yes               |  Yes                         |  Yes        |  No     |  No                   |
@@ Line 30: / Line 30: @@
 | alphabar maintenance              |  automatic         |  manual                      |             |         |  defaults + override  |
 | remote glossaries                 |  No                |  Yes, limited                |             |         |  Yes                  |
+| steganographic content protection |                    |  No                          |             |         |  Yes                  |
+| RDF information                   |                    |  No                       |   |   |  [[http://drupal.org/node/1029544|Yes]]  |
 ^ i18n                              ^                    ^                              ^             ^         ^                       ^
 | Translation template supplied     |  Yes               |  Yes                         |             |         |                       |
 | Multilingual blocks               |                    |  No                          |             |         |                       |
+| Translatable content              |  Use i18nterms     |  Use i18ncontent             |  Use i18ncontent  |   |                       |
 ^ Feature blocks                    ^                    ^                              ^             ^         ^                       ^
 | Alphabar                          |  No                |  Yes                         |  Use Views  |         |  Default View         |
@@ Line 40: / Line 43: @@
 | Search glossary                   |  Yes               |  No                          |  No         |         |  Yes                  |
 ^ Content filtering                 ^                    ^                              ^             ^         ^                       ^
-| automatic                         |  Yes               |  No                          |             |         |  Yes                  |
+| Input, automatic                  |  Yes               |  No                          |  No         |         |  Yes                  |
-| automatic, stop list              |  Single language   |  No                          |             |         |  i18n support         |
+| Input, automatic, stop list       |  Single language   |  No                          |  No         |         |  i18n support         |
-| explicit                          |  No                |  Yes, dfn element            |             |         |  Yes, custom element  |
+| Input, explicit                   |  No                |  Yes, dfn element            |  No         |         |  Yes, custom element  |
+| Output, automatic                 |  No                |  No                          |  Yes        |         |                       |
 | auto "title" on links             |  No                |  No                          |             |         |  Teaser / Disambiguation        |
 | Disambiguation pages              |  n.a.              |  Yes, limited                |             |         |  default + override   |
@@ Line 73: / Line 77: @@
 ", as in all Open Source software.
-===== Documentation =====
+====== Documentation ======
   * Glossary
@@ Line 84: / Line 88: @@
     * [[http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/glossify/README.TXT?view=markup&pathrev=DRUPAL-6--1|README]]
-===== Drupal 4.x to 6: Rationale for G2 specificities  =====
-  * 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 to bind blob content to terms, is not really efficient enough.
-  * Single glossary: multiple glossaries were not necessary to OSInet, which funded development
-  * Explicit linking to terms with dfn elements:
-    * limits system workload
-    * allows invisible marking of entries made of other entries. Think: XML-RPC, points to XML and to RPC with glossary.module and various wiki filters, but can point to 'XML-RPC' with G2. Wrapping XML-RPC in quotes is necessary to allow linking to this entry in glossary, but the quotes remain visible, degrading the UI.
-    * allows redactor-level choice of
-      * whether to link to an entry: glossary always links if the term matches, which is not always meaningful ("and" can be present in a glossary and you don't want "and" to be linked from in all nodes on the site).
-      * where to link to an entry: glossary allows only a predefined set of positions (first, last or all matches)
-  * nodes vs terms: this is the most salient difference.
-    * Using custom nodes (g2_entry in g2.module) allows large definitions, with the complete drupal feature set for nodes,
-    * Using terms (glossary.module) allows definitions to be bound to custom nodes instead of being nodes on their own
-  * Alphabar maintenance: large glossaries will most of the time use all available initials, so the processing cost of maintaining it is not justifiable