Le 10/09/16 à 11:57, Georg Baum a écrit :
Lyx now behaves as MS Word instead as a LaTeX typesetter. I don't think
the solution is to revert back my LyX to 2.1
LyX has never really been word nor a LaTeX typsetter. It is something in
between.
We could of course change the automatic
On 09/10/2016 05:57 AM, Georg Baum wrote:
> Danko Georgiev wrote:
>> Lyx now behaves as MS Word instead as a LaTeX typesetter. I don't think the
>> solution is to revert back my LyX to 2.1
> We could of course change the automatic conversion of consecutive hyphens on
> input if there is popular
Danko Georgiev wrote:
> Dear Scott,
>
> If you try typesetting time periods, in old LyX you could just type
> "2014--2016". When you print PDF you will read 2014[en-dash]2016. In
> other words, old Lyx printed the double dash as if it Latex code.
Yes. This behaviour caused lots of trouble (e.g.
Le 07/09/2016 à 17:19, Danko Georgiev a écrit :
Dear Scott,
If you try typesetting time periods, in old LyX you could just type
"2014--2016". When you print PDF you will read 2014[en-dash]2016. In
other words, old Lyx printed the double dash as if it Latex code.
Now in version 2.2.1 I tried to
Am Mittwoch, 7. September 2016 um 19:19:03, schrieb Danko Georgiev
> Dear Scott,
>
> If you try typesetting time periods, in old LyX you could just type
> "2014--2016". When you print PDF you will read 2014[en-dash]2016. In
> other words, old Lyx printed the double dash as
Dear Scott,
If you try typesetting time periods, in old LyX you could just type
"2014--2016". When you print PDF you will read 2014[en-dash]2016. In
other words, old Lyx printed the double dash as if it Latex code.
Now in version 2.2.1 I tried to type 2014--2016 but Lyx automatically
On Wed, Sep 07, 2016 at 07:02:58PM +0300, Danko Georgiev wrote:
> Hello,
>
> I have just updated to the newest LyX 2.2.1. and immediately got a problem
> with automatic conversion of double dashes -- to en-dash in a manuscript
> written with Lyx 2.1. This en-dash replacement resulted in error