ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Sections with additional dot: a little request
Date: Sat, 18 Feb 2006 05:32:42 +0100	[thread overview]
Message-ID: <6faad9f00602172032x43db81b3v88da06a4676d0efc@mail.gmail.com> (raw)

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.

There's a possible solution listed on
http://wiki.contextgarden.net/Dotted_number_in_caption, ie:

\def\Dot#1{#1.}
\setuphead[section][numbercommand=\Dot]
\setuplist[section][numbercommand=\Dot]
\setuplist[subsection][numbercommand=\Dot]
\setuplist[subsubsection][numbercommand=\Dot]

but this cannot be built into "languagespecifics" as such since it
interferes with user-defined "numbercommands" (if the user defines his
own numbercommand, the dot would disapear).

This is low-priority (can be circumvented and done properly if
needed), but I would be very glad if an additional keyword & its
setting could make its way into "languagespecifics" once in the future
if possible.

LaTeX people did that (not aplicable to ConTeXt at all):

\renewcommand\thepart         {\@Roman\c@part}
\renewcommand\thesection      {\@arabic\c@section.}
\renewcommand\thesubsection   {\thesection\@arabic\c@subsection}
\renewcommand\thesubsubsection{\thesubsection.\@arabic\c@subsubsection}
\renewcommand\theparagraph    {\thesubsubsection.\@arabic\c@paragraph}
\renewcommand\thesubparagraph {\theparagraph.\@arabic\c@subparagraph}

\renewcommand\appendix{\par
  \setcounter{section}{0}%
  \setcounter{subsection}{0}%
  \renewcommand\thesection{\@Alph\c@section.}}


Also, Part 1 may be written as "1. poglavje" (with dot) or "Poglavje
1" (without dot), so there has to remain an option to remove a dot
only for a certain title if necessary.

The only online reference I know (list of mistakes in babel) is
written in Slovenian
http://nl.ijs.si/gnusl/tex/tslovene/slolang/node98.html-l2#SECTION0002031400000000000000
but I guess that the content can at least partially be evident from
the TeX sources.

Once again the same comment as the last time with itemizing. If this
will ever be implemented and added, it will change the behaviour (and
break the old behaviour in a way), but I guess that there are not so
many people typesetting Slovenian in ConTeXt yet. There will be less
harm if a few old documents are fixed than if tons of other newer
documents are typeset wrong.

Thanks a lot,
    Mojca

             reply	other threads:[~2006-02-18  4:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18  4:32 Mojca Miklavec [this message]
2006-02-18 11:53 ` Hans Hagen
2006-02-19 15:38   ` Mojca Miklavec
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=6faad9f00602172032x43db81b3v88da06a4676d0efc@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).