Soft hyphens show up as dashes in content or TOC
When you use soft hyphen characters in FrameMaker, the characters are correctly passed into the output. Currently, the only browser that seems to display the correct behavior (showing the hyphen only if a word is broken at the end of a line of text) is Internet Explorer 7.0. Incorrect behavior in any other browser is evidence of a deficiency of the browser, rather than an ePublisher bug.
The best solution is to create a character map entry that removes the soft hyphen so that it will never appear in the output. Search the existing solutions for details on the method; the entry you'll want to add is:
In HTML Help, the problem is replicated in the table of contents (hyphens appear where they should not), and content passed to the TOC is not processed by the character maps, so the solution above will not apply.
Instead, it requires an override to a file called toc.xsl, located by default in the ePublisher Pro installation directory, here: ePublisher Pro\Formats\Microsoft HTML Help 1.x\Transforms\
Perform an override on that file, and open it in any text- or XML-editing application. Locate the "TOCText" template. Replace the whole template with this code:
<xsl:template name="TOCText"> <xsl:param name="ParamEntry" /> <xsl:variable name="VarText"> <xsl:call-template name="Paragraph"> <xsl:with-param name="ParamParagraph" select="$ParamEntry/wwdoc:Paragraph" /> </xsl:call-template> </xsl:variable> <xsl:variable name="VarFixSingleQuotes" select="wwstring:ReplaceWithExpression($VarText, '[‘’]', $GlobalSingleQuote)" /> <xsl:variable name="VarFixDoubleQuotes" select="wwstring:ReplaceWithExpression($VarFixSingleQuotes, '[“”]', '&quot;')" /> <xsl:variable name="VarRemoveSoftHyphens" select="wwstring:ReplaceWithExpression($VarFixDoubleQuotes, '­', '')" /> <xsl:value-of select="$VarRemoveSoftHyphens" /> </xsl:template>
That will result in the removal of the character from the TOC entries. When the CHM is compiled, the soft hyphens will not appear. Save toc.xsl and regenerate your project to apply the changes.
This issue is represented in our development database as defect #WWEP2530, and it will be listed in the release notes for the ePublisher version in which is is fixed.