From: denis.maier.lists@mailbox.org
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 10:26:31 +0200 (CEST) [thread overview]
Message-ID: <845268139.45917.1587025591759@office.mailbox.org> (raw)
In-Reply-To: <90B7B6F4-DF02-4BAF-AC1C-FB8F6CB05D7B@fiee.net>
> Henning Hraban Ramm <texml@fiee.net> hat am 16. April 2020 09:02 geschrieben:
> > 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?
Well, it's not field tested yet. But yes, the demo files work.
>
> >
> >> 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.)
Yeah, as always, the output is only as good as the input. That's partly why I use pandoc (twice, actually.) In a first run, I produce a normalized markdown file, where such idiosyncrasies are removed. There, I then add additional formatting. In the second run I can then produce the XML. We need the XML to produce a nice web view using the Lens Viewer. And also, with pandoc it's much easier to produce XML than ConTeXt.
Best,
Denis
___________________________________________________________________________________
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 8:26 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
2020-04-16 8:26 ` denis.maier.lists [this message]
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=845268139.45917.1587025591759@office.mailbox.org \
--to=denis.maier.lists@mailbox.org \
--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).