From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Typesetting Markdown - Part 8
Date: Tue, 28 Apr 2020 09:33:52 +0200 [thread overview]
Message-ID: <F0D35F6B-4C3E-4198-8EAE-927C84DB4CF2@fiee.net> (raw)
In-Reply-To: <254fb0ea-1792-d1c9-90f2-150e7aee7fd9@mailbox.org>
> Am 28.04.2020 um 08:32 schrieb Jan U. Hasecke <juh+ntg-context@mailbox.org>:
>
> 1. Nameing and organizing the project, product and environments files. I
> am currently reorganising the files for my cooperative. I think that
> besides some nameing conventions it is more or less up to me how I
> organise our print work. Any recommendations welcome.
Yes, the naming is completely up to you.
I use:
project_something.tex
env_something.tex
prd_oneissue.tex
c_onechapter.tex
That’s also what my script supports as default:
https://github.com/fiee/tools/blob/master/contextproject.py
Probably I should switch to .mkiv extensions, since I also have LaTeX projects now.
> 2. The "Deutsches Text Archiv" has prepared a text corpus of German
> texts up to 1900 in TEI PS XML, so we could use them directly to typeset
> books.
...
> The tokens/tags differ from text to text and I think the structure too
> so that it was beyond my knowledge to generate a general style file for
> all texts.
And it’s probably impossible. Like with HTML and ePub export, the mapping of structures is very individual.
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-28 7:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 2:00 Thangalin
2020-04-28 6:32 ` Jan U. Hasecke
2020-04-28 7:33 ` Henning Hraban Ramm [this message]
2020-04-28 14:12 ` Jan-Erik Hägglöf
2020-04-28 14:39 ` contextproject script (was: Typesetting Markdown - Part 8) Henning Hraban Ramm
2020-04-28 15:29 ` Jan-Erik Hägglöf
2020-04-28 16:47 ` Henning Hraban Ramm
2020-04-28 15:33 ` Typesetting Markdown - Part 8 Thangalin
2020-04-28 15:41 ` Jan-Erik Hägglöf
2020-04-28 16:07 ` Henning Hraban Ramm
2020-04-28 21:16 ` Henning Hraban Ramm
2020-04-28 8:35 ` Saša Janiška
2020-04-28 13:57 ` Jan U. Hasecke
2020-04-28 19:57 ` Thangalin
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=F0D35F6B-4C3E-4198-8EAE-927C84DB4CF2@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).