I like the doc version which omits the oldnomencl stuff. But I observed one
single problem: You are invoking makeindex for nomencl after checking the
the files with extensions .nlo OR .glo exists.. However, .glo extension is
also used by glotex. Therefore, if the user is as adventurous as to use
glotex in the lyx file, then we force lyx to use nomencl.sty for glotex
generated index.

Indeed, it is a very rare chance to use glotex package instead of/together
with the nomencl, since glotex does not provide any significant feature over
nomencl.

I have no direct solution for the moment,

ugras


On 4/22/07, Georg Baum <[EMAIL PROTECTED] > wrote:

Am Freitag, 20. April 2007 11:59 schrieb Ozgur Ugras BARAN:
> If you have a solution, go ahead, since I haven't got one but got an
idea
> only :). I just try to act responsible  :)

Good guy :-)

Here are my solutions: config.diff follows the idea suggested by
Jean-Marc:
Test for the nomencl version in chkconfig.ltx and put either "nomencl"
or "nomencl" and "oldnomencl" to the packages.list file. Then the
availability of "oldnomencl" is tested to determine the version, define
the needed commands in the preamble and use the correct invocations of
makeindex.
The advantage of this solution is that there are no checks in the
document.
The disadvantage is that you need to reconfigure if the nomencl version
changes.

The other version in doc.diff was almost finished before Jean-Marc made
his
suggestion, so I finished it and present it here, too. It moves the check
for the version into the document preamble, and simply checks for the
presence of the .glo file to decide whether makeindex should be run for
the old version.
The advantage of this solution is that the exported .tex file works with
both versions. A possible disadvantage is that makeindex could produce
errors if you use another glossary package that produces a .glo file (did
not test that).

Which solution should go in? Note that I did not handle the case when
nomencl is not installed, and I don't intend to do that.


Georg


Reply via email to