ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: Alan Braslau <alan.braslau@cea.fr>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: itemize[n] and dejavu fonts
Date: Tue, 7 Apr 2015 13:37:54 +0200	[thread overview]
Message-ID: <72589532-F154-4878-A17F-CC1F93F3A796@gmail.com> (raw)
In-Reply-To: <20150407133143.0a7bbb1b@iram-ha-003840.extra.cea.fr>


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


> Am 07.04.2015 um 13:31 schrieb Alan BRASLAU <alan.braslau@cea.fr>:
> 
> On Tue, 7 Apr 2015 12:39:08 +0200
> Wolfgang Schuster <schuster.wolfgang@gmail.com <mailto:schuster.wolfgang@gmail.com>> wrote:
> 
>> 
>>> Am 07.04.2015 um 12:29 schrieb Alan BRASLAU <alan.braslau@cea.fr>:
>>> 
>>> On Tue, 7 Apr 2015 11:46:06 +0200
>>> Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
>>> 
>>>>> MWE:
>>>>> 
>>>>> \setupbodyfont [dejavu,10pt]
>>>>> \starttext
>>>>> \startitemize [n]
>>>>> \dorecurse{10}{\startitem X\stopitem}
>>>>> \stoptext
>>>>> 
>>>>> (switching to 100 items is even worse!)  
>>>> 
>>>> You missed the \stopitemize after the last item.
>>> 
>>> Just in the email (and so-called MWE)
>>> but not in the test (and my applications).
>>> 
>>> Adding the missing \stopitemize in the MWE above
>>> does not change the problem.
>> 
>> When I add \stopitemize to your example and use the fit option which
>> is missing in your example there are no problems in the output but
>> you have to use the distance key to put a space between the last item
>> number and the content.
>> 
>> \setupbodyfont [dejavu,10pt]
>> \starttext
>> \startitemize [n,fit]%[itemalign=flushright,distance=\spaceamount]
>> \dorecurse{100}{\startitem X\stopitem}
>> \stopitemize
>> \stoptext
> 
> "fit" is without effect,
> so it is distance= that does not have a reasonable default.
> 
> Other fonts are not so bad, but dejavu (which is a bit larger)
> looks really bad, by default.

Can you show your output from the example and tell what you expect from the fit option.

Wolfgang

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

[-- Attachment #2: Type: text/plain, Size: 485 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:[~2015-04-07 11:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07  9:14 Alan BRASLAU
2015-04-07  9:46 ` Wolfgang Schuster
2015-04-07 10:29   ` Alan BRASLAU
2015-04-07 10:39     ` Wolfgang Schuster
2015-04-07 11:31       ` Alan BRASLAU
2015-04-07 11:37         ` Wolfgang Schuster [this message]
2015-04-07 12:16           ` Alan BRASLAU

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=72589532-F154-4878-A17F-CC1F93F3A796@gmail.com \
    --to=schuster.wolfgang@gmail.com \
    --cc=alan.braslau@cea.fr \
    --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).