From: "Schmitz Thomas A." <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \replaceword and \setreplacements with xml files
Date: Sat, 16 Jan 2016 13:31:57 +0100 [thread overview]
Message-ID: <90554673-5F43-40A6-8288-B23C9F125887@uni-bonn.de> (raw)
In-Reply-To: <569A285B.4090800@mailbox.org>
> On 16 Jan 2016, at 12:24, Jan U. Hasecke <juh+ntg-context@mailbox.org> wrote:
>
> Both solutions work fine if I use them in a simple context file, but I
> can't use neither solution in my xml processing.
>
> I use a customized version of the from-pandoc-to-context solution of Pablo.
>
> When I place the replacement commands somewhere in the style file I get
> no result. I can see no error message. The file is compiled just fine
> but without replacements.
>
> Has anyone yet implemented replacements in xml processing and can give
> me a hint where to place the commands?
Please provide a minimal example of your problem. It’s impossible to help when we have no clue what you’re doing.
Thomas
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-01-16 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 11:24 Jan U. Hasecke
2016-01-16 12:31 ` Schmitz Thomas A. [this message]
2016-01-16 14:58 ` Jan U. Hasecke
2016-01-17 19:05 ` Hans Hagen
2016-01-18 6:31 ` Jan U. Hasecke
2016-01-18 10:12 ` Hans Hagen
2016-01-18 9:16 ` Ligatures in EB Garamond (was: \replaceword and \setreplacements with xml files) Jan U. Hasecke
2016-01-18 10:09 ` Ligatures in EB Garamond Hans Hagen
2016-01-18 12:46 ` Jan U. Hasecke
2016-01-18 19:22 ` Hans Hagen
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=90554673-5F43-40A6-8288-B23C9F125887@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).