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

Save Ditamap As FM 11 book with components causing xrefs to disappear

New Here ,
Jan 26, 2013 Jan 26, 2013

Copy link to clipboard

Copied

When we used the Framemaker option Save
>Ditamap As > FM 10 book with components, all of our cross references were maintained.

Now for some odd reason with Framemaker 11, all the cross references are
disappearing when you save as FM 11 book with components.

We are using our own defined cross reference formats, such as heading and Page #.


This is repeatable across several machines in our office, and we have the
lastest version of Framemaker installed.

Has anyone seen this, or does anyone have any ideas? I rechecked this on a machine that has Frame 10 and it works fine there. I noticed a template folder was added to Framemaker 11 and I am wondering if we need to import our cross references formats into it.

Thanks in advance.
Margo

TOPICS
Structured

Views

1.5K

Translate

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
Community Expert ,
Jan 26, 2013 Jan 26, 2013

Copy link to clipboard

Copied

Hi Margo,

I believe you've struck upon the solution.

When working with DITA, your XML files get imported into a series of template files each time you open them. I'll wager that if you import the xref formats into those template files (make a backup of the templates folder, just in case...) that you'll get what you're looking for.

Votes

Translate

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
New Here ,
Jan 26, 2013 Jan 26, 2013

Copy link to clipboard

Copied

Turns out this was a different issue - xrefs weren't being written to the xml because of a setting in the ditafm.ini file.

Thanks for your help though. It is a good thinkg to know.

Margo

Votes

Translate

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
Explorer ,
Jul 12, 2013 Jul 12, 2013

Copy link to clipboard

Copied

Hi,
what setting was that, can you explain your solution? I am having a similar problem.

Robert

Votes

Translate

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
New Here ,
Jul 12, 2013 Jul 12, 2013

Copy link to clipboard

Copied

Hi Robert,

In the ditafm-output.ini file there is a setting uder General Options

CompositeDocTemplate_1.2=ditabase.template.fm

This is the template file used to create a composite book. Your cross-reference formats neet to be in this template.

Hope that helps.

Margo

Votes

Translate

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
Explorer ,
Jul 12, 2013 Jul 12, 2013

Copy link to clipboard

Copied

Thanks for the fast response. The template you mention is used for saving as composite documents. I am having problems with that and have shifted to saving as book with components (as you did in your original post). When I save as a book then my correct template (which also has all xref styles) is used, but yet the xrefs are still missing in the output.

I guess that my problem is different from yours then after all.

BR
Robert

Votes

Translate

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
Community Expert ,
Jul 12, 2013 Jul 12, 2013

Copy link to clipboard

Copied

Yes, the ditafm-output.ini (in the userdata\roaming\blah blah directory is used when saving an ditamap (or other xml structure) to .book with FM components.

As part of a 1-hour Adobe webinar on DITA to PDF, I'll be showing that workflow in a webinar in just under 2 hours. The registration link is

"How to" webinar: "FrameMaker DITA output to PDF" adobe.ly/14ZzI3E

I believe you will also be able to use that link to access the recording. If not, feel free to contact me for the link.

-Matt

Matt R. Sullivan

co-author Publishing Fundamentals: Unstructured FrameMaker 11

Votes

Translate

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
Explorer ,
Jul 12, 2013 Jul 12, 2013

Copy link to clipboard

Copied

Thanks that looks very interesting.

My problem is that xrefs that are valid in the DITA sources (they are resolved correctly when loading individual XML files) are not converted when I save to an FM book with components.

In the generated FM files, they look like this. As you see there is a problem with the outputclass, even though this is the correct xref name (it exists in the output files with this name).

Robert

FM_link_error.png

Votes

Translate

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
Community Beginner ,
Jul 12, 2013 Jul 12, 2013

Copy link to clipboard

Copied

Oh yes, that brings back memories, and those memories aren't good ones. We had the same exact issue.

I know I'm repeating myself and it probably doesn't make sense, but try what I suggested before if you haven't already tried it. I'm speaking from experience.

Marsha

Votes

Translate

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
Community Beginner ,
Jul 12, 2013 Jul 12, 2013

Copy link to clipboard

Copied

Hi Robert,

We save our bookmaps as a book with components and in the ditafm-output.ini General Options section, as Margo pointed out above, for the CompostiteDocTemplate_1.2, we still use the ditabase.template.fm. (CompositeDocTemplate_1.2=ditabase.template.fm).

Maybe it shouldn't, but it works for us.  

If you haven't yet tried it, give it a try.

Marsha

Votes

Translate

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
Explorer ,
Jul 12, 2013 Jul 12, 2013

Copy link to clipboard

Copied

Hi Marsha,

thanks for the hints, just to be sure in which folder do you store the ditabase.template.fm file with your xref definitions?

I am using DITA 1.1 here so I edited the corresponding CompositeDocTemplate_1.1 setting. I placed my templates into the Structure\xml\DITA\outputTemplates folder. It seems however that it is not the correct location yet.

Robert

Votes

Translate

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
Community Beginner ,
Jul 12, 2013 Jul 12, 2013

Copy link to clipboard

Copied

Where you store you templates is up to you but you must call that out in the ditafm-output.ini file as well.

In the General Options section, find this line:

TemplateDir=$STRUCTDIR\xml\DITA\outputTemplates

I changed mine to:

TemplateDir=$STRUCTDIR\xml\DITA_1.2\app\technicalContent\template\Book_Templates

HTH,

Marsha

Votes

Translate

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
Explorer ,
Jul 12, 2013 Jul 12, 2013

Copy link to clipboard

Copied

LATEST

Marsha, you're a charm! I changed the path to the xml\DITA_1.2\app\technicalContent\template\Book folder and stored my template there, now it works. The template was simply ignored in the original outputTemplates folder even with the path set correctly.

So although I am using the DITA 1.1 mode, storing a template in the DITA 1.2 directory and adjusting the path in the ditafm-output.ini file is required to fix the xrefs.

Sometimes working with Fm is like mastering black magic.

Robert

Votes

Translate

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