On 15 Oct 1999, Jean-Marc Lasgouttes wrote:
> How did you input the formula? Mathed gives errors when reading it:
>
> Line ~76: Math parse error: Expected {. Maybe you forgot to enclose an argument in {}
> Line ~76: Math parse error: Unmatching braces
> Math Panic, expect problems!
>
> You can
> "Rod" == Rod Pinna <[EMAIL PROTECTED]> writes:
Rod> This message is in MIME format. The first part should be
Rod> readable text, while the remaining parts are likely unreadable
Rod> without MIME-aware tools. Send mail to
Rod> [EMAIL PROTECTED] for more info.
Rod> ---559023410-851401618-9
On 14 Oct 1999, Jean-Marc Lasgouttes wrote:
Jean-Marc,
Thanks for having a look at the problem. In the end, it turned out the it
was a "stupid user" error. The problem was that the line:
> Rod> Also, I've got the following in the body of the text
> Rod> r_\textrm{wave}
should have been r_\math
> "Rod" == Rod Pinna <[EMAIL PROTECTED]> writes:
Rod> Hello all, I've run into a "behaviour" that hasn't occurred with
Rod> previous versions of lyx. After upgrading from 1.0.3 to 1.0.4,
Rod> Lyx is now including extra spaces in subscripts when a file is
Rod> closed and reopened. For example:
Hello,
On Wed, 6 Oct 1999, Rod Pinna wrote:
Something he can't reproduce again...
Essentially, I was getting a behaviour where Lyx (1.0.4) was inserting
extra spaces between non-roman characters and their sub- and superscripts.
Anyway, the problem turned out to be that in a preceeding paragrap
Hello all,
I've run into a "behaviour" that hasn't occurred with previous versions of
lyx. After upgrading from 1.0.3 to 1.0.4, Lyx is now including extra
spaces in subscripts when a file is closed and reopened. For example:
\beta
z
becomes
\beta
z
^
|---extra space.
