ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \setupbreakpoint[compound] not working
Date: Fri, 19 Apr 2013 00:59:02 -0400	[thread overview]
Message-ID: <49E9C76A-AD79-44D2-B05A-0EF145BD9F22@umich.edu> (raw)
In-Reply-To: <8E73F13E-CABE-46E5-8682-854A78BF352B@gmail.com>


On 2013-04-19, at 12:34 AM, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:

> 
> Am 19.04.2013 um 01:53 schrieb Aditya Mahajan <adityam@umich.edu>:
> 
>> Hi,
>> 
>> I do not get a line-break after a dash if I set
>> 
>> \setupbreakpoint[compound]
>> 
>> Minimal example (tested with 2013.04.14 MkIV)
>> 
>>   \setbreakpoints[compound]
>> 
>>   \setuppapersize[S3]
>> 
>>   \showframe
>>   \starttext
>> 
>>   ABCD
>>   node-to-node
>>   node-to-node
>>   node-to-node
>>   node-to-node
>> 
>>   \stoptext
>> 
>> See the attached file for output. Is it a bug, or am I missing something.
> 
> The breakpoint command expects a certain number of characters at
> the left and right side of the symbol before it performs a line break.
> 
> See also:
> 
> - http://www.ntg.nl/pipermail/ntg-context/2012/070340.html
> - http://www.ntg.nl/pipermail/ntg-context/2012/070344.html

Thanks.

Aditya
___________________________________________________________________________________
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-04-19  4:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18 23:53 Aditya Mahajan
2013-04-19  4:34 ` Wolfgang Schuster
2013-04-19  4:59   ` Aditya Mahajan [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=49E9C76A-AD79-44D2-B05A-0EF145BD9F22@umich.edu \
    --to=adityam@umich.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).