emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dov Grobgeld <dov.grobgeld@gmail.com>
Cc: 11710@debbugs.gnu.org
Subject: bug#11710: 24.1.50; Bidi attributes are not exported in org-mode html output
Date: Thu, 14 Jun 2012 22:42:30 +0300	[thread overview]
Message-ID: <8362aty921.fsf__26626.0995799259$1339703006$gmane$org@gnu.org> (raw)
In-Reply-To: <CA++fsGGSgAUPUGuy6n=G0xB=7oHa3MHuDy+CxOnoNPAae3i+ug@mail.gmail.com>

> Date: Thu, 14 Jun 2012 21:20:17 +0300
> From: Dov Grobgeld <dov.grobgeld@gmail.com>
> 
> When using bidi (bi-direction) reordering together with org-mode, all
> paragraphs automatically become either RTL or LTR according to the
> emacs' Bidi heuristic algorithm.

Did you customize Emacs to dynamically determine the paragraph
direction in Org buffers?  By default they are forced to be
left-to-right.

> But when exporting to HTML, the resolved paragraph direction is not
> included. In HTML the paragraph directions must be set explicitly,
> e.g. by <div dir="RTL">...</div>, and they should be set according
> to the directions resolved by emacs.

To the Org maintainers: the resolved paragraph direction at character
position N in the current buffer can be retrieved like this:

  (save-excursion
    (goto-char N) 
    (current-bidi-paragraph-direction))

       reply	other threads:[~2012-06-14 19:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA++fsGGSgAUPUGuy6n=G0xB=7oHa3MHuDy+CxOnoNPAae3i+ug@mail.gmail.com>
2012-06-14 19:42 ` Eli Zaretskii [this message]
     [not found] ` <8362aty921.fsf@gnu.org>
2012-06-15  6:17   ` Dov Grobgeld
     [not found]   ` <CA++fsGEeiz7E3n7FpdYOceEeKsxX5WZr-ZKH_qFzF86t9eh29w@mail.gmail.com>
2012-06-15  7:55     ` Eli Zaretskii
2020-05-22 11:41 ` bug#11710: Status: " Bastien

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='8362aty921.fsf__26626.0995799259$1339703006$gmane$org@gnu.org' \
    --to=eliz@gnu.org \
    --cc=11710@debbugs.gnu.org \
    --cc=dov.grobgeld@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/org-mode.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).