From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: (critical edition) compressseparatorbefore and compressseparatorafter
Date: Mon, 18 Nov 2013 21:19:04 +0100 [thread overview]
Message-ID: <528A7638.1060505@gmx.es> (raw)
Dear Thomas, Luigi and Hans,
code first:
\definepapersize[mine][width=3in,height=2in]
\setuppapersize[mine]
\definelinenote[Variant]
\setupnote[Variant][paragraph=yes, inbetween=\hskip2.5em]
\setupnotation[Variant][alternative=serried,distance=1em,compress=yes,
width=broad]
\starttext
\startlinenumbering
This\Variant{That} context\Variant{document} is\Variant{was} a
sample\Variant{an example} that I\Variant{she} want\Variant{didn’t
want} to show\Variant{publish}\stoplinenumbering
\stoptext
With compressed linenotes (when compressseparator isn’t set to none), I
think is important to have the ability to specify different lengths for
the compressseparator than for the linenotes.
If neither of them is defined, compressseparatorbefore should have the
same value as inbetween from setupnote and compressseparatorafter should
take its value from distance in setupnotation.
But with the sample above, I think that the spacing that can make sense
for line numbers might be visually misleading for separators.
Here I’m only an amateur, Thomas, you are the professional. What do you
think of this feature?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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
___________________________________________________________________________________
reply other threads:[~2013-11-18 20:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=528A7638.1060505@gmx.es \
--to=oinos@gmx.es \
--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).