ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: some problems with current
Date: Mon, 20 Jul 2009 19:03:27 +0200	[thread overview]
Message-ID: <4A64A35F.2040006@wxs.nl> (raw)
In-Reply-To: <alpine.LNX.2.00.0907200913020.15651@gaston.couberia.bzh>

Peter Münster wrote:
> Hello,
> 
> Here some minimal examples showing some problems:
> 
> 1.) Number missing before first item:
> 
> \starttext
> \startitemize[n][start=0]
> \item zero is missing here
> \item bla
> \item bla
> \stopitemize
> \stoptext

fixed, counters now have criterium=strict|all|positive

> 2.) Problem with \FlushStep:
> 
> \usemodule[pre-stepwise]
> \setupinteraction[state=start]
> \starttext
> \chapter{Footnote and stepwise}
> \StartSteps
> \startitemize
> \item bla\FlushStep             % 1. step: nothing
>   \footnote{footnote}\FlushStep % 2. step: only footnote, not the \item
> \item bla\FlushStep             % 3. step: first \item
> \stopitemize                    % second \item never appears
> \StopSteps
> \stoptext

fixed (had to do with optimization of layout components shown on layer; 
will always be somewhat messy

> 
> 3.) ERROR: LuaTeX error lpdf-ano.lua:340: attempt to
>     index global 'urls' (a nil value):
> 
> \setupinteraction[state=start]
> \starttext
> \goto{bla}[url(bla)]
> \stoptext

fixed

> 4.) \placeheadtext[chapter] showing section title:
> 
> \starttext
> \chapter{my chapter title}
> \section{my section title}
> test: \placeheadtext[chapter]
> \stoptext

fixed

> 5.) \setcatcodetable\prtcatcodes no more working:
> 
> \unprotect
> \def\bla@bla{sec title}
> \def\mySection{{\setcatcodetable\prtcatcodes\section{\bla@bla}}}
> \protect
> \starttext
> \mySection
> bla bla
> \stoptext

fixed, that is for the moment you need to set

catcodes=auto

or

catcodes=prtcatcodes

(in which case you can leave out the \setcatcodetable)

this mechanism is 'work in progress'as we also have to deal with complex 
  either or not expanded xml cases and i don't want to break too much of 
thomas's documents)

> 6.) "x.\ " should produce a normal space, not a wide space as "x. ":
> 
> \starttext
> x. x, x.\ x,\ x
> \stoptext 

actually i made it space, in order to make \space the same but a space 
and \ is not the same ... kind of a dilemma

\starttext

\bgroup
\unexpanded\def\ {\mathortext\normalspaceprimitive\space}
x. x, x.\ x,\ x \par
x. x, x.\space x,\ x \par
\let\ = \normalspaceprimitive x. x, x.\ x,\ x \par
\egroup

\bgroup
\unexpanded\def\ {\mathortext\normalspaceprimitive\space}
x. x \par
x.\ x \par
x.\space x \par
\let\ = \normalspaceprimitive x.\ x \par
\egroup

\stoptext

\stoptext


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2009-07-20 17:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20  7:38 Peter Münster
2009-07-20 17:03 ` Hans Hagen [this message]
2009-07-21  7:13   ` Peter Münster
2009-07-21 21:23     ` Hans Hagen

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=4A64A35F.2040006@wxs.nl \
    --to=pragma@wxs.nl \
    --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).