ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Braslau <braslau.list@comcast.net>
To: Gour <gour@atmarama.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Module for Markdown: any volunteer to make a ConTeXt interface?
Date: Sun, 24 Dec 2017 10:21:27 -0700	[thread overview]
Message-ID: <20171224102127.004a8efb@zoo.hsd1.co.comcast.net> (raw)
In-Reply-To: <p1ofcc$e06$1@blaine.gmane.org>

On Sun, 24 Dec 2017 16:01:27 +0100
Gour <gour@atmarama.com> wrote:

> On Sat, 23 Dec 2017 15:04:35 -0700
> Alan Braslau <braslau.list@comcast.net> wrote:
> 
> > This analysis is not quite correct.  
> 
> Thank you for your input.
> 
> > I use the "bibliography" subsystem as a general database tool,
> > defining glossaries, tables of crystallographic symmetries, catalogs
> > of diagrams, etc., so it is quite a bit more flexible than just to
> > create bibliographies.  
> 
> Does it mean there is no need for tools like JabRef, Zotero etc. if
> I'm staying within the scope of ConTeXt?

JabRef, Zotero are tools useful to manage bibliographic datasets. Their
use is not necessary, yet may be quite helpful, and even can be
customized at will, if desired.

Rik has pointed out a few bugs in the APA (author-year) formatting that
will be fixed as they get clearly reported. Even though I started out
with the APS (numbered) specification, I have been using APA more
thoroughly. Note that APS is purposely very compact (and limited).
Thomas seems to use the author-num scheme principally, and this appears
to be about the extent to which the ConTeXt system has been tested.

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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2017-12-24 17:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04 20:55 Mojca Miklavec
2017-05-05 19:54 ` Aditya Mahajan
2017-05-05 21:12   ` Mojca Miklavec
2017-05-05 22:04     ` Vít Novotný
2017-05-06  8:28   ` Hans Hagen
2017-05-06 11:16     ` Brian Ballsun-Stanton
2017-05-07 21:33       ` r.ermers
2017-12-05 18:20         ` Gour
2017-12-23 21:44           ` Rik Kabel
2017-12-23 22:04             ` Alan Braslau
2017-12-24 15:01               ` Gour
2017-12-24 17:21                 ` Alan Braslau [this message]
2017-05-06 15:42     ` John Culleton
2017-05-06 15:51       ` Mica Semrick

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=20171224102127.004a8efb@zoo.hsd1.co.comcast.net \
    --to=braslau.list@comcast.net \
    --cc=gour@atmarama.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).