From: Hans Hagen <pragma@wxs.nl>
To: vit.zyka@seznam.cz
Cc: ConTeXt <ntg-context@ntg.nl>, hajtmar@gyza.cz
Subject: Re: endlinechar redefinition
Date: Mon, 04 Jun 2007 16:33:56 +0200 [thread overview]
Message-ID: <466422D4.6080909@wxs.nl> (raw)
In-Reply-To: <466420A3.1090300@seznam.cz>
Vit Zyka wrote:
> Hans Hagen wrote:
>> Vit Zyka wrote:
>>>
>>> thanks for a remmembering. As I said: this mail is a suggestion to
>>> solve a general problem by systemic way.
>>>
>> sure, but \input cannot be redefined in a robust way because of its
>> scanning nature; ok, in luatex we can intercept things, but not in mkii
>> Hans
>
> I thought that the number of calling \input inside text state is
> limited---(only?) one example is a loading encoding definition file.
> Why not to incorporate the cleverness of setting a default
> \endinputchar to a macro that invokes \input?
>
>> \startreadingfile ... \stopreadingfile is an option then
>
> understand as a solution bypassing \input redefinition
it all depends on the usage ...
- most commands use \readfile, or \readjobfile or alike
- when loading modules of system files , we revert to tex catcode regimes etc
user files ... well, here tex (context) does not know what is dealt with; take xml, in that case we want to stay in xml mode; or verbatim, which needs to set up verbatim
actually this is all arranged already (and always has been)
your problem with the pdfr-enc file results from the fact that loading that file comes at a nasty moment and afaik loading now happens under the right regime; so, if there's a problem we need to find out what's the problem with that file, since it's unrelated to \input (loading that vector is managed so to say)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2007-06-04 14:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 7:42 Vit Zyka
2007-06-02 20:58 ` Hans Hagen
2007-06-04 11:38 ` Vit Zyka
2007-06-04 13:34 ` Hans Hagen
2007-06-04 14:24 ` Vit Zyka
2007-06-04 14:33 ` Hans Hagen [this message]
2007-06-04 15:50 ` Vit Zyka
2007-06-04 21:02 ` Hans Hagen
2007-06-04 14:14 ` docbook in context R. Ermers
2007-06-04 14:42 ` luigi scarso
2007-06-04 14:56 ` context file to publisher (was: docbook in context) R. Ermers
2007-06-04 16:44 ` luigi scarso
2007-06-05 8:18 ` docbook in context R. Ermers
2007-06-07 7:43 ` R. Ermers
2007-06-07 9:23 ` luigi scarso
2007-06-07 10:14 ` R. Ermers
2007-06-07 17:00 ` Aditya Mahajan
2007-06-07 23:29 ` luigi scarso
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=466422D4.6080909@wxs.nl \
--to=pragma@wxs.nl \
--cc=hajtmar@gyza.cz \
--cc=ntg-context@ntg.nl \
--cc=vit.zyka@seznam.cz \
/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).