ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz via ntg-context" <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: Critical Editions?
Date: Tue, 4 Jan 2022 21:02:34 +0100	[thread overview]
Message-ID: <AD32284A-E318-40A8-B5D4-062A4D0A62C8@uni-bonn.de> (raw)
In-Reply-To: <5920158a-4d93-aeec-70dc-36e26a0e5d89@free.fr>

I basically agree with everything you say, Jean-Pierre. Publishers are modern-day robber barons, and they have been stifling and exploiting scholars and scholarship for many years now. Behemoths such as Brill, de Gruyter, or Elsevier are bankrupting libraries in the entire world. However, we scholars also have some responsibility: if we could agree with each other, we could easily bypass the big publishers and have our critical editions (in a variety of formats) on our university’s websites. But we don’t do that: younger scholars need the validation of big name publications to build reputation and find a job, older scholars (myself included) are vain and/or old-fashioned and prefer a “real” book.

For your questions at the end: as you know, TEI is an insanely huge beast. Nobody will be willing and/or able to implement all of it in ConTeXt. What we need is actual use cases: scholars coming here and building up the expertise via the work they’re actually doing. Preferably in smaller installments so the developers and advanced users can slowly prepare bits and pieces of these stylesheets. No-one is going to look at a 400-page edition with all kinds of special needs in one go; we start with a chapter, a few pages, and we make our way. That’s what I expected when I wrote the wiki page on TEI xml: that it would slowly develop into something more comprehensive. Alas, it has been sitting there for 11 years… Every now and then, someone will appear on the mailing list and say: I need four apparatuses and six parallel translations and bells and whistles at every paragraph, but when you ask for real examples and specifications, they ride out into the sunset, never to be heard of again… So: I’m all for continuing in this direction, but we need some continuity. (And, not to brag, but still: I even managed to obtain some funding a couple of years ago to improve the bibliographical support in ConTeXt; if you have a real project, you can always allocate some funding for these things). As for learning TEI: I really think this is absolutely inevitable; even if new formats will be invented in the future (and TEI has serious shortcomings for many sorts of manuscript traditions), they will probably do so with TEI as a starting point.

I’m not working on a critical edition right now, but I have done some preparatory work and am willing to chip in!

All best

Thomas

> On 4. Jan 2022, at 18:54, Jean-Pierre Delange via ntg-context <ntg-context@ntg.nl> wrote:
> 
> Thomas,
> 
> You are deeply right ! But this is an issue in academic edition, not only because students read no more at length (specially in humanities), and by consequence, don't buy books, but among other reasons there is a general problem in publishing in academic fields, pointed by Jürgen Hanneder : even Universities libraries don't buy all items published by scholars in a specific field, but publishers themselves have leveled the academic criterium by commercial/economic considerations. Then, scholars have to gather financial funding with technical computing practice, which is another issue, and furthermore they have to find money in order to publish at expansive cost (see Brill prices, for example).
> 
> You are right about some academic tools, like those developed by Tuft University (like ancient greek thesaurus : http://stephanus.tlg.uci.edu/ or The Liddell-Scott-Jones online dictionary : http://stephanus.tlg.uci.edu/lsj/#eid=1), but for providing such tools as online digital work, there is two ways :
> 
> 1. Academic courses on TEI XML given to advanced students in order to help them to produce well achieved projects (and provide manuals to do that; an example here in French  : http://www.bvh.univ-tours.fr/XML-TEI/ManuelWeb/Manuel_TEI_BVH.html)
> 
> 2. Or, there are not so numerous nests like NTG-Context discussion list ! How to help Jürgen (and scholars generally) who knock at the door looking for an analysis of their needs and questioning how ConTeXt may help them ?
> 
> a) They have to learn TEI XML, then
> 
> b) learn Context stylesheet !
> 
> Is it possible to gather a group of people interested by these topics ? Are we starting today ?

___________________________________________________________________________________
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:[~2022-01-04 20:02 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21  9:50 hanneder--- via ntg-context
2021-12-21 10:06 ` Denis Maier via ntg-context
2021-12-21 10:51   ` Henning Hraban Ramm via ntg-context
2021-12-24 12:07 ` Hans Hagen via ntg-context
2021-12-24 16:39   ` Bruce Horrocks via ntg-context
2022-01-03  9:43     ` hanneder--- via ntg-context
2022-01-03 10:32       ` Jean-Pierre Delange via ntg-context
2022-01-03 13:37       ` Jean-Pierre Delange via ntg-context
2022-01-03 20:46         ` STIX2 font issues with freshly installed FMTX Heinrich Paeßens via ntg-context
     [not found]           ` <C24ABDC0-DB51-46B8-9D38-4136BE590017@me.com>
     [not found]             ` <3EF0489B-E388-4E1D-A14A-DE46EE607E40@me.com>
2022-01-05 14:03               ` STIX2 font issues with freshly installed LMTX Heinrich Paeßens via ntg-context
2022-01-04 12:38       ` Critical Editions? Thomas A. Schmitz via ntg-context
2022-01-04 17:54         ` Jean-Pierre Delange via ntg-context
2022-01-04 20:02           ` Thomas A. Schmitz via ntg-context [this message]
2022-01-04 23:00             ` Jean-Pierre Delange via ntg-context
2022-01-05  8:43               ` luigi scarso via ntg-context
2022-01-05  9:47                 ` Jean-Pierre Delange via ntg-context
2022-01-05 11:54                 ` Pablo Rodriguez via ntg-context
2022-01-05 12:34                   ` Jean-Pierre Delange via ntg-context
2022-01-05 13:06                     ` Jean-Pierre Delange via ntg-context
2022-01-06 16:34                     ` Pablo Rodriguez via ntg-context
2022-01-05 15:43                   ` Henning Hraban Ramm via ntg-context
2022-01-05 16:13                   ` luigi scarso via ntg-context
2022-01-05 17:28                     ` Jean-Pierre Delange via ntg-context
2022-01-05 18:38                       ` Jean-Pierre Delange via ntg-context
2022-01-05 22:15                   ` Jean-Pierre Delange via ntg-context
2022-01-04 12:42       ` Pablo Rodriguez via ntg-context
2022-01-04 11:57 ` Pablo Rodriguez via ntg-context
2022-01-05 11:52   ` hanneder--- via ntg-context
2022-01-05 12:29     ` Jean-Pierre Delange via ntg-context
2022-01-05 17:39       ` hanneder--- via ntg-context
2022-01-05 19:05         ` Aditya Mahajan via ntg-context
2022-01-06 16:31         ` Pablo Rodriguez via ntg-context
2022-01-06 16:57     ` Pablo Rodriguez via ntg-context
2022-01-06 17:47       ` Jean-Pierre Delange via ntg-context
2022-01-06 18:41         ` Hans Hagen via ntg-context
2022-01-06 19:00           ` Henning Hraban Ramm via ntg-context
2022-01-07 17:25             ` hanneder--- via ntg-context
2022-01-07 17:35               ` luigi scarso via ntg-context
2022-01-08 11:40                 ` Jean-Pierre Delange via ntg-context
2022-01-08 13:03                   ` Hans Hagen via ntg-context
2022-01-08 17:28                     ` Jean-Pierre Delange via ntg-context
2022-01-09 10:23                     ` hanneder--- via ntg-context
2022-01-09 11:50                       ` Robert via ntg-context
2022-01-09 16:18                         ` Fonts for transliteration (was: Critical Editions?) BPJ via ntg-context
2022-01-10  9:32                           ` Denis Maier via ntg-context
2022-01-10 12:28                             ` BPJ via ntg-context
2022-01-10 12:45                               ` Denis Maier via ntg-context
2022-01-09 13:06                       ` Critical Editions? Hans Hagen via ntg-context
2022-01-09 22:41                       ` Hans Hagen via ntg-context
2022-01-09 22:46                       ` Hans Hagen via ntg-context
2022-01-10 11:26                         ` Arthur Rosendahl via ntg-context
2022-01-10 13:31                           ` Jean-Pierre Delange via ntg-context
2022-01-10 14:18                             ` Arthur Rosendahl via ntg-context
2022-01-10 19:06                       ` Hans Hagen via ntg-context
2022-01-11 16:20                         ` Arthur Rosendahl via ntg-context
2022-01-08 17:52                   ` BPJ via ntg-context
2022-01-07 18:31               ` Hans Hagen via ntg-context

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=AD32284A-E318-40A8-B5D4-062A4D0A62C8@uni-bonn.de \
    --to=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).