On 24 Jan 2013 at 16:11, Stuart Rogers wrote:
Here's a thought: In the [Preferences] section of maker.ini, there's a
UseDisplayUnitInTemplate setting, followed by various (English and
metric) defaults. UseDisplayUnitInTemplate is set to Off in both my
maker.ini and the saved original
On 24 Jan 2013 at 16:11, Stuart Rogers wrote:
> > Here's a thought: In the [Preferences] section of maker.ini, there's a
> > UseDisplayUnitInTemplate setting, followed by various (English and
> > metric) defaults. UseDisplayUnitInTemplate is set to Off in both my
> > maker.ini and the saved
Have you tried saving as .mif and searching for that font?
On Wed, Jan 23, 2013 at 4:06 PM, Karen Robbins karendes...@gmail.com wrote:
A file (generated file from a plain text source) keeps displaying the
unavailable fonts error each time it opens.
I've run Silicoin Prairie's Paragraph Tools
the
unavailable fonts error each time it opens.
I've run Silicoin Prairie's Paragraph Tools on this file, and the
only font it finds in the file is HelveticaNeueLT Std--exactly as it
should be. I've checked the master pages (four)--no hidden text
boxes; and the reference page (one)--nothing
At 17:21 -0800 23/1/13, Karen Robbins wrote:
You are correct, that's just what it was--Times instances in the default
tables. (I did the mif to find this out; there are no tables in the document
itself.) I already thought I'd have to do what you say... How annoying that I
have to do this extra
Karen Robbins wrote:
You are correct, that's just what it was--Times instances in the default
tables. (I did the mif to find this out; there are no tables in the document
itself.)
That's why I said to insert an instance of each table format.
I already thought I'd have to do what you
I sure do learn something new every day! :-)
I could also define those formats in a stock document and always
import them to the working document. I do something similar for
indexes--a format master imported each time a new one is generated.
I like the idea of using SP's Table Tools to just
On 24/01/2013 11:18 AM, Karen Robbins wrote:
I sure do learn something new every day! :-)
I could also define those formats in a stock document and always
import them to the working document. I do something similar for
indexes--a format master imported each time a new one is generated.
I like
On 24/01/2013 11:05 AM, Combs, Richard wrote:
Or for a comprehensive, permanent solution, you can modify any and
all format definitions to suit you (as well as which formats exist)
in the behind-the-scenes template that FM uses when you create a new
document without selecting a template (Use
Stuart Rogers wrote:
I just modified shellnew.fm with your suggested changes, and there is no
effect on a new document. The table formats still use Times New Roman,
the ruler is still in cm.
There is another file, custom with no extension, also in the fminit
directory. I am able to use
On 24/01/2013 1:31 PM, Matt Sullivan wrote:
I believe the Document Properties in custom.fm will control units.
(setting custom.fm to use a specific unit of measure should fix this)
Should, but doesn't. The Custom file (no extension) opens with a ruler
in inches. New documents opened with
I wrote:
Oops, sorry. I misremembered some information from many years ago. You're
right, it's custom that's used when you create new blank paper documents in FM
(shellnew.fm is used when you create a new FM doc outside of FM; don't ask me
why).
Eating lunch seems to have slightly revived
For anyone still using FrameMaker 7 on Mac, the 'custom' file that sets the
defaults for new blank documents seems to be /Adobe FrameMaker
7.0/Modules/Custom New Document, in whatever root folder you have located your
Classic apps.
--
Steve
___
You
On 24/01/2013 3:07 PM, Combs, Richard wrote:
Stuart Rogers wrote:
Thanks for the link, Richard. I tried following the instructions
and overwrote the custom. file; no joy.
Sure sounds like a bug. But IIRC, you're on FM 10, right? It worked
in FM 10 for me.
Here's a thought: In the
Saving to Postscript and distilling does work,
but I did see a can't open [thisfilename].fm
message at the bottom of the book window beneath
the list of pages. The file did open, .ps file
was created correctly, distilled correctly.
I thought the save as PDF function in FM11 (my
current
Could this possibly be a FMinit setting?
Grant
On 1/24/2013 12:19 PM, Stuart Rogers wrote:
On 24/01/2013 1:31 PM, Matt Sullivan wrote:
I believe the Document Properties in custom.fm will control units.
(setting custom.fm to use a specific unit of measure should fix this)
Should, but doesn't.
n text source) keeps displaying the
> "unavailable fonts" error each time it opens.
>
> I've run Silicoin Prairie's Paragraph Tools on this file, and the
> only font it finds in the file is HelveticaNeueLT Std--exactly as it
> should be. I've checked the master pages (four)--no hidden
At 17:21 -0800 23/1/13, Karen Robbins wrote:
>You are correct, that's just what it was--Times instances in the default
>tables. (I did the mif to find this out; there are no tables in the document
>itself.) I already thought I'd have to do what you say... How annoying that I
>have to do this
Karen Robbins wrote:
> You are correct, that's just what it was--Times instances in the default
> tables. (I did the mif to find this out; there are no tables in the document
> itself.)
That's why I said to insert an instance of each table format.
> I already thought I'd have to do what you
I sure do learn something new every day! :-)
I could also define those formats in a "stock" document and always
import them to the working document. I do something similar for
indexes--a format master imported each time a new one is generated.
I like the idea of using SP's Table Tools to just
On 24/01/2013 11:18 AM, Karen Robbins wrote:
> I sure do learn something new every day! :-)
>
> I could also define those formats in a "stock" document and always
> import them to the working document. I do something similar for
> indexes--a format master imported each time a new one is generated.
On 24/01/2013 11:05 AM, Combs, Richard wrote:
>
> Or for a comprehensive, permanent solution, you can modify any and
> all format definitions to suit you (as well as which formats exist)
> in the behind-the-scenes template that FM uses when you create a new
> document without selecting a template
Stuart Rogers wrote:
> I just modified shellnew.fm with your suggested changes, and there is no
> effect on a new document. The table formats still use Times New Roman,
> the ruler is still in cm.
>
> There is another file, "custom" with no extension, also in the fminit
> directory. I am able
I believe the Document Properties in custom.fm will control units. (setting
custom.fm to use a specific unit of measure should fix this)
-Matt
Matt Sullivan
technical communication | online training | eLearning
twitter: @mattrsullivan
phone: 714 960-6840
On Jan 24, 2013, at 10:13 AM,
On 24/01/2013 1:31 PM, Matt Sullivan wrote:
> I believe the Document Properties in custom.fm will control units.
> (setting custom.fm to use a specific unit of measure should fix this)
>
Should, but doesn't. The Custom file (no extension) opens with a ruler
in inches. New documents opened with
I wrote:
> Oops, sorry. I misremembered some information from many years ago. You're
> right, it's custom that's used when you create new blank paper documents in FM
> (shellnew.fm is used when you create a new FM doc outside of FM; don't ask me
> why).
Eating lunch seems to have slightly
For anyone still using FrameMaker 7 on Mac, the 'custom' file that sets the
defaults for new blank documents seems to be /Adobe FrameMaker
7.0/Modules/Custom New Document, in whatever root folder you have located your
Classic apps.
--
Steve
On 24/01/2013 3:07 PM, Combs, Richard wrote:
> Stuart Rogers wrote:
>
>> Thanks for the link, Richard. I tried following the instructions
>> and overwrote the custom. file; no joy.
>
> Sure sounds like a bug. But IIRC, you're on FM 10, right? It worked
> in FM 10 for me.
>
> Here's a thought: In
Saving to Postscript and distilling does work,
but I did see a "can't open [thisfilename].fm"
message at the bottom of the book window beneath
the list of pages. The file did open, .ps file
was created correctly, distilled correctly.
I thought the "save as PDF" function in FM11 (my
current
Could this possibly be a FMinit setting?
Grant
On 1/24/2013 12:19 PM, Stuart Rogers wrote:
> On 24/01/2013 1:31 PM, Matt Sullivan wrote:
>> I believe the Document Properties in custom.fm will control units.
>> (setting custom.fm to use a specific unit of measure should fix this)
>
> Should, but
A file (generated file from a plain text source) keeps displaying the
unavailable fonts error each time it opens.
I've run Silicoin Prairie's Paragraph Tools on this file, and the
only font it finds in the file is HelveticaNeueLT Std--exactly as it
should be. I've checked the master pages
Karen Robbins wrote:
A file (generated file from a plain text source) keeps displaying the
unavailable fonts error each time it opens.
I've run Silicoin Prairie's Paragraph Tools on this file, and the
only font it finds in the file is HelveticaNeueLT Std--exactly as it
should be. I've
You are correct, that's just what it was--Times instances in the
default tables. (I did the mif to find this out; there are no tables
in the document itself.) I already thought I'd have to do what you
say... How annoying that I have to do this extra work to undo a
presumptuous default.
A file (generated file from a plain text source) keeps displaying the
"unavailable fonts" error each time it opens.
I've run Silicoin Prairie's Paragraph Tools on this file, and the
only font it finds in the file is HelveticaNeueLT Std--exactly as it
should be. I've checked the ma
Karen Robbins wrote:
> A file (generated file from a plain text source) keeps displaying the
> "unavailable fonts" error each time it opens.
>
> I've run Silicoin Prairie's Paragraph Tools on this file, and the
> only font it finds in the file is HelveticaNeueLT St
You are correct, that's just what it was--Times instances in the
default tables. (I did the mif to find this out; there are no tables
in the document itself.) I already thought I'd have to do what you
say... How annoying that I have to do this extra work to undo a
presumptuous default.
Have you tried saving as .mif and searching for that font?
On Wed, Jan 23, 2013 at 4:06 PM, Karen Robbins wrote:
> A file (generated file from a plain text source) keeps displaying the
> "unavailable fonts" error each time it opens.
>
> I've run Silicoin Prairie's Paragr
37 matches
Mail list logo
