FM - RH Style Mappings Save As Creates Zero Byte XML File

[Guest]

Our company has recently purchased several licenses of the new Adobe Technical Communications Suite. We have, mostly through painful "trial and error," come up with a single-sourcing process that works for our purposes. We author in FM, and our deliverables are in PDF and CHM formats. We also provide printed manuals for our customers.

One aspect of this product that is not working as advertised is the "save as" feature provided during the FrameMaker - RoboHelp Style Mappings process. The XML file that is created is a zero byte file.

Is there any estimate as to when this feature might be fixed? If it worked it would be a real time-saver!

Thanks,

Tim C @ Harris

[Peter Grainge]

Welcome to the forum.

I just attended a conference where to FM to RH process was described to us. I haven't yet got into all the nooks and crannies but I will be looking at this when I get back home.

Meantime, if you would like to send me a screenshot of the dialogue that contains this Save As, it might help me answer you sooner rather than later.

Please include a link to this thread when you email me via my site.

[Peter Grainge]

I have been asked to check if you have applied the 7.0.1 patch to RH?

[Guest]

Yes, we have applied all updates/patches to all products in the suite. We have work arounds in place for this "zero byte" XML file problem until such time as this feature is fixed.

[Peter Grainge]

OK, I'll report back on that.

Watch this space.

[JainVivek]

This is a bug in save as XML command. However, Mapping file is stored by RoboHelp as a text file and you can still re-use the same. For copying the mappings from one project to another, please use the following workaround -
1. Copy the RHFrameStyleMappings.APJ file to another project
2. Delete the CPD file of the new project
3. Start RoboHelp project
4. The style mappings show up in the RoboHelp project

[Guest]

Thank you for the response. I have tested this workaround and found it to do the job nicely. I have incorporated this process into our Single Sourcing procedure. This workaround does make the initial import process quite a bit simpler!

Thanks again for your help. We look forward to this bug being repaired in a future TCS update.

Regards,

Tim C @ Harris

[Guest]

For what it's worth, I've tried the Save Mappings feature with RH 7.0.1 and it creates an XML file correctly. Styles mapped to [Source] do not appear in the XML. Here's a sample:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<mappings version="1.0" expanded="true">
<characters>
</characters>
<paragraphs>
<mapping from="h5" to="h5"/>
<mapping from="Chapter" to="[IGNORE]"/>
<mapping from="h1" to="h1"/>
<mapping from="h2" to="h2"/>
<mapping from="h3" to="h3"/>
<mapping from="Cover Title" to="[IGNORE]"/>
<mapping from="h4" to="h4"/>
</paragraphs>
<xref>
</xref>
</mappings>

[JainVivek]

The bug exists only if you use cross reference mapping. Please use the workaround till the issue is fixed.