-
1. Re: font change not appearing in Autonumber
Bob Niland (Error 7103) Nov 15, 2012 3:50 AM (in response to rlauriston)Why isn't the format using a \b ?
-
2. Re: font change not appearing in Autonumber
rlauriston Nov 15, 2012 10:25 AM (in response to Bob Niland (Error 7103))Who knows? They're legacy docs. These formats were probably originally created with FrameMaker 5.5.6 around 1998 and have passed through uncounted hands since then.
-
3. Re: font change not appearing in Autonumber
rlauriston Nov 15, 2012 10:32 AM (in response to rlauriston)Seems like the issue is in how I hacked Adobe Pi Std. The Bullet2 paragraph tag, which is the same except the Autonumber string is n\t, is displaying a square bullet, as expected.
-
4. Re: font change not appearing in Autonumber
Arnis Gubins Nov 15, 2012 10:43 AM (in response to rlauriston)Robert,
As I mentioned in your other thread, you can still use the older Postscript fonts on a Win7 platform, so you could use either the ZaptDingbats or ZapgDingbats BT versions directly without hacking the AdobePiStd.
-
5. Re: font change not appearing in Autonumber
rlauriston Nov 15, 2012 10:50 AM (in response to Arnis Gubins)As I said above, the font mapping is not working, so I'd have to edit every document. I'll do that eventually, as the docs need to be updated, and get rid of dingbat font usage entirely.
-
6. Re: font change not appearing in Autonumber
rlauriston Nov 15, 2012 10:51 AM (in response to rlauriston)I eventually got the hacked font to work. I needed to reboot Windows to get it to recognize the modified font, and delete FrameMaker's .font_cache to get FrameMaker to apply it consistently.
-
7. Re: font change not appearing in Autonumber
Arnis Gubins Nov 15, 2012 2:15 PM (in response to rlauriston)All I'm saying is that if you install a PS version of ZapfDingbats, you wouldn't have to change anything in any document. Right now, if somebody else opens a document without your special hacked version of the font, you do have a maintenance issue.
Also, you can comment out the AdobePiStd substitution line in the maker.ini to prevent FM from trying to make any substituions.
-
8. Re: font change not appearing in Autonumber
rlauriston Nov 15, 2012 2:25 PM (in response to Arnis Gubins)Why would FrameMaker do any better with a PS version of Zapf Dingbats than with the OpenType version that's installed already?
I tried commenting out the font mapping line entirely, no change.
-
9. Re: font change not appearing in Autonumber
Arnis Gubins Nov 15, 2012 2:40 PM (in response to rlauriston)The encodings are different. With either version of Dingbats, you would be using thee original FrameRoman and all of the characters would display as intended.
Something sounds strange on your installation. I'm not seeing any substitutions taking place for ZapfDingbats on any of FM8-11 on XP or Win7 64-bit plaforms (nor do I even have the substitution line commented out).
Do you have the "Remember Missing Font Names" option set in your Preferences?
-
10. Re: font change not appearing in Autonumber
rlauriston Nov 15, 2012 3:40 PM (in response to Arnis Gubins)I believe I installed FM9 and then upgraded to TCS 3.5. The relevant maker.ini entry was:
[UnknownToKnownFontMap]
...
; Font Entries Added in Frame 8 due to Font Set Changes
...
Zapfdingbats, *,*= Adobe Pi Std,*,*
-
11. Re: font change not appearing in Autonumber
Arnis Gubins Nov 15, 2012 6:39 PM (in response to rlauriston)Shouldn't that be "ZapfDingbats"? FM is case-sensitive (unix heritage) for most things.
-
12. Re: font change not appearing in Autonumber
rlauriston Nov 16, 2012 8:56 AM (in response to Arnis Gubins)That file was created by the FM9 and/or TCS 3.5 installer, so if it's wrong, it's a bug.
But what are the chances of encountering a bug in FrameMaker 10? It's so robust you'd think it had been coded by Microsoft.