From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: issue embedding from Lua code
Date: Fri, 1 Nov 2019 11:48:27 +0100 [thread overview]
Message-ID: <876af4cd-3a5e-574b-aaa5-aeb11d73552c@gmx.es> (raw)
In-Reply-To: <42aa00c3-2d63-f222-5c22-d31d6f97e448@gmail.com>
On 11/1/19 11:08 AM, Wolfgang Schuster wrote:
> Pablo Rodriguez schrieb am 01.11.2019 um 10:44:
>> [...]
>> \start
>> \catcode`\#=12 % local change of character TeX category
>> \doloopif{\cA}{~=}{}{\getbuffer[main]}
>> \stop
>>
>> This \start..\stop is required to get identifiers in urls (such as
>> http://a.b/c#d). urls are read from a CSV file using the handlecsv module.
>>
>> Is there any way to avoid this issue?
> 1. Fix it in the module to ensure special characters are treated as letters.
This would make things way easier, I agree.
BTW, my issue was totally unrelated: missing closing brace (but the
error message in ConTeXt was misleading [at least, to me]).
> 2. Use the asciimode environment to make TeX's special characters normal
> letters.
Is there any ascii mode equivalent for Lua?
I mean, something like "asciimode(whatever)".
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2019-11-01 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 7:20 Pablo Rodriguez
2019-11-01 8:13 ` Wolfgang Schuster
2019-11-01 9:29 ` Hans Hagen
2019-11-01 9:44 ` Pablo Rodriguez
2019-11-01 10:08 ` Wolfgang Schuster
2019-11-01 10:48 ` Pablo Rodriguez [this message]
2019-11-01 11:06 ` Wolfgang Schuster
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=876af4cd-3a5e-574b-aaa5-aeb11d73552c@gmx.es \
--to=oinos@gmx.es \
--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).