[lucida] No output after installing Lucida Type 1

[Bruno Voisin]

> Le 14 févr. 2019 à 03:30, Pedro A. Marrone G. <pmarroneg at gmail.com> a écrit :
> 
> C:\Users\PedroAntonio>updmap-sys --listmaps
> updmap will read the following updmap.cfg files (in precedence order):
>   d:/texlive/2017/texmf-config/web2c/updmap.cfg
>   d:/texlive/2017/texmf-dist/web2c/updmap.cfg
> updmap may write changes to the following updmap.cfg file:
>   d:/texlive/2017/texmf-config/web2c/updmap.cfg
> [...]
> Map     lucida.map      enabled d:/texlive/2017/texmf-config/web2c/updmap.cfg

OK, something's odd here: according to the above output, lucida.map is enabled, but on the other hand, according to your preceding message, your run of

updmap-sys --force --enable Map=lucida.map

failed, because two map files (foo.map and newfont.map) weren't found.

Could you:


1) Look at the files

d:/texlive/2017/texmf-var/fonts/map/dvips/updmap/psfonts.map
d:/texlive/2017/texmf-var/fonts/map/pdftex/updmap/pdftex.map

and see whether you find there the content of lucida.map, which should start with the lines

% lucida.map
hlcbot8r LucidaTypewriterBoldOblique " TeXBase1Encoding ReEncodeFont " <8r.enc <lbtbo.pfb
hlcbot8y LucidaTypewriterBoldOblique " TeXnANSIEncoding ReEncodeFont " <texnansi.enc <lbtbo.pfb

These are the files telling dvips and pdftex which font files to use.


2) Run

updmap-sys --force --syncwithtrees --enable Map=lucida.map

so that not finding foo.map and newfont.map won't prevent updmap-sys from proceeding.


3) Copy /texlive/texmf-local/doc/fonts/lucidabr/lucida-sample.tex to a writable location (for example your desktop), run pdflatex on it, post there (as an attachment) the resulting file lucida-sample.log.


A final possibility I can think of is that you have a user-specific updmap setup, that may take over any system-wide change you would make using updmap-sys. You can check that by running

kpsewhich --var-value TEXMFVAR
kpsewhich --var-value TEXMFCONFIG

and looking inside these directories for alternative files updmap.cfg, psfonts.map and pdftex.map.

If so, then this means you have user-specific files, created and managed by updmap, taking over the system-wide files managed by updmap-sys. That's a known problem, that has created headaches for years.

In that event, you can simply delete the user-specific texlive tree and rerun updmap-sys afterwards. This will also remove the LuaTeX font databases should you have some, but they are recreated on-the-fly when needed.

I'm not sure where this tree lives on Windows. On the Mac it's

/Users/<username>/Library/texlive/2018

Running kpsewhich as above will reveal where it is. This could be something like

/Users/<username>/.texlive/2017

in your case. The "." at the start of the name may make the directory invisible, you may have to make all files and directories visible in the Windows Configuration Panel first (I don't remember exactly where and how this is done).

Hope this works,

Bruno Voisin