ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Gour <gour@mail.inet.hr>
To: ntg-context@ntg.nl
Subject: Re: [Context] Xindy
Date: Sat, 13 Sep 2008 07:28:28 +0200	[thread overview]
Message-ID: <87vdx0d37n.fsf@gaura-nitai.no-ip.org> (raw)
In-Reply-To: <6faad9f00809121630m743d8816w97687ec8c2012754@mail.gmail.com> (Mojca Miklavec's message of "Sat, 13 Sep 2008 01:30:18 +0200")


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

>>>>> "Mojca" == Mojca Miklavec <mojca.miklavec.lists@gmail.com> writes:

Mojca> Hello Gour, This is not a question for this mailing list, but
Mojca> rather for Hans himself.

OK.

Mojca> ConTeXt doesn't use makeindex, so I don't really understand your
Mojca> complaints about makeindex.

Well, I mentioned 'makeindex' in the context of the tool which cannot
properly handle Unicode, afaik.

Mojca> What features exactly do you miss? 

I'm not sure if indexing-feature in ConTeXt allow me to use English,
Croatian and Sanskrit diacritics (not Devanagari) all in one document and define that I
want e.g. that \'{s}, \d{s} has to be sorted under 'Š' ?

In short, xindy allows one to define his own sort-rules.

Mojca> It makes no sense to discuss distributing something before it can
Mojca> be used with ConTeXt.)

Right, that's why also asked "Now I'm interested how is support for
Xindy in ConTeXt" hoping that the context-distribution list has enough
knowledgeable people able to answer it.

Excuse me for the noise...redirecting to other list...


Sincerely,
Gour

-- 

Gour  | Zagreb, Croatia  | GPG key: D19DB797
----------------------------------------------------------------

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

[-- Attachment #2: Type: text/plain, Size: 487 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

       reply	other threads:[~2008-09-13  5:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87fxo5nz6c.fsf@nitai.hr>
     [not found] ` <6faad9f00809121630m743d8816w97687ec8c2012754@mail.gmail.com>
2008-09-13  5:28   ` Gour [this message]
2008-09-13 10:21     ` Hans Hagen
2008-09-13 15:08       ` Gour
2019-07-21  8:35       ` translating LyX/LaTex book into ConTeXt (was Re: [Context] Xindy) Gour
2019-07-21 10:35         ` Hans Hagen
2019-07-21 10:39           ` Denis Maier
2019-07-22  9:06           ` translating LyX/LaTex book into ConTeXt Saša Janiška
     [not found] ` <48CABC90.1050203@elvenkind.com>
     [not found]   ` <20080912190750.GN21092@phare.normalesup.org>
     [not found]     ` <20080912191602.GO21092@phare.normalesup.org>
2008-09-13  6:09       ` test files for Xindy (was Re: [Context] Xindy) Gour

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=87vdx0d37n.fsf@gaura-nitai.no-ip.org \
    --to=gour@mail.inet.hr \
    --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).