ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Philipp A." <flying-sheep@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: In-text itemizations break spacing
Date: Tue, 4 Jan 2011 21:33:36 +0100	[thread overview]
Message-ID: <AANLkTikjfbfZsVbTCMUQ-4U7wAdpE=kynhLJyz8XZF6n@mail.gmail.com> (raw)
In-Reply-To: <2CF231BA-3911-4640-8DAC-E8BB92FD163A@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2077 bytes --]

2011/1/4 Wolfgang Schuster <schuster.wolfgang@googlemail.com>

> Am 04.01.2011 um 18:51 schrieb Philipp A.:
>
> 2011/1/4 Wolfgang Schuster <schuster.wolfgang@googlemail.com>
>
>> Make a example next time!
>>
>> [Example]
>>
>> Wolfgang
>>
>
> so [textdistance=medium] is the solution, thanks!
>
> nevertheless, i couldn’t find documentation about “textdistance”,
>
> The option was added last march and it’s now up to you to document it.
>
> The values for the key are
>
> none   : no distance between items
> small  : half the value of a normal space, can be stretched by half of a em
> medium : normal space distance, can be stretched by 1em
> big    : 1em, can be stretched or shrinked by a space width
> <skip> : e.g. 3pt plus 2pt minus 1pt
>

been there <http://wiki.contextgarden.net/Reference/en/setupitemgroup>, done
that <http://wiki.contextgarden.net/Reference/en/keyword:textdistance>.

> and i don’t think it to be very intuitive, that this changes the space to
> be more flexible.
>
> sorry but i forgot why we used these values, maybe a smaller stretch value
> for small and medium make sense
>

i don’t think so (or at least not much less), and i meant sth. different:
“textdistance=medium” does not mean “greater flexibility”, it does mean “no
change in flexibility, just in distance”. using medium as standard value
would be ok, though, because you get the flexible (=mostly better) behavior
as standard, and the rigid as option.

> would you mind telling me why this is the case, and why this isn’t standard
> behavior?
>
> backward compatibility, i would also prefer “medium” as default value
>

can’t we just screw backward compatibility at all costs here? i mean:
“medium” won’t make it worse in most cases, just better! (the maximum space
is 1em+1sp, so we probably will never get different hyphenation, but almost
always less overfull \hboxes)

also, \setbreakpoints[compound] should be standard in my opinion.

Wolfgang
>

thanks for the answer,

phil

[-- Attachment #1.2: Type: text/html, Size: 3719 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
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:[~2011-01-04 20:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 16:44 Philipp A.
2011-01-04 17:30 ` Wolfgang Schuster
2011-01-04 17:51   ` Philipp A.
2011-01-04 18:58     ` Wolfgang Schuster
2011-01-04 20:33       ` Philipp A. [this message]
2011-01-05  9:24         ` Wolfgang Schuster

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='AANLkTikjfbfZsVbTCMUQ-4U7wAdpE=kynhLJyz8XZF6n@mail.gmail.com' \
    --to=flying-sheep@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).