ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Header number separator
Date: Wed, 15 Nov 2006 15:38:11 +0000	[thread overview]
Message-ID: <455B3463.8060502@wxs.nl> (raw)
In-Reply-To: <Pine.WNT.4.63.0611141147290.1620@nqvgln>

Aditya Mahajan wrote:
> On Tue, 14 Nov 2006, Hans Hagen wrote:
>
>> Jeff Smith wrote:
>>> On 11/7/06, Aditya Mahajan <adityam@umich.edu> wrote:
>>>
>>>
>>>
>>>> I need this functionality for a project (IEEE conference style), so
>>>> here is hack to get the feature. The referencing also works.
>>>>
>>>> Use with caution, can break existing macros.
>>>>
>>>
>>> Wow, thanks a lot! This works as expected. In what situation can it
>>> break existing macros? I intend to use that extensively but in a
>>> fairly simple document (a thesis... yeah, another one in ConTeXt!). Is
>>> there anything I should _not_ do?
>>>
>> hm, can on esummarize what will break macros? (i was away for a week 
>> with time for email)
>
> A patch that I sent to Jeff. There is a problem with separators and 
> setuphead. I have summarized the problem and a possible patch in the 
> attached file. However, I do not know if it will break something in 
> multi-lingual documents (esp. Arabic), so I sent the patch with a 
> disclaimer.
i took a quick look at it; the problem is that it will mess up other things; the period in fullsectionnumber is a placeholder that will be replaced later on; the actual code where things happen in \doseparatednumber and it's not that easy to hook level dependent separators in there 

(i will reimplement sectionnumbering some day soon due to some other pending issues) 

anyhow, here's another approach: 

\starttext

\unexpanded\def\seplist#1%
  {\ifx\sepnumber\undefined\def\sepnumber{0}\fi
   \increment\sepnumber
   \getfromcommacommand[#1][\sepnumber]%
   \ifx\commalistelement\empty
     \getcommalistsize[#1]%
     \def\sepnumber{\number\commalistsize}%
     \getfromcommacommand[#1][\sepnumber]%
   \fi
   \commalistelement}

% \setuphead[section]   [separator=\seplist{?,!,*}]
% \setuphead[subsection][separator=\seplist{??,!!,**}]

\let\spr\seplist % quick hack 

% \setuphead[section]   [separator={?,!,*}]
% \setuphead[subsection][separator={??,!!,**}]

\setupheads[separator={A,B,C,D,E,F}]

\chapter{test}
\section{test}
\subsection{test}
\subsection{test}
\section{test}
\subsection{test}
\subsection{test}

\stoptext


Hans 


-----------------------------------------------------------------
                                          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
-----------------------------------------------------------------

  parent reply	other threads:[~2006-11-15 15:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 19:43 Jeff Smith
2006-11-07 21:42 ` Aditya Mahajan
2006-11-07 22:22   ` Aditya Mahajan
2006-11-09 16:54     ` Jeff Smith
2006-11-09 18:39       ` Aditya Mahajan
2006-11-14 11:33       ` Hans Hagen
2006-11-14 16:53         ` Aditya Mahajan
2006-11-14 16:57           ` Hans Hagen
2006-11-15 15:38           ` Hans Hagen [this message]
2006-11-16  1:14             ` Aditya Mahajan

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=455B3463.8060502@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).