From: Jean Magnan de Bornier <jm.bornier@free.fr>
Subject: Re: Fonts problem
Date: Wed, 31 May 2006 14:30:33 +0200 [thread overview]
Message-ID: <8764jm9y1i.fsf@bornier.net> (raw)
In-Reply-To: <447D7EFE.8020500@wxs.nl> (Hans Hagen's message of "Wed, 31 May 2006 13:33:18 +0200")
Le 31 mai à 13:33:18 Hans Hagen <pragma@wxs.nl> écrit notamment:
| Jean Magnan de Bornier wrote:
| > Hi all,
| > On a fresh installed done following (very exactly)
| >
| > http://wiki.contextgarden.net/TeTeX_3.0_installation,
| >
| > I get the following message with this :
| > .............................
| > \starttext
| > �����
| > \oe \"a
| > \stoptext
| > .............................
| >
| > kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 ec-lmr12
| > mktexpk: don't know how to create bitmap font for ec-lmr12.
| > kpathsea: Appending font creation commands to missfont.log.
| > xdvi: Can't find pixel font ec-lmr12; using cmr10 instead at 600 dpi.
| > xdvi-motif.bin: Warning: Character 224 not defined in font cmr10
| > xdvi-motif.bin: Warning: Character 233 not defined in font cmr10
| > xdvi-motif.bin: Warning: Character 232 not defined in font cmr10
| > xdvi-motif.bin: Warning: Character 231 not defined in font cmr10
| > xdvi-motif.bin: Warning: Character 249 not defined in font cmr10
| > xdvi-motif.bin: Warning: Character 247 not defined in font cmr10
| > xdvi-motif.bin: Warning: Character 228 not defined in font cmr10
| >
| > Something's obviously missing in my install ... but what?
| > tia
| >
| i dunno where xdvi gets its info from, but it should use latin modern
| instead of cmr but then, there are no mf sources of latin modern; can
| xdvi use type 1 fonts?
>
| (is there a reason why you use xdvi?)
(just a viewer for dvi files, does it matter?)
Well, since the first post I ran updmap-sys, and then suddenly the dvi
file is as expected; but with the pdf option I get something unexpected:
instead of blank for accented letters (when I posted first) there are now
sometimes other characters than those I type (I'll send the pdf file if it
can help).
Thanks Renaud and Hans,
--
Jean
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-05-31 12:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 8:47 Jean Magnan de Bornier
2006-05-31 9:55 ` Renaud AUBIN
2006-05-31 11:33 ` Hans Hagen
2006-05-31 11:50 ` Renaud AUBIN
2006-05-31 12:30 ` Jean Magnan de Bornier [this message]
2006-05-31 12:55 ` Renaud AUBIN
2006-05-31 13:21 ` Jean Magnan de Bornier
2006-05-31 13:50 ` Renaud AUBIN
2006-05-31 17:09 ` nico
2006-05-31 20:41 ` Jean Magnan de Bornier
2006-05-31 21:51 ` Renaud AUBIN
2006-06-01 3:52 ` Jean Magnan de Bornier
2006-06-01 7:56 ` Thomas A. Schmitz
2006-06-01 8:05 ` Taco Hoekwater
2006-06-01 9:15 ` Jean Magnan de Bornier
2006-06-01 9:37 ` Thomas A. Schmitz
2006-06-01 11:44 ` Hans Hagen
2006-06-01 12:12 ` Jean Magnan de Bornier
2006-06-01 12:42 ` Hans Hagen
2006-06-01 13:16 ` gnwiii
2006-06-01 21:50 ` Thomas A. Schmitz
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=8764jm9y1i.fsf@bornier.net \
--to=jm.bornier@free.fr \
--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).