ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Braslau <braslau.list@comcast.net>
To: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: xml, language, btx problems
Date: Sun, 17 Jun 2018 16:58:07 -0600	[thread overview]
Message-ID: <20180617165807.79f0037c@poo.hsd1.co.comcast.net> (raw)
In-Reply-To: <77dfd9f9-cc57-51cf-7dc8-68ca20f28130@uni-bonn.de>

On Sun, 17 Jun 2018 19:52:35 +0200
"Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de> wrote:

> However, this implies a \starttext. And the btxdefinitions need to be 
> loaded before \starttext, or so it seems.

Thomas,

Why would the definitions need to be loaded before \starttext?
The bibliographic data can be loaded independent of any rendering or
use definitions. Also, why don't you write your custom definitions to
handle languages, rather than writing new definition sets based on
language?

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
___________________________________________________________________________________

  parent reply	other threads:[~2018-06-17 22:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-17 17:52 Thomas A. Schmitz
2018-06-17 19:37 ` Pablo Rodriguez
2018-06-17 20:10   ` Thomas A. Schmitz
2018-06-17 20:36     ` Wolfgang Schuster
2018-06-18 16:36     ` Pablo Rodriguez
2018-06-17 22:58 ` Alan Braslau [this message]
2018-06-18 10:19   ` Thomas A. Schmitz
2018-06-18 10:53     ` Hans Hagen
2018-06-18 11:07       ` Thomas A. Schmitz

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=20180617165807.79f0037c@poo.hsd1.co.comcast.net \
    --to=braslau.list@comcast.net \
    --cc=ntg-context@ntg.nl \
    --cc=thomas.schmitz@uni-bonn.de \
    /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).