> while a CSS modification would likely be much less verbose, doing it > in XSL has the advantage that you should be able to upgrade it > painlessly most of the time. That's because you'll copy the original > template into your theme and modify it, which is called template > overriding (conceptually similar to method overloading). The one in > your theme will have priority, thus overriding the original one. It > will continue to work after an ugprade even if there are changes to > the original theme, unless there's a change in that specific template > you've overriden, in which case you'd upgrade it as usual (diff).
OTOH, from an archival point of view, splitting a chunk of running text into paragraphs so you can reassemble them nicely later is an accident waiting to happen. CSS (re-)customisation is (I would guess) the lightest-weight of all (re-)customisations in web applications, certainly CSS skills are more common than XSLT skills. > The CSS looks a lot simpler, but I don't know which CSS or > /conf/ file to stick it in. I put all my tiny customisations at the end of the style.css for the theme I'm using. cheers stuart -- Stuart Yeates Library Technology Services http://www.victoria.ac.nz/library/ ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________ Dspace-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-general
