Hello everybody,

I can not open a FM12 file, the internal error code 12024, 18652356, 18692061 and 18514761 tells me nothing and I unless searching for a plain text translation for the error codes! This kind of trouble occures from time to time but now, first time on FM12. Therefore I try to check if my EDD rules producing this mistake, error or other undefined loop. I like to fix this error but I need to know where is the mistake, one week of work are be in danger in this case... !!!

Anybody a idea to fix this issue? (no *.Backup / *.Recovery file existing)

Any possibilities for "OPEN IN SAVE MODE"

Any possibilities for "CHECK FILE BEFORE TRY TO OPEN"

I can not believe that Adobe is unable to define plain text error codes, the technical support in unreachable!

Thanks for help,

My office recently upgraded to FrameMaker 11 in a Windows 7 environment. We previously used FrameMaker 8 | Windows XP.

We are in the process of replacing the following fonts:

Courier

Zapf Dingbats

With the following:

Courier New

ITC Zapf Dingbats Std Medium

I am having problems with Zapf Dingbats being replaced with ITC Zapf Dingbats Std Medium. I have used the fonts pod to update these fonts for all of the appropriate FrameMaker files.

We use an automated process to create the FrameMaker files. The process involves importing XML feeds into Structured FrameMaker 11 using an automated process. After the XML has been imported, it is fully formatted in FrameMaker 11. After I select the xml file to import and the automated process is about to import the xml file into FrameMaker 11, the FrameMaker console is displaying this message:

The “Zapfdingbats” font is not available.

It will be replaced by “AdobePiStd”.

The “Zapfdingbats” font is not available.

It will be replaced by “AdobePiStd”.

The “Courier” font is not available.

It will be replaced by “Courier New”.

When I view the fonts in this newly created FrameMaker 11 file in the font pod, the “AdobePiStd” font is displayed as part of the fonts in this file. I did update the Zapf Dingbats occurrences in the FrameMaker template to ITC Zapf Dingbats Std Medium and I updated all of the other systems files as well. I did update the FrameMaker Edd.

I looked at the maker.ini file and I noticed the following code:

; Font Entries Added in Frame 8 due to Font Set Changes

Zapfdingbats, *,*= Adobe Pi Std,*,*

In the automated process that I am using, when the xml feed is about to be imported is this line of code causing FrameMaker 11 to override the font changes that I made to all of the FrameMaker 11 files? Should I change this line of code to this in order to fix the problem:

Zapfdingbats, *,*= ITC Zapf Dingbats Std,*,*

Any help that you can give me will be appreciated.

Hello,

I changed Preferences setting to Structured Authoring.  I was prompted to restart FrameMaker 11.x.

When I tried to open a file, I got this error message:

Any suggestions on what I might have done wrong?  If there is a bug or workaround for this, I would love to find it.  Thanks!  Laura Ferrer

In Frame 12 all the templates have been updated.

I built my book using unstructured templates because I wanted to get a feel for the changes from my last version of Frame (8).

I now think I will need to redo the book entirely using the templates from structured Frame.

The unstructured Frame template for a book has all master pages in every file in the book. The structured template for Chapter has only master pages: left, right, first. Is there a reason for this? (Should not every file in the book have the same master and reference pages?)

Thanks.

I am working with DITA files in Frame 8, and am unable to save a generated Frame file as a PDF. I keep getting these errors:

• "To execute "Save as PDF" command you must have Acrobat Distiller version 5.05 or higher installed."
• "To execute "Save as PDF" command you must have PDF Job Options defined.

I have Acrobat Distiller 8 installed, so I don't know why I'm getting the first error. I opened Distiller, and still got the error.

Also, I did try to set job options using Format> Document> PDF Setup. On the PDF Setup dialog box, the only job option in the PDF Job Options drop-down list was High Quality Print. When I clicked Set, I got a message stating that "The selected PDF Job Option does not existing in the current installation. Either create this Job Option or select an available Job Option."

How do you create a valid job option? How do you get it to show up in the drop-down list? I looked at the Adobe PDF properties in Print Setup, and the Default Settings show several job options including the High Quality Print option.

Any advice would be greatly appreciated.

I want to round trip the xrefs and retain the format of a xref  where the format varies on whether the xref relates to a table, chapter, another topic, etc. For example, I want to retain something like this for an xref that refers to another topic: "Overview orf Something on page 1-2 describes ..... On the other hand, I would like to vary the xref for a table, e.g., Table 40 describes ..... The objective is to retain these cross reference formats during a round trip. We are using DocBook v4.2. I was told by our engineers that this cannot be done and one can only retain one format and cannot vary it. Has anyone had any experience with this issue?

See Overview of Something on Page 1-2for your information. ...

I was told that this cannot be done because the script looks like this after it has been exported:

See <XREF ID="xxxxx"> for your information. ...

I was told the following by engineers that provided a custom plug-in:

Import/Export plug-in can't distinguish the type of referred object during importing according to engineers.

After you import the xml file it reads as follows

It’s impossible to vary cross-reference format based on referenced object types such as table, figure, things like that.

... See Overview of Something for your information. ...

Still researching feasability of adding S1000D into our doc production and management.  Does anyone know if FM 9 Server's Common Source Database will EFFECTIVELY manage S1000D modules? The product description mentions a CSDB, but really doesn't nail it down definitively and sales just doesn't have the background to provide a concrete answer either.   I've researched and found some 3rd party vendors who do for standard FM 9 (which we are currently using), but their prices don't matchup well with ROI.  FM server does, if it will effectively manage S1000D modules.

Eric G.

Hi All,

I am trying to print to PDF a publication that is full of oversize wiring diagrams. The pages are all images ranging in size from standard A3 and A4 siz sheets through to a foldout being 1470 mm W X 297 mm H. We have no problem printing A3, A4 and 630 mm W X 297 H. These are all Portrait images. When we set up our custom print size to accomodate the 1470 mm W X 297 mm H we get the pages without the content, and even some of the oversize pages are not the correct size on print.

The page sizes we are using are:

• A4
• A3
• 630 x 297 mm
• 840 x 297 mm
• 1050 x 297 mm
• 1260 x 297 mm
• 1470 x 297 mm

The procedures we are using to set up the printing are:

1.      Print to PDF (Do not Save to PDF, you do not have control over paper sizes)

Under Print Setup make sure you select PDF Driver and select the Paper size as largest that is in your book.  Example: If A4 and A3 pages, print to A3

2.      Select Generate Acrobat Data and select

Note: Back in FM Print dialogue; make sure Print to File is turned OFF, before you click Print

Any assistance would be greatly appreciated.

Regards

AJ Wilkinson

Hi everyone...I am fairly new to structured framemaker and spent the last week reading every piece of information I could on the subject.

I've been given the task here at work of taking some unstructured framemaker documents and structure them using MIL-STD 40051C as a guide.

If someone could please give me some help on this....I don't even know where to begin. Information overload. I have a DTD provided to me, as well as a folder containing XSL stylesheets for what seems like nearly every tag and a boilerplate folder.

Some of the links for my source material can be found here:

https://pubsweb.redstone.army.mil/DTD-FOSI/40051C-AMCOM.html

http://www.asrl.com/tmconstr.htm

So far I have imported the DTD to framemaker and saved as an EDD. Everything seems to be fine there. As far as the next step, I really have no idea.

I presume that if I wanted to build, lets say, a cover page...I would refer to the standard and build a page using the tags described.

I have given this a try and all I get is a tree structure with no formatting. How am I supposed to link to a stylesheet in Framemaker? What's more...there are about 50 styles in the folder I was provided so how do I know which one I am supposed to refer to?

Basically this is a huge scope of an effort that I am just getting my feet wet in, so if someone who is familiar can PLEASE give me some initial guidance it would be sincerely appreciated. I can't even find any documentation for this stuff on the web so this is my only hope.

Thanks very much

- Doug

I am working in structured FM 9 and would like to break the title of my figures and tables to a second line.  How would I do this in the EDD?

I just upgraded to Framemaker 10. I am encountering a number of problems when I try to work with my Dita XML help topics, which were last saved in Framemaker 9 format.

1. Using the Default Dita Template

When I open one of my documents in Framemaker 10, the Dita 1.2 template ditabase.fm is automatically applied. Everything seems fine. But then when I convert the XML to Eclipse help (which is essentially html, so we're going from XML to HTML) using Dita Open Toolkit ant scripts, I see this message:

[pipeline] [DOTJ013E][ERROR] Failed to parse the referenced file 'html\c_licensing.xml' due to below exception. Please correct the reference base on the exception message.
[pipeline] c_licensing.xml Line 25:Attribute "xmlns:ditaarch" must be declared for element type "dita".

I then opened the xml  file in a text editor, and I saw this on line 25:

<dita xmlns:ditaarch = "http://dita.oasis-open.org/architecture/2005/">

Line 25 looks fine to me. Am I missing something? 

2. Switching to a 1.1 Dita Template

I tried to work around the above problem. In Framemaker, I tried to set a different structured application as the default one. I closed all files and chose the default Dita 1.1 structured application (it defaults to the Dita 1.1. Composite app.)

Then I tried to open my file: I got this message inside Framemaker:

"Validation of XML failed. Continue?
Error at [FILE PATH], line 25, char 72, Message: Attribute '{http://www.w3.org/2000/xmlns/}ditaarch' is not declared for element 'dita'

Sounds familiar, doesn't it?

I switched from the default Dita 1.1. Composite structured application to the Dita 1.1. Topic structured application. Then I dirtied the source file and saved it. The messages I got in FrameMaker log window included the one above, plus I got a variety of Unknown Element messages, things like this:

Unknown element dita,

unknown element concept,

various attributes are not declared for concept,

unknown element conbody.

If I switch back to the Dita 1.1 Composite application all of these messages diappear except for this one:

Attribute '{http://www.w3.org/2000/xmlns/}ditaarch' is not declared for element 'dita'

My ant conversion scripts from the Dita Open Toolkit are still unable to process this file. They give the same message as is listed in (1) above and the file is not converted to HTML.

Can anyone help me with this problem? I've also posted this question to the Dita Users Group on Yahoo Groups. If I get an answer in one place, I'll post it in the other.

Thanks,

Nina P.

FrameMaker 10 and patched || Windows 7 64-bit

Our company is migrating from unstructured to structured DITA XML.  We had not encountered any "showstoppers" that would keep us from proceeding...until we tried producing FM Book files for our print offerings.  It's my understanding that to take advantage of FrameMaker's numbering and pagination features using DITA source content, one must create a DITA map and save it out as a FM Book file, first.  However, when we do this—and subsequently try to print it like a "normal" book—all of our DITA <title> elements remain at the highest heading level.  In other words, each topic, which lives in a hierarchical structure inside any one of the DITA sub-maps, will always take on the paragraph style of .  My topic titles don't nest; everything is at a "flat" level!   Interestingly enough, they nest correctly if I print directly from a DITA map and not from a hybrid DITA+FM book file.  But if I take that route, I forfeit FrameMaker's ability to create a table of contents, index, etc.—features I can't live without.

I've tried fixing this behavior over the course of an entire week, but I have not had any success.  I cannot find any resources that address this issue, nor can I find anyone with the same issue.  Left to my own devices, I've experimented with re-building the maps numerous times; I've built the maps as plain maps and as bookmaps; I've even tried strange things like conref-ing everything.

What am I missing?  Does anyone know what is going on here?  How can I get my <title> elements to nest?

Some background information:

We place chapters in submaps (one per).

We place those submaps in one, big map.

Any help would be greatly appreciated,

Sean

Hi,

I'm trying to import my XML data into a table format. After adding an XSL file to my Structure Application as a Preprocessing Stylesheet, and importing my XML instance file with the Template file opened, the "Unknown File Type" error window appeared asking for a file format to Convert From. Picking any one doesn't create a table.

The XSL file tranforms the XML data into an HTML file that has a table with columns corresponding to the XML data. I was thinking using that type of XSL because it renders tables.

Below is the XSL markup:

<?xml version="1.0" encoding="ISO-8859-1"?>

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:template match="/">

  <html>

  <body>

  <h2>Products</h2>

    <table border="1">

      <tr bgcolor="#9acd32">

        <th>Title</th>

        <th>Number</th>

        <th>Date</th>

      </tr>

      <xsl:for-each select="Products/Product">

      <tr>

        <td><xsl:value-of select="Title"/></td>

        <td><xsl:value-of select="Number"/></td>

        <td><xsl:value-of select="Date"/></td>

      </tr>

      </xsl:for-each>

    </table>

  </body>

  </html>

</xsl:template>

</xsl:stylesheet>

Title, Number, and Date are child elements of the Product element, which is a child element of the Products root element in my XML file.

Am I applying the stylesheet correctly here? Am I using the write kind of stylesheet?

Thanks,

zeb

Hi All,

In the DITA-FMx plugin developed by Leximation, there's a feature called Generate Book from Map. It allows me to create a FrameMaker book from a DITA map or bookmap and then do whatever I can do with any FrameMaker book, including create a PDF.

Is there anything similar in the native Adobe's DITA plugin? How can I get to a book from a DITA map/bookmap?

Thanks in advance!

I have valid XML that I am importing into FrameMaker just for printing.

My <figure> element contains a <title> and a <graphic> element. The graphic comes in within an anchored frame, appearing after the figure title. The figure title needs to be below the graphic. How do I get this to work? I read a couple of threads that used tables to wrap the graphic & the title and to make the title appear below, but that was during an export function to XML, not an import. Short of editing the DTD, EDD & all of the XML data to have the graphic element structure come before the title within <figure>, how would this be accomplished? Thanks in advance.

In Frame 9 structured (DITA) we could force Frame to record the actual widths of table columns in the DITA XML.  Frame 9 would respect the widths when opening the file.  This was particularly useful for forcing tables to be wide -- to go across the column and the side head -- and for the columns to never resize. 

In Frame 9 this was done by commenting out the line

"writer use proportional widths;" 

like this

"/* writer use proportional widths; */"

in the topic.rules.text" file located in

"...\FrameMaker9\Structure\xml\DITA\app\DITA-Topic-FM"

This no longer works in Frame10 and Frame 11.  Even though the same line is commented out in all the "NAME.rules.txt" files in all the subdirectories of

    "...\AdobeFrameMaker11\Structure\xml\DITA_1.2\app"

and

    "...\AdobeFrameMaker11\Structure\xml\DITA\app"  

and
    "...\AdobeFrameMaker10\Structure\xml\DITA_1.2\app"

and

    "...\AdobeFrameMaker10\Structure\xml\DITA\app"  .

Commenting out the line does force Frame 10 and 11 to record  the absolute column width (2.357" etc.) in the DITA XML.

However, on Open,  Frame 10 and 11 force the table to fit in the column, not the column and sidehead. That is they behave as though they were still using proportional column widths.  It seems the original values (as inserted by Frame 10 and 11 before closing!) are recalculated on Open, thereby mimicking the default proportional width behavior.  

For example, this on Save then Close from Frame 10 or 11

<table frame = "topbot" colsep = "0" rowsep = "1">

<tgroup cols = "4" colsep = "0" rowsep = "1" outputclass = "FormatB">

<colspec colnum = "1" colname = "1" colwidth = "1.796in" colsep = "0"/>

<colspec colnum = "2" colname = "2" colwidth = "1.852in" colsep = "0"/>

<colspec colnum = "3" colname = "3" colwidth = "1.179in" colsep = "0"/>

<colspec colnum = "4" colname = "4" colwidth = "2.152in" colsep = "0"/>

goes to this on Open then Save: 

<table frame = "topbot" colsep = "0" rowsep = "1">

<tgroup cols = "4" colsep = "0" rowsep = "1" outputclass = "FormatB">

<colspec colnum = "1" colname = "1" colwidth = "1.351in" colsep = "0"/>

<colspec colnum = "2" colname = "2" colwidth = "1.393in" colsep = "0"/>

<colspec colnum = "3" colname = "3" colwidth = "0.887in" colsep = "0"/>

<colspec colnum = "4" colname = "4" colwidth = "1.618in" colsep = "0"/>

Any help at all would be appreciated!  

We have 8,000 to 10,000 pages to PDF in the next few days and about 33% of those pages are messed up tables!

Message was edited by: borealforest

Hi all,

when I save a ditamap as composite document, which template file must I edit to change the layout?

So far I have modified the topic templates (task.template.fm etc.) but I have not found the template relevant for the output yet.

Update

-----------

The ditafm_output.ini file contains the line CompositeDocTemplate_1.2=ditabase.template.fm but exchanging all ditabase.template.fm files in the FM directory did not do the job.

This seems like is a very basic question so I wonder why it is not documented - or am I missing something? The only workaround I found was to manually import the EDD and formatting from my template into the FM document each time after publishing.

-----------

Robert