Hi Brenda, 

as far as I can see you mentioned all relevant parts that lead to a
specific formatting in a XML workflow.
Pls also check the r/w-rules, there may be (older, non-Unicode)
definitions expecially directing the output for symbol fonts. 

Now, if you had a "clean" workflow - EDD and template - the font
information would correctly be Courier new or ITC Dingbats. 

The notification shows that Courier/ZapfDingbats are still "somewhere"
and will come up every time you convert an XML file to a Frame file.
This information is not part of the XML file, so it must still be in
your template: What happens if you open it? You may convert the template
to "mif" and check if the fonts are still defined (open it with a text
editor). As the template and therefore the "mif" file also contains all
EDD definitions, this should make clear where the problem is. 

Concerning the ZapfDingbats font: Probably the template has been
reworked with a FrameMaker where the entry in the maker.ini was NOT
present... 

Now, if you change e.g. this one entry in the maker.ini to: 

Zapfdingbats, *,*= ITC Zapf Dingbats Std,*,* 

as you mentioned, this may help for the Frame publications you produce,
but you would still get this message every time, which is quite
annoying. 

So it is better to find out about the template... 

There are 3 main issues here: 
(1) If you changed the EDD, it must be re-imported into the template.
(2) A change in the FrameMaker formats must always be done via the
"update all" command, otherwise the definition will not really be
affected.
(3) There may be formats on the master pages (that are not in the format
list) or formattings defined in the EDD eg. for prefixes or suffixes
that are not easily found. A text search in the mif file should show
everything. 

Btw, as far I can see, all characters in ZapfDingbats are on ANSI
positions whereas in the ITC font all relevant characters are on their
Unicode positions - maybe this will not work as expected if you only
change the font but not the character encoding information (eg. via
r/w-rules). 

Best regards - 

Tino H. Haida, Berlin 

George, Brenda (CAI): 

> My office recently upgraded to FrameMaker 11 in a Windows 7 environment. We 
> previously used FrameMaker 8 | Windows XP. 
> 
> We are in the process of replacing the following fonts: 
> 
> Courier 
> 
> Zapf Dingbats 
> 
> With the following: 
> 
> Courier New 
> 
> ITC Zapf Dingbats Std Medium 
> 
> I am having problems with Zapf Dingbats being replaced with ITC Zapf Dingbats 
> Std Medium. I have used the FrameMaker 11 fonts pod to update these fonts for 
> all of the appropriate FrameMaker files. 
> 
> We use an automated process to create the FrameMaker files. The process 
> involves importing XML feeds into Structured FrameMaker 11 using an automated 
> process. After the XML has been imported, it is fully formatted in FrameMaker 
> 11. After I select the xml file to import and the automated process is about 
> to import the xml file into FrameMaker 11, the FrameMaker console is 
> displaying this message: 
> 
> The "Zapfdingbats" font is not available. 
> 
> It will be replaced by "AdobePiStd". 
> 
> The "Zapfdingbats" font is not available. 
> 
> It will be replaced by "AdobePiStd". 
> 
> The "Courier" font is not available. 
> 
> It will be replaced by "Courier New". 
> 
> When I view the fonts in this newly created FrameMaker 11 file in the font 
> pod, the "AdobePiStd" font is displayed as part of the fonts in this file. I 
> did update the Zapf Dingbats occurrences in the FrameMaker template to ITC 
> Zapf Dingbats Std Medium and I updated all of the other systems files as 
> well. I did update the FrameMaker Edd. 
> 
> I looked at the maker.ini file and I noticed the following code: 
> 
> ; Font Entries Added in Frame 8 due to Font Set Changes 
> 
> Zapfdingbats, *,*= Adobe Pi Std,*,* 
> 
> In the automated process that I am using, when the xml feed is about to be 
> imported is this line of code causing FrameMaker 11 to override the font 
> changes that I made to all of the FrameMaker 11 files? Should I change this 
> line of code to this in order to fix the problem: 
> 
> Zapfdingbats, *,*= ITC Zapf Dingbats Std,*,* 
> 
> Any help that you can give me will be appreciated. 
> 
> Brenda George 
> 
> Desk: (724) 720-8491 
> 
> bgeo...@federatedinv.com
 
_______________________________________________


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.

Reply via email to