<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
I think you're still missing one point. It shouldn't be a matter of "which one" because each is an optimum solution for a different set of circumstances. For line art, anything containing text, or any kind of images generated by a computer program (and yes, this includes the kind of screen captures with gradients that John refers to), PNG will produce better looking results. For *photographic* images (i.e., something that actually exists and that was imaged through a lens), JPEG may produce a result that looks no worse and has a smaller file size than PNG. <BR>
<BR>
-Fred Ridder<BR> <BR>
<DIV>
<DIV id=SkyDrivePlaceholder></DIV>
<HR id=stopSpelling>
From: virginia.morgan@takesolutions.com<BR>To: jsgammato@IMPRIVATA.com; grant@hedgewizard.net<BR>Date: Mon, 16 Jan 2012 09:37:01 -0500<BR>Subject: RE: Recommended graphic file format for single-sourcing from Frame to Robohelp?<BR>CC: framers@lists.frameusers.com<BR><BR>
<META name=Generator content="Microsoft SafeHTML">
<STYLE>
.ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal
{margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri","sans-serif";color:black;}
.ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink
{color:blue;text-decoration:underline;}
.ExternalClass a:visited, .ExternalClass span.ecxMsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
.ExternalClass span.ecxEmailStyle17
{font-family:"Calibri","sans-serif";color:windowtext;}
.ExternalClass span.ecxEmailStyle18
{font-family:"Calibri","sans-serif";color:#1F497D;}
.ExternalClass span.ecxEmailStyle19
{font-family:"Calibri","sans-serif";color:#1F497D;}
.ExternalClass .ecxMsoChpDefault
{font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;}
.ExternalClass div.ecxSection1
{page:Section1;}
</STYLE>
<DIV class=ecxSection1>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">Thanks to all of you who responded for your input. It sounds like .jpg or .png will be the way to go – I will have to do more research and experimentation to determine which. I am only at the beginning of this process, but I appreciate pointing me in the right direction.</SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d"> </SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">Thank you for the recommendation for the image converter, which will be incredibly useful for converting legacy documents I am sure. FWIW, there is no option to not include text, as the most important information in the graphics is the text from the screenshots: names of fields, etc. I don’t think there’s any way around that. </SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d"> </SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">Any other experience/advice is appreciated. My recent graphic design experience has also led me to conclude that .jpgs work well for much more than photos, but the main reason we didn’t use them in old versions of FrameMaker (6.0 and before) even with photos was that we got the “ugly gray box” which was annoying since you couldn’t see your output until you produced a PDF. I’m assuming that “feature” is no longer the case? Like John, I would prefer to work with .jpgs if they produced the result I need. (Working in Windows XP, Frame10 currently.)</SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d"> </SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">Thanks again, </SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">Virginia</SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d"> </SPAN></P>
<DIV>
<DIV style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=ecxMsoNormal><B><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: windowtext; FONT-SIZE: 10pt">From:</SPAN></B><SPAN style="FONT-FAMILY: 'Tahoma','sans-serif'; COLOR: windowtext; FONT-SIZE: 10pt"> John Sgammato [mailto:jsgammato@IMPRIVATA.com] <BR><B>Sent:</B> Sunday, January 15, 2012 9:48 PM<BR><B>To:</B> 'grant@hedgewizard.net'; Virginia Morgan<BR><B>Cc:</B> framers@lists.frameusers.com<BR><B>Subject:</B> RE: Recommended graphic file format for single-sourcing from Frame to Robohelp?</SPAN></P></DIV></DIV>
<P class=ecxMsoNormal> </P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">With all due respect to my colleagues on this forum, IMO the line between JPG and other formats is no longer as neat as it once was. Many screenshots in Win 7 require gradients that JPG handles well. IMO anything that a photo can handle might not be so far removed as you might think from basic screen captures, We are no longer in the cartoony Win 3.x world. </SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">And since AFAIK FrameMaker still imports eleventyhundred colors with every .PNG file, I do not see why a PNG with its headaches is superior to the no-longer-extant difficulties of the .JPG format.</SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">Craving enlightenment…</SPAN></P>
<P class=ecxMsoNormal><SPAN style="COLOR: #1f497d">john</SPAN></P></DIV></DIV> </div></body>
</html>