Re: Double dash in Lyx 2.2.1 is not printed correctly

[Jean-Marc Lasgouttes]

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 conversion of consecutive hyphens on
input if there is popular demand. That would make entering of en-dashes and
em-dashes more difficult, and currently I believe that the current behaviour
is convenient for most users.


There was this idea of extending the autocorrect functionality in a 
configurable way. This would mean that one would be able to turn it off.


JMarc

Re: Double dash in Lyx 2.2.1 is not printed correctly

[Richard Heck]

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 demand. That would make entering of en-dashes and 
> em-dashes more difficult, and currently I believe that the current behaviour 
> is convenient for most users.

I think we do have a weird hybrid sort of behavior now. If there were
some binding we could use for this purpose, then maybe that would help.
Maybe dash then ctrl-dash gives an en-dash, or something like that?

Richard

Re: Double dash in Lyx 2.2.1 is not printed correctly

[Georg Baum]

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. 
http://www.lyx.org/trac/ticket/3647, http://www.lyx.org/trac/ticket/8561) 
and has been changed in version 2.2. Now a hyphen that is stored in a LyX 
document is always typeset as a hyphen, even for two or more consecutive 
hyphens.

> Now in version 2.2.1 I tried to type 2014--2016 but Lyx automatically
> overwrites this double dash with en-dash. This is simply WRONG thing to
> do. en-dash is a special character that I do not want in my code!

This conversion was implemented in order to mimic the 2.1 behaviour. In 2.1 
if you enter two consecutive hyphens, you get an en-dash in the output. In 
2.2, if you enter two consecutive hyphens, you get an en-dash in the output 
as well. The only difference is that in 2.2, the display on screen and the 
contents in the .lyx file are also copnsistent with the output.

> To make it clear: imagine that I want to type $\mu$ and LyX starts to
> convert this to unicode character mu U+039C,  or whatever

You can always enter - - and then delete the space if you really need two 
consecutive hyphens.

> 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 demand. That would make entering of en-dashes and 
em-dashes more difficult, and currently I believe that the current behaviour 
is convenient for most users.

> On 07-Sep-16 19:06, Scott Kostyshak wrote:
>> 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 message in index sorting when compiling PDF.

If a document that produces PDF output does not produce the same PDF output 
anymore after loading it in 2.2 then this is a bug. Please file it at 
http://www.lyx.org/trac/wiki/BugTrackerHome and include a test case in 2.1 
format.


Georg

Re: Double dash in Lyx 2.2.1 is not printed correctly

[Guillaume Munch]

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 type 2014--2016 but Lyx automatically
overwrites this double dash with en-dash. This is simply WRONG thing to
do. en-dash is a special character that I do not want in my code!



In which context is this? It is possible to input -- in ERT? (Ctrl+L).

Re: Double dash in Lyx 2.2.1 is not printed correctly

[Kornel Benko]

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 if it Latex code.
> 
> Now in version 2.2.1 I tried to type 2014--2016 but Lyx automatically 
> overwrites this double dash with en-dash. This is simply WRONG thing to 
> do. en-dash is a special character that I do not want in my code!
> 
> To make it clear: imagine that I want to type $\mu$ and LyX starts to 
> convert this to unicode character mu U+039C,  or whatever
> 
> 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
> 
> Thanks,
> 
> Danko
> 

To insert a dash dash, I use nobreakdash. To do it easy make a shortcut
Tools->Settings->Editing->Shortcuts
1.) search for nobreakdash
if not there add some sortcut. In my case
Function:   specialchar-insert nobreakdash
Shortcut: Ctrl+Alt+-

2.) You have to enable amsmath (e.g. automatic)
Document->Settings...->Options for Math

> On 07-Sep-16 19:06, Scott Kostyshak wrote:
> > 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 message in
> >> index sorting when compiling PDF.
> >>
> >> When I found that en-dashes appeared in the manuscript, I replaced them
> >> again with double dashes (as this was the case in Lyx 2.1). But then the
> >> compiled PDF by Lyx 2.2.1 shows double dashes in the PDF instead of 
> >> en-dash.
> >>
> >> I did not find an explanation of what is going on in internet, so decided 
> >> to
> >> share this problem with the lyx users list
> >>
> >> Any advice how to restore the old Lyx behavior in version 2.2.1 would be
> >> appreciated.
> >>
> >> D. Georgiev
> >>
> > Hi Danko,
> >
> > Can you please send a minimal example (to the list)? This will make it
> > easier to investigate.
> >
> > Thanks for this report.
> >
> > Scott
> 

Kornel

signature.asc
Description: This is a digitally signed message part.

Re: Double dash in Lyx 2.2.1 is not printed correctly

[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 if it Latex code.


Now in version 2.2.1 I tried to type 2014--2016 but Lyx automatically 
overwrites this double dash with en-dash. This is simply WRONG thing to 
do. en-dash is a special character that I do not want in my code!


To make it clear: imagine that I want to type $\mu$ and LyX starts to 
convert this to unicode character mu U+039C,  or whatever


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


Thanks,

Danko


On 07-Sep-16 19:06, Scott Kostyshak wrote:

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 message in
index sorting when compiling PDF.

When I found that en-dashes appeared in the manuscript, I replaced them
again with double dashes (as this was the case in Lyx 2.1). But then the
compiled PDF by Lyx 2.2.1 shows double dashes in the PDF instead of en-dash.

I did not find an explanation of what is going on in internet, so decided to
share this problem with the lyx users list

Any advice how to restore the old Lyx behavior in version 2.2.1 would be
appreciated.

D. Georgiev


Hi Danko,

Can you please send a minimal example (to the list)? This will make it
easier to investigate.

Thanks for this report.

Scott


--
Danko Georgiev, MD, PhD

Institute for Advanced Study
Pleven 5800, Bulgaria, EU
Tel: +359-877-095-888
E-mail: danko...@gmail.com
Skype: dankomed

Re: Double dash in Lyx 2.2.1 is not printed correctly

[Scott Kostyshak]

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 message in
> index sorting when compiling PDF.
> 
> When I found that en-dashes appeared in the manuscript, I replaced them
> again with double dashes (as this was the case in Lyx 2.1). But then the
> compiled PDF by Lyx 2.2.1 shows double dashes in the PDF instead of en-dash.
> 
> I did not find an explanation of what is going on in internet, so decided to
> share this problem with the lyx users list
> 
> Any advice how to restore the old Lyx behavior in version 2.2.1 would be
> appreciated.
> 
> D. Georgiev
> 

Hi Danko,

Can you please send a minimal example (to the list)? This will make it
easier to investigate.

Thanks for this report.

Scott


signature.asc
Description: PGP signature