<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general">
    <title>gmane.comp.text.xindy.general</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/955"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/954"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/953"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/952"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/951"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/950"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/949"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/948"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/947"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/946"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/945"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/944"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/943"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/942"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/941"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/940"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/939"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/938"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/937"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.text.xindy.general/936"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/955">
    <title>Tricky ignore-special</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/955</link>
    <description>&lt;pre&gt;Hi everybody !

I am building a new language rule set in order to create a dictionnary in
this language.

Let's say that we have the following entries:

"ko" a simple root ;
"ko=" a proclitic ;
"=ko" an enclitic ;
"ko-" a prefix and
"-ko" a suffix.

The equal and minus signs are linguistic metadata explaining what kind of
"word" it is. They are not actual letters.

 I want those entries to be sorted in the following order:
"ko" ; "ko=" ; "=ko" ; "ko-" and "-ko"

How do I set the "ignore special" part in the perl script to make the equal
(=) and the minus (-) signs to be ignored, but to make the word they follow
(or are followed by) be placed in the correct order ?

Thank you in advance to anyone who can help !

Best,

Pierric Sans
--
+33 (0)6 98 58 30 01
--
------------------------------------------------------------------------------
Try New Relic Now &amp;amp; We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Opt&lt;/pre&gt;</description>
    <dc:creator>Pierric Sans</dc:creator>
    <dc:date>2013-04-27T12:33:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/954">
    <title>Re: Spurious \hyperpage</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/954</link>
    <description>&lt;pre&gt;Am Mon, 25 Feb 2013 21:33:39 +0100 schrieb Joachim Schrod:



Yes. I do find it quite strange too ;-)


Sorry I meant naturally 

(markup-locref :open "" :close "" :attr "hyperpage")

(so that I overwrite the definition, but that naturally deactivate
hyperlinks).


Btw: Is it possible to "group" numbers in a location class? Or to
tell xindy which depth should be repeated in a list?

As an example if I have

(define-location-class "AusgabeB" 
  ("roman-numerals-uppercase"  
   "roman-numerals-lowercase"
   "arabic-numbers")
   :hierdepth 3) 

and Instances "Ii1" and  "Ii2" then I get in the Index
"Ii1, 2"  but I would like to get "Ii1, i2"



&lt;/pre&gt;</description>
    <dc:creator>Ulrike Fischer</dc:creator>
    <dc:date>2013-02-26T09:33:47</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/953">
    <title>Re: Spurious \hyperpage</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/953</link>
    <description>&lt;pre&gt;
To get you some feedback: I can confirm that error, but I don't know
yet the root cause, further analysis is needed. It's very strange. 
\hyperpage should only be output when the location attribute
"hyperpage" is used.


ack.


That I can't reproduce. Such a markup-locref clause is already given.

Cheers,
Joachim

&lt;/pre&gt;</description>
    <dc:creator>Joachim Schrod</dc:creator>
    <dc:date>2013-02-25T20:33:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/952">
    <title>Spurious \hyperpage</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/952</link>
    <description>&lt;pre&gt;I have the following minimal example:

\documentclass{article}
\usepackage{makeidx}
\makeindex
\begin{document}
\renewcommand\thepage{I\arabic{page}}
abc\index{abc}
\end{document}

And I have a test.xdy width this definition:

(define-location-class "Ausgabe" 
  ("roman-numerals-uppercase"  
   "arabic-numbers")
   :hierdepth 2) 

When I call

   xindy -M texindy -M test -L german-duden -C utf8 test.idx

I end with an unwanted \hyperpage command in the .ind:

  \item abc, \hyperpage{I1}

(My actual example is more complicated and there I even get nested
\hyperpage commands).

Where does it come from? 

It disappears if I remove the ":hierdepth 2". 

It also disappears if I add
(markup-locref :open "\hyperpage{" :close "}{}" :attr "hyperpage")

But both "solutions" are not really an option.



&lt;/pre&gt;</description>
    <dc:creator>Ulrike Fischer</dc:creator>
    <dc:date>2013-02-24T15:57:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/951">
    <title>Re: Attributes and cross-references</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/951</link>
    <description>&lt;pre&gt;Am Sat, 23 Feb 2013 12:25:33 +0100 schrieb Joachim Schrod:


 
 

No this wouldn't work: the idea I had in my mind uses quite a lot
attributes and I would end with too much combinations. Also it
doesn't feel right to create something so artificial like a "seebf".
I think the correct way would be too use two distinct index commands
directly one after the other. But I will have to test if it gives
the expected result. 



&lt;/pre&gt;</description>
    <dc:creator>Ulrike Fischer</dc:creator>
    <dc:date>2013-02-23T17:02:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/950">
    <title>Re: Attributes and cross-references</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/950</link>
    <description>&lt;pre&gt;
You may declare a cross reference class "seebf" and define its markup
such that it's typeset in boldface.

Best,
Joachim

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
&lt;/pre&gt;</description>
    <dc:creator>Joachim Schrod</dc:creator>
    <dc:date>2013-02-23T11:25:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/949">
    <title>Attributes and cross-references</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/949</link>
    <description>&lt;pre&gt;The xindy faq (http://xindy.sourceforge.net/doc/faq-1.html) claims
regarding attributes and cross-references

"Here we distinguish cleanly between attributes and cross
references."

But actually with LaTeX both uses the same syntax in index commands:

\index{attribute|textbf}
\index{markup|see{attribute}}

So what can I do, if I want both?

\index{textbf|textbf see{attribute}} doesn't work.

&lt;/pre&gt;</description>
    <dc:creator>Ulrike Fischer</dc:creator>
    <dc:date>2013-02-22T14:29:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/948">
    <title>Xindy on Mac OS 10.8</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/948</link>
    <description>&lt;pre&gt;Hi Simon,

Thank you very much for responding to my message regarding running
xindy on Mac OS X 10.8 - the fact that you have xindy running on 10.8
is good to hear :-)

Would you mind tarring up your xindy installation and sending it over to me?
(In particular, I would like to have access to the binaries -
tex2xindy, xindy.run, xindy.mem etc.)

For some reason, I didn't receive your reply directly - moreover, I
saw your message in the digest email. If you could send me a tarball
direct to james &amp;lt;at&amp;gt; james-pascoe.com, that would be much appreciated.

Thank you again and have a good day,

James

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>James Pascoe</dc:creator>
    <dc:date>2012-08-10T09:22:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/947">
    <title>Re: Building xindy.run and xindy.mem on MAC OS X 10.8(MountainLion)</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/947</link>
    <description>&lt;pre&gt;
Hi,

Does anybody on this list know if current TeX Live (2012, or maybe
last year's version) runs on OS X 10.8? If yes, James' best bet is to
use xindy from there.

James, as the README of xindy-kernel-3.0 tells, you need CLISP to get
it running. xindy.run is actually the CLISP executable, in the 3.0
kernel it's just called as clisp. xindy.mem is created by calling
"make" in the src sub-directory.

That the install instructions in README are concise (or terse,
depending on your view) is by design. xindy's upstream source
distribution does not target end users who want to compile xindy
themselves. It targets distributions like TeX Live who are going to
integrate xindy in their offering. You really need to know what you're
doing when you use this stuff.

An end user who wants to compile xindy himself is probably better off
to use TeX Live's source, available from
svn://tug.org/texlive/trunk/Build/source. There is a README that may
guide you. There, xindy is in util/; you don't need to compile the
whole TeX Li&lt;/pre&gt;</description>
    <dc:creator>Joachim Schrod</dc:creator>
    <dc:date>2012-08-10T08:42:11</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/946">
    <title>Re: Building xindy.run and xindy.mem on MAC OS X 10.8(Mountain Lion)</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/946</link>
    <description>&lt;pre&gt;
On 09.08.2012, at 23:03, James Pascoe &amp;lt;james&amp;lt; at &amp;gt;james-pascoe.com&amp;gt; wrote:


I cannot help with rebuilding, but can only report that xindy runs fine here with MacTeX2012 on OSX 10.8

Simon
--
Simon Spiegel
Steinhaldenstr. 50
8002 Zürich

Telephon: ++41 44 451 5334
Mobophon: ++41 76 459 6039

http://www.simifilm.ch

„It will take time to restore chaos.“ George W. Bush





------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>Simon Spiegel</dc:creator>
    <dc:date>2012-08-10T08:26:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/945">
    <title>Building xindy.run and xindy.mem on MAC OS X 10.8 (MountainLion)</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/945</link>
    <description>&lt;pre&gt;Hi Everybody,

I recently upgraded my Mac Book Pro from OS X 10.7 (Lion) to OS X 10.8 (Mountain Lion). I am using xindy 2.2
and noticed that when I run xindy, I now receive the following message:

/opt/xindy-2.2/bin/../lib/xindy.run: /opt/xindy-2.2/bin/../lib/xindy.run: cannot execute binary file

Would anybody be able to guide me through the process of building xindy.run / xindy.mem from source? I have rebuilt
tex2xindy from the 3.0 sources, but I am not sure how to go about rebuilding xindy.run and xindy.mem. Which package
should I download?

Many thanks for any help you can provide,

James
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
&lt;/pre&gt;</description>
    <dc:creator>James Pascoe</dc:creator>
    <dc:date>2012-08-09T21:03:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/944">
    <title>Re: Support for a new language</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/944</link>
    <description>&lt;pre&gt;2012/6/9 Pierric Sans &amp;lt;pierricsans&amp;lt; at &amp;gt;gmail.com&amp;gt;:
The *.xdy files are computer generated and human unreadable. The
sources for these tables are perl scripts. The TeX distributions
usually do not contain sources of these files, you have to download
the packages including the perl scripts from www.xindy.org. The sort
rules are defined by a simple human readable table. Look at the
structure of a few files and do it the same way.




&lt;/pre&gt;</description>
    <dc:creator>Zdenek Wagner</dc:creator>
    <dc:date>2012-06-10T09:25:46</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/943">
    <title>Support for a new language</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/943</link>
    <description>&lt;pre&gt;Hi everybody,

I am a newbie in Xindy. I am typesetting my PhD thesis in XeLaTeX under
Windows (no possibility to access a Linux computer in my lab), and using
the "glossaries" package. I am trying to make an index on an indigenous
language of Bolivia, for which no support is done, in Xindy.

I have tried to open the "lang" files in my Texlive distribution, trying to
"copy" them for my new language. For instance the
"traditional-utf8-lang.xdy" file contains MANY weird symbols (I cannot find
a way to see it correctly). Same for the "latin1" file.

Could someone help me in creating a new language support ? The language is
(I think) quite simple: it has only "classic" roman letters, with custum
letter groups ("xh", "ty", etc.), and a "special" vowel: the i-bar
(U+0268).

Oh, and by the way, the language name is Chiquitano. It is spoken by 5000
indigenous people in Bolivia.

Thank you very much in advance,

Pierric Sans
------------------------------------------------------------------------------
Live Security &lt;/pre&gt;</description>
    <dc:creator>Pierric Sans</dc:creator>
    <dc:date>2012-06-09T17:12:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/942">
    <title>FW: (te)xindy index references to footnotes</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/942</link>
    <description>&lt;pre&gt;
hi,

(apologies for sending this to the wrong address the first time around!)

i hope there is an obvious answer to this question, but can xindy be made to give references in the form &amp;lt;page&amp;gt;n&amp;lt;footnote number&amp;gt;?  with makeindex, this can be done with something like the following (which seems like a dirty trick):

\newcommand{\nn}{#2n#1}
\newcommand{\fntobeindexed}[1]{#1\index{#1|nn{\thefootnote}}}

but (i think, vaguely) xindy does something different than makeindex and its encapsulating mechanism.  at any rate, it seems to think i want a cross-reference macro because i get a warning in the form of:

WARNING: unknown cross-reference-class `nn'! (ignored)

but § 4.14 of the faq is for the wrong(?) type of 'cross-references'.

any advice/thoughts would be very helpful!

cheers,
jon.


"ubi enim durior pugna, ibi gloriosior inuenitur 'corona'."
              ------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover a&lt;/pre&gt;</description>
    <dc:creator>j robinson</dc:creator>
    <dc:date>2012-06-09T08:33:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/941">
    <title>Re: Cross references as last subitem of an entry</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/941</link>
    <description>&lt;pre&gt;
I've waited 11 days to find the time to try it out, but that doesn't
seem to happen, and next week I'm on the road, too.


Try

(define-location-class-order (("roman-page-numbers"
"arabic-page-numbers")
      ("see"
       "seealso")))

(Note the added parenthesis.) Does this work and make a difference?
Not tested, just from memory, etc., bla bla. You get it. ;-)

Cheers,
Joachim

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Joachim SchrodEmail: jschrod&amp;lt; at &amp;gt;acm.org
xindy maintainerhttp://www.xindy.org/
Roedermark, Germany

------------------------------------------------------------------------------
Virtualization &amp;amp; Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
&lt;/pre&gt;</description>
    <dc:creator>Joachim Schrod</dc:creator>
    <dc:date>2012-02-25T23:03:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/940">
    <title>Cross references as last subitem of an entry</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/940</link>
    <description>&lt;pre&gt;Is there a way of having seealso-cross references as the very last subitem at the end of an index entry?

Currently, I have

(markup-crossref-list :class "seealso" :open "~n\subitem\seealso{" :sep "; " :close "}{}")
(define-location-class-order ("roman-page-numbers"
      "arabic-page-numbers"
      "see"
      "seealso"))

But that puts the cross reference at the top of all possible subitems.

Thanks,
Till
&lt;/pre&gt;</description>
    <dc:creator>Heilmann, Till</dc:creator>
    <dc:date>2012-02-14T18:04:55</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/939">
    <title>Re: ERROR: SLOT-VALUE: The class #&lt;STANDARD-CLASSLOCREF:CROSSREF-LOCATION-REFERENCE&gt; has no slot named BASE:ORDNUMS</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/939</link>
    <description>&lt;pre&gt;Am 03.02.2012 um 03:38 schrieb Joachim Schrod:


Yes (see and seealso).


I don't think it's necessary. I figured it out: I use roman page numbers for the front matter of my book, so I had to add the line

(define-location-class "roman-page-numbers" ("roman-numbers-lowercase") :min-range-length 1)

to my custom module file and now everything runs just fine.


I do specify -L german-duden, I just didn't include it in the sample code.

Thanks for the fantastic program, btw!
Till
&lt;/pre&gt;</description>
    <dc:creator>Heilmann, Till A.</dc:creator>
    <dc:date>2012-02-03T14:00:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/938">
    <title>Re: ERROR: SLOT-VALUE: The class #&lt;STANDARD-CLASS LOCREF:CROSSREF-LOCATION-REFERENCE&gt; has no slot named BASE:ORDNUMS</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/938</link>
    <description>&lt;pre&gt;
I haven't seen this error message yet.

It's about cross references, i.e., \see and friends. It seems as if a
cross reference is used at a point where location references (page
numbers) are supposed to appear. Which would be a bug, I suppose.

Does your raw index use cross references?

Can you make available your raw index or do you need to keep it
private? I could have a look at it, what's going on.

Joachim

PS: You don't specify any language. Do you really want to sort your
index in ASCII order, caseisrt notwithstanding? If you have any
non-alphanumerical characters in your index, the result surely is
incorrect.

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Joachim SchrodEmail: jschrod&amp;lt; at &amp;gt;acm.org
xindy maintainerhttp://www.xindy.org/
Roedermark, Germany

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, Sha&lt;/pre&gt;</description>
    <dc:creator>Joachim Schrod</dc:creator>
    <dc:date>2012-02-03T09:38:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/937">
    <title>ERROR: SLOT-VALUE: The class #&lt;STANDARD-CLASS LOCREF:CROSSREF-LOCATION-REFERENCE&gt; has no slot named BASE:ORDNUMS</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/937</link>
    <description>&lt;pre&gt;CAVEAT: I haven't been able to construct a MWE of my problem so far (quite a complex case) but will keep trying. In the meantime, I'll give it a shot anyway, because someone on this list might be familiar with the error message.

Xindy (MacTeX 2011 release) dies on me like this:

Processing index... [10%] [20%]
ERROR: SLOT-VALUE: The class #&amp;lt;STANDARD-CLASS LOCREF:CROSSREF-LOCATION-REFERENCE&amp;gt; has no slot named BASE:ORDNUMS

… when processing a (Lua)TeX generated index file with the following command:

xindy -I latex -M modules filename.idx

… where modules.xdy is:

(require "latex.xdy")
(require "latex-loc-fmts.xdy")
(require "makeindex.xdy")
(require "german-sty.xdy")
(require "numeric-sort.xdy")
(require "word-order.xdy")
(require "lang/latin/caseisrt.xdy")
(define-location-class "arabic-page-numbers" ("arabic-numbers") :min-range-length 1)

The culprit here is the last line: (define-location-class "arabic-page-numbers" ...
Without it, xindy runs just fine.

Probably some of my \index{} commands (in tur&lt;/pre&gt;</description>
    <dc:creator>Heilmann, Till</dc:creator>
    <dc:date>2012-02-01T23:37:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/936">
    <title>Re: Why I am getting "ERROR: CHAR: index 0 should be less than the length of the string"</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/936</link>
    <description>&lt;pre&gt;Yes, that works but I was wondering why it does not work with grouping.

2011/10/25 Herbert Voss &amp;lt;Herbert.Voss&amp;lt; at &amp;gt;fu-berlin.de&amp;gt;

------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning&amp;lt; at &amp;gt;Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev&lt;/pre&gt;</description>
    <dc:creator>Vafa Khalighi</dc:creator>
    <dc:date>2011-10-24T16:52:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.text.xindy.general/935">
    <title>Re: Why I am getting "ERROR: CHAR: index 0 should be less than the length of the string"</title>
    <link>http://permalink.gmane.org/gmane.comp.text.xindy.general/935</link>
    <description>&lt;pre&gt;Am 24.10.2011 18:26, schrieb Vafa Khalighi:

this works for me:  \index{probability!\prior}

Herbert


------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning&amp;lt; at &amp;gt;Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
________________________________________________________________________
xindy-discuss mailing list -- general xindy announcements and discussions
Unsubscribe via https://lists.sourceforge.net/lists/listinfo/xindy-discuss&lt;/pre&gt;</description>
    <dc:creator>Herbert Voss</dc:creator>
    <dc:date>2011-10-24T16:49:38</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.text.xindy.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.text.xindy.general</link>
  </textinput>
</rdf:RDF>
