From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Mojca, Miktex, and seeming success!
Date: Thu, 2 Oct 2008 23:57:40 +0200 [thread overview]
Message-ID: <6faad9f00810021457m20dd9ed7m9b1ab326cfffd484@mail.gmail.com> (raw)
In-Reply-To: <20081002155339.W7FYK.546554.root@Web02>
On Thu, Oct 2, 2008 at 10:53 PM, <dwarnold45@suddenlink.net> wrote:
> Mojca,
>
> OK, saw your new post on:
>
> http://blog.miktex.org/post/2008/05/ConTeXt-support.aspx
>
> So, I extracted cont-tfm.zip to c:\Contet, used Miktex2.7->Settings to add it as a Root, refreshed the filename database, but the formats will still not build in Miktext2.7->Settings->Format cont-en.pdftex.
>
> Creating the cont-en.pdftex format file...
> Running pdftex...
> This is pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7) (INITEX)
>
> entering extended mode
>
> ("C:\Program Files\MiKTeX 2.7\tex\context\config\cont-en.ini")
>
> ! Emergency stop.
>
> <*> cont-en.ini
You could try to change "cont-en.ini" into "cont-en.tex". I have no
idea what's the difference, but one of the two of you who have
complained about non-working ConTeXt on MikTeX reported that changing
cont-en.ini into cont-en.tex has helped.
> makefmt: pdftex failed on cont-en.ini.
> initexmf.EXE: The operation failed for some reason.
I got that one lots of time as well, but no idea why.
> And my new format attempt won't build either:
>
> ("C:\Program Files\MiKTeX 2.7\tex\context\patterns\lang-hu.pat"
>
> ! TeX capacity exceeded, sorry [pattern memory=300000].
>
> l.1243 ^^c3^^a1h1ors
That one should be solvable, it's only that MikTeX handles those
memory values in some non-standard way.
See this thread:
http://www.linuxquestions.org/questions/linux-general-1/miktex-tex-capacity-exceeded-651565/
http://docs.miktex.org/manual/initexmf.html
I guess that it could be something like
initexmf --edit-config-file pdftex.cfg
and then you set pattern-memory or pattern_memory to some larger
value. But you would need to google and test.
> Finally, I gave up on trying to use Miktex2.7->Settings to build the formats, opened a DOS box, and typed:
>
> $ texmfstart texexec --make --all
If you create texexec.bat, you don't need to type all that. I never
use texmfstart, only texexec or context.
> I refreshed the filename database, now things seemingly work.
>
> This file:
>
> \starttext
> Hello, World!
> \stoptext
>
> Does compile with:
>
> $ texmfstart texexec --pdf junk.tex
>
> And this file:
>
> input mp-tool
>
> beginfig(1);
>
> numeric u;
> 10u=4in;
>
> drawdblarrow (-5u,0)--(5u,0);
> label.rt(btex $\theta$ etex, (5u,0));
> drawdblarrow (0,-5u)--(0,5u);
> label.top(btex $\phi$ etex, (0,5u));
>
> endfig;
>
> end.
>
> Does compile with:
>
> $ mpost junk.mp
>
> And more importantly, mptopdf now seemingly works, as I can now do:
>
> $ mptopdf junk.1
>
> Which produces junk-1.pdf and opens correctly with the correct fonts.
Great :)
> So, we'll see how this stands up ....
>
> Thanks for the help.
>
> Still open to further suggestion if any critique of my method.
See above, but if texexec --make works OK, that's fine. There have
been numerous problems with formats in MikTeX and I wasn't sure if
they have been resolved or not.
Mojca
___________________________________________________________________________________
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:[~2008-10-02 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 20:53 dwarnold45
2008-10-02 21:57 ` Mojca Miklavec [this message]
2008-10-03 8:42 ` Ulrike Fischer
2008-10-03 10:01 ` Ulrike Fischer
2008-10-03 10:09 ` Wolfgang Schuster
2008-10-03 11:34 ` Ulrike Fischer
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=6faad9f00810021457m20dd9ed7m9b1ab326cfffd484@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--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).