It just happened to be in my Miktex system. It was wrong in the sense that it
was outdated, but may be still working for Latex. My earlier version of Context
worked normally with it. The new version almost did.
This is one of the reasons I tend to postpone updates.
Robert
> Rob Ermers wrote:
Rob Ermers wrote:
Hi everybody,
Taco solved the problem in a private exchange of emails this evening
by suggesting, based on the log file I sent him, that the ushyphmax
file in my system could be in the wrong format. It was wrong indeed.
where did you get that faulty file from?
Hans
--
Hi everybody,
Taco solved the problem in a private exchange of emails this evening by
suggesting, based on the log file I sent him, that the ushyphmax file in
my system could be in the wrong format. It was wrong indeed.
It should contain the string \pattern{ ... patterns ... }.
Thanks a lot,
Rob Ermers wrote:
Hi,
I have been trying to get Context working properly for the last 4 hours
or so. I don't know what to do.
I'm baffled by this message as well, and the only thing I can come up
with is to try renaming or deleting this file:
(J:\tex\localtexmf\tex\context\base\./type-loc.t
Hi,
I have been trying to get Context working properly for the last 4 hours
or so. I don't know what to do.
I found out that the commands
\defaultlanguage \dogetupsometextprefix
occur in a file called lang-lab.tex.
But I don't know what to do with this knowledge.
I am ahead a deadline for
Hi,
Thanks for the link to the faq. I did what was said there:
1. I installed the lm fonts
2. I emended the miktex.ini file according to the specifications
The texexec -- make en nl still fails (see end of log)
My test file, the one I am working on, apparently processes normally,
but the out
