<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#336666">
<div class="moz-cite-prefix"><font face="Verdana">John...<br>
<br>
The mapping from elements and their context happens in the
structure application's template (which contains an EDD). The
EDD contains element definitions, which in turn contain context
rules. The context rules specify the formatting (paragraph and
character styles, or other specified properties). FrameMaker and
DITA-FMx provide default structure applications that you can use
as the basis for building your own customized apps. Rather than
just jumping in and modifying the default apps, I highly
recommend "cloning" them to create your own apps. This is a bit
more effort, but in the long run is the best way to go. While
customizing the apps, you will break something (we all do), and
it's very important to have the original apps readily available
for testing and comparison. Here's some information about
cloning the default DITA-FMx apps (a similar process can be used
to clone the default FM-DITA apps) ..<br>
<br>
<a class="moz-txt-link-freetext" href="http://docs.leximation.com/dita-fmx/1.1/?ditafmx_cloningtapps.html">http://docs.leximation.com/dita-fmx/1.1/?ditafmx_cloningtapps.html</a><br>
<br>
When you create a FM book from a DITA map using default FM-DITA,
you save your ditamap as a "book with FM components". The
chapter files are formatted with the current DITA structure
application template (and underlying EDD). You can either use a
customized app to get different formatting or you can import
alternate templates into the files after the book has been
created.<br>
<br>
If you're using DITA-FMx, use the "Generate Book from Map"
command. This performs various book-build operations (as defined
in the Book Build Settings dialog). If you set up a book-build
INI file, you can define the pagination and numbering properties
of the chapter files as well as the properties of any generated
lists you include in your bookmap. This INI file also lets you
specify additional (unstructured) files to include in the
generated book (like a title page or other files). As well .. if
you have metadata in you map (like copyright or version
information), you can specify that those values be imported into
the generated and included files as FM variables. This video
provides an overview of this process ..<br>
<br>
<a class="moz-txt-link-freetext" href="http://blog.leximation.com/2010/03/pdf-publishing-with-dita-fmx-1-1/">http://blog.leximation.com/2010/03/pdf-publishing-with-dita-fmx-1-1/</a><br>
<br>
Note that DITA-FMx 1.1 does not support DITA 1.2. When DITA-FMx
2.0 is available, that will support DITA 1.2. If you're using
FM11, be sure to start with the DITA 1.1 apps or the default
DITA-FMx apps as the basis for your customized apps.<br>
<br>
When publishing to HTML-based output, it really depends on what
tool you use, but the mapping would happen in that tool.
DITA-FMx provides a direct integration with DITA2Go and the
DITA-OT. If you have TCS and want to use RoboHelp, your best bet
is to generate a book from the map, then import that book into
RoboHelp (don't try the direct ditamap import into RH). (I would
love to hear from anyone who has had success with the ditamap to
RH import!)<br>
<br>
Cheers,<br>
<br>
...scott<br>
<br>
</font>
<pre class="moz-signature" cols="72">
</pre>
On 12/1/12 7:33 AM, John Sgammato wrote:<br>
</div>
<blockquote
cite="mid:CAKwJh1001sBcJvXaxuf0zoM0NM9v0GdRzZV6eVHgG5+=rGiOvQ@mail.gmail.com"
type="cite">But surely somehow the para tags get mapped to
elements for PDF output?
<div>When I publish a procedure to PDF, suppose I want the steps
to have 0pt above, 6pt after, etc - the stuff I usually set up
in the paragraph designer. How do the elements get that
information en route to becoming a PDF? I want to know how to
set that up, too. </div>
<div>And then I want to publish the same content to HTML, with
different presentation. Now that I separate the presentation
form the structure, I have misplaced where the presentation
layer went...</div>
<div><still scratching head></div>
<div>john<br>
<br>
<div class="gmail_quote">On Sat, Dec 1, 2012 at 10:03 AM, Rick
Quatro <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:rick@rickquatro.com" target="_blank">rick@rickquatro.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi John,<br>
<br>
In a structured FrameMaker document, the users don't deal
directly with<br>
paragraph (character, table) formats anyway, so there is no
practical reason<br>
to delete any.<br>
<span class="HOEnZb"><font color="#888888"><br>
Rick Quatro<br>
Carmen Publishing Inc.<br>
<a moz-do-not-send="true" href="tel:585-283-5045"
value="+15852835045">585-283-5045</a><br>
<a moz-do-not-send="true"
href="mailto:rick@frameexpert.com">rick@frameexpert.com</a><br>
</font></span>
<div class="im HOEnZb"><br>
-----Original Message-----<br>
From: <a moz-do-not-send="true"
href="mailto:framers-bounces@lists.frameusers.com">framers-bounces@lists.frameusers.com</a><br>
[mailto:<a moz-do-not-send="true"
href="mailto:framers-bounces@lists.frameusers.com">framers-bounces@lists.frameusers.com</a>]
On Behalf Of John Sgammato<br>
</div>
<div class="HOEnZb">
<div class="h5">Sent: Thursday, November 29, 2012 7:25 PM<br>
To: Writer<br>
Cc: <a moz-do-not-send="true"
href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a><br>
Subject: Re: greenfield and new structure<br>
<br>
I made great progress today. I was able to open the DITA
files and get them<br>
pretty consistent with new master pages, etc.<br>
I see two issues right now that I cannot figure out:<br>
* I want to get rid of many, many paragraph formats that
I won't need, but I<br>
don't know if it is safe to do that, or if it will break
something.<br>
* I have many topics that I want to nest as H2s under
H1s, etc, and I cannot<br>
see how to do that, but today was only my first day so I
am sure I will get<br>
there.<br>
I am grateful for the progress I have made, but I wish I
had some<br>
documentation!<br>
I tried the Yahoo group and Yahoo won't let me in with
my old credentials -<br>
I'll resolve that tomorrow. It's getting late here in
Boston!<br>
<br>
On Nov 29, 2012, at 7:16 PM, Writer <<a
moz-do-not-send="true"
href="mailto:generic668@yahoo.ca">generic668@yahoo.ca</a>>
wrote:<br>
<br>
<br>
<br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<br>
<table cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td valign="middle">
<p> </p>
</td>
<td valign="middle">
<p> </p>
</td>
<td valign="middle">
<p> </p>
</td>
<td valign="middle">
<p> </p>
</td>
<td valign="middle">
<p><b>John Sgammato </b></p>
<p>Documentation Architect</p>
<p><span><b>e</b> <a moz-do-not-send="true"
href="mailto:john.sgammato@actifio.com"
target="_blank"><span>john.sgammato@actifio.com</span></a> </span></p>
<p><span><b>w</b> </span>+1-781.890.2950 x7652<span> </span></p>
</td>
</tr>
</tbody>
</table>
<p> <i>Recover anything instantly for up to 90% less than
you're paying now.</i></p>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
You are currently subscribed to framers as <a class="moz-txt-link-abbreviated" href="mailto:sp10@leximation.com">sp10@leximation.com</a>.
Send list messages to <a class="moz-txt-link-abbreviated" href="mailto:framers@lists.frameusers.com">framers@lists.frameusers.com</a>.
To unsubscribe send a blank email to
<a class="moz-txt-link-abbreviated" href="mailto:framers-unsubscribe@lists.frameusers.com">framers-unsubscribe@lists.frameusers.com</a>
or visit <a class="moz-txt-link-freetext" href="http://lists.frameusers.com/mailman/options/framers/sp10%40leximation.com">http://lists.frameusers.com/mailman/options/framers/sp10%40leximation.com</a>
Send administrative questions to <a class="moz-txt-link-abbreviated" href="mailto:listadmin@frameusers.com">listadmin@frameusers.com</a>. Visit
<a class="moz-txt-link-freetext" href="http://www.frameusers.com/">http://www.frameusers.com/</a> for more resources and info.
</pre>
</blockquote>
<br>
</body>
</html>