From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jason Rumney Newsgroups: gmane.emacs.devel,gmane.emacs.bidi Subject: Re: [emacs-bidi] Re: Arabic support Date: Thu, 02 Sep 2010 21:09:57 +0800 Message-ID: <87occge1ga.fsf@home.jasonrumney.net> References: <83bp8oml9c.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1283433122 10513 80.91.229.12 (2 Sep 2010 13:12:02 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 2 Sep 2010 13:12:02 +0000 (UTC) Cc: emacs-bidi@gnu.org, emacs-devel@gnu.org, handa@m17n.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 02 15:12:01 2010 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 1Or9aB-0003Lv-Sn for ged-emacs-devel@m.gmane.org; Thu, 02 Sep 2010 15:12:00 +0200 Original-Received: from localhost ([127.0.0.1]:40113 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Or9aB-0008B4-6x for ged-emacs-devel@m.gmane.org; Thu, 02 Sep 2010 09:11:59 -0400 Original-Received: from [140.186.70.92] (port=38312 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Or9Yy-0007Pa-Kn for emacs-devel@gnu.org; Thu, 02 Sep 2010 09:10:47 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Or9Yt-0004C0-Q1 for emacs-devel@gnu.org; Thu, 02 Sep 2010 09:10:42 -0400 Original-Received: from mail-px0-f169.google.com ([209.85.212.169]:37785) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Or9YK-00044s-WF; Thu, 02 Sep 2010 09:10:05 -0400 Original-Received: by pxi5 with SMTP id 5so208551pxi.0 for ; Thu, 02 Sep 2010 06:10:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:received:from:to:cc :subject:references:date:in-reply-to:message-id:user-agent :mime-version:content-type; bh=EB8iq3vI+20+c2A3D5LGhZaPpD5h17VMSsWlyN0rwSQ=; b=SpeWVEEs6V1XYo0pU2b19uFVhk0P8KLM8znNkyf0DaxbiaWJWmpXhvflItcIYbVE0Q Ky0qu+hwLQg0Iu0+o8qHr4U6v9rMBg5oIADMJ8e6HynRqdNsIEstFBnsJNvsMivaTeUo TUgLUMkNnSr6S6GmVe5gYIwSpJMkUAEjm8Vts= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; b=GCkZRfqixlaurTDTjJ1vqJjLyw1/Y47PUTBouieHLdCmqBo3EC/Ml2L51679BwUI9T G6FdM7MmNEm9Oz/ywksTOzXaOgApphf9FqhTW3bOPhq0XCqx4AcNT4WhUWydthAcnbH4 o19R8FZbsOr10NtN21dw0wGZ68gXL/SAxduco= Original-Received: by 10.114.108.15 with SMTP id g15mr10351303wac.52.1283433003836; Thu, 02 Sep 2010 06:10:03 -0700 (PDT) Original-Received: from home.jasonrumney.net ([202.87.221.130]) by mx.google.com with ESMTPS id q6sm890724waj.22.2010.09.02.06.10.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 02 Sep 2010 06:10:02 -0700 (PDT) Original-Received: by home.jasonrumney.net (Postfix, from userid 1000) id D14D314DF; Thu, 2 Sep 2010 21:09:57 +0800 (MYT) In-Reply-To: (Eli Zaretskii's message of "Thu, 02 Sep 2010 08:00:30 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) 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:129590 gmane.emacs.bidi:800 Archived-At: Eli Zaretskii writes: > And another question: AFAIU, an LGSTRING specifies characters as > Unicode codepoints, while the Windows Uniscribe APIs expect wchar_t > wide characters, which on Windows means UTF-16. This means we should > encode the codepoints in LGSTRINGs to UTF-16 before passing them to > Uniscribe, rather than passing them unaltered, right? The current > code will break for characters whose Unicode codepoints are beyond the > BMP, right? Theortically, yes. In practice I don't think any of the scripts that we use the shaping engine for lie beyond the BMP.