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 about new Docbook output format we provide.

If anyone with related expertise could give it a try and provide
us the feedback that would be approeciated...

Pavel
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Testing Release of 2.4.0 Development Branch

2020-10-31 Thread Richard Kimberly Heck
On 10/30/20 7:27 PM, Shay Riggs wrote:
> On Thu, 29 Oct 2020 at 22:09, Richard Kimberly Heck  <mailto:rikih...@lyx.org>> 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 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 edited with 2.4.x cannot be opened in 2.3.x without being
> exported
> to that format.)
>
>
> I’ve been looking at the new table features (xltabular, tabularx…) and
> I love the improvements.
>
> Not sure if this is the appropriate forum for feature enhancements to
> v2.4, but I’d love a pair of “suppress column space beforeafter”
> tickboxes that put “@{}” before/after the column specifier.
>
> For example, if I have a table with several columns, one of which is a
> “Variable” width column, and then use the “LaTeX argument” field to
> override the definition, this triggers LyX into thinking you no longer
> want the X (“Variable”) type column any more, and instead of a
> “tabularx” table you get a “tabular” (which has no concept of an X
> column).

Probably best here to (i) file an enhancement request at the bug tracker
<https://www.lyx.org/trac/wiki/BugTrackerHome> and (ii) send a version
of this message to lyx-devel. That'll get it maximal exposure.

Riki



-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


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 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 edited with 2.4.x cannot be opened in 2.3.x without being exported
> to that format.)
>

I’ve been looking at the new table features (xltabular, tabularx…) and I
love the improvements.

Not sure if this is the appropriate forum for feature enhancements to v2.4,
but I’d love a pair of “suppress column space beforeafter” tickboxes that
put “@{}” before/after the column specifier.

For example, if I have a table with several columns, one of which is a
“Variable” width column, and then use the “LaTeX argument” field to
override the definition, this triggers LyX into thinking you no longer want
the X (“Variable”) type column any more, and instead of a “tabularx” table
you get a “tabular” (which has no concept of an X column).

Looks like the same thing happens on multi-page tables too :-(

I suppose a more general solution might be to have text fields where you
can put in whatever “@{}”-style overrides you like without interfering with
LyX’s column specifier.

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 repositories. (But, if you are on Linux, you should not
> have too much trouble compiling the source. If you need help, just ask.)
>
> We will greatly appreciate any reports on how well these packages work!
> You can post comments either to lyx-users or to lyx-devel.
>

Can confirm: it compiles and runs fine (during my very limited tests) on
Arch Linux.

Looking forward to the final release!

Regards
Shay
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


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 repositories. (But, if you are on Linux, you should not
> have too much trouble compiling the source. If you need help, just ask.)

BTW if you are using Fedora or Red Hat Enterprise Linux/CentOS I created a 
copr repository:

https://copr.fedorainfracloud.org/coprs/jamatos/lyx-devel/ 

There is just one package in that repository: lyx-devel. The package is 
parallel installable with the stable version and it does not change, neither 
uses any of the stable settings. That means that it is safe to use and 
uninstall that it will not mess with the current stable 2.3.5.2.

Beware that if you save a document with lyx-devel the stable version will not 
be able to read it (yet). On the other hand you can have a look of what is 
coming next in LyX without risking any work and helping to stabilize the next 
version.

> We will greatly appreciate any reports on how well these packages work!
> You can post comments either to lyx-users or to lyx-devel.
> 
> Riki

This applies as well, all feedback is welcome either here or on the lyx-devel 
mailing list.

Regards,
-- 
José Abílio-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


Re: Testing Release of 2.4.0 Development Branch

2020-10-30 Thread Yu Jin
Am Fr., 30. Okt. 2020 um 09:21 Uhr schrieb Baris Erkus <
bariser...@hotmail.com>:

> 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 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 edited with 2.4.x cannot be opened in 2.3.x without being exported
> > to that format.)
> >
> > 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 repositories. (But, if you are on Linux, you should not
> > have too much trouble compiling the source. If you need help, just ask.)
> >
> > We will greatly appreciate any reports on how well these packages work!
> > You can post comments either to lyx-users or to lyx-devel.
> >
> > Riki
> >
> Would it be possible to set it up seperately, while keeping the current
> stable LyX 2.3.5.2. Particularly Windows.
>
> I know I have several installations of LyX on my PC and I did not have
> any issue using them all. Will this be the case for the test release?
>

>From all I know this should be no problem. You should just make sure that
you uncheck "File associations" while installing the testing release. The
only small issue could happen is that the preview of vector images (like
pdf) will not work, then simply run reconfigure from the LyX UI. Otherwise
you could always ask for help here if something goes wrong.
-- 
Eugene
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


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 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 edited with 2.4.x cannot be opened in 2.3.x without being exported
to that format.)

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 repositories. (But, if you are on Linux, you should not
have too much trouble compiling the source. If you need help, just ask.)

We will greatly appreciate any reports on how well these packages work!
You can post comments either to lyx-users or to lyx-devel.

Riki

Would it be possible to set it up seperately, while keeping the current 
stable LyX 2.3.5.2. Particularly Windows.


I know I have several installations of LyX on my PC and I did not have 
any issue using them all. Will this be the case for the test release?


--

↓↓
Please bottom-post. Start your reply here:

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


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
of us do. (Be aware that you may have to deal with some bugs and that
files edited with 2.4.x cannot be opened in 2.3.x without being exported
to that format.)

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 repositories. (But, if you are on Linux, you should not
have too much trouble compiling the source. If you need help, just ask.)

We will greatly appreciate any reports on how well these packages work!
You can post comments either to lyx-users or to lyx-devel.

Riki


-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


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? (at least i thought 
that's where the problem was)



with the normal installers (230 and 2351) LyX would just always crash on 
startup, using the beta now finally let's me run the program...




br,
michael

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


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? If not, I
> wonder why not?
>

Yeah this happens on any software which is not known to Windows (from what
the web says
).
Programs, which not many users use (however Microsoft gets that data) are
considered insecure, this prompt will stop showing up eventually when
enough users run the installer. It will also not appear when you want to
run it a second time after you clicked on "run anyway" on previous
execution. FYI I just downloaded the official installer and got this prompt
when trying to run it for the first time.

> Also, when starting the installer, it complained that LyX was already
open, even though it was just a development version. I suppose that this
check should be performed much later, i.e. just when actually starting the
installation: is the LyX version installed in that folder already started?

Ok, your feedback has reached me, I will see what I can do there.

Eugene
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


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
http://lists.lyx.org/mailman/listinfo/lyx-users


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 considered beta (as marked).

Bugs can be reported either to lyx-de...@lists.lyx.org or via the bug
tracker (https://www.lyx.org/trac/wiki/BugTrackerHome).

Riki


-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users


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 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
> 
> 



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 the release of LyX 2.2.3.

For those on Linux, this should not be terribly difficult. You will need
to install some headers libraries, e.g., zlib-devel and especially
qt-devel (naming may vary on various distros), as well as the usual
compilation tools (automake, make, gcc). You will also need to install
git to be able to check out the repo. But the compilation procedure is
otherwise fairly straightforward.

Do this, from whatever directory you choose (in which you have write
privileges):

> git clone git://git.lyx.org/lyx/
> cd lyx
> git checkout 2.2.x

You have now checked out the 2.2.x branch, which is what will become
2.2.3. Have a look, if you wish, at the INSTALL file for some
information about what else you may need to do. Compiling is then the
usual three-step:

> ./autogen.sh
> ./configure --enable-build-type=rel

This flag gives you a "release version" rather than a "development
version", which is what 2.2.3 would actually be.

> ./configure --help

if you want more information on other options. It is, for example,
possible to install LyX to a location other than the default, which is
/usr/local/, and which will normally require root privileges.

You may find that configuation fails. This will usually be due to your
not having all the dependencies installed. The configuation script is
usually pretty good at telling you what you need. If you have problems,
then please respond to this email, and we'll help.

> make
> sudo make install

You can add an option "-j N" to the first command make to speed things
up. This tells make to compile N files simultaneously. Roughly speaking,
you can set N to the number of cores you have (or even a few more).

Richard Heck
Stable Branch Maintainer




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.??, but looking for the svg
> libraries with apt-cache search found what I needed).

Could you contact the Debian packager about this? I think they need to
add a dependency.

Scott


signature.asc
Description: PGP signature


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 yet to check it all out, but I am absolutely floored by the 
scrolling ability in math eqnarray finally.  As one who never can keep 
the line length in check during the writing process, it is a blessing to 
be able to see the whole line.  Formerly I have had to either set the 
font really, really small or (more recently) stretch the window over two 
monitors.  This is a great advance; thanks to all who developed it.


I have yet to see what has changed with the beamer layout.  I hope it is 
not too much of a PITA to change old files to the new layout, since I 
have classes on Tuesday that I need it for.  I will find that out 
tomorrow


--

David L. Johnson
Department of Mathematics
Lehigh University



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:


http://ftp.lyx.de/LyX%202.1.3/pdfview.exe

Viewing and also updating the view is then done via LyX's view button 
(the update button won't do anything visible).


Please test and report back if it works for you.
If it doesn't work, please write what version of Acrobat you are using 
and what Windows. Please also write the name of the Acrobat program 
window when a PDF is opened (e.g. Hello.pdf - Adobe Acrobat DC Pro).


many thanks and regards
Uwe


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:


http://ftp.lyx.de/LyX%202.1.3/pdfview.exe

Viewing and also updating the view is then done via LyX's view button 
(the update button won't do anything visible).


Please test and report back if it works for you.
If it doesn't work, please write what version of Acrobat you are using 
and what Windows. Please also write the name of the Acrobat program 
window when a PDF is opened (e.g. Hello.pdf - Adobe Acrobat DC Pro).


many thanks and regards
Uwe


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:


http://ftp.lyx.de/LyX%202.1.3/pdfview.exe

Viewing and also updating the view is then done via LyX's view button 
(the update button won't do anything visible).


Please test and report back if it works for you.
If it doesn't work, please write what version of Acrobat you are using 
and what Windows. Please also write the name of the Acrobat program 
window when a PDF is opened (e.g. "Hello.pdf - Adobe Acrobat DC Pro").


many thanks and regards
Uwe


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 already has LyX, currently at 2.0.6 
 http://www.macports.org/ports.php?by=namesubstr=lyx
 
 I have not used MacPorts for LyX. I'm currently using 2.1beta2 which
 is not available there. I wonder if the maintainer could be cajoled
 into keeping a beta version as well.

I guess this will be difficult:

Maintained by: nomaintainer

But still, if somebody would add a portfile for the betas, that would be
useful as well (although I prefer homebrew and will follow that path).

Cheers,

Rainer

 
 Jerry
 

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug



signature.asc
Description: OpenPGP digital signature


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 already has LyX, currently at 2.0.6 
 http://www.macports.org/ports.php?by=namesubstr=lyx
 
 I have not used MacPorts for LyX. I'm currently using 2.1beta2 which
 is not available there. I wonder if the maintainer could be cajoled
 into keeping a beta version as well.

I guess this will be difficult:

Maintained by: nomaintainer

But still, if somebody would add a portfile for the betas, that would be
useful as well (although I prefer homebrew and will follow that path).

Cheers,

Rainer

 
 Jerry
 

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug



signature.asc
Description: OpenPGP digital signature


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.
> 
> MacPorts already has LyX, currently at 2.0.6 
> http://www.macports.org/ports.php?by=name=lyx
> 
> I have not used MacPorts for LyX. I'm currently using 2.1beta2 which
> is not available there. I wonder if the maintainer could be cajoled
> into keeping a beta version as well.

I guess this will be difficult:

Maintained by: nomaintainer

But still, if somebody would add a portfile for the betas, that would be
useful as well (although I prefer homebrew and will follow that path).

Cheers,

Rainer

> 
> Jerry
> 

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug



signature.asc
Description: OpenPGP digital signature


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
 difficult to test every combination, and we have only a couple
 active OSX developers. Many of them use trunk (2.1.dev) for
 obvious sorts of reasons. So, well, we could really use a
 couple people who could test the OSX version on a more regular
 basis.
 Well, I'm running 2.1.0 dev (with good stability) on both OS X
 10.9 and Linux on a Chromebook (thanks to Crouton). Tell me what
 to do to help.
 
 It has been suggested that someone produce a homebrew recipe that
 would allow more

Yeah - that was me.

 ordinary users to compile and test the most recent versions, or
 even develop some system that would produce nightly, or perhaps
 weekly, builds. It would be best if this could be done for both
 trunk (2.1.dev) and branch (2.0.8dev, as things stand). Those

I agree. As I understand homebrew, the only difference wold be to
where the source is downloaded from (static URL, I think svn is also
possible, ...). I am looking loosely at the moment into the script,
and guess I will make slowly some progress. I will see that I setup a
github repo so that others can also work on it.

 of us on Linux can do this fairly easily, of course, but it's
 harder for people on OSX (or, God forbid, Windows). I confess that
 the one time I tried to

I agree. I was using Linux for more then 10 years and was very happy
with it - Ubuntu and Awesome window manager (
http://awesome.naquadah.org/ ) - a dream...

But then came the chance of getting a new laptop, and the Retia
display was there - well. and now I am using OSX.

But coming back, I am really missing the package management in Linux -
apt is so much easier then manually looking for updates, downloading
them, 

And then there came homebrew, which works very nicely, and does, in
contrast to Macports, not require root privileges.

I will keep you posted about the progress - and if somebody has any
experience with homebrew recipes, any input is welcome.

 compile LyX on OSX I failed and gave up.

Never tried it directly - only homebrew, and that works very smoothly.

Cheers,

Rainer


 
 Richard
 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS8KRnAAoJENvXNx4PUvmCknMH/1+DNMpiWvKT88Gr//8kNv/G
knT6fZGso9OLzFHXjs26GAMBlYDQaSlM8Du//WVGftk4kfdOnDnxyQHKUhspMZnI
e2dY8ZfoV2xOFG5x1kclkqtS6F0+/M7R9PpU5arD0HUoe6rXIfJe3rlPYn8WK2B/
uFnp9oVcWDtz/DcimBO6lzQAqP43QT3bYkFVuB78/nGU9Po/y08GxPm+9MtiySAe
PftI0OwK5bccje8Ou0xxpUCtMUAv4f0TVMM3Q1g3hpFHEFVCGDH953UyXOJrVfLX
qGV0lHQ0El9bEeP3aTyoesNJzM/QEinuv8KTCCdJ3ban+JglyurVI+bwgnwsGJI=
=ZdXW
-END PGP SIGNATURE-


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
http://www.macports.org/ports.php?by=namesubstr=lyx

I have not used MacPorts for LyX. I'm currently using 2.1beta2 which is not 
available there. I wonder if the maintainer could be cajoled into keeping a 
beta version as well.

Jerry

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
 difficult to test every combination, and we have only a couple
 active OSX developers. Many of them use trunk (2.1.dev) for
 obvious sorts of reasons. So, well, we could really use a
 couple people who could test the OSX version on a more regular
 basis.
 Well, I'm running 2.1.0 dev (with good stability) on both OS X
 10.9 and Linux on a Chromebook (thanks to Crouton). Tell me what
 to do to help.
 
 It has been suggested that someone produce a homebrew recipe that
 would allow more

Yeah - that was me.

 ordinary users to compile and test the most recent versions, or
 even develop some system that would produce nightly, or perhaps
 weekly, builds. It would be best if this could be done for both
 trunk (2.1.dev) and branch (2.0.8dev, as things stand). Those

I agree. As I understand homebrew, the only difference wold be to
where the source is downloaded from (static URL, I think svn is also
possible, ...). I am looking loosely at the moment into the script,
and guess I will make slowly some progress. I will see that I setup a
github repo so that others can also work on it.

 of us on Linux can do this fairly easily, of course, but it's
 harder for people on OSX (or, God forbid, Windows). I confess that
 the one time I tried to

I agree. I was using Linux for more then 10 years and was very happy
with it - Ubuntu and Awesome window manager (
http://awesome.naquadah.org/ ) - a dream...

But then came the chance of getting a new laptop, and the Retia
display was there - well. and now I am using OSX.

But coming back, I am really missing the package management in Linux -
apt is so much easier then manually looking for updates, downloading
them, 

And then there came homebrew, which works very nicely, and does, in
contrast to Macports, not require root privileges.

I will keep you posted about the progress - and if somebody has any
experience with homebrew recipes, any input is welcome.

 compile LyX on OSX I failed and gave up.

Never tried it directly - only homebrew, and that works very smoothly.

Cheers,

Rainer


 
 Richard
 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS8KRnAAoJENvXNx4PUvmCknMH/1+DNMpiWvKT88Gr//8kNv/G
knT6fZGso9OLzFHXjs26GAMBlYDQaSlM8Du//WVGftk4kfdOnDnxyQHKUhspMZnI
e2dY8ZfoV2xOFG5x1kclkqtS6F0+/M7R9PpU5arD0HUoe6rXIfJe3rlPYn8WK2B/
uFnp9oVcWDtz/DcimBO6lzQAqP43QT3bYkFVuB78/nGU9Po/y08GxPm+9MtiySAe
PftI0OwK5bccje8Ou0xxpUCtMUAv4f0TVMM3Q1g3hpFHEFVCGDH953UyXOJrVfLX
qGV0lHQ0El9bEeP3aTyoesNJzM/QEinuv8KTCCdJ3ban+JglyurVI+bwgnwsGJI=
=ZdXW
-END PGP SIGNATURE-


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
http://www.macports.org/ports.php?by=namesubstr=lyx

I have not used MacPorts for LyX. I'm currently using 2.1beta2 which is not 
available there. I wonder if the maintainer could be cajoled into keeping a 
beta version as well.

Jerry

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
>>> difficult to test every combination, and we have only a couple
>>> active OSX developers. Many of them use trunk (2.1.dev) for
>>> obvious sorts of reasons. So, well, we could really use a
>>> couple people who could test the OSX version on a more regular
>>> basis.
>> Well, I'm running 2.1.0 dev (with good stability) on both OS X
>> 10.9 and Linux on a Chromebook (thanks to Crouton). Tell me what
>> to do to help.
> 
> It has been suggested that someone produce a homebrew recipe that
> would allow more

Yeah - that was me.

> "ordinary users" to compile and test the most recent versions, or
> even develop some system that would produce nightly, or perhaps
> weekly, builds. It would be best if this could be done for both
> trunk (2.1.dev) and branch (2.0.8dev, as things stand). Those

I agree. As I understand homebrew, the only difference wold be to
where the source is downloaded from (static URL, I think svn is also
possible, ...). I am looking "loosely" at the moment into the script,
and guess I will make slowly some progress. I will see that I setup a
github repo so that others can also work on it.

> of us on Linux can do this fairly easily, of course, but it's
> harder for people on OSX (or, God forbid, Windows). I confess that
> the one time I tried to

I agree. I was using Linux for more then 10 years and was very happy
with it - Ubuntu and Awesome window manager (
http://awesome.naquadah.org/ ) - a dream...

But then came the chance of getting a new laptop, and the Retia
display was there - well. and now I am using OSX.

But coming back, I am really missing the package management in Linux -
apt is so much easier then manually looking for updates, downloading
them, 

And then there came homebrew, which works very nicely, and does, in
contrast to Macports, not require root privileges.

I will keep you posted about the progress - and if somebody has any
experience with homebrew recipes, any input is welcome.

> compile LyX on OSX I failed and gave up.

Never tried it directly - only homebrew, and that works very smoothly.

Cheers,

Rainer


> 
> Richard
> 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS8KRnAAoJENvXNx4PUvmCknMH/1+DNMpiWvKT88Gr//8kNv/G
knT6fZGso9OLzFHXjs26GAMBlYDQaSlM8Du//WVGftk4kfdOnDnxyQHKUhspMZnI
e2dY8ZfoV2xOFG5x1kclkqtS6F0+/M7R9PpU5arD0HUoe6rXIfJe3rlPYn8WK2B/
uFnp9oVcWDtz/DcimBO6lzQAqP43QT3bYkFVuB78/nGU9Po/y08GxPm+9MtiySAe
PftI0OwK5bccje8Ou0xxpUCtMUAv4f0TVMM3Q1g3hpFHEFVCGDH953UyXOJrVfLX
qGV0lHQ0El9bEeP3aTyoesNJzM/QEinuv8KTCCdJ3ban+JglyurVI+bwgnwsGJI=
=ZdXW
-END PGP SIGNATURE-


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
http://www.macports.org/ports.php?by=name=lyx

I have not used MacPorts for LyX. I'm currently using 2.1beta2 which is not 
available there. I wonder if the maintainer could be cajoled into keeping a 
beta version as well.

Jerry

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 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 certain versions of OSX. 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 sorts of reasons. So, well,
 we could really use a couple people who could test the OSX version
 on a more regular basis.
 
 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 contrast to downloading and installing, or even
 compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how to 
 use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be interested
 in helping. But apparently, it is not that difficult.

I am using this to the devel lits as this does not (yet?) concern a
normal user.

Looking into this, I am wondering: what are the settings to create the
LyX binary for Mac? I could not find a hotwo on how to compile on mac?

Cheers,

Rainer


 
 Cheers,
 
 Rainer
 
 
 
 rh
 
 
 
 
 -- NEW GERMAN FAX NUMBER!!!
 
 Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation 
 Biology, UCT), Dipl. Phys. (Germany)
 
 Centre of Excellence for Invasion Biology Natural Sciences
 Building Office Suite 2039 Stellenbosch University Main Campus,
 Merriman Avenue Stellenbosch South Africa
 
 Cell:   +27 - (0)83 9479 042 Fax:+27 - (0)86
 516 2782 Fax:+49 - (0)321 2125 2244 email:
 rai...@krugs.de mailto:rai...@krugs.de
 
 Skype:  RMkrug Google: r.m.k...@gmail.com
 mailto:r.m.k...@gmail.com
 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEbBAEBAgAGBQJS72ezAAoJENvXNx4PUvmCMiMH+KTsEB7QKNoXQtDwVfTrFUuZ
GEyhhOVHFFpWY9tsDEaGtzFDoCRFL8gPtyxdSKurQiL9zg+WCg6vQdJK02PIhl9d
FvaQWzMEE71JhUJeHiSJyJc/jI38EeObZthnnOqf8BW8hpgbZOPdic5HWokGR1QP
oy02Y42z4/25PaHMu7Q3ZntQZc+Ix8/imBIXUrsYbXYiCx56RQleoOWH0gddznKa
06HbiDmQ4ff9JrqACWzhGunZQxmRUmbcxT9KvnlWisJp7KMTm4IPJxpMgGGZre4Z
W7IvLVq19eXk9ADjmol/zDjIEmAIiy7tJg/q10XECY997ML3hB6XKmAdzrnfJA==
=0uWO
-END PGP SIGNATURE-


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 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 certain versions of OSX. 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 sorts of reasons. So, well,
 we could really use a couple people who could test the OSX version
 on a more regular basis.
 
 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 contrast to downloading and installing, or even
 compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how to 
 use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be interested
 in helping. But apparently, it is not that difficult.
 
 I am using this to the devel lits as this does not (yet?) concern a
 normal user.
 
 Looking into this, I am wondering: what are the settings to create the
 LyX binary for Mac? I could not find a hotwo on how to compile on mac?

Possibly a little bit outdated - but did you consider INSTALL.MacOSX?

Stephan

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 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 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 certain versions of OSX. 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 sorts
 of reasons. So, well, we could really use a couple people who
 could test the OSX version on a more regular basis.
 
 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 contrast to downloading and
 installing, or even compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how
 to use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be
 interested in helping. But apparently, it is not that
 difficult.
 
 I am using this to the devel lits as this does not (yet?) concern
 a normal user.
 
 Looking into this, I am wondering: what are the settings to
 create the LyX binary for Mac? I could not find a hotwo on how to
 compile on mac?
 
 Possibly a little bit outdated - but did you consider
 INSTALL.MacOSX?

Shame on me - there it is, in the obvious place.

Thanks, I'll look into it,

Rainer

 
 Stephan
 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS73C6AAoJENvXNx4PUvmC6WYIALVbED9DGwDNo5x7gYpImJCZ
38UW5FRanH8vB5//i6KKBNFsT6/bNCBp4gcR0LjdppGWgM1fgnCBw+TUtDLDPL3j
FYOw7D71+5lQAMT+ZgkVwQX0hrGCF2AJa1vYEUfJygrSv48VrMHDdYpCaLAw/zj6
imqgk/rx6pzaml3otn+BdqGIFzrkhLkfeS+VF08WIWXBhcLOZDG1EFLhBzgagLsd
FP1PI3b0jH8O5xKu5UHrxGCVjVOOx1ZG7hhOXz5EknaPtgGaaOEUc3mdlfpfjIXR
TFD0F47n8jpuGHSqjAJ1EARvUKqZaijQkDnafE0gL9asvscqplSehQaZuzn9Jns=
=stBe
-END PGP SIGNATURE-


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 , 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 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 certain versions of OSX. 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 sorts
 of reasons. So, well, we could really use a couple people who
 could test the OSX version on a more regular basis.
 
 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 contrast to downloading and
 installing, or even compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how
 to use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be
 interested in helping. But apparently, it is not that
 difficult.
 
 I am using this to the devel lits as this does not (yet?) concern
 a normal user.
 
 Looking into this, I am wondering: what are the settings to
 create the LyX binary for Mac? I could not find a hotwo on how to
 compile on mac?
 
 Possibly a little bit outdated - but did you consider
 INSTALL.MacOSX?
 
 Shame on me - there it is, in the obvious place.
 
 Thanks, I'll look into it,

No problem. I'll happily update it's contents to reflect your
findings on this matter. For LyX 2.1.X e.g. the gettext requirement
doesn't exist anymore. The Qt version for production is 4.8.5.
For development I've tried 5.0, 5.1 and 5.2 too. 
Version 5.2 definitively doesn't work - the menu is missing
almost completely. On current Mac systems Qt-Carbon isn't
available anymore.

I'm using the script development/LyX-Mac-binary-release.sh.
Something like that (note the back slashes):

ARCH=x86_64
Qt4Version=4.8.5
Qt4API=-cocoa
LyXVersion=lyx-2.1.0beta2
QtConfigureOptions=-debug-and-release Qt4API=${Qt4API} 
Qt4Version=${Qt4Version} \
 sh ${LyXVersion}/development/LyX-Mac-binary-release.sh \
   --with-sdkroot=10.8 --with-macosx-target=10.6 --with-arch=${ARCH} \
   --with-qt4-dir=$HOME/lyx-build/qt-${Qt4Version}-frameworks${Qt4API}-${ARCH}

Stephan

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 sorts of reasons. So,
 well, we could really use a couple people who could test the OSX
 version on a more regular basis.

Well, I'm running 2.1.0 dev (with good stability) on both OS X 10.9
and Linux on a Chromebook (thanks to Crouton). Tell me what to do to
help.

-chris


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
of them use trunk (2.1.dev) for obvious sorts of reasons. So,
well, we could really use a couple people who could test the OSX
version on a more regular basis.

Well, I'm running 2.1.0 dev (with good stability) on both OS X 10.9
and Linux on a Chromebook (thanks to Crouton). Tell me what to do to
help.


It has been suggested that someone produce a homebrew recipe that would 
allow more
ordinary users to compile and test the most recent versions, or even 
develop some
system that would produce nightly, or perhaps weekly, builds. It would 
be best if this
could be done for both trunk (2.1.dev) and branch (2.0.8dev, as things 
stand). Those
of us on Linux can do this fairly easily, of course, but it's harder for 
people on OSX
(or, God forbid, Windows). I confess that the one time I tried to 
compile LyX on OSX

I failed and gave up.

Richard



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 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 certain versions of OSX. 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 sorts of reasons. So, well,
 we could really use a couple people who could test the OSX version
 on a more regular basis.
 
 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 contrast to downloading and installing, or even
 compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how to 
 use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be interested
 in helping. But apparently, it is not that difficult.

I am using this to the devel lits as this does not (yet?) concern a
normal user.

Looking into this, I am wondering: what are the settings to create the
LyX binary for Mac? I could not find a hotwo on how to compile on mac?

Cheers,

Rainer


 
 Cheers,
 
 Rainer
 
 
 
 rh
 
 
 
 
 -- NEW GERMAN FAX NUMBER!!!
 
 Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation 
 Biology, UCT), Dipl. Phys. (Germany)
 
 Centre of Excellence for Invasion Biology Natural Sciences
 Building Office Suite 2039 Stellenbosch University Main Campus,
 Merriman Avenue Stellenbosch South Africa
 
 Cell:   +27 - (0)83 9479 042 Fax:+27 - (0)86
 516 2782 Fax:+49 - (0)321 2125 2244 email:
 rai...@krugs.de mailto:rai...@krugs.de
 
 Skype:  RMkrug Google: r.m.k...@gmail.com
 mailto:r.m.k...@gmail.com
 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEbBAEBAgAGBQJS72ezAAoJENvXNx4PUvmCMiMH+KTsEB7QKNoXQtDwVfTrFUuZ
GEyhhOVHFFpWY9tsDEaGtzFDoCRFL8gPtyxdSKurQiL9zg+WCg6vQdJK02PIhl9d
FvaQWzMEE71JhUJeHiSJyJc/jI38EeObZthnnOqf8BW8hpgbZOPdic5HWokGR1QP
oy02Y42z4/25PaHMu7Q3ZntQZc+Ix8/imBIXUrsYbXYiCx56RQleoOWH0gddznKa
06HbiDmQ4ff9JrqACWzhGunZQxmRUmbcxT9KvnlWisJp7KMTm4IPJxpMgGGZre4Z
W7IvLVq19eXk9ADjmol/zDjIEmAIiy7tJg/q10XECY997ML3hB6XKmAdzrnfJA==
=0uWO
-END PGP SIGNATURE-


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 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 certain versions of OSX. 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 sorts of reasons. So, well,
 we could really use a couple people who could test the OSX version
 on a more regular basis.
 
 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 contrast to downloading and installing, or even
 compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how to 
 use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be interested
 in helping. But apparently, it is not that difficult.
 
 I am using this to the devel lits as this does not (yet?) concern a
 normal user.
 
 Looking into this, I am wondering: what are the settings to create the
 LyX binary for Mac? I could not find a hotwo on how to compile on mac?

Possibly a little bit outdated - but did you consider INSTALL.MacOSX?

Stephan

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 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 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 certain versions of OSX. 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 sorts
 of reasons. So, well, we could really use a couple people who
 could test the OSX version on a more regular basis.
 
 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 contrast to downloading and
 installing, or even compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how
 to use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be
 interested in helping. But apparently, it is not that
 difficult.
 
 I am using this to the devel lits as this does not (yet?) concern
 a normal user.
 
 Looking into this, I am wondering: what are the settings to
 create the LyX binary for Mac? I could not find a hotwo on how to
 compile on mac?
 
 Possibly a little bit outdated - but did you consider
 INSTALL.MacOSX?

Shame on me - there it is, in the obvious place.

Thanks, I'll look into it,

Rainer

 
 Stephan
 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS73C6AAoJENvXNx4PUvmC6WYIALVbED9DGwDNo5x7gYpImJCZ
38UW5FRanH8vB5//i6KKBNFsT6/bNCBp4gcR0LjdppGWgM1fgnCBw+TUtDLDPL3j
FYOw7D71+5lQAMT+ZgkVwQX0hrGCF2AJa1vYEUfJygrSv48VrMHDdYpCaLAw/zj6
imqgk/rx6pzaml3otn+BdqGIFzrkhLkfeS+VF08WIWXBhcLOZDG1EFLhBzgagLsd
FP1PI3b0jH8O5xKu5UHrxGCVjVOOx1ZG7hhOXz5EknaPtgGaaOEUc3mdlfpfjIXR
TFD0F47n8jpuGHSqjAJ1EARvUKqZaijQkDnafE0gL9asvscqplSehQaZuzn9Jns=
=stBe
-END PGP SIGNATURE-


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 , 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 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 certain versions of OSX. 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 sorts
 of reasons. So, well, we could really use a couple people who
 could test the OSX version on a more regular basis.
 
 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 contrast to downloading and
 installing, or even compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how
 to use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be
 interested in helping. But apparently, it is not that
 difficult.
 
 I am using this to the devel lits as this does not (yet?) concern
 a normal user.
 
 Looking into this, I am wondering: what are the settings to
 create the LyX binary for Mac? I could not find a hotwo on how to
 compile on mac?
 
 Possibly a little bit outdated - but did you consider
 INSTALL.MacOSX?
 
 Shame on me - there it is, in the obvious place.
 
 Thanks, I'll look into it,

No problem. I'll happily update it's contents to reflect your
findings on this matter. For LyX 2.1.X e.g. the gettext requirement
doesn't exist anymore. The Qt version for production is 4.8.5.
For development I've tried 5.0, 5.1 and 5.2 too. 
Version 5.2 definitively doesn't work - the menu is missing
almost completely. On current Mac systems Qt-Carbon isn't
available anymore.

I'm using the script development/LyX-Mac-binary-release.sh.
Something like that (note the back slashes):

ARCH=x86_64
Qt4Version=4.8.5
Qt4API=-cocoa
LyXVersion=lyx-2.1.0beta2
QtConfigureOptions=-debug-and-release Qt4API=${Qt4API} 
Qt4Version=${Qt4Version} \
 sh ${LyXVersion}/development/LyX-Mac-binary-release.sh \
   --with-sdkroot=10.8 --with-macosx-target=10.6 --with-arch=${ARCH} \
   --with-qt4-dir=$HOME/lyx-build/qt-${Qt4Version}-frameworks${Qt4API}-${ARCH}

Stephan

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 sorts of reasons. So,
 well, we could really use a couple people who could test the OSX
 version on a more regular basis.

Well, I'm running 2.1.0 dev (with good stability) on both OS X 10.9
and Linux on a Chromebook (thanks to Crouton). Tell me what to do to
help.

-chris


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
of them use trunk (2.1.dev) for obvious sorts of reasons. So,
well, we could really use a couple people who could test the OSX
version on a more regular basis.

Well, I'm running 2.1.0 dev (with good stability) on both OS X 10.9
and Linux on a Chromebook (thanks to Crouton). Tell me what to do to
help.


It has been suggested that someone produce a homebrew recipe that would 
allow more
ordinary users to compile and test the most recent versions, or even 
develop some
system that would produce nightly, or perhaps weekly, builds. It would 
be best if this
could be done for both trunk (2.1.dev) and branch (2.0.8dev, as things 
stand). Those
of us on Linux can do this fairly easily, of course, but it's harder for 
people on OSX
(or, God forbid, Windows). I confess that the one time I tried to 
compile LyX on OSX

I failed and gave up.

Richard



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 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 certain versions of OSX. 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 sorts of reasons. So, well,
> we could really use a couple people who could test the OSX version
> on a more regular basis.
> 
> 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 contrast to downloading and installing, or even
> compiling first.
> 
> 
> This is a great idea, but of course someone on OSX who knew how to 
> use homebrew would need to do it.
> 
> 
> I'll ask on the homebrew list if there would somebody be interested
> in helping. But apparently, it is not that difficult.

I am using this to the devel lits as this does not (yet?) concern a
"normal" user.

Looking into this, I am wondering: what are the settings to create the
LyX binary for Mac? I could not find a hotwo on how to compile on mac?

Cheers,

Rainer


> 
> Cheers,
> 
> Rainer
> 
> 
> 
> rh
> 
> 
> 
> 
> -- NEW GERMAN FAX NUMBER!!!
> 
> Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation 
> Biology, UCT), Dipl. Phys. (Germany)
> 
> Centre of Excellence for Invasion Biology Natural Sciences
> Building Office Suite 2039 Stellenbosch University Main Campus,
> Merriman Avenue Stellenbosch South Africa
> 
> Cell:   +27 - (0)83 9479 042 Fax:+27 - (0)86
> 516 2782 Fax:+49 - (0)321 2125 2244 email:
> rai...@krugs.de 
> 
> Skype:  RMkrug Google: r.m.k...@gmail.com
> 
> 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEbBAEBAgAGBQJS72ezAAoJENvXNx4PUvmCMiMH+KTsEB7QKNoXQtDwVfTrFUuZ
GEyhhOVHFFpWY9tsDEaGtzFDoCRFL8gPtyxdSKurQiL9zg+WCg6vQdJK02PIhl9d
FvaQWzMEE71JhUJeHiSJyJc/jI38EeObZthnnOqf8BW8hpgbZOPdic5HWokGR1QP
oy02Y42z4/25PaHMu7Q3ZntQZc+Ix8/imBIXUrsYbXYiCx56RQleoOWH0gddznKa
06HbiDmQ4ff9JrqACWzhGunZQxmRUmbcxT9KvnlWisJp7KMTm4IPJxpMgGGZre4Z
W7IvLVq19eXk9ADjmol/zDjIEmAIiy7tJg/q10XECY997ML3hB6XKmAdzrnfJA==
=0uWO
-END PGP SIGNATURE-


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 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 certain versions of OSX. 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 sorts of reasons. So, well,
>> we could really use a couple people who could test the OSX version
>> on a more regular basis.
>> 
>> 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 contrast to downloading and installing, or even
>> compiling first.
>> 
>> 
>> This is a great idea, but of course someone on OSX who knew how to 
>> use homebrew would need to do it.
>> 
>> 
>> I'll ask on the homebrew list if there would somebody be interested
>> in helping. But apparently, it is not that difficult.
> 
> I am using this to the devel lits as this does not (yet?) concern a
> "normal" user.
> 
> Looking into this, I am wondering: what are the settings to create the
> LyX binary for Mac? I could not find a hotwo on how to compile on mac?

Possibly a little bit outdated - but did you consider INSTALL.MacOSX?

Stephan

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 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.
>>> 
>>> As often, this is due to changes in the underlying Qt platform
>>> that seem to exist only on certain versions of OSX. 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 sorts
>>> of reasons. So, well, we could really use a couple people who
>>> could test the OSX version on a more regular basis.
>>> 
>>> 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 contrast to downloading and
>>> installing, or even compiling first.
>>> 
>>> 
>>> This is a great idea, but of course someone on OSX who knew how
>>> to use homebrew would need to do it.
>>> 
>>> 
>>> I'll ask on the homebrew list if there would somebody be
>>> interested in helping. But apparently, it is not that
>>> difficult.
>> 
>> I am using this to the devel lits as this does not (yet?) concern
>> a "normal" user.
>> 
>> Looking into this, I am wondering: what are the settings to
>> create the LyX binary for Mac? I could not find a hotwo on how to
>> compile on mac?
> 
> Possibly a little bit outdated - but did you consider
> INSTALL.MacOSX?

Shame on me - there it is, in the obvious place.

Thanks, I'll look into it,

Rainer

> 
> Stephan
> 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS73C6AAoJENvXNx4PUvmC6WYIALVbED9DGwDNo5x7gYpImJCZ
38UW5FRanH8vB5//i6KKBNFsT6/bNCBp4gcR0LjdppGWgM1fgnCBw+TUtDLDPL3j
FYOw7D71+5lQAMT+ZgkVwQX0hrGCF2AJa1vYEUfJygrSv48VrMHDdYpCaLAw/zj6
imqgk/rx6pzaml3otn+BdqGIFzrkhLkfeS+VF08WIWXBhcLOZDG1EFLhBzgagLsd
FP1PI3b0jH8O5xKu5UHrxGCVjVOOx1ZG7hhOXz5EknaPtgGaaOEUc3mdlfpfjIXR
TFD0F47n8jpuGHSqjAJ1EARvUKqZaijQkDnafE0gL9asvscqplSehQaZuzn9Jns=
=stBe
-END PGP SIGNATURE-


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
>>> 
>>> 
>>> 
>>> 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 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 certain versions of OSX. 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 sorts
 of reasons. So, well, we could really use a couple people who
 could test the OSX version on a more regular basis.
 
 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 contrast to downloading and
 installing, or even compiling first.
 
 
 This is a great idea, but of course someone on OSX who knew how
 to use homebrew would need to do it.
 
 
 I'll ask on the homebrew list if there would somebody be
 interested in helping. But apparently, it is not that
 difficult.
>>> 
>>> I am using this to the devel lits as this does not (yet?) concern
>>> a "normal" user.
>>> 
>>> Looking into this, I am wondering: what are the settings to
>>> create the LyX binary for Mac? I could not find a hotwo on how to
>>> compile on mac?
>> 
>> Possibly a little bit outdated - but did you consider
>> INSTALL.MacOSX?
> 
> Shame on me - there it is, in the obvious place.
> 
> Thanks, I'll look into it,

No problem. I'll happily update it's contents to reflect your
findings on this matter. For LyX 2.1.X e.g. the gettext requirement
doesn't exist anymore. The Qt version for production is 4.8.5.
For development I've tried 5.0, 5.1 and 5.2 too. 
Version 5.2 definitively doesn't work - the menu is missing
almost completely. On current Mac systems Qt-Carbon isn't
available anymore.

I'm using the script development/LyX-Mac-binary-release.sh.
Something like that (note the back slashes):

ARCH=x86_64
Qt4Version=4.8.5
Qt4API=-cocoa
LyXVersion=lyx-2.1.0beta2
QtConfigureOptions="-debug-and-release" Qt4API=${Qt4API} 
Qt4Version=${Qt4Version} \
 sh ${LyXVersion}/development/LyX-Mac-binary-release.sh \
   --with-sdkroot=10.8 --with-macosx-target=10.6 --with-arch=${ARCH} \
   --with-qt4-dir=$HOME/lyx-build/qt-${Qt4Version}-frameworks${Qt4API}-${ARCH}

Stephan

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 sorts of reasons. So,
> well, we could really use a couple people who could test the OSX
> version on a more regular basis.

Well, I'm running 2.1.0 dev (with good stability) on both OS X 10.9
and Linux on a Chromebook (thanks to Crouton). Tell me what to do to
help.

-chris


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
of them use trunk (2.1.dev) for obvious sorts of reasons. So,
well, we could really use a couple people who could test the OSX
version on a more regular basis.

Well, I'm running 2.1.0 dev (with good stability) on both OS X 10.9
and Linux on a Chromebook (thanks to Crouton). Tell me what to do to
help.


It has been suggested that someone produce a homebrew recipe that would 
allow more
"ordinary users" to compile and test the most recent versions, or even 
develop some
system that would produce nightly, or perhaps weekly, builds. It would 
be best if this
could be done for both trunk (2.1.dev) and branch (2.0.8dev, as things 
stand). Those
of us on Linux can do this fairly easily, of course, but it's harder for 
people on OSX
(or, God forbid, Windows). I confess that the one time I tried to 
compile LyX on OSX

I failed and gave up.

Richard



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 certain versions of OSX. 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 sorts of reasons. So,
well, we could really use a couple people who could test the OSX
version on a more regular basis.

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 contrast to downloading and installing, or even compiling
first.


This is a great idea, but of course someone on OSX who knew how to use 
homebrew would need to do it.


rh




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 contrast to downloading and installing, or even compiling
first.


This is a great idea, but of course someone on OSX who knew how to use
homebrew would need to do it.


Or find a service somewhere that would build nightlies for us...

JMarc



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
 me, I would likely use (and update) it regularly  as it is no hassle
 at all (in contrast to downloading and installing, or even compiling
 first.


 This is a great idea, but of course someone on OSX who knew how to use
 homebrew would need to do it.


 Or find a service somewhere that would build nightlies for us...


This together with an update function from within LyX would work as well -
but the update from within LyX would be important  as otherwise one has to
manually visit the website and download to update.

Cheers,

Rainer


 JMarc



-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax (F):   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug


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 due to changes in the underlying Qt platform
 that seem to exist only on certain versions of OSX. 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 sorts of reasons. So,
 well, we could really use a couple people who could test the OSX
 version on a more regular basis.

 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 contrast to downloading and installing, or even compiling
 first.


 This is a great idea, but of course someone on OSX who knew how to use
 homebrew would need to do it.


I'll ask on the homebrew list if there would somebody be interested in
helping. But apparently, it is not that difficult.

Cheers,

Rainer



 rh




-- 
NEW GERMAN FAX NUMBER!!!

Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa

Cell:   +27 - (0)83 9479 042
Fax:+27 - (0)86 516 2782
Fax:+49 - (0)321 2125 2244
email:  rai...@krugs.de

Skype:  RMkrug
Google: r.m.k...@gmail.com


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 certain versions of OSX. 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 sorts of reasons. So,
well, we could really use a couple people who could test the OSX
version on a more regular basis.

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 contrast to downloading and installing, or even compiling
first.


This is a great idea, but of course someone on OSX who knew how to use 
homebrew would need to do it.


rh




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 contrast to downloading and installing, or even compiling
first.


This is a great idea, but of course someone on OSX who knew how to use
homebrew would need to do it.


Or find a service somewhere that would build nightlies for us...

JMarc



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
 me, I would likely use (and update) it regularly  as it is no hassle
 at all (in contrast to downloading and installing, or even compiling
 first.


 This is a great idea, but of course someone on OSX who knew how to use
 homebrew would need to do it.


 Or find a service somewhere that would build nightlies for us...


This together with an update function from within LyX would work as well -
but the update from within LyX would be important  as otherwise one has to
manually visit the website and download to update.

Cheers,

Rainer


 JMarc



-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax (F):   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug


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 due to changes in the underlying Qt platform
 that seem to exist only on certain versions of OSX. 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 sorts of reasons. So,
 well, we could really use a couple people who could test the OSX
 version on a more regular basis.

 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 contrast to downloading and installing, or even compiling
 first.


 This is a great idea, but of course someone on OSX who knew how to use
 homebrew would need to do it.


I'll ask on the homebrew list if there would somebody be interested in
helping. But apparently, it is not that difficult.

Cheers,

Rainer



 rh




-- 
NEW GERMAN FAX NUMBER!!!

Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa

Cell:   +27 - (0)83 9479 042
Fax:+27 - (0)86 516 2782
Fax:+49 - (0)321 2125 2244
email:  rai...@krugs.de

Skype:  RMkrug
Google: r.m.k...@gmail.com


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 certain versions of OSX. 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 sorts of reasons. So,
well, we could really use a couple people who could test the OSX
version on a more regular basis.

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 contrast to downloading and installing, or even compiling
first.


This is a great idea, but of course someone on OSX who knew how to use 
homebrew would need to do it.


rh




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 contrast to downloading and installing, or even compiling
first.


This is a great idea, but of course someone on OSX who knew how to use
homebrew would need to do it.


Or find a service somewhere that would build nightlies for us...

JMarc



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 LyX? At least for
>>> me, I would likely use (and update) it regularly  as it is no hassle
>>> at all (in contrast to downloading and installing, or even compiling
>>> first.
>>>
>>
>> This is a great idea, but of course someone on OSX who knew how to use
>> homebrew would need to do it.
>>
>
> Or find a service somewhere that would build nightlies for us...


This together with an update function from within LyX would work as well -
but the update from within LyX would be important  as otherwise one has to
manually visit the website and download to update.

Cheers,

Rainer

>
> JMarc
>
>

-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax (F):   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug


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.

>>> As often, this is due to changes in the underlying Qt platform
>>> that seem to exist only on certain versions of OSX. 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 sorts of reasons. So,
>>> well, we could really use a couple people who could test the OSX
>>> version on a more regular basis.
>>>
>> 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 contrast to downloading and installing, or even compiling
>> first.
>>
>
> This is a great idea, but of course someone on OSX who knew how to use
> homebrew would need to do it.


I'll ask on the homebrew list if there would somebody be interested in
helping. But apparently, it is not that difficult.

Cheers,

Rainer


>
> rh
>
>
>

-- 
NEW GERMAN FAX NUMBER!!!

Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa

Cell:   +27 - (0)83 9479 042
Fax:+27 - (0)86 516 2782
Fax:+49 - (0)321 2125 2244
email:  rai...@krugs.de

Skype:  RMkrug
Google: r.m.k...@gmail.com


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 on certain versions of OSX. 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 sorts of reasons. So,
 well, we could really use a couple people who could test the OSX
 version on a more regular basis.

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 contrast to downloading and installing, or even compiling
first.

Cheers,

Rainer

 I use the 2.0.x branch, on Linux, for all my work, so I always
 have the latest updates, and the latest bugs, too ;-) Lots of
 Linux people do this, and so we always have a very up-to-date
 picture of how things are there. As a result, there are rarely
 surprise bugs on Linux. If you can compile, then it is actually
 very easy. Check out the 2.0.x branch via git, then compile it
 manually or set up a cron job to keep it up to date, if you really
 want to be hi-tech.
 
 As Scott said, we will release an updated version shortly. There's 
 a fix for this issue already in branch, if you want to check that 
 out, though it apparently causes other problems. For now, you may 
 want to go back to 2.0.6.
 
 Richard Heck Branch Maintainer
 
 
 
 Scott
 
 On Tue, Jan 28, 2014 at 3:09 PM, Anders Ekberg a...@mac.com 
 wrote:
 Here too w OS X 10.9.1
 
 /Anders
 
 
 -Original Message- From: David Nuddleman 
 da...@xsharp.com Date: tisdag 28 januari 2014 20:51 To: 
 lyx-users@lists.lyx.org Subject: menu bar lost in OS X
 
 Major disappointment LyX 2.0.7,  on OS X 10.7.5 Mac Pro 1,1: 
 Full screen causes application menu bar options list to go 
 blank. Return from full screen does not restore list.
 
 1. Normal options present until fullscreen invoked.
 
 2. LyX 2.0.6 performs normally.
 
 Posted ticket tracker #8942 on January 25. Anyone else
 notice this?
 
 -- 
 
 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS6geYAAoJENvXNx4PUvmC1QUH/jMiJrPt3t0a2VvNhvfRRehI
CMed1fVsVVAy3d2TssVJJBFBAScsGgN4bREWWNBy++kEddcDocUiVpl3SvHMa24f
kV14QRLa03do5bb2A5+lwG260Mt57OzP7ZRxuAZPcrhYvMXk6tVqCxLtcyLFMju7
JtozBe9+ImWdrq8a95UPHUMZLLA03BEaFb5Nzr1N0iEftZkCG4FCA4ddChC/iDNf
Nlr7rpYqDoq9Sm0V7zxvIU0mwfQbkYFk8A8cxNrgY+rf0HiT3DBXQjUY08vrq5zW
+PYy89kR46oF83o8CsAV2kUtAwtqSCOs/4XuW8noeeEQ5QYzwk7kMsYJsSuz+5k=
=vAlX
-END PGP SIGNATURE-


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 on certain versions of OSX. 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 sorts of reasons. So,
 well, we could really use a couple people who could test the OSX
 version on a more regular basis.

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 contrast to downloading and installing, or even compiling
first.

Cheers,

Rainer

 I use the 2.0.x branch, on Linux, for all my work, so I always
 have the latest updates, and the latest bugs, too ;-) Lots of
 Linux people do this, and so we always have a very up-to-date
 picture of how things are there. As a result, there are rarely
 surprise bugs on Linux. If you can compile, then it is actually
 very easy. Check out the 2.0.x branch via git, then compile it
 manually or set up a cron job to keep it up to date, if you really
 want to be hi-tech.
 
 As Scott said, we will release an updated version shortly. There's 
 a fix for this issue already in branch, if you want to check that 
 out, though it apparently causes other problems. For now, you may 
 want to go back to 2.0.6.
 
 Richard Heck Branch Maintainer
 
 
 
 Scott
 
 On Tue, Jan 28, 2014 at 3:09 PM, Anders Ekberg a...@mac.com 
 wrote:
 Here too w OS X 10.9.1
 
 /Anders
 
 
 -Original Message- From: David Nuddleman 
 da...@xsharp.com Date: tisdag 28 januari 2014 20:51 To: 
 lyx-users@lists.lyx.org Subject: menu bar lost in OS X
 
 Major disappointment LyX 2.0.7,  on OS X 10.7.5 Mac Pro 1,1: 
 Full screen causes application menu bar options list to go 
 blank. Return from full screen does not restore list.
 
 1. Normal options present until fullscreen invoked.
 
 2. LyX 2.0.6 performs normally.
 
 Posted ticket tracker #8942 on January 25. Anyone else
 notice this?
 
 -- 
 
 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS6geYAAoJENvXNx4PUvmC1QUH/jMiJrPt3t0a2VvNhvfRRehI
CMed1fVsVVAy3d2TssVJJBFBAScsGgN4bREWWNBy++kEddcDocUiVpl3SvHMa24f
kV14QRLa03do5bb2A5+lwG260Mt57OzP7ZRxuAZPcrhYvMXk6tVqCxLtcyLFMju7
JtozBe9+ImWdrq8a95UPHUMZLLA03BEaFb5Nzr1N0iEftZkCG4FCA4ddChC/iDNf
Nlr7rpYqDoq9Sm0V7zxvIU0mwfQbkYFk8A8cxNrgY+rf0HiT3DBXQjUY08vrq5zW
+PYy89kR46oF83o8CsAV2kUtAwtqSCOs/4XuW8noeeEQ5QYzwk7kMsYJsSuz+5k=
=vAlX
-END PGP SIGNATURE-


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 on certain versions of OSX. 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 sorts of reasons. So,
> well, we could really use a couple people who could test the OSX
> version on a more regular basis.

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 contrast to downloading and installing, or even compiling
first.

Cheers,

Rainer

> I use the 2.0.x branch, on Linux, for all my work, so I always
> have the latest updates, and the latest bugs, too ;-) Lots of
> Linux people do this, and so we always have a very up-to-date
> picture of how things are there. As a result, there are rarely
> surprise bugs on Linux. If you can compile, then it is actually
> very easy. Check out the 2.0.x branch via git, then compile it
> manually or set up a cron job to keep it up to date, if you really
> want to be hi-tech.
> 
> As Scott said, we will release an updated version shortly. There's 
> a fix for this issue already in branch, if you want to check that 
> out, though it apparently causes other problems. For now, you may 
> want to go back to 2.0.6.
> 
> Richard Heck Branch Maintainer
> 
> 
>> 
>> Scott
>> 
>> On Tue, Jan 28, 2014 at 3:09 PM, Anders Ekberg  
>> wrote:
>>> Here too w OS X 10.9.1
>>> 
>>> /Anders
>>> 
>>> 
>>> -Original Message- From: David Nuddleman 
>>>  Date: tisdag 28 januari 2014 20:51 To: 
>>>  Subject: menu bar lost in OS X
>>> 
 Major disappointment LyX 2.0.7,  on OS X 10.7.5 Mac Pro 1,1: 
 Full screen causes application menu bar options list to go 
 blank. Return from full screen does not restore list.
 
 1. Normal options present until fullscreen invoked.
 
 2. LyX 2.0.6 performs normally.
 
 Posted ticket tracker #8942 on January 25. Anyone else
 notice this?
 
 -- &&
>>> 
> 

- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :   +33 - (0)9 53 10 27 44
Cell:   +33 - (0)6 85 62 59 98
Fax :   +33 - (0)9 58 10 27 44

Fax (D):+49 - (0)3 21 21 25 22 44

email:  rai...@krugs.de

Skype:  RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS6geYAAoJENvXNx4PUvmC1QUH/jMiJrPt3t0a2VvNhvfRRehI
CMed1fVsVVAy3d2TssVJJBFBAScsGgN4bREWWNBy++kEddcDocUiVpl3SvHMa24f
kV14QRLa03do5bb2A5+lwG260Mt57OzP7ZRxuAZPcrhYvMXk6tVqCxLtcyLFMju7
JtozBe9+ImWdrq8a95UPHUMZLLA03BEaFb5Nzr1N0iEftZkCG4FCA4ddChC/iDNf
Nlr7rpYqDoq9Sm0V7zxvIU0mwfQbkYFk8A8cxNrgY+rf0HiT3DBXQjUY08vrq5zW
+PYy89kR46oF83o8CsAV2kUtAwtqSCOs/4XuW8noeeEQ5QYzwk7kMsYJsSuz+5k=
=vAlX
-END PGP SIGNATURE-


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 read configuration file

Error while reading the configuration file
preferences.
Please check your installation.

and LyX is not showing up.

Does somebody know what I should check in the installation?

not yet done:
4) make install
   will install it. 

Thanks,

Wolfgang


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.
 
   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 read configuration file
 
 Error while reading the configuration file
 preferences.
 Please check your installation.
 
 and LyX is not showing up.
 
 Does somebody know what I should check in the installation?
 
 not yet done:
   4) make install
  will install it.
 
 Thanks,
 
 Wolfgang


-- 
-
Wolfgang Engelmann
Schlossgartenstrasse 22
D-72070 Tübingen
Tel 07071 68325


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 directory to build LyX. Like that:

$ mkdir lyxhome
$ cd lyxhome
$ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
$ mkdir lyx-build
$ cd lyx-build
$ ../lyx-2.0.6/configure
$ make
$ src/lyx

Stephan

  
   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 read configuration file
 
 Error while reading the configuration file
 preferences.
 Please check your installation.
  
 and LyX is not showing up.
  
 Does somebody know what I should check in the installation?
  
 not yet done:
   4) make install
  will install it. 
  
 Thanks,
  
 Wolfgang
  



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 idea to build in source tree.


 
 You should make a separate build directory to build LyX. Like that:
 
 $ mkdir lyxhome
 $ cd lyxhome
 $ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
 $ mkdir lyx-build
 $ cd lyx-build
 $ ../lyx-2.0.6/configure
 $ make
 $ src/lyx

Thats what I did !

I used in my home 
/lyx-2.0.6
and compiled there.

But as in my last mail the issue is solved now, after removing the .lyx 
folder.

Thanks

Wolfgang


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
 
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 directory to build LyX. Like that:
  
  $ mkdir lyxhome
  $ cd lyxhome
  $ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
  $ mkdir lyx-build
  $ cd lyx-build
  $ ../lyx-2.0.6/configure
  $ make
  $ src/lyx
  
 Thats what I did !
  
 I used in my home 
 /lyx-2.0.6
 and compiled there.

Ok, I thought you used the source tree because of the ./configure step 
in your previous mail. 

 But as in my last mail the issue is solved now, after removing the .lyx 
 folder.

Yes, that's fine. But this should only be a problem if the contents of this 
folder was written by LyX 2.1.

Stephan

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 a good idea to build in source tree.
 
 You should make a separate build directory to build LyX. Like that:
 
 $ mkdir lyxhome
 $ cd lyxhome
 $ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
 $ mkdir lyx-build
 $ cd lyx-build
 $ ../lyx-2.0.6/configure
 $ make
 $ src/lyx
 
 Stephan


Hi Stephan,

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 ./configure;make;make_install?

Once upon a time I built LyX in such a way that make distclean and make
clean didn't take out ghosts of compiles past, and I had to rm -rf and
tar again:

http://www.mail-archive.com/lyx-users@lists.lyx.org/msg62008.html
Could doing it your way, with a separate build directory, avoid that
problem? Is that why you're recommending it?

Thanks,

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


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 ./configure;make;make_install?


I would recommend building out of source tree any package. Package which 
do not support this are buggy IMO. In theory, you can set your source 
directory tree to read-only and still compile.


The advantage is that starting from scratch is trivial. This is even 
more important when compiling from a git check out, where you do not 
want old file to cause problems. In this case a rm -rf * (or the 
windows equivalent that I forgot (deltree?)), will start over cleanly.


JMarc


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
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 directory to build LyX. Like that:
 
 $ mkdir lyxhome
 $ cd lyxhome
 $ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
 $ mkdir lyx-build
 $ cd lyx-build
 $ ../lyx-2.0.6/configure
 $ make
 $ src/lyx
 
 Stephan
 
 
 Hi Stephan,
 
 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 ./configure;make;make_install?
 
 Once upon a time I built LyX in such a way that make distclean and make
 clean didn't take out ghosts of compiles past, and I had to rm -rf and
 tar again:
 
 http://www.mail-archive.com/lyx-users@lists.lyx.org/msg62008.html
 Could doing it your way, with a separate build directory, avoid that
 problem? Is that why you're recommending it?

Yes, this is the reason. Sometimes it doesn't help to avoid the modification
of the source tree completely. It happens the .po files need a rebuild and this
is only possible in-place in the source tree.

Stephan

 
 Thanks,
 
 SteveT
 
 Steve Litt*  http://www.troubleshooters.com/
 Troubleshooting Training  *  Human Performance



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 read configuration file

Error while reading the configuration file
preferences.
Please check your installation.

and LyX is not showing up.

Does somebody know what I should check in the installation?

not yet done:
4) make install
   will install it. 

Thanks,

Wolfgang


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.
 
   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 read configuration file
 
 Error while reading the configuration file
 preferences.
 Please check your installation.
 
 and LyX is not showing up.
 
 Does somebody know what I should check in the installation?
 
 not yet done:
   4) make install
  will install it.
 
 Thanks,
 
 Wolfgang


-- 
-
Wolfgang Engelmann
Schlossgartenstrasse 22
D-72070 Tübingen
Tel 07071 68325


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 directory to build LyX. Like that:

$ mkdir lyxhome
$ cd lyxhome
$ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
$ mkdir lyx-build
$ cd lyx-build
$ ../lyx-2.0.6/configure
$ make
$ src/lyx

Stephan

  
   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 read configuration file
 
 Error while reading the configuration file
 preferences.
 Please check your installation.
  
 and LyX is not showing up.
  
 Does somebody know what I should check in the installation?
  
 not yet done:
   4) make install
  will install it. 
  
 Thanks,
  
 Wolfgang
  



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 idea to build in source tree.


 
 You should make a separate build directory to build LyX. Like that:
 
 $ mkdir lyxhome
 $ cd lyxhome
 $ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
 $ mkdir lyx-build
 $ cd lyx-build
 $ ../lyx-2.0.6/configure
 $ make
 $ src/lyx

Thats what I did !

I used in my home 
/lyx-2.0.6
and compiled there.

But as in my last mail the issue is solved now, after removing the .lyx 
folder.

Thanks

Wolfgang


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
 
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 directory to build LyX. Like that:
  
  $ mkdir lyxhome
  $ cd lyxhome
  $ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
  $ mkdir lyx-build
  $ cd lyx-build
  $ ../lyx-2.0.6/configure
  $ make
  $ src/lyx
  
 Thats what I did !
  
 I used in my home 
 /lyx-2.0.6
 and compiled there.

Ok, I thought you used the source tree because of the ./configure step 
in your previous mail. 

 But as in my last mail the issue is solved now, after removing the .lyx 
 folder.

Yes, that's fine. But this should only be a problem if the contents of this 
folder was written by LyX 2.1.

Stephan

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 a good idea to build in source tree.
 
 You should make a separate build directory to build LyX. Like that:
 
 $ mkdir lyxhome
 $ cd lyxhome
 $ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
 $ mkdir lyx-build
 $ cd lyx-build
 $ ../lyx-2.0.6/configure
 $ make
 $ src/lyx
 
 Stephan


Hi Stephan,

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 ./configure;make;make_install?

Once upon a time I built LyX in such a way that make distclean and make
clean didn't take out ghosts of compiles past, and I had to rm -rf and
tar again:

http://www.mail-archive.com/lyx-users@lists.lyx.org/msg62008.html
Could doing it your way, with a separate build directory, avoid that
problem? Is that why you're recommending it?

Thanks,

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


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 ./configure;make;make_install?


I would recommend building out of source tree any package. Package which 
do not support this are buggy IMO. In theory, you can set your source 
directory tree to read-only and still compile.


The advantage is that starting from scratch is trivial. This is even 
more important when compiling from a git check out, where you do not 
want old file to cause problems. In this case a rm -rf * (or the 
windows equivalent that I forgot (deltree?)), will start over cleanly.


JMarc


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
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 directory to build LyX. Like that:
 
 $ mkdir lyxhome
 $ cd lyxhome
 $ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
 $ mkdir lyx-build
 $ cd lyx-build
 $ ../lyx-2.0.6/configure
 $ make
 $ src/lyx
 
 Stephan
 
 
 Hi Stephan,
 
 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 ./configure;make;make_install?
 
 Once upon a time I built LyX in such a way that make distclean and make
 clean didn't take out ghosts of compiles past, and I had to rm -rf and
 tar again:
 
 http://www.mail-archive.com/lyx-users@lists.lyx.org/msg62008.html
 Could doing it your way, with a separate build directory, avoid that
 problem? Is that why you're recommending it?

Yes, this is the reason. Sometimes it doesn't help to avoid the modification
of the source tree completely. It happens the .po files need a rebuild and this
is only possible in-place in the source tree.

Stephan

 
 Thanks,
 
 SteveT
 
 Steve Litt*  http://www.troubleshooters.com/
 Troubleshooting Training  *  Human Performance



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 read configuration file

Error while reading the configuration file
preferences.
Please check your installation.

and LyX is not showing up.

Does somebody know what I should check in the installation?

not yet done:
4) make install
   will install it. 

Thanks,

Wolfgang


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.
> 
>   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 read configuration file
> 
> Error while reading the configuration file
> preferences.
> Please check your installation.
> 
> and LyX is not showing up.
> 
> Does somebody know what I should check in the installation?
> 
> not yet done:
>   4) make install
>  will install it.
> 
> Thanks,
> 
> Wolfgang


-- 
-
Wolfgang Engelmann
Schlossgartenstrasse 22
D-72070 Tübingen
Tel 07071 68325


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 directory to build LyX. Like that:

$ mkdir lyxhome
$ cd lyxhome
$ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
$ mkdir lyx-build
$ cd lyx-build
$ ../lyx-2.0.6/configure
$ make
$ src/lyx

Stephan

>  
>   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 read configuration file
> 
> Error while reading the configuration file
> preferences.
> Please check your installation.
>  
> and LyX is not showing up.
>  
> Does somebody know what I should check in the installation?
>  
> not yet done:
>   4) make install
>  will install it. 
>  
> Thanks,
>  
> Wolfgang
>  



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,
> 
> it's not a good idea to build in source tree.


> 
> You should make a separate build directory to build LyX. Like that:
> 
> $ mkdir lyxhome
> $ cd lyxhome
> $ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
> $ mkdir lyx-build
> $ cd lyx-build
> $ ../lyx-2.0.6/configure
> $ make
> $ src/lyx

Thats what I did !

I used in my home 
/lyx-2.0.6
and compiled there.

But as in my last mail the issue is solved now, after removing the .lyx 
folder.

Thanks

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) ./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 directory to build LyX. Like that:
> > 
> > $ mkdir lyxhome
> > $ cd lyxhome
> > $ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
> > $ mkdir lyx-build
> > $ cd lyx-build
> > $ ../lyx-2.0.6/configure
> > $ make
> > $ src/lyx
>  
> Thats what I did !
>  
> I used in my home 
> /lyx-2.0.6
> and compiled there.

Ok, I thought you used the source tree because of the "./configure" step 
in your previous mail. 

> But as in my last mail the issue is solved now, after removing the .lyx 
> folder.

Yes, that's fine. But this should only be a problem if the contents of this 
folder was written by LyX 2.1.

Stephan

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 Wolfgang,
> 
> it's not a good idea to build in source tree.
> 
> You should make a separate build directory to build LyX. Like that:
> 
> $ mkdir lyxhome
> $ cd lyxhome
> $ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
> $ mkdir lyx-build
> $ cd lyx-build
> $ ../lyx-2.0.6/configure
> $ make
> $ src/lyx
> 
> Stephan


Hi Stephan,

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 ./configure;make;make_install?

Once upon a time I built LyX in such a way that make distclean and make
clean didn't take out ghosts of compiles past, and I had to rm -rf and
tar again:

http://www.mail-archive.com/lyx-users@lists.lyx.org/msg62008.html
Could doing it your way, with a separate build directory, avoid that
problem? Is that why you're recommending it?

Thanks,

SteveT

Steve Litt*  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance


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 ./configure;make;make_install?


I would recommend building out of source tree any package. Package which 
do not support this are buggy IMO. In theory, you can set your source 
directory tree to read-only and still compile.


The advantage is that starting from scratch is trivial. This is even 
more important when compiling from a git check out, where you do not 
want old file to cause problems. In this case a "rm -rf *" (or the 
windows equivalent that I forgot (deltree?)), will start over cleanly.


JMarc


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
>>> 
>>> 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 directory to build LyX. Like that:
>> 
>> $ mkdir lyxhome
>> $ cd lyxhome
>> $ tar xfz ${download_dir}/lyx-2.0.6.tar.gz
>> $ mkdir lyx-build
>> $ cd lyx-build
>> $ ../lyx-2.0.6/configure
>> $ make
>> $ src/lyx
>> 
>> Stephan
> 
> 
> Hi Stephan,
> 
> 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 ./configure;make;make_install?
> 
> Once upon a time I built LyX in such a way that make distclean and make
> clean didn't take out ghosts of compiles past, and I had to rm -rf and
> tar again:
> 
> http://www.mail-archive.com/lyx-users@lists.lyx.org/msg62008.html
> Could doing it your way, with a separate build directory, avoid that
> problem? Is that why you're recommending it?

Yes, this is the reason. Sometimes it doesn't help to avoid the modification
of the source tree completely. It happens the .po files need a rebuild and this
is only possible in-place in the source tree.

Stephan

> 
> Thanks,
> 
> SteveT
> 
> Steve Litt*  http://www.troubleshooters.com/
> Troubleshooting Training  *  Human Performance



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)

 Yes. In the LyX source file, that is. In the LyX workarea, we have (siht)
 in
 all cases.



When I'm typing Hebrew, I want to open braces by typing Shift+0  and close
by Shift+9
When I'm typing English, I want to open braces with Shift+0 and close with
Shift+0

I'm not sure what you mean by correct input .


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)

 Yes. In the LyX source file, that is. In the LyX workarea, we have (siht)
 in
 all cases.



When I'm typing Hebrew, I want to open braces by typing Shift+0  and close
by Shift+9
When I'm typing English, I want to open braces with Shift+0 and close with
Shift+0

I'm not sure what you mean by correct input .


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(   for Hebrew (babel)
>
> Yes. In the LyX source file, that is. In the LyX workarea, we have (siht)
> in
> all cases.
>
>

When I'm typing Hebrew, I want to open braces by typing Shift+0  and close
by Shift+9
When I'm typing English, I want to open braces with Shift+0 and close with
Shift+0

I'm not sure what you mean by "correct input" .


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 we have )siht( in the LyX source for Hebrew and (siht) for Arabic.]

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)

I would prefer if the LyX input were (siht) for both, Hebrew and
Arabic, regardless of the language package.

 IMO, this is a polyglossia feature. It may be regarded as a regression, if
 we fix it to behave like babel:

 However, the applied patch seems to do exactly this. Whether it is a
 fix or a regression depends on the use case.

  + documents written for babel also work with polyglossia,
  - text pasted from other applications now fails with both, babel and
polyglossia.

 Please correct me if I am wrong. 

 The patch does not touch the input (neither the input method nor the 
 representation in the LyX source and window), we just adapt the output if we 
 output to LaTeX with polyglossia. So I do not think anything will change 
 (except the output with polyglossia will be correct).

The patch changes the output, i.e. if someone uses the input convention
used in other Unicode editors and also in Arabic, the output will be wrong
with LyX. 

In this sense, it changes which input is required to get the correct output:

* You will get the correct output with polyglossia for documents intended for
  Hebrew (babel).
  
* You will get the wrong output with polyglossia for existing documents that
  used to work with Hebrew (polyglossia).

* You will get the wrong output with polyglossia for text inserted from
  OpenOffice or similar sources.  

It fixes one problem but creates two others, this is why I consider this
a regression.

A possible fix would be to toggle the parantheses whenever the document
settings change between use of babel and polyglossia or a function that
does so on user request. Also, the different input conventions and the
reasoning behind them should be documented.

Günter



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) in 
all cases.

The main difference, from a user POV, is that in Arabic you have to press ')' 
for an opening bracket (to get ')' in the LyX window), while in Hebrew you 
have to press '('. This has been the case since support for these languages 
was introduced. I find this also irritating, but maybe these are simply 
different input conventions, logical versus visual (I have added a FIXME that 
requests clarification).

As far as pating is concerned, your should always get (siht) (in the LyX 
window) when you paste (siht). I have not tested this, but the patch also does 
not change this.

 I would prefer if the LyX input were (siht) for both, Hebrew and
 Arabic, regardless of the language package.

Me, too. But then, I'm neither a Hebrew nor an Arabic writer.

 The patch changes the output, i.e. if someone uses the input convention
 used in other Unicode editors and also in Arabic, the output will be wrong
 with LyX.

I don't think this is true.

 In this sense, it changes which input is required to get the correct output:
 
 * You will get the correct output with polyglossia for documents intended
 for Hebrew (babel).
 
 * You will get the wrong output with polyglossia for existing documents that
 used to work with Hebrew (polyglossia).
 
 * You will get the wrong output with polyglossia for text inserted from
   OpenOffice or similar sources.

Can you provide an example?

Jürgen



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 we have )siht( in the LyX source for Hebrew and (siht) for Arabic.]

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)

I would prefer if the LyX input were (siht) for both, Hebrew and
Arabic, regardless of the language package.

 IMO, this is a polyglossia feature. It may be regarded as a regression, if
 we fix it to behave like babel:

 However, the applied patch seems to do exactly this. Whether it is a
 fix or a regression depends on the use case.

  + documents written for babel also work with polyglossia,
  - text pasted from other applications now fails with both, babel and
polyglossia.

 Please correct me if I am wrong. 

 The patch does not touch the input (neither the input method nor the 
 representation in the LyX source and window), we just adapt the output if we 
 output to LaTeX with polyglossia. So I do not think anything will change 
 (except the output with polyglossia will be correct).

The patch changes the output, i.e. if someone uses the input convention
used in other Unicode editors and also in Arabic, the output will be wrong
with LyX. 

In this sense, it changes which input is required to get the correct output:

* You will get the correct output with polyglossia for documents intended for
  Hebrew (babel).
  
* You will get the wrong output with polyglossia for existing documents that
  used to work with Hebrew (polyglossia).

* You will get the wrong output with polyglossia for text inserted from
  OpenOffice or similar sources.  

It fixes one problem but creates two others, this is why I consider this
a regression.

A possible fix would be to toggle the parantheses whenever the document
settings change between use of babel and polyglossia or a function that
does so on user request. Also, the different input conventions and the
reasoning behind them should be documented.

Günter



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) in 
all cases.

The main difference, from a user POV, is that in Arabic you have to press ')' 
for an opening bracket (to get ')' in the LyX window), while in Hebrew you 
have to press '('. This has been the case since support for these languages 
was introduced. I find this also irritating, but maybe these are simply 
different input conventions, logical versus visual (I have added a FIXME that 
requests clarification).

As far as pating is concerned, your should always get (siht) (in the LyX 
window) when you paste (siht). I have not tested this, but the patch also does 
not change this.

 I would prefer if the LyX input were (siht) for both, Hebrew and
 Arabic, regardless of the language package.

Me, too. But then, I'm neither a Hebrew nor an Arabic writer.

 The patch changes the output, i.e. if someone uses the input convention
 used in other Unicode editors and also in Arabic, the output will be wrong
 with LyX.

I don't think this is true.

 In this sense, it changes which input is required to get the correct output:
 
 * You will get the correct output with polyglossia for documents intended
 for Hebrew (babel).
 
 * You will get the wrong output with polyglossia for existing documents that
 used to work with Hebrew (polyglossia).
 
 * You will get the wrong output with polyglossia for text inserted from
   OpenOffice or similar sources.

Can you provide an example?

Jürgen



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 we have )siht( in the LyX source for Hebrew and (siht) for Arabic.]

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)

I would prefer if the LyX input were "(siht)" for both, Hebrew and
Arabic, regardless of the language package.

>> IMO, this is a polyglossia feature. It may be regarded as a regression, if
>> we "fix" it to behave like babel:

>> However, the applied patch seems to do exactly this. Whether it is a
>> "fix" or a "regression" depends on the use case.

>>  + documents written for babel also work with polyglossia,
>>  - text pasted from other applications now fails with both, babel and
>>polyglossia.

>> Please correct me if I am wrong. 

> The patch does not touch the input (neither the input method nor the 
> representation in the LyX source and window), we just adapt the output if we 
> output to LaTeX with polyglossia. So I do not think anything will change 
> (except the output with polyglossia will be correct).

The patch changes the output, i.e. if someone uses the input convention
used in other Unicode editors and also in Arabic, the output will be wrong
with LyX. 

In this sense, it changes which input is required to get the correct output:

* You will get the correct output with polyglossia for documents intended for
  Hebrew (babel).
  
* You will get the wrong output with polyglossia for existing documents that
  used to work with Hebrew (polyglossia).

* You will get the wrong output with polyglossia for text inserted from
  OpenOffice or similar sources.  

It fixes one problem but creates two others, this is why I consider this
a regression.

A possible fix would be to toggle the parantheses whenever the document
settings change between use of "babel" and "polyglossia" or a function that
does so on user request. Also, the different input conventions and the
reasoning behind them should be documented.

Günter



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) in 
all cases.

The main difference, from a user POV, is that in Arabic you have to press ')' 
for an opening bracket (to get ')' in the LyX window), while in Hebrew you 
have to press '('. This has been the case since support for these languages 
was introduced. I find this also irritating, but maybe these are simply 
different input conventions, logical versus visual (I have added a FIXME that 
requests clarification).

As far as pating is concerned, your should always get (siht) (in the LyX 
window) when you paste (siht). I have not tested this, but the patch also does 
not change this.

> I would prefer if the LyX input were "(siht)" for both, Hebrew and
> Arabic, regardless of the language package.

Me, too. But then, I'm neither a Hebrew nor an Arabic writer.

> The patch changes the output, i.e. if someone uses the input convention
> used in other Unicode editors and also in Arabic, the output will be wrong
> with LyX.

I don't think this is true.

> In this sense, it changes which input is required to get the correct output:
> 
> * You will get the correct output with polyglossia for documents intended
> for Hebrew (babel).
> 
> * You will get the wrong output with polyglossia for existing documents that
> used to work with Hebrew (polyglossia).
> 
> * You will get the wrong output with polyglossia for text inserted from
>   OpenOffice or similar sources.

Can you provide an example?

Jürgen



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 Hebrew and (siht) for Arabic.]

 IMO, this is a polyglossia feature. It may be regarded as a regression, if
 we fix it to behave like babel:
 
 However, the applied patch seems to do exactly this. Whether it is a
 fix or a regression depends on the use case.
 
  + documents written for babel also work with polyglossia,
  - text pasted from other applications now fails with both, babel and
polyglossia.
 
 
 Please correct me if I am wrong. 

The patch does not touch the input (neither the input method nor the 
representation in the LyX source and window), we just adapt the output if we 
output to LaTeX with polyglossia. So I do not think anything will change 
(except the output with polyglossia will be correct).

Jürgen


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 Hebrew and (siht) for Arabic.]

 IMO, this is a polyglossia feature. It may be regarded as a regression, if
 we fix it to behave like babel:
 
 However, the applied patch seems to do exactly this. Whether it is a
 fix or a regression depends on the use case.
 
  + documents written for babel also work with polyglossia,
  - text pasted from other applications now fails with both, babel and
polyglossia.
 
 
 Please correct me if I am wrong. 

The patch does not touch the input (neither the input method nor the 
representation in the LyX source and window), we just adapt the output if we 
output to LaTeX with polyglossia. So I do not think anything will change 
(except the output with polyglossia will be correct).

Jürgen


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 Hebrew and (siht) for Arabic.]

> IMO, this is a polyglossia feature. It may be regarded as a regression, if
> we "fix" it to behave like babel:
> 
> However, the applied patch seems to do exactly this. Whether it is a
> "fix" or a "regression" depends on the use case.
> 
>  + documents written for babel also work with polyglossia,
>  - text pasted from other applications now fails with both, babel and
>polyglossia.
> 
> 
> Please correct me if I am wrong. 

The patch does not touch the input (neither the input method nor the 
representation in the LyX source and window), we just adapt the output if we 
output to LaTeX with polyglossia. So I do not think anything will change 
(except the output with polyglossia will be correct).

Jürgen


  1   2   3   4   >