Hi Jean-Marc and Hi everybody..
Well, I am almost back. In less than a month I will be back for coding..
(Waiting for you all to finish debugging for lyx-1.5 so I can enjoy
developing new features.. ;-) ).
Now, about glossaries:
First of all, nomencl can be used as glossary, although it is intended
primarily for notation list. My primary choice of naming was keeping it as
Notations, instead of glossary, thinking that in the future I (or
somebodyelse ) can add support for another glossary package. However, this
was discussed in the list and decided the naming is changed to glossary.
If you are asking that why we used nomencl in the first place for glossary
support, here is the answer (well, not an answer but an explanation why I
did so) : In the time I was implementing the nomencl support there were a
couple of alternatives about glossaries/notations. The main reason why I
choose the nomencl was various:
- I have already used nomencl with lyx in my thesis. Then I had a
experience, and seemed to me it will be a quick hack (though I could not
guess I will re-write inset code :) )
- nomencl seem to be the most available package among the other
glossary packages in Linux. For example in my ubuntu there is only nomencl
as a standard glossary package. In Suse 10, the situation was similar.
- There was a wishlist item in bugzilla on nomencl, but not on the
others..
- I go learn every other glossary package, first.. here are my humble
opinions:
- glosstex: It is no more than nomencl + acronym.. I thought I
don't need to complicate things. One can write acronym package
seperately.
Also this package is not available in many standard distros.
- glotex is a good option for automated glossary database, but
makeglos was way better in terms of applicability to lyx
- makeglos: this package is quite new and its documentation is
rather weak. I didn't see any significant advantage of this
package, then I
skipped.
- gloss: This package is very good, but uses bibtex instead of
makeindex. bibtex part of the lyx is something I know much less
than index
part (where in the index case I had to go play with the
latex.Conly). Ifwe need to consider multiple indices, we need to
choose between
gloss and glossary.
- glossary: I regret not to implement this package. But it was a
bit too early to give the support for multiple glossaries before multiple
indices. Moreover, the package was quite new (2006) and is not standard,
yet. I should add that, glossary package has much more options
compared to
glossary that users will ask support for. This package is in my
implementation list, of course if everybody will be agree with me.
Well, I guess that was enough about history..
regards,
Ugras
On 4/12/07, Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
Is it really normal that, when one asks for a glossary (list of
words), LyX uses nomencl.sty for a nomenclature (list of symbols)?
This seems very fishy to me. A document may want to have both a
glossary and a nomenclature.
JMarc
