You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
First of all thanks for maintaining this useful package! I had been searching for some time for a way to use MinionPro with pdflatex and microtype and your package is the only working solution.
I was just wondering if you could help me out with understanding this warning, its relevance / importance:
Package microtype Warning: Unknown slot number of character
(microtype) `\j '
(microtype) in font encoding `T1' in inheritance list
(microtype) `microtype.cfg/263(protrusion)'.
but the warnings are still produced. Also, contrary to what the stackexchange answer states, putting MinionPro before or after microtype makes no difference.
Thanks for any help and/or explanations you could provide.
Best regards,
Mark.
The text was updated successfully, but these errors were encountered:
Hi there,
First of all thanks for maintaining this useful package! I had been searching for some time for a way to use MinionPro with pdflatex and microtype and your package is the only working solution.
I was just wondering if you could help me out with understanding this warning, its relevance / importance:
Searching around the code and old issues, I noted that MinionPro apparently doesn't provide the "dotless j" (latex
\j
) and this discussion (which is old and you already commented on): https://tex.stackexchange.com/questions/220777/minionpro-microtype-and-j-is-there-a-way-to-get-rid-of-a-strange-warning/222471#222471 explains this should be fixed by setting a\DeclareCharacterInheritance
inmt-MinionPro.cfg
that does not include\j
.Well, I happen to have just such a thing in my setup:
but the warnings are still produced. Also, contrary to what the stackexchange answer states, putting MinionPro before or after microtype makes no difference.
Thanks for any help and/or explanations you could provide.
Best regards,
Mark.
The text was updated successfully, but these errors were encountered: