unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 22786@debbugs.gnu.org, mohamed.hibti@gmail.com
Subject: bug#22786: 25.1.50; eww arabic rendering
Date: Sun, 28 Feb 2016 17:41:13 +0200	[thread overview]
Message-ID: <831t7wc06e.fsf@gnu.org> (raw)
In-Reply-To: <878u25xyk0.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  28 Feb 2016 14:43:03 +1030)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: mohamed.hibti@gmail.com,  22786@debbugs.gnu.org
> Date: Sun, 28 Feb 2016 14:43:03 +1030
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > But if there's no such hint, and all we have is the text itself, then
> > the UBA determines the paragraph direction from the first strong
> > directional character, and we then keep that direction until the
> > paragraph ends, which is indicated by an empty line.  There's no way
> > around this, it's how the bidirectional display engine works.
> >
> > Specifically, we need a way to distinguish between the list of
> > languages on a Wikipedia page from the Al Jazeera home page.  Can you
> > spot anything in the page sources that will allow such a distinction?
> 
> Nope.  But since Firefox is able to do this, that means that their bidi
> algo is doing something else than what Emacs' bidi algo is doing...
> 
> So we have demonstrated that there is a way around this.  :-)

The way around it is to support frames (or "side bars").  Then each
frame could have its own base paragraph direction.  AFAICT, eww
doesn't support that yet.

> > In any case, I think it will be good to add a "Switch page direction"
> > menu item to EWW on the emacs-25 branch.
> 
> Good idea; I'll all that.

Thanks.





  reply	other threads:[~2016-02-28 15:41 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 22:50 bug#22786: 25.1.50; eww arabic rendering Mohamed Hibti
2016-02-24  1:07 ` Lars Ingebrigtsen
2016-02-24 10:16   ` Mohamed Hibti
2016-02-24 17:37     ` Eli Zaretskii
2016-02-24 18:18       ` Mohamed Hibti
2016-02-24 18:24       ` Mohamed Hibti
2016-02-24 19:11         ` Eli Zaretskii
2016-02-25  5:35     ` Lars Ingebrigtsen
2016-02-25 11:08       ` Mohamed Hibti
2016-02-25 15:55       ` Eli Zaretskii
2016-02-26  5:45         ` Lars Ingebrigtsen
2016-02-26  8:59           ` Eli Zaretskii
2016-02-28  4:13             ` Lars Ingebrigtsen
2016-02-28 15:41               ` Eli Zaretskii [this message]
2016-02-28 16:07                 ` Eli Zaretskii
2016-02-29  2:34                   ` Lars Ingebrigtsen
2016-02-29  3:38                     ` Eli Zaretskii
2016-02-29  4:36                       ` Lars Ingebrigtsen
2016-02-29 15:38                         ` Eli Zaretskii
2016-03-01  0:31                           ` Lars Ingebrigtsen
2016-03-01  8:55                             ` Mohamed HIBTI
2016-02-29  2:33                 ` Lars Ingebrigtsen
2016-02-29  3:36                   ` Eli Zaretskii
2016-02-29  4:35                     ` Lars Ingebrigtsen
2016-02-29 15:37                       ` Eli Zaretskii
2016-02-29 23:56                         ` Lars Ingebrigtsen
2016-03-01 16:44                           ` Eli Zaretskii
2016-03-02 17:01                             ` Lars Ingebrigtsen
2016-03-02 19:33                               ` Eli Zaretskii
2016-03-01  0:26                         ` Lars Ingebrigtsen
2016-03-01 16:49                           ` Eli Zaretskii
2016-03-02 17:08                             ` Lars Ingebrigtsen
2016-03-02 19:38                               ` Eli Zaretskii
2016-03-03  5:38                                 ` Lars Ingebrigtsen

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=831t7wc06e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22786@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=mohamed.hibti@gmail.com \
    /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).