From: Mohammad Hossein Bateni <bateni@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Paragraph breaking bug with BiDi text
Date: Mon, 11 Jan 2016 11:58:19 -0500 [thread overview]
Message-ID: <CAMHZ1daycGe12tGeseLWmRj3uW3d11PVrYWtFTEysO+UttVZMg@mail.gmail.com> (raw)
In-Reply-To: <5693B180.9090506@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1552 bytes --]
>
> It is a side effect of what the the par builder considers to be valid
> breakpoints. The current approach is playing very safe but after looking at
> it Taco and I decided that it can be a more tolerant with respect to end
> dirs so the next luatex version will have that.
>
> Anyway: You need to code carefully: the space after "TRT" in "\textdir TRT
> x" is meaningful so in your example you introduce spaces.
>
Thanks for the explanation. So the space after \textdir TLT is meaningful
but the one after \lefttoright isn't. (I guess, I should have used
\textdir TLT\relax. I'm going to use the high-level \lefttoright command
from now on.)
Also, in context don't use \textdir etc directly, just use \lefttoright and
> \righttoleft in combination with \setupalign as I will not spend much time
> on side effects of interfering with these low level dir changers directly.
>
Great! You partly answered another question I meant to ask: what is the
proper way to write \textdir and \pardir in CONTEXT? So \lefttoright and
\righttoleft are replacements for \textdir TLT and \textdir TRT. How
should I code in \pardir TRT in CONTEXT? I couldn't find anything for that
in spac-ali.mkiv.
Those low-level LuaTeX directives were part of an attempt to come to the
core of a problem I'd run into with numbers at the end of a right-to-left
line. The BiDi algorithm correctly gave left-to-right direction to that
digit sequence and the result was that the word following the number had
gone into the margin.
—MHB
[-- Attachment #1.2: Type: text/html, Size: 2109 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2016-01-11 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 3:40 Mohammad Hossein Bateni
2016-01-09 3:47 ` Mohammad Hossein Bateni
2016-01-11 13:43 ` Hans Hagen
2016-01-11 16:58 ` Mohammad Hossein Bateni [this message]
2016-01-11 19:24 ` Wolfgang Schuster
2016-01-11 21:52 ` Hans Hagen
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=CAMHZ1daycGe12tGeseLWmRj3uW3d11PVrYWtFTEysO+UttVZMg@mail.gmail.com \
--to=bateni@gmail.com \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).