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 -----------------------------------------------------------------