sebschub / FontPro

LaTeX support for Adobe's Pro opentype fonts: Minion Pro, Myriad Pro, Cronos Pro and possibly more
225 stars 42 forks source link

Thanks, questions, and suggestions #65

Open misterBart opened 5 years ago

misterBart commented 5 years ago

I thank you for providing FontPro, which helped me install Minion Pro and Myriad Pro. Still, a few questions and a few suggestions for improvement.

Questions: (Q1) How can I use the semibold every now and then and the usual bold for the rest? The option medfamily or fullfamily overrides the usual bold, which I find undesirable (and from the posts on stackexchange I seem not to be the only one). It would be more user-friendly that the conventional boldface always remains the standard and the semibold becomes selectable.

(Q2) Without 'expanded' option for 'makeall', is Microtype's expansions still working for pdf and not of lesser quality? I found the README not 100% clear about this.

(Q3) The output of the MyriadPro installation started with: "Different font versions found: --pack option is disabled" My otf fonts (taken from my Adobe Creative Suite CS4): Myriad CAD Regular: 1.023;PS 1.000;hotconv 1.0.57;makeotf.lib2.0.21895 Myriad Currency Regular: 1.006;PS 3.000;hotconv 1.0.67;makeotf.lib2.5.33168 Myriad Pro Regular and others: 2.037;PS 2.000;hotconv 1.0.51;makeotf.lib2.0.18671 I did not saw a message of FontPro processing Myriad CAD Regular and Myriad Currency Regular. All the others were processed. MyriadPro-BoldCond did give the warning: cfftot1: glyph 'ohorn': warning: complex flex hint replaced with curves cfftot1: (This font contains flex hints prohibited by Type 1. They've been cfftot1: replaced by ordinary curves.) Still, the MinionPro also gave similar warnings of the kind above, so I am not really worried about the warning. How to proceed best with these fonts in a future installation?

(Q4) The output of the MyriadPro installation gave me the impression MyriadPro uses MnSymbol. Wouldn't it make more sense MyriadPro uses MdSymbol?

(Q5) I receive the following Microtype warnings (see my Microtype settings at the bottom of this email): Package microtype Warning: I cannot find a protrusion list for font (microtype) OML/MinionPro-TOsF/m/it/12'. Switching off (microtype) protrusion for this font on input line 59. Package microtype Warning: I cannot find a protrusion list for font (microtype)OML/MinionPro-TOsF/m/it/8'. Switching off (microtype) protrusion for this font on input line 59. Package microtype Warning: I cannot find a protrusion list for font (microtype) `OML/MinionPro-TOsF/m/it/6'. Switching off (microtype) protrusion for this font on input line 59. Can this be fixed by me? Or by you? Or is this the responsibility of the microtype maintainer?

Suggestions: (S1) Update README: root priviliges -> root or superuser priviliges. Superusers should precede './scripts/install' and 'updmap-sys' commands with 'sudo'

(S2) Make it easier: Already have an empty 'otf' folder for the user, instead of asking the user to create such a folder.

(S3) Output of installations of MinionPro and MyriadPro: Warning: missing glyph hookrightchar'. Warning: missing glyphhookleftchar'. Perhaps this can be fixed? Still, I cannot recall I ever used these glyphs, so don't go through much trouble to fix this.

My Microtype settings: \usepackage[final,step=1,tracking,spacing]{microtype} \microtypecontext{spacing=nonfrench} %Ensures Microtype's interword spacing remains enabled when other packages change the interword spacing \DeclareMicrotypeSet{allmathT1}{ encoding = {T1,TS1,OML,OMS} } \DeclareMicrotypeSet{basicmathT1} { encoding = {T1,OML,OMS}, family = {rm,sf}, series = {md}, size = {normalsize,footnotesize,small,large} } \DeclareMicrotypeSet{basictextT1} { encoding = {T1}, family = {rm,sf}, series = {md}, size = {normalsize,footnotesize,small,large} } \DeclareMicrotypeSet{smallcapsT1} { encoding = {T1,TS1}, shape = {sc*,si,scit} } \UseMicrotypeSet[protrusion]{allmathT1} \UseMicrotypeSet[expansion]{basicmathT1} \UseMicrotypeSet[tracking]{smallcapsT1} \UseMicrotypeSet[spacing]{basicmathT1}

misterBart commented 4 years ago

Anybody?

rien333 commented 4 years ago

How did you get semibold MyriadPro to work? If I try to load the semibold variant in a pdflatex file, like so:

\usepackage[medfamily]{MyriadPro}
\begin{document}
    \textbf{hello world!}
\end{document}

The competition fails with:

$ pdflatex mwe.tex
...
kpathsea: Running mktextfm MyriadPro-Semibold-osf-ot1
/usr/share/texmf-dist/web2c/mktexnam: Could not map sou
rce abbreviation M for MyriadPro-Semibold-osf-ot1.
/usr/share/texmf-dist/web2c/mktexnam: Need to update /usr/share/texmf-dist/fonts/map/fontname/specia>
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input MyriadPro-Semibold>
This is METAFONT, Version 2.7182818 (TeX Live 2019/Arch Linux) (preloaded base=mf)

kpathsea: Running mktexmf MyriadPro-Semibold-osf-ot1
! I can't find file `MyriadPro-Semibold-osf-ot1'.
<*> ...nstopmode; input MyriadPro-Semibold-osf-ot1

Indeed, this mktexmf MyriadPro-Semibold-osf-ot1 file is nowhere to be found. @sebschub, any idea why this semibold variant is not generated? Or do I absolutely have to use xelatex/luatex in order to use semibold variants?

misterBart commented 4 years ago

I have not tested semibold with Myriad Pro, but with Minion Pro I proceed as the pdf manual states: use the package option 'medfamily' or 'fullfamily'.

Perhaps you do not have a separate semibold font file? During installation you have to provide a separate semibold font file. In addition, the README states the font file needs to follow a naming scheme structure, i.e. MyriadPro-Semibold.otf

My experience with semibold Minion Pro is that is not clear enough. You sometimes read over it without noticing it was slightly thicker than the rest.

misterBart commented 4 years ago

For those who stumble upon this thread. Solved (Q3) by not putting the Currency and CAD variant of the font file in the otf/ folder.