Re: LyX 2.2.3, Finally?
On 2017-03-28, Richard Heck wrote: > On 03/28/2017 04:55 PM, Guenter Milde wrote: >> On 2017-03-28, Richard Heck wrote: >>> It looks as if we're now ready for 2.2.3, after some of the recent work. >>> Any reason not to freeze strings now? >> Yes, ... > Sorry, think there is some confusion. I was talking about 2.2.3, NOT > 2.3.0. Correct me if I'm wrong, but those all look like issues for 2.3.0. You are right, I mixed up 2.3. and 2.2.3. For 2.2.3, I propose a patch to work around the overfull lines with em-dashes: As lyx2lyx converts --- and -- to the intermediate representation \threehyphens and \twohyphens, we can add a "line break opportunity" (ZWSP) after the literal dashes in the second conversion step: --- a/src/Text.cpp +++ b/src/Text.cpp @@ -506,9 +506,11 @@ void Text::readParToken(Paragraph & par, Lexer & lex, par.insert(par.size(), from_ascii("---"), font, change); } else { if (token == "\\twohyphens") - par.insertChar(par.size(), 0x2013, font, change); - else - par.insertChar(par.size(), 0x2014, font, change); + par.insertChar(par.size(), 0x2013, font, change); // EN DASH + else { + par.insertChar(par.size(), 0x2014, font, change); // EM DASH + par.insertChar(par.size(), 0x200b, font, change); // ZWSP + } } } else if (token == "\\backslash") { par.appendChar('\\', font, change); Of course, this cannot restore lost information if converted documents are already modified and saved with 2.2. Günter
Re: LyX 2.2.3, Finally?
On 03/28/2017 04:55 PM, Guenter Milde wrote: > On 2017-03-28, Richard Heck wrote: >> It looks as if we're now ready for 2.2.3, after some of the recent work. >> Any reason not to freeze strings now? > Yes: > > * Quote styles are missing the "catchy" names from 2.2 and hard to > discern on small screen or for the visually impaired. > > I like the "language" names back - preferably combined with > example using the correct Unicode characters, e.g. > > »›Danish‹ quotes« > „‚German‘ quotes“ > «“Italian“ quotes» > ... > > * As a stop-gap measure until a proper fix is ready, can we please change > the misleading font-encoding GUI name "Default" now? > > http://www.lyx.org/trac/ticket/9741#comment:6 > > * The special character for a "line break opportunity without hyphen" > needs translation of name and tooltip. > http://www.lyx.org/trac/ticket/10585 Sorry, think there is some confusion. I was talking about 2.2.3, NOT 2.3.0. Correct me if I'm wrong, but those all look like issues for 2.3.0. Richard
Re: LyX 2.2.3, Finally?
On 2017-03-28, Richard Heck wrote: > It looks as if we're now ready for 2.2.3, after some of the recent work. > Any reason not to freeze strings now? Yes: * Quote styles are missing the "catchy" names from 2.2 and hard to discern on small screen or for the visually impaired. I like the "language" names back - preferably combined with example using the correct Unicode characters, e.g. »›Danish‹ quotes« „‚German‘ quotes“ «“Italian“ quotes» ... * As a stop-gap measure until a proper fix is ready, can we please change the misleading font-encoding GUI name "Default" now? http://www.lyx.org/trac/ticket/9741#comment:6 * The special character for a "line break opportunity without hyphen" needs translation of name and tooltip. http://www.lyx.org/trac/ticket/10585 Thanks, Günter
Re: LyX 2.2.3, Finally?
Go ahead. JMarc Le 28 mars 2017 21:00:50 GMT+02:00, Richard Hecka écrit : >It looks as if we're now ready for 2.2.3, after some of the recent >work. >Any reason not to freeze strings now? > >Richard