On Thu, Oct 11, 2012 at 6:25 AM, Carles Pina <[email protected]> wrote: > Some of the tasks were simple changes in CSL styles (other tasks were > search a CSL style, etc.): > "23. Edit the style for the Journal of Community Health to put the > inline citation between parentheses: ( ) instead of square brackets: [ > ].", " > "24. Replace the comma between the inline citation numbers with an > ampersand: &." > "25. Make the inline citation bold." > "26. Give the Author names in the bibliography small-caps formatting."
Do any of these cases require use of the XML tree? I'm wondering if it wouldn't be clearer to hide it by default, since you're mostly focusing on facilitating minor edits. >> do I make a date localize?"), and then focus on the CSL XML needed to >> meet that goal. I like the idea, but it would be a significant >> undertaking, probably matching or exceeding the specification in size. > > it also would require some extra-effort for users who never wrote XML, > they don't know what is an element/attribute, need to validate the > styles... Yes, but there will always be a class of power users that isn't afraid of hand-editing XML. Reducing the amount of time these users need to invest to get familiar with CSL seems worthwhile. I see it more as a parallel approach to the CSL editor, which is more aimed at casual users. > Documentation needs to be done, I agree. Where would we host it? The GitHub wiki? (https://github.com/citation-style-editor/csl-editor/wiki) Rintze ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
