From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: ntg-context@ntg.nl
Subject: Re: (mkii) language-specific options for \placeregister[index] ?
Date: Fri, 21 Dec 2007 15:55:13 +0100 [thread overview]
Message-ID: <20071221155513.6395675a.schuster.wolfgang@googlemail.com> (raw)
In-Reply-To: <6FF5A11A-81D2-4C2B-92A6-F0AC74C46A67@st.estfiles.de>
On Wed, 19 Dec 2007 22:01:14 +0100
Steffen Wolfrum <context@st.estfiles.de> wrote:
> Am 19.12.2007 um 14:45 schrieb Wolfgang Schuster:
>
> > 2007/12/19, Steffen Wolfrum <context@st.estfiles.de>:
> >> Hi,
> >>
> >> the following (with mkii) is probably not the most pressuring topic
> >> to most of you ... apologies!
> >>
> >> Although I have set \mainlanguage[de] the register seems
> >> to be
> >> unaffected. All my cultural heritage (i.e. the Umaut) is ignored!!!
> >>
> >> o(
> >>
> >> The problem is the sorting – keywords containing umlauts seem to be
> >> sorted after "e":
> >>
> >> Bestimmung
> >> Bühler
> >> Bildung
> >>
> >> Are there language-specific arguments/options for
> >> \placeregister[index]?
> >>
> >> Thanks,
> >>
> >> Steffen
> >
> > Hi Steffen,
> >
> > Can you post a example where this did happen for you.
Hi Hans and all others,
I found the reason for the wrong index sorting in Steffens files.
The correct sorted file contains something like this.
\enableregime[utf]
\starttext
text\index{Bestimmung} text\index{Bühler} text\index{Bildung} text
\placeindex
\stoptext
The text is enclosed by the normal start/stoptext pair and the document
setup is written before the start of the document while the wrong file
contains this:
\starttext
\enableregime[utf]
text\index{Bestimmung} text\index{Bühler} text\index{Bildung} text
\placeindex
\stoptext
The files did not really contain start/stop but use ConTeXts document
structure and \everystarttext is executed by \startpoduct, the first
command in the product file.
The problem is now, ConTeXt write information for the index sorting
into the tui file and a few additional entries for every spcifiec file
encoding, in this utf-8.
This works quite well in the first example because \enableregime is
writte before \starttext while in the second example the sorting
information are written before ConTeXt knows the file encoding.
A workaround for the moment is to write \enableregime before
\startproduct in the main file but I hope this coule be fiyed in the
next release.
I still wonder why nobody noticed this untill now.
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2007-12-21 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 9:47 Steffen Wolfrum
2007-12-19 13:45 ` Wolfgang Schuster
2007-12-19 21:01 ` Steffen Wolfrum
2007-12-21 14:55 ` Wolfgang Schuster [this message]
2007-12-21 17:34 ` Hans Hagen
2007-12-21 18:01 ` Wolfgang Schuster
2007-12-21 18:35 ` Hans Hagen
2007-12-21 18:50 ` Wolfgang Schuster
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=20071221155513.6395675a.schuster.wolfgang@googlemail.com \
--to=schuster.wolfgang@googlemail.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).