From: Eli Zaretskii <eliz@gnu.org>
To: Mohsen BANAN <list-general@mohsen.1.banan.byname.net>
Cc: emacs-bidi@gnu.org, emacs-devel@gnu.org
Subject: Re: Now: Paragraph Direction Detection and Harmonization
Date: Tue, 26 Apr 2011 22:23:03 +0300 [thread overview]
Message-ID: <83fwp495rc.fsf@gnu.org> (raw)
In-Reply-To: <yx2sjt427nf.fsf_-_@mohsen.1.banan.byname.net>
> From: Mohsen BANAN <list-general@mohsen.1.banan.byname.net>
> Cc: Mohsen BANAN <list-general@mohsen.1.banan.byname.net>, emacs-bidi@gnu.org, emacs-devel@gnu.org
> Date: Tue, 26 Apr 2011 11:24:04 -0700
>
> I don't know if there is a PICS-Proforma for
> http://unicode.org/reports/tr9/.
>
> If there was, it would take the form of tables
> refering to the base spec asking for details of
> implementation with regard to each
> section/option/feature/... of the specification.
>
> An example of PICS-Proforma in the RFC Series is:
> http://tools.ietf.org/html/rfc1708
I don't think such a thing exists for UAX#9. There's Section 4
"Bidirectional Conformance"; Emacs implements everything it requires
under "Full bidirectionality" class, as stated in the fragment of NEWS
I cited. That's all there is to it.
> In the absence of a PICS-Proforma, based on your
> implementation details, you (or somebody) can go
> through the specification and include emacs-bidi
> implementation details and cross-referencing UAX#9
> sections.
The source code in bidi.c already includes such cross-references.
> Given the lack of precision for uniformity in
> determination of say paragraph direction, based on
> the emacs PICS, we can then visit our sisters at
> Mozilla and have a conversation towards more
> harmony.
The algorithm used by Emacs to determine the paragraph base direction
is exactly as prescribed by UAX#9. What differs, under the
"high-level protocol" fire escape, is the definition of the
paragraph. This definition is explained in the message I quoted
earlier in this thread and in the Emacs User Manual. It is quite
simple and easy to understand, so I really see no place for any
misunderstanding.
next prev parent reply other threads:[~2011-04-26 19:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 21:18 Bidirectional editing in Emacs -- main design decisions Eli Zaretskii
2009-10-09 21:55 ` joakim
2009-10-09 22:29 ` Eli Zaretskii
2009-10-09 22:42 ` joakim
2009-10-10 7:08 ` Eli Zaretskii
2009-10-10 7:28 ` joakim
2009-10-10 8:20 ` Eli Zaretskii
2009-10-09 22:41 ` Eli Zaretskii
2009-10-10 9:16 ` Richard Stallman
2009-10-10 11:38 ` Eli Zaretskii
2009-10-11 8:41 ` Richard Stallman
2009-10-11 20:12 ` Eli Zaretskii
2009-10-11 21:11 ` Eli Zaretskii
2009-10-12 10:11 ` Richard Stallman
2009-10-12 18:40 ` Eli Zaretskii
2009-10-10 13:44 ` Sascha Wilde
2009-10-10 14:06 ` Eli Zaretskii
2009-10-10 15:54 ` Sascha Wilde
2009-10-10 14:57 ` Ehud Karni
2009-10-10 16:38 ` Eli Zaretskii
2009-10-10 15:13 ` Jason Rumney
2009-10-10 16:06 ` Eli Zaretskii
2009-10-10 16:29 ` Jason Rumney
2009-10-10 17:18 ` James Cloos
2009-10-10 18:33 ` Eli Zaretskii
2011-04-18 14:54 ` Eli Zaretskii
2011-04-19 13:11 ` Stefan Monnier
2011-04-19 16:02 ` Eli Zaretskii
2011-04-20 3:15 ` Stefan Monnier
2011-04-25 17:31 ` Mohsen BANAN
2011-04-25 17:58 ` Eli Zaretskii
2011-04-25 18:44 ` Mohsen BANAN
2011-04-25 18:59 ` Eli Zaretskii
2011-04-25 21:31 ` Now: Paragraph Direction Detection and Harmonization -- Was: " Mohsen BANAN
2011-04-25 22:00 ` Eli Zaretskii
2011-04-26 7:56 ` Mohsen BANAN
2011-04-26 18:05 ` Eli Zaretskii
2011-04-27 21:58 ` Now: Paragraph Direction Detection and Harmonization Mohsen BANAN
2011-04-26 18:24 ` Mohsen BANAN
2011-04-26 19:23 ` Eli Zaretskii [this message]
2011-04-26 1:22 ` Now: Paragraph Direction Detection and Harmonization -- Was: Re: Bidirectional editing in Emacs -- main design decisions Stephen J. Turnbull
2011-04-28 0:52 ` Requesting instructions for enabling bidi by default Mohsen BANAN
2011-04-28 1:21 ` Juanma Barranquero
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=83fwp495rc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-bidi@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=list-general@mohsen.1.banan.byname.net \
/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).