ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: David Arnold <darnold@northcoast.com>
Cc: cs@miktex.org, ntg-context@ntg.nl, miktex@dsts.dk
Subject: Re: Font problems
Date: Tue, 21 Aug 2001 10:48:55 -0700	[thread overview]
Message-ID: <3.0.5.32.20010821104855.0086ac60@mail.northcoast.com> (raw)
In-Reply-To: <5.1.0.14.1.20010821101947.0341a320@server-1>

Hans,

Some progress, still not there. Here is the file I am compiling. Call it
junk.tex.

%output=pdf
\starttext
\usetypescript [all] [lucida] [texnansi]
My name is David!
\stoptext

As per installation directions, I found \miktex\pdftex\config\pdftex.cfg.
It looked like this before I started messing with it. 

pk_resolution 600
output_format 1
compress_level 9
decimal_digits
3
page_width 210 true mm
page_height 297 true mm
horigin 1 true in
vorigin
1 true in
map psfonts.map

I added the following as per instructions in minstall.pdf.

pk_resolution 600
output_format 1
compress_level 9
decimal_digits
3
page_width 210 true mm
page_height 297 true mm
horigin 1 true in
vorigin
1 true in
map psfonts.map
map +context.map

Now, the above file (junk.tex) compiles, but fonts are completely igonored
and the resulting pdf file reports (Document Properties->Fonts) that cmr12
is used. If I change the last line of pdftex.cfg to:

map context.map

then compiling junk.tex gives me a pdf file that reports (Document
Properties->Fonts) that the orginal font is F1, type is Type 3, encoding is
Custom, Actual font is F1, and type is Type 3. So, that is the good news.
Of course, that's not Lucida and the output looks terrible. So that's the
bad news.

As another test, with map context.map in pdftex.cfg, the following file

%output=pdf
\starttext
\setupbodyfont[lbr]
My name is David!
\stoptext

still gives this error:

cannot find LucidaBright source file.
hbf2gf -q -g LucidaBright 300
MAKETFM: don't know how to make LucidaBright

! Font \*12ptrmtf*=LucidaBright at 12.0pt not loadable: Metric (TFM) file
not f
ound.
\lastfontname ...idaBright at \scaledfont

\donoparsefontspec ...sname \lastfontname
                                          \relax \the \everyfont \relax
\xxdododefinefont ...tclass #1\fontsize *}
                                          \doresetrelativefontsize \f...
\fontstrategy ...ame #2#3#4#5#6\endcsname
                                          \let \fontstrategy \gobbles...
<inserted text> ...talternative \fontsize
                                          \fontstrategy \autofontsize...
\synchronizefont ... \the \fontstrategies
                                          \ifskipfontcharacteristics ...
...
l.4 \setupbodyfont[lbr]

?

As another interesting test, with either

pk_resolution 600
output_format 1
compress_level 9
decimal_digits
3
page_width 210 true mm
page_height 297 true mm
horigin 1 true in
vorigin
1 true in
map psfonts.map

or

pk_resolution 600
output_format 1
compress_level 9
decimal_digits
3
page_width 210 true mm
page_height 297 true mm
horigin 1 true in
vorigin
1 true in
map psfonts.map
map +context.map

the file (call it junk2.tex)

\documentclass{article}
\usepackage{lucidabr}
\begin{document}
Hello, cruel world!
\end{document}

compiles just fine. The pdf file reports (Document Properties->Fonts)
Original font as LucidaBright, type as Type 1, Encoding as custom, Actual
font as Embedded subset, and type as Type 1. However, if I use

pk_resolution 600
output_format 1
compress_level 9
decimal_digits
3
page_width 210 true mm
page_height 297 true mm
horigin 1 true in
vorigin
1 true in
map psfonts.map
map context.map

then the resulting pdf file reports Original font as F6, type as Type 3,
Encoding as Custom, Actual font F16, and type as Type 3, just as above with
my context file junk.tex.

I am using Miktex 2 with Update 1.

At 10:21 AM 8/21/01 +0200, you wrote:
>At 07:55 PM 8/20/2001 -0700, David Arnold wrote:
>>Hans,
>>
>>My file context-vectors.tex, which compiled just fine last fall, no longer
>>compiles. I get:
>>
>>cannot find LucidaBright source file.
>>hbf2gf -q -g LucidaBright 300
>>MAKETFM: don't know how to make LucidaBright
>>
>>! Font \*9ptrmtf*=LucidaBright at 9.0pt not loadable: Metric (TFM) file not
>
>see other mail,
>
>as soon as you see a FullFontName this way, it's a signal that a mapping i 
>smissing; in the worst case, you can select the typescript:
>
>\usetypescript [all] [lucida] [texnansi]
>-------------------------------------------------------------------------
>                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
>                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
>-------------------------------------------------------------------------
>
>


       reply	other threads:[~2001-08-21 17:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3.0.5.32.20010820195552.00859200@mail.northcoast.com>
     [not found] ` <5.1.0.14.1.20010821101947.0341a320@server-1>
2001-08-21 17:48   ` David Arnold [this message]
2013-05-31 11:52 "H. Özoguz"
2013-05-31 12:22 ` Khaled Hosny
2013-05-31 13:24 "H. Özoguz"
2013-05-31 14:19 ` Idris Samawi Hamid ادريس   سماوي حامد
2013-05-31 14:32 ` Idris Samawi Hamid ادريس   سماوي حامد
2015-05-02 14:19 John Culleton
2015-05-02 18:05 ` Pablo Rodriguez
2021-11-26 11:59 font problems jdh via ntg-context
2021-11-26 12:30 ` Hans Hagen via ntg-context
2021-11-25  5:28   ` jdh via ntg-context

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=3.0.5.32.20010821104855.0086ac60@mail.northcoast.com \
    --to=darnold@northcoast.com \
    --cc=cs@miktex.org \
    --cc=miktex@dsts.dk \
    --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).