On Tue, Dec 20, 2011 at 2:53 AM, Charles Parnot <[email protected]>wrote:

> The fixtures follow the same format as the one on the repo. I have never
> in fact fixed a bug without creating a corresponding test, which I am very
> happy about.
>

Can these test fixtures already be contributed to Frank's test suite?

Note that in Papers 2.1, we introduced some Papers2-specific CSL variables
> to deal with some user requests. Inspired by CSS and vendor-specific
> extensions, I prefixed those variables with 'papers2_', and thus named
> those `papers2_pmid`, `papers2_pmcid` and `papers2_notes`. They are quite
> self-explanatory. Please let me know if you have any questions, or comments
> on that. We certainly don't want to 'fork' CSL or go crazy with new
> variables or other modifications of the CSL. On the contrary, we think a
> strong and consistent CSL implementation across multiple platforms and
> sofwtare packages is also in Mekentosj's best interest.
>

I'm a strong proponent for adding PMID and PMCID variables to CSL 1.0.1.


> At this stage, we thus have a good Objective C processor, with still a few
> holes, as well also a nice harness app to keep fixing bugs without breaking
> existing behavior, and with the ability to leverage present and future CSL
> fixtures. In the back of our mind, we have the idea of open-sourcing all
> that stuff maybe one day, but at the moment, it still has too many
> dependencies shared with the rest of Papers2. Also, it's not clear we can
> do a good job at managing an open-source project in an acceptable way for
> others (our poor records in communicating with the CSL devs so far is not a
> good indication!). Also, I am not even sure that it would be very useful to
> many people other than us. Let us know what you think.
>

There is interest for an Objective C citeproc:
https://groups.google.com/d/msg/zotero-dev/lAcACTgY5uQ/MrESI5i9aBUJ


> When we launched Papers 2.0, we shipped CSL 1.0 styles. At the time, I
> used the Zotero svn repository to pull the 0.8 styles, then used the XSLT
> file to translate the styles to 1.0. For a while, this is how the styles
> were updated as well with new versions of Papers 2.0.x. For Papers 2.1.10
> (soon in beta), I have updated the script to directly use the GitHub
> repository. Back then and still now, we apply a few more filters, to remove
> styles that have a non-commercial license (that's only a small number of
> them)


Do we still have (L)GPL styles? I really think we should get rid of that
type of license in the style repo.


> to adjust a few titles we thought were not correct or did not like (e.g.
> 'Nature Journal' becomes simply 'Nature')


Can you supply us with an overview of these adjustments? I might fix up a
few styles upstream if I agree with the changes.


> I also have a handful of styles contributed by some users, that I'd like
> to push to the main CSL repository. I'd be happy to have direct commit
> access, but then I also don't know what the process is to get commit
> access. Maybe getting commit access would be counterproductive for you, so
> I'm just as happy to submit them through the normal submission process (I
> have read the instructions, etc… so no worry, I don't need them, and I know
> it's not the right place to ask questions about this). Whatever minimizes
> the amount of work on your end. Same for the fixtures.
>

As I indicated in the other thread, just make sure that the style you
commit are valid CSL 1.0. If you start with a few, Sebastian and I will
review them and let you know if there's anything we would like to see
different.

Thanks for the update, Charles, it's much appreciated.

Rintze
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel

Reply via email to