ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <pgesang@ix.urz.uni-heidelberg.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: two buglets
Date: Tue, 5 Oct 2010 23:55:12 +0200	[thread overview]
Message-ID: <20101005215512.GF13466@aides> (raw)
In-Reply-To: <4CAB9845.9040603@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1670 bytes --]

On 2010-10-05 <23:27:33>, Hans Hagen wrote:
> On 5-10-2010 11:17, Philipp Gesang wrote:
> 
> >I guess there is some testing going on in order to determine
> >whether to proceed with the current entry or switch to the next
> >one. The position is the same, however the comparison with the
> >last item fails and a new one is created instead. (Only
> >guessing.)
> 
> it's a sequence of tests per comparison, like
> 
> Polyneikes
>     polyneikes % lowercased
>     polyneikes % shapes

I assume by “shapes” you mean the base symbol (all diacritics
stripped).

>     Polyneikes % unicode
> 
> Πολυνείκης
>     Πολυνείκης % lowercased
>     polyneikes % shapes
>     Πολυνείκης % unicode
> 
> casing and shapes depends on the mapping vectors and the order can
> be influenced, you can see this in action with
> 
> \enabletrackers[sorters.tests]

Bingo! The tracker instantly revealed a really nasty flaw in the
German standard transcription for Greek: “υ” is normally
converted to Latin “y”, but is retained as Latin “u” in
diphthongs like “ευ” and “ηυ”. So with the sorting definition I
posted I get amongst the results:

sorters         > Kapaneys > Kapaneus

because all “υ” are lazily mapped to “y”. Thus, for those
occasional three words per book, determining the sorting position
by hand (e.g. “\index[Kapaneus]{Καπανεύς}”) might be less prone
to error.

Thanks for the hint and sorry for posting a non-solution,

Philipp


-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 bytes --]

___________________________________________________________________________________
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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2010-10-05 21:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 15:52 Thomas A. Schmitz
2010-02-11 17:17 ` Hans Hagen
2010-02-11 17:35   ` Thomas A. Schmitz
2010-02-11 19:29     ` Hans Hagen
2010-02-11 21:27       ` Thomas A. Schmitz
2010-02-11 18:14   ` David Rogers
2010-10-03  8:24   ` Thomas A. Schmitz
2010-10-03 10:29     ` Hans Hagen
2010-10-03 10:58       ` Thomas A. Schmitz
2010-10-03 15:10         ` Hans Hagen
2010-10-03 15:43           ` Thomas A. Schmitz
2010-10-05 12:15             ` Philipp Gesang
2010-10-05 12:39               ` Hans Hagen
2010-10-05 13:29               ` Thomas A. Schmitz
2010-10-05 21:17                 ` Philipp Gesang
2010-10-05 21:27                   ` Hans Hagen
2010-10-05 21:55                     ` Philipp Gesang [this message]
2010-10-06  7:50                       ` Hans Hagen
2010-02-11 17:19 ` 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=20101005215512.GF13466@aides \
    --to=pgesang@ix.urz.uni-heidelberg.de \
    --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).