ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: Henri Menke <henrimenke@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to extend btx rendering?
Date: Mon, 18 Jul 2016 13:39:45 -0600	[thread overview]
Message-ID: <20160718133945.0b6306c8@cea.fr> (raw)
In-Reply-To: <44e84409-3da4-2530-e35c-1c98a65ac76f@gmail.com>

On Mon, 18 Jul 2016 20:05:52 +0200
Henri Menke <henrimenke@gmail.com> wrote:

> I think it would be advantageous to also have the eprint/howpublished
> field available for @article such that I can link the arXiv even
> though an article has been published.  This way people without
> subscription to a specific journal can readily access the preprint
> (open-access philosophy).  Do you consider this a viable option?

Actually, correct usage *requires* you to give the published reference
and doi. The APS, for example, will accept manuscripts that have been
put on a preprint database, but the author *must* subsequently modify
the entry on the preprint database to give the published reference.

The howpublished field would be inappropriate for a published
@article{}.

An author can always choose to add a note, as in
  note={preprint available as arxiv:1607.04624},
but this will not get hyperlinked to the url using the aps
bibliography specifications.

My suggestion would be to keep your (@electronic) entry in the .bib
file and to add the published version as a new @article entry. Then one
has two choices:
  \cite[article,electronic]
that will generate two references, or
  \cite[article+electronic] 
that will generate a single reference. Note that (often?) the year
might differ (depending on when in the year and how long it took to get
published)!

Alan
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2016-07-18 19:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18  8:54 Henri Menke
2016-07-18 13:06 ` Henri Menke
2016-07-18 15:40   ` Alan BRASLAU
2016-07-18 18:05     ` Henri Menke
2016-07-18 18:30       ` Henri Menke
2016-07-18 19:39       ` Alan BRASLAU [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160718133945.0b6306c8@cea.fr \
    --to=alan.braslau@cea.fr \
    --cc=henrimenke@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).