unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-bidi@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Handling invisible text in bidirectional display
Date: Mon, 18 Jan 2010 20:09:14 +0900	[thread overview]
Message-ID: <tl7aawbzn39.fsf@m17n.org> (raw)
In-Reply-To: <E1NWnPC-0008Vx-NO@fencepost.gnu.org> (message from Eli Zaretskii on Mon, 18 Jan 2010 03:56:14 -0500)

In article <E1NWnPC-0008Vx-NO@fencepost.gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:

> > From: Kenichi Handa <handa@m17n.org>
> > Cc: monnier@iro.umontreal.ca, emacs-bidi@gnu.org, emacs-devel@gnu.org
> > Date: Mon, 18 Jan 2010 16:40:15 +0900
> > 
> > > I will also need to tell you how to find the necessary
> > > information in the glyph row struct.
> > 
> > Sorry, but I don't know that much about 'struct glyph_row'.
> > All my work has been down without investigatng it in detail.

> No need for any detailed investigation.  There's a flag there now that
> you will need to consult, it tells you whether the glyphs in the row
> are reversed (for paragraphs whose base direction is R2L).  That's
> about it.  (There are a few more flags and values in struct glyph, but
> that can wait for later.)

Ok, anyway I'll wait for your code being available by bzr.

---
Kenichi Handa
handa@m17n.org

      reply	other threads:[~2010-01-18 11:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16 16:54 Handling invisible text in bidirectional display Eli Zaretskii
2010-01-16 18:43 ` martin rudalics
2010-01-16 20:32   ` Eli Zaretskii
2010-01-17  8:59     ` martin rudalics
2010-01-17 19:06       ` Eli Zaretskii
2010-01-18  8:11         ` martin rudalics
2010-01-18  9:54           ` Eli Zaretskii
2010-01-18 10:39             ` martin rudalics
2010-01-18 12:35               ` Eli Zaretskii
2010-01-16 19:15 ` David Kastrup
2010-01-16 20:37   ` Eli Zaretskii
2010-01-17 16:05     ` Richard Stallman
2010-01-17 19:29       ` Eli Zaretskii
2010-01-17 20:17         ` David Kastrup
2010-01-17 20:39           ` Ehud Karni
2010-01-17 20:51           ` Eli Zaretskii
2010-01-18  6:42             ` David Kastrup
2010-01-18  8:52               ` Eli Zaretskii
2010-01-16 19:56 ` Stefan Monnier
2010-01-16 20:53   ` Eli Zaretskii
2010-01-17 16:04     ` Richard Stallman
2010-01-17 18:24       ` Eli Zaretskii
2010-01-18 11:56         ` Richard Stallman
2010-01-22 13:41       ` Bidi TODO (was: Handling invisible text in bidirectional display) Eli Zaretskii
2010-02-01 14:48         ` [emacs-bidi] " Ehud Karni
2010-01-18  1:27     ` Handling invisible text in bidirectional display Kenichi Handa
2010-01-18  4:00       ` Eli Zaretskii
2010-01-18  7:40         ` Kenichi Handa
2010-01-18  8:56           ` Eli Zaretskii
2010-01-18 11:09             ` Kenichi Handa [this message]

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=tl7aawbzn39.fsf@m17n.org \
    --to=handa@m17n.org \
    --cc=eliz@gnu.org \
    --cc=emacs-bidi@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).