A simple question:
I have this minimal working example where I use amsart with esint:
\documentclass[11pt,oneside]{amsart}
\usepackage{mathtools}
\usepackage{esint}
\begin{document}
\[\varointctrclockwise\limits_{\text{loop}}\vec{B}\cdot d\vec{l}=0\]
\end{document}
but the result is a bad resolution with pixels making the zoom of TeXworks and directly with the pdf.
Is there a conflict with amsart and esint package? If I use this MWE
\documentclass[11pt,oneside]{amsart}
\usepackage{mathtools}
\usepackage{amssymb}
\begin{document}
\[\oint_{\text{loop}}\vec{B}\cdot d\vec{l}=0\]
\end{document}
I have not problem.
EDIT: I have seen that into my MikTeX distribuition I have these esint packages:
I think that I have the contents of this package https://ctan.org/tex-archive/fonts/ps-type1/esint (see previous image). What is the exact link where must I take these postscript fonts esint? Here or where are they exactly?
Related: my procedure to install new fonts
Latest MiKTeX: suggestions on how to install new fonts using the MiKTeX Console





esintfonts have not been installed. See https://tex.stackexchange.com/q/473015/4427 – egreg Apr 15 '20 at 21:50Output written on. Among others, I have</usr/share/texlive/texmf-dist/fonts/type1/public/esint-type1/esint10.pfb>and there is no pixellation. PFB is a file format for vector fonts (PostScript). – frougon Apr 15 '20 at 21:55<C:\Users\utente\AppData\Local\MiKTeX\2.9\fonts/pk/ljfour/public/esint/dpi657 \esint10.pk><C:/Program Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmmi10. pfb><C:/Program Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmr10.pfb><C:/P rogram Files/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmr8.pfb><C:/Program Fil es/MiKTeX 2.9/fonts/type1/public/amsfonts/cm/cmsy10.pfb> Output written on p.pdf (1 page, 34141 bytes). SyncTeX written on p.synctex.gz. Transcript written on p.log.– Sebastiano Apr 15 '20 at 22:06dpi657 \esint10.pk. The problem exist. – Sebastiano Apr 15 '20 at 22:07esint10.pkis your culprit. PK fonts are bitmap fonts, typically generated from MetaFont sources. You probably have a problem of font map configuration: what tells the driver how a font for TeX-the-engine should become in the output (PDF probably here). – frougon Apr 15 '20 at 22:08amsart. Please remove that tag. – barbara beeton Apr 15 '20 at 22:09psfonts.mapand look for a line containingesint10... which probably won't be there until you've solved the problem. – frougon Apr 15 '20 at 22:13psfonts.map, verifyesint10isn't mentioned there and then try to reinstall theesintpackage looking very carefully at all the log output you can have for this operation in order to make sure you don't miss any problem when MiKTeX tries to update its map file (which I believe it should do in such a case)? – frougon Apr 15 '20 at 22:20initexmf --mkmapswill help, or you need someone who knows MiKTeX better than me... Plus, the tool has a--adminmode, and I'm not sure if you should use it here. You can runinitexmf --admin --update-fndbbefore, I think it can only help. – frougon Apr 15 '20 at 22:33--adminshould be used are given here. “Using this option requires a shared MiKTeX setup, i.e., MiKTeX must have been set up for all users.” So, it depends on how you manage your MiKTeX installation. – frougon Apr 15 '20 at 22:41.mapfiles. When installed, this or these map files get incorporated (with possible massaging to account for differences between formats) into a big one that has the info for all vector fonts of your installation (e.g., psfonts.map, pdftex.map, etc.). This is what “updating the font map/map files“ means. – frougon Apr 15 '20 at 23:13