Re: lyx2lyx patch fixing ctests.

Am Mittwoch, 17. Januar 2018 um 18:12:03, schrieb Guenter Milde <mi...@users.sf.net> > Dear Docutils developers, dear Kornel, > > the follwing patch should fix some of the ctest failing due to the lyx2lyx > "Warning: This document contained both literal and "ligature

lyx2lyx patch fixing ctests.

Dear Docutils developers, dear Kornel, the follwing patch should fix some of the ctest failing due to the lyx2lyx "Warning: This document contained both literal and "ligature" dashes. Line breaks may have changed. See UserGuide chapter 3.9.1 for details." It is

Re: [PATCH] to avoid crash in misspelled marker painting while deleting table rows fast

On Fri, Oct 27, 2017 at 10:52:02AM +, Jean-Marc Lasgouttes wrote: > Le 13/10/2017 à 07:24, Stephan Witt a écrit : > > > A question: is the 'quickly' important to get the crash? From what I see, > > > Cursor::newWord() is not updated to the changes in the document > > > structure. Why does

Re: [patch] use https in in first line of LyX files

On Sun, Dec 17, 2017 at 12:37:08AM +, Uwe Stöhr wrote: > El 16.12.2017 a las 20:10, Scott Kostyshak escribió: > > > It's fine for 2.3.0. > > OK, I'll put it in. > > > Usually what I do when changing http to https is to > > check that the https link is indeed secure. > > This is what I did.

Re: [patch] use https in in first line of LyX files

s. I fear special cases in lyx2lyx or tex2lyx where I > might have missed a thing. Then they might not work correctly just because > if this. I played a bit around and it looks safe but one never knows and so > short before a release it seems too risky. As it is not that pressing I > wou

Re: [patch] use https in in first line of LyX files

because if this. I played a bit around and it looks safe but one never knows and so short before a release it seems too risky. As it is not that pressing I would postpone it. I committed the full patch to master and only the https support for tex2lyx to the 2.3.x branch. regards Uwe

Re: [patch] support for the paratype fonts

On 12/16/2017 07:40 PM, Uwe Stöhr wrote: > El 16.12.2017 a las 23:45, Richard Heck escribió: > >> I know it's late for a format change, but what about including this in >> 2.3.0? > > I am opposed to this because this would change strings. I mean the > user can simply add \usepackage{paratype} to

Re: [patch] support for the paratype fonts

El 16.12.2017 a las 23:45, Richard Heck escribió: I know it's late for a format change, but what about including this in 2.3.0? I am opposed to this because this would change strings. I mean the user can simply add \usepackage{paratype} to the preamble to use it for all fonts. I can also

Re: [patch] use https in in first line of LyX files

El 16.12.2017 a las 20:10, Scott Kostyshak escribió: It's fine for 2.3.0. OK, I'll put it in. Usually what I do when changing http to https is to check that the https link is indeed secure. This is what I did. if it is not secure I left it with http. While doing this I detected a lot of

Re: [patch] support for the paratype fonts

On 12/14/2017 06:15 PM, Uwe Stöhr wrote: > Yuriy asked if LyX could support the paratype fonts > https://ctan.org/pkg/paratype > to offer an outline font alternative for the computer modern fonts for > Cyrillic. > > This is in my opinion a good idea and so I created

Re: [patch] use https in in first line of LyX files

On Thu, Dec 14, 2017 at 02:22:13PM +, Uwe Stöhr wrote: > I think we should use https wherever possible: > https://www.lyx.org/trac/ticket/10945 > Attached is a patch that does this. > OK to go in? > > What about LyX 2.3, should we do this there as well or can this be done

Re: [patch] support for the paratype fonts

On Sat, Dec 16, 2017 at 05:06:41PM +, Uwe Stöhr wrote: > El 16.12.2017 a las 06:27, Pavel Sanda escribió: > > > I was about to ask the same, please don't break portability of files > > until 2.3 is out if possible. > > OK. > > By the way, why don't we release RC1 right now? Did I miss

Re: [patch] support for the paratype fonts

El 16.12.2017 a las 06:27, Pavel Sanda escribió: I was about to ask the same, please don't break portability of files until 2.3 is out if possible. OK. By the way, why don't we release RC1 right now? Did I miss something? thanks and regards Uwe

Re: [patch] support for the paratype fonts

Richard Heck wrote: > So I guess I'd suggest we wait to commit any format changes to master > until 2.3 is released. Any other thoughts? I was about to ask the same, please don't break portability of files until 2.3 is out if possible. Pavel

Re: [patch] support for the paratype fonts

On 12/14/2017 06:15 PM, Uwe Stöhr wrote: > Yuriy asked if LyX could support the paratype fonts > https://ctan.org/pkg/paratype > to offer an outline font alternative for the computer modern fonts for > Cyrillic. > > This is in my opinion a good idea and so I created

[patch] support for the paratype fonts

Yuriy asked if LyX could support the paratype fonts https://ctan.org/pkg/paratype to offer an outline font alternative for the computer modern fonts for Cyrillic. This is in my opinion a good idea and so I created the applied patch. This is a fileformat change. As it is the first fileformat

[patch] use https in in first line of LyX files

I think we should use https wherever possible: https://www.lyx.org/trac/ticket/10945 Attached is a patch that does this. OK to go in? What about LyX 2.3, should we do this there as well or can this be done for 2.3.1? In Buffer.cpp there are with the patch still 2 non-https links

[RFC] [PATCH] Fix configuration problems with python3 on the Mac

The attached patch fixes the rather nasty problems Joel Kulesza reported at http://www.lyx.org/trac/ticket/10671 (configure failed for him on the Mac when LyX was launched from the finder or icon as opposed to the terminal). It turned out in the given case configure opened files (with open

Re: PATCH for 2.3, use frescobaldi as preferred editor for lilypond material

ary +1, but I guess I feel like >>>>>> Scott should probably chime in on this. >>>>> Thanks, yes, for feature patches I like to be involved. >>>>> >>>>> This feature is fine with me, so since Richard +1'd it, go ahead for >>>>&g

Re: PATCH for 2.3, use frescobaldi as preferred editor for lilypond material

probably chime in on this. > >>> Thanks, yes, for feature patches I like to be involved. > >>> > >>> This feature is fine with me, so since Richard +1'd it, go ahead for > >>> 2.3.0. Thanks for the patch, Helge. > >> Helge or Richard, please commit as

Re: PATCH for 2.3, use frescobaldi as preferred editor for lilypond material

gt;>> This feature is fine with me, so since Richard +1'd it, go ahead for >>> 2.3.0. Thanks for the patch, Helge. >> Helge or Richard, please commit as soon as possible if you would like >> this in 2.3.0rc1. > I committed to master at c4b4305f and to 2.3.x

Re: [PATCH] to avoid crash in misspelled marker painting while deleting table rows fast

Le 13/10/2017 à 07:24, Stephan Witt a écrit : A question: is the 'quickly' important to get the crash? From what I see, Cursor::newWord() is not updated to the changes in the document structure. Why does this happen? Sorry for the delay. I tried to reproduce and cannot anymore ATM. I had the

Re: PATCH for 2.3, use frescobaldi as preferred editor for lilypond material

t for > > > 2.3.x myself, so I'd give it the necessary +1, but I guess I feel like > > > Scott should probably chime in on this. > > > > Thanks, yes, for feature patches I like to be involved. > > > > This feature is fine with me, so since Richard +1'd i

Re: [PATCH] to avoid crash in misspelled marker painting while deleting table rows fast

On Wed, Oct 25, 2017 at 05:26:25PM +, Scott Kostyshak wrote: > What shall we do with this regarding rc1? If for some reason we do not > put in Stephan's patch, can we at least put in some debug code or an > assert or something to help us make progress on this in the future?

Re: PATCH for 2.3, use frescobaldi as preferred editor for lilypond material

e > > Scott should probably chime in on this. > > Thanks, yes, for feature patches I like to be involved. > > This feature is fine with me, so since Richard +1'd it, go ahead for > 2.3.0. Thanks for the patch, Helge. Helge or Richard, please commit as soon as possible if

Re: [PATCH] to avoid crash in misspelled marker painting while deleting table rows fast

ple rows from a table with > >> bottom table toolbar quickly. > >> This happened with LyX 2.2. - I can reproduce it with master. > >> I’m attaching the crash report and a patch to avoid the crash. I’d like to > >> put it in and if possible backport it to 2.3.x at

Re: PATCH for 2.3, use frescobaldi as preferred editor for lilypond material

es I like to be involved. This feature is fine with me, so since Richard +1'd it, go ahead for 2.3.0. Thanks for the patch, Helge. I have two comments: 1. Note that there are three different case styles: "Lilypond files", "lilypond editor", "LilyPond music". Perhaps tha

Re: PATCH for 2.3, use frescobaldi as preferred editor for lilypond material

to the text view. This makes it easier to > work with lilypond music. Frescobaldi exists on linux, mac and > windows, and is popular for working with lilypond. > > So this patch specifies frescobaldi as the preferred editor for > lilypond files. If it is not present, the usual

PATCH for 2.3, use frescobaldi as preferred editor for lilypond material

music. Frescobaldi exists on linux, mac and windows, and is popular for working with lilypond. So this patch specifies frescobaldi as the preferred editor for lilypond files. If it is not present, the usual text editors are fallback alternatives. I have compiled, installed, and tested that LyX

Re: [PATCH] to avoid crash in misspelled marker painting while deleting table rows fast

ened with LyX 2.2. - I can reproduce it with master. >> I’m attaching the crash report and a patch to avoid the crash. I’d like to >> put it in and if possible backport it to 2.3.x at least. Ok? > > A question: is the 'quickly' important to get the crash? From what I see, > Cursor

Re: [PATCH] to avoid crash in misspelled marker painting while deleting table rows fast

Le 08/10/2017 à 18:01, Stephan Witt a écrit : Hi, these days I’ve got a crash while deleting multiple rows from a table with bottom table toolbar quickly. This happened with LyX 2.2. - I can reproduce it with master. I’m attaching the crash report and a patch to avoid the crash. I’d like

[PATCH] to avoid crash in misspelled marker painting while deleting table rows fast

Hi, these days I’ve got a crash while deleting multiple rows from a table with bottom table toolbar quickly. This happened with LyX 2.2. - I can reproduce it with master. I’m attaching the crash report and a patch to avoid the crash. I’d like to put it in and if possible backport it to 2.3.x

Re: dash documentation patch

On Sat, Sep 02, 2017 at 09:19:50PM +, Guenter Milde wrote: > On 2017-09-02, Scott Kostyshak wrote: > > In the RELEASE-NOTES file, we could reference > > https://wiki.lyx.org/LyX/ReleaseNotes for release notes relating to > > previous versions of LyX. Actually, I need to update that Wiki page.

Re: fix lyx2lyx dash conversion (patch attached)

On Sat, Sep 30, 2017 at 10:12:28PM +, Guenter Milde wrote: > The patch allows removal of all dash-related caveats in the 2.3 RELEASE NOTES. > > Please try it out and give a +1 or improvement suggestions. (to any potential patch reviewers) In case anyone is concerned about a regres

fix lyx2lyx dash conversion (patch attached)

Dear LyX developers, the attached patch cleans up lyx2lyx issues after the recent fixes to dash handling in LyX. Commiting requires the +1 from at least one other developer. * Backwards compatibility for both, documents containing literal dashes and documents containing ligature dashes

fix lyx2lyx dash conversion (patch)

Dear LyX developers, the attached patch cleans up lyx2lyx issues after the recent fixes to dash handling in LyX. Commiting requires the +1 from at least one other developer. * Backwards compatibility for both, documents containing literal dashes and documents containing ligature dashes

Re: [PATCH] How to setup image converters on Mac?

On Thu, Sep 28, 2017 at 07:30:45AM +, Enrico Forestieri wrote: > On Wed, Sep 27, 2017 at 10:34:20PM +0200, Stephan Witt wrote: > > > > Ok, here is my next proposed patch. Now lyxconvert should be compiled > > and installed on Mac only, in convertDefault.py a test fo

Re: [PATCH] How to setup image converters on Mac?

On Wed, Sep 27, 2017 at 10:34:20PM +0200, Stephan Witt wrote: > > Ok, here is my next proposed patch. Now lyxconvert should be compiled > and installed on Mac only, in convertDefault.py a test for platform > darwin is active to ensure it is called on Mac only. > > This s

Re: [PATCH] How to setup image converters on Mac?

>> >> I agree. > > Whatever you all agree on for 2.3.x is fine in my opinion. Thanks for > all of your work on this issue. Ok, here is my next proposed patch. Now lyxconvert should be compiled and installed on Mac only, in convertDefault.py a test for platform darwin is active

Re: [PATCH] How to setup image converters on Mac?

On Tue, Sep 26, 2017 at 09:32:34PM +, Enrico Forestieri wrote: > > What do you think? IMO, the benefit on Mac is enough to take the risk. > > That’s not true for the other platforms. > > I agree. Whatever you all agree on for 2.3.x is fine in my opinion. Thanks for all of your work on this

Re: [PATCH] How to setup image converters on Mac?

On Tue, Sep 26, 2017 at 11:07:00PM +0200, Stephan Witt wrote: > Am 26.09.2017 um 21:10 schrieb Enrico Forestieri : > > > > On Mon, Sep 25, 2017 at 11:38:05PM +0200, Stephan Witt wrote: > >> Am 25.09.2017 um 23:23 schrieb Enrico Forestieri : > >>> > >>> There are a

Re: [PATCH] How to setup image converters on Mac?

Am 26.09.2017 um 21:10 schrieb Enrico Forestieri : > > On Mon, Sep 25, 2017 at 11:38:05PM +0200, Stephan Witt wrote: >> Am 25.09.2017 um 23:23 schrieb Enrico Forestieri : >>> >>> There are a few icons with empty text, but there are also all the ipa icons >>> that

Re: [PATCH] How to setup image converters on Mac?

On Mon, Sep 25, 2017 at 11:38:05PM +0200, Stephan Witt wrote: > Am 25.09.2017 um 23:23 schrieb Enrico Forestieri : > > > > There are a few icons with empty text, but there are also all the ipa icons > > that contain text. These texts should be changed to paths, otherwise they > >

Re: [PATCH] How to setup image converters on Mac?

ork on platforms not being Linux. >> On Mac I have to fool the QFontDatabase class by creating an empty directory >> Contents/lib/fonts in the application bundle. On X11-Linux it should work. >> But Cygwin and Windows… I have no idea how it goes. >> >> Please, try the update

Re: [PATCH] How to setup image converters on Mac?

But Cygwin and Windows… I have no idea how it goes. > > Please, try the updated patch attached if possible. Thanks. It works on Cygwin. But I don't know whether the offscreen plugins is to be expected on native Windows because it relies on the freetype library. Maybe the available plugins c

Re: [PATCH] How to setup image converters on Mac?

logical cases > may occur, as demonstrated. You’re right. Meanwhile I found the relevant bug https://bugreports.qt.io/browse/QTBUG-31990 We may cleanup our icons. Unfortunately we cannot guarantee the fallback converter is not used by some arbitrary SVG image and crashes. I tried to pas

Re: [PATCH] How to setup image converters on Mac?

Am Montag, 25. September 2017 um 16:12:08, schrieb Stephan Witt > Am 25.09.2017 um 15:00 schrieb Kornel Benko : > > > > Am Montag, 25. September 2017 um 14:33:04, schrieb Enrico Forestieri > > > >> On Mon, Sep 25, 2017 at 09:31:45AM +0200,

Re: [PATCH] How to setup image converters on Mac?

On Mon, Sep 25, 2017 at 03:13:18PM +0200, Stephan Witt wrote: > Am 25.09.2017 um 14:15 schrieb Enrico Forestieri : > > > > On Mon, Sep 25, 2017 at 09:17:41AM +0200, Stephan Witt wrote: > >> > >> Oh no. I did some further testing and now I’m feeling blue. > >> > >> Not all SVG

Re: [PATCH] How to setup image converters on Mac?

Am 25.09.2017 um 15:00 schrieb Kornel Benko : > > Am Montag, 25. September 2017 um 14:33:04, schrieb Enrico Forestieri > >> On Mon, Sep 25, 2017 at 09:31:45AM +0200, Jean-Marc Lasgouttes wrote: >>> Le 25/09/2017 à 08:26, Stephan Witt a écrit : Now I wonder

Re: [PATCH] How to setup image converters on Mac?

Am 25.09.2017 um 14:15 schrieb Enrico Forestieri : > > On Mon, Sep 25, 2017 at 09:17:41AM +0200, Stephan Witt wrote: >> >> Oh no. I did some further testing and now I’m feeling blue. >> >> Not all SVG images we provide can be converted this way. >> >> $

Re: [PATCH] How to setup image converters on Mac?

Am Montag, 25. September 2017 um 14:33:04, schrieb Enrico Forestieri > On Mon, Sep 25, 2017 at 09:31:45AM +0200, Jean-Marc Lasgouttes wrote: > > Le 25/09/2017 à 08:26, Stephan Witt a écrit : > > > Now I wonder if it would be better to name the utility lyxconvert. > > > It will be

Re: [PATCH] How to setup image converters on Mac?

On Mon, Sep 25, 2017 at 09:31:45AM +0200, Jean-Marc Lasgouttes wrote: > Le 25/09/2017 à 08:26, Stephan Witt a écrit : > > Now I wonder if it would be better to name the utility lyxconvert. > > It will be installed in /usr/local/bin or something like that? > > I was about to suggest this. And then

Re: [PATCH] How to setup image converters on Mac?

On Mon, Sep 25, 2017 at 09:17:41AM +0200, Stephan Witt wrote: > > Oh no. I did some further testing and now I’m feeling blue. > > Not all SVG images we provide can be converted this way. > > $ lyx-build/LyX-2.4.0dev.app/Contents/MacOS/lyxconvert -d > lyx/lib/images/math-subscript.svgz

Re: [PATCH] How to setup image converters on Mac?

Le 25/09/2017 à 10:57, Stephan Witt a écrit : Am 25.09.2017 um 09:31 schrieb Jean-Marc Lasgouttes : Le 25/09/2017 à 08:26, Stephan Witt a écrit : Now I wonder if it would be better to name the utility lyxconvert. It will be installed in /usr/local/bin or something like

Re: [PATCH] How to setup image converters on Mac?

Am 25.09.2017 um 09:31 schrieb Jean-Marc Lasgouttes : > > Le 25/09/2017 à 08:26, Stephan Witt a écrit : >> Now I wonder if it would be better to name the utility lyxconvert. >> It will be installed in /usr/local/bin or something like that? > > I was about to suggest this. And

Re: [PATCH] How to setup image converters on Mac?

Le 25/09/2017 à 08:26, Stephan Witt a écrit : Now I wonder if it would be better to name the utility lyxconvert. It will be installed in /usr/local/bin or something like that? I was about to suggest this. And then do we want to honor version-suffix? I guess not, but we might end up installing

Re: [PATCH] How to setup image converters on Mac?

that. > > Thanks, Stephan, for the patch, and Enrico, for testing on Linux and > Cygwin. I think it is a good plan for 2.3.0. Stephan, I would say go > ahead and put it in the 2.3.x branch if you are comfortable with it. > > Scott Oh no. I did some further testing and now I’m fee

Re: [PATCH] How to setup image converters on Mac?

stalled the new imgconvert command is used. >>>> >>>> In this way, whatever conversion between image formats supported by Qt >>>> would succeed (without the need of new converter definitions). >>> >>> This is a good idea too. I have to admi

Re: [PATCH] How to setup image converters on Mac?

On Sun, Sep 24, 2017 at 11:39:09PM +0200, Enrico Forestieri wrote: > It works for me on linux and cygwin. Of course, one has to move away > convert, rsvg-convert, and inkscape to appreciate that. Thanks, Stephan, for the patch, and Enrico, for testing on Linux and Cygwin. I think it is

Re: [PATCH] How to setup image converters on Mac?

ne. However, I would avoid introducing 2 more converters > >> and instead I would modify convertDefault.py so that when imagemagick is > >> not installed the new imgconvert command is used. > >> > >> In this way, whatever conversion between image formats supported

Re: [PATCH] How to setup image converters on Mac?

rtDefault.py so that when imagemagick is >> not installed the new imgconvert command is used. >> >> In this way, whatever conversion between image formats supported by Qt >> would succeed (without the need of new converter definitions). > > This is a good idea

Re: [PATCH] How to setup image converters on Mac?

uld succeed (without the need of new converter definitions). This is a good idea too. I have to admit, I had scruple to do this. I’ll try to present a patch with this alternative. Stephan

Re: [PATCH] Re: How to setup image converters on Mac?

On Sun, Sep 24, 2017 at 12:24:26PM +0200, Stephan Witt wrote: > > This is the solution I’d like to propose. It’s not tested on Linux and > Windows. > > The idea is to add imgconvert as fallback-converter for SVG to PDF and PNG to > PDF. > At the moment it uses the Qt library routines for image

Re: [PATCH] Re: How to setup image converters on Mac?

Am 24.09.2017 um 12:24 schrieb Stephan Witt : > > Am 21.09.2017 um 15:08 schrieb Stephan Witt : >> >> Am 21.09.2017 um 14:54 schrieb Enrico Forestieri : >>> >>> On Thu, Sep 21, 2017 at 11:43:29AM +0200, Stephan Witt wrote: My question

[PATCH] Re: How to setup image converters on Mac?

Am 21.09.2017 um 15:08 schrieb Stephan Witt : > > Am 21.09.2017 um 14:54 schrieb Enrico Forestieri : >> >> On Thu, Sep 21, 2017 at 11:43:29AM +0200, Stephan Witt wrote: >>> >>> My question (again): how can I circumvent this and configure „my“ converter >>> so

Re: dash documentation patch

tead of just > > documenting them? > > Fine with me as long as you get a +1. Has anyone taken a look at the patch? Scott signature.asc Description: PGP signature

Re: dash documentation patch

now > > the conditions under which they might experience a caveat. > > > I don't really have a strong opinion on this, but I think a concise > > description of the conditions for a caveat, combined with a reference > > for further information, could be a reasonable compromise. &g

Re: dash documentation patch

On Wed, Sep 06, 2017 at 07:14:26PM +, Guenter Milde wrote: > On 2017-08-31, Guenter Milde wrote: > > Dear LyX developers, > > is there a chance to fix the following problems instead of just > documenting them? Fine with me as long as you get a +1. Scott signature.asc Description: PGP

Re: dash documentation patch

t;uncodable character" issues if the document is actually > loaded by that LyX version. LyX 2.1 and later versions already have the > necessary definition in their unicodesymbols file Export to 2.1 and older changes dashes from ligature to literal. Proposed changes (see

Re: dash documentation patch

reference > for further information, could be a reasonable compromise. Agreed. I will prepare a patch for review. Günter

Re: dash documentation patch

On Sat, Sep 02, 2017 at 09:19:50PM +, Guenter Milde wrote: > Dear Scott, dear Enrico, dear lyx developers, > > On 2017-09-02, Scott Kostyshak wrote: > > On Sat, Sep 02, 2017 at 12:34:05AM +0200, Enrico Forestieri wrote: > >> On Thu, Aug 31, 2017 at 08:53:41PM +, Guenter Milde wrote: > >

Re: dash documentation patch

Dear Scott, dear Enrico, dear lyx developers, On 2017-09-02, Scott Kostyshak wrote: > On Sat, Sep 02, 2017 at 12:34:05AM +0200, Enrico Forestieri wrote: >> On Thu, Aug 31, 2017 at 08:53:41PM +, Guenter Milde wrote: >> See above. Release notes should be used to illustrate current changes, not

Re: dash documentation patch

On Sat, Sep 02, 2017 at 12:34:05AM +0200, Enrico Forestieri wrote: > On Thu, Aug 31, 2017 at 08:53:41PM +, Guenter Milde wrote: > > This also one of the caveats then upgrading from earlier versions (which are > > not limited to upgrading from 2.2). > > See above. Release notes should be used

Re: dash documentation patch

On Thu, Aug 31, 2017 at 08:53:41PM +, Guenter Milde wrote: > On 2017-08-31, Enrico Forestieri wrote: > > On Wed, Aug 30, 2017 at 11:06:25PM +0200, Guenter Milde wrote: > > >> +* Since version 2.2, -- and --- in the LyX source are output as -{}- and > >> + -{}-{}- to prevent conversion to en-

Re: dash documentation patch

ecessary definition in their unicodesymbols file IMO, it is best to render both of them superfluous by not adding ZWSP in the back conversion and not removing it in the forward conversion. This also opens the way for true compatibility when exporting to 2.1 and older formats. See patc

Re: dash documentation patch

On Wed, Aug 30, 2017 at 11:06:25PM +0200, Guenter Milde wrote: > > +* Since version 2.2, -- and --- in the LyX source are output as -{}- and > + -{}-{}- to prevent conversion to en- and em-dashes by TeX. > + Occurences in pre-2.2 documents are converted to literal Unicode dashes. > + In some

Re: dash documentation patch

On 2017-08-31, Scott Kostyshak wrote: > On Wed, Aug 30, 2017 at 11:06:25PM +0200, Guenter Milde wrote: >> Dear LyX developers, >> The following patch brings RELEASE_NOTES and UserGuide up to the current >> state of dash handling in lyx. (The UserGuide was still at 2.1

Re: dash documentation patch

On Wed, Aug 30, 2017 at 11:06:25PM +0200, Guenter Milde wrote: > Dear LyX developers, > > The following patch brings RELEASE_NOTES and UserGuide up to the current > state of dash handling in lyx. (The UserGuide was still at 2.1 behaviour.) I get the following output: $

dash documentation patch

Dear LyX developers, The following patch brings RELEASE_NOTES and UserGuide up to the current state of dash handling in lyx. (The UserGuide was still at 2.1 behaviour.) Günter From 69a3f093bf2a2fb060e0f1bc4daf1cd6dc6c8754 Mon Sep 17 00:00:00 2001 From: @qšÑh <ÐѪŒV> Date: Tue, 29 Aug 2

Re: Patch documentation

On Wed, Aug 16, 2017 at 03:06:06PM +0930, racoon wrote: > Hi, > > I vaguely remember to have gotten a message from someone (Jürgen?) about > documenting my patches somewhere. Unfortunately, I cannot find that email > just now. > > How do I find what needs to be documented? I think you might be

Patch documentation

Hi, I vaguely remember to have gotten a message from someone (Jürgen?) about documenting my patches somewhere. Unfortunately, I cannot find that email just now. How do I find what needs to be documented? Best, Daniel

Re: [LyX/master] The shell escape patch

ate: Thu Aug 3 13:07:41 2017 +0200 > > > > The shell escape patch > > > > Probably forgotten emblem-shellescape.svgz? Yes, thanks for the reminder. -- Enrico

Re: [LyX/master] The shell escape patch

Am Donnerstag, 3. August 2017 um 13:08:04, schrieb Enrico Forestieri <for...@lyx.org> > commit f11bfe1697492f79f8cc02d4021305005cf539ef > Author: Enrico Forestieri <for...@lyx.org> > Date: Thu Aug 3 13:07:41 2017 +0200 > > The shell escape patch >

Re: [patch] update PDF viewers in configure.py

he name of > the executable is just "masterpdfeditor". The will discuss this. > So unless the name of the executable is not uniform on all OSes, I won't > support it. Thus I retract my patch. Fine. > I still think however that we should remove KPDF and KGhostscript. > Ho

Re: [patch] update PDF viewers in configure.py

nt version numbers. Moreover, on Windows the name of the executable is just "masterpdfeditor". The will discuss this. So unless the name of the executable is not uniform on all OSes, I won't support it. Thus I retract my patch. I still think however that we should remove KPDF and KGhostsc

Re: [patch] update PDF viewers in configure.py

On 31 July 2017 at 19:52, Pavel Sanda wrote: > Kornel Benko wrote: > > > It is not a demo. Only if you want to have all features like e.g. > > > splitting PDF pages one has to buy another version. So it is the same > as > > > with Acrobat Reader, for the full feature set of

Re: [patch] update PDF viewers in configure.py

Uwe Stöhr wrote: >> There's one certainty, regardless of the OS: no matter which order you >> specify, /someone/ is going to complain. ;-) > > Yes. So to avoid a discussion about it I have undone the sort order change > in the attached updated patch. Actually you did n

Re: [patch] update PDF viewers in configure.py

Kornel Benko wrote: > > It is not a demo. Only if you want to have all features like e.g. > > splitting PDF pages one has to buy another version. So it is the same as > > with Acrobat Reader, for the full feature set of Acrobat one has to pay. > > Do we really try to promote commercial

Re: [patch] update PDF viewers in configure.py

On 30 July 2017 at 23:47, Jean-Marc Lasgouttes wrote: > >Under Linux I was looking for a PDF program with which I can properly > >fill out and submit PDF forms. I found the Program Master PDF editor > >and > >would therefore like to support it in LyX. > > To be frank I never

Re: [patch] update PDF viewers in configure.py

On Mon, Jul 31, 2017 at 12:18:59AM +0200, Uwe Stöhr wrote: > El 30.07.2017 a las 23:47, Jean-Marc Lasgouttes escribió: > > > > would therefore like to support it in LyX. > > > > To be frank I never heard of it before today. It seems to be some > > commercial program which only can be found as

Re: [patch] update PDF viewers in configure.py

On Mon, Jul 31, 2017 at 01:22:48AM +0200, Uwe Stöhr wrote: > El 31.07.2017 a las 01:00, Paul A. Rubin escribió: > > > IIRC, the script cycles through the options and stops at the first > > match. (This is true on all operating systems, not just Linux.) If, for > > example, Evince precedes Xreader

Re: [patch] update PDF viewers in configure.py

On Sun, Jul 30, 2017 at 07:00:44PM -0400, Paul A. Rubin wrote: > I could make an argument for putting choices not normally > installed ahead of the ones packaged with the operating system (call that > one the system default), on the theory that if the user installed something > other than the

Re: [patch] update PDF viewers in configure.py

Am Montag, 31. Juli 2017 um 00:18:59, schrieb Uwe Stöhr > El 30.07.2017 a las 23:47, Jean-Marc Lasgouttes escribió: > > >> would therefore like to support it in LyX. > > > > To be frank I never heard of it before today. It seems to be some > > commercial program which only

Re: [patch] update PDF viewers in configure.py

there is a way to determine this? Maybe our pyhtonists have an idea? There's one certainty, regardless of the OS: no matter which order you specify, /someone/ is going to complain. ;-) Yes. So to avoid a discussion about it I have undone the sort order change in the attached updated patch. regards

Re: [patch] update PDF viewers in configure.py

On 07/30/2017 06:26 PM, Uwe Stöhr wrote: Okular -> qpdfview -> Evince means 2 Qt programs before the first GTK program. I noticed that on popular distros (Mint, Ubuntu, Fedora) Evince is the default viewer. Still true for Fedora and Ubuntu (I think); on Mint, the default viewer is now

Re: [patch] update PDF viewers in configure.py

El 30.07.2017 a las 22:10, Stephan Witt escribió: You didn’t mention the change to remove xreader. Did you remove it accidentally? Oops, sorry. Attached is the correct patch where this is not removed. Why did you change the order of tested programs? Okular -> qpdfview -> Evince mean

Re: [patch] update PDF viewers in configure.py

El 30.07.2017 a las 23:47, Jean-Marc Lasgouttes escribió: would therefore like to support it in LyX. To be frank I never heard of it before today. It seems to be some commercial program which only can be found as demo. I am not very fond of promoting such things. It is not a demo. Only if

Re: [patch] update PDF viewers in configure.py

Le 30 juillet 2017 21:51:15 GMT+02:00, "Uwe Stöhr" a écrit : >I reviewed the PDF viewers LyX is searching for. It turned out that the > >last stable version of KGhostView and KPDF were released 9 years ago, >so >I think we could remove their support. Yes, that make sense, or

Re: [patch] update PDF viewers in configure.py

32 are the replacements (which we already support). > > So the attached patch removes to check for ghostview, KPDF and KGhostView and > adds to check for masterpdfeditor. > > Could this go in or are there any reasons against this? You didn’t mention the change to remove xreader

[patch] update PDF viewers in configure.py

the Program Master PDF editor and would therefore like to support it in LyX. I also found out that "ghostview" is deprecated since years and gv, gsview64 and gsview32 are the replacements (which we already support). So the attached patch removes to check for ghostview, KPDF and

<    7   8   9   10   11   12   13   14   15   16   >