From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: stephen@xemacs.org, emacs-devel@gnu.org
Subject: Re: bidi properties from uniprop tables
Date: Tue, 23 Aug 2011 17:49:58 +0300 [thread overview]
Message-ID: <838vqki3mx.fsf@gnu.org> (raw)
In-Reply-To: <87wre4watk.fsf@m17n.org>
> From: Kenichi Handa <handa@m17n.org>
> Cc: eliz@gnu.org, emacs-devel@gnu.org
> Date: Tue, 23 Aug 2011 21:51:03 +0900
>
> I've just installed fixes.
Thanks. I committed a followup changeset, to make the default
bidi-class properties consistent with the latest UCD, to adapt bidi.c
to the changes, and to document in the ELisp manual the default values
for the unassigned codepoints.
> But, it still returns nil for these properties ("string
> property" in UCD terminology):
> decimal-digit-value, digit-value, numeric-value,
> uppercase, lowercase, titlecase, mirroring
> UCD says that the default value is a character itself for
> them, but to implement it, we have to fill all char-table
> elements by corresponding characters (which makes the table
> very big), or have to implement a special mechanism to
> return a character ifself if the value is nil (which I think
> is not adequate at the current timing of feature freeze).
> So, I just added this kind of statement in the docstring.
>
> The value nil means that the actual property value of a
> character is the character itself.
I agree with this implementation, and documented these properties
accordingly in the ELisp manual.
Thanks.
next prev parent reply other threads:[~2011-08-23 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 19:06 bidi properties from uniprop tables Eli Zaretskii
2011-08-19 4:44 ` Stephen J. Turnbull
2011-08-19 6:43 ` Eli Zaretskii
2011-08-19 9:15 ` Stephen J. Turnbull
2011-08-19 10:36 ` Eli Zaretskii
2011-08-19 12:10 ` Stephen J. Turnbull
2011-08-20 12:42 ` Kenichi Handa
2011-08-20 13:00 ` Eli Zaretskii
2011-08-23 12:51 ` Kenichi Handa
2011-08-23 14:49 ` Eli Zaretskii [this message]
2011-08-23 23:36 ` Kenichi Handa
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=838vqki3mx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=stephen@xemacs.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).