From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: "Idris Samawi Hamid ادريس سماوي حامد" <Idris.Hamid@colostate.edu>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Hans Hagen <pragma@wxs.nl>
Subject: Re: bidi in footnotes
Date: Fri, 22 Jun 2018 22:13:22 +0200 [thread overview]
Message-ID: <5B2D5862.8070401@gmail.com> (raw)
In-Reply-To: <op.zk0xsip2ejo439@desktop-mt1m160>
[-- Attachment #1.1: Type: text/plain, Size: 1742 bytes --]
> Idris Samawi Hamid ادريس سماوي حامد <mailto:Idris.Hamid@colostate.edu>
> 22. Juni 2018 um 21:01
> On Thu, 21 Jun 2018 08:36:52 -0600, Alan Braslau
> <braslau.list@comcast.net> wrote:
>
>
> Many thanks. Is there (Hans? Wolfgang?) available somewhere
>
> 1. a complete list of these environments whose typographical settings
> are decoupled from the rest of the document?
The problem you mentioned isn’t limited to bidi but applies also to
linbreaking for east asian languages (e.g. chinese) and fixing it makes
sense.
The reason why you have to re-enable the functions is that certain
environment disable a number of Lua attributes to avoid side effects,
e.g. to change the footnote color when you change the text color at the
page break.
One way to fix this is to make the attributes of the affected commands
global which means they won’t be reseted, e.g. change the line
(typo-dir.mkiv)
\definesystemattribute[directions][public]
to
\definesystemattribute[directions][public,global]
Another way is to re-enable the commands in footnotes etc.
\appendtoks
\ifcase\directionsbidimode \else
\setdirection[\number\directionsbidimode]%
\fi
\to \everybeforenoteinsert
There are three parts in context where attributes are disabled which
affects bidi:
1. Note inserts which affects \footnote.
2. Margin data which affects \inmargin etc.
3. The output routine which affects header and footer lines.
2. a complete list of those typographical settings (bidi, whitespace,
etc,) which are have to explicitly setup for such environments?
Whitespace etc. are unrelated to the problem above and can be changed
with the normal setup-commands.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 3107 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-06-22 20:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 21:22 Idris Samawi Hamid ادريس سماوي حامد
2018-06-20 21:27 ` Mohammad Hossein Bateni
2018-06-21 4:31 ` Otared Kavian
2018-06-21 12:20 ` Idris Samawi Hamid ادريس سماوي حامد
2018-06-21 13:24 ` Mohammad Hossein Bateni
2018-06-21 14:36 ` Alan Braslau
2018-06-22 19:01 ` Idris Samawi Hamid ادريس سماوي حامد
2018-06-22 20:13 ` Wolfgang Schuster [this message]
2018-06-23 12:17 ` Idris Samawi Hamid ادريس سماوي حامد
2018-06-23 12:32 ` Idris Samawi Hamid ادريس سماوي حامد
2018-06-23 13:10 ` Wolfgang Schuster
2018-06-23 21:49 ` Idris Samawi Hamid ادريس سماوي حامد
2018-06-27 8:03 ` Wolfgang Schuster
2018-06-27 19:24 ` Idris Samawi Hamid ادريس سماوي حامد
2018-06-23 12:31 ` Idris Samawi Hamid ادريس سماوي حامد
2018-06-23 10:04 ` 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=5B2D5862.8070401@gmail.com \
--to=schuster.wolfgang@gmail.com \
--cc=Idris.Hamid@colostate.edu \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).