unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eli Osherovich <eli.osherovich@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: improving bidi documents display
Date: Thu, 24 Feb 2011 21:54:08 +0200	[thread overview]
Message-ID: <837hcpryxr.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTim9bMAYzt5O8ceScprbqWy9Z=q6bJDGVRBe97VU@mail.gmail.com>

> Date: Thu, 24 Feb 2011 14:32:35 +0200
> From: Eli Osherovich <eli.osherovich@gmail.com>
> 
> At the moment (using rev. 103371)  I can edit Hebrew/English LaTeX
> documents, however, the way they are displayed in Emacs is not perfect.
> Please look at the file attached as you can see any English text that
> appears inside a Hebrew paragraph requires certain decorations around it
> (e.g., \L{some English text}) these decorations are displayed in an ugly
> fashion.

Yes, it's a known problem.  The Unicode UAX#9 Bidirectional algorithm
(which is what Emacs implements for bidirectional display) does not
produce good results with LaTeX (and with other kinds of markup).

> Is there anything that can be done about it?

Something _should_ be done, for sure.  But for that, Someone™ should
figure out how this kind of problems could be solved using Emacs
display features.  Any solution will probably involve reordering only
parts of text, but a more detailed design suggestion is needed before
it can be implemented.  People are welcome to try to tackle this,
because I'm still busy with low-level bidi support of plain text.




  reply	other threads:[~2011-02-24 19:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 12:32 improving bidi documents display Eli Osherovich
2011-02-24 19:54 ` Eli Zaretskii [this message]
2011-02-27 10:01   ` Michael Welsh Duggan
2011-02-27 10:34     ` "Martin J. Dürst"
2011-02-27 21:19       ` Eli Zaretskii
2011-03-02  1:50         ` "Martin J. Dürst"
2011-03-02  4:02           ` Eli Zaretskii
2011-03-04 10:34             ` [emacs-bidi] " "Martin J. Dürst"
2011-02-27 21:15     ` Eli Zaretskii
2011-02-28  1:10       ` Miles Bader
2011-02-28  4:02         ` Eli Zaretskii
2011-03-02  0:58       ` James Cloos
2011-03-02 18:59         ` Eli Zaretskii
2011-03-02  2:09       ` [emacs-bidi] " "Martin J. Dürst"
2011-03-02  2:39         ` Miles Bader
2011-03-02  4:03           ` Eli Zaretskii
2011-03-02  7:06             ` Miles Bader
2011-03-02 18:39               ` Eli Zaretskii
2011-03-03  1:32                 ` Miles Bader
2011-03-03  4:07                   ` Eli Zaretskii
2011-03-03  6:11                     ` "Martin J. Dürst"
2011-03-03 10:40                       ` [emacs-bidi] " Eli Zaretskii
2011-03-04 10:34                         ` "Martin J. Dürst"
2011-03-04  3:58                 ` Stefan Monnier
2011-03-04  8:04                   ` Eli Zaretskii
2011-03-04  4:25                 ` Miles Bader
2011-03-04  9:52                   ` Eli Zaretskii

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=837hcpryxr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eli.osherovich@gmail.com \
    --cc=emacs-devel@gnu.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).