bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#22429: Force character to be recognized as LTR inside RTL paragraph


From: Filipe Moreira
Subject: bug#22429: Force character to be recognized as LTR inside RTL paragraph
Date: Fri, 22 Jan 2016 11:54:45 +0000

Hi Eli,

Thank for taking the time to look into this

On Fri, Jan 22, 2016 at 8:08 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> Date: Thu, 21 Jan 2016 13:14:22 -0800
> From: "Filipe Moreira" <famoreira@gmail.com>
>
> I’m using Emacs as a LaTeX editor, with the AUCTeX mode. One document I’m
> authoring is written in English with some paragraphs in Hebrew or Greek.
>
> The issue I have is with mixing some neutral characters that need to be LTR,
> inside a paragraph which is RTL. An example of this is the slash (i.e. ‘\’)
> character used by LaTeX to signal its commands. Inside a RTL paragraph I
> ideally want to force Emacs to always interpret the slash character, as well as
> the open and close brackets (i.e. {}) as LTR.
>
> This is not what happens at the moment. Here I have a visual representation of
> the problem:
> http://emacs.stackexchange.com/questions/19696/handling-left-to-right-inside-right-to-left-paragraphs-using-emacs-and-auctex.
>
> Is it possible to whitelist some characters that should always be interpreted
> as LTR?

The directionality of characters is determined by their bidirectional
class property as defined by the Unicode Character Database.  Emacs
uses those definitions in its implementation of the UBA, the Unicode
Bidirectional Algorithm, when it lays out text for display.
Punctuation characters, such as \, {, and } have "weak
directionality": they take the directionality of the surrounding text,
and if the directionality on either side is different, they default to
the paragraph's base direction, which is RTL in your case.  So that is
what you see.

Emacs being Emacs, you can programmatically change the bidirectional
class of every character, but that change has global effect: it will
affect the directionality of that character everywhere in the Emacs
session.  So this is not recommended.

Also this is not recommended, I would be willing to have the bidi class property of some characters set to left-to-right, like the example of the slash character. Can you point somewhere regarding this? I saw the get-char-code-property function but could not find anyway to actually change the setting.
 

The correct solution to these problems is to wrap the footnote block
in the LRE..PDF or LRI..PDI control characters, so that the footnote
is rendered independently of the surrounding bidirectional context.
See the example below.  Not sure if LaTeX will DTRT with directional
control characters, but if it doesn't, that's a bug/misfeature in
LaTeX.

\begin{hebrew}
  \pstart

בְּרֵאשִׁ֖ית‪\footnoteA{This is a Hebrew related footnote}‬ בָּרָ֣א אֱלֹהִ֑ים אֵ֥ת הַשָּׁמַ֖יִם וְאֵ֥ת הָאָֽרֶץ׃

  \pend
\end{hebrew}

In this example the direction of the surrounding Hebrew text has been changed. The word בְּרֵאשִׁ֖ית should come before (i.e. on the right) of the word בָּרָ֣א. So while the footnote command is correctly shown as LTR the Hebrew text has been changed. I don't think is is the expected. See the updated image (http://emacs.stackexchange.com/questions/19696/handling-left-to-right-inside-right-to-left-paragraphs-using-emacs-and-auctex) that shows TextEdit correct handling of this.
 

Another possibility is to insert newlines between the footnote and the
surrounding text, as shown below.  Not sure if LaTeX will be happy
with that, and I think it's uglier anyway.

\begin{hebrew}
  \pstart

בְּרֵאשִׁ֖ית

\footnoteA{This is a Hebrew related footnote}

בָּרָ֣א אֱלֹהִ֑ים אֵ֥ת הַשָּׁמַ֖יִם וְאֵ֥ת הָאָֽרֶץ׃

  \pend
\end{hebrew}

Unfortunately for my use case this is not possible. 

I don't think there's a bug to fix here, so I'm going to close this
bug report.  Any objections?

Is there any change of having a way to set the unicode bidirectionally of  a character within each separate mode? Could this be considered a feature?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]