Quantcast
Channel: Adobe Community : Popular Discussions - FrameMaker Structured
Viewing all 66580 articles
Browse latest View live

FrameMaker 2017, DITA Keys, and the Keyspace Manager

$
0
0

Hi all,

 

I'm having a difficult time absorbing how FrameMaker 2017's support for DITA keys works.

 

I have a top-level map:

 

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

<title>Put Book Title Here</title>

<mapref href="keys.ditamap" format="ditamap"/>

<topicref .../>

<topicref .../>

</map>

 

that references a lower-level "keys" map, where all the key definitions are kept:

 

<map>

  <keydef keys="var1">

    <topicmeta><keywords><keyword>This Product Name</keyword></keywords></topicmeta>

  </keydef>

</map>

 

Then I reference these keys in my topic files:

 

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

<title>My Topic Title</title>

<body>

  <p>VARIABLE VALUE: <ph keyref="var1"></ph></p>

</body>

</topic>

 

When I open a topic in the editor, the variable name is blank:

 

 

When I save this topic as a PDF, or when I save the top-level ditamap as a PDF, the variable value is not shown.

 

So next I also open the keys.ditamap file, then go into the Keyspace Manager:

 

 

I'm sure what I'm actually supposed to *do* here, but I select the key map, ensure "Update Reference..." is checked, and choose OK.

 

But that doesn't do anything. The key value isn't shown in the editor, nor is it shown in the output, whether generated from the topic file or the top-level map file.

 

The only time the variable value is shown is when I generate output using DITA-OT (Structure > DITA > Generate DITA-OT Output). Otherwise, as far as I can tell, FrameMaker 2017's support for this simple keyref scenario is broken.

 

What am I missing?


Can't Save As PDF

$
0
0

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.

FrameMaker 2017 Constantly Crashing

$
0
0

Just trying to set up FM 2017; while trying to set up EDD rules for my output templates, FrameMaker is crashing constantly.

 

Usually all it takes to cause a crash is trying to scroll through structured view or expanding a collapsed tag or structure item.

 

Sometimes the crash is so bad that I have to restart my computer to get the FM processes to actually stop.

 

I sent all of the crash logs to fmerror@adobe.com but the message bounced.

 

Anything I can do? I'm currently on a 30-day trial so I can get it set up before my boss(es) pony up for licenses. I got FM11 working successfully at my previous company so I really talked it up at this new place. Not making a great first impression here, though...

 

Edit to add: I have tried uninstalling and reinstalling FM2017. I have also noticed that the crashes tend to happen with the referenced sections of EDDs. I can open the modules without too much trouble.

Table cell alignment problem in FrameMaker 7.1 XML

$
0
0

Hai All,

 

I am using FrameMaker 7.1(Structure) and trying to align the table cell through “colspec” element using the “align” attribute, it is not working. But i have tried “colwidth” (eg., “colwidth="120.5"”) it is working fine when flowing the XML in to FrameMaker.

 

I have defined the colspec in rules file also find the below.

 

element "colspec"

{

is fm colspec;

attribute "colnum" is fm property column number;

attribute "colname" is fm property column name;

attribute "align" is fm property cell alignment type;

attribute "charoff" is fm property cell alignment offset;

attribute "char" is fm property cell alignment character;

attribute "colwidth" is fm property column width;

attribute "colsep" is fm property column ruling;

attribute "rowsep" is fm property row ruling;

}

 

Please provide some solution.

 

Thanks in Advance

 

Mathew.cj

Converting Structured FM documents into unstruc. FrameMaker

$
0
0

After experiencing problems working with Structured FM via a VPN connection, we are contemplating alternative software solutions.  Is it possible to convert existing Structured FM docs into unstructured FrameMaker?  Or does anyone have a sugggestion for another Adobe software that can handle  20-100 pp. Operations & Maintenance manuals and diagnostic guides, with a large number of .wmf inmages.  We are currently required to generate. the documents in .pdf format.  Suggestions would be much appreciated.  Thank you.

Can't save ]]> in document text to XML

$
0
0

Dear colleagues,

 

I am currently evaluating a Save-as-XML problem with FrameMaker 9.0p255. The content of the document shows some XML examples which contains CDATA sections, like

 

<environment>  <var name="service"><![CDATA[Inhalt]]></var></environment>

 

Reminder: This is in the text of the FrameMaker document.

 

When I save as XML, the XML parser complains: »Error at line 140, char 77, Message: The sequence ']]>' is not allowed in character data«

 

When I open the XML file in a XML editor I see that all < are correctly escaped as &lt; and all > are left as is. The built-in Xerxes parser also reports: »The character sequence "]]>" must not appear in content unless used to mark the end of a CDATA section.«

And the XML Recommendation says:

The right angle bracket (>) may be represented using the string " &gt; ", and must, for compatibility, be escaped using either " &gt; " or a character reference when it appears in the string "]]> " in content, when that string is not marking the end of a CDATA section.

 

It seems to me FrameMaker should either write all > as &gt; to avoid the possibility that it might be used after ]].

 

Can you reproduce this issue (I can using the UserGuide structured application, by just putting ]]> in any element)?

 

Have you found a way to workaround this, maybe with a special R/W rule?

 

Thanks,

 

- Michael

Importing DITA 1.2 EDDs into templates

$
0
0

I have been modifying the DITA 1.2 EDDs for my custom features and switching in my template customizations for tags and page layout. I understand the text insets, the need to modify the inset eddmod files and update the text insets in the referencing files. However, I can't figure out the order of precedence among the EDDs and which templates to import them into to get the full set. If I import one EDD into the basetopic.template, I get errors about elements that are referenced but not defined. I try to import EDDs that define those elements to whittle down the list, but then a subsequent EDD import takes me back to more elements that are not defined. This result makes me think that importing definitions is not an accumulative process as with importing formats but a wipeout process, as in losing all memory of element definitions previously imported. Can somebody explain how this is supposed to work? It's a lot more complicated than previous versions of DITA.

 

Susan

Equation editing crash

$
0
0

I'm a long time fm user now on windows v 10, under windows 7. Here's the issue - I created an equation in a file recycled from another project but cleared of all data, using esc m m, typed it in, and shrink wrapped it using esc mp. Then to edit it, I clicked into the equation frame and got an immediate internal error, and crashed to the desktop. No, problem, just a quirk. I restarted/reopened the file and clicked into another equation frame - same result - then repeated 3-4 times. If I click into an expanded equation frame things are fine. If I open a new doc and try this, no problem. Ideas?


Defining formatting for structured FrameMaker files that will be published in RoboHelp

$
0
0

I've used unstructured FrameMaker for years, but now we're attempting to move to structured authoring (to facilitate content reuse). I just went through the tutorial in Part 1 of "Developing Structured Applications with Adobe FrameMaker 9," which shows how to define formatting within the EDD. When you define formatting this way, it looks like all paragraphs within Frame are tagged as "Body" and the formatting is derived from the EDD.

 

I've also gone through the exercise of mapping Frame styles to elements in our RoboHelp CSS and publishing a Frame book in RH. My assumption is that if I put our formatting definitions in the EDD, I cannot map styles to the RH CSS. Is this true? If not, what am I missing? Or if so, can someone point me to instructions for defining traditional Frame paragraph tags for use with an EDD?

 

Thanks!

Melanie

Tables not expanding across a sidehead+column

$
0
0

DITA 1.2 XML

FrameMaker 10.0.2.419

 

I have some tables that I want to go across my column and sidehead for my printed manuals. I have been able to change my EDD/template to place the table anchor in the sidehead and that is working just fine. That's not the problem. The problem is that the tables do not proportionally (or even absolutely) expand to the width of the column+sidehead. The table remains the width of the column, but is in the sidehead leaving a gap in the column. In my ditabase.template.fm file when I insert a table, it spans the sidehead+column. When I save a map as a composite FrameMaker file, the tables are just the width of the column, albeit starting in the sidehead.

 

At first I thought the issue might be related to colspec or colwidth as in http://forums.adobe.com/message/3906515, but that's not the case.

 

I am not using DITA-FMx (not yet, Scott), but in my searching I found a mention of a potential FrameMaker bug and I am wondering if I am running into it. It was mentioned here http://docs.leximation.com/dita-fmx/1.1/ditafmx_tables.html. But I believe the issue is specifically an issue about column widths and not column+sidehead widths. Editing out the writer use proportional widths; had no effect on my composite file.

 

I have pgwide = 1 for my tables. The tables I am looking at are of the type 'table,' not 'choicetable' or 'simpletable,' but those may also be affected. I don't know.

 

So, other than going through a book/composite FrameMaker file right before I print and manually resizing table widths, what I can I do?

 

-Lief

How to get the Figure Title to appear below the graphic, not above

$
0
0

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.

Frame 9 solution for table column + side head does not work in Frame 10 and 11

$
0
0

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

Issues with fm-indexterm

$
0
0

Hi all,

 

I am working with Framemake11 and DITA 1.2. Fm-indexterm is defined the commonElements.eddmod.fm.  I added  fm-indexterm to the general rule list for all the elements I would use it in,  such as the following:

 

(<TEXT> | ph | codeph | filepath | msgph | userinput | systemoutput | b | u | i | sup | sub | uicontrol | xref | fm-xref | cmdname | msgnum | varname | tm | note | dl | ul | ol | sl | codeblock | msgblock | fig | image | table | fn | menucascade | draft-comment | keyword | term | indexterm | fm-indexterm)*

 

 

I can insert an fm- indexterm without error, but when I save, I consistently get the following xml error:

 

Error at file C:\Untitled2.dita.058, line 38, char 47, Message: Unknown element 'fm-indexterm'

 

This is happening in tasks, concepts, and references.

 

Any ideas on what I need to do to fix this?

 

Thanks in advance. This list is a life (and time) saver.

 

Margo

Looking for MIL-STD-2361 EDD/Template or DTD.

$
0
0

I need to create an Army Depot-Level maintenance manual using MIL-STD-2361 in structured FrameMaker. Does anyone know where I might find a template/EDD for this? If not, can anyone direct me to just the plain DTD? I will be creating XML and PDF files for output.

 

Thank you!

Whitespace deleted when saving FM > XML

$
0
0

In FM 11, when I save a FM document into XML, the whitespacing between inline elements and after cross-refs is removed. Did anyone experience the same problem? Any solution available?

 

Ann


Nested tables

$
0
0

Hi all,

there is some Information in the Framemaker help how to nest tables in structured documents but I simply don't understand how to implemend this. This is a DITA document and I know that nesting tables is very bad style. However it is a requirement and after all DITA does support it.

 

In unstructured documents we used anchored Frames in table cells. The approach for structured documents seems similar:

"Select a graphic element for empty anchored frames in the Element Catalog, and click New Frame"

 

I wonder how I can accomplish this. In the EDD I would have to set up an element (perhaps a dedicated paragraph class) to insert an anchored Frame in which then the table is inserted.

 

Has anybody succeeded in using nested tables in structured documents with Framemaker?

 

Robert

Toolbars and Tools Palette show color AND grey Icons

$
0
0

Running FMv12 on Win7.

  1. Both sets of icons are trying to show. However, Toolbars are cut off so only left several icons show, and remaining toolbar is blank all the way to right side of program window. Toolbar separators are shown all the way across, but segments are empty.
  2. At same time, Tools Palette, docked to left side of screen, shows dual set of icons also, but they are jumbled. That is, they are not neatly arranged in two columns, and color or grey set is trying to display on top of the other, slightly offset. As if trying to display two sets of two columns, but overlapped.
  3. * All above display correctly when FM first starts. Then, when User hovers something to use it, before he clicks, the screen changes as if tooltip timing, going to fail mode described above.  Recovery requires restarting FM.
  4. Also, document zoom, and other controls at bottom, are invisible until mouse hover. User has to hunt to find, and then with hover, controls appear as if tooltip; and then click works normal. Different from 3 above, these controls do not show at FM start/document open.

 

What we've tried:

Screen/Display Resolution. Tested high and low settings.

Undocking toolbars, palette, and document window. No effect.

Different combinations of Color/Grey and Large/Normal icon settings in preferences. Settings take affect correctly, but above symptoms still present.

 

Any help, please?

Dave

Changes to the structured application settings via the Structured Application Designer leave the structapps.fm file with invalid structure.

$
0
0

FYI.

 

With both FM 11 & 12 saving a Structured Application via the Structured Application Designer leaves the structapps.fm file (%appdata%\Adobe\FrameMaker\[11|12]) with invalid structure, if the element RulesSearchPaths is present.  I have reported this to Adobe as bug #3943816.

 

The scenario is most probably unlikely as most of the time an application would use the default search paths for rules.  I have chosen to use the element due to the previously reported entity mapping errors (see Incorrect entity mapping in FrameMaker 11 and 12 - A FYI!). I have placed screen snaps of the before and after to illustrate the problem.

 

 

RulesSearchPaths.PNG

The scenario is the same for applications in the Global Application Definitions, i.e adding a RulesSearchPaths will cause the global structapps.fm file to have invalid structure if the Structured Application Designer is used to Save the application.

 

An important note is that is not necessary to make changes to the structured application definitions in ether scenario.  Why the Save or Save As buttons are active when there have been no changes made is another question, probably linked to the prompt to save changes, when none have been made, when either Edit Application Definitions or Edit Global Application Definitions are clicked.

 

Jon

java.lang.OutOfMemoryError: Java heap space

$
0
0

I am using FM 12 to output PDF by using DITA-OT. But I get the following message:

 

 

BUILD FAILED

D:\DITA-OT1.8.5\build.xml:44: The following error occurred while executing this line:

D:\DITA-OT1.8.5\plugins\org.dita.pdf2\build.xml:150: The following error occurred while executing this line:

D:\DITA-OT1.8.5\plugins\org.dita.pdf2\build_fop.xml:175: java.lang.OutOfMemoryError: Java heap space

  at org.apache.commons.io.output.ByteArrayOutputStream.toByteArray(ByteArrayOutputStream.java :237)

  at org.apache.commons.io.IOUtils.toByteArray(IOUtils.java:219)

  at org.apache.fop.fonts.truetype.FontFileReader.init(FontFileReader.java:45)

  at org.apache.fop.fonts.truetype.FontFileReader.<init>(FontFileReader.java:74)

  at org.apache.fop.fonts.truetype.TTFFontLoader.read(TTFFontLoader.java:104)

  at org.apache.fop.fonts.truetype.TTFFontLoader.read(TTFFontLoader.java:91)

  at org.apache.fop.fonts.FontLoader.getFont(FontLoader.java:205)

  at org.apache.fop.fonts.FontLoader.loadFont(FontLoader.java:154)

  at org.apache.fop.fonts.FontLoader.loadFont(FontLoader.java:115)

  at org.apache.fop.fonts.autodetect.FontInfoFinder.find(FontInfoFinder.java:251)

  at org.apache.fop.fonts.FontAdder.add(FontAdder.java:58)

  at org.apache.fop.fonts.FontDetector.detect(FontDetector.java:95)

  at org.apache.fop.fonts.FontInfoConfigurator.configure(FontInfoConfigurator.java:94)

  at org.apache.fop.render.PrintRendererConfigurator.buildFontList(PrintRendererConfigurator.j ava:109)

  at org.apache.fop.render.PrintRendererConfigurator.setupFontInfo(PrintRendererConfigurator.j ava:132)

  at org.apache.fop.render.intermediate.IFUtil.setupFonts(IFUtil.java:170)

  at org.apache.fop.render.intermediate.IFRenderer.setupFontInfo(IFRenderer.java:188)

  at org.apache.fop.area.RenderPagesModel.<init>(RenderPagesModel.java:75)

  at org.apache.fop.area.AreaTreeHandler.setupModel(AreaTreeHandler.java:135)

  at org.apache.fop.area.AreaTreeHandler.<init>(AreaTreeHandler.java:105)

  at org.apache.fop.render.RendererFactory.createFOEventHandler(RendererFactory.java:358)

  at org.apache.fop.fo.FOTreeBuilder.<init>(FOTreeBuilder.java:105)

  at org.apache.fop.apps.Fop.createDefaultHandler(Fop.java:100)

  at org.apache.fop.apps.Fop.<init>(Fop.java:78)

  at org.apache.fop.apps.FopFactory.newFop(FopFactory.java:297)

  at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:109)

  at org.apache.fop.tools.anttasks.FOPTaskStarter.renderInputHandler(Fop.java:653)

  at org.apache.fop.tools.anttasks.FOPTaskStarter.render(Fop.java:676)

  at org.apache.fop.tools.anttasks.FOPTaskStarter.run(Fop.java:534)

  at org.apache.fop.tools.anttasks.Fop.execute(Fop.java:366)

  at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)

  at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)

 

Can anyone show me how to fix it?

 

[Message moved to Strucutred Forum by moderator]

Converting structured FM to DITA

$
0
0

Hello,

 

I have received structured FM file from a client and I would like to convert this file to DITA.

 

I have tried to achieve this several times by restarting from the beginning and by reading all the doc I could find, but I cannot manage to get my XML file.

 

Below are the steps I followed:

  1. Open the file (2 Safety.fm).
  2. Create a new structured application (named "TEST") with no DTD, no read/write rules, etc, only template.
  3. Define structured application (TEST) for the document 2 Safety.fm.
  4. Export elements catalog as EDD.
  5. Save this EDD as a DTD.
  6. Save 2 Safety.fm as XML.
  7. Added line <!DOCTYPE chapter SYSTEM ".... DTD\test2.dtd"> in the XML file to declare the external DTD obtained at step 5.
  8. Tried importing XML file into FM but there's many elements appearing in red in the structure view, there's no formatting, and errors appear in the console (below are 2 of them translated from French, sorry about that) :

 

Error at line 34, column 59, Message : Empty invalid content for content model '(entry)+'.

Error at line 75, column 30, Message : Attribute '{http://www.w3.org/2000/xmlns/}fm' has not been declared for element 'module'.

 

 

Now I have a few questions :

  • I don't understand the error with undeclared http://www.w3.org/2000/xmlns/ attribute, can someone help me on this point ?
  • Is it now that I have to write the read/write rules to remove the errors above ? Is the StructureTools / New read write rules method the right method to create these rules ?
  • About formatting, will declare a template in the TEST application will be sufficient to get everything looking as in the FM file ?

 

Thank you very much in advance for your explanations and for enlightning me on this matter.

 

Regards.

Viewing all 66580 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>