[Framers] Publishing HTML5 and CSS implementation in FM 2015

Bragg, Judy - Xylem judy at hypack.com
Thu Aug 24 13:51:02 PDT 2017


Hi all,

I've been learning to publish to HTML5  from FM 2015 and I have a couple of "problem paragraph styles" and I'm hoping someone here has a fix suggestion.  Here's what I'm doing:

The Beware, Note, Important and Tip paragraph styles all begin with the corresponding tag word and are configured with hanging indent to accentuate the tag word.  I have 3 note styles, each indented a different amount to align with BodyText (Note0) and list level indents (Note1, Note2). The other styles are configured to make their tag word extend into the side head in the PDF output, but I don't think that makes a difference in the HTML5 output, which is formatted based on an imported CSS.
[cid:image004.png at 01D31CF6.47C51FF0]
Until recently, I've been typing & formatting that tag word manually each time.  Now, I'm trying to let FM 2015 do it by configuring the paragraphs to "autonumber" the paragraph with the tag word, and each tag word has a distinct character style applied.

Here's the problem: Tip, Important, Note1 & Note2 all render correctly in the HTML5. The Beware and Note0 styles appear correctly except no character style is applied to the tag word.  It's extra troubling because the Beware and Important styles are almost identical--the only difference is the text and character style of their tag words-- but 1 works and the other doesn't.

When I look in the source code, the paragraphs that render correctly, have span tags that apply the character style (class) to the tag text.  For some reason, those other 2 do not and their tag words appear in the default paragraph (body) font.
Important Style works:

-          CSS

p.ImportantP {

              margin-left:54pt;

              text-indent:-.75in;

              background-color:CCE4FF;

}

p.ImportantP:before {

                     content:Important: \0020;

}

span.ImportantC {

                 font-weight:bold;

                 font-variant:small-caps;

                 color:#bc0c3d;

                 font-style:normal;

                 font-size:11pt;

}

-          OUTPUT:
<p dir="ltr" class="ImportantP"><span class="ImportantC">Important:</span> All
 data should be logged on the <?rh-udv_start name="SurveyDredgepack" ?>SURVEY or DREDGEPACK(r)<?rh-udv_end ?> computer.
 </p>

Beware style doesn't.

-          CSS:

p.WarnP {

              margin-left:54pt;

              text-indent:-.75in;

              background-color:CCE4FF;

}

p.WarnP:before {

                  content:beware: \0020;

}

span.WarnC {

              font-weight:bold;

              font-variant:small-caps;

              color:#bc0c3d;

              font-style:normal;

              font-size:11pt;

}

-          OUTPUT:

<p dir="ltr" class="WarnP"> Beware! <span style="padding-left: 27pt;" class="FMAutoNumber_1"></span>Take care about archiving files that may be contained in more than one LOG file. If you archive a file contained in more than one cata­log, it will be unavailable to any catalogs of which it is a member in your Data Files list.</p>
Where is the FMAutoNumber_1 class from? (It's not in the CSS) And why does it appear in 2 styles, but not the others?

I'm out of ideas. How about you?

Judy Bragg
Technical Writer/QC
HYPACK - A Xylem Brand
56 Bradley St.
Middletown, CT 06457
O: +1.860.635.1500
Judy.bragg at xyleminc.com<mailto:Judy.bragg at xyleminc.com>
www.hypack.com<http://www.hypack.com/>
[Email Logo]
[HYPACK 2018 Email Banner]

CONFIDENTIALITY NOTICE: This e-mail, including any attachments and/or linked documents, is intended for the sole use of the intended addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any unauthorized review, dissemination, distribution, or copying is prohibited. If you have received this communication in error, please contact the original sender immediately by reply email and destroy all copies of the original message and any attachments. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Xylem Inc.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6946 bytes
Desc: image001.jpg
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20170824/6110ca82/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 15874 bytes
Desc: image004.png
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20170824/6110ca82/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 20084 bytes
Desc: image005.jpg
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20170824/6110ca82/attachment-0001.jpg>


More information about the Framers mailing list