Received: by 10.224.97.134 with SMTP id l6mr544093qan.6.1336008421558;
        Wed, 02 May 2012 18:27:01 -0700 (PDT)
X-BeenThere: chromium-b...@chromium.org
Received: by 10.224.176.78 with SMTP id bd14ls931876qab.0.gmail; Wed, 02 May
 2012 18:27:00 -0700 (PDT)
Received: by 10.224.33.134 with SMTP id h6mr1273173qad.28.1336008420317;
        Wed, 02 May 2012 18:27:00 -0700 (PDT)
Received: by 10.224.33.134 with SMTP id h6mr1273171qad.28.1336008420291;
        Wed, 02 May 2012 18:27:00 -0700 (PDT)
Return-Path: <35N6hTwgODasNScZXTfXRZZRWPNZOP.NZXNScZXTfX-MfRdNScZXTfX....@codesite.bounces.google.com>
Received: from mail-qa0-f76.google.com (mail-qa0-f76.google.com [209.85.216.76])
        by mx.google.com with ESMTPS id g5si1210823qct.135.2012.05.02.18.27.00
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 02 May 2012 18:27:00 -0700 (PDT)
Received-SPF: pass (google.com: domain of 35N6hTwgODasNScZXTfXRZZRWPNZOP.NZXNScZXTfX-MfRdNScZXTfX....@codesite.bounces.google.com designates 209.85.216.76 as permitted sender) client-ip=209.85.216.76;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of 35N6hTwgODasNScZXTfXRZZRWPNZOP.NZXNScZXTfX-MfRdNScZXTfX....@codesite.bounces.google.com designates 209.85.216.76 as permitted sender) smtp.mail=35N6hTwgODasNScZXTfXRZZRWPNZOP.NZXNScZXTfX-MfRdNScZXTfX....@codesite.bounces.google.com
Received: by mail-qa0-f76.google.com with SMTP id p27so23227qat.3
        for <chromium-b...@chromium.org>; Wed, 02 May 2012 18:27:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.110.207 with SMTP id o15mr545169qap.7.1336008420230; Wed,
 02 May 2012 18:27:00 -0700 (PDT)
Reply-To: codesite-nore...@google.com
X-Generated-By: Google Code
X-GoogleCode-Project: chromium
X-GoogleCode-Issue-Id: 105685
References: <21-1824057202445553401-8175610992786815520-chromium=googlecode.com@googlecode.com>
 <0-1824057202445553401-8175610992786815520-chromium=googlecode.com@googlecode.com>
In-Reply-To: <21-1824057202445553401-8175610992786815520-chromium=googlecode.com@googlecode.com>
Message-ID: <22-1824057202445553401-8175610992786815520-chromium=googlecode....@googlecode.com>
Date: Thu, 03 May 2012 01:27:00 +0000
Subject: Re: Issue 105685 in chromium: Arabic text align incorrect
From: chrom...@googlecode.com
To: chromium-b...@chromium.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes


Comment #22 on issue 105685 by benjamin...@gmail.com: Arabic text align  
incorrect
http://code.google.com/p/chromium/issues/detail?id=105685

If it's a bug in the old Harfbuzz, maybe this could be an extra incentive  
to speed up the switch to Harfbuzz-ng?