"unavailable fonts" problem: URGENT (Bill Swallow)

[Bill Swallow]

Hey, how'd I get in the subject line??? ;-)

I agree that blowing out the text in MIF is drastic, though it'll
definitely solve the problem. Editing the MIF to replace the offending
font name with another one is a better route. Still, the 'remember
missing font names' quick fix will work to produce a PDF in a pinch.

On Feb 7, 2008 10:24 AM, Combs, Richard  wrote:
> Miriam Boral wrote:
>
> > Save the offending file as .mif and then open the .mif file with a
> > text editor to view the underlying code. Search for the missing font
> > and delete the text that uses it. Save the file and then
> > resave as .fm.
> >
> > This is the only foolproof solution I've found!
>
> That seems a bit drastic, compared to turning off Remember Missing Font
> Names. For one thing, you might want the text that uses that font! For
> another, the font could be referenced in, for instance, a default pgf of
> a table format -- you probably don't want to delete the table format.
>
> If you insist on mucking about in the MIF, a better approach would be to
> replace the font name with the one you want to use -- but you can
> accomplish the same thing -- once and for all, for all files going
> forward -- by setting the desired font substitution in maker.ini and
> then turning off Remember Missing Font Names.

-- 
Bill Swallow
HATT List Owner
WWP-Users List Owner
Senior Member STC, TechValley Chapter
STC Single-Sourcing SIG Manager
http://techcommdood.blogspot.com

Re: "unavailable fonts" problem: URGENT (Bill Swallow)

[Frank Stearns]

On Thu, 7 Feb 2008, Bill Swallow wrote:

> Hey, how'd I get in the subject line??? ;-)
>
> I agree that blowing out the text in MIF is drastic, though it'll
> definitely solve the problem. Editing the MIF to replace the offending
> font name with another one is a better route. Still, the 'remember
> missing font names' quick fix will work to produce a PDF in a pinch.
>
> On Feb 7, 2008 10:24 AM, Combs, Richard <[EMAIL PROTECTED]> wrote:
>> Miriam Boral wrote:
>>
>>> Save the offending file as .mif and then open the .mif file with a
>>> text editor to view the underlying code. Search for the missing font
>>> and delete the text that uses it. Save the file and then
>>> resave as .fm.
>>>
>>> This is the only foolproof solution I've found!


We've found over the years that sometimes the internal mazes of the 
object lists that make up an FM doc can leave you with no way back.

As an example, it's possible to get "stale" font information lodged 
inside a table with NO WAY via the user interface to get to it. At 
that point, a MIF edit is the only way to get to that stale font.

Doesn't happen very often, but it can be frustrating when it does.

Frank Stearns Associates | makers of IXgen(tm) for FrameMaker(r)
[EMAIL PROTECTED] 
TOLL FREE Voice (USA and Canada):  800-567-6421
USA Voice: 360-892-3970  USA FAX: 360-253-1498
http://www.fsatools.com
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

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

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

"unavailable fonts" problem: URGENT (Bill Swallow)

[Frank Stearns]

On Thu, 7 Feb 2008, Bill Swallow wrote:

> Hey, how'd I get in the subject line??? ;-)
>
> I agree that blowing out the text in MIF is drastic, though it'll
> definitely solve the problem. Editing the MIF to replace the offending
> font name with another one is a better route. Still, the 'remember
> missing font names' quick fix will work to produce a PDF in a pinch.
>
> On Feb 7, 2008 10:24 AM, Combs, Richard  wrote:
>> Miriam Boral wrote:
>>
>>> Save the offending file as .mif and then open the .mif file with a
>>> text editor to view the underlying code. Search for the missing font
>>> and delete the text that uses it. Save the file and then
>>> resave as .fm.
>>>
>>> This is the only foolproof solution I've found!


We've found over the years that sometimes the internal mazes of the 
object lists that make up an FM doc can leave you with no way back.

As an example, it's possible to get "stale" font information lodged 
inside a table with NO WAY via the user interface to get to it. At 
that point, a MIF edit is the only way to get to that stale font.

Doesn't happen very often, but it can be frustrating when it does.

Frank Stearns Associates | makers of IXgen(tm) for FrameMaker(r)
franks at fsatools.com 
TOLL FREE Voice (USA and Canada):  800-567-6421
USA Voice: 360-892-3970  USA FAX: 360-253-1498
http://www.fsatools.com

Re: "unavailable fonts" problem: URGENT (Bill Swallow)

[Bill Swallow]

Hey, how'd I get in the subject line??? ;-)

I agree that blowing out the text in MIF is drastic, though it'll
definitely solve the problem. Editing the MIF to replace the offending
font name with another one is a better route. Still, the 'remember
missing font names' quick fix will work to produce a PDF in a pinch.

On Feb 7, 2008 10:24 AM, Combs, Richard <[EMAIL PROTECTED]> wrote:
> Miriam Boral wrote:
>
> > Save the offending file as .mif and then open the .mif file with a
> > text editor to view the underlying code. Search for the missing font
> > and delete the text that uses it. Save the file and then
> > resave as .fm.
> >
> > This is the only foolproof solution I've found!
>
> That seems a bit drastic, compared to turning off Remember Missing Font
> Names. For one thing, you might want the text that uses that font! For
> another, the font could be referenced in, for instance, a default pgf of
> a table format -- you probably don't want to delete the table format.
>
> If you insist on mucking about in the MIF, a better approach would be to
> replace the font name with the one you want to use -- but you can
> accomplish the same thing -- once and for all, for all files going
> forward -- by setting the desired font substitution in maker.ini and
> then turning off Remember Missing Font Names.

-- 
Bill Swallow
HATT List Owner
WWP-Users List Owner
Senior Member STC, TechValley Chapter
STC Single-Sourcing SIG Manager
http://techcommdood.blogspot.com
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

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

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

"unavailable fonts" problem: URGENT (Bill Swallow)

[Combs, Richard]

Miriam Boral wrote:

> Save the offending file as .mif and then open the .mif file with a 
> text editor to view the underlying code. Search for the missing font 
> and delete the text that uses it. Save the file and then 
> resave as .fm.
> 
> This is the only foolproof solution I've found!

That seems a bit drastic, compared to turning off Remember Missing Font
Names. For one thing, you might want the text that uses that font! For
another, the font could be referenced in, for instance, a default pgf of
a table format -- you probably don't want to delete the table format.

If you insist on mucking about in the MIF, a better approach would be to
replace the font name with the one you want to use -- but you can
accomplish the same thing -- once and for all, for all files going
forward -- by setting the desired font substitution in maker.ini and
then turning off Remember Missing Font Names. 

BTW, when you post in reply to a digest entry, please don't leave the
entire digest in your reply. 

Richard


--
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
--
rgcombs AT gmailDOTcom
303-777-0436
--

RE: "unavailable fonts" problem: URGENT (Bill Swallow)

[Combs, Richard]

Miriam Boral wrote:

> Save the offending file as .mif and then open the .mif file with a 
> text editor to view the underlying code. Search for the missing font 
> and delete the text that uses it. Save the file and then 
> resave as .fm.
> 
> This is the only foolproof solution I've found!

That seems a bit drastic, compared to turning off Remember Missing Font
Names. For one thing, you might want the text that uses that font! For
another, the font could be referenced in, for instance, a default pgf of
a table format -- you probably don't want to delete the table format.

If you insist on mucking about in the MIF, a better approach would be to
replace the font name with the one you want to use -- but you can
accomplish the same thing -- once and for all, for all files going
forward -- by setting the desired font substitution in maker.ini and
then turning off Remember Missing Font Names. 

BTW, when you post in reply to a digest entry, please don't leave the
entire digest in your reply. 

Richard


--
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
--
rgcombs AT gmailDOTcom
303-777-0436
--




___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

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

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

"unavailable fonts" problem: URGENT (Bill Swallow)

[Miriam Boral]

ramers-request at lists.frameusers.com?subject=subscribe>
>Sender: framers-bounces at lists.frameusers.com
>Errors-To: framers-bounces at lists.frameusers.com
>
>Send Framers mailing list submissions to
> framers at lists.frameusers.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.frameusers.com/mailman/listinfo/framers
>or, via email, send a message with subject or body 'help' to
> framers-request at lists.frameusers.com
>
>You can reach the person managing the list at
> framers-owner at lists.frameusers.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Framers digest..."
>
>
>Today's Topics:
>
>1. Internal Error (Shmuel Wolfson)
>2. Re: Revising Help topics created in WebWorks (Yves Barbion)
>3. RE: Working with Images (richard.melanson at us.tel.com)
>4. RE: Working with Images (Dennis Brunnenmeyer)
>5. Re: keep with next para (Stuart Rogers)
>6. RE: keep with next para (Combs, Richard)
>7. Re: Working with Images (Stuart Rogers)
>8. Re: Duplicating a two-page section (Stuart Rogers)
>9. Re: Working with Images (Peter Gold)
>   10. page layout for a double-wide table  (Ben Hechter)
>   11. RE: Working with Images (Dennis Brunnenmeyer)
>   12. FM8 now works for us (Austin Meredith)
>   13. "unavailable fonts" problem: URGENT (Brewster, Christopher C)
>   14. Re: page layout for a double-wide table (Stuart Rogers)
>   15. Re: "unavailable fonts" problem: URGENT (Bill Swallow)
>   16. Question about applying and removing character tags in FM6.0
>   (maxwell.hoffmann)
>   17. RE: Question about applying and removing character tags in
>   FM6.0 (Owen, Clint)
>   18. Distiller 7 missing fonts (Shuttleworth, Roger)
>   19. RE: Distiller 7 missing fonts (Owen, Clint)
>   20. Re: Working with Images (Stuart Rogers)
>   21. RE: Distiller 7 missing fonts (Alan Litchfield)
>   22. RE: Distiller 7 missing fonts (rebecca officer)
>   23. Re: Distiller 7 missing fonts (Mike Wickham)
>   24. Re: Question about applying and removing character tags in
>   FM6.0 (Peter Gold)
>   25. re: keep with next para (solved) (Graeme R Forbes)
>   26. RE: Distiller 7 missing fonts (Jacob Sch?ffer)
>
>
>--
>
>Message: 1
>Date: Wed, 06 Feb 2008 13:22:24 +0200
>From: Shmuel Wolfson 
>Subject: Internal Error
>To: Framers 
>Message-ID: <47A99870.8020608 at actcom.com>
>Content-Type: text/plain; charset=UTF-8; format=flowed
>
>I occasionally have the dreaded "Internal Error" after a search in FM,
>then FM closes. Would extra RAM help? I have 1 GB of RAM now.
>
>--
>Regards,
>Shmuel Wolfson
>
>
>
>
>--
>
>Message: 2
>Date: Wed, 06 Feb 2008 12:43:37 +0100
>From: Yves Barbion 
>Subject: Re: Revising Help topics created in WebWorks
>To: Rebecca Martin 
>Cc: framers at lists.frameusers.com
>Message-ID: <47A99D69.2050603 at gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>Hi Rebecca,
>
>if you only need to change the text in the footer, the easiest (and
>cheapest) way is to open all the HTML files in a plain text editor and
>do a global search and replace there. For example, you could use EditPad
>Lite for this: http://www.editpadpro.com/editpadlite.html
>
>Thus, you don't have to upgrade WebWorks (or FrameMaker).
>
>Good luck.
>
>Yves Barbion
>Documentation Architect
>Adobe-Certified FrameMaker Instructor
>
>
>Scripto bvba
>Asselsstraat 65
>9031 Gent
>Belgium
>T: +32 494 12 01 89
>F: +32 9 366 50 23
>BTW (VAT) BE 0886.192.394
>skype: yves.barbion
>
>
>
>
>Rebecca Martin wrote:
> > I have a legacy Help project that was created in Frame7.1 and published via
> > Webworks Publisher 2003 for FrameMaker. We need to make changes to the
> > footer in every topic, but have been unable to find the project file for
> > editing. I was told we should make the changes in Frame and republish the
> > help with Webworks. Unfortunately, it looks like we cannot make changes to
> > the current project unless we use the WebWorks Publisher Professional
> > Edition 7.0. (That would require us to upgrade, but we're not sure the
> > current version of FM would work with it.)
> >
> >
> >
> > Is that a correct assumption?
> >
> >
> >
> > Is there a project file we should be looking for? We have found .wdt and
> > .wfp files, none of