Re: Testing Release of 2.4.0 Development Branch

2020-11-02 Thread Pavel Sanda
On Thu, Oct 29, 2020 at 06:09:24PM -0400, Richard Kimberly Heck wrote: > We will greatly appreciate any reports on how well these packages work! > You can post comments either to lyx-users or to lyx-devel. I would like to point out that the major push for this release was to get some feedback

Re: Testing Release of 2.4.0 Development Branch

2020-10-31 Thread Richard Kimberly Heck
.4.0. Toward that end, we have prepared a > 'testing' > release. Please note that this is very much for testing. We do not > necessarily recommend that anyone use it for daily work, although some > of us do. (Be aware that you may have to deal with some bugs and that >

Re: Testing Release of 2.4.0 Development Branch

2020-10-30 Thread Shay Riggs
On Thu, 29 Oct 2020 at 22:09, Richard Kimberly Heck wrote: > Hi, everyone, > > We are beginning the process of moving towards the next major release of > LyX, which will be 2.4.0. Toward that end, we have prepared a 'testing' > release. Please note that this is very much for

Re: Testing Release of 2.4.0 Development Branch

2020-10-30 Thread José Abílio Matos
On Thursday, October 29, 2020 10:09:24 PM WET Richard Kimberly Heck wrote: > Both source code and binaries for Windows and OSX can be found here: > > http://ftp.lyx.org/ftp/pub/lyx/devel/lyx-2.4/ > > Binaries for various Linux distros may or may not be available from > their associated

Re: Testing Release of 2.4.0 Development Branch

2020-10-30 Thread Yu Jin
Toward that end, we have prepared a 'testing' > > release. Please note that this is very much for testing. We do not > > necessarily recommend that anyone use it for daily work, although some > > of us do. (Be aware that you may have to deal with some bugs and that > > files

Re: Testing Release of 2.4.0 Development Branch

2020-10-30 Thread Baris Erkus
On 30-Oct-20 1:09 AM, Richard Kimberly Heck wrote: Hi, everyone, We are beginning the process of moving towards the next major release of LyX, which will be 2.4.0. Toward that end, we have prepared a 'testing' release. Please note that this is very much for testing. We do not necessarily

Testing Release of 2.4.0 Development Branch

2020-10-29 Thread Richard Kimberly Heck
Hi, everyone, We are beginning the process of moving towards the next major release of LyX, which will be 2.4.0. Toward that end, we have prepared a 'testing' release. Please note that this is very much for testing. We do not necessarily recommend that anyone use it for daily work, although some

Re: New Windows Installers for Testing

2020-06-17 Thread michael mayr
Am 08.06.2020 um 17:08 schrieb Richard Kimberly Heck: One of our new contributors, Eugene, has re-written the Windows installer and also produced a 64-bit binary. nice... i guess this solves an issue with the old installer not being able to create the config files in the %appdata% folder?

Re: New Windows Installers for Testing

2020-06-09 Thread Yu Jin
Am Mo., 8. Juni 2020 um 18:00 Uhr schrieb Richard Kimberly Heck < rikih...@lyx.org>: > On 6/8/20 11:19 AM, Thibaut Cuvelier wrote: > > Dear list, > > > > I just tried this installer. It looks like it's missing a kind of > > signature: > > Does this also happen with the 'official' LyX installer?

Re: New Windows Installers for Testing

2020-06-08 Thread Richard Kimberly Heck
On 6/8/20 11:19 AM, Thibaut Cuvelier wrote: > Dear list, > > I just tried this installer. It looks like it's missing a kind of > signature: Does this also happen with the 'official' LyX installer? If not, I wonder why not? Riki -- lyx-users mailing list lyx-users@lists.lyx.org

New Windows Installers for Testing

2020-06-08 Thread Richard Kimberly Heck
One of our new contributors, Eugene, has re-written the Windows installer and also produced a 64-bit binary. His installers can be found here: http://ftp.lyx.org/ftp/pub/lyx/devel/lyx-2.3/ While we expect this become the official LyX installer, please note that, at the moment, these should be

Testing archives

2019-10-17 Thread Jean-Marc Lasgouttes
Just a quick message to see whether archiving works again. JMarc -- lyx-users mailing list lyx-users@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Testing for landscape

2018-11-10 Thread Dr Eberhard Lisse
\makeatletter \if@landscape \KOMAoptions{fontsize=16pt} \else \KOMAoptions{fontsize=11pt} \fi \recalctypearea \makeatother On 2018-11-10 15:44 , Dr Eberhard Lisse wrote: > Hi, > > it's obviously a LaTeX question, but clicking

Testing form landscape

2018-11-10 Thread Dr Eberhard Lisse
Hi, it's obviously a LaTeX question, but clicking landscape in a document results in this: \documentclass[landscape]{scrartcl} How can I test in the Preamble whether landscape is being used so that I can sue a different font and fontsize? Any idea? mfg, el

Re: Testing

2018-05-14 Thread Wolfgang Engelmann
Got it, Wolfgang Am 14.05.2018 um 12:35 schrieb Baris Erkus: My e-mails do not appear in the list. This is a test. Sorry... BE.

Testing

2018-05-14 Thread Baris Erkus
My e-mails do not appear in the list. This is a test. Sorry... BE.

Testing of the 2.2.x Branch (esp Slowness)

2017-01-06 Thread Richard Heck
We (specifically, Jean-Marc Lasgouttes) have recently made some changes to the text rendering algorithms in LyX. We would appreciate it if those who are able could compile and use the 2.2.x branch of the git repository, so that these changes can receive sufficient testing before we schedule

Re: Just upgraded to 2.2.0 on debian testing

2016-06-30 Thread Scott Kostyshak
On Thu, Jun 30, 2016 at 11:09:26PM -0400, David L. Johnson wrote: > Debian testing just included the upgrade to lyx 2.2.0. I want to point out > one thing: If you don't see menu icons, you need to add the svg versions of > the qt library (it may still be linked with qt-4.??, bu

Just upgraded to 2.2.0 on debian testing

2016-06-30 Thread David L. Johnson
Debian testing just included the upgrade to lyx 2.2.0. I want to point out one thing: If you don't see menu icons, you need to add the svg versions of the qt library (it may still be linked with qt-4.??, but looking for the svg libraries with apt-cache search found what I needed). I have

Solution for the PDF viewing problems with Acrobat DC and request for testing

2015-05-20 Thread Uwe Stöhr
Dear LyXers, as you might have noticed, it is not possible to view and update the view of PDF files with LyX 2.1.3 if you use Acrobat Reader DC as viewer for PDF files. The solution it to replace the file pdfview.exe on your PC (in the same folder as the lyx.exe) with this one:

Solution for the PDF viewing problems with Acrobat DC and request for testing

2015-05-20 Thread Uwe Stöhr
Dear LyXers, as you might have noticed, it is not possible to view and update the view of PDF files with LyX 2.1.3 if you use Acrobat Reader DC as viewer for PDF files. The solution it to replace the file pdfview.exe on your PC (in the same folder as the lyx.exe) with this one:

Solution for the PDF viewing problems with Acrobat DC and request for testing

2015-05-20 Thread Uwe Stöhr
Dear LyXers, as you might have noticed, it is not possible to view and update the view of PDF files with LyX 2.1.3 if you use Acrobat Reader DC as viewer for PDF files. The solution it to replace the file pdfview.exe on your PC (in the same folder as the lyx.exe) with this one:

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-06 Thread Rainer M Krug
On 02/05/14, 01:06 , Jerry wrote: On Feb 4, 2014, at 1:27 AM, Rainer M Krug rai...@krugs.de wrote: And then there came homebrew, which works very nicely, and does, in contrast to Macports, not require root privileges. I too once tried to build LyX from source and gave up. MacPorts

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-06 Thread Rainer M Krug
On 02/05/14, 01:06 , Jerry wrote: On Feb 4, 2014, at 1:27 AM, Rainer M Krug rai...@krugs.de wrote: And then there came homebrew, which works very nicely, and does, in contrast to Macports, not require root privileges. I too once tried to build LyX from source and gave up. MacPorts

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-06 Thread Rainer M Krug
On 02/05/14, 01:06 , Jerry wrote: > > On Feb 4, 2014, at 1:27 AM, Rainer M Krug wrote: > >> And then there came homebrew, which works very nicely, and does, >> in contrast to Macports, not require root privileges. > > I too once tried to build LyX from source and gave up. >

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-04 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/04/14, 03:08 , Richard Heck wrote: On 02/03/2014 08:04 PM, Chris Menzel wrote: On 01/29/14, 02:41 , Richard Heck wrote: ...We have had this problem before, and there are other issues about Cocoa versus whatever versus whatever else. It is

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-04 Thread Jerry
On Feb 4, 2014, at 1:27 AM, Rainer M Krug rai...@krugs.de wrote: And then there came homebrew, which works very nicely, and does, in contrast to Macports, not require root privileges. I too once tried to build LyX from source and gave up. MacPorts already has LyX, currently at 2.0.6

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-04 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/04/14, 03:08 , Richard Heck wrote: On 02/03/2014 08:04 PM, Chris Menzel wrote: On 01/29/14, 02:41 , Richard Heck wrote: ...We have had this problem before, and there are other issues about Cocoa versus whatever versus whatever else. It is

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-04 Thread Jerry
On Feb 4, 2014, at 1:27 AM, Rainer M Krug rai...@krugs.de wrote: And then there came homebrew, which works very nicely, and does, in contrast to Macports, not require root privileges. I too once tried to build LyX from source and gave up. MacPorts already has LyX, currently at 2.0.6

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-04 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/04/14, 03:08 , Richard Heck wrote: > On 02/03/2014 08:04 PM, Chris Menzel wrote: >> On 01/29/14, 02:41 , Richard Heck wrote: >>> ...We have had this problem before, and there are other issues >>> about Cocoa versus whatever versus whatever

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-04 Thread Jerry
On Feb 4, 2014, at 1:27 AM, Rainer M Krug wrote: > And then there came homebrew, which works very nicely, and does, in > contrast to Macports, not require root privileges. I too once tried to build LyX from source and gave up. MacPorts already has LyX, currently at 2.0.6

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/31/14, 20:28 , Rainer M Krug wrote: Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org mailto:rgh...@lyx.org a écrit : On 01/30/2014 03:04 AM, Rainer M Krug wrote: On 01/29/14, 02:41 , Richard Heck wrote: On 01/28/2014

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Stephan Witt
Am 03.02.2014 um 10:56 schrieb Rainer M Krug rai...@krugs.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/31/14, 20:28 , Rainer M Krug wrote: Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org mailto:rgh...@lyx.org a écrit : On 01/30/2014 03:04 AM, Rainer M Krug

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/03/14, 11:07 , Stephan Witt wrote: Am 03.02.2014 um 10:56 schrieb Rainer M Krug rai...@krugs.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/31/14, 20:28 , Rainer M Krug wrote: Le vendredi 31 janvier 2014, Richard Heck

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Stephan Witt
Am 03.02.2014 um 11:34 schrieb Rainer M Krug rai...@krugs.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/03/14, 11:07 , Stephan Witt wrote: Am 03.02.2014 um 10:56 schrieb Rainer M Krug rai...@krugs.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/31/14, 20:28 ,

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Chris Menzel
On 01/29/14, 02:41 , Richard Heck wrote: ...We have had this problem before, and there are other issues about Cocoa versus whatever versus whatever else. It is difficult to test every combination, and we have only a couple active OSX developers. Many of them use trunk (2.1.dev) for obvious

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Richard Heck
On 02/03/2014 08:04 PM, Chris Menzel wrote: On 01/29/14, 02:41 , Richard Heck wrote: ...We have had this problem before, and there are other issues about Cocoa versus whatever versus whatever else. It is difficult to test every combination, and we have only a couple active OSX developers. Many

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/31/14, 20:28 , Rainer M Krug wrote: Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org mailto:rgh...@lyx.org a écrit : On 01/30/2014 03:04 AM, Rainer M Krug wrote: On 01/29/14, 02:41 , Richard Heck wrote: On 01/28/2014

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Stephan Witt
Am 03.02.2014 um 10:56 schrieb Rainer M Krug rai...@krugs.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/31/14, 20:28 , Rainer M Krug wrote: Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org mailto:rgh...@lyx.org a écrit : On 01/30/2014 03:04 AM, Rainer M Krug

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/03/14, 11:07 , Stephan Witt wrote: Am 03.02.2014 um 10:56 schrieb Rainer M Krug rai...@krugs.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/31/14, 20:28 , Rainer M Krug wrote: Le vendredi 31 janvier 2014, Richard Heck

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Stephan Witt
Am 03.02.2014 um 11:34 schrieb Rainer M Krug rai...@krugs.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/03/14, 11:07 , Stephan Witt wrote: Am 03.02.2014 um 10:56 schrieb Rainer M Krug rai...@krugs.de: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/31/14, 20:28 ,

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Chris Menzel
On 01/29/14, 02:41 , Richard Heck wrote: ...We have had this problem before, and there are other issues about Cocoa versus whatever versus whatever else. It is difficult to test every combination, and we have only a couple active OSX developers. Many of them use trunk (2.1.dev) for obvious

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Richard Heck
On 02/03/2014 08:04 PM, Chris Menzel wrote: On 01/29/14, 02:41 , Richard Heck wrote: ...We have had this problem before, and there are other issues about Cocoa versus whatever versus whatever else. It is difficult to test every combination, and we have only a couple active OSX developers. Many

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/31/14, 20:28 , Rainer M Krug wrote: > > > Le vendredi 31 janvier 2014, Richard Heck > a écrit : > > On 01/30/2014 03:04 AM, Rainer M Krug wrote: > > On 01/29/14, 02:41 , Richard Heck wrote: > > On

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Stephan Witt
Am 03.02.2014 um 10:56 schrieb Rainer M Krug : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > On 01/31/14, 20:28 , Rainer M Krug wrote: >> >> >> Le vendredi 31 janvier 2014, Richard Heck > > a écrit : >> >> On 01/30/2014

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/03/14, 11:07 , Stephan Witt wrote: > Am 03.02.2014 um 10:56 schrieb Rainer M Krug : > >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> >> >> On 01/31/14, 20:28 , Rainer M Krug wrote: >>> >>> >>> Le vendredi 31

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Stephan Witt
Am 03.02.2014 um 11:34 schrieb Rainer M Krug : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > > On 02/03/14, 11:07 , Stephan Witt wrote: >> Am 03.02.2014 um 10:56 schrieb Rainer M Krug : >> >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>> >>>

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Chris Menzel
On 01/29/14, 02:41 , Richard Heck wrote: >...We have had > this problem before, and there are other issues about Cocoa versus > whatever versus whatever else. It is difficult to test every > combination, and we have only a couple active OSX developers. Many > of them use trunk (2.1.dev) for

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-02-03 Thread Richard Heck
On 02/03/2014 08:04 PM, Chris Menzel wrote: On 01/29/14, 02:41 , Richard Heck wrote: ...We have had this problem before, and there are other issues about Cocoa versus whatever versus whatever else. It is difficult to test every combination, and we have only a couple active OSX developers. Many

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-31 Thread Richard Heck
On 01/30/2014 03:04 AM, Rainer M Krug wrote: On 01/29/14, 02:41 , Richard Heck wrote: On 01/28/2014 03:14 PM, Scott Kostyshak wrote: This should be fixed shortly and a new installer will be uploaded. As often, this is due to changes in the underlying Qt platform that seem to exist only on

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-31 Thread Jean-Marc Lasgouttes
31/01/2014 15:34, Richard Heck: On 01/30/2014 03:04 AM, Rainer M Krug wrote: To facilitate this, may I suggest to create a homebrew recipe to facilitate the installation and update of the latest LyX? At least for me, I would likely use (and update) it regularly as it is no hassle at all (in

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-31 Thread Rainer M Krug
Le vendredi 31 janvier 2014, Jean-Marc Lasgouttes lasgout...@lyx.org a écrit : 31/01/2014 15:34, Richard Heck: On 01/30/2014 03:04 AM, Rainer M Krug wrote: To facilitate this, may I suggest to create a homebrew recipe to facilitate the installation and update of the latest LyX? At least for

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-31 Thread Rainer M Krug
Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org a écrit : On 01/30/2014 03:04 AM, Rainer M Krug wrote: On 01/29/14, 02:41 , Richard Heck wrote: On 01/28/2014 03:14 PM, Scott Kostyshak wrote: This should be fixed shortly and a new installer will be uploaded. As often, this is

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-31 Thread Richard Heck
On 01/30/2014 03:04 AM, Rainer M Krug wrote: On 01/29/14, 02:41 , Richard Heck wrote: On 01/28/2014 03:14 PM, Scott Kostyshak wrote: This should be fixed shortly and a new installer will be uploaded. As often, this is due to changes in the underlying Qt platform that seem to exist only on

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-31 Thread Jean-Marc Lasgouttes
31/01/2014 15:34, Richard Heck: On 01/30/2014 03:04 AM, Rainer M Krug wrote: To facilitate this, may I suggest to create a homebrew recipe to facilitate the installation and update of the latest LyX? At least for me, I would likely use (and update) it regularly as it is no hassle at all (in

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-31 Thread Rainer M Krug
Le vendredi 31 janvier 2014, Jean-Marc Lasgouttes lasgout...@lyx.org a écrit : 31/01/2014 15:34, Richard Heck: On 01/30/2014 03:04 AM, Rainer M Krug wrote: To facilitate this, may I suggest to create a homebrew recipe to facilitate the installation and update of the latest LyX? At least for

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-31 Thread Rainer M Krug
Le vendredi 31 janvier 2014, Richard Heck rgh...@lyx.org a écrit : On 01/30/2014 03:04 AM, Rainer M Krug wrote: On 01/29/14, 02:41 , Richard Heck wrote: On 01/28/2014 03:14 PM, Scott Kostyshak wrote: This should be fixed shortly and a new installer will be uploaded. As often, this is

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-31 Thread Richard Heck
On 01/30/2014 03:04 AM, Rainer M Krug wrote: On 01/29/14, 02:41 , Richard Heck wrote: On 01/28/2014 03:14 PM, Scott Kostyshak wrote: This should be fixed shortly and a new installer will be uploaded. As often, this is due to changes in the underlying Qt platform that seem to exist only on

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-31 Thread Jean-Marc Lasgouttes
31/01/2014 15:34, Richard Heck: On 01/30/2014 03:04 AM, Rainer M Krug wrote: To facilitate this, may I suggest to create a homebrew recipe to facilitate the installation and update of the latest LyX? At least for me, I would likely use (and update) it regularly as it is no hassle at all (in

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-31 Thread Rainer M Krug
Le vendredi 31 janvier 2014, Jean-Marc Lasgouttes a écrit : > 31/01/2014 15:34, Richard Heck: > >> On 01/30/2014 03:04 AM, Rainer M Krug wrote: >> >>> To facilitate this, may I suggest to create a homebrew recipe to >>> facilitate the installation and update of the latest

Re: Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-31 Thread Rainer M Krug
Le vendredi 31 janvier 2014, Richard Heck a écrit : > On 01/30/2014 03:04 AM, Rainer M Krug wrote: > >> On 01/29/14, 02:41 , Richard Heck wrote: >> >>> On 01/28/2014 03:14 PM, Scott Kostyshak wrote: >>> This should be fixed shortly and a new installer will be uploaded.

Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-30 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/29/14, 02:41 , Richard Heck wrote: On 01/28/2014 03:14 PM, Scott Kostyshak wrote: This should be fixed shortly and a new installer will be uploaded. As often, this is due to changes in the underlying Qt platform that seem to exist only

Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-30 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/29/14, 02:41 , Richard Heck wrote: On 01/28/2014 03:14 PM, Scott Kostyshak wrote: This should be fixed shortly and a new installer will be uploaded. As often, this is due to changes in the underlying Qt platform that seem to exist only

Facilitate testing on OSX - WAS: menu bar lost in OS X

2014-01-30 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/29/14, 02:41 , Richard Heck wrote: > On 01/28/2014 03:14 PM, Scott Kostyshak wrote: >> This should be fixed shortly and a new installer will be >> uploaded. > > As often, this is due to changes in the underlying Qt platform > that seem to

testing compiled lyx 2.0.6

2013-05-25 Thread Wolfgang Engelmann
I have compiled lyx 2.0.6 according to 1) ./configure configures LyX according to your system. 2) make compiles the program. 3) src/lyx runs the program so you can check it out. while doing this, I get: LyX: Done! Warning: Could not

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Wolfgang Engelmann
Am Saturday, 25. May 2013, 13:56:36 schrieb Wolfgang Engelmann: I found out in the meantime, that removing the old .lyx folder solved the issue. Sorry for the noice. Wolfgang I have compiled lyx 2.0.6 according to 1) ./configure configures LyX according to your system.

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Stephan Witt
Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann engelm...@uni-tuebingen.de: I have compiled lyx 2.0.6 according to 1) ./configure configures LyX according to your system. Hi Wolfgang, it's not a good idea to build in source tree. You should make a separate build

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Wolfgang Engelmann
Am Saturday, 25. May 2013, 15:24:22 schrieb Stephan Witt: Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann engelmann@uni- tuebingen.de: I have compiled lyx 2.0.6 according to 1) ./configure configures LyX according to your system. Hi Wolfgang, it's not a good

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Stephan Witt
Am 25.05.2013 um 15:32 schrieb Wolfgang Engelmann engelm...@uni-tuebingen.de: Am Saturday, 25. May 2013, 15:24:22 schrieb Stephan Witt: Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann engelm...@uni-tuebingen.de: I have compiled lyx 2.0.6 according to 1) ./configure

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Steve Litt
On Sat, 25 May 2013 15:24:22 +0200 Stephan Witt st.w...@gmx.net wrote: Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann engelm...@uni-tuebingen.de: I have compiled lyx 2.0.6 according to 1) ./configure configures LyX according to your system. Hi Wolfgang, it's not

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Jean-Marc Lasgouttes
Le 25/05/13 17:54, Steve Litt a écrit : Why is what you did above any better than ./configure; make; make install from lyxhome itself? I didn't even know the separate build directory could be done. Do you recommend the separate build directory for compiling all programs where you need to

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Stephan Witt
Am 25.05.2013 um 17:54 schrieb Steve Litt sl...@troubleshooters.com: On Sat, 25 May 2013 15:24:22 +0200 Stephan Witt st.w...@gmx.net wrote: Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann engelm...@uni-tuebingen.de: I have compiled lyx 2.0.6 according to 1) ./configure

testing compiled lyx 2.0.6

2013-05-25 Thread Wolfgang Engelmann
I have compiled lyx 2.0.6 according to 1) ./configure configures LyX according to your system. 2) make compiles the program. 3) src/lyx runs the program so you can check it out. while doing this, I get: LyX: Done! Warning: Could not

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Wolfgang Engelmann
Am Saturday, 25. May 2013, 13:56:36 schrieb Wolfgang Engelmann: I found out in the meantime, that removing the old .lyx folder solved the issue. Sorry for the noice. Wolfgang I have compiled lyx 2.0.6 according to 1) ./configure configures LyX according to your system.

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Stephan Witt
Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann engelm...@uni-tuebingen.de: I have compiled lyx 2.0.6 according to 1) ./configure configures LyX according to your system. Hi Wolfgang, it's not a good idea to build in source tree. You should make a separate build

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Wolfgang Engelmann
Am Saturday, 25. May 2013, 15:24:22 schrieb Stephan Witt: Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann engelmann@uni- tuebingen.de: I have compiled lyx 2.0.6 according to 1) ./configure configures LyX according to your system. Hi Wolfgang, it's not a good

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Stephan Witt
Am 25.05.2013 um 15:32 schrieb Wolfgang Engelmann engelm...@uni-tuebingen.de: Am Saturday, 25. May 2013, 15:24:22 schrieb Stephan Witt: Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann engelm...@uni-tuebingen.de: I have compiled lyx 2.0.6 according to 1) ./configure

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Steve Litt
On Sat, 25 May 2013 15:24:22 +0200 Stephan Witt st.w...@gmx.net wrote: Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann engelm...@uni-tuebingen.de: I have compiled lyx 2.0.6 according to 1) ./configure configures LyX according to your system. Hi Wolfgang, it's not

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Jean-Marc Lasgouttes
Le 25/05/13 17:54, Steve Litt a écrit : Why is what you did above any better than ./configure; make; make install from lyxhome itself? I didn't even know the separate build directory could be done. Do you recommend the separate build directory for compiling all programs where you need to

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Stephan Witt
Am 25.05.2013 um 17:54 schrieb Steve Litt sl...@troubleshooters.com: On Sat, 25 May 2013 15:24:22 +0200 Stephan Witt st.w...@gmx.net wrote: Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann engelm...@uni-tuebingen.de: I have compiled lyx 2.0.6 according to 1) ./configure

testing compiled lyx 2.0.6

2013-05-25 Thread Wolfgang Engelmann
I have compiled lyx 2.0.6 according to 1) ./configure configures LyX according to your system. 2) make compiles the program. 3) src/lyx runs the program so you can check it out. while doing this, I get: LyX: Done! Warning: Could not

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Wolfgang Engelmann
Am Saturday, 25. May 2013, 13:56:36 schrieb Wolfgang Engelmann: I found out in the meantime, that removing the old .lyx folder solved the issue. Sorry for the noice. Wolfgang > I have compiled lyx 2.0.6 according to > > 1) ./configure > configures LyX according to your system. >

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Stephan Witt
Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann : > I have compiled lyx 2.0.6 according to > > 1) ./configure > configures LyX according to your system. Hi Wolfgang, it's not a good idea to build in source tree. You should make a separate build

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Wolfgang Engelmann
Am Saturday, 25. May 2013, 15:24:22 schrieb Stephan Witt: > Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann : > > I have compiled lyx 2.0.6 according to > > > > 1) ./configure > > > >configures LyX according to your system. > > Hi Wolfgang, > >

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Stephan Witt
Am 25.05.2013 um 15:32 schrieb Wolfgang Engelmann : > Am Saturday, 25. May 2013, 15:24:22 schrieb Stephan Witt: > > Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann > > : > > > I have compiled lyx 2.0.6 according to > > > > > > 1)

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Steve Litt
On Sat, 25 May 2013 15:24:22 +0200 Stephan Witt wrote: > Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann > : > > > I have compiled lyx 2.0.6 according to > > > > 1) ./configure > >configures LyX according to your system. > > Hi

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Jean-Marc Lasgouttes
Le 25/05/13 17:54, Steve Litt a écrit : Why is what you did above any better than ./configure; make; make install from lyxhome itself? I didn't even know the separate build directory could be done. Do you recommend the separate build directory for compiling all programs where you need to

Re: testing compiled lyx 2.0.6

2013-05-25 Thread Stephan Witt
Am 25.05.2013 um 17:54 schrieb Steve Litt : > On Sat, 25 May 2013 15:24:22 +0200 > Stephan Witt wrote: > >> Am 25.05.2013 um 13:56 schrieb Wolfgang Engelmann >> : >> >>> I have compiled lyx 2.0.6 according to >>> >>>

Re: Arabic\Farsi and XeTeX, testing a patch

2012-07-28 Thread Ronen Abravanel
On Fri, Jul 27, 2012 at 12:38 PM, Jürgen Spitzmüller sp...@lyx.org wrote: Guenter Milde wrote: I see, so we actually have (siht) for Arabic (babel polyglossia) and Hebrew (polyglossia) as well as for Arabic and Hebrew in OpenOffice etc. )siht( for Hebrew (babel)

Re: Arabic\Farsi and XeTeX, testing a patch

2012-07-28 Thread Ronen Abravanel
On Fri, Jul 27, 2012 at 12:38 PM, Jürgen Spitzmüller sp...@lyx.org wrote: Guenter Milde wrote: I see, so we actually have (siht) for Arabic (babel polyglossia) and Hebrew (polyglossia) as well as for Arabic and Hebrew in OpenOffice etc. )siht( for Hebrew (babel)

Re: Arabic\Farsi and XeTeX, testing a patch

2012-07-28 Thread Ronen Abravanel
On Fri, Jul 27, 2012 at 12:38 PM, Jürgen Spitzmüller wrote: > Guenter Milde wrote: > > I see, so we actually have > > > > (siht) for Arabic (babel & polyglossia) and Hebrew (polyglossia) > > > >as well as for Arabic and Hebrew in OpenOffice etc. > > > > )siht(

Re: Arabic\Farsi and XeTeX, testing a patch

2012-07-27 Thread Guenter Milde
On 2012-07-24, Jürgen Spitzmüller wrote: Guenter Milde wrote: If I understand right, babel converts the input )siht ekil( to (like this) while xelatex+polyglossia converts (siht ekil) to (like this). Yes [for Hebrew, for that matter. In Arabic, the case is different. This is why

Re: Arabic\Farsi and XeTeX, testing a patch

2012-07-27 Thread Jürgen Spitzmüller
Guenter Milde wrote: I see, so we actually have (siht) for Arabic (babel polyglossia) and Hebrew (polyglossia) as well as for Arabic and Hebrew in OpenOffice etc. )siht( for Hebrew (babel) Yes. In the LyX source file, that is. In the LyX workarea, we have (siht)

Re: Arabic\Farsi and XeTeX, testing a patch

2012-07-27 Thread Guenter Milde
On 2012-07-24, Jürgen Spitzmüller wrote: Guenter Milde wrote: If I understand right, babel converts the input )siht ekil( to (like this) while xelatex+polyglossia converts (siht ekil) to (like this). Yes [for Hebrew, for that matter. In Arabic, the case is different. This is why

Re: Arabic\Farsi and XeTeX, testing a patch

2012-07-27 Thread Jürgen Spitzmüller
Guenter Milde wrote: I see, so we actually have (siht) for Arabic (babel polyglossia) and Hebrew (polyglossia) as well as for Arabic and Hebrew in OpenOffice etc. )siht( for Hebrew (babel) Yes. In the LyX source file, that is. In the LyX workarea, we have (siht)

Re: Arabic\Farsi and XeTeX, testing a patch

2012-07-27 Thread Guenter Milde
On 2012-07-24, Jürgen Spitzmüller wrote: > Guenter Milde wrote: >> If I understand right, >> babel converts the input ")siht ekil(" to "(like this)" >> while >> xelatex+polyglossia converts "(siht ekil)" to "(like this)". > Yes [for Hebrew, for that matter. In Arabic, the case is

Re: Arabic\Farsi and XeTeX, testing a patch

2012-07-27 Thread Jürgen Spitzmüller
Guenter Milde wrote: > I see, so we actually have > > (siht) for Arabic (babel & polyglossia) and Hebrew (polyglossia) > >as well as for Arabic and Hebrew in OpenOffice etc. > > )siht( for Hebrew (babel) Yes. In the LyX source file, that is. In the LyX workarea, we have

Re: Arabic\Farsi and XeTeX, testing a patch

2012-07-24 Thread Jürgen Spitzmüller
Guenter Milde wrote: If I understand right, babel converts the input )siht ekil( to (like this) while xelatex+polyglossia converts (siht ekil) to (like this). Yes [for Hebrew, for that matter. In Arabic, the case is different. This is why we have )siht( in the LyX source for

Re: Arabic\Farsi and XeTeX, testing a patch

2012-07-24 Thread Jürgen Spitzmüller
Guenter Milde wrote: If I understand right, babel converts the input )siht ekil( to (like this) while xelatex+polyglossia converts (siht ekil) to (like this). Yes [for Hebrew, for that matter. In Arabic, the case is different. This is why we have )siht( in the LyX source for

Re: Arabic\Farsi and XeTeX, testing a patch

2012-07-24 Thread Jürgen Spitzmüller
Guenter Milde wrote: > If I understand right, > > babel converts the input ")siht ekil(" to "(like this)" > > while > > xelatex+polyglossia converts "(siht ekil)" to "(like this)". Yes [for Hebrew, for that matter. In Arabic, the case is different. This is why we have )siht( in the

  1   2   3   4   >