ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: some difficulties with btxlist
Date: Mon, 25 Apr 2016 17:16:24 +0200	[thread overview]
Message-ID: <571E34C8.5040507@gmx.es> (raw)
In-Reply-To: <571D3FC9.3090108@uni-bonn.de>

On 04/24/2016 11:51 PM, Thomas A. Schmitz wrote:
> Hi all (in particular Hans and Alan...),
> 
> I'm finishing a book project where I'm using the new bibliographic 
> system. Everything is working as it should, but I have two problems with 
> line breaks:
> 
> 1. Page numbers in ranges are separated by an n-dash (as in: 234–567). 
> It looks as though ConTeXt doesn't break lines at this n-dash. I'm sure 
> there must be an easy way to tell TeX that this is a legitimate 
> breakpoint (short of inserting some \penalty manually after every 
> n-dash), but I can't figure it out myself.

Hi Thomas,

this should do the trick:

    \definebreakpoint
        [compound]
        [—]% em-dash

    \definebreakpoint
        [compound]
        [–]% en-dash

    \setbreakpoints
        [compound]

I hope it helps,

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:[~2016-04-25 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-24 21:51 Thomas A. Schmitz
2016-04-25 15:16 ` Pablo Rodriguez [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=571E34C8.5040507@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).