From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28383 invoked by alias); 8 Aug 2011 22:28:38 -0000 Received: (qmail 28372 invoked by uid 22791); 8 Aug 2011 22:28:37 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from etr-usa.com (HELO etr-usa.com) (130.94.180.135) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 08 Aug 2011 22:28:24 +0000 Received: (qmail 42519 invoked by uid 13447); 8 Aug 2011 22:28:23 -0000 Received: from unknown (HELO [172.20.0.42]) ([71.33.33.107]) (envelope-sender ) by 130.94.180.135 (qmail-ldap-1.03) with SMTP for ; 8 Aug 2011 22:28:23 -0000 Message-ID: <4E4062F8.5020508@etr-usa.com> Date: Mon, 08 Aug 2011 22:28:00 -0000 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: cygwin-apps@cygwin.com Subject: Re: 256x256 px icons References: <20110801080730.GT26203@calimero.vinschen.de> <20110802152428.GC8652@calimero.vinschen.de> <4E3C29DE.7010000@etr-usa.com> <20110806082812.GS21692@calimero.vinschen.de> <20110806174346.GA11601@calimero.vinschen.de> <4E4011FF.30805@etr-usa.com> <20110808204351.GP11601@calimero.vinschen.de> In-Reply-To: <20110808204351.GP11601@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2011-08/txt/msg00098.txt.bz2 On 8/8/2011 2:43 PM, Corinna Vinschen wrote: > If you have a way to create a C which > is not handdrawn *and* stands out, I would very much like to see it. That's why I quoted Andy: increasing the stroke width can help. By starting with a much thicker outer stroke, you end up with a brighter yet still AA'd outline. You can also play with (x, y) placement and the sampling algorithm. An 8 px white stroke on black scaled 256:32 (8x) will not necessarily end up a single 1 px white stroke on black. Given a case where that happens, then shifting the line 4 px from that position, downsampling can give you two 50% gray lines side by side if the algorithm interprets the source image as having half the line on one side of the pixel boundary and half on the other. Then if you leave the line where it is, 4 px "off" optimal for one algorithm but use a different sampling algorithm, you might get good results again. This same issue is also why on-screen type hinting is difficult.