I'll prepare the JSON file and open a pull request. Might be a day or two,
though.
Rintze
On Wednesday, October 16, 2013, Sebastian Karcher wrote:
> ah OK, great - I was confused by your wording in that last mail.
> We should update the specs before this goes life, too, to prevent
> confusion.
> @Rintze - do you want me to pack the list into a JSON file? Do you want to
> handle editing the specs?
>
>
> On Wed, Oct 16, 2013 at 10:00 AM, Frank Bennett <[email protected]>wrote:
>
> I linked it in the last mail -- it's the gist you posted earlier in
> the discussion.
>
> https://gist.github.com/adam3smith/6326169
>
> There's no JSON file as far as I know, but I wanted to refactor the
> title case code anyway, so I went ahead and used your draft list. The
> changes aren't yet live in Zotero or MLZ, it's just out for testing so
> far.
>
> Frank
>
>
>
> On Thu, Oct 17, 2013 at 12:33 AM, Sebastian Karcher
> <[email protected]> wrote:
> > where is the list you're using? We never created the JSON file, did we?
> >
> >
> > On Wed, Oct 16, 2013 at 9:29 AM, Frank Bennett <[email protected]>
> > wrote:
> >>
> >> I've set up citeproc-js to use the new list, and installed the new
> >> version in the Zotero CSL processor patch plugin. I've added a few
> >> terms that seemed to be missing, mentioned here:
> >>
> >> https://gist.github.com/adam3smith/6326169
> >>
> >> It would be great if anyone has time to try it out and see if there
> >> are any obvious problems. Here's the plugin:
> >>
> >> http://gsl-nagoya-u.net/http/pub/zotero-processor.xpi
> >>
> >> Frank
> >>
> >>
> >>
> >>
> >> On Thu, Oct 10, 2013 at 7:33 AM, Frank Bennett <[email protected]>
> >> wrote:
> >> > I'm fine with implementing the new list in citeproc-js. I'll wait
> >> > until the JSON file is ready, but it's not problem to set up.
> >> >
> >> > Frank
> >> >
> >> > On Tue, Aug 27, 2013 at 12:32 AM, Sebastian Karcher
> >> > <[email protected]> wrote:
> >> >> this is the list from Wikipedia (WP) narrowed down manually by me as
> >> >> described.
> >> >> If there are not objections against the list itself, yes, putting
> these
> >> >> in
> >> >> the documentation as JSON sounds good.
> >> >> Frank and other proc maintainers - any issues/wishes for implementing
> >> >> this?
> >> >>
> >> >>
> >> >> On Mon, Aug 26, 2013 at 9:29 AM, Rintze Zelle <
> [email protected]>
> >> >> wrote:
> >> >>>
> >> >>> What's "WP"? Should I go ahead and store these words in a JSON file
> in
> >> >>> the "documentation" repository, e.g. in a file "prepositions.json"?
> >> >>>
> >> >>> Rintze
> >> >>>
> >> >>> On Sat, Aug 24, 2013 at 1:09 AM, Sebastian Karcher
> >> >>> <[email protected]> wrote:
> >> >>> > ok, here's a suggested list of prepositions. Took the one and two
> >> >>> > word
> >> >>> > list
> >> >>> > from WP, removed anything that I could conceivably see being used
> in
> >> >>> > a
> >> >>> > non-preposition way. Didn't include three words and outdated
> >> >>> > prepositions
> >> >>> > (though some of these are already on the outdated side of things).
> >> >>> > https://gist.github.com/adam3smith/6326169
> >> >>> >
> >> >>> >
> >> >>> > On Fri, Aug 2, 2013 at 8:56 AM, Sebastian Karcher
> >> >>> > <
>
>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
