<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:Consolas;
panose-1:2 11 6 9 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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.st
{mso-style-name:st;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{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'>Hi Tino,<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'>I get what you are saying. Maybe instead of "print engine" I should use the term "layout engine". In my opinion, the whole EDD concept for formatting XML in FrameMaker is very powerful and accessible. I don't think there is anything quite as good in the XML world, especially if you need quality print and PDF output. Thanks for the feedback.<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<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>Heiko Haida<br><b>Sent:</b> Monday, May 13, 2013 2:11 PM<br><b>To:</b> Framers<br><b>Subject:</b> RE: Corporate madness - Adobe software to be subscription only<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p><span style='font-family:"Verdana","sans-serif"'>Dear Rick,<o:p></o:p></span></p><p><span style='font-family:"Verdana","sans-serif"'>please allow one note about the "print engine".<o:p></o:p></span></p><p><span style='font-family:"Verdana","sans-serif"'>FrameMaker is still using the old Distiller engine (at least version 10 does).<br>I recently had to switch a workflow from Indesign to FrameMaker and found it annoying that Indesign would produce a valid PDF right away whereas with FrameMaker I have to correct all PDFs in Acrobat to produce PDF/X3 with color profile and valid bleed box.<br>And as transparency is not fully supported via the Distiller engine, the actual PDF/X4 format cannot be produced (the favorite format for one of our<span class=st> printing service companies)</span>.<o:p></o:p></span></p><p><span style='font-family:"Verdana","sans-serif"'>So finally, I came to think that not FrameMaker, but Indesign may have one of the best "print engines" - at least more flexible and more up to date than FrameMaker's.<o:p></o:p></span></p><p><span style='font-family:"Verdana","sans-serif"'>Best regards -<o:p></o:p></span></p><p><span style='font-family:"Verdana","sans-serif"'>Tino H. Haida, Berlin<o:p></o:p></span></p><p><span style='font-family:"Verdana","sans-serif"'> <o:p></o:p></span></p><p><span style='font-family:"Verdana","sans-serif"'>Rick Quatro:<o:p></o:p></span></p><blockquote style='border:none;border-left:solid #1010FF 1.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-bottom:5.0pt'><pre>Here is my suggestion on where to start. I would like a light-weight editor<o:p></o:p></pre><pre>where the user could apply styles, insert tables, images, etc. The styles<o:p></o:p></pre><pre>would be mapped to a schema so that the user could output XML. Then a full<o:p></o:p></pre><pre>copy of FrameMaker could be used as "print engine". You would set up a<o:p></o:p></pre><pre>structured application in full FrameMaker, and import the XML for print,<o:p></o:p></pre><pre>etc.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>The reasons I favor this approach:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>1) FrameMaker is currently the best "print engine" on the market for<o:p></o:p></pre><pre>producing high-quality print/PDF output.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>2) With a light-weight editor, you would only need one copy of FrameMaker<o:p></o:p></pre><pre>for output. The rest of the writers/editors could use the light-weight<o:p></o:p></pre><pre>editor.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>3) You could easily exchange content with users of other XML editors as long<o:p></o:p></pre><pre>as everyone is using the same schema.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>4) This is a realistic "first step" to a FrameMaker replacement. Anything<o:p></o:p></pre><pre>more complex may be too ambitious and not get too far.<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Rick Quatro<o:p></o:p></pre><pre>Carmen Publishing Inc.<o:p></o:p></pre><pre>585-283-5045<o:p></o:p></pre><pre><a href="mailto:rick@frameexpert.com">rick@frameexpert.com</a><o:p></o:p></pre></blockquote></div></body></html>