From: "Idris Samawi Hamid ادريس سماوي حامد" <Idris.Hamid@colostate.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: r2l alignment and linenumbering conflict?
Date: Sun, 2 Aug 2015 05:51:50 -0600 [thread overview]
Message-ID: <op.x2qokopuejo439@ishamid-pc> (raw)
In-Reply-To: <744B7EEA-9D1D-416E-AA76-7237786EBC8C@fastmail.fm>
On Sun, 02 Aug 2015 03:24:12 -0600, talazem@fastmail.fm
<talazem@fastmail.fm> wrote:
> Thanks for that, Wolfgang. I can only hope that, as the culprit is
> known, it can be apprehended!
Talal, here is a barbarous workaround using \thinrule:
======================
\setuppapersize[A6]
\starttext \showframe
\setupthinrules[color=white]
\setupwhitespace[big]
\section{Incorrect}
\startlinenumbering
\startalignment[r2l]
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque
molestie dictum quam non congue. Integer ut dolor vel mi vestibulum
molestie vel et nulla.\thinrule
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque
molestie dictum quam non congue. Integer ut dolor vel mi vestibulum
molestie vel et nulla.
\stopalignment
\stoplinenumbering
\section{Correct}
\startalignment[r2l]
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque
molestie dictum quam non congue. Integer ut dolor vel mi vestibulum
molestie vel et nulla.
\stopalignment
\stoptext
======================
This effectively hides the problem. Unfortunately it is apparently not
straightforward to invoke the \thinrule automatically at the end of every
paragraph [see the other thread with Alan].
Best wishes
Idris
--
Idris Samawi Hamid
Professor of Philosophy
Colorado State University
Fort Collins, CO 80523
___________________________________________________________________________________
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:[~2015-08-02 11:51 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 ادريس سماوي حامد [this message]
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
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=op.x2qokopuejo439@ishamid-pc \
--to=idris.hamid@colostate.edu \
--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).