From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: automatically adding commands to some characters
Date: Mon, 28 Apr 2014 18:10:16 -0400 [thread overview]
Message-ID: <535ED1C8.5000506@rik.users.panix.com> (raw)
In-Reply-To: <535ECDEF.70905@gmx.es>
[-- Attachment #1.1: Type: text/plain, Size: 845 bytes --]
On 2014-04-28 17:53, Pablo Rodriguez wrote:
> Dear list,
>
> with slashes and en-dashes I experience the following in ConTeXt:
> sometimes I need to add an \hskip0pt command after them to allow
> linebreaks. One example would be "Council Directive 93/98/EEC".
>
> The issue comes when using ConTeXt as target format from markdown
> sources. pandoc generates the file, but it makes no sense to edit the
> ConTeXt source.
>
> Is there any command that allows the addition of arbitrary commands when
> a character appears in text? I mean, a way that internally replaces
> "Council Directive 93/98/EEC" with "Council Directive 93/\hskip0pt
> 98/\hskip0pt EEC"
>
> Many thanks for your help,
>
>
> Pablo
\setbreakpoints <http://wiki.contextgarden.net/Command/setbreakpoints>in
MKIV should do it. Just add it to you pandoc context template.
--
Rik
[-- Attachment #1.2: Type: text/html, Size: 1194 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2014-04-28 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 21:53 Pablo Rodriguez
2014-04-28 22:10 ` Rik Kabel [this message]
2014-05-01 18:58 ` 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=535ED1C8.5000506@rik.users.panix.com \
--to=context@rik.users.panix.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).