On Sun, Jul 24, 2011 at 12:53 AM, Bruce D'Arcus <[email protected]> wrote: > On Sat, Jul 23, 2011 at 6:02 PM, Frank Bennett <[email protected]> wrote: >> On Sat, Jul 23, 2011 at 8:33 PM, Bruce D'Arcus <[email protected]> wrote: >>> So we've periodically talked about two things: >>> >>> 1) a higher-level style editing/creation wizard, with one variant relying on >>> modifying formatted output to get the appropriate CSL >>> >>> 2) using existing style data to help us do this >>> >>> Do we have any actual data that would give us a concrete sense of how >>> flexible a UI would need to be? >> >> There's this: https://bitbucket.org/fbennett/csl-lib/overview >> >> I haven't touched it in the past year, but the scripts should still >> work. The data dumps are idiosyncratic, but if someone wanted to clean >> it up, the logic is there. > > Cool; thanks. > >>> I just had in my mind's eye a UI that is a formatted bib, but where one >>> could interact with the variable tokens. Just wondering if we have any >>> evidence whether that's feasible. >>> >>> Bruce >> >> I've spoken with Steve Rideout (IIRC) about the possibility of tagging >> output with links or hints that lead back to the portion(s) of CSL >> from which it is derived, to allow this kind of reverse-direction >> editing. It's a very tough problem due to the complexity of >> inheritance and cross-node interaction in much of the formatting >> logic. It's a tempting concept, but there would be a risk of finding >> in the end that it wouldn't work well enough to be useful. I don't >> expect to do anything on it in the foreseeable future myself. > > What I'm contemplating here is actually simpler, and is a riff on my > earlier ideas about a makebst-like wizard interface. So rather than > there be some direct mapping of CSL to HTML, there'd just be just be > tokens that were tied to a pre-selected list of macro options, where > one would just click the token to get the list, click on what looked > right, etc. > > But come to think of it, this may not be any better than my original > idea; not sure. > > Bruce
That was what I had in mind with csl-lib as well. The hard part (or at least the part that no one has tried to do yet) would be to work out a typology of style structures (since not every style breaks things down in the same way). With that in hand, you should be able to build a style by chosing a structure, and then selecting from a subset of macros for each slot in the structure. Working out the typology would require back-and-forth between analyzing styles to identify top-level patterns, and then looking at the styles to see if the number of top-level patterns can be reduced. Some styles would have to be left out, as "bespoke CSL", but many of the author-date and numeric styles, in particular, might be amenable. > > ------------------------------------------------------------------------------ > Magic Quadrant for Content-Aware Data Loss Prevention > Research study explores the data loss prevention market. Includes in-depth > analysis on the changes within the DLP market, and the criteria used to > evaluate the strengths and weaknesses of these DLP solutions. > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > _______________________________________________ > xbiblio-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel > ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
