Re: Basic test of alpha1 tar

Am Sonntag 15 November 2015, 14:44:40 schrieb Kornel Benko: > Cmake build: Using '-DLYX_MERGE_FILES=ON' I get this error: > > [ 46%] Building CXX object > src/support/CMakeFiles/support.dir/_allinone_const.C.o cd > /usr/BUILD/BuildLyxGitQtlocal/src/support && /usr/bin/c++ >

Re: Basic test of alpha1 tar

Am Sonntag 15 November 2015, 16:16:35 schrieb Kornel Benko: > It does, in this case. But as the compilation proceeds, I get lot of errors > and warnings. Is the attached too big for list? That's at least definitely too much for my agenda. Let's see first if we can get monolithic build working

Re: Basic test of alpha1 tar

Am Sonntag, 15. November 2015 um 14:30:21, schrieb Jürgen Spitzmüller > Am Samstag 14 November 2015, 21:34:43 schrieb Scott Kostyshak: > > On Sat, Nov 14, 2015 at 04:31:55PM -0800, Pavel Sanda wrote: > > > Scott Kostyshak wrote: > > > > Dear all, > > > > > > > > If you have time,

Re: Basic test of alpha1 tar

Le 15/11/2015 01:18, Pavel Sanda a écrit : Scott Kostyshak wrote: Dear all, If you have time, please download the LyX 2.2.0alpha1 tar and test that it compiles/installs as expected. It is located here: non harmful, but warnings: GuiViewSource.cpp:174:9: warning: 'QString

Re: [patch] RFC: better submenu for tables

Am Sonntag, 15. November 2015 um 13:36:50, schrieb Jürgen Spitzmüller > Am Freitag 13 November 2015, 13:15:05 schrieb Kornel Benko: > > What about multipage table? > > Yes, why not. There are 5 strings which would need new wordings: 1 " long table" 2

Re: [patch] RFC: better submenu for tables

Am Sonntag 15 November 2015, 14:10:07 schrieb Kornel Benko: > Am Sonntag, 15. November 2015 um 13:36:50, schrieb Jürgen Spitzmüller > > > Am Freitag 13 November 2015, 13:15:05 schrieb Kornel Benko: > > > What about multipage table? > > > > Yes, why not. > > There are 5

Re: Basic test of alpha1 tar

Am Samstag 14 November 2015, 21:34:43 schrieb Scott Kostyshak: > On Sat, Nov 14, 2015 at 04:31:55PM -0800, Pavel Sanda wrote: > > Scott Kostyshak wrote: > > > Dear all, > > > > > > If you have time, please download the LyX 2.2.0alpha1 tar and test that > > > > > it compiles/installs as expected.

Re: [patch] RFC: better submenu for tables

Am Freitag 13 November 2015, 13:15:05 schrieb Kornel Benko: > What about multipage table? Yes, why not. Jürgen

Re: We now include both png and svgz?

On Sun, Nov 15, 2015 at 05:59:38PM +0100, Jean-Marc Lasgouttes wrote: > Le 15/11/2015 17:57, Georg Baum a écrit : > >OK, if it is assumed that qt can show svg images, then it does not make > >sense to ship or own .pngs. If we want to stick with this, we should remove > >the .pngs now and require

Re: Basic test of alpha1 tar

Jean-Marc Lasgouttes wrote: > And how does this compare to a 2.1 build? 2.1 seems to be the same as 2.0. > Could you provide a profile log for 2.2 being slow? Not now, but i will try get to it, it's pretty annoying. BTW my defaults are: xset r rate 300 180 maybe you can see it with this

Re: Basic test of alpha1 tar

Scott Kostyshak wrote: > Same Qt version? Yes, 4.8.5. P

Re: Basic test of alpha1 tar

Jürgen Spitzmüller wrote: > This probably points to > http://www.lyx.org/trac/changeset/7f1d33efc1d0b4302875706ba85d42c2a8f35a67/lyxgit/ > > Please try the attached patch. Yep, this fixes it. Pavel

Re: master branch is open again

On Sun, Nov 15, 2015 at 12:18:28PM -0500, Richard Heck wrote: > On 11/15/2015 12:05 PM, Jean-Marc Lasgouttes wrote: > > Le 14/11/2015 05:13, Scott Kostyshak a écrit : >> I have tagged and tarred > > (and signed) alpha1. I will upload the > tarballs >> soon. >> >> Development is open for

Re: [LyX/master] Fix 480937a103708a651/lyxgit. See also #9740.

On 2015-11-12, Kornel Benko wrote: > The actual failed export tests. > 117 failed, that is 9 less than previously. We are advancing. > 309:export/doc/EmbeddedObjects_pdf4_systemF Example of "high bit" chars in listings. Fails with XeTeX due ot limiation to ASCII (no LICR in listings

Re: Basic test of alpha1 tar

Le 15/11/2015 03:14, Pavel Sanda a écrit : Pavel Sanda wrote: non harmful, but warnings: Apart from that I was able to build and run it on gentoo system. Sadly, moving cursor in paragraph is considerably slower than in my current 2.0 build :( And how does this compare to a 2.1 build?

Re: master branch is open again

Le 14/11/2015 05:13, Scott Kostyshak a écrit : I have tagged and tarred (and signed) alpha1. I will upload the tarballs soon. Development is open for post-alpha commits. So can we just commit as we see fit, or would you like stuff to go to mailing list first? First example would be the

Re: Basic test of alpha1 tar

Works fine here (Debian jessie). Georg

Re: master branch is open again

On 11/15/2015 12:05 PM, Jean-Marc Lasgouttes wrote: > Le 14/11/2015 05:13, Scott Kostyshak a écrit : >> I have tagged and tarred > (and signed) alpha1. I will upload the tarballs >> soon. >> >> Development is open for post-alpha commits. > > So can we just commit as we see fit, or would you like

Re: synchronizing po file of branch and trunk

Am Sonntag, 15. November 2015 um 19:03:01, schrieb Georg Baum > Kornel Benko wrote: > > > Am Freitag, 13. November 2015 um 20:18:46, schrieb Georg Baum > > > >> > >> I am tempted to write our own merge tool in python.. > > > > I

Re: We now include both png and svgz?

Enrico Forestieri wrote: > It is not intended to work that way. If the svgz image is there, it is > not expected that Qt is not able to show it. The double entry are there > only to assure that if there is no svgz then the png can be used instead. > In this way, you are able to override the

Re: We now include both png and svgz?

Le 15/11/2015 17:57, Georg Baum a écrit : OK, if it is assumed that qt can show svg images, then it does not make sense to ship or own .pngs. If we want to stick with this, we should remove the .pngs now and require qtsvg at configure time. For me personally the svgs work fine both with qt 4.8

Re: synchronizing po file of branch and trunk

Kornel Benko wrote: > Am Freitag, 13. November 2015 um 20:18:46, schrieb Georg Baum > >> >> I am tempted to write our own merge tool in python.. > > I have a script ready, though it is perl. Nice, but a pity that it is not python;-( Many years ago it was decided