From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: Aditya Mahajan <adityam@umich.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bad argument #1 to 'prehypenchar'
Date: Tue, 15 Sep 2020 21:43:57 +0200 [thread overview]
Message-ID: <984fff4c-5946-b94b-575f-d8a0ec1ce3d3@gmail.com> (raw)
In-Reply-To: <nycvar.YAK.7.78.908.2009151518360.1104819@nqv-guvaxcnq>
Aditya Mahajan schrieb am 15.09.2020 um 21:19:
> On Tue, 15 Sep 2020, Wolfgang Schuster wrote:
>
>> You have to add \resetbreakpoints to the vim/filter module.
>
> Thanks. I had:
>
> \doifnotinset{\v!hyphenated}{\externalfilterparameter\c!option}
> {\language\minusone}%
>
> which I changed to
>
> \doifnotinset{\v!hyphenated}{\externalfilterparameter\c!option}
> {\language\minusone
> \resetbreakpoints}%
>
> and this fixed the error.
Don't use the \language hack, the official and supported commands are
\nohypens and \dohyphens or when you need a interface for it use
\usehyphensparameter\...parameter
which allows
\setup...[hyphens=yes|no]
Wolfgang
___________________________________________________________________________________
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-09-15 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 3:30 Aditya Mahajan
2020-09-15 6:50 ` Wolfgang Schuster
2020-09-15 19:19 ` Aditya Mahajan
2020-09-15 19:43 ` Wolfgang Schuster [this message]
2020-09-15 19:51 ` Aditya Mahajan
2020-09-15 20:13 ` 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=984fff4c-5946-b94b-575f-d8a0ec1ce3d3@gmail.com \
--to=wolfgang.schuster.lists@gmail.com \
--cc=adityam@umich.edu \
--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).