From: Oliver Marugg <rauricastone@gmail.com>
To: Alan Braslau <alan.braslau@icloud.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: APA 7 and https
Date: Sun, 17 Dec 2023 09:05:07 +0100 [thread overview]
Message-ID: <304CFCD1-23E6-49F4-A2BB-CEFB9A7DEAFF@gmail.com> (raw)
In-Reply-To: <20231216143318.305bbf9b@boo.my.domain>
Hi Alan
Many thanks for your solution.
Oliver
> Am 16.12.2023 um 22:33 schrieb Alan Braslau <alan.braslau@icloud.com>:
>
> A "better" solution is to put
>
> doi = {https://doi.org/__doi__},
>
> in your bibtex database
>
> but I would actually use
>
> url = {https://doi.org/__doi__},
>
> Not all editors want the complete url for the doi, but some do.
> The current scheme lets the user define url= and doi= as they wish (and
> even both) and does not impose a particular format.
>
> Alan
>
>
>
> On Fri, 15 Dec 2023 22:07:25 -0000
> rauricastone@gmail.com wrote:
>
>> Hi
>>
>> I found a solution to reach APA7 list and links.
>>
>> Using
>> $PATH/ConTeXtPATH/tex/texmf-context/tex/context/base/mkiv/publ-imp-apa.mkvi
>> in line 1306-1312, where \starttexdefinition mutable protected
>> btx:apa:doi \texdefinition {btx:format:goto} {
>> url(https://doi.org/\btxflush{doi})
>> } {
>> \hyphenatedurl{https://\btxflush{doi}}
>> }
>> \stoptexdefinition
>>
>> Change:
>> url(http://dx.doi.org/\btxflush{doi}) to
>> url(https://doi.org/\btxflush{doi}) and
>> \hyphenatedurl{doi:\btxflush{doi}} to
>> \hyphenatedurl{https://\btxflush{doi}}.
>>
>> With this two changes the correct format in the list of publications
>> is shown according apa7 and as well https links instead of http links
>> will be generated, which is also needed in apa7. Not all apa7
>> definitions are yet reach with this changes, but its a small step
>> towards.
>>
>> Merry Christmas.
>>
>> Oliver
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2023-12-18 2:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 14:34 [NTG-context] " Oliver Marugg
2023-12-15 22:07 ` [NTG-context] " rauricastone
2023-12-15 22:17 ` rauricastone
2023-12-16 21:33 ` Alan Braslau via ntg-context
2023-12-17 8:05 ` Oliver Marugg [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=304CFCD1-23E6-49F4-A2BB-CEFB9A7DEAFF@gmail.com \
--to=rauricastone@gmail.com \
--cc=alan.braslau@icloud.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).