ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Renaud AUBIN <aubin@nibua-r.org>
Subject: Re: Fonts problem
Date: Wed, 31 May 2006 11:55:43 +0200	[thread overview]
Message-ID: <447D681F.1020607@nibua-r.org> (raw)
In-Reply-To: <87slmqvawl.fsf@bornier.net>


Hi Jean,

Your example works here...
I'm not a font guru but it is maybe more interesting for you to use
type1 fonts. Depending on which linux distro you use, you have to tell
tetex to use type1. On my debian testing box, I have uncommented "Map
lm.map" in /etc/texmf/updmap.d/10tetex-base.cfg and sudo update-updmap
(as I remember...).

I'm not sure this will solve your problem but you can try anyway since
IMHO, it's better to have type1 fonts instead of bitmap...

Moreover, if you want correct language settings for french, you should
better write:

\setupoutput[pdf]
\useencoding[ffr]
\mainlanguage[fr]

\starttext
àéèçù
\oe \"a
\stoptext

Cordialement ;)

Renaud


Jean Magnan de Bornier a écrit :

>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
>  
>

  reply	other threads:[~2006-05-31  9:55 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 [this message]
2006-05-31 11:33 ` Hans Hagen
2006-05-31 11:50   ` Renaud AUBIN
2006-05-31 12:30   ` Jean Magnan de Bornier
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=447D681F.1020607@nibua-r.org \
    --to=aubin@nibua-r.org \
    --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).