On Tue, Mar 07, 2017 at 11:48:41AM +0100, Enrico Forestieri wrote: > The attached patch fixes the regression introduced in 2.2 about the > output of en- and em-dashes. In 2.2 en- and em-dashes are output as > the \textendash and \textemdash macros, causing changed output in > old documents and also bugs (for example, #10490). > > With this patch, documents produced with older versions work again > as intended, while documents produced with 2.2 can be made to produce > the exact same output by simply checking "Don't use ligatures for en- > and em-dashes" in Document->Settings->Fonts. > > Actually, I am attaching two patches. They differ only in the way > documents are exported to earlier versions. If one wants to use > ligatures for en/em-dashes, in order to not cause changed output, > a zero-width space inset is inserted after each en/em-dash when > using the first patch, while the second patch inserts a zero-width > space character (U+200B). Both are removed when reloading documents > with 2.3, so that they don't accumulate. > > The second patch produces more visually pleasant documents, as the > zero-width space character is invisible on screen, but they work > OOTB only when exporting to 2.1 at most. This is because 2.0 and > earlier versions don't define U+200B in the unicodesymbols file. > However it could be manually added there.
Apparently, nobody has a preference, so I am going to commit the second patch, i.e., the one using a zero-width space character. -- Enrico
