ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Critical Editions?
Date: Fri, 7 Jan 2022 19:31:49 +0100	[thread overview]
Message-ID: <f0043e03-14cf-b587-2961-de73d893bbb2@xs4all.nl> (raw)
In-Reply-To: <20220107182528.Horde.hYPNPWfwD1QYo42algP0sjm@home.staff.uni-marburg.de>

On 1/7/2022 6:25 PM, hanneder--- via ntg-context wrote:
> 
> Probably the situation in South Asian Studies (Indology) is peculiar.
> As I indicated, there are mostly no  budgets for book typesetting in 
> Indology and
> I know of no real expert for typesetting in this field. In other words, 
> the authors
> have do it themselves, usually in Word etc., but some do use TeX etc. 
> Our publications
> series (Indologica Marpurgensia) is, for instance, all done with LaTeX, 
> as are my publications
> with Harrassowitz, which is the largest publisher in our field in 
> Germany. There is no institution
> offering typesetting of Sanskrit editions, because there is no 
> commercial interest in it and I
> think there is no expertise for this (especially when Indian scripts are 
> used instead of transliteration).

there was a time that publishers had some pride in offering low volume 
publications and paid for that by large volume succes stories ... but 
those were real publishers (persons, not companies)

> Journals are different. Indological journals published by Brill use TeX 
> internally, which is convenient,
> but most others know only Word (->InDesign). That is the situation, 
> frustrating in a way, but it also
> gives some freedom for using TeX (and, sadly, creating one's own 
> dilettantic designs).
that brings me to the question:

   what do those who are independent from publishers really
   want in a typeseting system .. not bound by what a specific
   publisher with no real interest but profit demands

i'm often puzzled by the fact that in spite of what technology (and 
thereby tex) makes possible is not used to its full extend .. (my 
favourite exmaple: why go along the troublesome accessibility path 
instead of providing plenty variants that suit specific users and 
publish the sources so that those interested in it can do it ... 
interestingly easy audio inclusion was dropped from pdf instead of 
adding means to attach that to a stretch of text) .. i think publishers 
were never really interested in those things (no reserch lab anyway)

so ... what features would make *you* happy if you didn't have to take 
publishing (which doesn't happen) and tradition (imposed by those who 
don't publish your work anyway) into account but could produce the best 
for your reader

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2022-01-07 18:31 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
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 [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=f0043e03-14cf-b587-2961-de73d893bbb2@xs4all.nl \
    --to=ntg-context@ntg.nl \
    --cc=j.hagen@xs4all.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).