Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
0

Conversion of the highest valid element passing attributes?

Guest
Mar 02, 2012 Mar 02, 2012

Copy link to clipboard

Copied

Hello,

Question. I am trying to convert a large book. I would like to assign some attritubes to the highest valid element.

My conversion table looks like this:

RE:RootElement

Document[SpecTitle=”titlehere”
& SpecNumber=”XXXXX”

& Revision=”A01”

& ChapterName=”??”]

RE        

After the conversion, the root element is red with the attributes assigned. When I change it to the same root element in my element catalog all the attributes disappear.

Is it wrong to want to assign attributes to the highest valid element (root element)?

If it is "legal" to assign attributes is there something wrong with my conversion table?

Thanks for any help!

Margaret

TOPICS
Structured

Views

645
Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guide ,
Mar 02, 2012 Mar 02, 2012

Copy link to clipboard

Copied

Margaret,

After you applied the structure with your conversion table, did you import your EDD into the structured document? If not, FrameMaker has no way of knowing what is and is not allowed in your structure. I have never changed an element with invalid attributes to another one; so I am not sure whether FrameMaker would keep them or delete them.

In any event, try importing the EDD before checking the validity of the structure. Without it, FrameMaker is just guessing.

Van

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Mar 02, 2012 Mar 02, 2012

Copy link to clipboard

Copied

Yes I did import the edd and template into the new structure doc. The

converted RE doesn't match the edd. So.... that must mean my edd needs to

match my RE in the conversion table including the assigned attributes?

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guide ,
Mar 02, 2012 Mar 02, 2012

Copy link to clipboard

Copied

Yes, the EDD has to specify that the root element is allowed at the highest level. AND the EDD has to specify that the attributes are indeed part of the root element's definition; of course, the EDD does not have to specify the values of the attributes.

NOTE that the EDD can specify that several elements are allowed at the highest level. There is no restriction to just one.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Mar 02, 2012 Mar 02, 2012

Copy link to clipboard

Copied

Shoot. I have the attributes in the EDD for the RE or Highest Valid

Element. I was wondering if I had to actually define the "Strings" in the

EDD to make this legal but noticed I could not.

I have other attributes getting assigned in the conversion process but the

RE is not behaving.

I have a feeling there is a bug somewhere here.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guide ,
Mar 06, 2012 Mar 06, 2012

Copy link to clipboard

Copied

LATEST

Margaret,

I believe you are correct. It appears to be a bug to me also.

My conversion table does not set any attributes for the root element. To test this, I added an attribute to the root element:

RE:RootElementChapter[title=”chapter”]

When I applied the structure to an unstructured document, the root element was:

Chapter[title=”chapter”]

FrameMaker did NOT create a root element named Chapter with an attribute named title with a value equal to chapter. FrameMaker used the entire string as the NAME of the root element.

I suggest filing a bug report.

Van

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines