From: Dov Grobgeld <dov.grobgeld@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 11700@debbugs.gnu.org
Subject: bug#11700: 24.1.50; Bad interaction between BiDi and org-tables
Date: Thu, 14 Jun 2012 21:10:46 +0300 [thread overview]
Message-ID: <CA++fsGEWbmfgEn1=WVd_HcqxXVySPg0P-SsPzrF2gZ0gu_-0ww@mail.gmail.com> (raw)
In-Reply-To: <83mx46y4f5.fsf@gnu.org>
Do you think that you can provide some lisp code that builds the
buffer contents and the display properties for the three options that
ou refered to as an illustration?
I tried inserting tabs into the buffer before the vertical bars, but
after reordering it still didn't come out right.
Regards,
Dov
On Thu, Jun 14, 2012 at 6:10 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 13 Jun 2012 22:26:35 +0300
>> From: Dov Grobgeld <dov.grobgeld@gmail.com>
>>
>> Imagine you have a buffer with the following logical contents (using the
>> convention that capitals are RTL characters).
>>
>> | abcdef | abc |
>> | ABCDEF | ABC |
>>
>> I would like this to be displayed as:
>>
>> | abcdef | abc |
>> | FEDCBA | CBA |
>>
>> The problem is that I want to each column of the table to be isolated
>> (with regards to bidi influence) from other columns in the table. (Of
>> course we also want to choose the table direction, but that is a
>> different and solvable issue.) If there is no such separation, which
>> is the behaviour currently get in emacs HEAD, then the resulting
>> rendered buffer is:
>>
>> | abcdef | abc |
>> | CBA | FEDCBA |
>>
>> Is this even solvable in the current emacs bidi model?
>
> Yes, it is. The solution involves putting segment separators between
> the table columns. These could be TAB characters or a display
> property whose value is (space . :width N) or (space . :align-to COL).
>
> Org maintainers, please ask if you need help in fixing this.
next parent reply other threads:[~2012-06-14 18:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA++fsGHi3oq-jkanE6eBV3R+Wd0phYSV6b-w61Xyk7YHjxxDyg@mail.gmail.com>
[not found] ` <83mx46y4f5.fsf@gnu.org>
2012-06-14 18:10 ` Dov Grobgeld [this message]
2012-06-14 19:37 ` bug#11700: 24.1.50; Bad interaction between BiDi and org-tables Eli Zaretskii
[not found] ` <837gv9y99l.fsf@gnu.org>
2012-06-15 6:39 ` bug#11700: " Dov Grobgeld
[not found] ` <CA++fsGEZ4hpgYQ=12vnHryS9LJbqycGHnuWs5JN5G0M776p6Gw@mail.gmail.com>
2012-06-15 8:38 ` Eli Zaretskii
2017-12-04 20:27 ` Nicolas Goaziou
[not found] ` <87mv2y6xx2.fsf@nicolasgoaziou.fr>
2017-12-04 20:35 ` Dov Grobgeld
[not found] ` <CA++fsGFeTBLaxS8tEVjDcJoX1GjGp0Xat1tf71rj3hHOY1WBgg@mail.gmail.com>
2017-12-04 20:43 ` Eli Zaretskii
[not found] ` <834lp6xlzz.fsf@gnu.org>
2017-12-04 20:53 ` Eli Zaretskii
2017-12-04 20:45 ` Eli Zaretskii
2017-12-04 21:02 ` Nicolas Goaziou
[not found] ` <877eu26wc7.fsf@nicolasgoaziou.fr>
2017-12-08 9:28 ` Eli Zaretskii
2017-12-08 17:08 ` Nicolas Goaziou
2017-12-23 13:38 ` Eli Zaretskii
[not found] ` <83y3ltk1j0.fsf@gnu.org>
2017-12-23 13:48 ` Eli Zaretskii
2017-12-23 22:51 ` Nicolas Goaziou
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='CA++fsGEWbmfgEn1=WVd_HcqxXVySPg0P-SsPzrF2gZ0gu_-0ww@mail.gmail.com' \
--to=dov.grobgeld@gmail.com \
--cc=11700@debbugs.gnu.org \
--cc=eliz@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/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).