From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: Latest version + itemize
Date: Wed, 8 Jun 2005 19:06:39 +0200 [thread overview]
Message-ID: <93917691-4E21-4D38-BF5B-EA6EE3625DDC@uni-bonn.de> (raw)
In-Reply-To: <42A4166F.6080709@elvenkind.com>
Just wanted to mention that I'm back to my box with the latest
ConTeXt. Uncommenting the line
\resetmapfiles \usetypescript [map] [base] [all]
and commenting everything else in the \resetmapfiles-department
appears to have fixed all my troubles in OS X. Let's see if htings
continue to work. Thanks to everybody, especially to Taco.
Best
Thomas
On Jun 6, 2005, at 11:25 AM, Taco Hoekwater wrote:
>
> I just realized something else that could be wrong: did you guys
> fix you texmf.cnf for engine support after upgrading? If not,
> then you are perhaps still using the old formats but with the
> new runtime files.
>
> [taco@glenlivet tmp]$ texexec --version
>
> TeXExec 5.4.2 - ConTeXt / PRAGMA ADE 1997-2005
>
> texexec : TeXExec 5.4.2 - ConTeXt / PRAGMA ADE
> 1997-2005
> texutil : TeXUtil 9.0.0 - ConTeXt / PRAGMA ADE
> 1992-2004
> tex : pdfeTeXk, 3.141592-1.21a-2.2 (Web2C 7.5.3)
> context : ver: 2005.06.03
> cont-en : ver: 2005.06.03 fmt: 2005.6.6 mes: english
> cont-nl : ver: 2005.06.03 fmt: 2005.6.6 mes: dutch
>
> total run time : 3 seconds
>
>
> Taco Hoekwater wrote:
>
>> Thomas A. Schmitz wrote:
>>
>>> Hmm, when I have \startitemize[2], the symbol should be an
>>> emdash, so no math-font should be involved, right? And yes, I
>>> did run texhash after upgrading (it's run by texexec --make
>>> automagically, isn't it?). And as I said: my laptop has an older
>>> version and compiles the same file without a hitch.
>>>
>> Something became messed up during your (and Lutz') upgrade. The trick
>> is figuring out what ;) I am quite confident that a clean context
>> install does the right thing, because that's precisely what I did
>> yesterday, and I have no problems. Perhaps you can send me the log
>> files of the texexec --make (cont-en.log) and this test file?
>> Taco
>> _______________________________________________
>> ntg-context mailing list
>> ntg-context@ntg.nl
>> http://www.ntg.nl/mailman/listinfo/ntg-context
>>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next prev parent reply other threads:[~2005-06-08 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 8:01 Thomas A. Schmitz
2005-06-06 8:11 ` Taco Hoekwater
2005-06-06 8:44 ` Lutz Haseloff
2005-06-06 9:07 ` Taco Hoekwater
2005-06-06 10:00 ` Lutz Haseloff
2005-06-06 9:04 ` Thomas A. Schmitz
2005-06-06 9:13 ` Taco Hoekwater
2005-06-06 9:25 ` Taco Hoekwater
2005-06-08 17:06 ` Thomas A. Schmitz [this message]
2005-06-06 9:38 ` Lutz Haseloff
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=93917691-4E21-4D38-BF5B-EA6EE3625DDC@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).