ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: hanneder--- via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: hanneder@staff.uni-marburg.de
Subject: Re: Critical Editions?
Date: Fri, 07 Jan 2022 18:25:28 +0100	[thread overview]
Message-ID: <20220107182528.Horde.hYPNPWfwD1QYo42algP0sjm@home.staff.uni-marburg.de> (raw)
In-Reply-To: <095b6885-e778-2434-0499-436baeba3b3e@fiee.net>


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).

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).

Jürgen

> I know one company in Leipzig that works for big publishers  
> (www.le-tex.de). I talked to them a few years ago at a book fair and  
> applied twice for their job offers (but they want people to work at  
> their office).
>
> For scientific publications they’re using a XML-to-LaTeX workflow,  
> otherwise Word-based (->XML->LaTeX or ->InDesign). Of course they  
> accept all kind of data; it looks like they’re really good in  
> automated workflows.
>
> But I guess there are strong competitors in the far east...
>
> Hraban
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


----- Ende der Nachricht von Henning Hraban Ramm via ntg-context  
<ntg-context@ntg.nl> -----



---

Prof. Dr. Juergen Hanneder
Philipps-Universitaet Marburg
FG Indologie u. Tibetologie
Deutschhausstr.12
35032 Marburg
Germany
Tel. 0049-6421-28-24930
hanneder@staff.uni-marburg.de

___________________________________________________________________________________
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-07 17:25 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 [this message]
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=20220107182528.Horde.hYPNPWfwD1QYo42algP0sjm@home.staff.uni-marburg.de \
    --to=ntg-context@ntg.nl \
    --cc=hanneder@staff.uni-marburg.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).