Re: [NTG-context] Re: Confusion with font instructions
On 4 juil. 2005, at 9:54, Patrick Gundlach wrote: Hello David,
I am new to ConTeXt, as my question is about to reveal.
This questions can also come from more experienced users :)
Which set of instructions should I follow, in order to allow use of Palatino or Times, on Mac OS X, Gerben Wierda's TeX distribution, latest ConTeXt installed?
OK, do you have LaTeX working? Then you can use the standard postscript fonts for ConTeXt as well. Have a look at the (yet unfinished page)
http://contextgarden.net/Psnfss
Patrick --
Hi Patrick, David and Adam, It is right that handling fonts is extremely disappointing and instable... For instance, what used to work does not work anymore properly with the new version of ConTeXt I installed two weeks ago... For instance: \usetypescript [adobekb][\defaultencoding] \setupbodyfont[postscript] \usetypescript[times][\defaultencoding] %or helvetica, or palatino \setupbodyfont[times,12pt] used to work fine, but now it results in ConTeXt creating, the first time, a whole bunch of things regarding fonts, and then the resulting PDF contains some ugly jagging bitmap-looking characters (interestingly this happens only to the text characters, not to the math characters...). Adding \usetypescript[postscript] does not help neither. I wanted to answer David's question on Saturday but when I tried my examples, I was dispappointed and did not answer. Best regards: OK PS: When I added two samples of the PDF files to my previous post, it was blocked due to the fact that the message was over 40 Kb. So I am posting again without the attachments.
Hi Otared, What you mention sounds like a bug propagated by Hans last month. Take a look at this thread: <http://archive.contextgarden.net/thread/ 20050610.172825.65f0c37f.html#20050610.172825.65f0c37f> (Assuming you're comfortable with the CLI, I'd suggest verifying the bad file by navigating to /usr/local/teTeX/share or wherever your tex trees live, and looking for the file: ls */fonts/map/*/context/pdftex.map If a file is returned, delete it (and mktexlsr again). If nothing is returned, then never mind, it's something else on your system. One brief comment on your font selection below: Otared Kavian said this at Mon, 4 Jul 2005 16:28:31 +0200:
\usetypescript [adobekb][\defaultencoding] \setupbodyfont[postscript] \usetypescript[times][\defaultencoding] %or helvetica, or palatino \setupbodyfont[times,12pt]
The [postscript] line in the above example is unnecessary. I'd suggest cutting it out entirely. With a properly-configured system, the three remaining lines should give you the results you expect. adam -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Adam Lindsay wrote:
Hi Otared,
What you mention sounds like a bug propagated by Hans last month. Take a look at this thread: <http://archive.contextgarden.net/thread/ 20050610.172825.65f0c37f.html#20050610.172825.65f0c37f>
(Assuming you're comfortable with the CLI, I'd suggest verifying the bad file by navigating to /usr/local/teTeX/share or wherever your tex trees live, and looking for the file: ls */fonts/map/*/context/pdftex.map
If a file is returned, delete it (and mktexlsr again).
I deleted the pdftex.map file you mentioned, ran mktexlsr, and I still get the same effect. (I changed the font in my document from Times to Palatino, in case I was only getting a Times that had been badly generated on my first try with the map file still installed, but it now creates a bad version of Palatino as well.) David
David Rogers said this at Mon, 4 Jul 2005 09:02:56 -0700:
I deleted the pdftex.map file you mentioned, ran mktexlsr, and I still get the same effect. (I changed the font in my document from Times to Palatino, in case I was only getting a Times that had been badly generated on my first try with the map file still installed, but it now creates a bad version of Palatino as well.)
Sounds frustrating all around. I might be able to do more with a log file (send off-list, please). -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
David Rogers wrote:
I deleted the pdftex.map file you mentioned, ran mktexlsr, and I still get the same effect. (I changed the font in my document from Times to Palatino, in case I was only getting a Times that had been badly generated on my first try with the map file still installed, but it now creates a bad version of Palatino as well.)
how does your current tex file looks like? Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hi Adam, Hans... ...and all of you who are trying to help us solve (and maybe understand) the intricacies of font management! Here is what I did: on Saturday I tried to answer David Rogers' question and so typeset an example file I had, before sending him. Unfortunately everything went wrong for some reasons and so I gave up. After Adam's and Hans' suggestion right this afternoon, I uninstalled my gwTeX, as well as ConTeXt and reinstalled everything anew. I did not, and I do not have pdftex.map in */fonts/map/*/context/ and nevertheless when I tried to typeset my minimal sample file: % times-bad.tex \usetypescript [adobekb] [\defaultencoding] \usetypescript [postscript][\defaultencoding] %\setupbodyfont [postscript] % with or without this line \usetypescript[times][\defaultencoding] \setupbodyfont[times,12pt] \starttext \input knuth \stoptext on my "virgin" installation, something goes wrong and the log shows the following: [...snip...] Running mktexpk --mfmode / --bdpi 72 --mag 1+14/72 --dpi 86 ptmr8r mktexpk: Running gsftopk ptmr8r 86 gsftopk(k) version 1.19.2 Process aborted /813 [1] [2] [3] [4] [5] [6] [7] [8] [9] [11] [12] [14] [15] [16] [17] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] [41Terminated ("Terminated" because I aborted the process). I am not at all familiar with mktexpk (I even ignored its exisetnce up to now...), but the option --bpdi 72 makes me think it is building a "72 dots per inch" font which we all hate, even after magnification --mag 1+14/72... I should also say that this does not infer with math fonts which appear correctly as one may see from the PDF attachments I sent (and which went finally through the list's moderator). Thanks again for your help: OK On 4 juil. 2005, at 17:11, Adam Lindsay wrote:
Hi Otared,
What you mention sounds like a bug propagated by Hans last month. Take a look at this thread: <http://archive.contextgarden.net/thread/ 20050610.172825.65f0c37f.html#20050610.172825.65f0c37f>
(Assuming you're comfortable with the CLI, I'd suggest verifying the bad file by navigating to /usr/local/teTeX/share or wherever your tex trees live, and looking for the file: ls */fonts/map/*/context/pdftex.map
If a file is returned, delete it (and mktexlsr again).
If nothing is returned, then never mind, it's something else on your system.
One brief comment on your font selection below:
Otared Kavian said this at Mon, 4 Jul 2005 16:28:31 +0200:
\usetypescript [adobekb][\defaultencoding] \setupbodyfont[postscript] \usetypescript[times][\defaultencoding] %or helvetica, or palatino \setupbodyfont[times,12pt]
The [postscript] line in the above example is unnecessary. I'd suggest cutting it out entirely. With a properly-configured system, the three remaining lines should give you the results you expect.
adam --
Otared Kavian wrote:
% times-bad.tex \usetypescript [adobekb] [\defaultencoding] \usetypescript [postscript][\defaultencoding] %\setupbodyfont [postscript] % with or without this line \usetypescript[times][\defaultencoding] \setupbodyfont[times,12pt] \starttext \input knuth \stoptext
Does: \usetypescript [adobekb] [ec] \usetypescript [postscript][ec] \loadmapfile[ec-base.map] \usetypescript[times][\defaultencoding] \setupbodyfont[times,12pt] \starttext \input knuth \stoptext work? If so, i'll add the map file loading to the adobekb typescripts Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 4 juil. 2005, at 23:33, Hans Hagen wrote:
Does:
\usetypescript [adobekb] [ec] \usetypescript [postscript][ec]
\loadmapfile[ec-base.map]
\usetypescript[times][\defaultencoding] \setupbodyfont[times,12pt]
\starttext \input knuth \stoptext
work? If so, i'll add the map file loading to the adobekb typescripts
Hi Hans, Thanks for your help and patience with my inexperience... I tried your minimal file above on a new gwTeX + ConTeXt (ver: 2005.06.27 fmt: 2005.7.4 int: english mes: english) installation and the result is the same, that is a PDF with bitmap fonts... I am using: pdfeTeX, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) The log-file of the first run says (among other things): mktexpk: /var/tmp/texfonts/pk/modeless/adobe/times/ptmr8r.86pk: successfully generated. When I add \loadallfontmapfiles to your minimal file, or (and) when I input the file type-akb.tex you sent in another message, the resulted PDF is the same (the only thing which changes is the log-file is that those ugly bitmap fonts are not anymore generated since they are cretaed in a first typesetting). Although it is challenging to understand the problem, I can avoid using postscript fonts: so please don't spend much time on the issue... Best regards: OK
Hans Hagen wrote:
Does:
\usetypescript [adobekb] [ec] \usetypescript [postscript][ec]
\loadmapfile[ec-base.map]
\usetypescript[times][\defaultencoding] \setupbodyfont[times,12pt]
\starttext \input knuth \stoptext
work? If so, i'll add the map file loading to the adobekb typescripts
No, it's not. But replacing ec-base with context-base solves the
problem. I don't know why. Relevant lines in these files identical.
Using 8r encoding also helps, but texnansi gives same result as ec.
--
Radhelorn
Otared Kavian wrote:
It is right that handling fonts is extremely disappointing and instable... For instance, what used to work does not work anymore properly with the new version of ConTeXt I installed two weeks ago...
much of this has nothing to do with context but with - switching from cm to lm (context has done this switch, latex will do that later) - changes in the tds structure (hard to cope with automatically) - changes in map files etc (there will be some more but in the end that mess will be cleaned up so that we don;t have differences in backends any more)
For instance:
\usetypescript [adobekb][\defaultencoding]
this maps kb names and should work if they are present (only when your encoding is ec!)
\setupbodyfont[postscript] \usetypescript[times][\defaultencoding] %or helvetica, or palatino \setupbodyfont[times,12pt]
nothing has changed here
used to work fine, but now it results in ConTeXt creating, the first time, a whole bunch of things regarding fonts, and then the resulting PDF contains some ugly jagging bitmap-looking characters (interestingly this happens only to the text characters, not to the math characters...).
behaviour also depends on your local cont-sys.tex; what happens if you remove that file (or rename it)? it seems that you have a map file problem
Adding \usetypescript[postscript] does not help neither.
Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Hans Hagen wrote:
Otared Kavian wrote:
used to work fine, but now it results in ConTeXt creating, the first time, a whole bunch of things regarding fonts, and then the resulting PDF contains some ugly jagging bitmap-looking characters (interestingly this happens only to the text characters, not to the math characters...).
behaviour also depends on your local cont-sys.tex; what happens if you remove that file (or rename it)?
I don't have a cont-sys.tex anywhere, only cont-sys.ori and cont-sys.rme (two of each). Is this relevant? David
David Rogers wrote:
Hans Hagen wrote:
Otared Kavian wrote:
used to work fine, but now it results in ConTeXt creating, the first time, a whole bunch of things regarding fonts, and then the resulting PDF contains some ugly jagging bitmap-looking characters (interestingly this happens only to the text characters, not to the math characters...).
behaviour also depends on your local cont-sys.tex; what happens if you remove that file (or rename it)?
I don't have a cont-sys.tex anywhere, only cont-sys.ori and cont-sys.rme (two of each). Is this relevant?
i that case things should work, so i'm puzzled; maybe some map files are not on your system? what happens if you say (after loading the typescripts): \loadallfontmapfiles (i'll add some more map sync points) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (5)
-
Adam Lindsay -
David Rogers -
Hans Hagen -
Otared Kavian -
Radhelorn