RE: Unavailable fonts message - incorrect?

[David Artman]

Excellent summary from Fred!I'll just add the (very minor) point that SVG graphics can have font information in them, too. If the font's glyphs used in the SVG's aren't embedded, that would trigger this FM error.


 Original Message ----
Subject: RE: Unavailable fonts message - incorrect?
From: Fred Ridder <docu...@hotmail.com>... They can even be hiding in certain types of graphic objects that contain font specifications (PDF, EPS, WMF, EMF).



___


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.

Unavailable fonts message - incorrect?

[Fred Ridder]

Quite right about SVG, David. I neglected to include SVG in my list because I 
have never actually used that format. The last time I experimented with 
SVGs--back in FM7, if I recall correctly--they weren't fully supported so I 
abandoned my attempt to use them.  For the last several years, I have always 
used cropped PDFs whenever possible and have had very few issues with them.

I do have personal experience with missing fonts messages caused by each of the 
four formats I mentioned. EMF and WMF are particularly troublesome because 
those formats only embed the font *name*, never any of the glyph outlines from 
the font itself, so the graphics are totally dependent on each system's 
complement of installed fonts.

-Fred Ridder

From: da...@davidartman.com
To: docudoc at hotmail.com; pascale.stephenson at upu.int; framers at 
lists.frameusers.com
Subject: RE: Unavailable fonts message - incorrect?
Date: Wed, 21 Aug 2013 10:59:15 -0700

Excellent summary from Fred!
I'll just add the (very minor) point that SVG graphics can have font 
information in them, too. If the font's glyphs used in the SVG's aren't 
embedded, that would trigger this FM error.




 Original Message ----

Subject: RE: Unavailable fonts message - incorrect?

From: Fred Ridder 

... They can even be hiding in certain types of graphic objects that contain 
font specifications (PDF, EPS, WMF, EMF).




-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.frameusers.com/pipermail/framers/attachments/20130821/94a6b906/attachment.html>

RE: Unavailable fonts message - incorrect?

[Fred Ridder]

Quite right about SVG, David. I neglected to include SVG in my list because I 
have never actually used that format. The last time I experimented with 
SVGs--back in FM7, if I recall correctly--they weren't fully supported so I 
abandoned my attempt to use them.  For the last several years, I have always 
used cropped PDFs whenever possible and have had very few issues with them.

I do have personal experience with missing fonts messages caused by each of the 
four formats I mentioned. EMF and WMF are particularly troublesome because 
those formats only embed the font *name*, never any of the glyph outlines from 
the font itself, so the graphics are totally dependent on each system's 
complement of installed fonts.

-Fred Ridder

From: da...@davidartman.com
To: docu...@hotmail.com; pascale.stephen...@upu.int; 
framers@lists.frameusers.com
Subject: RE: Unavailable fonts message - incorrect?
Date: Wed, 21 Aug 2013 10:59:15 -0700

Excellent summary from Fred!
I'll just add the (very minor) point that SVG graphics can have font 
information in them, too. If the font's glyphs used in the SVG's aren't 
embedded, that would trigger this FM error.




 Original Message ----

Subject: RE: Unavailable fonts message - incorrect?

From: Fred Ridder 

... They can even be hiding in certain types of graphic objects that contain 
font specifications (PDF, EPS, WMF, EMF).



  ___


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.

Unavailable fonts message - incorrect?

[David Artman]

An HTML attachment was scrubbed...
URL: 

RE: Unavailable fonts message - incorrect?

[STEPHENSON pascale]

Yes - I said as much to Fred myself but forgot to post my answer to the list. 
This is really useful, detailed information.

Thanks

Pascale

From: Alison Craig [mailto:alison.cr...@ultrasonix.com]
Sent: 15 August 2013 18:51
To: Fred Ridder; STEPHENSON pascale; framers@lists.frameusers.com
Subject: RE: Unavailable fonts message - incorrect?

Wow.

This e-mail goes in my "reference" folder. Next time I need this info, I want 
it to be able to retrieve it immediately.

Thanks for great lesson, Fred.

Alison

Alison Craig | Technical Documentation Lead
Ultrasonix | 130-4311 Viking Way | Richmond, BC  V6V 2K9 | 
analogicultrasound.com<http://www.analogicultrasound.com>
T 604-279-8550 ext 127 | F 604-279-8559

Analogic
Ultrasound



[cid:image001.gif@01CE6B83.A9238C10]<http://www.analogicultrasound.com/bk>

[cid:image002.gif@01CE6B83.A9238C10]<http://www.analogicultrasound.com/ultrasonix>

[cid:image003.gif@01CE6B83.A9238C10]<http://www.analogicultrasound.com/sti>


From: 
framers-boun...@lists.frameusers.com<mailto:framers-boun...@lists.frameusers.com>
 [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Fred Ridder
Sent: Thursday, August 15, 2013 6:06 AM
To: STEPHENSON pascale; 
framers@lists.frameusers.com<mailto:framers@lists.frameusers.com>
Subject: RE: Unavailable fonts message - incorrect?

You posting seems to reflect several small misconceptions about how FrameMaker 
works. Let me see if I can address them one at a time.

First, a single "unavailable fonts" message in one file can, in fact, also be 
the cause of subsequent "unresolved cross-references" messages in other files. 
When you open any file that contains cross-references, FrameMaker attempts to 
refresh all of those references by looking at each target location and grabbing 
the current text string and numbering properties (autonumbering and page 
numbering). If any of those cross-references point to locations that are in 
other files, FM has to silently open each of those files to refresh the 
references. But if a "target" file has an unavailable font condition, that 
error prevents FM from completing the "silent open" operation that is necessary 
to resolve the cross-reference. The result is an "unresolved cross-reference" 
message. But note that if the file with the unavailable font condition is 
already open when you open the file that refers to it, you will *not* get an 
"unresolved" message because FM doesn't need to do a silent open.

Second, FrameMaker *does* report which fonts are unavailable, but does not do 
it in the warning message itself. Instead, you have to look in the FrameMaker 
console window, which most of us are in the habit of ignoring or dismissing 
without bothering to read it.

Third, the unavailable font does not have to be applied to any content that 
appears in the body of the document to cause the warning message. It is enough 
for the font to be specified in the definition of some format that you don't 
actually use, and this font specification can be in any of your catalogs--a 
character format, a paragraph format, a cross-reference format, or a table 
format. Table formats are a particular problem because each format definition 
invisibly embeds the character and paragraph formatting for the table title, 
and for each cell in the heading row, the footing row, and the first body row 
of the table that was the prototype when the format was defined; you will never 
be able to find these using the FM GUI unless you create an instance of each 
table format that exists in your catalog. Unavailable fonts can also lurk on 
master pages and reference pages which are not examined when you do a "find 
font" operation (which only searches the context in the current view) or List 
of References operation (which only looks at body pages). They can even be 
hiding in certain types of graphic objects that contain font specifications 
(PDF, EPS, WMF, EMF).

Fourth, to get rid of an unavailable fonts condition you need to *UN-check* the 
"Remember Missing Font Names" preference. Remembering the names means that FM 
will do a *temporary* substitution of an available font for an unavailable one, 
but will retain the original, unavailable font specification in the version of 
the file that it saves. What you need is for FM to *forget* the names of the 
unavailable fonts and save the file with the substituted font specifications. 
So the procedure would be:
1.  Open the offending file, dismissing the "unavailable fonts" warning.
2.  Examine the FrameMaker console to determine whether all of the 
substitutions FM has made are appropriate (e.g., no sans-serif font subbed for 
a serif, no text font subbed for a symbol or wingding font).
3.  Close the file.
4.  Turn OFF "Remember Missing Font Names".
5.  Open the file. Not

Unavailable fonts message - incorrect?

[STEPHENSON pascale]

Yes - I said as much to Fred myself but forgot to post my answer to the list. 
This is really useful, detailed information.

Thanks

Pascale

From: Alison Craig [mailto:alison.cr...@ultrasonix.com]
Sent: 15 August 2013 18:51
To: Fred Ridder; STEPHENSON pascale; framers at lists.frameusers.com
Subject: RE: Unavailable fonts message - incorrect?

Wow.

This e-mail goes in my "reference" folder. Next time I need this info, I want 
it to be able to retrieve it immediately.

Thanks for great lesson, Fred.

Alison

Alison Craig | Technical Documentation Lead
Ultrasonix | 130-4311 Viking Way | Richmond, BC  V6V 2K9 | 
analogicultrasound.com<http://www.analogicultrasound.com>
T 604-279-8550 ext 127 | F 604-279-8559

Analogic
Ultrasound



[cid:image001.gif at 01CE6B83.A9238C10]<http://www.analogicultrasound.com/bk>

[cid:image002.gif at 
01CE6B83.A9238C10]<http://www.analogicultrasound.com/ultrasonix>

[cid:image003.gif at 01CE6B83.A9238C10]<http://www.analogicultrasound.com/sti>


From: framers-bounces at lists.frameusers.com<mailto:framers-bounces at 
lists.frameusers.com> [mailto:framers-boun...@lists.frameusers.com] On Behalf 
Of Fred Ridder
Sent: Thursday, August 15, 2013 6:06 AM
To: STEPHENSON pascale; framers at lists.frameusers.com<mailto:framers at 
lists.frameusers.com>
Subject: RE: Unavailable fonts message - incorrect?

You posting seems to reflect several small misconceptions about how FrameMaker 
works. Let me see if I can address them one at a time.

First, a single "unavailable fonts" message in one file can, in fact, also be 
the cause of subsequent "unresolved cross-references" messages in other files. 
When you open any file that contains cross-references, FrameMaker attempts to 
refresh all of those references by looking at each target location and grabbing 
the current text string and numbering properties (autonumbering and page 
numbering). If any of those cross-references point to locations that are in 
other files, FM has to silently open each of those files to refresh the 
references. But if a "target" file has an unavailable font condition, that 
error prevents FM from completing the "silent open" operation that is necessary 
to resolve the cross-reference. The result is an "unresolved cross-reference" 
message. But note that if the file with the unavailable font condition is 
already open when you open the file that refers to it, you will *not* get an 
"unresolved" message because FM doesn't need to do a silent open.

Second, FrameMaker *does* report which fonts are unavailable, but does not do 
it in the warning message itself. Instead, you have to look in the FrameMaker 
console window, which most of us are in the habit of ignoring or dismissing 
without bothering to read it.

Third, the unavailable font does not have to be applied to any content that 
appears in the body of the document to cause the warning message. It is enough 
for the font to be specified in the definition of some format that you don't 
actually use, and this font specification can be in any of your catalogs--a 
character format, a paragraph format, a cross-reference format, or a table 
format. Table formats are a particular problem because each format definition 
invisibly embeds the character and paragraph formatting for the table title, 
and for each cell in the heading row, the footing row, and the first body row 
of the table that was the prototype when the format was defined; you will never 
be able to find these using the FM GUI unless you create an instance of each 
table format that exists in your catalog. Unavailable fonts can also lurk on 
master pages and reference pages which are not examined when you do a "find 
font" operation (which only searches the context in the current view) or List 
of References operation (which only looks at body pages). They can even be 
hiding in certain types of graphic objects that contain font specifications 
(PDF, EPS, WMF, EMF).

Fourth, to get rid of an unavailable fonts condition you need to *UN-check* the 
"Remember Missing Font Names" preference. Remembering the names means that FM 
will do a *temporary* substitution of an available font for an unavailable one, 
but will retain the original, unavailable font specification in the version of 
the file that it saves. What you need is for FM to *forget* the names of the 
unavailable fonts and save the file with the substituted font specifications. 
So the procedure would be:
1.  Open the offending file, dismissing the "unavailable fonts" warning.
2.  Examine the FrameMaker console to determine whether all of the 
substitutions FM has made are appropriate (e.g., no sans-serif font subbed for 
a serif, no text font subbed for a symbol or wingding font).
3.  Close the file.
4.  Turn OFF "Remember Missing Font Names&quo

RE: Unavailable fonts message - incorrect?

[STEPHENSON pascale]

Hi all

Thanks for the replies. I now have a better understanding of the situation, if 
I haven't exactly solved it. However, I have enough information to be going on 
with.

Thanks all for your help.

Regards

Pascale
___


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: Unavailable fonts message - incorrect?

[Craig Ede]

Fred presents a very cogent discussion of how fonts can hide out. 

 

I would add that one can dictate which font substitutes for another
(important when you turn off Remember Missing Fonts) by using the [Fonts]
area of the maker.ini file, although that area of the .ini file has gotten
rather complicated.

And one relatively recent improvements to the interface is the Fonts Pod
where you can track down and replace fonts that are actually in the
documents body, master and reference pages. It even tells you where the
substitution if taking place.

Mif washing can get rid of errant font information as well, especially
information that ends up being in the book file itself. The book file seems
to collect information from its components and can retain that information
after the components have been cleansed.

 

Craig

 

From: framers-boun...@lists.frameusers.com
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of Fred Ridder
Sent: Thursday, August 15, 2013 8:06 AM
To: STEPHENSON pascale; framers@lists.frameusers.com
Subject: RE: Unavailable fonts message - incorrect?

 

You posting seems to reflect several small misconceptions about how
FrameMaker works. Let me see if I can address them one at a time.

First, a single "unavailable fonts" message in one file can, in fact, also
be the cause of subsequent "unresolved cross-references" messages in other
files. When you open any file that contains cross-references, FrameMaker
attempts to refresh all of those references by looking at each target
location and grabbing the current text string and numbering properties
(autonumbering and page numbering). If any of those cross-references point
to locations that are in other files, FM has to silently open each of those
files to refresh the references. But if a "target" file has an unavailable
font condition, that error prevents FM from completing the "silent open"
operation that is necessary to resolve the cross-reference. The result is an
"unresolved cross-reference" message. But note that if the file with the
unavailable font condition is already open when you open the file that
refers to it, you will *not* get an "unresolved" message because FM doesn't
need to do a silent open.

Second, FrameMaker *does* report which fonts are unavailable, but does not
do it in the warning message itself. Instead, you have to look in the
FrameMaker console window, which most of us are in the habit of ignoring or
dismissing without bothering to read it.

Third, the unavailable font does not have to be applied to any content that
appears in the body of the document to cause the warning message. It is
enough for the font to be specified in the definition of some format that
you don't actually use, and this font specification can be in any of your
catalogs--a character format, a paragraph format, a cross-reference format,
or a table format. Table formats are a particular problem because each
format definition invisibly embeds the character and paragraph formatting
for the table title, and for each cell in the heading row, the footing row,
and the first body row of the table that was the prototype when the format
was defined; you will never be able to find these using the FM GUI unless
you create an instance of each table format that exists in your catalog.
Unavailable fonts can also lurk on master pages and reference pages which
are not examined when you do a "find font" operation (which only searches
the context in the current view) or List of References operation (which only
looks at body pages). They can even be hiding in certain types of graphic
objects that contain font specifications (PDF, EPS, WMF, EMF).

Fourth, to get rid of an unavailable fonts condition you need to *UN-check*
the "Remember Missing Font Names" preference. Remembering the names means
that FM will do a *temporary* substitution of an available font for an
unavailable one, but will retain the original, unavailable font
specification in the version of the file that it saves. What you need is for
FM to *forget* the names of the unavailable fonts and save the file with the
substituted font specifications. So the procedure would be:

1.  Open the offending file, dismissing the "unavailable fonts" warning.
2.  Examine the FrameMaker console to determine whether all of the
substitutions FM has made are appropriate (e.g., no sans-serif font subbed
for a serif, no text font subbed for a symbol or wingding font).
3.  Close the file.
4.  Turn OFF "Remember Missing Font Names".
5.  Open the file. Notice that the warning message has changed, and that
FrameMaker now warns you that it will be permanently *replacing* the fonts
rather than substituting for them. 
6.  Examine the file to make sure it looks OK.
7.  Save the file. Many people neglect to do this because they haven't
made any explicit edits or format changes, but the f

Unavailable fonts message - incorrect?

[STEPHENSON pascale]

Hi all

Thanks for the replies. I now have a better understanding of the situation, if 
I haven't exactly solved it. However, I have enough information to be going on 
with.

Thanks all for your help.

Regards

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

Unavailable fonts message - incorrect?

[Alison Craig]

Wow.

This e-mail goes in my "reference" folder. Next time I need this info, I want 
it to be able to retrieve it immediately.

Thanks for great lesson, Fred.

Alison

Alison Craig | Technical Documentation Lead
Ultrasonix | 130-4311 Viking Way | Richmond, BC  V6V 2K9 | 
analogicultrasound.com<http://www.analogicultrasound.com>
T 604-279-8550 ext 127 | F 604-279-8559

Analogic
Ultrasound



[cid:image001.gif at 01CE999C.EC651B00]<http://www.analogicultrasound.com/bk>

[cid:image002.gif at 
01CE999C.EC651B00]<http://www.analogicultrasound.com/ultrasonix>

[cid:image003.gif at 01CE999C.EC651B00]<http://www.analogicultrasound.com/sti>


From: framers-bounces at lists.frameusers.com 
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of Fred Ridder
Sent: Thursday, August 15, 2013 6:06 AM
To: STEPHENSON pascale; framers at lists.frameusers.com
Subject: RE: Unavailable fonts message - incorrect?

You posting seems to reflect several small misconceptions about how FrameMaker 
works. Let me see if I can address them one at a time.

First, a single "unavailable fonts" message in one file can, in fact, also be 
the cause of subsequent "unresolved cross-references" messages in other files. 
When you open any file that contains cross-references, FrameMaker attempts to 
refresh all of those references by looking at each target location and grabbing 
the current text string and numbering properties (autonumbering and page 
numbering). If any of those cross-references point to locations that are in 
other files, FM has to silently open each of those files to refresh the 
references. But if a "target" file has an unavailable font condition, that 
error prevents FM from completing the "silent open" operation that is necessary 
to resolve the cross-reference. The result is an "unresolved cross-reference" 
message. But note that if the file with the unavailable font condition is 
already open when you open the file that refers to it, you will *not* get an 
"unresolved" message because FM doesn't need to do a silent open.

Second, FrameMaker *does* report which fonts are unavailable, but does not do 
it in the warning message itself. Instead, you have to look in the FrameMaker 
console window, which most of us are in the habit of ignoring or dismissing 
without bothering to read it.

Third, the unavailable font does not have to be applied to any content that 
appears in the body of the document to cause the warning message. It is enough 
for the font to be specified in the definition of some format that you don't 
actually use, and this font specification can be in any of your catalogs--a 
character format, a paragraph format, a cross-reference format, or a table 
format. Table formats are a particular problem because each format definition 
invisibly embeds the character and paragraph formatting for the table title, 
and for each cell in the heading row, the footing row, and the first body row 
of the table that was the prototype when the format was defined; you will never 
be able to find these using the FM GUI unless you create an instance of each 
table format that exists in your catalog. Unavailable fonts can also lurk on 
master pages and reference pages which are not examined when you do a "find 
font" operation (which only searches the context in the current view) or List 
of References operation (which only looks at body pages). They can even be 
hiding in certain types of graphic objects that contain font specifications 
(PDF, EPS, WMF, EMF).

Fourth, to get rid of an unavailable fonts condition you need to *UN-check* the 
"Remember Missing Font Names" preference. Remembering the names means that FM 
will do a *temporary* substitution of an available font for an unavailable one, 
but will retain the original, unavailable font specification in the version of 
the file that it saves. What you need is for FM to *forget* the names of the 
unavailable fonts and save the file with the substituted font specifications. 
So the procedure would be:
1.   Open the offending file, dismissing the "unavailable fonts" warning.
2.   Examine the FrameMaker console to determine whether all of the 
substitutions FM has made are appropriate (e.g., no sans-serif font subbed for 
a serif, no text font subbed for a symbol or wingding font).
3.   Close the file.
4.   Turn OFF "Remember Missing Font Names".
5.   Open the file. Notice that the warning message has changed, and that 
FrameMaker now warns you that it will be permanently *replacing* the fonts 
rather than substituting for them.
6.   Examine the file to make sure it looks OK.
7.   Save the file. Many people neglect to do this because they haven't 
made any explicit edits or format changes, but the font change will not "take" 
and be carried forward unless the

Unavailable fonts message - incorrect?

[Fred Ridder]

You posting seems to reflect several small misconceptions about how FrameMaker 
works. Let me see if I can address them one at a time.

First, a single "unavailable fonts" message in one file can, in fact, also be 
the cause of subsequent "unresolved cross-references" messages in other files. 
When you open any file that contains cross-references, FrameMaker attempts to 
refresh all of those references by looking at each target location and grabbing 
the current text string and numbering properties (autonumbering and page 
numbering). If any of those cross-references point to locations that are in 
other files, FM has to silently open each of those files to refresh the 
references. But if a "target" file has an unavailable font condition, that 
error prevents FM from completing the "silent open" operation that is necessary 
to resolve the cross-reference. The result is an "unresolved cross-reference" 
message. But note that if the file with the unavailable font condition is 
already open when you open the file that refers to it, you will *not* get an 
"unresolved" message because FM doesn't need to do a silent open.

Second, FrameMaker *does* report which fonts are unavailable, but does not do 
it in the warning message itself. Instead, you have to look in the FrameMaker 
console window, which most of us are in the habit of ignoring or dismissing 
without bothering to read it.

Third, the unavailable font does not have to be applied to any content that 
appears in the body of the document to cause the warning message. It is enough 
for the font to be specified in the definition of some format that you don't 
actually use, and this font specification can be in any of your catalogs--a 
character format, a paragraph format, a cross-reference format, or a table 
format. Table formats are a particular problem because each format definition 
invisibly embeds the character and paragraph formatting for the table title, 
and for each cell in the heading row, the footing row, and the first body row 
of the table that was the prototype when the format was defined; you will never 
be able to find these using the FM GUI unless you create an instance of each 
table format that exists in your catalog. Unavailable fonts can also lurk on 
master pages and reference pages which are not examined when you do a "find 
font" operation (which only searches the context in the current view) or List 
of References operation (which only looks at body pages). They can even be 
hiding in certain types of graphic objects that contain font specifications 
(PDF, EPS, WMF, EMF).

Fourth, to get rid of an unavailable fonts condition you need to *UN-check* the 
"Remember Missing Font Names" preference. Remembering the names means that FM 
will do a *temporary* substitution of an available font for an unavailable one, 
but will retain the original, unavailable font specification in the version of 
the file that it saves. What you need is for FM to *forget* the names of the 
unavailable fonts and save the file with the substituted font specifications. 
So the procedure would be:
Open the offending file, dismissing the "unavailable fonts" warning.Examine the 
FrameMaker console to determine whether all of the substitutions FM has made 
are appropriate (e.g., no sans-serif font subbed for a serif, no text font 
subbed for a symbol or wingding font).Close the file.Turn OFF "Remember Missing 
Font Names".Open the file. Notice that the warning message has changed, and 
that FrameMaker now warns you that it will be permanently *replacing* the fonts 
rather than substituting for them. 
Examine the file to make sure it looks OK.Save the file. Many people neglect to 
do this because they haven't made any explicit edits or format changes, but the 
font change will not "take" and be carried forward unless the file is saved 
after you let FM make the replacement.Turn "Remember Missing Font Names" back 
ON. (It is normally a very good idea not to reformat a file from a colleague or 
client to match your own less complete font library.)This *should* take care of 
the problem unless the bad font name is embedded in a graphic.



Another approach that some users swear by is to save the offending file as MIF 
and then use a text editor to search for the names of the unavailable fonts, as 
reported in the FM console. After making the substitution with the font editor, 
the file is saved as MIF, then opened from FrameMaker and saved back to .fm 
file format. This approach still will not look inside graphics objects, but I 
have personally seen cases where the source .fm file contained a *completely* 
spurious font specification (for a Chinese font in my case) that was removed 
simply by passing it through the FM->MIF filter (i.e., the bad font was not 
findable in the the MIF file and was gone when the file was restored

Unavailable fonts message - incorrect?

[Craig Ede]

Fred presents a very cogent discussion of how fonts can hide out. 



I would add that one can dictate which font substitutes for another
(important when you turn off Remember Missing Fonts) by using the [Fonts]
area of the maker.ini file, although that area of the .ini file has gotten
rather complicated.

And one relatively recent improvements to the interface is the Fonts Pod
where you can track down and replace fonts that are actually in the
documents body, master and reference pages. It even tells you where the
substitution if taking place.

Mif washing can get rid of errant font information as well, especially
information that ends up being in the book file itself. The book file seems
to collect information from its components and can retain that information
after the components have been cleansed.



Craig



From: framers-boun...@lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of Fred Ridder
Sent: Thursday, August 15, 2013 8:06 AM
To: STEPHENSON pascale; framers at lists.frameusers.com
Subject: RE: Unavailable fonts message - incorrect?



You posting seems to reflect several small misconceptions about how
FrameMaker works. Let me see if I can address them one at a time.

First, a single "unavailable fonts" message in one file can, in fact, also
be the cause of subsequent "unresolved cross-references" messages in other
files. When you open any file that contains cross-references, FrameMaker
attempts to refresh all of those references by looking at each target
location and grabbing the current text string and numbering properties
(autonumbering and page numbering). If any of those cross-references point
to locations that are in other files, FM has to silently open each of those
files to refresh the references. But if a "target" file has an unavailable
font condition, that error prevents FM from completing the "silent open"
operation that is necessary to resolve the cross-reference. The result is an
"unresolved cross-reference" message. But note that if the file with the
unavailable font condition is already open when you open the file that
refers to it, you will *not* get an "unresolved" message because FM doesn't
need to do a silent open.

Second, FrameMaker *does* report which fonts are unavailable, but does not
do it in the warning message itself. Instead, you have to look in the
FrameMaker console window, which most of us are in the habit of ignoring or
dismissing without bothering to read it.

Third, the unavailable font does not have to be applied to any content that
appears in the body of the document to cause the warning message. It is
enough for the font to be specified in the definition of some format that
you don't actually use, and this font specification can be in any of your
catalogs--a character format, a paragraph format, a cross-reference format,
or a table format. Table formats are a particular problem because each
format definition invisibly embeds the character and paragraph formatting
for the table title, and for each cell in the heading row, the footing row,
and the first body row of the table that was the prototype when the format
was defined; you will never be able to find these using the FM GUI unless
you create an instance of each table format that exists in your catalog.
Unavailable fonts can also lurk on master pages and reference pages which
are not examined when you do a "find font" operation (which only searches
the context in the current view) or List of References operation (which only
looks at body pages). They can even be hiding in certain types of graphic
objects that contain font specifications (PDF, EPS, WMF, EMF).

Fourth, to get rid of an unavailable fonts condition you need to *UN-check*
the "Remember Missing Font Names" preference. Remembering the names means
that FM will do a *temporary* substitution of an available font for an
unavailable one, but will retain the original, unavailable font
specification in the version of the file that it saves. What you need is for
FM to *forget* the names of the unavailable fonts and save the file with the
substituted font specifications. So the procedure would be:

1.  Open the offending file, dismissing the "unavailable fonts" warning.
2.  Examine the FrameMaker console to determine whether all of the
substitutions FM has made are appropriate (e.g., no sans-serif font subbed
for a serif, no text font subbed for a symbol or wingding font).
3.  Close the file.
4.  Turn OFF "Remember Missing Font Names".
5.  Open the file. Notice that the warning message has changed, and that
FrameMaker now warns you that it will be permanently *replacing* the fonts
rather than substituting for them. 
6.  Examine the file to make sure it looks OK.
7.  Save the file. Many people neglect to do this because they haven't
made any explicit edits or format changes, but th

Unavailable fonts message - incorrect?

[Rick Quatro]

Hi Pascale,



The FrameMaker Console window will tell you which fonts are missing. The
missing fonts may be on Reference or Master pages, or inside of table
formats.



Rick



Rick Quatro

Carmen Publishing Inc.

585-283-5045

rick at frameexpert.com







From: framers-boun...@lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of STEPHENSON
pascale
Sent: Wednesday, August 14, 2013 6:17 AM
To: framers at lists.frameusers.com
Subject: Unavailable fonts message - incorrect?



Hello



I am using FrameMaker 9 on Windows 7. When I open a particular book, I get
the classic 'unavailable fonts' error on many of the files (followed by
'unresolved cross-reference' errors, but for now I'm assuming the two are
related). When my colleague opens the same book, he doesn't get any errors.
Fair enough, our font setup might be a little bit different.



FM doesn't report which fonts are causing the problem in the message, so I
took two files, one with the error and one without, and generated a list of
fonts using Special > List Of > References. Both files contain exactly the
same fonts so I can't isolate it to any font in particular. Indeed, the fact
one has a problem with one of the fonts and the other doesn't makes me think
the error itself may be incorrect.



Has anyone else experienced this or have any idea what I can do next? It
seems to be one particular book causing the problem.

Checking the 'Remember Missing Font Names' option doesn't stop the problem
from re-occurring.



Thanks in advance.



Pascale

-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.frameusers.com/pipermail/framers/attachments/20130815/2254292b/attachment.html>

RE: Unavailable fonts message - incorrect?

[Fred Ridder]

You posting seems to reflect several small misconceptions about how FrameMaker 
works. Let me see if I can address them one at a time.

First, a single "unavailable fonts" message in one file can, in fact, also be 
the cause of subsequent "unresolved cross-references" messages in other files. 
When you open any file that contains cross-references, FrameMaker attempts to 
refresh all of those references by looking at each target location and grabbing 
the current text string and numbering properties (autonumbering and page 
numbering). If any of those cross-references point to locations that are in 
other files, FM has to silently open each of those files to refresh the 
references. But if a "target" file has an unavailable font condition, that 
error prevents FM from completing the "silent open" operation that is necessary 
to resolve the cross-reference. The result is an "unresolved cross-reference" 
message. But note that if the file with the unavailable font condition is 
already open when you open the file that refers to it, you will *not* get an 
"unresolved" message because FM doesn't need to do a silent open.

Second, FrameMaker *does* report which fonts are unavailable, but does not do 
it in the warning message itself. Instead, you have to look in the FrameMaker 
console window, which most of us are in the habit of ignoring or dismissing 
without bothering to read it.

Third, the unavailable font does not have to be applied to any content that 
appears in the body of the document to cause the warning message. It is enough 
for the font to be specified in the definition of some format that you don't 
actually use, and this font specification can be in any of your catalogs--a 
character format, a paragraph format, a cross-reference format, or a table 
format. Table formats are a particular problem because each format definition 
invisibly embeds the character and paragraph formatting for the table title, 
and for each cell in the heading row, the footing row, and the first body row 
of the table that was the prototype when the format was defined; you will never 
be able to find these using the FM GUI unless you create an instance of each 
table format that exists in your catalog. Unavailable fonts can also lurk on 
master pages and reference pages which are not examined when you do a "find 
font" operation (which only searches the context in the current view) or List 
of References operation (which only looks at body pages). They can even be 
hiding in certain types of graphic objects that contain font specifications 
(PDF, EPS, WMF, EMF).

Fourth, to get rid of an unavailable fonts condition you need to *UN-check* the 
"Remember Missing Font Names" preference. Remembering the names means that FM 
will do a *temporary* substitution of an available font for an unavailable one, 
but will retain the original, unavailable font specification in the version of 
the file that it saves. What you need is for FM to *forget* the names of the 
unavailable fonts and save the file with the substituted font specifications. 
So the procedure would be:
Open the offending file, dismissing the "unavailable fonts" warning.Examine the 
FrameMaker console to determine whether all of the substitutions FM has made 
are appropriate (e.g., no sans-serif font subbed for a serif, no text font 
subbed for a symbol or wingding font).Close the file.Turn OFF "Remember Missing 
Font Names".Open the file. Notice that the warning message has changed, and 
that FrameMaker now warns you that it will be permanently *replacing* the fonts 
rather than substituting for them. 
Examine the file to make sure it looks OK.Save the file. Many people neglect to 
do this because they haven't made any explicit edits or format changes, but the 
font change will not "take" and be carried forward unless the file is saved 
after you let FM make the replacement.Turn "Remember Missing Font Names" back 
ON. (It is normally a very good idea not to reformat a file from a colleague or 
client to match your own less complete font library.)This *should* take care of 
the problem unless the bad font name is embedded in a graphic.



Another approach that some users swear by is to save the offending file as MIF 
and then use a text editor to search for the names of the unavailable fonts, as 
reported in the FM console. After making the substitution with the font editor, 
the file is saved as MIF, then opened from FrameMaker and saved back to .fm 
file format. This approach still will not look inside graphics objects, but I 
have personally seen cases where the source .fm file contained a *completely* 
spurious font specification (for a Chinese font in my case) that was removed 
simply by passing it through the FM->MIF filter (i.e., the bad font was not 
findable in the the MIF file and was gone when the file was resto

RE: Unavailable fonts message - incorrect?

[Rick Quatro]

Hi Pascale,

 

The FrameMaker Console window will tell you which fonts are missing. The
missing fonts may be on Reference or Master pages, or inside of table
formats.

 

Rick

 

Rick Quatro

Carmen Publishing Inc.

585-283-5045

r...@frameexpert.com

 

 

 

From: framers-boun...@lists.frameusers.com
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of STEPHENSON
pascale
Sent: Wednesday, August 14, 2013 6:17 AM
To: framers@lists.frameusers.com
Subject: Unavailable fonts message - incorrect?

 

Hello

 

I am using FrameMaker 9 on Windows 7. When I open a particular book, I get
the classic 'unavailable fonts' error on many of the files (followed by
'unresolved cross-reference' errors, but for now I'm assuming the two are
related). When my colleague opens the same book, he doesn't get any errors.
Fair enough, our font setup might be a little bit different.

 

FM doesn't report which fonts are causing the problem in the message, so I
took two files, one with the error and one without, and generated a list of
fonts using Special > List Of > References. Both files contain exactly the
same fonts so I can't isolate it to any font in particular. Indeed, the fact
one has a problem with one of the fonts and the other doesn't makes me think
the error itself may be incorrect.

 

Has anyone else experienced this or have any idea what I can do next? It
seems to be one particular book causing the problem.

Checking the 'Remember Missing Font Names' option doesn't stop the problem
from re-occurring.

 

Thanks in advance.

 

Pascale

___


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.

Unavailable fonts message - incorrect?

[STEPHENSON pascale]

Hello

I am using FrameMaker 9 on Windows 7. When I open a particular book, I get the 
classic 'unavailable fonts' error on many of the files (followed by 'unresolved 
cross-reference' errors, but for now I'm assuming the two are related). When my 
colleague opens the same book, he doesn't get any errors. Fair enough, our font 
setup might be a little bit different.

FM doesn't report which fonts are causing the problem in the message, so I took 
two files, one with the error and one without, and generated a list of fonts 
using Special > List Of > References. Both files contain exactly the same fonts 
so I can't isolate it to any font in particular. Indeed, the fact one has a 
problem with one of the fonts and the other doesn't makes me think the error 
itself may be incorrect.

Has anyone else experienced this or have any idea what I can do next? It seems 
to be one particular book causing the problem.
Checking the 'Remember Missing Font Names' option doesn't stop the problem from 
re-occurring.

Thanks in advance.

Pascale
___


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.

Unavailable fonts message - incorrect?

[STEPHENSON pascale]

Hello

I am using FrameMaker 9 on Windows 7. When I open a particular book, I get the 
classic 'unavailable fonts' error on many of the files (followed by 'unresolved 
cross-reference' errors, but for now I'm assuming the two are related). When my 
colleague opens the same book, he doesn't get any errors. Fair enough, our font 
setup might be a little bit different.

FM doesn't report which fonts are causing the problem in the message, so I took 
two files, one with the error and one without, and generated a list of fonts 
using Special > List Of > References. Both files contain exactly the same fonts 
so I can't isolate it to any font in particular. Indeed, the fact one has a 
problem with one of the fonts and the other doesn't makes me think the error 
itself may be incorrect.

Has anyone else experienced this or have any idea what I can do next? It seems 
to be one particular book causing the problem.
Checking the 'Remember Missing Font Names' option doesn't stop the problem from 
re-occurring.

Thanks in advance.

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