The original UI makeover in FrameMaker 9 broke a lot of keyboard
shortcuts that Adobe never fixed.
On Thu, May 17, 2018 at 11:34 AM, Harding, Dan wrote:
> Pardon me for the rant, but I need to vent.
> I just recently upgraded from Frame 2012 to Frame 2017 as the former
Log some bugs at Adobe. :D
And yes, it is annoying when they break something in the process of adding
new features or changing the design. I got very accustomed to using ESC
keyboard shortcuts in FM, and when I finally had a job with FM 10, I was
annoyed to discover that some of them didn't work
Can you provide the autonumbering from the heading tags? Not the TOC tags,
but the ones used in the document.
On Thu, May 17, 2018 at 1:29 PM, Gillian Flato wrote:
> My headings throughout my guide are numbered. I want the numbering to
> reflect in the TOC. I have the
Pardon me for the rant, but I need to vent.
I just recently upgraded from Frame 2012 to Frame 2017 as the former doesn't
work at all with high resolution displays. However, in the process I've
discovered that Adobe has broken several things... and there's nothing more
annoying than lazy
Check the reference pages. Code for the TOC is stored there. You'll see things
like <$paratext> and then you can put <$paranum> in front of it. That pulls the
numbering from the source file. You can play around with the specifics of how
and what happens, but that, or <$paranumonly> should get
My headings throughout my guide are numbered. I want the numbering to reflect
in the TOC. I have the numbering working after the chapter number but not for
the chapter number.
So what I mean is that in the TOC I have the following:
1 Chapter 1
1.1 Heading 1
1.1.1 Heading 2
220.127.116.11 Heading 3