On Wednesday 11 August 2004 21:19, Herbert Voss wrote:
> you have a lot of errors in your code.

It's not MY code, it's LyX's code ;). i just do the typing.
i find it extremely disappointing that lyx allows me to enter invalid 
entries using the Index entry dialog!!!

> - the underscore is _math_ character, so you cannot use it as
>    text character. You have a lot of labels like blah_blah. A safe
>    way is to use here blah-blah

i didn't know that.

> - same for a lot of the index entries. They always should use
>    the \_ characters for the text underscore. And by the way,
>    where is the sense to put section titles into the index? For
>    this you have the table of contents.

i don't see anything fundamentally wrong with putting section number 
text into the index. It's just text, after all, and the TOC is not 
alphabetized like the index is.

> - in some items you also forget the backslash at the underscores.
> -  \item class_name\<\>   this is senseless, use <> in textmode
> - \(\)  are the characters for the inline mathmode, what
>     you mean is only ()

i tried \<\> as a last resort, trying to get rid of the error messages. 
If i now change the entry to, e.g., "foo", i get a whole slew of 
complete unrelated errors going all the way back to the title line.

> you can try to use the underscore package in the preamble, then
> have to fix only the errors for the last three items.

i will go through and get rid of all the underscores in the index, but 
i've got to say, i'm NOT at all happy about that. For example, i'm 
indexing C++ class names, like foo_bar.

> I corrected the exported tex file, because the error handling
> with the error boxes inside LyX is a mess. Give me your
> private email and I'll send you the tex file.

i appreciate that, but the tex itself won't do me much good. i don't 
know tex, which is why i use LyX.

Thanks VERY much for your feedback!

-- 
----- [EMAIL PROTECTED]   http://s11n.net
"...pleasure is a grace and is not obedient to the commands
of the will." -- Alan W. Watts

Reply via email to