ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ConTeXt users <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: ConTeXt source from XML
Date: Tue, 4 Jun 2024 17:21:55 +0200	[thread overview]
Message-ID: <25ded686-f033-4a9e-a657-26abbb2bcfe7@gmx.es> (raw)
In-Reply-To: <9ec847c8-d48f-4a4a-bf32-de940af93934@edenhauser.net>

On 6/4/24 13:51, Christoph Edenhauser wrote:
> Dear list,
>
> I am currently trying to get into Context and XML. I would like to do
> the typographical fine-tuning in Context and not in the XML document. My
> question is: Is it possible to have ConTeXt output a (preliminary)
> ConTeXt file instead of typesetting a PDF file, for further editing?

Hi Christoph,

not clear to me whether you meant an environment (a format file) with
the ConTeXt generated file.

In that case, this might help:

  context --extra=xml --analyze --template your-file.xml

With that template, you may run:

  context --environment=xml-analyze-template.tex your-file.xml

BTW, there are two typos in xml-analyze-template.tex (lines 8-9):

  - \startxmlsetup should read \startxmlsetups.
  - \xmlsetsetups should read \xmlsetsetup.

But consider that this only flushes text with no formatting (you will
have all text in a single paragraph.

If this is not what you need, a more detailed (or simply more verbose)
explanation) might help.

Just in case it might help,

Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2024-06-04 15:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 11:51 [NTG-context] " Christoph Edenhauser
2024-06-04 15:21 ` Pablo Rodriguez via ntg-context [this message]
2024-06-04 19:21   ` [NTG-context] " Christoph Edenhauser
2024-06-04 20:09     ` Hans Hagen
2024-06-05 10:00       ` Christoph Edenhauser
2024-06-05 12:16         ` Henning Hraban Ramm
2024-06-05 14:13           ` Christoph Edenhauser
2024-06-05 15:08           ` Hans Hagen
2024-06-05 14:34         ` Pablo Rodriguez via ntg-context
2024-06-05 18:23           ` Christoph Edenhauser
2024-06-06 15:33             ` Pablo Rodriguez via ntg-context
2024-06-06 15:42               ` Hans Hagen via ntg-context
2024-06-06 20:53               ` [NTG-context] " Christoph Edenhauser
2024-06-07 19:41                 ` [NTG-context] " Pablo Rodriguez via ntg-context
2024-06-07 20:34                   ` Henning Hraban Ramm
2024-06-08  7:14                   ` Denis Maier via ntg-context
2024-06-08  7:49                     ` Wolfgang Schuster
2024-06-08  8:49                       ` vm via ntg-context
2024-06-08  8:59                         ` Thomas A. Schmitz
2024-06-08  8:59                         ` Pablo Rodriguez via ntg-context
2024-06-08  9:04                       ` Pablo Rodriguez via ntg-context
2024-06-05 16:30       ` Pablo Rodriguez 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=25ded686-f033-4a9e-a657-26abbb2bcfe7@gmx.es \
    --to=ntg-context@ntg.nl \
    --cc=oinos@gmx.es \
    /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).