From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: r2l alignment and linenumbering conflict?
Date: Tue, 4 Aug 2015 23:06:42 +0200 [thread overview]
Message-ID: <55C12962.2050200@wxs.nl> (raw)
In-Reply-To: <30722134-227C-43CB-AD9F-9EE49E83506B@fastmail.fm>
On 8/4/2015 5:46 AM, talazem@fastmail.fm wrote:
> Hans, the beta is a solid step forward regarding bidi and Arabic support, and not just in footnotes. Thank you.
>
> However, it appears that my earlier declarations of ‘problem solved’ were a bit premature. Footnotes display everything correctly, but not linenumber notes. Using the three bidi methods of \setupdirections[bidi]:
>
> - ‘default’ orders the linenumber notes and their texts right-to-left, but any number therein is reversed (4102 instead of 2014).
let's first try to get that one right .. new beta coming (also needs
testing by idris
> - ‘one’ does not render either the note block nor the individual notes' texts right-to-left.
i have to rewrite that one using more efficient means (i really need 48
hour sin a day)
> - ‘two’ is identical to method ‘one’.
it is .. just a newer version of the unicode bidi one
> Compare these to regular footnotes, where everything is rendered correctly as of this new beta.
you can trace flagging in default with:
\enabletrackers[typesetters.directions.default]
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2015-08-04 21:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 15:30 talazem
2015-08-01 15:37 ` talazem
2015-08-01 18:04 ` Pablo Rodriguez
2015-08-01 18:35 ` Idris Samawi Hamid ادريس سماوي حامد
2015-08-01 18:47 ` Wolfgang Schuster
2015-08-02 9:24 ` talazem
2015-08-02 11:51 ` Idris Samawi Hamid ادريس سماوي حامد
2015-08-02 13:31 ` talazem
2015-08-02 17:15 ` Idris Samawi Hamid ادريس سماوي حامد
2015-08-02 20:46 ` talazem
2015-08-03 13:54 ` talazem
2015-08-03 14:56 ` Hans Hagen
2015-08-03 15:13 ` Hans Hagen
2015-08-03 15:42 ` Idris Samawi Hamid ادريس سماوي حامد
2015-08-03 15:56 ` Hans Hagen
2015-08-03 16:17 ` Idris Samawi Hamid ادريس سماوي حامد
2015-08-03 16:06 ` Idris Samawi Hamid ادريس سماوي حامد
2015-08-03 19:25 ` Otared Kavian
2015-08-03 23:30 ` Hans Hagen
2015-08-04 16:25 ` Otared Kavian
2015-08-03 15:19 ` Hans Hagen
2015-08-03 16:29 ` talazem
2015-08-03 16:52 ` talazem
2015-08-04 3:46 ` talazem
2015-08-04 21:06 ` Hans Hagen [this message]
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=55C12962.2050200@wxs.nl \
--to=pragma@wxs.nl \
--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).