From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: Header number separator
Date: Thu, 9 Nov 2006 13:39:48 -0500 (EST) [thread overview]
Message-ID: <Pine.WNT.4.63.0611091326460.384@nqvgln> (raw)
In-Reply-To: <2e8813a0611090854i59a71b36uc06372f310a98b9b@mail.gmail.com>
On Thu, 9 Nov 2006, 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?
In principle, it should work fine for european languages. Lot of the
trickery with numbers and number formats is present because ConTeXt
also supports other languages like chinese and arabic.
@@longsectionnumber is used a lot by the sectioning macros, and I do
not completely understand what is happening here. My solution was
based on trial and error and figuring out what works.
Moreover, it changes a core feature of ConTeXt. I am associating
separators with sectioning levels rather than with heads. Right now,
in principle, you can have different separators for different heads at
the same level. For example
\setuphead[remark][section=section-4,separator=.]
\setuphead[note][section=section-4,separator=-]
With this change, this will no longer work. So, the macro is not
backward compatible, and thus can break existing code. If you have
only one head at each sectioning level, and do not plan to use Chinese
or Arabic, it should work fine. Atleast for my simple, 5 page
document, it works correctly :-)
Aditya
next prev parent reply other threads:[~2006-11-09 18:39 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 [this message]
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
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=Pine.WNT.4.63.0611091326460.384@nqvgln \
--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).