[no subject]

Dow Hurst wrote:
> That is the right way to do it.  You have to have the image large enough 
> to print aliased.  Your screen is at 75dpi while the printer prints at 
> 600dpi. So your image that is small enough to fit in your screen will be 
> tiny on the page.  The software can "blowup" the image to fit the page 
> size creating fuzzy edges, or you can make the image large enough that 
> it fits on the page at 600dpi.  So a 75dpi rendition of your image will 
> be the size of your wall!  An uncompressed TIFF image that is at 600dpi 
> for a printsize of 7.5"x3.0" is 100Mb.  Manipulating the image at the 
> monitor's 75dpi resolution is a pain. But, the final print is gorgeous(I 
> use PNG when possible).  I've had to get involved with preparing images 
> for print in journals for the research papers we've submitted.  Each 
> journal requires a particular process and format for what is submitted, 
> so I've had to find out some of this stuff.  I'd like to know a better 
> way than what I am doing currently.  What I need is a combination of 
> VMD, Sodipodi, and OOo Draw, and Gimp.  Sometime I'll post some specific 
> questions about this.
> Dow
> 
> 
> Chris Fowler wrote:
> 
>> I set up the print size in gimp so that the program will know what size
>> is going to be printed.  I then use the text tool.  I get crisp text.
>>
>> On Fri, 2004-03-12 at 16:27, John Mills wrote:
>>
>>> ALErs -
>>>
>>> I use GIMP to set up web-page graphics and for some image manipulation,
>>> but I have never figured out how to get clean, sharp text when I print a
>>> GIMP image out. The text always has a lot of 'bleeding' into the
>>> surrounding image area. Basically I just used the GIMP text tool and 
>>> type
>>> in my text, and get fuzzy-edged characters when I print the image. (If
>>> necessary I can post a couple of samples on my web space.) The effect is
>>> probably present with screen images, but I have never been able to 
>>> see it.
>>>
>>> I've been told that the text must be rendered into the image at
>>> essentially the resolution with which it will be printed, and the 
>>> problem
>>> won't appear. I have not managed to do this.
>>>
>>> I don't have the problem with [say] Corel Photo-Paint in MsWin. (I 
>>> haven't
>>> actually tried this on GIMP in MsWin to check if this is a Linux 
>>> problem.)
>>>
>>> Has anyone fought this through? It would be nice to eliminate one 
>>> more thing I have to boot MsWin to do. (There wouldn't be many left!)
>>>
>>> TIA.
>>>
>>> - John Mills
>>>   1884 Ridgewood Dr, NE
>>>   Atlanta, GA 30307-1166
>>>   404.377.2577
>>>   john.m.mills at alum.mit.edu
>>>
>>> _______________________________________________
>>> Ale mailing list
>>> Ale at ale.org
&gt;&gt;&gt; <a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
&gt;&gt;
&gt;&gt;
&gt;&gt;
&gt;&gt; _______________________________________________
&gt;&gt; Ale mailing list
&gt;&gt; Ale at ale.org
&gt;&gt; <a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
&gt;&gt;
&gt; 

-- 
__________________________________________________________
Dow Hurst                  Office: 770-499-3428            *
Systems Support Specialist    Fax: 770-423-6744            *
1000 Chastain Rd. Bldg. 12                                 *
Chemistry Department SC428  Email:   dhurst at kennesaw.edu   *
Kennesaw State University         Dow.Hurst at mindspring.com *
Kennesaw, GA 30144                                         *
************************************************************
This message (including any attachments) contains          *
confidential information intended for a specific individual*
and purpose, and is protected by law.  If you are not the  *
intended recipient, you should delete this message and are *
hereby notified that any disclosure, copying, distribution *
of this message, or the taking of any action based on it,  *
is strictly prohibited.                                    *
************************************************************


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00435" href="msg00435.html">[ale] GIMP text question</a></strong>
<ul><li><em>From:</em> esoteric at 3times25.net (Geoffrey)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00416" href="msg00416.html">[ale] GIMP text question</a></strong>
<ul><li><em>From:</em> johnmills at speakeasy.net (John Mills)</li></ul></li>
<li><strong><a name="00417" href="msg00417.html">[ale] GIMP text question</a></strong>
<ul><li><em>From:</em> cfowler at outpostsentinel.com (Chris Fowler)</li></ul></li>
<li><strong><a name="00425" href="msg00425.html">[ale] GIMP text question</a></strong>
<ul><li><em>From:</em> dhurst at kennesaw.edu (Dow Hurst)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00425.html">[ale] GIMP text question</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00427.html">[ale] ramdisk howto</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00425.html">[ale] GIMP text question</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00435.html">[ale] GIMP text question</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00426"><strong>Date</strong></a></li>
<li><a href="threads.html#00426"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>