On Thu, Jun 01, 2017 at 08:52:18PM +0000, Guenter Milde wrote: > Dear Enrico, > > thank you for the patch. > > On 2017-06-01, Enrico Forestieri wrote: > > On Thu, Jun 01, 2017 at 02:12:56PM +0000, Guenter Milde wrote: > > > Please, try the attached. I don't know what you are trying to do, > > but I hope you are not trying to sabotage the last fixes to the > > en/emdash mess. > > I would be really upset to see all of them as ert. > > If this is a first step toward a really clean solution (to solve I > > don't know what), that would be fine, though. > > I am trying to clean up the mess after the last fixes just moved the > problems to another area (see http://www.lyx.org/trac/ticket/10543, comment > 3 section "LyX 2.3dev"). > > ERT is the only fully backwards compatible solution for 2.2. > > It can be converted to plain -- or --- in backward conversion from 2.2 to > 2.1. > > For 2.3, we can use a new "SpecialChar" inset. > Then, > > * a "ligature dash" can be back-converted to "\twohyphens" or > "\threehyphens" with lyx2lyx. It will become ERT in 2.2 and > (unmarked) -- or --- in 2.1 and earlier. > > * an ERT with just -- or --- can be converted to the SpecialChar > inset with lyx2lyx forward conversion from 2.2. to 2.3.
I really don't want to go again through all this, but I am fiercely opposed to having en/em-dashes as ERT because you end up with a mess if you have to edit those documents, unless you want to also enter in ERT all dashes that you may need to add. But maybe I am simply misunderstanding. I think that the actual solution is the lesser evil. You have problems only if the document was later edited with 2.2. And having to manually select a preference to adjust things is not that intolerable, IMO. And I don't consider decisive the fact that literal and ligatures dashes may have been mixed together. In the past I had to adapt to more cumbersome changes. -- Enrico
