Re: We now include both png and svgz?

2015-11-10 Thread Scott Kostyshak
On Tue, Nov 10, 2015 at 06:42:50PM -0800, Pavel Sanda wrote: > Scott Kostyshak wrote: > > > At the moment you cannot use LyX with Qt4 because it cannot read svgz > > > files, and the code is not correctly falling back to png files. > > > > > > So yes, we need both, otherwise we will have to requir

Re: We now include both png and svgz?

2015-11-10 Thread Pavel Sanda
Scott Kostyshak wrote: > > At the moment you cannot use LyX with Qt4 because it cannot read svgz > > files, and the code is not correctly falling back to png files. > > > > So yes, we need both, otherwise we will have to require newer versions of > > Qt. > > I see. Makes sense. I will set a note

[patch] RFC: better submenu for tables

2015-11-10 Thread Uwe Stöhr
Am 04.11.2015 um 10:42 schrieb Jean-Marc Lasgouttes: This is not how contextual menus are supposed to work IMO. I would propose instead to use submenus and to micmick what libreoffice (for ex.) does. I agree that submenus are better than to remove things. Attached is a patch. OK to go in? ---

Re: [patch] proof of concept for bug 9744: allow parallel configuration of TeX and non-TeX fonts

2015-11-10 Thread Scott Kostyshak
On Tue, Nov 10, 2015 at 04:17:36PM +, Guenter Milde wrote: > I want to be able to prepare a document that works with many output > formats (one source fits all). One more use-case: template > documents with sensible settings for the various export formats. +1 > However, the most problematic

Re: Plan for the current testing situation

2015-11-10 Thread Scott Kostyshak
On Tue, Nov 10, 2015 at 03:30:24PM +, Guenter Milde wrote: > On 2015-11-10, Scott Kostyshak wrote: > > On Mon, Nov 09, 2015 at 11:19:16AM +0100, Vincent van Ravesteijn wrote: > >> And yes of course there is an implicit rule that when your commit breaks > >> something or has problems whatsoever

Re: No patch file for the major release, right?

2015-11-10 Thread Scott Kostyshak
On Tue, Nov 10, 2015 at 10:02:59AM +0100, Jean-Marc Lasgouttes wrote: > Le 10/11/2015 04:15, Scott Kostyshak a écrit : > >I just want to confirm that we only publish patch files for minor > >releases and not for major releases. Is that correct? > > Yes, it is correct. Thanks. Scott

Re: We now include both png and svgz?

2015-11-10 Thread Scott Kostyshak
On Tue, Nov 10, 2015 at 10:02:15AM +0100, Vincent van Ravesteijn wrote: > On Tue, Nov 10, 2015 at 4:13 AM, Scott Kostyshak wrote: > > When experimenting with building the tar balls, I noticed a significant > > difference in size between 2.2.0dev and 2.1.4. > > > > lyx-2.1.4.tar.gz is 20.8 MB > > l

Re: [patch] support for OpenDocument as input format for Pandoc

2015-11-10 Thread Scott Kostyshak
On Wed, Nov 11, 2015 at 12:52:53AM +0100, Uwe Stöhr wrote: > Attached is a simple patch that adds support for OpenDocument text as input > format for conversion to LaTeX via Pandoc. > > Pandoc recently made great progress: > http://pandoc.org/releases.html > > It supports now to use OpenDocument.

Re: docs with \origin unavailable

2015-11-10 Thread Scott Kostyshak
On Tue, Nov 10, 2015 at 08:43:56PM +0100, Georg Baum wrote: > Hi, > > we have currently several documents with > > \origin unavailable > > instead of > > \origin /systemlyxdir/doc/ > > in master (because of bug 9815). I suggest to save all these files with > correct \origin for the alpha, eve

[patch] support for OpenDocument as input format for Pandoc

2015-11-10 Thread Uwe Stöhr
Attached is a simple patch that adds support for OpenDocument text as input format for conversion to LaTeX via Pandoc. Pandoc recently made great progress: http://pandoc.org/releases.html It supports now to use OpenDocument. With the attached patch it is possible to use this feature. Especiall

Re: export test status (was: [LyX/master] Store both sets of font selections)

2015-11-10 Thread Guenter Milde
On 2015-11-10, Guenter Milde wrote: > On 2015-11-09, Kornel Benko wrote: > This is XeTeX with TeX fonts. > It currently always fails because the encoding after footnotes, tables, > boxes, and some other insets is set to the document language default. I > suggest to take these somehow out of calcu

docs with \origin unavailable

2015-11-10 Thread Georg Baum
Hi, we have currently several documents with \origin unavailable instead of \origin /systemlyxdir/doc/ in master (because of bug 9815). I suggest to save all these files with correct \origin for the alpha, even if there are still problems with 9815. It is probably also a good idea to update

Re: [LyX/master] Reset encoding after insets and environments also for LuaTeX with TeX fonts.

2015-11-10 Thread Kornel Benko
Am Dienstag, 10. November 2015 um 13:36:24, schrieb Guenter Milde ... > >> For LuaTeX + TeX-fonts, only "auto" needs to be changed. Preferably to > >> the document languages default encoding, but any 8-bit encoding or > >> ascii will do. > > > This I am omitting for now. > > You could try wit

Re: [LyX/master] Reset encoding after insets and environments also for LuaTeX with TeX fonts.

2015-11-10 Thread Guenter Milde
On 2015-11-10, Kornel Benko wrote: > Am Dienstag, 10. November 2015 um 10:50:30, schrieb Guenter Milde > >> Mind, that changing the inputencoding is only seldom tested and can >> exhibit a number of currently hidden problems. For example, the Russian >> documents fail with inputenc==ascii due to

Re: [patch] proof of concept for bug 9744: allow parallel configuration of TeX and non-TeX fonts

2015-11-10 Thread Guenter Milde
Dear Georg, On 2015-11-08, Georg Baum wrote: Thanks for the patch with parallel config values for tex and non-tex fonts. > The next step for the tests would then be to explicitly set sensible non-TeX > fonts for those files of our documentation that have special requirements, > so that we can ge

Re: Plan for the current testing situation

2015-11-10 Thread Guenter Milde
On 2015-11-10, Scott Kostyshak wrote: > On Mon, Nov 09, 2015 at 11:19:16AM +0100, Vincent van Ravesteijn wrote: >> >> So my preferred policy would be: >> if a >> >> commit is found to have broken a test, either the situation is resolved >> within >> >> a day (i.e. the bug is fixed or the test is f

Re: [LyX/master] Reset encoding after insets and environments also for LuaTeX with TeX fonts.

2015-11-10 Thread Guenter Milde
On 2015-11-10, Kornel Benko wrote: > Am Dienstag, 10. November 2015 um 10:50:30, schrieb Guenter Milde > >> On 2015-11-10, Kornel Benko wrote: >> > Am Dienstag, 10. November 2015 um 07:34:42, schrieb Guenter Milde >> > >> for a safe handling of XeTeX + TeX-fonts without hacks in the LyX code,

Re: [LyX/master] Reset encoding after insets and environments also for LuaTeX with TeX fonts.

2015-11-10 Thread Kornel Benko
Am Dienstag, 10. November 2015 um 10:50:30, schrieb Guenter Milde > Mind, that changing the inputencoding is only seldom tested and can > exhibit a number of currently hidden problems. For example, the Russian > documents fail with inputenc==ascii due to #9637 (textgreek and textcyr > depend on

Re: [LyX/master] Reset encoding after insets and environments also for LuaTeX with TeX fonts.

2015-11-10 Thread Kornel Benko
Am Dienstag, 10. November 2015 um 10:50:30, schrieb Guenter Milde > On 2015-11-10, Kornel Benko wrote: > > Am Dienstag, 10. November 2015 um 07:34:42, schrieb Guenter Milde > > > > Dear Kornel, > > for a safe handling of XeTeX + TeX-fonts without hacks in the LyX code, I > recommend to allow

Re: [LyX/master] Reset encoding after insets and environments also for LuaTeX with TeX fonts.

2015-11-10 Thread Guenter Milde
On 2015-11-10, Kornel Benko wrote: > Am Dienstag, 10. November 2015 um 07:34:42, schrieb Guenter Milde > Dear Kornel, for a safe handling of XeTeX + TeX-fonts without hacks in the LyX code, I recommend to allow this combination only, if "inputenc" == "ascii". for a safe handling of LuaTeX + Te

beamer workflow

2015-11-10 Thread Edwin Leuven
dear all, when i insert a new frame, add the title and hit enter the new line is set to “Frame” similarly if i am editing the contents of my frame which is an indented standard environment enter gives me a new line set to “Frame” is it possible to have the environment default to “Standard" in

Re: [LyX/master] Reset encoding after insets and environments also for LuaTeX with TeX fonts.

2015-11-10 Thread Kornel Benko
Am Dienstag, 10. November 2015 um 07:34:42, schrieb Guenter Milde > Dear Kornel, dear LyXers, > > sorry, there were typos in my last post > (On 2015-11-09, Guenter Milde wrote ...). > > Trying again. > > On 2015-11-09, Kornel Benko wrote: > > > Am Montag, 9. November 2015 um 15:50:09, schrieb

Re: No patch file for the major release, right?

2015-11-10 Thread Jean-Marc Lasgouttes
Le 10/11/2015 04:15, Scott Kostyshak a écrit : I just want to confirm that we only publish patch files for minor releases and not for major releases. Is that correct? Yes, it is correct. JMarc

Re: We now include both png and svgz?

2015-11-10 Thread Vincent van Ravesteijn
On Tue, Nov 10, 2015 at 4:13 AM, Scott Kostyshak wrote: > When experimenting with building the tar balls, I noticed a significant > difference in size between 2.2.0dev and 2.1.4. > > lyx-2.1.4.tar.gz is 20.8 MB > lyx-2.2.0dev.tar.gz is 24.8 MB > > A quick check seems to show that most of the chang

Re: #8077: command-alternatives doesn't work with layout Chapter

2015-11-10 Thread Andrew Parsloe
On 10/11/2015 1:35 p.m., LyX Ticket Tracker wrote: #8077: command-alternatives doesn't work with layout Chapter +- Reporter: aparsloe| Owner: lasgouttes Type: defect | Status: new Priority: normal | Milest

export test status (was: [LyX/master] Store both sets of font selections)

2015-11-10 Thread Guenter Milde
On 2015-11-09, Kornel Benko wrote: >> I rerun the failed export tests (265), and all of sudden now only 16 >> of them did not pass. ... > It would have been so nice. But I was mocked (probably by myself). > We have now 260 failed export tests. > *.pdf4_texF: 139 This is XeTeX with TeX fonts.

Re: [patch] Finding the generated latex file

2015-11-10 Thread Guillaume Munch
Le 10/11/2015 01:08, Scott Kostyshak a écrit : On Mon, Nov 09, 2015 at 08:04:29AM +, Guillaume Munch wrote: Le 06/11/2015 10:35, Jean-Marc Lasgouttes a écrit : Le 06/11/2015 04:16, Scott Kostyshak a écrit : I also agree that it's better to replace the alert with a message on stderr. I noti