On 10/6/06, Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
>>>>> "Ozgur" == Ozgur Ugras BARAN <[EMAIL PROTECTED]> writes:>> What do you have in mind? Ozgur> well... multiple indices.. :) Like in ${x_i}_j$, for example? ;) Ozgur> I plan to support splitidx, since it runs once on the file. So, Ozgur> it is easier to handle. For example, I will not have to control Ozgur> the number of indices, since the file write handle of Latex is Ozgur> limited. I assume you have seen this page: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multind
yes, I have..
What is wrong with multind.sty?
nothing.. It just seems to me it is no fancier than index.sty.. it also requires multiple makeindex runs, so I didn't see any advantage over index.sty. We can still support it anyhow, but this will increase confusion.
Ozgur> However, splitidx is not available in every distro (for example Ozgur> my suse doesn't have it). My teTeX2 does not either. Ozgur> supporting both packages brings new difficulties in terms of Ozgur> consistency, though... Ozgur> Oh, I will also keep support for ordinary index package. The FAQ also says that memoir has its own implmentation. It might be worth looking at.
why not?? But as far as I can see, memoir implementation is not that compatible with the other three. Another point is, It is better develop a more general multiple indexing mechanism that supports all classes. So, let's keep it general for the moment, and add memoir multi index support in the future..
Ozgur> - I assume you have some idea on how to implement this feature, Ozgur> in terms of user interface etc. If you share your vision about Ozgur> multiple indices, then both of us will be happy with the Ozgur> result. No. But Juergen has probably more to say on the subject.
this message was a reply to Juergen. I just wanted to quote your message.. :)
Ozgur> - I have limited time. I mean in two months, I will probably Ozgur> disappear for six months. therefore I need somebody to maintain Ozgur> the code when I am away. I am sure that I will finish a working Ozgur> and clean version before I leave, but I cannot guarantee things Ozgur> will work in every frontend. If it works and is correctly documented, that should not be a big problem.
Sure.. Otherwise I won't submit.
JMarc
