From mint-bounce@lists.fishpool.fi Wed Jul 8 04:47:24 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=0YvIdxO8xNTWZwtctyYULZ7MYZeWu7cyqAdYdfU1/SM=; b=fCJvTrl2cGCSFkvVzc5NlAGBLQApG5XLdjz8Mc8D/VxClvntIeWA0AaBCsWHsZB9Xz 6otCkA3Of+1+1cgJd0AZza1Q8VAujbxHdVJmzSLNzXbEaUd+xJnNQDtlkKAeIOsq3CVP CMM92JEsgc9Mto24evoo+Uitx31Be2mN944Ck= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=MWxGDqEs5ywlaM0tq01uTi43kXya/4x7N9wspRyPrt+5c2u/oXgMmPSEsbX/V5aY+q 0Bbvwvtb34ylKsrIe8xoOe4+ooiE+k6kZKhtVs5bR2h7wa/3YxZ7Pvm/Xhrf0XSaJ5P7 eBd4Skcnfpd2bR1Nal6RKIw1qp5bAqNB9VClY= MIME-Version: 1.0 In-Reply-To: <4A54322C.2080202@online.no> References: <4A53BEF3.5000100@online.no> <4A54322C.2080202@online.no> Date: Wed, 8 Jul 2009 10:44:13 +0200 X-Google-Sender-Auth: 5ce665366d02e022 Message-ID: Subject: Re: [MiNT] XaAES From: Johan Klockars To: Jo Even Skarstein Cc: "mint@lists.fishpool.fi" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: johan@klockars.net Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: >> And where we're at it: On my aranym the italic text is always cut off at >> the half of the last letter. Its not wrong clipping (I switched it off for >> testing), maybe fvdi does this. > > This is a problem with fvdi. I don't think this happens if you use NVDI for Rather than changing the font settings for links, this bug should be fixed in fVDI. I thought it must be something simple, like forgetting to take the slant into account when calculating the blit size but, looking at the code, that does not appear to be the case. I assume the problem is not present with vector fonts? Or is it only vector fonts? (I don't have a working Atari setup of any form at the moment.) /Johan