From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Question: Are there any ConTeXt aware scientific pulishers yet
Date: Thu, 16 Apr 2020 09:02:43 +0200 [thread overview]
Message-ID: <90B7B6F4-DF02-4BAF-AC1C-FB8F6CB05D7B@fiee.net> (raw)
In-Reply-To: <1333714293.40770.1586983931754@office.mailbox.org>
> Am 15.04.2020 um 22:52 schrieb denis.maier.lists@mailbox.org:
>
> Hi,
>
>> 1) Does anybody know of any scientific publisher or single journals
>> which accept papers/book chapters typeset in ConTeXt yet
>
> I will use ConTeXt to typeset the Jewish Studies journal *Judaica* (https://bop.unibe.ch/index.php/judaica/index). (The first issue should appear soon.) However, we do not accept ConTeXt sources as we use jats xml as our production format. (Actually, I don't expect any of our authors is using ConTeXt.)
Interesting. Is ConTeXt handling Hebrew well?
>
>> 2) If there are any is any of them convinced enought about ConTeXt to recommend use of ConTeXt or even provide template?
>
> Yes, I gave two talks last year at the Public Knowledge Project Conference in Barcelona. One was about our general workflow (going from docx via pandoc markdown to jats xml; the other was about typesetting xml with ConTeXt.)
I’m using a Python script to convert DOCX to ConTeXt. The better the input, the better the output can be. Usually there’s a lot of manual work. (Last week I had an article whose author never grew out of the typewriter, i.e. every line was a paragraph, footnotes were just paragraphs at the end of his pages – of course my script couldn’t handle that well.)
>> 3) What would be needed and what could help to make them aware?
>> (difficult to properly formulate, if unclear dont bother)
>
> Don't know. Perhaps more examples?
Even LaTeX is a niche; there are not enough users of ConTeXt for it to look reliable, I guess. You can’t really use it without involving yourself in the community.
And while I generally love working with ConTeXt, I’m cursing it often enough for unexpected/undocumented behaviour, unfinished features and scattered documentation. My book is intended to fix the latter, but there’s no progress – I got too many different projects and severe limitations of working capacity. And children at home...
Best, 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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-04-16 7:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 15:47 Christoph Hintermüller
2020-04-15 17:18 ` Henning Hraban Ramm
2020-04-15 20:52 ` denis.maier.lists
2020-04-16 7:02 ` Henning Hraban Ramm [this message]
2020-04-16 8:26 ` denis.maier.lists
2020-04-16 8:32 ` luigi scarso
2020-04-16 10:24 ` Hans Hagen
2020-04-16 12:03 ` denis.maier.lists
2020-04-19 10:16 ` Hans Hagen
2020-04-16 7:53 ` Pablo Rodriguez
2020-04-16 8:00 ` Arthur Reutenauer
2020-04-16 14:04 ` Pablo Rodriguez
2020-04-16 8:05 ` denis.maier.lists
2020-04-16 14:05 ` Pablo Rodriguez
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=90B7B6F4-DF02-4BAF-AC1C-FB8F6CB05D7B@fiee.net \
--to=texml@fiee.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).