Build failed in Jenkins: Support and maintenance jobs » Check-author-email-in-commit-log #48

https://ci.inria.fr/lyx/job/support/job/Check-author-email-in-commit-log/48/Changes: [spitz] Fix child document regex in scanLogFile [spitz] tex2lyx: normalize bib and bst paths [milde] lyx2lyx fixes and cleanup. [forenr] Avoid an infinite loop [sanda] Cosmetics per JMarc's suggestions.

Re: LyX version 2.3.0rc2 available

On Thu, Feb 01, 2018 at 01:58:54PM +, Joel Kulesza wrote: > I would include the link to the mirror listing. Otherwise, I can imagine > frustration of having a slow/failed download causing me to then go hunt for > a better alternative on the website (for a new user, who may not be totally >

Re: [LyX/master] Unify graphics-groups inside marked block functionality.

On 02/15/2018 05:52 AM, Pavel Sanda wrote: > Pavel Sanda wrote: >> commit b88ed81e7f1d2f59bb606351d95e093380b4eead >> Author: Pavel Sanda >> Date: Thu Feb 8 21:33:37 2018 +0100 >> >> Unify graphics-groups inside marked block functionality. >> >> Fixes #11026. >

Re: integral upper limit adjacent to integral sign

Pavel Sanda wrote: > Jean-Marc Lasgouttes wrote: > > Le 15 février 2018 16:32:23 GMT+01:00, Jean-Marc Lasgouttes > > a écrit : > > > > >>I can try to prepare that. What character you want me to paste there? > > >>I can't take 'f' from esint, there is no 'f' included. Pavel >

Re: integral upper limit adjacent to integral sign

Jean-Marc Lasgouttes wrote: > Le 15 février 2018 16:32:23 GMT+01:00, Jean-Marc Lasgouttes > a écrit : > > >>I can try to prepare that. What character you want me to paste there? > >>I can't take 'f' from esint, there is no 'f' included. Pavel > > > >The integral at position

Re: integral upper limit adjacent to integral sign

Le 15 février 2018 16:32:23 GMT+01:00, Jean-Marc Lasgouttes a écrit : >>I can try to prepare that. What character you want me to paste there? >>I can't take 'f' from esint, there is no 'f' included. Pavel > >The integral at position 1. And glyph number 4, I think. JMarc

Re: integral upper limit adjacent to integral sign

Le 15 février 2018 16:23:16 GMT+01:00, Pavel Sanda a écrit : >Jean-Marc Lasgouttes wrote: >> Le 15/02/2018 ?? 16:13, Pavel Sanda a écrit : >>> So what about copy-paste esint(f) into DejaVuSerif-Italic via >fontforge >>> and check what happens. >>> If there is some metainfo set

Re: integral upper limit adjacent to integral sign

Jean-Marc Lasgouttes wrote: > Le 15/02/2018 ?? 16:13, Pavel Sanda a écrit : >> So what about copy-paste esint(f) into DejaVuSerif-Italic via fontforge >> and check what happens. >> If there is some metainfo set wrong we could use Dejavu as a skeleton >> and copy our symbols there... > > I never

Re: integral upper limit adjacent to integral sign

Le 15/02/2018 à 16:13, Pavel Sanda a écrit : So what about copy-paste esint(f) into DejaVuSerif-Italic via fontforge and check what happens. If there is some metainfo set wrong we could use Dejavu as a skeleton and copy our symbols there... I never used fontforge to modify a font... JMarc

Re: integral upper limit adjacent to integral sign

Jean-Marc Lasgouttes wrote: > Le 14/02/2018 ?? 17:11, Pavel Sanda a écrit : >> 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 >>

Re: integral upper limit adjacent to integral sign

Le 14/02/2018 à 17:11, Pavel Sanda a écrit : 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

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: Staging Branches

Jean-Marc Lasgouttes 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

Re: Staging Branches

Le 14/02/2018 à 18:54, Richard Heck a écrit : 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

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

Le 15/02/2018 à 11:29, Jean-Marc Lasgouttes a écrit : Pavel is supposed to push his original work on 2.3.1. I am waiting to see whether this happens. Everything is in place now. JMarc

Re: [LyX/master] Unify graphics-groups inside marked block functionality.

Pavel Sanda wrote: > commit b88ed81e7f1d2f59bb606351d95e093380b4eead > Author: Pavel Sanda > Date: Thu Feb 8 21:33:37 2018 +0100 > > Unify graphics-groups inside marked block functionality. > > Fixes #11026. Richard, can this go to 2.3.2? P > >

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

Le 14/02/2018 à 16:13, Richard Heck a écrit : 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

Re: Staging Branches

Pavel Sanda wrote: > Richard Heck wrote: > > If we don't need to do anything > > super-fast, then I'll just merge 2.3.2-staging into 2.3.1-staging. > > I see, sounds good. Pavel When I think more about it though, if *getting the branch tested* from other devs is important goal of yours, then the

Re: Basque translation

I??aki Larra??aga Murgoitio wrote: > > (*): > > "Property" > > "Solution" > > "Listing" > > "Listings" > > "List of Listings" > > "see equation[[nomencl]]" > > "page[[nomencl]]" > > > > > Are those new messages into PO file? Anyway, let me translate them to basque > for you: (english : basque)

Re: Staging Branches

Richard Heck wrote: > If we don't need to do anything > super-fast, then I'll just merge 2.3.2-staging into 2.3.1-staging. I see, sounds good. Pavel