Cronos Pro Opticals new version: 2.112

[ctwelve]

Hello,

Just acquired the latest Cronos Pro Opticals set from Adobe. Love the font, but FontPro had me generate a new encoding map. I've transmitted the new map to your email address.

There does seem to be an interesting definition issue, however: if I load MinionPro before CronosPro, I get this:

If I merely switch the loading order around:

[sebschub]

Thanks for providing the glyph list.
Could you please provide a complete minimal example? I cannot reproduce the behaviour with \slantfrac.

[ctwelve]

Sure thing!

\documentclass{scrartcl}

\title{A Simple Demonstration}
\author{Zaphod Beeblebrox}

% Functions correctly
\usepackage{CronosPro}
\usepackage{MinionPro}

% Does not function
%\usepackage{MinionPro}
%\usepackage{CronosPro}

\usepackage{lipsum}
\usepackage[american,latin]{babel}
\usepackage[kerning,spacing,tracking]{microtype}

\begin{document}

% For fun!
\maketitle
\tableofcontents

\section{Fraction Testing}

This is a fraction of \slantfrac{7}{9}-th size! Also for comparison:

This is a \textonehalf\ fraction using \texttt{\textbackslash{}textonehalf} coding.

This is a \slantfrac{1}{2}\ fraction using \texttt{\textbackslash{}slantfrac\{1\}\{2\}} coding.

\section{Latin Explosion}
\lipsum

\subsection{Even Moar!}
\lipsum

\section{Revenge of Latin}
\lipsum

\subsection{And the Bad Sequel}
\lipsum

\end{document}

Also note I tested this on the following:

• A freshly rebuilt Mac running both Mavericks and Yosemite,
• A fresh, freshly-patched version of Mac TeX,
• Cleanly rebuilt fonts using the latest FontPro (within last few days),
• Built using pdfLaTeX and microtype package.

Here are the results:

Anyways, the above example will faithfully recreate the issue for me, every time.

Edits: many, because I am having several derp-moments back-to-back.

[sebschub]

Thanks, while I cannot reproduce your ugly results, mine are also not correct:

The Cronos package should not overwrite \slantfrac and apparently the spacing is also not nice... At least my problem shouldn't be too hard to fix. Anyway, I'll investigate.

[ctwelve]

With luck they may be the same problem. Who knows?