ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Pablo Rodríguez" <oinos@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: wrong space when compressseparator is empty
Date: Thu, 27 Jun 2013 07:43:19 +0200	[thread overview]
Message-ID: <51CBD0F7.7020601@web.de> (raw)

Dear Hans,

I have the following sample:

    \showstruts
    \setupnote[linenote][paragraph=yes, inbetween=\hskip1.5em]
    \setupnotation[linenote][alternative=serried, compress=yes,
    compressseparator=, distance=1em]
    \starttext
    \startlinenumbering
    \dorecurse{500}{text\linenote{variant} }
    \stoplinenumbering
    \stoptext

that shows the following issue: when compressseparator is set to none,
ConTeXt doesn’t suppress the distance that comes after the separator at
the beginning of the line.

As a general rule, I think it would make sense to always suppress
distance after separator when the separator isn’t set (not only at the
beginning of the line). This wouldn’t only fix the issue described
above, but it would avoid that compressed linenotes have more separation
space than uncompressed ones.

Could you fix this?

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-06-27  5:43 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=51CBD0F7.7020601@web.de \
    --to=oinos@web.de \
    --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).