ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Johan Sandblom" <jsandblom@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Johan.Sandblom@ki.se
Subject: Re: definesortkey
Date: Sat, 1 Apr 2006 21:49:54 +0200	[thread overview]
Message-ID: <97a06f070604011149g5b58877el5d72acd490d401da@mail.gmail.com> (raw)
In-Reply-To: <442D6105.8090909@wxs.nl>

Testfile below. Lowercase named letters (\aring etc) work fine.
Uppercase, however, are sorted under the letter they resemble (A, O).
Inputting the letter directly (å,ä,ö) make them be indexed before the
start of the alphabetized index, not even under a, o.

Regards, Johan

\mainlanguage[sv] \readfile{sort-ini}{}{}
\starttext
a\index{a}
z\index{z}
å\index{å}
ä\index{ä}
ö\index{ö}
\aring\index{\aring}
\adiaeresis\index{\adiaeresis}
\odiaeresis\index{\odiaeresis}
A\index{A}
Å\index{Å}
Ä\index{Ä}
Ö\index{Ö}
\Aring\index{\Aring}
\Adiaeresis\index{\Adiaeresis}
\Odiaeresis\index{\Odiaeresis}

\placeindex

\stoptext


2006/3/31, Hans Hagen <pragma@wxs.nl>:
> Johan Sandblom wrote:
> > I have a document in Swedish with an index. Merely setting
> > mainlanguage[sv] does not give correct sort order. I remember doing
> > something like
> >
> > \startlanguagespecifics[sv]
> > \definesortkey[�][z][a][�]
> > \definesortkey[�][z][b][�]
> > \definesortkey[�][z][c][�]
> > \stoplanguagespecifics
> >
> > but this no longer has any effect and gives
> >
> > TeXUtil | unknown entry k in line k {sv}{ec}{�}{z}{a}{�}
> > TeXUtil | unknown entry k in line k {sv}{ec}{�}{z}{b}{�}
> > TeXUtil | unknown entry k in line k {sv}{ec}{�}{z}{c}{�}
> >
> > from newtexexec (this is on a current windows standalone context)
> >
> > What is the correct code?
> >
> take a look in sort-ini and sort-def to see how it's done nowadasys
>
> then make a sample file so that we can test
>
> 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
> -----------------------------------------------------------------
>
>


--
Johan Sandblom  N8, MRC, Karolinska sjh
t +46851776108  17176 Stockholm
m +46735521477  Sweden
"What is wanted is not the will to believe, but the
will to find out, which is the exact opposite"
- Bertrand Russell
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

  reply	other threads:[~2006-04-01 19:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30 23:47 definesortkey Johan Sandblom
2006-03-31 17:04 ` definesortkey Hans Hagen
2006-04-01 19:49   ` Johan Sandblom [this message]
2006-04-03 22:08     ` definesortkey Hans Hagen
2006-04-03 23:31       ` definesortkey Mojca Miklavec
2006-04-04  7:56         ` definesortkey 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=97a06f070604011149g5b58877el5d72acd490d401da@mail.gmail.com \
    --to=jsandblom@gmail.com \
    --cc=Johan.Sandblom@ki.se \
    --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).