Richard Heck wrote:
> On 05/26/2014 05:02 PM, José Matos wrote:
>>
>> I favour the second option for exactly the same arguments you have
>> used. It is also reasonable to assume that people that relied on the
>> "bug"/lyx current behaviour are capable to workaround the problems.
>>
>
> Same here.
On 05/26/2014 05:02 PM, José Matos wrote:
On Monday 26 May 2014 22:07:01 Georg Baum wrote:
> What do you think? We cannot get a 100% correct solution, and I
slightly
> tend towards the second option, since IMHO amsmath is needed for any
serious
> math document anyway.
>
>
> Georg
I fa
On Monday 26 May 2014 22:07:01 Georg Baum wrote:
> What do you think? We cannot get a 100% correct solution, and I slightly
> tend towards the second option, since IMHO amsmath is needed for any serious
> math document anyway.
>
>
> Georg
I favour the second option for exactly the same argumen
Hi,
I am currently cleaning up my stash pile and finishing native support for
\smash[t] and \smash[b] (this came from bug 8967) and \notag (same as
\nonumber, but uses amsmath, this is helpful if you want to import AMS
example documents with tex2lyx).
These commands cause now amsmath to be aut
> First, if you haven't noticed, version 1.1.5cvs uses
>"\SpecialChar \protected_separator\n" (2)
> whereas previous versions used
>"\n\protected_separator\n" (1)
> My suggestion is to use
>"\SpecialChar ~\n" (3)
> Using (3) may break lyx2* converters.
On Sat, Apr 08, 2000 at 10:48:37AM +0200, Asger K. Alstrup Nielsen wrote:
> > Why a protected separator is encoded as "\SpecialChar \protected_separator"
> > and not "\SpecialChar ~" ?
> > The latter is shorter, and it is more consistent to the encoding of other
> > special chars (\SpecialChar \-
> Why a protected separator is encoded as "\SpecialChar \protected_separator"
> and not "\SpecialChar ~" ?
> The latter is shorter, and it is more consistent to the encoding of other
> special chars (\SpecialChar \- or \SpecialChar \@.)
I suspect the only reason is historical.
However, to keep
Why a protected separator is encoded as "\SpecialChar \protected_separator"
and not "\SpecialChar ~" ?
The latter is shorter, and it is more consistent to the encoding of other
special chars (\SpecialChar \- or \SpecialChar \@.)
