ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henri Menke <henrimenke@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to extend btx rendering?
Date: Mon, 18 Jul 2016 20:30:29 +0200	[thread overview]
Message-ID: <a14efd2d-583d-be64-7b82-3853ef86111b@gmail.com> (raw)
In-Reply-To: <44e84409-3da4-2530-e35c-1c98a65ac76f@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3849 bytes --]

Alan,

I noticed that there are some difficulties.  The patched version of
`publ-imp-aps.mkvi` behaves unexpected.  The year in the @electronic
citation is now missing a space and an opening parenthesis.
Furthermore, when I place hyperlinks the color »spills over«, see
attached.  The link is only on the string `arXiv:1607.04624` but the
whole line is coloured.  Below is some minimal code to reproduce using
ConTeXt in TL2016.

Cheers,
Henri

---

\startbuffer [references]
  @electronic{Kudryashov2016,
    title = {Normal State of the Metallic Hydrogen Sulfide},
    author = {Kudryashov, Nikolay A. and Kutukov, Alexander A. and
Mazur, Evgeny A.},
    year = {2016},
    howpublished = {arXiv:1607.04624},
    url = {https://arxiv.org/abs/1607.04624}
  }
\stopbuffer

\setupinteraction[state=start]

\usebtxdataset[references.buffer]
\usebtxdefinitions[aps]

\starttext

\cite{Kudryashov2016}
\placelistofpublications

\stoptext

On 07/18/2016 08:05 PM, Henri Menke wrote:
> Alan,
> 
> thanks for your speedy reply.  Actually, I also dislike the scattered
> specification of `eprint` and `archivePrefix`, but thought that it might
> be better to keep it for interoperability between ConTeXt and biblatex.
> 
> The solution you sent to me works nicely and looks very clean.  I will
> repeat it here, because you only sent it to me personally instead of the
> list and it might be helpful to other people, so here it is:
> 
> @electronic{Kudryashov2016,
>     title = {Normal State of the Metallic Hydrogen Sulfide},
>     author = {Kudryashov, Nikolay A. and Kutukov, Alexander A. and
>     Mazur, Evgeny A.},
>     year = {2016},
>     howpublished = {arxiv:1607.04624},
>     url = {http://arxiv.org/abs/1607.04624},
> }
> 
> 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?
> 
> Cheers,
> Henri
> 
> On 07/18/2016 05:40 PM, Alan BRASLAU wrote:
>> On Mon, 18 Jul 2016 15:06:06 +0200
>> Henri Menke <henrimenke@gmail.com> wrote:
>>
>>> But I don't want to edit any system files, because this is not
>>> portable. Also I don't want to have a copy of this file in my project
>>> directory, because this is just redundant.
>>>
>>> How can I add the two fields `eprint` and `archivePrefix` to
>>> `categories.article.optional` from the document level?
>>
>> Hi Henri,
>>
>> eprint and archivePrefix are in no ways standard to bibtex.
>>
>> But really, an eprint is NOT an *article* until it gets published, and
>> then it should be cited as an article and not as a preprint.
>>
>>
>> What you are looking for is a way to attach a label "arXiv:1607.04624"
>> to the url = {http://arxiv.org/abs/1607.04624}, similarly to how a doi
>> is handled.
>>
>> I can easily add the field arxiv to the "aps" rendering as it is
>> well-defined.
>>
>> I can also add the field eprint (to be combined with the url field) as
>> in
>>   eprint = {arxiv:1607.04624},
>>   url = {http://arxiv.org/abs/1607.04624},
>> as this use can be pretty general. But I do *not* like the
>> archivePrefix use of biblatex as it is a good example of bloat and
>> feature creep.
>>
>> So I will modify the aps specifications to be used as
>>
>> @unpublished{Kudryashov2016,
>>     title = {Normal State of the Metallic Hydrogen Sulfide},
>>     author = {Kudryashov, Nikolay A. and Kutukov, Alexander A. and
>>     Mazur, Evgeny A.},
>>     year = {2016},
>>     eprint = {arxiv:1607.04624},
>>     url = {http://arxiv.org/abs/1607.04624},
>> }
>>
>>
>>
>>
>> Alan
>>
> 


[-- Attachment #2: test.pdf --]
[-- Type: application/pdf, Size: 11976 bytes --]

[-- Attachment #3: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2016-07-18 18:30 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 [this message]
2016-07-18 19:39       ` Alan BRASLAU

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=a14efd2d-583d-be64-7b82-3853ef86111b@gmail.com \
    --to=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).