Fact Sheet Fusion FAQs

Fact Sheet Fusion Frequently Asked Questions

Fact Sheet Fusion

Can I view and edit the Topic text HTML code directly?

Yes, version 2 editor has an additional tab called ‘Code’. Click this to view and/or edit the HTML directly. Ensure your code changes are well formed.

Fact Sheet Fusion editor HTML code view option

Fact Sheet Fusion editor HTML code view option

Can version 1 and 2 be installed at the same time?

Yes, both versions can be installed at the same time. You must install each version to its own unique location. By default version 2 setup package will install to a separate folder.

Does Fact Sheet Fusion support the export of PDFs?

Yes, Fact Sheet Fusion supports exporting PDFs.

Fact Sheet Fusion PDF Export option

Fact Sheet Fusion PDF Export option

 

Fact Sheet Fusion PDF settings dialog

Fact Sheet Fusion PDF settings dialog

Does Fact Sheet Fusion work on a Mac (OSX) or Linux?

Yes, Fact Sheet Fusion will work under virtual Windows environments under OSX and Linux. If you need a virtualization solution try Virtual Box, free from www.virtualbox.org.

What are the system requirements for Fact Sheet Fusion?

See the following System Requirements page for this information.

Note: You do need a privileged account (e.g. Administrator rights) to install Fact Sheet Fusion.

Where’s the save button?

There is no save button in the main interface. Saving is done automatically when you move between topic or entities.

Why are there no font type options in the editor?

There are no font type selection options in the editors main toolbar because the font type and text sizes are controlled by the export template you select. The idea for topic text is to only select general formatting and layout options such as heading sizes, bold, italics, indenting, lists, and tables etc. This may look somewhat like “plain text” in the editor, but the idea is to let the export template do all the hard work when it comes to applying the look of the fact sheet.

For example, if you were to individually apply formatting such as font type and size to your topic text, which would take additional time, and found it didn’t look as good as you thought in a browser, then you would need to re-edit all the topics where these formats were applied. Where as if you have the topic text formatted with just heading types, paragraphs and no specific formatting, the export template will have definitions as to what these should look like. In this case if you need to make a change, it would just be a matter of simply adjusting the template style sheet, rather than potentially thousands of topic entries!

Why can’t I edit the caption of my media item or it some of its properties?

You may be looking the media caption and properties via the Derived Properties view. That is the media item is inheriting its caption and properties from the media library. If you need to change the media items global properties or caption you can change the view to the ‘Library Properties.

Derived Properties or Library Properties

Derived Properties or Library Properties

Or if you only wish to make a change to this one instance you can set the Media Object Derived property to True.

Media Object Derived Option

Media Object Derived Option

From the Help…

Media Properties – Inherited vs Derived
It is important to understand how media is handled in Fact Sheet Fusion. When media is added to a project via the Media Manager , default properties such as watermarks, copyright, photographer and caption etc can be added against the media. This information and the properties associated with the media are automatically available when attached to a Topic, Entity or Glossary Term. This concept is referred to as inheritance. This saves you from having to enter the same information over and over again each time the image is reused. However there are circumstances where the properties and information associated with a media item need to be customized. If these changes are not global in nature; and you don’t want these changes reflected in all the other instances where the media is attached, you can set the attached media item to be derived.

Why is there no formatting on my image captions when I export via some templates?

Problem: The problem is when the fact sheets are exported no formatting such as italics or bold etc appears in the image captions.

Solution: Some template authors may use the ‘plain text’ version of the caption, rather than the formatted caption as it guarantees clean text for the image caption and won’t interfere with image viewing scripts such as Lightbox. If you prefer to use the formatted edition of your media captions then you easily change the template to do so.

Open your templates folder and look in the sub-folder called ‘fs_template’. Assuming the template is based on a default FSF v2 template you will see the image processing template called ‘media_image.xslt’. Open this in a text editor such as Notepad++ and look for the following block of code:

<xsl:if test="captionalttext !=''">
<xsl:attribute name="title">
<xsl:value-of select="captionalttext"><xsl:text> </xsl:text>
</xsl:value-of></xsl:attribute>
</xsl:if>

The above code adds an attribute called ‘title’ to the images HREF tag, which is used by the Lightbox script. The title text is derived from the captions alt text,which the plain text version of the caption. You can change this to use the regular ‘formatted’ caption text by changing it to:

<xsl:if test="caption !=''">
<xsl:attribute name="title">
<xsl:value-of select="caption"><xsl:text> </xsl:text>
</xsl:value-of></xsl:attribute>
</xsl:if>

Further below this section is where the image caption is rendered below the image:

<xsl:if test="caption !=''">
<xsl:value-of select="captionalttext" disable-output-escaping="yes">
</xsl:value-of>
</xsl:if>

Change this to use formatted caption text like so:

<xsl:if test="caption !=''">
      <xsl:value-of select="caption" disable-output-escaping="yes"></xsl:value-of>
</xsl:if>

Note: As always we recommend backing up your template before attempting any customisations. You must take care when editing XSLT as any broken tags or missing tags will prevent the template from working.