From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Typesetting Markdown - Part 8
Date: Tue, 28 Apr 2020 12:57:48 -0700 [thread overview]
Message-ID: <CAANrE7oqwwSM1HHOVaQgtsiA_rEL+6dL_YRW1N22k+R6DHUMxA@mail.gmail.com> (raw)
In-Reply-To: <254fb0ea-1792-d1c9-90f2-150e7aee7fd9@mailbox.org>
Hi Jan,
> 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.
Download "themes.zip" from the blog post. It shows some naming
conventions and relationships between projects, products,
environments, and components.
> books. What I am looking for is a script to extract all XML tags/tokens
> from their files to have a complete list of things that should be
> handled in a ConTeXt style file. Five years ago I tried to create such a
> style file by hand, but I gave up.
XSL was designed specifically to parse XML. ConTeXt has facilities for
mapping XML tokens, as you've used. Depending on the complexity of
what you're trying to accomplish, take a look at "book.zip" from the
blog post. Inside you'll find "se2md.xsl"; a similar approach could
work for TEI: put the complexity of parsing TEI into XSL, then use
ConTeXt to typeset the resulting document.
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2020-04-28 19:57 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
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 [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=CAANrE7oqwwSM1HHOVaQgtsiA_rEL+6dL_YRW1N22k+R6DHUMxA@mail.gmail.com \
--to=thangalin@gmail.com \
--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).