<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Let me add to what Chris has said. If you need high-quality PDFs, nothing beats Adobe FrameMaker (InDesign is good too). I can't understand users who move to structured FrameMaker then try to get PDFs from the DITA Open Toolkit. They are never going to be as good as the PDFs that FrameMaker produces. Plus, you can take advantage of FrameMaker's templates: you might have a stripped-down non-WYSIWYG template for authors and content providers, perhaps based on XHTML structure, and then a "pretty" template that a layout person could import that would be suitable for PDF output. That kind of process eliminates the temptation of authors to worry about pagination and line breaks early in the development process.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>And if the ultimate desire is to ditch FrameMaker, your content is at least already structured, and you can use FrameMaker to get PDFs until your DITA-OT PDF styles are fully developed.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Or, another realistic possibility: if you use a schema like DITA, let the authors and content providers use whatever editor they like. Then simply use a FrameMaker license as a "print-engine" to produce high-quality PDFs.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Rick Quatro<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Carmen Publishing Inc.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>585-366-4017<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>rick@frameexpert.com<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> framers-bounces@lists.frameusers.com [mailto:framers-bounces@lists.frameusers.com] <b>On Behalf Of </b>Chris Despopoulos<br><b>Sent:</b> Wednesday, April 15, 2015 1:12 PM<br><b>To:</b> framers@lists.frameusers.com<br><b>Subject:</b> Re: Flare vs DITA<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div id="yui_3_16_0_1_1429098252380_112784"><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>Using Maker eliminates FO. Instead, you set up a Maker template, and work in near WYSIWYG. If you will use Maker, definitely, use structured Maker. You could use a simplified structure -- not necessarily DITA. For example, why not use XHTML? Then you can make your PDF look like whatever you want via Maker template design, and your source is in XHTML. If you later want to go to DITA, run a transform (yes, that would be a script).<o:p></o:p></span></p></div><div id="yui_3_16_0_1_1429098252380_112844"><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'><o:p> </o:p></span></p></div><div id="yui_3_16_0_1_1429098252380_112882"><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>If you want to use Maker to edit DITA, that can be done -- I do it. Templates are not as straight forward as they could be... Adobe unfortunately embeds lots of formatting in the EDD in ways that might even be called gratuitous... That only makes it more difficult to modify your template. But it can be done, and once done you're using familiar tools... No FO scripts that need constant tweaking. <o:p></o:p></span></p></div><div id="yui_3_16_0_1_1429098252380_112883"><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'><o:p> </o:p></span></p></div><div id="yui_3_16_0_1_1429098252380_112906"><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>Like I said, I do this today. There are those who poo-poo me for it, but it works just fine. I'm crying all the way to the bank.<o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>cud<o:p></o:p></span></p></div><div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>===================<o:p></o:p></span></p></div><div id="yui_3_16_0_1_1429098252380_112786"><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>Yes, those are the scripts I am talking about.<o:p></o:p></span></p></div><p class=MsoNormal style='background:white'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'><br>-Gillian<br>> On Apr 14, 2015, at 12:03 PM, Rick Quatro <<a href="mailto:rick@rickquatro.com" id="yui_3_16_0_1_1429098252380_112052">rick@rickquatro.com</a>> wrote:<br>> <br>> Art, Gillian is probably referring to XSL-FO scripts which need to be customized to get the PDF output you want. <br>> <o:p></o:p></span></p></div></div></body></html>