ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: Sections with additional dot: a little request
Date: Sun, 19 Feb 2006 16:38:20 +0100	[thread overview]
Message-ID: <6faad9f00602190738r33c6b025hfd2ef4a149a82d33@mail.gmail.com> (raw)
In-Reply-To: <43F70AAC.2030504@wxs.nl>

On 2/18/06, Hans Hagen wrote:
> Mojca Miklavec wrote:
> > Hello Hans,
> >
> > The sections in Slovenian have to be numbered wih dots at the end:
> >
> > 1. Introduction
> > 2. Contents
> > 2.1. Subsection
> > 2.1.1. Subsubsection
> > 2.1.2. Subsubsection
> > 2.2. Subsection
> > 2.3. Subsection
> > 3. Bibliography
> >
> > rather than
> >
> > 1  Introduction
> > 2  Contents
> > 2.1  Subsection
> > 2.1.1  Subsubsection
> > 2.1.2  Subsubsection
> > 2.2  Subsection
> > 2.3  Subsection
> > 3  Bibliography
> >
> > There are many commands in ConTeXt which support "delimiter" key, but
> > here the delimiter already stands for the dot delimiting subsequent
> > numbers in this case.
> >
> a quick way out:
>
> \setuplabeltext
>   [sl]
>   [chapter={{},{.}}]

Thanks a lot. It's an interesting trick.

> it is no problem to provide some language dependent conversion handling, but then i'd like to implement everything at once (i know that hungarian also has special demands).
>
> so ... best is t o start meking a 'document' with proposed extensions (to which other users can add their wishes); most of what you need, is not that hard to implement, but i'd like to do it all at once

Wiki is a perfect place for such a thing. (I also have some other
half-written page about language support to be placed there.)

I can only hope that anyone is reading this and will reply or leave a
note on the wiki about his or her requests.

Thanks,
   Mojca

  reply	other threads:[~2006-02-19 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18  4:32 Mojca Miklavec
2006-02-18 11:53 ` Hans Hagen
2006-02-19 15:38   ` Mojca Miklavec [this message]
2006-02-20  8:37     ` 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=6faad9f00602190738r33c6b025hfd2ef4a149a82d33@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).