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: Thu, 25 Feb 2016 17:55:16 +0200 [thread overview]
Message-ID: <83wppsg4yj.fsf@gnu.org> (raw)
In-Reply-To: <87egc1z71n.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 25 Feb 2016 16:05:16 +1030)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 25 Feb 2016 16:05:16 +1030
> Cc: 22786@debbugs.gnu.org
>
> eww defaults `bidi-paragraph-direction' to `left-to-right', and depends
> on web pages including the "dir" attribute to <HTML> to change that.
> The Al Jazeera web site doesn't do that, so things look wrong.
(This, of course, is unrelated to the original problem.)
> Is there a simple heuristic we could use to determine that we're on a
> page where we should flip the paragraph direction?
The heuristic that we have happens automagically if
bidi-paragraph-direction is nil. (It's not a heuristic, it's what the
Unicode Bidirectional Algorithm prescribes to do.) Then each
paragraph gets its own direction computed on the fly.
> Some pages may have a bit of RTL text without wanting to change the
> paragraph direction (like most Wikipedia pages)...
Exactly. Which is why we changed eww to its current default.
I think at this stage we should add to the eww menu an item that
allows to change the page direction, and let users override the
default if needed. This should solve most, if not all, of the cases
where the default doesn't DTRT.
next prev parent reply other threads:[~2016-02-25 15:55 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wppsg4yj.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.