Hi Everyone,

Glad to see some other FrameMaker users out there, as I've been feeling on a bit lonesome lately on my new position.

A bit of background... I was recently hired as a contractor to help a company maintain and re-do some FrameMaker documentation in a Structured environment. Big manuals, many 300+ pages, full of diagrams, tables, etc. I am the only FrameMaker user here, having previously been experienced with unstructured FrameMaker, but not with structured...

One of my primary tasks is to convert old unstructured framemaker documents, as well as non-framemaker documents (interleaf) into Structured Framemaker. A previous contractor made an attempt at setting up some Master EDD docs as well as Master Style templates, which do work for new documents, but I'm not convinced that they are really set up correctly for the main task of being a recepticle for converting these other docs.

So, here's a few questions I have:

1. Is my thought correct that if the main goal is to convert into Structured Frame, then the main templates and EDD may possibly need some extra elements and hierarchy that is specifically there to help be able to make the conversion to Structured more automatable via conversion tables?

2. A big difficulty I am having is with Tables. I can't seem to quite grasp the best or correct way to do tables within the Structured format. Should there be one element that is called "Table" that works for all tables, and then this is wrapped in something to identify the formatting for a specific type of table? Or should each type of table be it's own independent element? Or is there no choice on this?  I can't tell if there are standard pre-defined table elements that I shouldn't be messing with, or whether these need to be defined by me?

3. For example, the previous person who set up the EDD (or modified some other EDD, to be more precise), has different names for the standard table elements. For example, instead of what I presume are the standard TITLE, HEADING, BODY, FOOTING, ROW, CELL, there are elements called THead, Tbody, Tfoot, Trow, Tentry, and one called TGroup that is not a standard table part. Is this good practice to have these be different? Or is this just creating an extra layer of confusion?   I can't seem to be able to use the conversion table to get this stuff to heirarch these correctly, but I don't know if it is somehow because of the different names, and I should be referencing these table elements somehow differently.

Well, as you can see, I am a bit lost.  Any thoughts, words of wisdom, or examples of good ways to do things would be appreciated.

Thanks!

Darren

I'm looking for a guide explaining all the operators that may be used in the Wrap this object or objects column of a conversion table. Can someone please point me in the right direction?

Thanks.

Hi there,

I have internal cross-references between elements of the document as well as external references to elements of other documents. The external references working fine, but when I open a document with internal cross references a get the message "No cross-reference ID specified for the element (Xref)". But the element I link to has an ID, and my xref element refers to this ID.

What did I do wrong?

Greetings.

Frame Maker 11 reports an error if an element name is declared more than once in XSD. However Dot.NET 4.0 validation with the same XSD is OK with such model and validates the different modeled elements with the same name (e.g. fett) correctly. We need the "double declaration of the same element" feature in Frame Maker 11 in a big migration project. We migrate  SGML data to XML. How can we solve this?

Hint: we explicitly want to prohibit an endless recursive nesting of elements!

Sample XSD:

<xs:schema xmlns="http://tempuri.org/test-rekursion" xmlns:tr="http://tempuri.org/test-rekursion" elementFormDefault="qualified" attributeFormDefault="unqualified" targetNamespace="http://tempuri.org/test-rekursion" xmlns:xs="http://www.w3.org/2001/XMLSchema" > <xs:group name="inlineBase"> <xs:choice> <xs:element name="sup" type="xs:string" /> <xs:element name="sub" type="xs:string" /> <xs:element name="keyword" type="xs:string" /> <xs:element name="inline-graphics" type="xs:string" /> </xs:choice> </xs:group> <xs:element name="paragraph"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:group ref="tr:inlineBase" /> <xs:element name="bold"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:group ref="tr:inlineBase" /> <xs:element name="italic"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:group ref="tr:inlineBase" /> </xs:choice> </xs:complexType> </xs:element> </xs:choice> </xs:complexType> </xs:element> <xs:element name="italic"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:group ref="tr:inlineBase" /> <xs:element name="bold"> <xs:complexType mixed="true"> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:group ref="tr:inlineBase" /> </xs:choice> </xs:complexType> </xs:element> </xs:choice> </xs:complexType> </xs:element> </xs:choice> <xs:attribute name="autor" type="xs:string" /> </xs:complexType> </xs:element> </xs:schema>

Sample XML:

<paragraph xmlns="http://tempuri.org/test-rekursion" xsi:schemaLocation="http://tempuri.org/test-rekursion test-recursion2.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > Lorem ipsum <bold>dolor <italic>sit amet<sup>hoch 2</sup>, consetetur </italic>sadipscing elitr, sed diam nonumy eirmod</bold> tempor invidunt ut labore et <italic>dolore <bold>magna aliquyam<sup>hoch 3</sup> erat</bold>, sed diam voluptua</italic>. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. </paragraph>

Opening the XML in Frame Maker 11 results in following error:

XML Read Report Log Source Document: C:\Work\DOCS\120820-Base-Umstrukturierung\Bold-Italic-Test-2.xml XML Parser Messages (Document Prolog) Error at file C:\Users\t25681a\AppData\Local\Temp\FMTCCD7.tmp, line 18, char 17, Message: Element 'italic' has already been declared Error at line 19, char 15, Message: Element 'bold' has already been declared

Thanks a lot for any suggestions

Miro

Fellow Forum Members,

Does FrameMaker offer a S1000D specification publishing solution that includes a Common Source Data Base (CSDB)? And outputs an Interactive Electronic Technical Publication (IETP) as well as a PDF? 

Any info will be greatly appreciated.  Thanks in advance

Hi all,

currently I am trying to format the DITA <lq> element (long quote) to display a line above and below its content. For the line below I have tried to use a suffix rule in the EDD. I can assign any text and character formatting below the long quote without problems, but Framemaker ignores any imaged frames that I define there.

The EDD does not allow the definition of a frame directly in the suffix rule, so I am using a format change list.

This is the suffix rule in the <lq> element. It refers to the format chanhe list "line_below" (the EDD language is German):

This is the corresponding format change list that defines a frame below.

If I define any other formatting in the format change list such as red text color there are no problems at all, only the image frames are ignored.

Does anybody have an idea how to solve this?

Robert

In FM 10, whenever I open a DITA topic, the Structure View and Element Catalog display options revert to defaults that look cluttered and annoying to me. The Structure View displays all the attributes, and the Element Catalog shows all the element descriptive tags. In the Structure View, I right-click, select Attribute Display Options, and set the display option to No Attributes. In the Element Catalog, I click the Options button and unset the option Show Element Descriptive Tags. Then both windows are simple and uncluttered. When I finish editing my DITA topic, save it, and close it and then open another DITA topic, the Structure View and Element Catalog revert to the cluttered view again. This gets annoying. I looked for preferences to making my preferred views permanent, but I could not find anything in the interface, in the DITA options, in the user manual, or in the maker.ini file. I tried saving the settings as part of my DITA workspace configuration, but the preferences weren't saved with the workspace, either. I don't mind having these more elaborate views available, but I do mind not being able to control them as a preference. Does anyone have a solution for this?

Susan

I know the error is caused by using a character definition that uses the Courier font (indicating 'user input' in a technical documentation document). FM indicates that Courier is an available font.

Hi everyone,

Using the FDK I have saved a DITAMAP (referencing several concept files) as a Book with FM components and the resulting book is invalid with the highest level element of NoName.

If I select the NoName element in FrameMaker's structure view, then select concept within the element catalog and click the Change button my book is now valid after an Update Book.

Is there a way using the FDK to achieve a valid book after the save operation?

Using the FDK I am outlining a means of selecting all elements in the book, wrapping everything in a concept element, then selecting the NoName element and unwrapping it. To me this option feels like I am correcting structure as a result of not previously defining the structure of the saved book.

The newly created book file already has element definitions for concept without importing.

Could this be a case of some way specifying a template to be used during the save?

If I can provide any further details please don't hesitate to ask.

Any input at all would be much appreciated.

Using Framemaker 12.0.1.331 all publish operations crash if the document contains a UserString of 1 or more characters in a table element.  We use UserStrings in this way to hold metadata about tables such as database keys and effective dates.

The Mif looks like this:  [We would normally have an xml fragment here but this is enough to produce a crash]

<Tbl

  <TblID 10>

<UserString `A'>

  <TblTag `Format A'>

  <TblFormat

Incidently a zero length UserString doesn't result in a crash.

Looks like a bug to me.

regards,

    Colin

• 
  
• DITA / XML
• 
  
• FrameMaker binary (.fm)
• 
  

I have an issue with an attribute not being exported to XML from FM8.

Here is the excerpt from the DTD:

<!ELEMENT std.table.header (std.table.row+)>
<!ATTLIST std.table.header
  cols CDATA #REQUIRED
  rowsep CDATA "1"
>

The first issue I had was "cols" not showing up as an attribute in the Structured View. I solved with issue (with the help of MarttiP) by adding it to the EDD as shown below:

Element (Container): std.table.header
General rule: std.table.row+
Attribute list
Name: cols  Integer  Required

Now the issue I am having is on export of the XML, the "cols" attribute is not being exported and I am getting an error "required attribute 'cols' not provided". Any suggestions?

I have a large set of reference graphics in which I am changing eps to pngs, and now Frame says it is out of memory (plenty still on the box) and

then crashes, with log files like this below. Has this happeded to others? Will going to Frame 9 fix this?  Any help would be appreciated, Thanks

=== Header Begin ===
Internal Error: 7104, 6062898, 7693379, 0
FrameMaker 7.1.0 for Intel
Build: 7.1p114
Window System: MSWindows
Operating System: Windows NT 5.1 (major.minor.build: 5.1.2600 Service Pack 3)
Generated on: Monday, December 07, 2009 1:36:51 PM
To file: c:\program files\adobe\framemaker7.1\FrameLog_09.12.07_13.36.51.txt
=== Header End ===c.

=== Stack Trace Begin ===
$5c8332
$756443
=== Stack Trace End ===

=== Open Window List Begin ===
# not implemented
=== Open Window List End ===

=== Recent Commands Begin ===
=== Recent Commands End ===

=== Recent API Calls Begin ===
# not implemented
=== Recent API Calls End ===

=== Windows Relocation Information Begin ===
Application: 00400000
FrameMaker.exe: 00400000 00484000
ntdll.dll: 7c900000 000af000
kernel32.dll: 7c800000 000f6000
ADVAPI32.dll: 77dd0000 0009b000
RPCRT4.dll: 77e70000 00092000
Secur32.dll: 77fe0000 00011000
COMCTL32.dll: 5d090000 0009a000
GDI32.dll: 77f10000 00049000
USER32.dll: 7e410000 00091000
comdlg32.dll: 763b0000 00049000
SHELL32.dll: 7c9c0000 00817000
msvcrt.dll: 77c10000 00058000
SHLWAPI.dll: 77f60000 00076000
FMDBMS32.dll: 10000000 00014000
ole32.dll: 774e0000 0013d000 etc.

On saving my document as xml the table titles are not carried into the xml the file. Tbale head nd body elemets are created in xml but the table title element is created at all.

Any ideas what I have done wrong would be much appreciated.

DTD:

<!ELEMENT Table      (Tgroup) >
<!ATTLIST Table      Position  (Anywhere|TopOfPage)  "Anywhere"
                     Orientation  (Portrait|Rotated)  "Portrait" >

<!--Tgroup: Tgroup. Group of elements that go together to form a table.-->
<!ELEMENT Tgroup     (colspec*, spanspec*, Ttitle?, Thead?, Tbody, Tfoot?) >
<!ATTLIST Tgroup     ID        ID        #IMPLIED
colsep      NMTOKEN   #IMPLIED
   cols        NMTOKEN   #REQUIRED
   colwidth    CDATA     #IMPLIED
   rowsep      NMTOKEN   #IMPLIED
   tabstyle    CDATA   #IMPLIED
>

<!ELEMENT colspec  EMPTY>
<!ATTLIST colspec
   align    (left|center|right|justify|char) #IMPLIED
   char     CDATA     #IMPLIED
   charoff  NMTOKEN   #IMPLIED
   colname  NMTOKEN   #IMPLIED
   colnum   NMTOKEN   #IMPLIED
   colsep   NMTOKEN   #IMPLIED
   colwidth CDATA     #IMPLIED
   rowsep   NMTOKEN   #IMPLIED
>

<!ELEMENT spanspec  EMPTY>
<!ATTLIST spanspec
   align    (left|center|right|justify|char) #IMPLIED
   char     CDATA     #IMPLIED
   charoff  NMTOKEN   #IMPLIED
   colsep   NMTOKEN   #IMPLIED
   nameend  NMTOKEN   #REQUIRED
   namest   NMTOKEN   #REQUIRED
   rowsep   NMTOKEN   #IMPLIED
   spanname NMTOKEN   #REQUIRED
>
<!--Ttitle: TabelTitle. Table title text.-->
<!ELEMENT Ttitle     (#PCDATA | Footnote | Tcont | IndexMarker)* >

<!--Thead: Thead. Heading table row.-->
<!ELEMENT Thead      (colspec*, Tr+) >

<!--Tbody: Tbody. Tbale body composed of rows.-->
<!ELEMENT Tbody      (colspec*, Tr+) >

<!--Tfoot: Tfoot. Tabel footer row.-->
<!ELEMENT Tfoot      (colspec*, Tr+) >

<!--Tr: Tr. Table row composed of table cells-->
<!ELEMENT Tr         (Td+) >

<!--Td: Td. Table cell containing text.-->
<!ELEMENT Td         (#PCDATA | Para | Footnote | XRef | Part |
                              PartNumber | PartDescription | Graphic |
                              IndexMarker)* >
<!ATTLIST Td         VertAlign  (Top|Middle|Bottom)  "Top"
                     HozAlign  (Left|Centre|Right)  "Left" >

<!--Tcont: Tcont. Table continuation.-->
<!ELEMENT Tcont      EMPTY >

EDD:

Element (Container): Table
General rule:  Tgroup
Attribute list
Name: Position  Choice  Optional
Choices: Anywhere, TopOfPage
Default: Anywhere
Name: Orientation  Choice  Optional
Choices: Portrait, Rotated
Default: Portrait
Automatic insertions
Automatically insert child: Tgroup
Text format rules
In all contexts.
Use paragraph format: Table
If context is: [Position = “TopOfPage”]
Pagination properties
Start position: Top of page
Tgroup. Group of elements that go together to form a table.
Element (Table): Tgroup
General rule: Ttitle?, Thead?, Tbody, Tfoot?
Attribute list
Name: ID  Unique ID  Optional
Control flags: Read-only
Initial table format
If context is: Table < RevDetails
Table format: RevisionDetails
Ttitle. Table title text.
Element (Table Title): Ttitle
General rule: (<TEXT> | Footnote | Tcont | IndexMarker)*
Text format rules
In all contexts.
Use paragraph format: TableTitle
Thead. Heading table row.
Element (Table Heading): Thead
General rule: Tr+
Tbody. Tbale body composed of rows.
Element (Table Body): Tbody
General rule: Tr+
Tfoot. Tabel footer row.
Element (Table Footing): Tfoot
General rule: Tr+
Tr. Table row composed of table cells
Element (Table Row): Tr
General rule: Td+
Td. Table cell containing text.
Element (Table Cell): Td
General rule: (<TEXT> | Para | Footnote | XRef | Part | PartNumber | PartDescription | Graphic | IndexMarker)*
Attribute list
Name: VertAlign  Choice  Optional
Choices: Top,Middle,Bottom
Default: Top
Name: HozAlign  Choice  Optional
Choices: Left,Centre,Right
Default: Left
Text format rules
If context is: Tr < Thead
Use paragraph format: CellHeading
Else
Use paragraph format: CellBody
If context is: [VertAlign = “Top”]
Table cell properties
Vertical alignment: Top
Else, if context is: [VertAlign = “Middle”]
Table cell properties
Vertical alignment: Middle
Else, if context is: [VertAlign = “Bottom”]
Table cell properties
Vertical alignment: Bottom
If context is: [HozAlign = “Left”]
Basic properties
Alignment: Left
Else, if context is: [HozAlign = “Centre”]
Basic properties
Alignment: Center
Else, if context is: [HozAlign = “Right”]
Basic properties
Alignment: Right
Tcont. Table continuation.
Element (System Variable): Tcont
System variable format rule
In all contexts.
Use system variable: Table Continuation

How to to copy FrameMaker book to a different folder path using FrameMaker API ?

You've got to love error messages and the people who put them together. On the one hand they can be useful and tell you (or at least guide you in the right direction to) the problem so you know not to do it again; on the other hand they're plain mystifying.

I'm working in WinXP with structured FM7.2. What does 'unexpected purge 4000' mean? I received this message while working in a table, however it didn't result in me losing any work (which is good). It's as mystifying to me as 'A Type 11 error has occured' (yes, I used to work with Macs).

Advice appreciated.

Cheers

Carl