ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: two buglets
Date: Tue, 5 Oct 2010 15:29:38 +0200	[thread overview]
Message-ID: <27D66F2D-88F8-438F-909F-73CF8B17679A@uni-bonn.de> (raw)
In-Reply-To: <20101005121543.GD13466@aides>


On Oct 5, 2010, at 2:15 PM, Philipp Gesang wrote:
> 
> Hi Thomas and others,
> 
> technically speaking the problem is solved by ISO 14651.[1]
> 
> In praxi multilingual sorting depends on local rules, of
> which “One index per script|language.” seems to be the most
> common.

Yes, that's what I was trying to say. In practice, hardly anyone will want an individual index for Spanish  if they have just two Spanish words in an English book. And someone (me) might say that they want three Greek terms in their German index at logical places. 

> 
> Some time ago I made an lpeg from the bnf in [1]. It matches the
> collation rules from [2], but as I couldn’t figure out how to map
> them onto context’s sorting mechanism I never got around to
> actually capture the information. As I won’t be having the time
> to try it with the new structure of sort-lan I guess I’ll just
> attach the peg grammar for anyone to use as a starting point.
> Unicode collation would be great to have in context.
> 
>> transliteration. The problem with polytonic Greek is that so many
>> different unicode characters need to have the same sort entry. If
> 
> Isn’t that just what the Greek rules in sort-lan.lua do? If not
> then it would be a bug.
> 
Oh yes, you're right, I missed that. Thanks for pointing that out!

Thomas

___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2010-10-05 13:29 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 [this message]
2010-10-05 21:17                 ` Philipp Gesang
2010-10-05 21:27                   ` Hans Hagen
2010-10-05 21:55                     ` Philipp Gesang
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=27D66F2D-88F8-438F-909F-73CF8B17679A@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.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).