From: David Arnold <david-arnold@redwoods.edu>
Subject: Re: Iwona font
Date: Mon, 28 Nov 2005 10:31:19 -0800 [thread overview]
Message-ID: <EC04309B-C1D3-4C8A-AB44-700BBA10109F@redwoods.edu> (raw)
In-Reply-To: <438B288C.5010105@wxs.nl>
Hans,
Frustrating and I agree.
So, perhaps the way to go is through trouble shooting advice in the
manuals. This advice should take the form of "If you see this, then
do this..."
The difficulty, at least for me, is the fact that I don't understand
the sequence of engines that are brought to bear when compiling. When
compiling stops with an error with "this not found" or "that not
found," I have no clue on how to fix it.
On the other hand, you and other gurus see such a message and you
seem to say "oh, such and such is missing." Maybe a manual like
mfonts.tex should spend a significant amount of space addressing
these trouble shooting techniques.
On Nov 28, 2005, at 7:55 AM, Hans Hagen wrote:
> David Arnold wrote:
>
>> Hans, I did, but I'll try again:
>
> well, the log says:
> Warning: pdfetex (file texnansi-iwona.map): cannot open font map file
>
> and i took a look at the latest zip and there they use
>
> iwona-*.map
>
> names instead of
>
> *-iwona.map
>
> so ... another uncommunicated change in names
>
> i slowly come to the conclusion that
>
> (1) we should forget about being early adopters (or not adopt at all)
> (2) distributions will become more and more instable
> (3) if things go on this way, tex will not survive
> (4) it's time we start making our own repository and distribution
>
> i simply don't have the time to keep up with all those changes; it
> looks like the policy of today is "wipe out and start new" which
> also means "never buy a font" and "don't install your own stuff" etc
>
> (there is no way to determine such changes unless we load every map
> file available which is something i don't want to do at all because
> it's the cause of even more trouble)
>
>>
>> sudo texhash
>>
>> And got this response:
>>
>> Password:
>> texhash: Updating /usr/local/teTeX/share/texmf/ls-R...
>> texhash: Updating /usr/local/teTeX/share/texmf.gwtex/ls-R...
>> texhash: Updating /usr/local/teTeX/share/texmf.local/ls-R...
>> texhash: Updating /usr/local/teTeX/share/texmf.tetex/ls-R...
>> texhash: Updating /var/tmp/texfonts/ls-R...
>> texhash: Done.
>>
>> Mktexlsr seems to do the same thing:
>>
>> 011-101:~/tmp davidarnold$ sudo mktexlsr
>> mktexlsr: Updating /usr/local/teTeX/share/texmf/ls-R...
>> mktexlsr: Updating /usr/local/teTeX/share/texmf.gwtex/ls-R...
>> mktexlsr: Updating /usr/local/teTeX/share/texmf.local/ls-R...
>> mktexlsr: Updating /usr/local/teTeX/share/texmf.tetex/ls-R...
>> mktexlsr: Updating /var/tmp/texfonts/ls-R...
>> mktexlsr: Done.
>>
>> Then:
>>
>> 011-101:~/tmp davidarnold$ cat junk.tex
>>
>> \definetypeface[david][rm][sans][iwona][default][encoding=texnansi]
>> %\definetypeface[david][mm][math][iwona][default]
>>
>> \setupbodyfont[david,ss,10pt]
>>
>> \starttext
>> This should work.
>> \stoptext
>>
>> And, no luck. Log file attached.
>>
>>
>>
>> On Nov 28, 2005, at 2:38 AM, Hans Hagen wrote:
>>
>>> David Arnold wrote:
>>>
>>>> 1. Do I have to also do an updmap or enable or some such thing?
>>>
>>>
>>> no, context loads the files needed at runtime
>>>
>>>>
>>>> 2. I note that on my office system, /usr/local/teTeX is owned
>>>> by root:wheel. But done in my fonts directory, some files are
>>>> owned by darnolddarn:admind and some by root:admin. Could this
>>>> be a problem?
>>>
>>>
>>> did you run a mktexlsr ? (otherwise tex cannot find the files)
>>>
>>> Hans
>>> _______________________________________________
>>> ntg-context mailing list
>>> ntg-context@ntg.nl
>>> http://www.ntg.nl/mailman/listinfo/ntg-context
>>
>>
>> David Arnold
>> College of the Redwoods
>> Mathematics Department
>> Eureka, CA 95501
>> (707) 476-4222
>> http://online.redwoods.edu/instruct/darnold/
>>
>>
>> ---------------------------------------------------------------------
>> ---
>>
>> _______________________________________________
>> 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
David Arnold
College of the Redwoods
Mathematics Department
Eureka, CA 95501
(707) 476-4222
http://online.redwoods.edu/instruct/darnold/
next prev parent reply other threads:[~2005-11-28 18:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 3:35 David Arnold
2005-11-26 5:25 ` David Arnold
2005-11-26 9:05 ` VnPenguin
2005-11-27 20:37 ` Hans Hagen
2005-11-27 20:31 ` Hans Hagen
[not found] ` <FAE9B483-F880-4C57-B4E1-874E3FC5B658@redwoods.edu>
[not found] ` <438A304E.5000705@wxs.nl>
2005-11-28 1:24 ` David Arnold
2005-11-28 10:38 ` Hans Hagen
2005-11-28 15:25 ` David Arnold
2005-11-28 15:55 ` Hans Hagen
2005-11-28 18:31 ` David Arnold [this message]
2005-11-28 19:37 ` Hans Hagen
2005-11-28 22:43 ` I can't find the format file `pdfetex.fmt'! ktt
2005-11-28 23:23 ` Hans Hagen
2005-11-29 5:48 ` ktt
2005-11-29 9:19 ` Hans Hagen
2005-11-29 22:03 ` Iwona font David Arnold
2005-11-30 8:18 ` Hans Hagen
2005-11-28 16:09 ` Hans Hagen
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=EC04309B-C1D3-4C8A-AB44-700BBA10109F@redwoods.edu \
--to=david-arnold@redwoods.edu \
--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).