From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Adrian Robert Newsgroups: gmane.emacs.devel Subject: Re: Use Core Text for Cocoa Emacs Date: Wed, 19 May 2010 09:14:02 +0300 Message-ID: <7B391C59-908A-4B79-9D61-EEE9EA91F09D@gmail.com> References: <94E6FF46-4227-4DA2-BE35-C64908558378@gmail.com> <18325.1274214480@ccs.covici.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1274249659 4651 80.91.229.12 (19 May 2010 06:14:19 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 19 May 2010 06:14:19 +0000 (UTC) Cc: emacs-devel@gnu.org To: covici@ccs.covici.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 19 08:14:18 2010 connect(): No such file or directory Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OEcXq-0007N7-2b for ged-emacs-devel@m.gmane.org; Wed, 19 May 2010 08:14:18 +0200 Original-Received: from localhost ([127.0.0.1]:55358 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OEcXp-0005mU-28 for ged-emacs-devel@m.gmane.org; Wed, 19 May 2010 02:14:17 -0400 Original-Received: from [140.186.70.92] (port=33390 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OEcXh-0005mO-AG for emacs-devel@gnu.org; Wed, 19 May 2010 02:14:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OEcXe-0007iS-Ql for emacs-devel@gnu.org; Wed, 19 May 2010 02:14:09 -0400 Original-Received: from mail-ew0-f216.google.com ([209.85.219.216]:62311) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OEcXe-0007iJ-Jo for emacs-devel@gnu.org; Wed, 19 May 2010 02:14:06 -0400 Original-Received: by ewy8 with SMTP id 8so1934076ewy.8 for ; Tue, 18 May 2010 23:14:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=DcGqlUlrkUQmDHbm9pyZY9FZ5A9ooAbiCpg0r0totek=; b=AYX7/EErhT1l45WSYtLjaAHe16U23ZWAlBkFQ/Dw7zYknmtXVwwr5P7Ku6SuiYPnXO NH1ogO1fIbW5YoglaxBwNNVp2dowM91ezvHPAr+qOWS/nVbe/0G63vylJDnNJ5WuFe/O Vix42561vgFwDc6CvXzOmgFH0FNVirb83t67A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=GuBmzxuhpyiKgVDPC9xP/ntD2s/owXgEBJAu/GgTg7kdChZnbvPoxUJfjyZQ6HnmxV wZq/VdgAocmiU+H04llQjMEPOU6b6zoWSkBmQT/7hz76rsg2U7bC7SFotJ21lUUa+xMe D0orLF9aW9uEU37VcFImfJpGW4H31mqBI2Vxo= Original-Received: by 10.213.39.137 with SMTP id g9mr3484653ebe.92.1274249645498; Tue, 18 May 2010 23:14:05 -0700 (PDT) Original-Received: from [10.0.1.2] (dsl-hkibrasgw2-ff6ec300-110.dhcp.inet.fi [88.195.110.110]) by mx.google.com with ESMTPS id 13sm3434231ewy.9.2010.05.18.23.14.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 18 May 2010 23:14:04 -0700 (PDT) In-Reply-To: <18325.1274214480@ccs.covici.com> X-Mailer: Apple Mail (2.1077) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:124925 Archived-At: On May 18, 2010, at 11:28 PM, covici@ccs.covici.com wrote: > Adrian Robert wrote: >=20 >> Wang Ling gmail.com> writes: >>=20 >>>=20 >>> Is it possible and advantageous to use Core Text for Cocoa Emacs? >>> I'm just wondering whether it is a practical and meaningful thing to = do for >> Mac Emacsers. >>=20 >> Hi, >>=20 >> Overall it's probably a wash at the present time. Using it would not = result in >> any immediate user-visible changes by itself and might make = supporting Tiger >> difficult. (The framework is there on Tiger, but it's private, and = I'm not sure >> how mature compared to the CG APIs.) But on the other hand, it = exposes a bit >> more of the guts of the Text system than earlier APIs, which should = make support >> of advanced font backend features easier. The cost here would be = forking this >> code to keep GNUstep supported. (Right now CG (vs. DPS on GNUstep) = is only used >> at the very lowest level for emacs rendering, so the split code is = small.) >>=20 >=20 > What about accessibility -- which of these would work better with > Voiceover? I haven't looked at this particular issue, but the main problem no = matter which API were used for rendering would be getting the text onto = the Cocoa side. In the Emacs model all high-level control of the text = resides in the generic code, so the Cocoa side just sees small pieces as = they need to be rendered, not the whole buffer.