[Closed] FrameMaker 7.x/8 Feature Requests

Report · Aug 19, 2002

Time to start entering these. If you are unsure about whether FM has the feature yet, please do some research and figure it out before posting.

Please don't post requests for assistance in here, either.

Cheers,

Sean

Report · Aug 26, 2003

5. Print paragraph and character styles listing, including all attributes (like MIFMunch).
6. LastPage Variable.

Report · Aug 26, 2003

«Turn off automatic backup files»

Can be done now. Click File, Prefernces and then check the appropriate box.

Report · Sep 02, 2003

<<Tables within tables.>>

Can be done now, although it's awkward. Insert anchored frame within table cell, draw a text box in the anchored frame, then insert new table in the text box.

Report · Sep 02, 2003

Gloria is correct but note that Quadralay's WebWorks Publisher rasterizes anything contained in an anchored frame: the AF's contents are converted into a graphic.

This means that for WWP users, table insets generated as on-line content become no longer searchable or editable as text. Perhaps not a big problem, but I too would like to be able to simply nest a table inside of a table. Good Heavens, even clunky old HTML can do that...

Cheers,
Riley

Report · Sep 03, 2003

True. This solution works well (other than laborious setup) for paper or PDF; not so well for other online formats. I would also prefer a real solution.

--Gloria Mc

Report · Sep 09, 2003

Bleah! It only took me 4.5 hours to read all 376 messages!

My wish list for the next Frame release:

1) multiple undos (4-to-6 should be enough)

2) (As mentioned in message #118), provide a utility to print reports on unused character tags, paragraph tags, unused variables, unused cross-reference formats, etc. Just something to help us clean up old stuff carried over from legacy style sheets. Also provide the ability to print a list of variables used and the page numbers on which they occur (the way a list of references works). I know we can currently create a list of markers and cross-references, but is there currently a way to do this with variables?

3) (As mentioned in message #341), provide the ability to assign color to different marker types. I try to stick a comment marker at the beginning of a publication, in case there's any reminders/comments I need to make known before the next update of the publication. Having these markers appear in perky red or another color from the Windows color box would be cool.

4) For lengthy index references, let the column break that occurs from the bottom of one column to the top of the next cause a variable to be inserted that lists the Level1IX text, plus "(continued)." (I'd like this to work similarly to how the Table continuation variable works).

5) Fix the bug in FrameMaker 7.0 that creates the error message "The filter encountered an error and could not complete the translation." This happens with every *.wmf file I import by reference that has anything more than a couple words of text. (Frame 6.0 imported *.wmf files of any size/detail with no annoying error message.)

My workaround for the above problem, which seems to be an Import/Filter bug, is as follows:

a) Create a simple *.wmf file using just a text box with one word,
such as "Temp" or "Crap!"

b) Name the *.wmf file as you would using your preferred naming convention.

c)Import the *.wmf file into an anchored frame in your FrameMaker document. The file, since it is so simple, should import at 100% scaling with no problem.

d) Save the REAL graphic you want to import as a *.wmf file and give it the same name that you used in step b. When the "file already exists" message appears, click Yes to overwrite the existing file. Since Frame has already accepted and imported the simpleton version of the filename, it will replace the original *.wmf graphic with the more detailed version.

e) Size and scale the graphic as needed.

Caution: If you delete the graphic from the frame, you will have to repeat steps a through e.

6) From a message I posted on 09/08/03: Fix whatever the problem is that is causing one of my graphics not to appear in a PDF file (although it appears in the Frame file and on the printed page).

that's all,
ChristyG

Report · Sep 09, 2003

Nix item number 6) from my feature request list, since the problem was solved by replacing a non-true *.wmf graphic file with a true *.gif version of the file.

ChristyG

Report · Sep 10, 2003

I like the suggestion about different colors for different marker types. However, I've been working with markers a lot lately and sometimes have 3 or 4 different markers that I want to put in the same place (e.g., index, cross reference, hyper text, and custom).

Perhaps another way would be to have one marker, and then have have a single dialog that lets you edit or insert multiple marker values. When I need to edit one of my markers, I have to select each by trial and error until I find the right one. I'd rather have just one place and one interface.

&& Mike

Report · Sep 17, 2003

Line numbering for books and single files. Should be available to number consecutively or restart by page or section.

Useful for legal and software engineering document review where references are made to section 1, page 5, line 112. Basically, see Word's implementation. No, I don't want to go back to word, but it does do SOME things well.

Report · Sep 18, 2003

Searchability within Equation boxes and anchored frames....I specialize in setting up math books, and this would be a plus.

Support for foreign ways of writing equations...In norway, we use a period like a comma in numbers and a comma like a decimalpoint. We also put a space in between million, thousandand, hundreds, etc.

Searching for non existant paragraph formats....as in when you import a document from word...to be able to find any paragraphs which would be imported as *paragraph format (Asterix+name). Particularly useful when most of the doc has been reformated with search and replace Paraformat to find anything that has fallen through the cracks.

Report · Sep 18, 2003

The possibility of endnotes as opposed to footnotes. It isn't used so often, but we occationally have authors which want them.

Report · Sep 19, 2003

The ability for cross-references to "know where they are" such that "below" or "above" can replace "pagenum" when the source and target are on the same page.

Report · Sep 19, 2003

Steven,

You should have learned by now not to use above and below. Leaves you subject to all kind of printing changes.

Report · Sep 19, 2003

I call it an "if...then" cross-ref. Dealing with cross-refs that point to
the same page is one example. Imagine how cool it would be to have one
cross-ref definition do:
See Installation on page 34.
See Installation, below.
See Installation, later in this chapter.
See Installation, above.
See Installation, earlier in this chapter.

Report · Sep 22, 2003

Tim,

That would be nice.

Report · Sep 22, 2003

Yeah. You can FrameScript it.

Cheers,

Sean

Report · Sep 22, 2003

Sean,

This is very interesting. For the FrameScript-challenged, could you refer me to some helpful links, please?

thanks,
ChristyG

Report · Sep 22, 2003

The best link is this: . Also, see .

Cheers,

Sean

Report · Sep 23, 2003

Most of these things can be done using a macro editing tool such as QuicKeys or MacroExpress. The advantage of such tools is that they are generic and can be used in other software, e.g., MS Office, Acrobat, etc. They do not work for heavy duty stuff, e.g., database automation within FM, but can easily handle the items in this thread.

robertusPunctumPacificus

Report · Sep 24, 2003

Horace. Your comment is totally unnecessary. Of COURSE I don't use "above" and "below" now! But if FM handled it correctly, I would certainly use it. That's why I entered a FEATURE REQUEST.

Report · Sep 24, 2003

I would love to see a "PostIt note" like feature that I can "stick" on some text or frame and it will stay with that object. Further, this feature will not affect paginiation and will not (by default) print or be included in PDF. Basically, I want to leave notes for myself that do not have to be "conditionalized" and which do not affect pagination when displayed.

Currently I have to leave notes using a special para tag. I have to condition the paragraph to not be included when printing and generating PDF (and generating HTML). Further, I can't see how my page paginates without hiding the paragraphs.

I realize that I could kludge this with floating frames and anchor frames, but why should it be so hard? I'd like the tool to just do it please.

Report · Sep 25, 2003

Mike,

It doesn't have to be hard. You just need to set this up once in a
template on your reference pages. Create and anchored frame holding a
text frame. Set the anchored frame to be outside of the text area.
Create a paratag to use for your notes that uses a non-printing colour
that you've defined and set up in your Views.

You can copy and paste this from the Reference page as needed or use
Steve Kubis' Auto-text (http://www262.pair.com/spsoft/) to insert it
from a menu selection

Report · Sep 25, 2003

Arnis, Thanks, that's an interesting hack. How do you propose turning them "off" when you don't want to see them: to hide them? I hope not by changing the colors each time.

More important though, I really don't want it to be that hard to use. FM is a very powerful tool which allows you to produce all kinds of effects like you describe. However, why does it have to be so hard to use? (Just think about all the amazing kludges we produce with tables to get around formatting inadequacies.) Further, I don't want to have to use a third party product. I don't want to have to define special colors, etc. I just want the feature in the product as shipped.

But thanks again for the suggestion; I'll play with it and see if it suits my needs!

Mike

Report · Sep 25, 2003

Mike,

Check out how to use Views. You can quickly switch between pre-defined
views that hide certain colours by using the esc v v [1-6] shortcuts.
I usually toggle between views 1 & 6 to hide or uncover things. It's
as near instantaneous as you can get.

Report · Sep 25, 2003

I too agree that the interface leaves much to be desired. Frame was originally developed on UNIX (ported to all flavors: AIX, HP-UX, Solaris, etc.) and it still supported on just about every UNIX platform along with Windows and Mac. Adobe noticed that Frame held a unique corner of the market that they knew no other DTP product offered: long doc support and the ability to handle global updates with absolute ease.

I've asked a person from Adobe's technical marketing dept directly why the interface hadn't been touched since Adobe acquired it 5 years ago, and he said 1) "current customers are comfortable with the UI" 2) "it would be a big undertaking". In short, the code is ancient and to go through a rewrite all that code would apparently take an extreme amount of time and resources. While this may be true, I think this quote from Tom Arah at Designer-info.com sums up the problem nicely:

"FrameMaker's underlying principles and layout engine remain as powerful as theyve always been and for institutional users looking for long technical document handling and multichannel output it remains the most flexible choice. The fact is though, that with the paradigm shift to XML-based publishing and repurposing, FrameMaker should be stronger than ever and winning new markets rather than trading on its past. Unless Adobe stops bundling and gets coding that's simply not going to happen and FrameMaker will remain a niche option - mainframe rather than mainstream."

You can read his full review of Frame 7 here:

http://www.designer-info.com/DTP/framemaker.htm

Does Adobe want Frame to remain a niche tool? Who knows, but with a 2-year development cycle that yields very little with each release, it's hard to know what their true intentions may be. With the surge of technical communicators over the last few years who rely very heavily on Frame (I believe Frame is as important to tech writers as Photoshop to graphic artists) Frame should be even more powerful than ever. As a technical writer, Frame still remains the only tool I truly rely on for producing manuals and other technical documentation. I couldn't imagine working in a Word shop, especially with the thousands of pages of doc I have to manage now.

Adobe recently moved Frame development to Adobe India, which I believe could mean one of two things: 1) move Frame out of our US offices so we can focus on the products that "really matter" (Photoshop, InDesign, Illustrator, Acrobat, etc..), or 2) get Frame to a development environment that will take a fresh approach to Frame's development, while also allowing them to reduce the costs (being in a third-party country) it will take to overhaul the product. I can only hope for the second assumption.

We can expect the next release of Frame in another year, so only time will tell what Adobe's got in mind for the world's best DTP tool.