font problems again

font problems again

[Hraban]

Sorry, I must further go on your nerves...

Now I've \setupbodyfont[ber,pos,ppl,10pt] in my test document.
pdfetex claims "Font pplr8r" not found", that must be a Palatino-Roman.
In all font*.tex files of context P-R is mapped to "pplr8t".
I found a file "pplr8r.tfm" below of \fonts
and some lines with "pplr8r" in the following files:
/dvips/config/
 lw35extra-adobe-buildin.map
 lw35extra-adobe-kb.map
 lw35extra-urw-kb.map
 lw35extra-urw-urw.map
 pdftex.map
 ps2pk.map
 psfonts.map
/dvips/base
 psfonts.map

Does it make sense to change it in some of this map files?
(Sorry, I don't understand what these file really do -- 
I thought, ConTeXt wouldn't use dvips if output is pdf.)

BTW: phvr8r (Helvetica?) is also not found, and if I process
an large file (my book project), then there're just more...

-- 
Grüßlis vom Hraban!
---
http://angerweit.tikon.ch/lieder/
http://www.planet-interkom.de/fiee.visuelle/formelsammlung.html

Re: font problems again

[Hans Hagen]

Hans van der Meer wrote:

>
> Do I now understand correctly that I MUST use texfont first in order  
> to work with fonts in ConTeXt? I did not realize that when going over  
> to the new tetex setup. I guess the typescripts for the lm/cmr fonts  
> are ready-made in the context distribution?

not for lm and cm, just if you want to use the other free fonts in 
whatever encoding

> Is there somewhere a script to do this (somewhat painless) for the  
> "regular" fonts in the teTeX distribution or should I generate just  
> by hand for whatever font I need?
>
> (2) about math typesetting
>
> Although computer modern (lm fonts) now appear in text, there is  
> something strange with math. Running the next example coming from the  
> ConTeXt manual (page 103):
> \starttext
> {$\sqrt{a^2 + b^2} = c\ \hbox{whatever} + \sin(2x)$} math\crlf
> {$\bf \sqrt{a^2 + b^2} = c\ \hbox{whatever} + \sin(2x)$} boldmath BUT  
> `sin' ISN'T, sqrt NEVER IS \crlf
> {$\bf\mf \sqrt{a^2 + b^2} = c\ \hbox{whatever} + \sin(2x)$} boldmath  
> NOW `sin' IS, sqrt NEVER IS \crlf
> \stoptext
> The second line doesn't show the "sin" in bold as contrasted with the  
> special remark in the manual. I does show in bold with \mf however.  
> Has the math behaviour changed meanwhile? Or does it point to still  
> another flaw in my setup?
> The following fonts appear in the pdf (as seen in Adobe Reader):  
> CMMI12, CMSY10, LMRoman12-Bold (and 9), LMRoman12-Regular (and 9).


this behaviour is ok; \bf switches the text font (using families) and 
that's just of of the 16 possible math fonts then; the problem with math 
and fonts is that (1) we don't have enough families and (2) using tricks 
to bypass that do not help because math fonts come into play at the 
second parsing of the math list, when tex knows what it's dealing with; 
by then only fam numbers are uses intermediate changing of font 
assignments to them has been lost (the last family assignment counts)

> in comparison, the following LaTeX example has the right behaviour:
> \documentclass{article}
> \begin{document}
> {$\sqrt{a^2 + b^2} = c$} math\hfill\break
> {\boldmath$\sqrt{a^2 + b^2} = c + \sin{}x$} boldmath\par
> \end{document}

btw, you can use:

$\bfmath \sqrt{a2 + b2} = c\ \hbox{whatever} + \sin(2x)$

a more massive change is:

%D \usetypescript [lucida] [texnansi]
%D
%D \definetypeface [boldmath] [rm] [serif]
%D   [lucida] [default] [encoding=texnansi]
%D \definetypeface [boldmath] [tt] [mono]
%D   [lucida] [default] [encoding=texnansi]
%D \definetypeface [boldmath] [ss] [sans]
%D   [lucida] [default] [encoding=texnansi]
%D \definetypeface [boldmath] [mm] [boldmath]
%D   [lucida] [default] [encoding=texnansi]
%D
%D \switchtobodyfont[lucida,10pt]
%D
%D \showmathtoken{Gamma} $\Gamma \Delta \alpha \delta \zeta$
%D
%D \switchtobodyfont[boldmath,10pt]
%D
%D \showmathtoken{Gamma} $\Gamma \Delta \alpha \delta \zeta$

Hans

Re: font problems again

[Hans Hagen]

Taco Hoekwater wrote:

>
> Hi Hans,
>
> (I am not really going to answer you, sorry).
>
> I usually ignore those "cannot find <encoding>-urw-<family>.map"
> messages (yes, I get them as well).
>
> The needed font mapping lines for the 'base' postscript
> fonts are also in "<encoding>-base.map", and that file usually
> is found. The message is often just paranoia from context.

indeed, the reason being that there is no way to determine if such a 
file exists or not)

>
> Another question from me: wasn't there a \boldmath in one of
> the third party math modules? And if yes, is it possible that
> that be added to the core in some way / some day?
>
bold math is also supported in typescripts, but depends (or course) on 
the pressence of fonts

(i forgot who made the definitions -)

Hans

Re: font problems again

[Taco Hoekwater]

Hi Hans,

(I am not really going to answer you, sorry).

I usually ignore those "cannot find <encoding>-urw-<family>.map"
messages (yes, I get them as well).

The needed font mapping lines for the 'base' postscript
fonts are also in "<encoding>-base.map", and that file usually
is found. The message is often just paranoia from context.


Hi other Hans,

Another question from me: wasn't there a \boldmath in one of
the third party math modules? And if yes, is it possible that
that be added to the core in some way / some day?


Cheers, Taco
Hans van der Meer wrote:
> Two more questions:
> 
> (1) On Nov 14, 2005, at 0:07, Hans Hagen wrote:
> 
> Do I now understand correctly that I MUST use texfont first in order  to 
> work with fonts in ConTeXt? ?
> 
> (2) about math typesetting
> Or does it point to still  another flaw in my setup?

Re: font problems again

[Hans van der Meer]

Two more questions:

(1) On Nov 14, 2005, at 0:07, Hans Hagen wrote:

> Hans van der Meer wrote:
>
>
>> No help from enabling in cont-sys.tex of:
>> \usetypescript[adobekb] [\defaultencoding]
>> (updmap.cfg contains URWkb for the LW35 fonts)
>> then it starts asking for (non-existing) maps like:
>> Warning: pdfetex (file ec-urw-helvetica.map): cannot open font map  
>> file
>>
>
> that is when you use texfont generated metrics
> texfont --encoding=ec --batch type-tfm.dat
> will generate those metrics (which are the ones i use)
>

Do I now understand correctly that I MUST use texfont first in order  
to work with fonts in ConTeXt? I did not realize that when going over  
to the new tetex setup. I guess the typescripts for the lm/cmr fonts  
are ready-made in the context distribution?
Is there somewhere a script to do this (somewhat painless) for the  
"regular" fonts in the teTeX distribution or should I generate just  
by hand for whatever font I need?

(2) about math typesetting

Although computer modern (lm fonts) now appear in text, there is  
something strange with math. Running the next example coming from the  
ConTeXt manual (page 103):
\starttext
{$\sqrt{a^2 + b^2} = c\ \hbox{whatever} + \sin(2x)$} math\crlf
{$\bf \sqrt{a^2 + b^2} = c\ \hbox{whatever} + \sin(2x)$} boldmath BUT  
`sin' ISN'T, sqrt NEVER IS \crlf
{$\bf\mf \sqrt{a^2 + b^2} = c\ \hbox{whatever} + \sin(2x)$} boldmath  
NOW `sin' IS, sqrt NEVER IS \crlf
\stoptext
The second line doesn't show the "sin" in bold as contrasted with the  
special remark in the manual. I does show in bold with \mf however.  
Has the math behaviour changed meanwhile? Or does it point to still  
another flaw in my setup?
The following fonts appear in the pdf (as seen in Adobe Reader):  
CMMI12, CMSY10, LMRoman12-Bold (and 9), LMRoman12-Regular (and 9).

in comparison, the following LaTeX example has the right behaviour:
\documentclass{article}
\begin{document}
{$\sqrt{a^2 + b^2} = c$} math\hfill\break
{\boldmath$\sqrt{a^2 + b^2} = c + \sin{}x$} boldmath\par
\end{document}

Hans van der Meer

Re: font problems again

[Hans van der Meer]

I used to work with the TeX i-Package install. But every once in a  
while tex has to be updated. Then I was confronted with fairly hefty  
downloads for my humble isdn-telephone connection (not everyone has  
adsl). That's the reason I switched over to installing teTeX and  
ConTeXy directly. Not much of a pain with an installer shell script  
and a fast machine. But thanks for your interest anyway.

On Nov 14, 2005, at 8:51, Gerben Wierda wrote:

>> With the last release of context the problem of not getting cm fonts
>> is over. These are now found.
>>
>> However, other font selections bring new difficulties.
>> I tried various combinations but did not succeed.
>> The simple program (using TeXShop):
>>
>
> Since you are using Mac OS X, if you install the TeX i-Package, you  
> get
> the texmf tree of teTeX 3.0 as well, but with a replacement of old  
> Latin
> Modern with new. A newer ConTeXt assumes the newer Latin Modern  
> afaik. The
> ConTeXt updater i-Package will get you the latest ConTeXt in  
> texmf.local.
>
> If such an install still does not get you a working ConTeXt, I'd be
> interested to find out why (and we can help each other) because it  
> is my
> goal that you have a working ConTeXt after such an install).
>
> G
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>

met vriendelijke groet,
Hans van der Meer

Re: font problems again

[Gerben Wierda]

> With the last release of context the problem of not getting cm fonts
> is over. These are now found.
>
> However, other font selections bring new difficulties.
> I tried various combinations but did not succeed.
> The simple program (using TeXShop):

Since you are using Mac OS X, if you install the TeX i-Package, you get
the texmf tree of teTeX 3.0 as well, but with a replacement of old Latin
Modern with new. A newer ConTeXt assumes the newer Latin Modern afaik. The
ConTeXt updater i-Package will get you the latest ConTeXt in texmf.local.

If such an install still does not get you a working ConTeXt, I'd be
interested to find out why (and we can help each other) because it is my
goal that you have a working ConTeXt after such an install).

G

Re: font problems again

[Hans Hagen]

Hans van der Meer wrote:

> No help from enabling in cont-sys.tex of:
> \usetypescript[adobekb] [\defaultencoding]
> (updmap.cfg contains URWkb for the LW35 fonts)
> then it starts asking for (non-existing) maps like:
> Warning: pdfetex (file ec-urw-helvetica.map): cannot open font map file

that is when you use texfont generated metrics

texfont --encoding=ec --batch type-tfm.dat

will generate those metrics (which are the ones i use)

>
> If I use
> \setupbodyfont[lbr,12pt]
> then I get just lm-roman, although I have the YandY lucida fonts  
> installed with their original YandY names (lb--.pfb)
> Here no help from changing between texnansi and ec default encoding.

lucida is a special case -)

because i used lucida a lot, those definitions ended up in the core, but 
when i bought more and more fonts, i finally decided to move the lucida 
defs to the type-buy.tex typescript because that;s where they belong

you can add the line:

  \usetypescriptfile[type-buy]

to the cont-sys.tex file, but best is (because it's a document property) 
to say in you document (or style):

\usetypescriptfile[type-buy]         % loads commercial font definitions
\usetypescript[lucida][texnansi]   % defines a lucida typeface
\setupbodyfont[lucida,12pt]         % enables the  typeface  defined as 
'lucida'

(see type-buy.tex)

so, basically, the 'lbr' choice is gone

the same is true for 'pos'; which originally was meant for the fonts 
that adobe shipped (but no longer does); over time it became for instance

\usetypescript[postscript][ec]   % times, helvetica,  courier, tx math; 
properly r-scaled 

or in components

\usetypescript[times][ec]

\setupbodyfont[times,12pt]      

in principle the

\usetypescript [adobekb] [ec]  %  depending on what is in use, if in 
doubt use [all]

should work; (keep in mind that in spite of all kind of references in 
tex environments to encodings, often only ec is shipped)

> Any idea whats amiss? I ran this on a teTeX3 install with the context  
> files unzipped into texmf-local.
> (I must confess I am tempted to give up on ConTeXt altogether,  
> because of these many font troubles.)

well, latin modern is kind of special for a while (because it involves 
some major changes in distributions as well) but that will stabelize 
(only new fonts will be added to the latin modern family; context for 
instance does support teh condensed monospaced already)

concerning distributions: because of changes in map, enc, whatever, i 
don't use updmap (i have way more fonts on my machine than present in 
distributed map files)

how old is your cont-sys.tex? take a look at cont-sys.rme and see what 
has changed (keep in mind that pdftex occasionally changes and we need 
to keep up with that as well)

[once a generic map file model is in place - which is on the agenda for 
pdftex cum suis] live may become more easy

Hans

font problems again

[Hans van der Meer]

With the last release of context the problem of not getting cm fonts  
is over. These are now found.

However, other font selections bring new difficulties.
I tried various combinations but did not succeed.
The simple program (using TeXShop):

\starttext
\setupbodyfont[tim,12pt]
hello world
\stoptext

Fails and aborts with:
This is pdfeTeX, Version 3.141592-1.30.4-2.2 (Web2C 7.5.5)
ConTeXt  ver: 2005.11.11  fmt: 2005.11.13  int: english  mes: english
....
! Font \*times12ptrmtf*:=utmr8t at 12.0pt not loadable: Metric (TFM)  
file not found.

Changing into \usetypescript[phv]\setupbodyfont[phv,12pt]
! Font \*postscript12ptrmtf*:=utmr8t at 12.0pt not loadable: Metric  
(TFM) file not found.

No help from enabling in cont-sys.tex of:
\usetypescript[adobekb] [\defaultencoding]
(updmap.cfg contains URWkb for the LW35 fonts)
then it starts asking for (non-existing) maps like:
Warning: pdfetex (file ec-urw-helvetica.map): cannot open font map file

If I use
\setupbodyfont[lbr,12pt]
then I get just lm-roman, although I have the YandY lucida fonts  
installed with their original YandY names (lb--.pfb)
Here no help from changing between texnansi and ec default encoding.

Any idea whats amiss? I ran this on a teTeX3 install with the context  
files unzipped into texmf-local.
(I must confess I am tempted to give up on ConTeXt altogether,  
because of these many font troubles.)

Hans van der Meer