Frank Bennett <[email protected]> writes: > On Mon, Feb 20, 2012 at 11:36 PM, Bruce D'Arcus <[email protected]> wrote: >> On Mon, Feb 20, 2012 at 6:20 PM, Ian Mulvany <[email protected]> >> wrote: >> >>> Are there any tools that inspect an outputted CSL formatted citation, >>> and show which parts of the CSL code was responsible for that bit of >>> formatting, kind of like being able to inspect an element in a web >>> browser? >>> >>> I'm assuming not, but I wanted to check. >> >> I'm not sure, but think that ... >> >> 1) Simon's is related: >> >> <https://github.com/simonster/csl-inference> >> >> 2) Sylvester may have mentioned his code could extended fairly easily >> to do this (?): >> >> <https://github.com/inukshuk/anystyle-parser> >> >> Bruce > > Sorry for being slow to respond. citeproc-js can't do this currently. > I've thought about it, but it seems it would be difficult to implement > into citeproc-js. Other implementations may be more well positioned > for it.
In citeproc-hs implementing something like this should be easy but tedious -- well, it depends on how you would do it. Even now it is possible to generate an intermediate representation of a formatted citation from which it is not difficult to infer the part of CSL that produced it. Something like this is among my long term plans for a major rewrite of the processor I have in mind, but it has a very low priority in my to-do list for the time being. Andrea ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
