From: Jason Rumney <jasonr@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-bidi@gnu.org, emacs-devel@gnu.org, handa@m17n.org
Subject: Re: [emacs-bidi] Re: Arabic support
Date: Thu, 02 Sep 2010 21:09:57 +0800 [thread overview]
Message-ID: <87occge1ga.fsf@home.jasonrumney.net> (raw)
In-Reply-To: <E1Or8T0-0004zO-EO@fencepost.gnu.org> (Eli Zaretskii's message of "Thu, 02 Sep 2010 08:00:30 -0400")
Eli Zaretskii <eliz@gnu.org> 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.
next prev parent reply other threads:[~2010-09-02 13:09 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 1:10 Arabic support Kenichi Handa
2010-08-27 9:56 ` Eli Zaretskii
2010-08-28 10:15 ` Amit Aronovitch
2010-08-29 5:07 ` James Cloos
2010-08-29 5:13 ` James Cloos
2010-08-30 2:07 ` Kenichi Handa
2010-08-30 13:42 ` Amit Aronovitch
2010-08-30 14:11 ` [emacs-bidi] " Amit Aronovitch
2010-09-03 7:35 ` Kenichi Handa
2010-09-03 7:54 ` [emacs-bidi] " Amit Aronovitch
2010-09-01 2:55 ` Kenichi Handa
2010-09-01 4:58 ` Eli Zaretskii
2010-09-01 5:06 ` Kenichi Handa
2010-09-01 7:12 ` [emacs-bidi] " Stefan Monnier
2010-09-03 7:17 ` Kenichi Handa
2010-08-30 7:47 ` Kenichi Handa
2010-08-30 14:06 ` Eli Zaretskii
2010-09-01 2:17 ` Kenichi Handa
2010-09-01 3:47 ` "Martin J. Dürst"
2010-09-02 7:45 ` 大嶋 俊祐
2010-09-02 9:31 ` Eli Zaretskii
2010-09-02 12:58 ` "Martin J. Dürst"
2010-09-02 14:13 ` [emacs-bidi] " Eli Zaretskii
2010-09-01 6:11 ` Eli Zaretskii
2010-09-01 7:08 ` Kenichi Handa
2010-09-01 17:55 ` Eli Zaretskii
2010-09-02 2:13 ` Jason Rumney
2010-09-02 11:53 ` Eli Zaretskii
2010-09-02 12:00 ` Eli Zaretskii
2010-09-02 13:09 ` Jason Rumney [this message]
2010-09-02 14:29 ` Eli Zaretskii
2010-09-02 14:37 ` [emacs-bidi] " Jason Rumney
2010-09-02 13:01 ` Kenichi Handa
2010-09-02 14:04 ` Eli Zaretskii
2010-09-03 1:00 ` Kenichi Handa
2010-09-03 9:16 ` Eli Zaretskii
2010-09-03 10:18 ` David Kastrup
2010-09-03 11:08 ` Kenichi Handa
2010-09-03 14:54 ` Eli Zaretskii
2010-09-03 13:25 ` Eli Zaretskii
2010-09-03 14:32 ` Amit Aronovitch
2010-09-03 14:43 ` Eli Zaretskii
2010-09-04 7:13 ` Eli Zaretskii
2010-09-06 6:04 ` Kenichi Handa
2010-09-04 15:29 ` Eli Zaretskii
2010-09-02 13:48 ` Jason Rumney
2010-09-02 14:49 ` Eli Zaretskii
2010-09-06 13:45 ` Thamer Mahmoud
2010-09-07 4:22 ` TAKAHASHI Naoto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87occge1ga.fsf@home.jasonrumney.net \
--to=jasonr@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-bidi@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).