GithubHelp home page GithubHelp logo

citation-style-language / styles Goto Github PK

View Code? Open in Web Editor NEW
3.2K 85.0 3.7K 66.75 MB

Official repository for Citation Style Language (CSL) citation styles.

Home Page: https://citationstyles.org/

Ruby 100.00%
citation-style-language bibliography citations citation-styles csl hacktoberfest

styles's Introduction

CSL logo

Citation Style Language - Style Repository

License Build Status

Introduction

The independent open source Citation Style Language (CSL) project aims to facilitate scholarly communication by automating the formatting of citations and bibliographies. The primary components of the CSL ecosystem are:

  • The CSL schema and specification, which describe how the XML-based CSL styles and locale files should be written and interpreted
  • Curated repositories of CSL styles and locale files
  • Third party CSL processors, software libraries for rendering formatted citation and bibliographies from CSL styles, CSL locale files, and item metadata

This README describes our official curated repository of CSL styles, hosted at https://github.com/citation-style-language/styles/. CSL locale files, which provide default localization data for CSL styles (such as translations and date formats), can be found at https://github.com/citation-style-language/locales.

For more information about CSL and CSL styles, check out https://citationstyles.org/ and the information files in this repository (Style Requirements, Style Development, Requesting Styles, Contributing Styles, and Quality Control).

Criteria for inclusion

The official CSL style repository is the only repository of its kind, is used by dozens of third-party software products, and is relied upon by hundreds of thousands of users. The popularity of this repository is in large part due to its crowd-sourced nature, and, we believe, also due to our careful curation. While we evaluate style submissions on a case-by-case basis, we generally use the following criteria for inclusion in the CSL style repository:

  • Styles must be of sufficient quality and meet our style requirements. While we may be able to assist with this, its ultimately the submitter's responsibility to provide a style that meets our standards.
  • Styles should be based on an official style guide (and link to the style guide in online or printed form).
  • Styles should be of interest to a wider audience. We are happy to accept styles with a niche audience, but as a rule of thumb, style submitters should not know all individuals who would be interested in their style. If you do, it's generally better to distribute your style to them yourself.

Based on these criteria, we generally accept:

  • styles for journals with open (unsolicited) submissions (and styles for publishers of such journals).
  • styles for published style guides, such as those from professional organizations, universities, and university departments.

However, we typically won't accept:

  • styles for personal use, or for internal use within small organizations.
  • styles solely for use with an (internal) API.

If in doubt whether your style is a good fit for the repository, feel free to open an issue or pull request and ask for our opinion. If we don't accept your submission, we encourage you to distribute your CSL style yourself.

Versioning and style distribution

We currently only actively maintain CSL styles in the "master" branch for the latest released version of CSL.

In addition, in order to provide a stable location for styles of a given CSL version, styles in "master" are automatically copied to a branch named after the latest version of CSL (e.g. "v1.0.2" when CSL 1.0.2 is the latest version). Once a new version of CSL is released (e.g. CSL 1.1.0), "master" will upgrade to that version, after which styles will be copied from "master" to a new version branch ("v1.1.0"). Version branches for old versions of CSL are kept but typically become dormant, as for these branches we generally stop maintenance, won't accept third-party contributions via pull requests, nor backport changes made to styles in "master".

Starting with branch "v1.0.1", the version branches differ from "master" in the following ways:

  • the latest version branch only receives updates from "master" if all tests in "master" pass
  • <updated/> timestamps of styles in the version branch are changed to match the git modification date of each individual style in "master"
  • superfluous files present in "master", e.g. for style testing, are removed.

As such, especially for downstream integrators, you are encouraged to obtain your CSL styles from the appropriate version branch (e.g. "v1.0.2" for CSL 1.0.2 styles). Currently, the styles repository includes the following (protected) branches:

  • "master"
  • "v1.0.2" (for CSL 1.0.2 styles)
  • "v1.0.1" (for CSL 1.0.1 styles)
  • "v1.0" (for CSL 1.0 styles)

The release regimen described here is also used for our CSL locales.

As of November 2020, https://github.com/citation-style-language/styles-distribution, which fulfilled a similar role to the version branches, has been deprecated and no longer receives updates from https://github.com/citation-style-language/styles.

Licensing

All styles in this repository are released under the Creative Commons Attribution-ShareAlike 3.0 Unported license. For attribution, any software using CSL styles from this repository must include a clear mention of the CSL project and a link to https://citationstyles.org/. When redistributing styles, the listings of authors and contributors in the style metadata must be kept as is.

styles's People

Contributors

adam3smith avatar adunning avatar aurimasv avatar bwiernik avatar cparnot avatar cpina avatar danycoolqc avatar dependabot[bot] avatar eu-genia avatar f-mb avatar fbennett avatar fshigashikawa avatar ganapathir001 avatar georgd avatar inukshuk avatar libora avatar mtarakci avatar natch-nacht avatar nicolassouchon avatar nmonteix avatar pobrien333 avatar retorquere avatar rmzelle avatar roaldfrosig avatar sankar-geo-els avatar serpodrick avatar tipichris avatar tungphamfsh avatar xavi-mat avatar zuphilip avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

styles's Issues

MLA style needs some love

I have some concerns about locator handling in this style, as well as the 'medium' macro. I suspect there may be other issues as well, that mean the style could benefit from a cleanup.

settle on conventions for versioning

We need to figure out our plan going forward for version-management vis-a-vis schema changes. Possible options:

  1. ids are stable across versions, and so versioning happens with git branching
  2. ids are tied to versions, and so versioning happens via structure of directories in repositories; e.g. http://citationstyles.org/styles/1.1/apa.csl.

journal of clinical investigation

Hi,
i was experimenting with csl and edited a style for the journal of clinical investigation

git://gist.github.com/1647561.git

appreciate any comment/suggestion and hope i'm following the right path to add it to the repository

Something needs to happen wrt repository

So we've been in repository-limbo for several months now and it's getting increasingly difficult to maneuver on the ground.
Some issues:

  1. At least Zotero auto-updates it's default styles from the repository - that means that, e.g., the improved APA gets overwritten every 24hs even if you install it manually
  2. It's a hassle in general to deal with two parallel repos
  3. (Perhaps most importantly) As far as the repos diverge, things become really messy - every time someone commits or proposes a fix to a 0.8.1 style I need to check if the style has been otherwise changed to adopt some additional 1.0 features - if that's the case I (or Rintze or Frank) need to manually update the parallel 1.0 style

I know people are busy and no one is doing this full time, but this is becoming untenable for me as one of the people dealing with the large share of style updates and commits.
Maybe we should just ask Zotero to update the entire repository to 1.0 and keep style development there until a repo on citationstyles.org is ready? Maybe there is another solution? But I really do not want to keep working with the status quo for another 6+months....

settle on new base uri for styles, update ids accordingly

Right now, styles have a base uri of http://zotero.org/styles. We need to change that to a more generic like http://citationstyles.org/styles/.

A separate question is whether we want to serve files directly from github, either using the github base uri, or some sort of indirection (cnames, or whatever).

Request removal of Bluebook 19th ed.

As I have been warned off of attempting a full implementation of the Bluebook style by its editors, I will be suspending development for the present. The current version of the style is incomplete, and likely to cause inconvenience to unsuspecting users whom I am unable to assist. This has already happened, unfortunately:

http://forums.zotero.org/discussion/19675/bluebook-bbperiodicalsubsequent/

Accordingly, and with regret, I would like to ask that the Bluebook 19th ed. style be removed from the repository. I will retain a personal copy of the style, and if there is a change in the position, I will be happy to restore it to the repo, with any improvements made to it in the meantime.

Changed Harvard 7 Style (de) for Political Science

Hello!

I have changed the Harvard 7 Style (de) developed by Julian Onions and Sven Rothe to suit the needs for citing in Harvard style in German texts, especially in Political Science. Mainly, I changed the in-text citation style to [author year: page], avoiding the abbreviation for pages (S.) and changing the delimiters (no comma between author and year). For example: (Asbach 1999: 45) instead of (Asbach, 1999: S. 45) which is not the correct citing style in text for Political Science.

The style has been uploaded to:

git://gist.github.com/1546825.git

It might be interesting for others, as the in-text citation style meets the requirements of the "amerikanische Zitierweise" oder "Harvard Zitiersystem" (Harvard citation style in German) for theses in Political Science/Social Sciences. Is it possible to add it to the zotero style repository?

Thanks in advance!

Best,

Saskia Mestern

Scandinavian Journal of Clinical and Laboratory Investigation

Hi,
i just tried to post a new journal style in the repository. It's my fist attempt, so I'm not shure wether I followed all steps correctly, but here it is: git://gist.github.com/2310288.git

The style validates and works correctly in Papers2 (at least for my manuscript).

Sincerely
/Magnus

Create Quality Markers

Inspired by this tweet.
It would be very useful if users could gauge the level of vetting and thoroughness that has gone into a citation style - e.g. CMoS and APA are very good, APSA is only soso, etc. Could be done either with some type of crowd evaluate tool, or simply indicated by the author/committer.

APA Capitalization Issues

APA style requires that journal article titles have only the initial letter and the first letter following a colon capitalized, all the rest lower-case. The apa.csl file here doesn't seem to output in that format (unless, of course, I enter the article title in that way to begin with). As I regularly switch between APA and MLA, this is problematic. Can the CSL file specify the proper capitalization?

Palaeontology citation style

I've added a new citation style to github for the Journal 'Palaeontology'. The link is git://gist.github.com/1768562.git or https://gist.github.com/1768562

Details for the journal can be found at http://onlinelibrary.wiley.com/journal/10.1111/(ISSN)1475-4983 and http://www.palass.org/modules.php?name=palaeo&sec=publications&page=68.

The only issue that I have found is the subsequent-author-substitute does not allow for e.g.

AYE, A., BEE, B. and CEE, C. 1999...
——, —— and ——. 2000...

(subsequent-author-substitute-rule could not be implemented in Mendeley and so was excluded, presumably due to not being formally included in CSL release).

What happened to the misq.csl style?

I'm a bit confused about the file misq.csl (a style for Management Information Systems Quarterly). I could have sworn it used to be in this repository, and I see it in forked ones (including mine and Mendeley's). I might be sucking at the github; could anyone explain a) what happened (I checked dependent styles) or better b) how I can navigate github forking to find out what happened?

sage-harvard bugs for online sources

Howdy, I noticed that Sage Harvard (as specified 1) has some problems, especially for online sources:

  • extra ' .' after online titles;
  • no '(accessed 10 July 2011)';
  • no 'In: Blog title" for online/blog sources.

[rmzelle: crossposted as http://forums.zotero.org/discussion/23389/?Focus=126027#Comment_126027 ]

adding the total number of authors

I am writing a csl file for Molecular Biology and Evolution from Oxford Journals.

A requirement for this citation style is that, when there are more than 10 authors, the citation in the bibliography must contain the total number of authors.

For example:
Wilson R, Ainscough R, Anderson K, et al. (55 co-authors). 1994. 2.2 Mb of contiguous nucleotide sequence from chromosome III of C. elegans. Nature 368:32-38.

note the (55 co-authors) text after 'et al'.
How do I implement this in a csl stylesheet? How can I count the number of authors?

Early Medieval Europe journal style

I've created a new style for the journal Early Medieval Europe, that I would like to submit to the repository.

https://gist.github.com/2302143

Some final issues with the style were worked out on the Zotero forum here: http://forums.zotero.org/discussion/22752
The gist version has been edited so that the locator updates as required following fbennet's advice in that discussion, but since this fix is "just beyond the edge of the CSL 1.0 schema " it now fails validation:

"Error: Bad value locator for attribute variable on element number from namespace http://purl.org/net/xbiblio/csl.
From line 157, column 10; to line 157, column 37
↩ ↩
Error: Bad value locator for attribute variable on element number from namespace http://purl.org/net/xbiblio/csl.
From line 163, column 5; to line 163, column 32
" "/>↩ ↩ </m"

It works though!

Thanks!

apa.csl bugs (use commas instead of semicolons between citations)

Hello, I recently used apa.csl and noticed two issues, the first of which is definitely a bug.

  1. Citations of two or more works are separated by semi-colons, not commas e.g., (Jones & Powell, 1993; Peterson, 1995, 1998; Smith, 1990).
  2. A question really: in the references should bell hooks (i.e., "hook, b.") be with the other Hs, or at the end?

request for adding ISO 690:2010, Czech, author-date + numeric to Zotero style repository

I have already submitted two version of ISO 690 for Zotero at github.com:

https://gist.github.com/2658892 - ISO 690:2010 (author date, Czech)
https://gist.github.com/2658893 - ISO 690:2010 (numeric, Czech)

I worked with English versions because present Czech version includes more mistakes. I have translate some words (volume, accessed etc.), make a few changes in order of some data and punctuation to make the style being corresponding as much as possible to Czech version of ISO 690:2010.

I would be glad if you coud add these styles to Zotero repository.

Thank you in advance

Jiri Kratochvil
Masaryk University Campus Library
[email protected]
co-author of http://is.muni.cz/do/rect/el/estud/prif/ps11/metodika/web/ebook_citace_2011.html

Updated style for Journal of Applied Animal Science

I have updated the style of our journal, git://gist.github.com/1813930.git.

Anyway, I tried to write a style that support multilingual but there is an error even I followed the instruction in video. However, I left Thai term inside for users who use the locale as Thailand.

If I updated again, especially Thai supporting, I will send the new update to you again.

Thank you in advance.

Domestic Animal Endocrinology

I have edited the Traffic code to apply for the journal Domestic Animal Endocrinology. I don't know if all of the code is correct. I have validated the code, but I do not know if it will properly cite the bibliography for Domestic Animal Endocrinology yet. Please let me know if there is something wrong with the code, and I can work on correcting it.

The gist is https://gist.github.com/2141389

Thanks,
Dawn

Make it clear where to discuss a style

At the moment the general advice seems to be, "In the Zotero Styles Forums". That's fine as far as it goes, but there is a lot of noise there and noI think it would be great if every style file on http://zotero.org/styles or https://github.com/citation-style-language/styles had a link to a specific (sub)-forum to discuss it. Maybe a tracker system so that previous discussions can be referenced? Hmmm, maybe this is really a request to the Zotero forums, but one placed I looked for this was in the metadata of a CSL style.

Adding a new harvard citation style?

This is based on the Open University Harvard style but I needed the bibliography to display all author names regardless of how many there were so I made a few changes as I could not find a style that did this already. Is it possible to add this to the zotero list of styles?

https://gist.github.com/1419313

Fixing the "Accessed" glitch in CSL 0.8.1 & CSL 1.0

Deployment of citeproc-js in Zotero 2.1 has revealed a problem that affects a short list of 89 styles in the current Zotero repository. The relevant discussion can be found here.

The styles will need to be fixed by hand. As users of Zotero 2.1 can currently install styles from either zotero.org or from github, the changes will need to be reflected in both repositories. Since the conversion to github happened recently, there should not be major discrepancies between the two archives for most of the styles in the set, so if we move soon, we should be able to make the changes to the CSL 0.8.1 styles at zotero.org, and pull converted copies across. If we move soon on this, we should be able to avoid any major confusion among users.

The thread linked above includes a note on the update process, a list of affected styles, and blocks of sample code as a guide for the update required in each style.

sort lowercase names (e.g., bell hooks) in apa.csl and others?

This issue evolved from #185. The question is in the references should bell hooks (i.e., "hook, b.") be with the other Hs, or at the end with other lowercase letters? It is presently at the end (lowercase letters are apparently sorted after upper case letters). Assuming APA (or any other style) said one should sort upper/lower case together, how does one achieve this in CSL? Thanks!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.