Re: Plan for final steps of 2.3.0 release

Le 13/02/2018 à 21:30, Scott Kostyshak a écrit : On Tue, Feb 13, 2018 at 01:14:43PM +, Jean-Marc Lasgouttes wrote: Scott, do you want to wait for a nod from the windows side or can I apply the patch now ? Please go ahead now. Thanks for the patch. Done. Someone might want to remove the

Re: [LyX/master] Fix crash when citeengine is unknown.

Am Montag, den 12.02.2018, 16:31 -0500 schrieb Richard Heck: > > src/frontends/qt4/GuiDocument.cpp |6 ++ > > 1 files changed, 6 insertions(+), 0 deletions(-) > > > > diff --git a/src/frontends/qt4/GuiDocument.cpp > > b/src/frontends/qt4/GuiDocument.cpp > > index 85318bc..8149b50 100644

Russian UI (was: Disable and hide the pixmap cache feature)

Le 14/02/2018 à 10:29, Jean-Marc Lasgouttes a écrit : --- a/lib/RELEASE-NOTES +++ b/lib/RELEASE-NOTES @@ -20,6 +20,10 @@ See chapter 3.9.1.1 "Dashes and Line Breaks" of the User Guide and "Caveats when upgrading from earlier versions to 2.3.x" below. +* The preference

Re: Russian UI (was: Disable and hide the pixmap cache feature)

Jean-Pierre Chrétien wrote: > Russian UI translation has been recently completed, right? Right. > OK to commit? Sorry, I didn't see your patch and committed myself... P

Re: integral upper limit adjacent to integral sign

Le 14/02/2018 à 16:50, Pavel Sanda a écrit : Jean-Marc Lasgouttes wrote: I have tried to run ttfdump on the ttf files, and it shows properly negative right bearings for both fonts. At this point, I give up :) Maybe we can try bipartisan attempt on Qt bug tracking system. I recently filled up

Re: [LyX/master] UserGuide.lyx: document the removal of the pixmap cache for all languages

Le 14/02/2018 à 14:51, Uwe Stöhr a écrit : commit 1fb1b0a3f8429a12ce63b6daada1ac4ec4119889 Author: Uwe Stöhr Date: Wed Feb 14 14:51:22 2018 +0100 UserGuide.lyx: document the removal of the pixmap cache for all languages Dear Uwe, Technically pixmap cache has not

Re: [LyX/master] Implement buffer-anonymize more efficiently

On 02/12/2018 08:39 AM, Jean-Marc Lasgouttes wrote: > Le 12/02/2018 à 14:38, Jean-Marc Lasgouttes a écrit : >> commit 1dba36c7cec6aeec2576e7a99e2967e867076a01 >> Author: Jean-Marc Lasgouttes >> Date:   Wed Feb 7 15:35:46 2018 +0100 >> >> Implement buffer-anonymize more

Re: Plan for final steps of 2.3.0 release

On 02/14/2018 09:34 AM, Jean-Marc Lasgouttes wrote: > Le 13/02/2018 à 07:53, Jürgen Spitzmüller a écrit : >> Am Dienstag, den 13.02.2018, 01:54 +0100 schrieb Uwe Stöhr: >>> In my opinion a major version should contain all major bugfixes. Here >>> we >>> have a menu entry for a feature that doesn't

Re: Staging Branches

Am Mittwoch, den 14.02.2018, 10:15 -0500 schrieb Richard Heck: > I've just created two staging branches: 2.3.1-staging and 2.3.2- > staging. > Rules for committing to these are the same as for stable branch, > i.e., > clear it with me first. > > As usual, the reason to create these is that we

Re: [LyX/master] Fix crash when citeengine is unknown.

On 02/14/2018 03:04 AM, Jürgen Spitzmüller wrote: > Am Montag, den 12.02.2018, 16:31 -0500 schrieb Richard Heck: >>> src/frontends/qt4/GuiDocument.cpp |6 ++ >>> 1 files changed, 6 insertions(+), 0 deletions(-) >>> >>> diff --git a/src/frontends/qt4/GuiDocument.cpp >>>

Re: Plan for final steps of 2.3.0 release

Le 13/02/2018 à 07:53, Jürgen Spitzmüller a écrit : Am Dienstag, den 13.02.2018, 01:54 +0100 schrieb Uwe Stöhr: In my opinion a major version should contain all major bugfixes. Here we have a menu entry for a feature that doesn't work. This is no good advertisement for LyX. We have a working

2.2.4

Since we are approaching the 2.3.0 release, that means we are also approaching the last release of the 2.2.x series. I'd like to freeze strings and notify our translators on Sunday or Monday, so if there is anything left you'd like to do there, let me know ASAP. Richard

Re: integral upper limit adjacent to integral sign

Jean-Marc Lasgouttes wrote: > I have tried to run ttfdump on the ttf files, and it shows properly > negative right bearings for both fonts. At this point, I give up :) Maybe we can try bipartisan attempt on Qt bug tracking system. I recently filled up the bug for Qt5 not rendering characters for

Re: [LyX/master] Fix crash when citeengine is unknown.

Am Mittwoch, den 14.02.2018, 10:11 -0500 schrieb Richard Heck: > > I wonder how that happens. > > LyXCiteEngine const * CiteEnginesList::operator[](string const & str) > const > { > LyXCiteEnginesList::const_iterator it = englist_.begin(); > for (; it != englist_.end(); ++it) >

Staging Branches

I've just created two staging branches: 2.3.1-staging and 2.3.2-staging. Rules for committing to these are the same as for stable branch, i.e., clear it with me first. As usual, the reason to create these is that we have some fixes piling up already, and I don't want to forget them. Richard

Re: integral upper limit adjacent to integral sign

Le 13/02/2018 à 00:10, Scott Kostyshak a écrit : Does that seem reasonable to you (for 2.3.0)? Yes, I think so. Also because this regression will put pressure on JMarc for quickly finding a solution ;) Thanks, sounds good. OK, I know nobody cares, but it seems that the issue is not really

Re: integral upper limit adjacent to integral sign

Jean-Marc Lasgouttes wrote: > I took a look at the Qt4 and Qt5 code and did not see a difference. It > might be that our fonts are malformed. I loaded esint10.ttf into fontforge and when I go to Metrics->set L/RBearings of integral sign (#1) I see the value 113.5. I doesn't look as what your log

Re: 2.2.4

On 02/14/2018 12:04 PM, Guenter Milde wrote: > On 2018-02-14, Richard Heck wrote: >> Since we are approaching the 2.3.0 release, that means we are also >> approaching the last release of the 2.2.x series. I'd like to freeze >> strings and notify our translators on Sunday or Monday, so if there is

Re: [LyX/master] Fix sideset hints, part of bug #11015.

Pavel Sanda wrote: > commit 584b83d33c50a8bd88e1baae9b6d4dcbadcf0b82 > Author: Pavel Sanda > Date: Sat Feb 3 17:51:00 2018 +0100 > > Fix sideset hints, part of bug #11015. Richard, 2.3.1 or 2? Pavel

Re: Staging Branches

Richard Heck wrote: > > can we merge the painting branch into 2.3.1 staging? > > I'm inclusively working on master without larger issues for quite some time > > now. That does not say anything about mac/win arch, but the sooner we start > > testing the better. > > I'd be happy to have it in

Re: 2.2.4

On 2018-02-14, Richard Heck wrote: > Since we are approaching the 2.3.0 release, that means we are also > approaching the last release of the 2.2.x series. I'd like to freeze > strings and notify our translators on Sunday or Monday, so if there is > anything left you'd like to do there, let me

Re: lyx2lyx problems (nothing to do with '--' ligatures)

On 2018-01-22, Kornel Benko wrote: > I expanded the lyx2lyx test so, the an error is emitted at 10th > repeated run to export lyx16x. > If two consecutive created lyx-files are identical, the test stops > without error. if a created lyx-file is not loadable, test stops with > error. We found

Re: [LyX/master] Fix crash when citeengine is unknown.

Am Mittwoch, den 14.02.2018, 12:50 -0500 schrieb Richard Heck: > I wonder if what we really need to do here is add the 'unknown' cite > engine the way we do unknown layouts. Otherwise, if, say, the font is > modified in Document>Settings, then I am guessing we won't save the > document with the

Re: Staging Branches

Richard Heck wrote: > I've just created two staging branches: 2.3.1-staging and 2.3.2-staging. > Rules for committing to these are the same as for stable branch, i.e., > clear it with me first. Richard/JMarc, can we merge the painting branch into 2.3.1 staging? I'm inclusively working on master

Re: Staging Branches

On 02/14/2018 11:13 AM, Jürgen Spitzmüller wrote: > Am Mittwoch, den 14.02.2018, 10:15 -0500 schrieb Richard Heck: >> I've just created two staging branches: 2.3.1-staging and 2.3.2- >> staging. >> Rules for committing to these are the same as for stable branch, >> i.e., >> clear it with me first.

Re: Staging Branches

On 02/14/2018 12:17 PM, Pavel Sanda wrote: > Richard Heck wrote: >> I've just created two staging branches: 2.3.1-staging and 2.3.2-staging. >> Rules for committing to these are the same as for stable branch, i.e., >> clear it with me first. > Richard/JMarc, > > can we merge the painting branch

Re: Staging Branches

On Wed, Feb 14, 2018 at 06:40:28PM +, Richard Heck wrote: > On 02/14/2018 01:09 PM, Pavel Sanda wrote: > > Richard Heck wrote: > >>> can we merge the painting branch into 2.3.1 staging? > >>> I'm inclusively working on master without larger issues for quite some > >>> time > >>> now. That

Re: integral upper limit adjacent to integral sign

On Wed, Feb 14, 2018 at 03:31:24PM +, Jean-Marc Lasgouttes wrote: > Le 13/02/2018 à 00:10, Scott Kostyshak a écrit : > > > > Does that seem reasonable to you (for 2.3.0)? > > > > > > Yes, I think so. Also because this regression will put pressure on > > > JMarc for quickly finding a solution

Re: [LyX/master] Fix crash when citeengine is unknown.

On 02/14/2018 11:12 AM, Jürgen Spitzmüller wrote: > Am Mittwoch, den 14.02.2018, 10:11 -0500 schrieb Richard Heck: >>> I wonder how that happens. >> LyXCiteEngine const * CiteEnginesList::operator[](string const & str) >> const >> { >> LyXCiteEnginesList::const_iterator it = englist_.begin();

Re: Basque translation

Hi Pavel, > On 12 Feb 2018, at 21:29, Pavel Sanda wrote: > > I??aki Larra??aga Murgoitio wrote: >> Hi Jürgen, and LyX devel team, >> >> Basque translation updated at %100 as requested :-) > > Not so fast! :) > > There is one more check we need from you - I just committed

Re: Staging Branches

On 02/14/2018 01:09 PM, Pavel Sanda wrote: > Richard Heck wrote: >>> can we merge the painting branch into 2.3.1 staging? >>> I'm inclusively working on master without larger issues for quite some time >>> now. That does not say anything about mac/win arch, but the sooner we start >>> testing the

Re: [LyX/master] Fix sideset hints, part of bug #11015.

On 02/14/2018 01:02 PM, Pavel Sanda wrote: > Pavel Sanda wrote: >> commit 584b83d33c50a8bd88e1baae9b6d4dcbadcf0b82 >> Author: Pavel Sanda >> Date: Sat Feb 3 17:51:00 2018 +0100 >> >> Fix sideset hints, part of bug #11015. > Richard, 2.3.1 or 2? Seems fine for 2.3.1. rh

Re: lyx2lyx problems (nothing to do with '--' ligatures)

Am Mittwoch, 14. Februar 2018 17:26:47 CET schrieb Guenter Milde : > On 2018-01-22, Kornel Benko wrote: > > I expanded the lyx2lyx test so, the an error is emitted at 10th > > repeated run to export lyx16x. > > > > If two consecutive created lyx-files are identical, the test