RE: The Zapfdingbats Font Family is not available. (Was: Updating older versions of Adobe fonts? Slightly off-topic, but related in a way!)

2013-01-23 Thread Dov Isaacs 
To be very clear, Adobe has not shipped a copy of Zapf Dingbats with FrameMaker 
since FrameMaker 5.5.6 if I recall correctly.

However, in fact, every printer with Adobe PostScript 3 still ships with a 
host-installable Type 1 (both for Windows and Macintosh) versions of Zapf 
Dingbats.

The real issue appears to be not whether Adobe ships this font under what 
circumstances, but rather, whether the users install the font (assuming they 
have use of an Adobe PostScript 3 device) and a likely bug/omission in 
FrameMaker by which a font substitution is made without making a character 
remapping to Unicode at the same time.

- Dov

[cid:image001.png@01CDF919.2249C150]

Dov Isaacs
Principal Scientist
Adobe Systems Incorporated

+1 408.536.2896 (tel)
+1 408.242.5161 (cell)
isa...@adobe.commailto:isa...@adobe.com

345 Park Avenue
San Jose, CA  95110-2704 USA
http://www.adobe.comhttp://www.adobe.com/






Feel free to print this e-mail if your needs dictate hard copy.
There is no need to feel guilty about printing!
Paper is renewable and recyclable.

ISAACS-MOBILE.corp.adobe.com



From: framers-boun...@lists.frameusers.com 
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of Simon BUCH
Sent: Monday, January 21, 2013 1:16 AM
To: Craig Ede
Cc: framers
Subject: The Zapfdingbats Font Family is not available. (Was: Updating older 
versions of Adobe fonts? Slightly off-topic, but related in a way!)


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
inline: image001.png___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

RE: The Zapfdingbats Font Family is not available. (Was: Updating older versions of Adobe fonts? Slightly off-topic, but related in a way!)

2013-01-23 Thread Dov Isaacs 
Make no such assumptions. Assume that for correct output you need the actual 
font on your editing system!

- Dov


[cid:image001.png@01CDF936.14256E40]

Dov Isaacs
Principal Scientist
Adobe Systems Incorporated

+1 408.536.2896 (tel)
+1 408.242.5161 (cell)
isa...@adobe.commailto:isa...@adobe.com

345 Park Avenue
San Jose, CA  95110-2704 USA
http://www.adobe.comhttp://www.adobe.com/






Feel free to print this e-mail if your needs dictate hard copy.
There is no need to feel guilty about printing!
Paper is renewable and recyclable.

ISAACS-MOBILE.corp.adobe.com



From: Craig Ede [mailto:craig...@hotmail.com]
Sent: Wednesday, January 23, 2013 6:37 AM
To: Dov Isaacs; framers
Subject: RE: The Zapfdingbats Font Family is not available. (Was: Updating 
older versions of Adobe fonts? Slightly off-topic, but related in a way!)

Thanks for this clarification Dov. This simplifies things a great deal in that 
it implies that for any PS or PDF file that is destined to be sent to a high 
quality printing service bureau one can assume that allowing temporary font 
substitution in FM will not cause problems with final output having the correct 
font (since their devices will have Zapf-Dingbats installed).

Or is that too optimistic a reading? Must the PS or PDF file be produced with 
that font available to FM on the machine producing the PS of PDF file?

Craig


From: isa...@adobe.commailto:isa...@adobe.com
To: framers@lists.frameusers.commailto:framers@lists.frameusers.com
Date: Wed, 23 Jan 2013 03:24:20 -0800
Subject: RE: The Zapfdingbats Font Family is not available. (Was: Updating 
older versions of Adobe fonts? Slightly off-topic, but related in a way!)
To be very clear, Adobe has not shipped a copy of Zapf Dingbats with FrameMaker 
since FrameMaker 5.5.6 if I recall correctly.

However, in fact, every printer with Adobe PostScript 3 still ships with a 
host-installable Type 1 (both for Windows and Macintosh) versions of Zapf 
Dingbats.

The real issue appears to be not whether Adobe ships this font under what 
circumstances, but rather, whether the users install the font (assuming they 
have use of an Adobe PostScript 3 device) and a likely bug/omission in 
FrameMaker by which a font substitution is made without making a character 
remapping to Unicode at the same time.

- Dov

inline: image001.png___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

RE: The Zapfdingbats Font Family is not available. (Was: Updating older versions of Adobe fonts? Slightly off-topic, but related in a way!)

2013-01-23 Thread Craig Ede 

Thanks for this clarification Dov. This simplifies things a great deal in that 
it implies that for any PS or PDF file that is destined to be sent to a high 
quality printing service bureau one can assume that allowing temporary font 
substitution in FM will not cause problems with final output having the correct 
font (since their devices will have Zapf-Dingbats installed). Or is that too 
optimistic a reading? Must the PS or PDF file be produced with that font 
available to FM on the machine producing the PS of PDF file? Craig
 From: isa...@adobe.com
To: framers@lists.frameusers.com
Date: Wed, 23 Jan 2013 03:24:20 -0800
Subject: RE: The Zapfdingbats Font Family is not available. (Was: Updating
older   versions of Adobe fonts? Slightly off-topic,but related in a way!)

To be very clear, Adobe has not shipped a copy of Zapf Dingbats with FrameMaker 
since FrameMaker 5.5.6 if I recall correctly. However, in fact, every printer 
with Adobe PostScript 3 still ships with a host-installable Type 1 (both for 
Windows and Macintosh) versions of Zapf Dingbats. The real issue appears to be 
not whether Adobe ships this font under what circumstances, but rather, whether 
the users install the font (assuming they have use of an Adobe PostScript 3 
device) and a likely bug/omission in FrameMaker by which a font substitution is 
made without making a character remapping to Unicode at the same time.  
   - Dovattachment: image001.png___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

The "Zapfdingbats" Font Family is not available. (Was: Updating older versions of Adobe fonts? Slightly off-topic, but related in a way!)

2013-01-23 Thread Dov Isaacs 
To be very clear, Adobe has not shipped a copy of Zapf Dingbats with FrameMaker 
since FrameMaker 5.5.6 if I recall correctly.

However, in fact, every printer with Adobe PostScript 3 still ships with a 
host-installable Type 1 (both for Windows and Macintosh) versions of Zapf 
Dingbats.

The real issue appears to be not whether Adobe ships this font under what 
circumstances, but rather, whether the users install the font (assuming they 
have use of an Adobe PostScript 3 device) and a likely bug/omission in 
FrameMaker by which a font substitution is made without making a character 
remapping to Unicode at the same time.

- Dov

[cid:image001.png at 01CDF919.2249C150]

Dov Isaacs
Principal Scientist
Adobe Systems Incorporated

+1 408.536.2896 (tel)
+1 408.242.5161 (cell)
isaacs at adobe.com

345 Park Avenue
San Jose, CA  95110-2704 USA
http://www.adobe.com






Feel free to print this e-mail if your needs dictate hard copy.
There is no need to feel guilty about printing!
Paper is renewable and recyclable.

ISAACS-MOBILE.corp.adobe.com



From: framers-bounces at lists.frameusers.com 
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of Simon BUCH
Sent: Monday, January 21, 2013 1:16 AM
To: Craig Ede
Cc: framers
Subject: The "Zapfdingbats" Font Family is not available. (Was: Updating older 
versions of Adobe fonts? Slightly off-topic, but related in a way!)


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
-- next part --
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 871 bytes
Desc: image001.png
URL:

The "Zapfdingbats" Font Family is not available. (Was: Updating older versions of Adobe fonts? Slightly off-topic, but related in a way!)

2013-01-23 Thread Dov Isaacs 
Make no such assumptions. Assume that for correct output you need the actual 
font on your editing system!

- Dov


[cid:image001.png at 01CDF936.14256E40]

Dov Isaacs
Principal Scientist
Adobe Systems Incorporated

+1 408.536.2896 (tel)
+1 408.242.5161 (cell)
isaacs at adobe.com

345 Park Avenue
San Jose, CA  95110-2704 USA
http://www.adobe.com






Feel free to print this e-mail if your needs dictate hard copy.
There is no need to feel guilty about printing!
Paper is renewable and recyclable.

ISAACS-MOBILE.corp.adobe.com



From: Craig Ede [mailto:craig...@hotmail.com]
Sent: Wednesday, January 23, 2013 6:37 AM
To: Dov Isaacs; framers
Subject: RE: The "Zapfdingbats" Font Family is not available. (Was: Updating 
older versions of Adobe fonts? Slightly off-topic, but related in a way!)

Thanks for this clarification Dov. This simplifies things a great deal in that 
it implies that for any PS or PDF file that is destined to be sent to a high 
quality printing service bureau one can assume that allowing temporary font 
substitution in FM will not cause problems with final output having the correct 
font (since their devices will have Zapf-Dingbats installed).

Or is that too optimistic a reading? Must the PS or PDF file be produced with 
that font available to FM on the machine producing the PS of PDF file?

Craig


From: isaacs at adobe.com
To: framers at lists.frameusers.com
Date: Wed, 23 Jan 2013 03:24:20 -0800
Subject: RE: The "Zapfdingbats" Font Family is not available. (Was: Updating 
older versions of Adobe fonts? Slightly off-topic, but related in a way!)
To be very clear, Adobe has not shipped a copy of Zapf Dingbats with FrameMaker 
since FrameMaker 5.5.6 if I recall correctly.

However, in fact, every printer with Adobe PostScript 3 still ships with a 
host-installable Type 1 (both for Windows and Macintosh) versions of Zapf 
Dingbats.

The real issue appears to be not whether Adobe ships this font under what 
circumstances, but rather, whether the users install the font (assuming they 
have use of an Adobe PostScript 3 device) and a likely bug/omission in 
FrameMaker by which a font substitution is made without making a character 
remapping to Unicode at the same time.

- Dov

-- next part --
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 871 bytes
Desc: image001.png
URL:

The "Zapfdingbats" Font Family is not available. (Was: Updating older versions of Adobe fonts? Slightly off-topic, but related in a way!)

2013-01-23 Thread Craig Ede 

Thanks for this clarification Dov. This simplifies things a great deal in that 
it implies that for any PS or PDF file that is destined to be sent to a high 
quality printing service bureau one can assume that allowing temporary font 
substitution in FM will not cause problems with final output having the correct 
font (since their devices will have Zapf-Dingbats installed). Or is that too 
optimistic a reading? Must the PS or PDF file be produced with that font 
available to FM on the machine producing the PS of PDF file? Craig
 From: isaacs at adobe.com
To: framers at lists.frameusers.com
Date: Wed, 23 Jan 2013 03:24:20 -0800
Subject: RE: The "Zapfdingbats" Font Family is not available. (Was: Updating
older   versions of Adobe fonts? Slightly off-topic,but related in a way!)

To be very clear, Adobe has not shipped a copy of Zapf Dingbats with FrameMaker 
since FrameMaker 5.5.6 if I recall correctly. However, in fact, every printer 
with Adobe PostScript 3 still ships with a host-installable Type 1 (both for 
Windows and Macintosh) versions of Zapf Dingbats. The real issue appears to be 
not whether Adobe ships this font under what circumstances, but rather, whether 
the users install the font (assuming they have use of an Adobe PostScript 3 
device) and a likely bug/omission in FrameMaker by which a font substitution is 
made without making a character remapping to Unicode at the same time.  
   - Dov
-- next part --
An HTML attachment was scrubbed...
URL: 

-- next part --
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 871 bytes
Desc: not available
URL:

The Zapfdingbats Font Family is not available. (Was: Updating older versions of Adobe fonts? Slightly off-topic, but related in a way!)

2013-01-21 Thread Simon BUCH 

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


___


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscr...@lists.frameusers.com
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

The "Zapfdingbats" Font Family is not available. (Was: Updating older versions of Adobe fonts? Slightly off-topic, but related in a way!)

2013-01-21 Thread Simon BUCH 
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