unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: RTL lines
Date: Thu, 28 Oct 2021 09:03:11 +0200	[thread overview]
Message-ID: <20211028070311.GA17431@tuxteam.de> (raw)
In-Reply-To: <3345060.FcSoDe5yjW@galex-713.eu>

[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]

On Thu, Oct 28, 2021 at 08:08:53AM +0200, Alexandre Garreau wrote:

[...]

> Oh ok, but do they define what a paragraph is?

This is... complicated. See [0], especially [1], and the references
from there. My take (but note that I'm an analphabet here) is that
there usually will be a surrounding level of "markup" (e.g. XML,
HTML, something else) which decides what a paragraph is. The usual
convention of an empty line separating paragraphs is fine as that
"surrounding level", too. Unicode also has a "paragraph separator",
\u2029, in case you need one.

However that separation is done, the BIDI algorithm doesn't care.
It works exclusively whithin one paragraph, whatever happens in one
paragraph doesn't touch the others, and thus it wants to be fed
single paragraphs.

Read the refs. Very instructive (and you'll learn to appreciate a
bit more what a labour of love Eli has been doing before he became
our maintainer).

Cheers

[0] https://www.unicode.org/reports/tr9/
[1] https://www.unicode.org/reports/tr9/#Basic_Display_Algorithm

 - t

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2021-10-28  7:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 12:40 RTL lines Alexandre Garreau
2021-10-18 13:18 ` Eli Zaretskii
2021-10-27 19:26   ` Alexandre Garreau
2021-10-28  6:04     ` Eli Zaretskii
2021-10-28  6:08       ` Alexandre Garreau
2021-10-28  7:03         ` tomas [this message]
2021-10-28  8:59         ` Eli Zaretskii
2021-10-27 14:50 ` Verticality and future of display engine and lines (bis) [Was: Re: RTL lines] Alexandre Garreau
2021-10-27 16:18   ` Eli Zaretskii
2021-10-27 18:46     ` Alexandre Garreau
2021-10-27 18:58       ` Eli Zaretskii
2021-10-27 19:54         ` Alexandre Garreau
2021-10-28  6:53           ` Eli Zaretskii
2021-10-28  7:12             ` Alexandre Garreau
2021-10-28  9:23               ` Eli Zaretskii
2021-10-28 14:40                 ` Alexandre Garreau
2021-10-28 16:11                   ` Eli Zaretskii
2021-10-28  7:18             ` Alexandre Garreau
2021-10-28  9:28               ` Eli Zaretskii
2021-10-28 14:28                 ` Alexandre Garreau
2021-10-28 16:07                   ` Eli Zaretskii

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=20211028070311.GA17431@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@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.
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).