>>> "Gennady" == Gennady Uraltsev writes:
> Hello everyone,
> I am sorry for all the problems that have arisen. I wanted to contribute
> to the discussion somewhat.
This is for sure not your fault.
> 1) Personally I often have double subscripts i.e. expressions of the form
> $
Hello everyone,
I am sorry for all the problems that have arisen. I wanted to contribute
to the discussion somewhat.
1) Personally I often have double subscripts i.e. expressions of the form
$
\int_{a_i}^{a_{i+1}}
$
(I am a PhD in math)
2) LaTeX (or at least AMS) forbids expressions of the typ
> Uwe Brauer writes:
> Hi Uwe,
> That might indicate that you are working in a field of math where there
> are few exponentiated expressions which are already exponentiated. But
> I don't think that exponents have grown out of vogue in general. ;-)
Well I really wish to see the
Uwe Brauer writes:
Hi Uwe,
> I have seen his shots, these are border line cases, which are used very
> little. Look I have written mathematics with latex over the last 25
> years and in countless occasions I have used ^or but never nested
> expressions and this is also true for the publication
> Uwe Brauer writes:
> Hi Uwe,
> Yes, exactly.
> Sorry, but I think there's no value in a feature which only works in the
> simplest cases and might be wrong otherwise. Have a look at Gennady's
> screenshots.
I have seen his shots, these are border line cases, which are u
Uwe Brauer writes:
Hi Uwe,
> > Given that it doesn't work and produces even wrong results, I removed
> > the complete feature, i.e., the values multi-level and invisible. I
> > don't see how it could be made working without parsing the actual math
> > expressions and incremental
>>> "Tassilo" == Tassilo Horn writes:
> Uwe Brauer writes:
> Hi Uwe and Gennady,
>> Not really. I also don't really need that feature.
> Given that it doesn't work and produces even wrong results, I removed
> the complete feature, i.e., the values multi-level and invisible.
Uwe Brauer writes:
Hi Uwe and Gennady,
> Not really. I also don't really need that feature.
Given that it doesn't work and produces even wrong results, I removed
the complete feature, i.e., the values multi-level and invisible. I
don't see how it could be made working without parsing the actua
