On Mon, Aug 13, 2012 at 1:09 AM, Charles Parnot <[email protected]>wrote:
> - I would tend to agree with Bruce that we don't need to tie the terms to
> a specific version of CSL; we update the locales at every update, and if a
> user wants to develop a new style with a just added term, well, they'll
> just have to wait a bit before it works in Papers; I think the gained
> flexibility is well worth the annoyance of getting client up to speed;
> locales would also probably the easiest ones to grab from the repository in
> a more automated fashion by the app
>
There are very few cases where new terms are introduced by themselves,
though. In most cases they are accompanied by new variables, or new logic
in the CSL processor. If the goal is to make CSL development more agile,
then there are other ways to do that.
Also, it's clear that most changes to CSL don't receive very close scrutiny
from all parties involved at the time they are developed (which I can
understand, as following everything takes quite a bit of time). But because
of that, capturing all changes to CSL into versioned releases, and creating
review periods (like the one we're in right now for 1.0.1) gives me some
peace of mind, as it provides short time frames where I ask people for
their attention.
Rintze
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
