From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Alan Braslau <braslau.list@comcast.net>
Subject: Re: xml, language, btx problems
Date: Mon, 18 Jun 2018 12:19:33 +0200 [thread overview]
Message-ID: <0b1ce3e0-5393-ef2b-2a7d-f576d704f0d7@uni-bonn.de> (raw)
In-Reply-To: <20180617165807.79f0037c@poo.hsd1.co.comcast.net>
Hi Alan,
thanks for joining the discussion! Just to answer your two queries about
my setup:
On 06/18/2018 12:58 AM, Alan Braslau wrote:
> Thomas,
>
> Why would the definitions need to be loaded before \starttext?
> The bibliographic data can be loaded independent of any rendering or
> use definitions.
That's what I deduced from my experiments. When I load the definitions
in the xml setup of the root element, they are not loaded, but printed
verbatim to the pdf file. My deduction may be wrong - this is a pretty
complex setup, in which I produce slides, manuscript (in different
formats), handout, and bibliography all from the same xml source. So it
may be some interference/interaction of these complex parts that I don't
quite understand. I'll continue experimenting...
Also, why don't you write your custom definitions to
> handle languages, rather than writing new definition sets based on
> language?
>
There is one stumbling block that made me think I had to have two
separate setups (in addition to the fact that it makes the source
cleaner and easier to maintain): I copied publ-imp-apa.* and modified it
to suit my needs. Now for apa, editors and authors are included in one
set, e.g., in line 169-171:
categories.book = {
sets = {
author = { "author", "editor", "publisher", "title" },
}
In my German bibliography file, I distinguish between authored volumes
and edited volumes both for the presentation and for the sorting:
Author, Firstname: Title ...
as opposed to
Edited Volume, hrsg. von Firstname Editor ...
and I found that as long as I had this "set" line in my
publ-imp-style.lua file, I would always get
Editor, Firstname: Edited Volume, hrsg. von Firstname Editor ...
When I deleted the line, I could get what I wanted. So my inference was
that for my German bibliography, I needed a different lua and a
different publ-imp-.tex file. But maybe I was wrong and you have an
easier approach?
All best and thanks!
Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2018-06-18 10:19 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
2018-06-18 10:19 ` Thomas A. Schmitz [this message]
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=0b1ce3e0-5393-ef2b-2a7d-f576d704f0d7@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--cc=braslau.list@comcast.net \
--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).