ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TEI - conTeXt
Date: Thu, 16 Dec 2010 08:34:44 +0100	[thread overview]
Message-ID: <D61E0ED3-C12D-4127-97E7-6064DFDA29CC@uni-bonn.de> (raw)
In-Reply-To: <AANLkTinp4AUiwa8j9T8mDUsrZz3QLfsZ6XE+-+Qc6MP2@mail.gmail.com>


On Dec 11, 2010, at 8:56 PM, Jon Crump wrote:

> 
> I've done as you suggest and downloaded the minimals beta leaving the
> TeX-live distribution behind, so I can be on the same page with you
> all. Hans's fix has worked. I'm gratified that my intuition about how
> @xml:id should work was not wrong. The example in my last message now
> works as expected.
> 

If you want to try the latest and greatest, it's indeed better to work with the minimals. You can always keep texlive if you want to use other TeX stuff or if you want a stable fallback in case the latest beta breaks.

> 
> This looks sensible to me. I'll see if I can't make it work with my
> document next week. Thanks ever so much. Is that string substitution
> function a bit of Lua?
> 

Indeed, that's a lua function. It's extracting a substring (substitution would be string.gsub).

> 
> Thomas, I do not take it in a negative way; simply practical. I take
> seriously both the principle and practice of open-source endeavors
> like ConTeXt, and the scholarly work it can support. I hope and intend
> that as I get up to speed, I'll be able to make some small
> contribution, even if it's only posting the commented example of our
> project on the wiki. I've done some programming in Python, and am
> rather keen to learn something about Lua, as they have quite a bit in
> common. It's unlikely I'll be able to make substantive contributions
> to the code, but not impossible in the fullness of time. I'm mindful
> of the generosity of all involved, and all on this list, and offer
> great thanks and kudos.
> 
> Your cautionary note on the bilingual edition is taken to heart, and I
> have recommended that for the time being our project will not try to
> implement a facing page translation. This remains an important
> desideratum for us however, and I will attend with great interest your
> progress, and the insights of any engaged in similar efforts. The
> specific use-case we have in mind, and the problems associated with it
> may be of interest to others and I'll post it on the wiki.

Good, that's the spirit!

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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2010-12-16  7:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 23:20 Jon Crump
2010-12-10 17:57 ` Thomas Schmitz
2010-12-10 20:00   ` Jon Crump
2010-12-10 20:40     ` Thomas Schmitz
2010-12-11 19:56       ` Jon Crump
2010-12-16  7:34         ` Thomas A. Schmitz [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=D61E0ED3-C12D-4127-97E7-6064DFDA29CC@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.de \
    --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).