Re: ascii package with Miktex (Ulrike Fischer)
Ulrike Fischer <[email protected]>
| Newsgroups | gmane.comp.tex.miktex |
|---|---|
| Message-ID | <[email protected]> |
Am Tue, 28 Jun 2011 21:27:19 +0200 schrieb Halland, Kenneth: > I can see that there is a problem with the creation/reading of the > ascii.map file. Maybe i have placed it (the one i downloaded) in > the wrong directory? Well you put it in <????>Miktex 2.8\fonts\map\ascii\ I guess this is the main root of miktex Comments: 1. You actually shouldn't put manually files in the main root. There is always the danger that they get lost at updates. Better use a local root. That means - create somewhere (outside miktex) a folder e.g. Kenneth_texmf. - Then put the files in this folder. Eg. the tfm in Kenneth_texmf\fonts\tfm\ascii. - Then add Kenneth_texmf as a new root in miktex settings. 2. If you put files in main root of miktex you must update the FNDB in admin mode. 3. I don't know if fonts\map\ascii works, I think yes but you can also try fonts\map\dvips\ascii. (Don't forget to to update the FNDB at best run "initexmf -u" *and* "initexmf --admin -u". As you now have run updmap (= initexmf --mkmaps) in user mode once you should always do it. The local map files will from now on take precedence. If still don't work after you moved the map, recreated the FNDB and rerun updmap, sent me the log-files of the pdflatex run and of updmap.log per mail along with a list of the *exact* pathes of ascii.map and the updmap.cfg where you added the "Map ascii.map" entry. -- Ulrike Fischer ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2