On 2017-01-24, Enrico Forestieri wrote:
> On Tue, Jan 24, 2017 at 12:00:02PM +0000, Guenter Milde wrote:
>> On 2017-01-24, Enrico Forestieri wrote:
>> > On Mon, Jan 23, 2017 at 10:14:39PM +0000, Guenter Milde wrote:

>> > ... However, I am more radical and would like that the automatic
>> > transformation of -- and --- to \textendash and \textemdash be
>> > removed. If I enter -- I want to get --, otherwise strange things
>> > and obscure bugs can happen.

However, with LaTeX font ligatures, similar strange things happen:

>> For example:
>> > 1) start a new document and input "--" and you get \textendash

In LaTeX and LyX 2.1, you get an EN DASH in the output.

>> > 2) now enter another "-" and you get \textemdash

In LaTeX and LyX 2.1, you get an EM DASH in the output.

>> > 3) now enter another "-" and everything gets replaced by "-"

In LaTeX and LyX 2.1, you get an EM DASH followed by - in the output.


>> > This means that I am not able to enter "---------", for example.

>> At least not easily. (It works if you insert with spaces and delete them
>> later.)

> Not at all. You get -{}-{}-{}-{}-{}-{}-{}-{}- which is worse.

This is to ensure you get ----------- in the output (for normal
text fonts).

> You have to use ERT to introduce four hyphens? How's that?

There are alternatives: LyX-Code, set the font to \texttt, mathed

>> OTOH, with the old behaviour strange things happen on export:

>> 1) start a new document and insert this---foo
>> 2) copy from another source bar—bar (with Unicode emdash literal)

Sorry, I did not check. The following statement has to be corrected:

- In LyX <2.2, both emdashes look completely identical, but one allows
- line breaks after the dash and the other not!

+ In LyX <2.2, the GUI shows "--", but the output contains an en-dash,
+ the GUI shows "---" but the output has and em-dash!

This is in contrast to, e.g. handling of >>: in the LaTeX output the > are
separated to prevent ligating to ».


> But packages that expect to see two hyphens instead of \textendash
> are not broken...

They are not broken but they are also not intended to be fed with "standard"
text.

Günter

Reply via email to