Getting an error while generating TOC in structured framemaker 11

Hi all,

I understand the use of {first} when identifying the context of an element, such as:

If context is: {first}<Section

But what if I want to set whether Section is first inside its parent?

For instance, for this hierarchy:

<chapter>

  <section></title></section>

  <section></title></section>

</chapter>

I want to say that if <title> appears in the first <section> element within a <chapter>,  then apply a particular format.  Otherwise, apply a different format if <title> appears in a <section> that is not first within a <chapter>. -- i.e. a parent element context, if you will.

The syntax to do this is eluding me.  My EDD has a series of context rules for a <title>, including for when it appears within a <section>, like this:

Else, if context is: Section < Chapter
     If context is: <{first}<Chapter
        Use paragraph format: Heading1NoNewPage
     Else
        Use paragraph format: Heading1

Whatever syntax I try for the context rule above (that the section be first within the chapter), I get parsing errors or the rule is not read.  I've tried:

If context is: Section<Chapter{first}

If context is: <{first}<Chapter                   // invalid

If context is: Section{first}<Chapter          // applies only Heading1; never reads this

If context is: Section < {first} Chapter       // invalid

Any ideas if there is a syntax that allows you to set a context for  the parent element, and not just for the element in question?

Thanks for anyone's help on this.

Shelley

Shelley Hoose

Rogue Wave Software

Senior Documentation Developer

I'm using FrameMaker 9 to author DITA content. Adobe markets FrameMaker 9 as a DITA Editor.

The DITA standard specifies that all references (regardless of type) are a standard URL format.

FrameMaker 9, by default, is writing my references (hrefs, topicrefs, imgs, etc.) using "\" as a file seperator instead of "/".

Why is FrameMaker using Windows file path seperators and how do I convert them to use more reliable URL path seperators? I don't want to use backslashes, I want to use slashes (as everyone should).

You can see this behavior by opening up the sample DITA content included with FrameMaker, saving the file, and comparing the two versions in a text editor. Your links are essentially 'broken' if you try to view them with another XML editor. Note that FrameMaker reads the "/" seperators and resolves them just fine, then

I played around with the "Cross Platform File Naming" preferences (File menu > Preferences > General) and this didn't change the behavior.

Thanks for your help.

My EDD is set up to insert anchored frames as I import a graphic by reference. The default position is centre aligned. I would like to change this to left aligned.

Then I would like to be able to set up a fixed alignment offset on the graphic. At present I have to manually set up the position (not a major problem but I think it must be possible to get it set up as I would like).

Finally coming back in from XML the cgm files remove the alignment offset and place the graphic at the very left of the anchored frame.

Any pointers woulod be much appreciated.

Thanks

Edd

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

In FDK development, I want to access registry to get information.

StringT GetDirInfoFromReg()
{
   HKEY hKey;      
    CharT       SubKeyName[]= "SOFTWARE\\airport raw data";      
     CharT      ValueName[] = "template"; 
  CharT keyValue[64];
  IntT i;
       
     BYTE        ValueData[64];      
     DWORD       Buffer; 
  StringT  key=NULL;
       
     //open key   
     if(RegOpenKeyEx(HKEY_LOCAL_MACHINE,SubKeyName,0,KEY_ALL_ACCESS,&hKey) !=ERROR_SUCCESS)      
     {      
         printf(      "Error:        Regedit        cannot        be        opened! ");      
     }      
     else      
     {      
     //read key value      
     Buffer=sizeof(ValueData);      
     if(RegQueryValueEx(hKey,ValueName,0,NULL,ValueData,&Buffer)==ERROR_SUCCESS)      
     {
          //Convert ValueDate  to StringT

    key=(StringT)ValueData//***************************Error:I can not get the right data.

     RegCloseKey(hKey);      
     }      
           
     }

  return key;

}

I don't know how to convert byte to StringT.

I'm using structured FM10 in TCS3 on Windows XP.

We upgraded from TCS1 FM8 to the current version and are having a problem with our images.  All of our window images are constructed within a table. So we have table > tgroup and then the image within the table. The image is center aligned. I select the anchored frame that contains the image and select left alignment on the Anchored Frame pod. After saving, closing, and reopening, the image reverts to its center alignment.

This worked just fine in FM8.  What could have changed?

Thanks in advance.

FrameMaker Fonts Not Being Recognized

OS: Windows 7

FrameMaker (Structured): Version 10.0.2.419

Problem:

We noticed that the PC I have does not include all of the client's fonts. We purchased the fonts based upon the Missing Fonts error FrameMaker (structured) keeps displaying. IT installed the recently purchased fonts (the fonts have the same name). Microsoft Word recognizes the fonts but for some reason when opening those source files, those fonts are not recognized/loaded by FrameMaker. Consequently, the fonts are temporarily replaced, as expected in this scenario. The same files open fine on another PC. 

This is what we tried:

• Uninstalled both Acrobat Professional (version 10.1.3) and FrameMaker 10 (10.0.2.419). Reinstalled both packages and opened the source files once again. The fonts still are not recognized. In FrameMaker they appear greyed-out in the selection field.

Could the system profile be corrupted? Years ago I remember RoboHelp repeatedly corrupting my system profile on my Windows XP system. Could a “Running out of memory” situation do this?

Any suggestions as to where to look?

Thanks in advance!

I think this is a very simple question (and apologise if I have just repeated someone else - I looked but could not find the answer I was looking for).

I have used Structured Framemaker for quite some time but am only now looking into XML output and roundtripping.

The issue I have is I cannot seem to get the read / write rules to do anything - they do not seem to interact with the writing or reading of XML.

Now I am sure that I have missed something very, very simple (and not for the first time) so it would be great if someone can tell me what I am doing wrong. So...

The Input XML script shown here has an element named "Para", as well as various other elements that are named exactly as they are in FM (Paragraph, Section, Document, etc...)

---

<Document><Title>Round Trip Test Document</Title>

<Section><Title>Section one - Waking up</Title>

<Para>This should be a standard Paragraph Element in FM <Emphasis>emphasised </Emphasis>text in

a paragraph.</Para>

<Paragraph ID = "GFJHDEAB">This is the second paragraph in the first section</Paragraph>

<Section ID = "BABBCABA"><Title>Section one point one. Tips for getting out of bed</Title>

<Paragraph>This is the first paragraph in the first nested section</Paragraph></Section></Section>

<Section><Title>Section two - making the tea</Title>

<Paragraph>This is a cross reference to <Xref IDref = "BABBCABA" Format = "Section"/></Paragraph>

<Paragraph>This section includes and anchored frame for a table followed by a graphic</Paragraph></Section></Document>

---

I want my read/write rules to map any instances of 'Para' element to the FM element "Paragraph".

So the read / write rules have the following lines:

fm version is "9.0";

  /*

* Include all ISO entity mapping rules.

*/

#include "isoall.rw"

element "Para" is fm element "Paragraph";

---

Structapps application (QuickStart) is pointing to the correct rules file:

--

But when I open the XML I get:

And the structure shows the same thing:

---

So why has the XML element 'Para' not been changed into FM element 'Paragraph'. I know that the element 'Para' is an unknown element - thus the rule telling it to map this to the 'Paragraph' element.

FM > XML

When I output from FM to XML I have followed all the instructions from the manuals and cannot get these process to work either. The Output XML is exactly the same if I have rules or not.

i.e. if I map my FM elements, to elements of the same name but all in lowercase - the output XML shows the element names exactly as they are in FM, as though there were no rules involved.

Any help would be appreciated, Cheers.

Alan

***I suspect this might be an XSL-related solution***

I've inherited a client's xml structapp that goes out to XML quite nicely, but doesn't read in the requisite idref upon opening in FM11.

The read/write rules are fairly straightforward:

element "xref"

{

  is fm cross-reference element "XRef";

  attribute "xrefstyle" is fm property cross-reference format;

  attribute "linkend"           is fm property cross-reference id;

}

However, the linkend attribute is not populated upon opening, nor is the value (which is present in the XML file) passed as the cross-ref id into FM.

Anyone have a solution?

Could this be a result of XSL parsing, and might the XSL be dropping the attribute upon import prior to application of the RWR? I haven't dug into the import XSL yet, but suspect that's where I need to go.

-Matt

I am familiar with FrameMaker. However, I have never used structured FrameMaker or DITA. I am just starting a new project and need to make recommendations.

Hi ,

I managed to make a conversion table to structure the documents of out company.I am having a proble with images.I am importing the word file to our template with a custom EDD document.When the import finishes I am having all images at almost correct places.The issue is when i apply the custom conversion table all the images at anchored at insertion point.The correct position would be at below current line.I am stuck and I can not find a solution to this.

My EDD is as follows:

EDD Version is 12.0

Structured Application: ReportPlain

F:\FramemakerBooks\Part B -Section 3.fm

April 14, 2014

Element (Container): Author

General rule:          <TEXT>

Text format rules

In all contexts.

Use paragraph format: ReportAuthor

Element (Container): Emphasis

General rule:          <TEXTONLY>

Text format rules

In all contexts.

Text range.

Use character format: Emphasis

Element (Equation): Equation

Element (Container): EquationPara

General rule:          Equation

Text format rules

Element paragraph format: Equation

Element (Container): Extract

General rule:          (<TEXT> | Emphasis | Term | Superscript | Subscript | XRef)*

Attribute list

Name: ID           Unique ID           Optional

Text format rules

In all contexts.

Use paragraph format: Extract

Element (Container): Figure

General rule:          (<TEXT> | Frame)*

Attribute list

Name: ID           Unique ID           Optional

Name: XRefLabel           String           Optional

Default:          Figure

Name: Imported           Choice           Optional

Choices:          Yes, No

Default:          No

Text format rules

In all contexts.

Use paragraph format: Figure

Element (Footnote): Footnote

General rule:          <TEXT>

Text format rules

In all contexts.

Use paragraph format: Footnote

If context is: * < Table

Use paragraph format: TableFootnote

Element (Graphic): GRAPHIC

Initial graphic element format

In all contexts.

Insert anchored frame.

Anchored Frame Object Style:FiguredCentered

Element (Graphic): Frame

Initial graphic element format

If context is: Figure[Imported = "Yes"]

Insert imported graphic file.

Else

Insert anchored frame.

Element (Container): Head

General rule:          <TEXT>

Text format rules

Count ancestors named:          Section

If level is: 1

Context label: H1

Use paragraph format: Heading1

Else, if level is: 2

Context label: H2

Use paragraph format: Heading2

Else, if level is: 3

Context label: H3

Use paragraph format: Heading3

Else, if level is: 4

Context label: H4

Use paragraph format: Heading4

Else, if level is: 5

Context label: H5

Use paragraph format: HeadingRunIn

Else

Numbering properties

Autonumber format:

If context is: {first} < Report

Use paragraph format: ReportTitle

Else, if context is: HeadingRunIn

Use paragraph format: HeadingRunIn

Element (Container): HeadingRunIn

General rule:          Head, Para+

Element (Container): Item

General rule:          (<TEXT> | Emphasis | Term | Superscript | Subscript | XRef | Para)*

Format rules for first paragraph in element

If context is: List[Type = "Plain"]

No additional formatting.

Else, if context is: List[Type = "Bulleted"]

Use paragraph format: Bulleted clean

Else, if context is: {first}

Use paragraph format: Numbered1

Else

Use paragraph format: Numbered

Element (Container): List

General rule:          Item+

Attribute list

Name: ID           Unique ID           Optional

Name: Type           Choice           Optional

Choices:          Plain, Bulleted, Numbered

Default:          Bulleted

Automatic insertions

Automatically insert child:          Item

Element (Container): Para

General rule:          (<TEXT> | Emphasis | Term | Superscript | Subscript | XRef | Footnote | Table )*

Attribute list

Name: ID           Unique ID           Optional

Text format rules

If context is: {after Head }

Use paragraph format: Body

Else, if context is: {after List}

Use paragraph format: BodyAfterHead

Else

Use paragraph format: Body

Element (Container): Part

Valid as the highest-level element.

General rule:          (Para | Footnote | Table | Section )*

Attribute list

Name: ID           Unique ID           Optional

Control flags: Read-only

Automatic insertions

Automatically insert child:          Head

Text format rules

Element paragraph format: Body

Element (Container): Purpose

General rule:          <TEXT>

Text format rules

Element paragraph format: ReportPurpose

Element (Container): Section

General rule:          (Section,Head |Section | Para | List  | Table | Figure  | HeadingRunIn )*

Attribute list

Name: ID           Unique ID           Optional

Name: XRefLabel           String           Optional

Default:          Section

Automatic insertions

Automatically insert child:          Head

Element (Container): Subscript

General rule:          <TEXTONLY>

Text format rules

In all contexts.

Text range.

Font properties

Superscript/Subscript: Subscript

Element (Container): Superscript

General rule:          <TEXTONLY>

Text format rules

In all contexts.

Text range.

Font properties

Superscript/Subscript: Superscript

Element (Table): Table

General rule:          TableTitle?, TableHead?, TableBody

Attribute list

Name: ID           Unique ID           Optional

Control flags: Read-only

Name: XRefLabel           String           Optional

Default:          Table

Control flags: Read-only

Initial table format

In all contexts.

Table format: Format A

Element (Table Body): TableBody

General rule:          TableRow+

Element (Table Cell): TableCell

General rule:          (<TEXT> | Emphasis | Term | Superscript | Subscript | XRef | Frame| Para)*

Text format rules

Element paragraph format: Bodycell

Element (Table Heading): TableHead

General rule:          TableHeadRow+

Element (Table Cell): TableHeadCell

General rule:          <TEXT>

Element (Table Row): TableHeadRow

General rule:          TableHeadCell+

Element (Table Row): TableRow

General rule:          TableCell+

Element (Table Title): TableTitle

General rule:          <TEXT>

Text format rules

Element paragraph format: TableTitle

Element (Container): Term

General rule:          <TEXTONLY>

Text format rules

In all contexts.

Text range.

Use character format: Emphasis

Element (CrossReference): XRef

Attribute list

Name: IDRef           ID Reference           Required

Control flags: Read-only

Limit values for format change list properties

First indent

Maximum: 39.0"

Minimum: 0.0"

Left indent

Maximum: 39.0"

Minimum: 0.0"

Right indent

Maximum: 39.0"

Minimum: 0.0"

Space above

Maximum: 32767.0 pt

Minimum: -32767.0 pt

Space below

Maximum: 32767.0 pt

Minimum: -32767.0 pt

Line spacing

Maximum: 32767.0 pt

Minimum: -32767.0 pt

Tab stop position

Maximum: 39.0"

Minimum: 0.0"

Font size

Maximum: 400.0 pt

Minimum: 2.0 pt

Spread

Maximum: 1000.0%

Minimum: -1000.0%

Stretch

Maximum: 1000.0%

Minimum: 10.0%

Cell margins

Top

Maximum: 32767.0 pt

Minimum: 0.0 pt

Bottom

Maximum: 32767.0 pt

Minimum: 0.0 pt

Left

Maximum: 32767.0 pt

Minimum: 0.0 pt

Right

Maximum: 32767.0 pt

Minimum: 0.0 pt

And my conversion table is:

Wrap this object or objects          In this element          With this qualifier

TC:          TableCell

P:Body          Para

P:Normal          Para

P:Heading 5          Head          head5

E:Head[head5],(Para | Frame | List | Table )*          Section          section5

P:Heading 4          Head          head4

E:Head[head4],(Para | Frame | List | Table |  [section5])*          Section          section4

P:Heading 3          Head          head3

Head[head3],(Para | List | Frame | Table | [section4])*          Section          section3

P:Heading 2          Head          head2

Head[head2],(Para | List | Frame | Table | [section3])*          Section          section2

P:Heading 1          Head          head1

Head[head1],(Para | List | Frame | Table | [section2])*          Section          section

T:Table          Table (promote)

TT:          TableTitle

TH:          TableHead

TB:          TableBody

TF:          FOOTING

TR:          TableRow

RE:RootElement          Part

P:List Paragraph          Item

Item+          List

G:          GRAPHIC(promote)

RE:RootElement          Part

I am almost done with the template"Application"I just need to place the pictures in the correct position.Can anyone point me to the right direction?

Thanks a lot in advance

Hi everyone

I was very sorry to see a recent post on the dita-users list saying that Jeremy has died. We've used Mif2Go extensively and found Jeremy incredibly helpful. The FM community won't be the same without him.

Regards

Rebecca

>>> 8/06/14 10:25 >>>

[Thread locked: earlier messages already on this subject. See: https://forums.adobe.com/thread/1492743 ]

I'd like to set the background color of running headers and footers, based on an attribute from an element in my imported XML-file.

Basically what I want is to have different colors of headers or footers for different chapters in the book (catalogue).

Is there any way to do formatting like this from the EDD or rules? Or is there some other way to achieve a similar result?

[Moved to Structured Forum by moderator]

Hello,

I am using TCS4.

I have used structured Framemaker extensively, but have never created from there.

Is there a Dummies for creating structured FM or any other sort literature that would help a beginner?

I have already watched this excellent tutorial http://tv.adobe.com/watch/structured-authoring-xml-and-dita/migrating-to-structured-framem aker-using-conversion-tables/.

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.