Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What are the rules for shortening a year? #64

Open
customcommander opened this issue Feb 28, 2019 · 8 comments
Open

What are the rules for shortening a year? #64

customcommander opened this issue Feb 28, 2019 · 8 comments

Comments

@customcommander
Copy link
Contributor

Hi,

This is related to the behaviour of the form="short" attribute on a year's <date-part> element, e.g. <date-part name="year" form="short"/>. Cf date-part documentation

The above date-part element would render 2005 as 05.

Questions:

  1. Is keeping the last two numbers when shortening a year the only rule when shortening a year?
  2. Should years such as 1666, 452 or -734 be allowed to be shortened?
  3. Should only years in the 21st century be allowed to be shortened?
  4. Should shortening a year be allowed only if it doesn't create confusion? e.g. 00 can be the short version of 2000 or 1900.
@bwiernik
Copy link
Member

bwiernik commented Nov 4, 2020

Shortened years are primarily used in physical sciences styles, where references to older works isn't common, so I think that permitting shortened years on any positive (CE) 4-digit year (i.e., whenever CE/AD or BCE/BE wouldn't apply) is fine. If we drew a later line, such as 1950 or something, I'm not sure where that would appropriately be.

@denismaier @bdarcus ?

@denismaier
Copy link
Member

Not really sure, but maybe "shorten years if current year - issued year < 100". I.e, in 2020 you'd shorten all dates beginning with 1921.

@denismaier
Copy link
Member

Otoh, I think that's done mostly with label citation styles where I think this ambiguity is not so problematic as @bwiernik has pointed out.

@bwiernik
Copy link
Member

bwiernik commented Nov 5, 2020

I'm not sure how much we want to embed "current year" into CSL processing? In any event, I think it is a rare enough occurrence that we can just apply the same rules as BC/AD and call it a day.

@denismaier
Copy link
Member

I'm not sure how much we want to embed "current year" into CSL processing? In any event, I think it is a rare enough occurrence that we can just apply the same rules as BC/AD and call it a day.

Probably correct. I'm just wondering whether this is actually used in styles? As said above, I think this should mostly be relevant for label citation styles, and I doubt there will be much for for this in author date or note styles. If so, while "Ein07" my be fairly common, we'll probably never see "Einstein 07" in an author date style.

Btw, I've checked what biblatex has to offer here: Searching the manual for "two digits" only leads to two results—both in the same paragraph—that discuss how labels in label citation styles are being constructed.

@customcommander
Copy link
Contributor Author

Just to give you some context: as a pet project I'm writing a CSL processor so these are just questions about what it should do in situation X, Y or Z (as I wasn't too sure). It's not meant to be a bug report in the specs. Although if it highlights areas that could do with a bit of clarifications then bonus.

Thanks both for looking into this though :)

@denismaier
Copy link
Member

Just to give you some context: as a pet project I'm writing a CSL processor so these are just questions about what it should do in situation X, Y or Z (as I wasn't too sure). It's not meant to be a bug report in the specs. Although if it highlights areas that could do with a bit of clarifications then bonus.

Thanks both for looking into this though :)

Cool. What is that for?

@bwiernik
Copy link
Member

bwiernik commented Nov 5, 2020

Okay, cool. Let's go with short years following era marker rules.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants