Skip to main content
rombanks
Inspiring
March 4, 2014
Question

body text turns to cellbullet after conversion to structured

  • March 4, 2014
  • 1 reply
  • 627 views

Hello fellows,

My environment: FM10 structured, Win7

I created a conversion table with the following conversion rules. When converting an FM file to structured, for some unclear reason, the body text becomes cellbullet (bulleted list style used in table cells). Any ideas why this happens?

An additional question: how are table and figure anchors treated during conversion, and whether there is a need to add some rule for them?

Thank you in advance!

 

P:BodyAfterHeading

p[

otherprops=”AfterHead”]

body

P:Body

p

body

P:BodyIndented

p

indented

 

   

P:Bullet

p

bullet

P:BulletLast

p

bulletlast

P:BulletSub

p

bullet2

P:BulletSubLast

p

bullet2_last

P:CellBullet

p

cellbullet

p[bulleted], p[indented]*, (ul[2]|ol[2])*

li

bullet

li[bullet]*

ul

1

p[bullet2], p[indented]*

li

bullet2

li[bullet2]*

ul

2

p[cellbullet]

li

cellbullet

li[cellbullet]*

ul

cell_ulist

 

This topic has been closed for replies.

1 reply

ScottPrentice
Inspiring
March 4, 2014

Hi Rombanks...

After applying a conversion table you need to import an EDD and corresponding template in order for the formatting to get straightened out. After the conversion table, the formatting will be wonky.

Cheers,

...scott

rombanks
rombanksAuthor
Inspiring
March 4, 2014

Hi Scott,

First of all, thank you very much for your response!

I do not have a custom EDD yet, nor a structured template - just started the conversion process. In any case, this looks like a bug in Framemaker - the body text should not have become a bulleted list.

My best regards,

Roman

Inspiring
March 4, 2014

Roman,

    In a structured document, element definitions include format rules that specify how each type of element is formatted. The format rules can be context-dependent. Since your conversion table maps 8 different paragraph formats to the <p> element, the formatting of <p> needs to be context-sensitive if you want to duplicate existing format.

   To elaborate just a bit on Scott's suggestion, an EDD defines format rules that can be context-sensitive. When you apply a conversion table to a document that does not already have element definitions, FM creates preliminary element definitions. Since it is not possible to automatically deduce the contexts that cause desired formatting to change, conversion tables simply assign the same format to all occurrences of an element.

  Thus, the behavior you describe is probably not a bug, but the result of an incomplete process. The conversion table helps deduce an element structure, but it cannot build a complete EDD.

   By the way, you can use the preliminary element definitions to get started in developing your EDD. The StructureTools > Export Element Catalog as EDD command generates an EDD corresponding to the minimal element definitions built by the conversion table. You can edit the result. For example, as well as making the formatting context-senstivie, you'll probably want to change the everything-is-allowed-everywhere GeneralRules. You can also rearrange the element definitions, group them into sections, and add comments.

    --Lynne