Dear Craig,
I experienced this same issue as my company's product reads in *alot* of
XML content, and one of the customers panics whenever they see _any_
FrameMaker 'console' messages.
The mapping appears to be made in an entity formats document:
"C:\Program Files\Adobe\AdobeFrameMaker10\Structure\entfmts"
which has a rather historic comment that "FrameMaker+SGML copies
character formats and user variables from this file while importing
SDATA entities from SGML documents".
This isn't the first occurrence of where Adobe ships files that
reference fonts that are no longer supplied, and probably won't be the last.
// Simon BUCH
On 18/01/2013 15:24, Craig Ede wrote:
> Dov,
>
> I didn't initiate this conversation, but I'd like to chime in.
>
> Your points are well taken, but a problem I had with the Adobe PI
> substitution was that simple bullets were coming across as question marks in
> my PDFs. That would indicate a mapping problem that is pretty obvious.
>
> Also, you might want to tell the Framemaker team that whenever I open a new
> DITA document in FrameMaker I get the following messages in the FrameMaker
> console:
>
> The "Zapfdingbats" Font Family is not available.
> "Adobe Pi Std" will be used in this session.
> The "Zapfdingbats Regular" Font is not available.
> "AdobePiStd" will be used in this session.
>
> If Adobe Pi Std is not a problem, maybe they should update the DITA templates
> for the next release and remove the source of this error. That is, unless
> Zapf-Dingbats is somehow part of the DITA standard (which really can't be
> true). The fewer the error messages the more likely we are to see critical
> errors.
>
> Thanks for all your insights.
>
> Craig
