We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.

Bug 3687 - XML: Extend the xmlGalleys plugin to include support for DocBook, TEI, and Erudit
XML: Extend the xmlGalleys plugin to include support for DocBook, TEI, and Er...
Product: OJS
Classification: Unclassified
Component: Plug-ins
PC Mac OS X 10.0
: P1 normal
Assigned To: jerico
Depends on:
  Show dependency treegraph
Reported: 2008-07-15 22:06 PDT by James MacGregor
Modified: 2013-05-29 15:18 PDT (History)
3 users (show)

See Also:
Version Reported In:
Also Affects:


Note You need to log in before you can comment on or make changes to this bug.
Description James MacGregor 2008-07-15 22:06:44 PDT
The current xmlGalleys plugin has built-in support for the NLM XML schema. It also allows for standalone XSL stylesheets to be uploaded and used instead of the included NLM XSL. However, it is hard to support whole XSL libraries, such as DocBook, where more than one XSL will normally come into play. 


After some discussion MJ and I have pinpointed TEI, DocBook, and Erudit as the primary schemas we should look to support, in addition to NLM. This will involve packaging relevant XSL stylesheets similarly to how NLM is currently packaged (after checking on licensing terms, of course); we will also have to identify a best-practices path for upgrading our packaged XSL when new stylesheets are released (thankfully, not very often), and possibly provide a method by which users can easily add their own XSL libraries or upgrade the ones we include. 


Users should be able to choose from one or more stock/default stylesheets for each schema (for example, specify that they want single HTML and/or PDF generated from TEI XML). Users should also be able to upload their own customization layers to draw from the installed libraries (this should already be supported by using the current upload function). 


Development will focus on building in XHTML and basic PDF support first where currently available, with an eye to more fully supporting more robust PDF generation down the road.
Comment 1 Ruth Knechtel 2008-07-16 08:10:28 PDT
Comment 2 James MacGregor 2009-07-06 12:45:54 PDT
Deferred from 2.3.
Comment 3 jerico 2009-10-07 19:15:48 PDT
Will not immediately implement, just assigned to me so the bug appears on my todo list. If anybody wants to step in please tell me.