Since some time (unfortunately not documented when), nomencl uses the
rather odd % escape character (instead of " due to its activation by
babel etc.), but we haven't adapted it fully yet.
The attached patch does that.
Master uses the right escape char with its new approach.
OK?
--
J
On 7/22/24 3:56 AM, Jürgen Spitzmüller wrote:
Am Montag, dem 22.07.2024 um 07:53 + schrieb Juergen Spitzmueller:
commit 5bc4c11fd601773a7ffba850524afa03eafe13f9
Author: Juergen Spitzmueller
Date: Mon Jul 22 09:51:54 2024 +0200
tex2lyx: Fix two bugs in nomencl import
Am Montag, dem 22.07.2024 um 07:53 + schrieb Juergen Spitzmueller:
> commit 5bc4c11fd601773a7ffba850524afa03eafe13f9
> Author: Juergen Spitzmueller
> Date: Mon Jul 22 09:51:54 2024 +0200
>
> tex2lyx: Fix two bugs in nomencl import
>
> * The comment chara
Am Donnerstag, den 28.12.2017, 14:20 -0500 schrieb Richard Heck:
> Can you try the attached? Looks like I was over-enthusiastic about
> aborting.
Yes, this works.
Thanks
Jürgen
> rh
>
signature.asc
Description: This is a digitally signed message part
On 12/27/2017 09:34 AM, Jürgen Spitzmüller wrote:
> Am Freitag, den 22.12.2017, 00:58 +0100 schrieb Richard Heck:
>> commit b5e5c2576a8ed83faa52d0a35bb15dc54a8b1a91
>> Author: Richard Heck
>> Date: Thu Dec 21 18:46:06 2017 -0500
>>
>> Allow makeindex, nomenc
Am Freitag, den 22.12.2017, 00:58 +0100 schrieb Richard Heck:
> commit b5e5c2576a8ed83faa52d0a35bb15dc54a8b1a91
> Author: Richard Heck
> Date: Thu Dec 21 18:46:06 2017 -0500
>
> Allow makeindex, nomencl, and bibtex runs to be canceled, too.
As of this commit, BibTeX error
am Sonntag, 26. August 2007 12:29 schrieb Jürgen Spitzmüller:
> > i was especially interested in the new glossary feature, and basicly it's
> > just what i was wishing for. but then again, i can't figure out how to
> > pass options to the nomencl package; it seems
m.eik michalke wrote:
> i was especially interested in the new glossary feature, and basicly it's
> just what i was wishing for. but then again, i can't figure out how to pass
> options to the nomencl package; it seems it's loaded without options
> hardcoded (src/LaTeXFe
hi,
i'm testing the 1.5.x version of LyX (compiled a package for debian
testing) -- and: wow! awesome! i love it!
i was especially interested in the new glossary feature, and basicly it's just
what i was wishing for. but then again, i can't figure out how to pass
options
José Matos schrieb:
On Sunday 29 April 2007 16:48:35 Michael Gerz wrote:
Hi,
the attached patch changes some uses of the term "glossary" to
"nomenclature".
I will commit as soon as I get two OKs. (José vote will count as two).
AFAIU this is consensual, so please go ahead.
As so
On Sunday 29 April 2007 16:48:35 Michael Gerz wrote:
> Hi,
>
> the attached patch changes some uses of the term "glossary" to
> "nomenclature".
>
> I will commit as soon as I get two OKs. (José vote will count as two).
AFAIU this is consensual, so please go ahead.
> Michael
--
José Abílio
Uwe Stöhr wrote:
> the attached patch changes some uses of the term "glossary" to
"nomenclature".
>
> I will commit as soon as I get two OKs. (José vote will count as two).
Why that? The official name for this is "Glossary" and is used in all my
books I have?
I therefore vote for no, so n
Uwe Stöhr schrieb:
Michael Gerz schrieb:
Please note that LaTeX will produce a "glossary" with the title
"Nomenclature" (try it out if you don't believe).
Oops, indeed.
Ok I give an OK.
Fine. Now I need a second OK to proceed. Guys?
Michael
Michael Gerz schrieb:
Please note that LaTeX will produce a "glossary" with the title
"Nomenclature" (try it out if you don't believe).
Oops, indeed.
Ok I give an OK.
regards Uwe
Uwe Stöhr schrieb:
> the attached patch changes some uses of the term "glossary" to
"nomenclature".
>
> I will commit as soon as I get two OKs. (José vote will count as two).
Why that? The official name for this is "Glossary" and is used in all
my books I have?
I therefore vote for no, so no
> the attached patch changes some uses of the term "glossary" to "nomenclature".
>
> I will commit as soon as I get two OKs. (José vote will count as two).
Why that? The official name for this is "Glossary" and is used in all my books
I have?
I therefore vote for no, so now you need three OKs ;
t;)));
dialog->bc().bp(new NoRepeatedApplyReadOnlyPolicy);
} else if (name == "label") {
dialog->setController(new ControlCommand(*dialog, name, name));
Index: lib/doc/LaTeXConfig.lyx.in
=
On Wednesday 25 April 2007 8:53:54 am Georg Baum wrote:
>
> What I mean is that the insets that creates a nomenclature for LaTeX should
> not create a glossary for docbook. This is confusing, therefore the
> nomenclature inset should output something else than glossary entries for
> docbook IMHO.
In practice there is no single difference. All packages accept math symbols
and sort them in an identical way. That is why we can replace them easily.
Ugras
On 4/25/07, Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> "Ozgur" == Ozgur Ugras BARAN <[EMAIL PROTECTED]> writes:
Ozgur> umm..
> "Ozgur" == Ozgur Ugras BARAN <[EMAIL PROTECTED]> writes:
Ozgur> umm.. Really, what is the difference?? :-)
One is for words and the other for mathematical notation. Or at least
I thought so.
JMarc
umm.. Really, what is the difference?? :-)
On 4/25/07, Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> "Ozgur" == Ozgur Ugras BARAN <[EMAIL PROTECTED]> writes:
Ozgur> This is in my TODO list. I have already finished the multiple
Ozgur> indices and thinking on extending it for multiple g
> "Ozgur" == Ozgur Ugras BARAN <[EMAIL PROTECTED]> writes:
Ozgur> This is in my TODO list. I have already finished the multiple
Ozgur> indices and thinking on extending it for multiple glossaries.
Ozgur> But how will users react for this? Two glossary packages will
Ozgur> create confusion.
N
finished the multiple indices and
thinking on extending it for multiple glossaries. But how will users react
for this? Two glossary packages will create confusion. Probably we will have
to remove nomencl to replace with new glossary package. If this will be the
case it may be wise to change the glossary
José Matos wrote:
> On Monday 23 April 2007 5:52:23 pm Jean-Marc Lasgouttes wrote:
>>
>> Georg> The only problem with this is the docbook output. AFAIK docbook
>> Georg> does not support a nomenclature or list of symbols. Maybe one
>> Georg> could use variablelist, but it does not fit exactly. IMH
> "Ozgur" == Ozgur Ugras BARAN <[EMAIL PROTECTED]> writes:
Ozgur> Terminology fits good, but Jean-Marc has a point. The title of
Ozgur> the glossary is Nomenclature by default and it will be wise to
Ozgur> keep the same word for menu references for the sake of
Ozgur> consistency.
Yes, I think
problem is there is no "Real" glossary package. The most common one was (and
still is) nomencl.
I can add/ switch to support for a better glossary package. But the question
is which one.. If there would be any concensus on which glossary package to
switch for, I will happily im
Terminology fits good, but Jean-Marc has a point. The title of the glossary
is Nomenclature by default and it will be wise to keep the same word for
menu references for the sake of consistency.
Anybody else wishes switching for another glossary package? It will be easy
for me to implement it (if
On Tue, 24 Apr 2007, Michael Gerz wrote:
Ozgur Ugras BARAN schrieb:
Notation Entry/ Notation List in user visible places, IMHO. People
complained about Nomenclature word before. (Some people also complained
for
Notation word :-) ).
Actually, it was me who complained about "Notation" :-) Thi
Ozgur Ugras BARAN schrieb:
Notation Entry/ Notation List in user visible places, IMHO. People
complained about Nomenclature word before. (Some people also
complained for
Notation word :-) ).
Actually, it was me who complained about "Notation" :-) This term - at
least in German - is rather mean
attached fix corrects the tab orders in QNomencl.ui for lyx-1.5-beta-2
*** QNomenclUi.orig.ui 2007-04-24 17:41:45.0 +0300
--- QNomenclUi.ui 2007-04-24 17:39:11.0 +0300
***
*** 116,121
--- 116,122
symbolED
+ descriptionTE
prefixED
okPB
> "Ozgur" == Ozgur Ugras BARAN <[EMAIL PROTECTED]> writes:
Ozgur> Notation Entry/ Notation List in user visible places, IMHO.
Ozgur> People complained about Nomenclature word before. (Some people
Ozgur> also complained for Notation word :-) ).
But Nomenclature is the word that appears in the
t;>>> "Ozgur" == Ozgur Ugras BARAN <[EMAIL PROTECTED]> writes:
Ozgur> I like the doc version which omits the oldnomencl stuff. But I
Ozgur> observed one single problem: You are invoking makeindex for
Ozgur> nomencl after checking the the files with extensi
>>>>> "Ozgur" == Ozgur Ugras BARAN <[EMAIL PROTECTED]> writes:
Ozgur> I like the doc version which omits the oldnomencl stuff. But I
Ozgur> observed one single problem: You are invoking makeindex for
Ozgur> nomencl after checking the the files with extensi
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
On Monday 23 April 2007 5:52:23 pm Jean-Marc Lasgouttes wrote:
>
> Georg> The only problem with this is the docbook output. AFAIK docbook
> Georg> does not support a nomenclature or list of symbols. Maybe one
> Georg> could use variablelist, but it does not fit exactly. IMHO
> Georg> glossary shoul
TeXFeatures
>> part has been changed.
Georg> Fine with me. Do you put that in, or shall I do?
If you do not do it, I'll do it tomorrow. However, you'll be better at
writing the changelog.
Georg> Did you see Ugras' explanation for the choice of nomencl?
Yes.
Geo
>>>>> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> What I forgot: Of course you can misuse the nomencl stuff for
Georg> glossaries and redefine \nomname in the preamble, but I don't
Georg> think that LyX should do that.
Indeed.
JMarc
Georg Baum wrote:
> Jean-Marc Lasgouttes wrote:
>> Then the is the problem of glossary versus nomenclature. At least my
>> version of nomencl.sty writes a helpful "Nomenclature" heading in
>> front of my glossary. This is stupid.
>
> Did you see Ugras&#
roblem of glossary versus nomenclature. At least my
> version of nomencl.sty writes a helpful "Nomenclature" heading in
> front of my glossary. This is stupid.
Did you see Ugras' explanation for the choice of nomencl? IMHO the easiest
solution for this problem would be to not
>>>>> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> Here are my solutions: config.diff follows the idea suggested
Georg> by Jean-Marc: Test for the nomencl version in chkconfig.ltx and
Georg> put either "nomencl" or "nomencl"
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
If you have a solution, go ahead, since I haven't got one but got an idea
only :). I just try to act responsible :)
I can still give you a hand, if you wish..
On 4/20/07, Georg Baum <[EMAIL PROTECTED]> wrote:
Ozgur Ugras BARAN wrote:
> Hi all,
>
> If I can find a computer this weekend and if
Ozgur Ugras BARAN wrote:
> Hi all,
>
> If I can find a computer this weekend and if nobody is already caring
> about nomencl.sty version mess, I'll try to find a solution.
As I wrote some days ago I have a solution that is almost finished and that
I will send when Jean-Marc is back. Of course if
On Thursday 19 April 2007 3:46:37 pm Ozgur Ugras BARAN wrote:
> Hi all,
>
> If I can find a computer this weekend and if nobody is already caring about
> nomencl.sty version mess, I'll try to find a solution.
Please do. :-)
> Maybe you may wish to postpone Beta-2 until I submit the patch. Indee
Hi all,
If I can find a computer this weekend and if nobody is already caring about
nomencl.sty version mess, I'll try to find a solution.
Maybe you may wish to postpone Beta-2 until I submit the patch. Indeed,
releasing beta with this bug will end up with thousands of complaints. For
me, it is
Am Dienstag, 7. November 2006 21:05 schrieb Michael Gerz:
> Glossary sounds much better. I am going to change this, if you don't
mind.
>
> OK?
With me certainly. Please don't forget the documentation in Extended.lyx.
Georg
Georg Baum wrote:
Because Ugras thought that nomenclature is not well known by non-native
speakers. I don't know Notation either. Should we replace it
with "Glossary and "Glossary Entry" instead?"
As you know, the term "Notation" is quite generic in German. I guess the
same holds in English
Am Dienstag, 7. November 2006 20:51 schrieb Michael Gerz:
> Hi,
>
> why are the menu entries called "Notation"?
>
> stdmenus.ui: Item "Notation Entry" "nomencl-insert"
> stdmenus.ui:Item "Notation List" &qu
Hi,
why are the menu entries called "Notation"?
stdmenus.ui:Item "Notation Entry" "nomencl-insert"
stdmenus.ui: Item "Notation List" "nomencl-print"
stdtoolbars.ui: Item "Insert notation entry" "nomencl-insert"
Michael
... is missing.
It's getting difficult to find sensible icons in the KDE set. However, I'm
gonna put in the attached, which is sort-of-sensible, just that we have one.
It can be replaced if someone comes up with a better one.
Jürgen
nomencl-insert.xpm
Description: X pixmap
On Mon, Sep 11, 2006 at 11:50:31AM +0100, Ozgur Ugras BARAN wrote:
> It is so rare that, It is fantastic not to be wrong. :))
>
> then it should work well for the case \command[][]{}
>
> any comments on backporting this feature to lyx 1.4.x ?? it shouldn't
> take too much time for me..
Have it
On Mon, Sep 11, 2006 at 09:19:14AM +0100, Ozgur Ugras BARAN wrote:
> Therefore the command and its parameters are isolated from anything else,
> including another {}. Am I wrong?? (probably I am :) )
Erm. No. I was probably thinking about tex2lyx or such.
Should be pretty safe given this explan
OK.. I'll start next week, but I am not sure when I can finish. It can take
time depending on my free time.
I am very glad that you will handle lyx2lyx conversion :)
he necessary lyx2lyx conversion methods, and we put it in.
> Then we put the nomencl support in.
> This order has the advantage that the lyx2lyx changes will be a bit easier.
FWIW I agree with Georg on all points above.
> Georg
--
José Abílio
rs of
InsetCommandParams to get and set the parameters.
> If you still think the new insetCommand syntax is necessary, I can
> code it (don't know how long it takes). For the moment, nomencl
> implementation needs a slighly enhanced version of InsetCommandParams.
OK, then I suggest we pro
I can
code it (don't know how long it takes). For the moment, nomencl
implementation needs a slighly enhanced version of InsetCommandParams.
For the 1.4.x issue: That is fine for me. If anybody needs (and if I
have time), I can create a patch and put it on the wiki.
Ugras
On 9/11/06,
Ozgur Ugras BARAN wrote:
> It is so rare that, It is fantastic not to be wrong. :))
>
> then it should work well for the case \command[][]{}
The fact that InsetCommand stores its parameters in LaTeX-like syntax in LyX
files is a historical mistake, so I would rather avoid to extend this even
fu
It is so rare that, It is fantastic not to be wrong. :))
then it should work well for the case \command[][]{}
any comments on backporting this feature to lyx 1.4.x ?? it shouldn't
take too much time for me..
On 9/11/06, Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> "Ozgur" == Ozgur Ug
> "Ozgur" == Ozgur Ugras BARAN <[EMAIL PROTECTED]> writes:
Ozgur> \begin_inset LatexCommand \command[]{}{} \end_inset
Ozgur> Therefore the command and its parameters are isolated from
Ozgur> anything else, including another {}. Am I wrong?? (probably I
Ozgur> am :) )
No you are not!
JMarc
On 9/8/06, Andre Poenitz <[EMAIL PROTECTED]> wrote:
On Fri, Sep 08, 2006 at 03:24:56PM +0100, Ozgur Ugras BARAN wrote:
> and last of all, I developed this against the lyx 1.5.x. However, (if
> insetCommandParams mod. is correct) there is no reason not to add this
> functionality in lyx 1.4.x
>
On Fri, Sep 08, 2006 at 03:24:56PM +0100, Ozgur Ugras BARAN wrote:
> and last of all, I developed this against the lyx 1.5.x. However, (if
> insetCommandParams mod. is correct) there is no reason not to add this
> functionality in lyx 1.4.x
>
> with my kindest regards,
As usual: Things about whic
Dear all,
You can find an implementation of nomencl support in the attachments.
there are two diffs and the tgz file for the new files.
I basically developed everything deriving from the index counterpart.
Files in the directory frontend should be OK ( except the silly
constructors), since they
"Ozgur Ugras BARAN" <[EMAIL PROTECTED]> writes:
| Hi all,
|
| I added support for nomencl for glossary entries in the lyx code (qt3
| only, yet). If anybody interests in this functionality, I'll be glad
| to add my contribution.
Contributions are always welcome.
Do you hav
Hi all,
I added support for nomencl for glossary entries in the lyx code (qt3
only, yet). If anybody interests in this functionality, I'll be glad
to add my contribution.
regards,
Ugras
64 matches
Mail list logo
