xindy-discuss — General mailing list for the xindy index processor (low volume)

[xindy] -I / --input-markup (supported: latex, xelatex, omega, xindy)

[Müller, M. A. <Mar...@oe...>]

Hello,

I am trying to set up a XeLaTeX-Workflow via Github Action. Basically the task is to iterate through tex-files and create PDFs via XeLaTeX.

The workflow can be seen here:
https://github.com/arthur-schnitzler/schnitzler-briefe-tex/blob/main/.github/workflows/leseansicht-letzte-dateien.yml

Everything is working except the indices. As I have several indices I call xindy this way:

for i in L027*.tex; do splitindex -m "texindy -M ../tex-inputs/xindy-pdf" $i;done

This has an unwanted result:
Encountered unexpected char '\' on line 1
7<https://github.com/arthur-schnitzler/schnitzler-briefe-tex/runs/7973653577?check_suite_focus=true#step:7:8>Encountered unexpected char 'i' on line 1
8<https://github.com/arthur-schnitzler/schnitzler-briefe-tex/runs/7973653577?check_suite_focus=true#step:7:9>Encountered unexpected char 'n' on line 1
9<https://github.com/arthur-schnitzler/schnitzler-briefe-tex/runs/7973653577?check_suite_focus=true#step:7:10>Encountered unexpected char 'p' on line 1
10<https://github.com/arthur-schnitzler/schnitzler-briefe-tex/runs/7973653577?check_suite_focus=true#step:7:11>Encountered unexpected char 'u' on line 1
11<https://github.com/arthur-schnitzler/schnitzler-briefe-tex/runs/7973653577?check_suite_focus=true#step:7:12>Encountered unexpected char 't' on line 1
12<https://github.com/arthur-schnitzler/schnitzler-briefe-tex/runs/7973653577?check_suite_focus=true#step:7:13>Encountered unexpected char '{' on line 1

I found the solution to add "-I xindy" online . Even though the manual states the options are "latex, xelatex, omega, xindy" this seems to be outdated and the only working options are "-I / --input-markup   (supported: latex, omega)"

So this error is to expected:

shell: /usr/bin/bash -e {0}
6<https://github.com/arthur-schnitzler/schnitzler-briefe-tex/runs/7973767900?check_suite_focus=true#step:7:7>Unsupported input markup xindy.

neither the option omega nor latex create the desired indices.

Can you be so kind and point me to the right direction?
Thank you!
Martin

[xindy] Bug : xindy.x86_64-linuxmusl is missing

[John Y <joh...@ou...>]

Hello,

As explained here (https://github.com/xu-cheng/latex-action/issues/32), we find out that TeXLive does not offer xindy binaries for Linux musl environment (the missing package is thus xindy.x86_64-linuxmusl).

Can you fix it ?

Thanks for the help

[xindy] Fix xindy dataloss with hyperref (\hyperindexformat)

[Jürgen S. <sp...@ly...>]

Hi!

I suggest the following addition to makeindex.xdy:


--- /usr/local/texlive/current/texmf-
dist/xindy/modules/base/makeindex.xdy
+++ /tmp/meld-tmpa44n5mo1
@@ -9,6 +9,9 @@
 ;; \see takes two parameters, the second one is for the page number.
 ;; We don't emit one in xindy, so we add an empty second argument.
 (markup-crossref-list :class "see" :open "\see{" :sep "; " :close
"}{}")
+
+(define-crossref-class "hyperindexformat" :unverified)
+(markup-crossref-list :class "hyperindexformat" :open
"\hyperindexformat{" :sep "; " :close "}{}")
 
 ;; FIXME: This does not work properly. This should be for entries that
 ;; have both a locref (e.g., the page number) and a cross reference.


This does not link the \see[also] entries with their targets, but at
least it prints them, fixing the current (long-known) dataloss there is
with xindy, \see[also] and hyperref.

Regards
Jürgen

[xindy] [bug] clisp startup issues

[Ralph S. <ra...@mu...>]

Hi,

xindy's clisp kernel fails to start with my personal ~/.clisprc file.

     $ touch demo.idx
     $ texindy demo.idx
     *** - Can't reliably convert wild pathname
           #P"/home/ralph/lib/lisp/FOLDER NAME WITH SPACE CHARACTERS/"

#P"/home/ralph/lib/lisp/FOLDER NAME WITH SPACE CHARACTERS/" is pulled in
via (asdf:initialize-source-registry).

Retry without ~/.clisprc:

     $ mv ~/.clisprc ~/.clisprc-
     $ texindy demo.idx
     [...]
     Markup written into file "./demo.ind".

I propose to add ‘-norc’ when calling ‘xindy.run’, i.e.

     my @command = ("$lib_dir/xindy.run", '-q', '-norc',
                    '-B', $lib_dir, '-M', $mem_file, '-E', 'iso-8859-1');

This should fix the above bug.  Thank you.

     $ xindy --version
     xindy release: 2.5.1
     xindy script version: 1.18
     xindy kernel version: 3.0
     CLISP version 2.49.92 (2018-02-18) (built on bulldog [127.0.0.1]) architecture: X86_64
     $ type -path xindy
     /usr/local/texlive/2018/bin/x86_64-linux/xindy

-- 
Ralph

Re: [xindy] Kurdish Language support in Xindy

[Zdenek W. <zde...@gm...>]

Yes, it should be simple. Just a small question, is وو considered as a
single letter similarly as CH in some European languages? does it mean that
وو should appear after وی although ی is after و if it is not part of this
group?

Zdeněk Wagner
http://ttsm.icpf.cas.cz/team/wagner.shtml
http://icebearsoft.euweb.cz

2018-08-10 2:25 GMT+02:00 Vafa Khalighi <vk...@uo...>:

>
>
> It is simple; it needs a slight modification to my xindy script files
> which can be found on ctan under the package xindy-Persian.
>
> ________________________________
> From: Asad Abuzed <abo...@gm...>
> Sent: Friday, August 10, 2018 1:48:55 AM
> To: Jörg Sommer; xin...@li...
> Subject: [xindy] Kurdish Language support in Xindy
>
> Dear Sir/Madam,
>
> I want to know how to add Xindy support for Kurdish language as it is
> similar but a little more than Persian alphabets.
> Is it possible to add this to Xindy?
>
> This is the Kurdish alphabet in order but the last one need to be with
> first one.
>
> Best regards
>
> [cid:4DE30469-DB7D-47F2-92EC-FB816A0D6D54]
>
> On 9 Aug 2018, at 18:44, Jörg Sommer <jo...@al...<mailto:joe
> rg...@al...>> wrote:
>
> Hi,
>
> did you send a message to the xindy mailinglist
> xin...@li...<mailto:xindy-
> di...@li...>? Please, resend the message. It got
> lost before delivery to the list members.
>
> Thanks
>
> Jörg
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ________________________________________________________________________
> xindy-discuss mailing list -- general xindy announcements and discussions
> Unsubscribe via https://lists.sourceforge.net/lists/listinfo/xindy-discuss
>

Re: [xindy] Kurdish Language support in Xindy

[Vafa K. <vk...@uo...>]

It is simple; it needs a slight modification to my xindy script files which can be found on ctan under the package xindy-Persian.

________________________________
From: Asad Abuzed <abo...@gm...>
Sent: Friday, August 10, 2018 1:48:55 AM
To: Jörg Sommer; xin...@li...
Subject: [xindy] Kurdish Language support in Xindy

Dear Sir/Madam,

I want to know how to add Xindy support for Kurdish language as it is similar but a little more than Persian alphabets.
Is it possible to add this to Xindy?

This is the Kurdish alphabet in order but the last one need to be with first one.

Best regards

[cid:4DE30469-DB7D-47F2-92EC-FB816A0D6D54]

On 9 Aug 2018, at 18:44, Jörg Sommer <jo...@al...<mailto:jo...@al...>> wrote:

Hi,

did you send a message to the xindy mailinglist
xin...@li...<mailto:xin...@li...>? Please, resend the message. It got
lost before delivery to the list members.

Thanks

Jörg

[xindy] Kurdish Language support in Xindy

[Asad A. <abo...@gm...>]

Dear Sir/Madam,

I want to know how to add Xindy support for Kurdish language as it is similar but a little more than Persian alphabets.
Is it possible to add this to Xindy?

This is the Kurdish alphabet in order but the last one need to be with first one.

Best regards



> On 9 Aug 2018, at 18:44, Jörg Sommer <jo...@al...> wrote:
> 
> Hi,
> 
> did you send a message to the xindy mailinglist
> xin...@li...? Please, resend the message. It got
> lost before delivery to the list members.
> 
> Thanks
> 
> Jörg

[xindy] How to suppress 'Cross-reference-target (“entry”) does not exist' error for entries without locators

[Kevin G. <go...@gm...>]

Hello.

I would like to know if there's a way to suppress the
'Cross-reference-target ("entry") does not exist' error for entries without
locators.

First, consider the following index entry:

    \index{entry|see{non-existent entry}}

When xindy builds the index, it will complain about the dangling
cross-reference:

    ERROR: Cross-reference-target ("non-existent entry") does not exist!

We can instruct xindy not to validate the 'see' and 'seealso'
cross-references by adding the following to a custom .xdy module:

    (define-crossref-class "see" :unverified)
    (define-crossref-class "seealso" :unverified)

and passing the name of that module to xindy using the -M parameter.

I like having xindy validate my cross-references so I don't have dangling
pointers in my index. Unfortunately, it gives me false errors in the
following case:

    \index{entry!subentry}
    \index{another entry|see{entry}}

xindy complains:

    ERROR: Cross-reference-target ("entry") does not exist!

I assume this is because 'entry' has no locators (page numbers) itself and
only has subentries.

How can I get xindy to mark cross-references to such locatorless entries as
valid?

(If you'd like to earn fake Internet points for answering this question,
I've also posted it at <https://tex.stackexchange.com/q/424722/80>.)

Thanks for your help!

—Kevin Godby

[xindy] Can one define a general numbering system in xindy?

[Vafa K. <vk...@uo...>]

Hi List


In the source of xindy (common Lisp), few numbering systems like roman, arabic, etc are defined. One may need numbering systems that are not provided by xindy. For instance, the package zahl2string[1] provides ordinal strings but xindy does not understand this or other similar numbering systems which are not defined by xindy. One can define a new alphabet or location class as explained in xindy advanced tutorial[2] but if the range of the numbers is big, then it is out of luck.


Is there a programmatic way to define a new numbering system in xindy? Can one program such a numbering system using Common Lisp?


If it is not possible to do this, then I guess it is a good feature to add since this kind of numbering exists in most languages.



Yours sincerely,

  Vafa Khalighi





[1] https://ctan.org/pkg/zahl2string

[2] http://www.xindy.org/doc/tutorial-3.html

[xindy] latex /usr/bin/tex2xindy: No such file or directory

[luteva <lu...@fr...>]

Hi,

I have a problem which seemed to be similar to a bug report but, still
does not work and I am not sure if the issue is relevant to xindy or what.

So, I run in a tex file (latex)

\makeindex[program=texindy,options= -C utf8 -M texindy -L french]

or even directly in the command shell :
texindy  -I latex -C utf8 --language french fichier.idx

and the result is ....

sh: /usr/bin/tex2xindy: No such file or directory
/usr/lib64/clisp-2.49+/base/lisp.run: initialization file
`/usr/bin/xindy.mem' was not created by this version of CLISP runtime

Any Idea of what shall I do with this ? Thanks.

-- 
--------------------------------------
magnetic.aboulafia 
Fedora FC26 x86_64 GNU/Linux

[xindy] How to implement custom letter groups (in use with TeX)?

[Tobi W. <ma...@to...>]

Dear xindy users and developers,


At the moment I’m trying to use xindy to set up an index of books/passages from the bible, where the main sorting layer should be the book (Gen, Ex, …) and not the normal alphabet. I already postet on TeX.SX which you may like to take a look at for the details: http://tex.stackexchange.com/q/356285/4918.
You may answer over on TeX.SX or here and I make up an answer on TeX.SY myself showing the solution (if there is one).

Although my current application for this is bible books, but I’d be happy with the general answer on how to implement custom letter groups. Simply following the windy manual didn’t work for me.


Any help is appreciated :-)
Best regards,
Tobi

—

Tobi W_


Tobias Weh
Spindelstraße 25
49080 Osnabrück

+49 541 40757837

ma...@to...
http://tobiw.de

Re: [xindy] Problems with merge-rule

[Joachim S. <js...@ac...>]

Simon Spiegel writes:
> 
> > When entries are merged, the first index key is always used as the
> > printed representation. One cannot change that.
> > 
> > In 2012, there were some discussions how one could change that, but no
> > solution was settled or realized. 
> > https://sourceforge.net/p/xindy/feature-requests/42/
> 
> So is there a reason not to implement the suggested „print-rule“ 
> functionality (except lack of time).

For sure, lack of time is the most important issue. But, I'm unsure if
print-rules are really the right way to model the problem.

The current model of merge-rules is already a failure: Your usage is
the intended one, as is normalization of markup (that's what I
intended it to be). But many usages of merge-rules are actually means
to create sort order -- and they only work due to no conflicting data.

I'm afraid to introduce a similar incorrect model in the system. The
relationship of merge rules, sort rules, and potential print rules are
still not well established, there's need for discussion. Thus, I'm
reluctant to change the system in such a fundamental way at some idea
that never received any serious review.

Cheers,
	Joachim

PS: For me, the currently most important problem is a completely
different issue: xindy is based on CLISP which is not supported
anymore since several years. I/we need to move it to another base
framework. The implementation is inherently tied to Common Lisp's
notion of general functions, class-independent methods and multiple
dispatch. (E.g., markup generation specialices on several dimensions,
represented by argument classes or even objects.) Thus, changing to a
more mainstream-line programming language like Lua or Python won't
work. I'm evaluating what open source CL framework could be used.

PPS: I miss the time we worked at University (where we created xindy),
when we could use the daily coffee break to discuss such issues and
resolve them as a team,

Re: [xindy] Problems with merge-rule

[Simon S. <si...@si...>]

>> 
>> What I want to achieve is that the two entries 〓Morus, Thomas‘ and
>> 〓More, Thomas‘  are both sorted under 〓Morus, Thomas‘. In the MWE
>> the are alphabetically sorted correctly – the entry appears after
>> 〓Mort‘ – but what is displayed is 〓More, Thomas‘. This seems to
>> depend entirely on which index entry appears first in the document.
>> If change the order and have \index{Morus, Thomas} first, everything
>> is as it should be. How can I make it, that the 〓Morus, Thomas‘ is
>> printed in the index, regardless of the order of appearance? 
> 
> When entries are merged, the first index key is always used as the
> printed representation. One cannot change that.
> 
> In 2012, there were some discussions how one could change that, but no
> solution was settled or realized. 
> https://sourceforge.net/p/xindy/feature-requests/42/

So is there a reason not to implement the suggested „print-rule“ functionality (except lack of time).

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

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


http://www.simifilm.ch
http://www.utopia2016.ch

„Selbst in der Sphäre der Makkaroni, Zwetschgen und Kaffeebohnen gibt es umwälzende Ideen und siegreichen Durchbruch des Jungen.“ Gottlieb Duttweiler

Re: [xindy] Package Maintainer

[Joachim S. <js...@ac...>]

Hello,

> Do you have a time frame where you expect to start testing the LISP system?
> Or whereever testing input paths would be a thing? (But I am guessing at
> the end of the dev cycle?)

In February, I'm on holidays, for an extended stay in New Zealand. I
hope that I'll find the time to work on xindy in that month.

Cheers,
	Joachim

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Joachim Schrod, xindy maintainer. Roedermark, Germany
Email: js...@ac..., http://www.xindy.org/

Re: [xindy] Problems with merge-rule

[Joachim S. <js...@ac...>]

Simon,

> I have some trouble with merge-rules. It’s probably just me not
> understanding something properly, but help is appreciated.

You're hitting a limit of xindy.

> Consider the following MWE:
> 
> \RequirePackage{filecontents}
> \documentclass{article}
> \usepackage{imakeidx}
> \begin{filecontents*}{test.xdy}
> (merge-rule "More, Thomas" "Morus, Thomas" :again )
> (merge-rule "… (.*)" "\1" :again)
> \end{filecontents*}
> \def\xindyopt{-d level=3 -t xindyxindy.log -C utf8 -M test -M texindy}
> \makeindex[program=truexindy,options=\xindyopt]
> \usepackage{fontspec}
> \setmainfont{TeX Gyre Pagella}
> \begin{document}
> Test
> \index{Mort}
> \index{More, Thomas}
> \newpage
> New Test
> \index{Morus, Thomas}
> \printindex
> \end{document}
> 
> What I want to achieve is that the two entries 〓Morus, Thomas‘ and
> 〓More, Thomas‘  are both sorted under 〓Morus, Thomas‘. In the MWE
> the are alphabetically sorted correctly – the entry appears after
> 〓Mort‘ – but what is displayed is 〓More, Thomas‘. This seems to
> depend entirely on which index entry appears first in the document.
> If change the order and have \index{Morus, Thomas} first, everything
> is as it should be. How can I make it, that the 〓Morus, Thomas‘ is
> printed in the index, regardless of the order of appearance? 

When entries are merged, the first index key is always used as the
printed representation. One cannot change that.

In 2012, there were some discussions how one could change that, but no
solution was settled or realized. 
https://sourceforge.net/p/xindy/feature-requests/42/

Sorry that I cannot be of more help.

	Joachim

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Joachim Schrod, xindy maintainer. Roedermark, Germany
Email: js...@ac..., http://www.xindy.org/

Re: [xindy] Package Maintainer

[Ντέντος Σ. <st...@gm...>]

Okay, sure!
Do you have a time frame where you expect to start testing the LISP system?
Or whereever testing input paths would be a thing? (But I am guessing at
the end of the dev cycle?)

Ντέντος Σταύρος

On 16 January 2017 at 04:30, Joachim Schrod <js...@ac...> wrote:

>
> Hello,
>
> Yes, xindy is still maintained, by me.
>
> But, sorry to say, the cited bug is not on any of my high-priority
> lists. It's a bug caused by an issue in our basic LISP implementation
> system -- and that system is not maintained any more. Thus, my
> high-priority issue is the replacement of CLISP by another system.
> That's tracked by https://sourceforge.net/p/xindy/feature-requests/46/.
>
> It might be that this will solve your problem -- but frankly, I won't
> test for your specific problem. If you linger on this mailing list,
> I'll post any updates on that project and you can check yourself.
>
> Sorry that I can't give you more help.
>
> Cheers,
>         Joachim
>
>
> Ντέντος Σταύρος writes:
> > Hello to everyone,
> >
> > Is xindy still maintained? I was looking for the maintainer of the Xindy
> > project, since I was
> > using it successfully for the most part
> > Unfortunately, I am mainly working on Greek Windows, and I am
> > suffering from this bug https://sourceforge.net/p/xindy/bugs/56/)
> > aswell (Greek characters in the path).
> >
> > My current workaround is to use makeindex temporarily, and maybe at
> > the end move the folder structure somewhere shallower and use xindy.
> > But I thought it could worth the trouble to find the maintainer.
> >
> > Thank you for your time :)
> >
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Joachim Schrod, xindy maintainer. Roedermark, Germany
> Email: js...@ac..., http://www.xindy.org/
>
> ------------------------------------------------------------
> ------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> ________________________________________________________________________
> xindy-discuss mailing list -- general xindy announcements and discussions
> Unsubscribe via https://lists.sourceforge.net/lists/listinfo/xindy-discuss

[xindy] Problems with merge-rule

[Simon S. <si...@si...>]

Hi,

I have some trouble with merge-rules. It’s probably just me not understanding something properly, but help is appreciated.

Consider the following MWE:

\RequirePackage{filecontents}
\documentclass{article}
\usepackage{imakeidx}
\begin{filecontents*}{test.xdy}
(merge-rule "More, Thomas" "Morus, Thomas" :again )
(merge-rule "… (.*)" "\1" :again)
\end{filecontents*}
\def\xindyopt{-d level=3 -t xindyxindy.log -C utf8 -M test -M texindy}
\makeindex[program=truexindy,options=\xindyopt]
\usepackage{fontspec}
\setmainfont{TeX Gyre Pagella}
\begin{document}
Test
\index{Mort}
\index{More, Thomas}
\newpage
New Test
\index{Morus, Thomas}
\printindex
\end{document}

What I want to achieve is that the two entries ‚Morus, Thomas‘ and ‚More, Thomas‘  are both sorted under ‚Morus, Thomas‘. In the MWE the are alphabetically sorted correctly – the entry appears after ‚Mort‘ – but what is displayed is ‚More, Thomas‘. This seems to depend entirely on which index entry appears first in the document. If change the order and have \index{Morus, Thomas} first, everything is as it should be. How can I make it, that the ‚Morus, Thomas‘ is printed in the index, regardless of the order of appearance?

Thanks

Simon


--
Simon Spiegel
Steinhaldenstr. 50
8002 Zürich

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


http://www.simifilm.ch
http://www.utopia2016.ch

„Yesterday is history. Tomorrow is a mystery. Today is a gift. That is why they call it the present.“

Re: [xindy] Package Maintainer

[Joachim S. <js...@ac...>]

Hello,

Yes, xindy is still maintained, by me.

But, sorry to say, the cited bug is not on any of my high-priority
lists. It's a bug caused by an issue in our basic LISP implementation
system -- and that system is not maintained any more. Thus, my
high-priority issue is the replacement of CLISP by another system. 
That's tracked by https://sourceforge.net/p/xindy/feature-requests/46/.

It might be that this will solve your problem -- but frankly, I won't
test for your specific problem. If you linger on this mailing list,
I'll post any updates on that project and you can check yourself. 

Sorry that I can't give you more help.

Cheers,
	Joachim


Ντέντος Σταύρος writes:
> Hello to everyone,
> 
> Is xindy still maintained? I was looking for the maintainer of the Xindy
> project, since I was
> using it successfully for the most part
> Unfortunately, I am mainly working on Greek Windows, and I am
> suffering from this bug https://sourceforge.net/p/xindy/bugs/56/)
> aswell (Greek characters in the path).
> 
> My current workaround is to use makeindex temporarily, and maybe at
> the end move the folder structure somewhere shallower and use xindy.
> But I thought it could worth the trouble to find the maintainer.
> 
> Thank you for your time :)
> 

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Joachim Schrod, xindy maintainer. Roedermark, Germany
Email: js...@ac..., http://www.xindy.org/

[xindy] Package Maintainer

[Ντέντος Σ. <st...@gm...>]

Hello to everyone,

Is xindy still maintained? I was looking for the maintainer of the Xindy
project, since I was
using it successfully for the most part
Unfortunately, I am mainly working on Greek Windows, and I am
suffering from this bug https://sourceforge.net/p/xindy/bugs/56/)
aswell (Greek characters in the path).

My current workaround is to use makeindex temporarily, and maybe at
the end move the folder structure somewhere shallower and use xindy.
But I thought it could worth the trouble to find the maintainer.

Thank you for your time :)

Ντέντος Σταύρος

Re: [xindy] xindy rule to remove an entry completely

[Simon S. <si...@si...>]

> On 20 Dec 2016, at 16:13, Zdenek Wagner <zde...@gm...> wrote:
> 
> 2016-12-20 14:46 GMT+01:00 Simon Spiegel <si...@si...>:
> 
> > On 20 Dec 2016, at 13:11, Florian Grammel <Gr...@gm...> wrote:
> >
> > I usually use some simple sed-commands for this kind of post-processing.
> > They can either be put into a little script together with the xindy-call or you can get many editors to call them whenever the file is typeset; e.g. using TeXShop you can put them in the engine-files.
> 
> I have never used sed. Could you give a simple example of a sed call which would eliminate an entry?
> 
> You can use any scripting language you know, lua, perl, awk, python, ruby, … 

A short followup on this. Someone on tex.stackexchange.com came up with the following pure xindy solution which seems to work nicely

\RequirePackage{filecontents}
\begin{filecontents*}{DontIndex.xdy}
(require "texindy.xdy")
(define-letter-group "DontIndex" :prefixes ("~b") :before "default")
(merge-rule "^Test$" "~b") ;$
(merge-rule "^XYZ$" "~b") ;$
(markup-letter-group  :group "DontIndex" :open "\def\DontShowMe#1{}\DontShowMe{" :close "}")
\end{filecontents*}
\documentclass{article}
\usepackage[xindy]{imakeidx}
\def\xindyopt{-M DontIndex -L german-din}
\makeindex[program=truexindy,options=\xindyopt]
\begin{document}
Disappear 
\index{Test} \index{XYZ}
More 
\index{abc}\\
Still more 
\index{xyz}
\index{=}
\\
And now testing 
\index{Testing}
\printindex
\end{document}

Thank to all who chimed in.

Simon

--
Simon Spiegel
Steinhaldenstr. 50
8002 Zürich

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


http://www.simifilm.ch
http://www.utopia2016.ch

„The first rule of Tautology Club is the first rule of Tautology Club.“

Re: [xindy] xindy rule to remove an entry completely

[Zdenek W. <zde...@gm...>]

2016-12-20 14:46 GMT+01:00 Simon Spiegel <si...@si...>:

>
> > On 20 Dec 2016, at 13:11, Florian Grammel <Gr...@gm...> wrote:
> >
> > I usually use some simple sed-commands for this kind of post-processing.
> > They can either be put into a little script together with the xindy-call
> or you can get many editors to call them whenever the file is typeset; e.g.
> using TeXShop you can put them in the engine-files.
>
> I have never used sed. Could you give a simple example of a sed call which
> would eliminate an entry?
>

You can use any scripting language you know, lua, perl, awk, python, ruby,
...

>
> Best,
>
> Simon
>
>
> Zdeněk Wagner
> http://ttsm.icpf.cas.cz/team/wagner.shtml
> http://icebearsoft.euweb.cz
>
>
> --
> Simon Spiegel
> Steinhaldenstr. 50
> 8002 Zürich
>
> Telephon: ++41 44 451 5334
> Mobophon: ++41 76 459 6039
>
>
> http://www.simifilm.ch
> http://www.utopia2016.ch
>
> „Etwas ist immer.“ Kurt Tucholsky
>
>
>
> ------------------------------------------------------------
> ------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/intel
> ________________________________________________________________________
> xindy-discuss mailing list -- general xindy announcements and discussions
> Unsubscribe via https://lists.sourceforge.net/lists/listinfo/xindy-discuss
>

Re: [xindy] xindy rule to remove an entry completely

[Simon S. <si...@si...>]

> On 20 Dec 2016, at 13:11, Florian Grammel <Gr...@gm...> wrote:
> 
> I usually use some simple sed-commands for this kind of post-processing.
> They can either be put into a little script together with the xindy-call or you can get many editors to call them whenever the file is typeset; e.g. using TeXShop you can put them in the engine-files.

I have never used sed. Could you give a simple example of a sed call which would eliminate an entry?

Best,

Simon

--
Simon Spiegel
Steinhaldenstr. 50
8002 Zürich

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


http://www.simifilm.ch
http://www.utopia2016.ch

„Etwas ist immer.“ Kurt Tucholsky
 

Re: [xindy] xindy rule to remove an entry completely

[Florian G. <Gr...@gm...>]

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>I usually use&nbsp;some simple sed-commands for this kind of post-processing.</div>

<div>They can either be put into a little script together with the xindy-call or you can get many editors to call them whenever the file is typeset; e.g. using TeXShop you can put them in the engine-files.</div>

<div>&nbsp;</div>

<div>But if there is a pure xindy-solution, I&#39;d&nbsp;love to learn it, too.</div>

<div>&nbsp;</div>

<div>Best,</div>

<div>Florian.</div>

<div>&nbsp;</div>

<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div name="quoted-content">Hi,<br/>
<br/>
is it possible to create a rule which prevents an entry from appearing in the index? For example, if I have something like &#92;index{unknown} that &bdquo;unknown&ldquo; does not appear in the index?<br/>
<br/>
TIA<br/>
<br/>
Simon<br/>
&nbsp;</div>
</div>
</div></div></body></html>

[xindy] xindy rule to remove an entry completely

[Simon S. <si...@si...>]

Hi,

is it possible to create a rule which prevents an entry from appearing in the index? For example, if I have something like \index{unknown} that „unknown“ does not appear in the index?

TIA

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

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

http://www.simifilm.ch
http://www.utopia2016.ch

„If there's one thing I've learned, it's that life is one crushing defeat after another until you just wish Flanders was dead.“ Homer Simpson

[xindy] custom sorting not working any more with 2.5.1 (TL16)

[Florian G. <Gr...@gm...>]

I have several home-spun sorting schemes built after the following principle:


-------------------------------------
(require "latex.xdy")
(require "makeindex.xdy")
(require "numeric-sort.xdy");; "V64" appears before "V128".
(require "latex-loc-fmts.xdy")


(require "ff-ranges.xdy")
;;(require "book-order.xdy")



;; minimal alphabet
(define-alphabet "myminimal"
    ("Start with C though" "Letter A" "Letter B" "Test Unicode ð"))



;; minimal letters
(sort-rule "A" "Letter A")
(sort-rule "B" "Letter B")
(sort-rule "C" "Start with C though")
(sort-rule "Ð" "Test Unicode ð")


    
(define-location-class "myminimal"
    ("myminimal" :sep " " "arabic-numbers" :sep "," "arabic-numbers"))


(define-letter-groups
  ("Start with C though" "Letter A" "Letter B" "Test Unicode ð"))




(markup-letter-group :open-head "~n {\bf " :close-head "}
"
                     )
-------------------------------------


Using this to sort an idx-file like


-------------------------------------
\indexentry{Ant}{2}
\indexentry{Bison}{2}
\indexentry{Camel}{2}
\indexentry{Unicorn}{2}
\indexentry{Ðuck}{2}
-------------------------------------

with 
xindy -o index.ind -C utf8 -M test.xdy -M m.idx

has always given me (and still does when calling TL2014's version 2.5.0):


-------------------------------------
{\bf default}

  \item Unicorn, 2

  \indexspace

 {\bf Start with C though}

  \item Camel, 2

  \indexspace

 {\bf Letter A}

  \item Ant, 2

  \indexspace

 {\bf Letter B}

  \item Bison, 2

  \indexspace

 {\bf Test Unicode ð}

  \item Ðuck, 2
-------------------------------------


which is precisely what I need.
But with 2.5.1 as in TL2016 the standard alphabet sort of overrules my sorting:


-------------------------------------
 {\bf A}

  \item Ant, 2

  \indexspace

 {\bf B}

  \item Bison, 2

  \indexspace

 {\bf C}

  \item Camel, 2

  \indexspace

 {\bf U}

  \item Unicorn, 2

  \indexspace

 {\bf Test Unicode ð}

  \item Ðuck, 2
-------------------------------------



Is there a way to get back to the earlier behaviour?
Or how could I change my module-file to achieve the old behaviour with up-to-date xindy?

I assume this might be a feature, not a bug. But I haven't been able to find a comprehensive Change Log anywhere to make sure.


Thanks in advance!
Florian.
 

____________________________________________

Florian Grammel

Copenhagen, Denmark