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
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
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
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
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
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
mages (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