FC_WEIGHT didn't match

[jfbu]

Hi Bob,

Le 5 mars 2019 à 15:09, Bob Tennent <rdtennent at gmail.com> a écrit :

>> |Processing the following MWE
>> |
>> |\documentclass{minimal}
>> |\usepackage{mathpazo}
>> |\begin{document}
>> |foo
>> |\end{document}
>> |
>> |using a traditional latex -> dvips -> ps2pdf chain, I'm getting
>> |
>> |DEBUG: FC_WEIGHT didn't match
>> |
>> |from ps2pdf. This is on a linux system with the TL2019
>> |pretest. I believe dvips is the culprit because I get the
>> |same message on another system from the ps file, but not
>> |vice versa.  I've not seen that error message before.
>> |What does it mean?
> 
> The problem seems to have been the
> 
> download standard fonts (dvips)
> 
> configuration in updmap.cfg. The ps file was referencing
> Palatino-Roman rather than URWPalladioL-Roma.
> 

I get this at end of ps file

 515 440 a 1348 1857 a @beginspecial @setspecial
  tx at Dict begin STP newpath 0.8 SLW 0  setgray   gsave /xGridOffset
0.0 def /yGridOffset 0.0 def  1. .setopacityalpha  0.4 SLW 0  setgray
-85.35823 -142.26372 85.35823 142.26372 -85.35823 -142.26372 28.45274
abs 28.45274 abs 1 0 { 0  setgray } 0.0 /NimbusSanL-Regu findfont 0.0
scalefont setfont Grid grestore  end


@endspecial 0 TeXcolorgray 0 TeXcolorgray eop end
%%Trailer

userdict /end-hook known{end-hook}if
%%EOF


which involves a reference to NimbusSansL-Regu

with my pst-plot example

Jean-François