RE: LyX math --> svg?

2017-10-27 Thread edu Gpl
Go to:
www.tlhiv.org/ltxpreview/
Or
www.codecogs.com/latex/eqneditor.php

Write your math then save as svg or png.

*thank you for texstackexchange.com
Regards

بتاريخ ٢٥‏/١٠‏/٢٠١٧ ٦:٣٠ م، كتب "Bernt Lie" <bernt@usn.no>:

> Thanks, Ricardo.
>
>
>
> I received perfect help from the developer of WriteTeX… I needed to
> install a load of dlls related to pdf2svd, and include the directory in the
> path… I’m not a “computer scientist” – but managed to figure it out.
>
>
>
> -B
>
>
>
> *From:* lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] *On
> Behalf Of *Ricardo Berlasso
> *Sent:* Wednesday, October 25, 2017 17:18
> *To:* lyx-users@lists.lyx.org
> *Subject:* Re: LyX math --> svg?
>
>
>
> 2017-10-24 12:57 GMT+02:00 Bernt Lie <bernt@usn.no>:
>
> I'm using LyX 2.2.2 on Windows 10 (64 bit).
>
> Question:
> * Is there a way to copy some math expression from LyX and paste it into,
> say, Inkscape, as svg?
> * If not, any other way to produce svg files? (I have tried to install
> WriteTeX as an extension in Inkscape, but this doesn't work properly at the
> moment.)
>
>
>
> It's possible to create cropped PDF files and then convert them to SVG
> with external utilities like pdf2svg (it's available on Linux, not sure
> about other OSs).
>
>
>
> If you go to File → New from template you'll find the PDF-cropped.lyx
> template: use it to create your expression and then save the resulting PDF.
> Then you can use pdf2svg the following way
>
>
>
> pdf2svg input.pdf output.svg
>
>
>
> to get the SVG file.
>
>
>
> Regards,
>
> Ricardo
>
>
>
>
>
>
>
>
> Thanks,
> BL
>
>
>


Re: Lyx Babel issue

2017-10-25 Thread Scott Kostyshak
On Fri, Sep 22, 2017 at 06:42:49AM +, Jürgen Spitzmüller wrote:
> Am Freitag, den 22.09.2017, 10:22 +1000 schrieb Peter Drummond:
> > `Package babel Error: Unknown language `english'. Either you have'
> > 
> > In the next pane, I have: 
> > 
> > `\selectlanguage{english}
> > You may proceed, but expect unexpected results'
> > 
> > In the Document Settings, I  find the Language package is always set
> > to 'Automatic'. If I then reset this to 'Always Babel', the error
> > goes away. I discovered this by trial and error. It is certainly not
> > remotely obvious. Why would a babel package error go away when one
> > sets the language package to 'babel'? I would have expected that if
> > the language package was set to 'Automatic', then it would either
> > choose 'babel' or some other package. If it chose 'babel', I might
> > get 'babel' errors, but they would surely remain if I set the option
> > to 'Always Babel'!
> 
> That's strange indeed. The only expected thing that might happen with
> automatic is that polyglossia is used rather than babel if you use
> "non-TeX fonts" and specific languages.
> 
> How does the LaTeX preamble (in View Source) in the two variants look
> like? Also the LaTeX log could be revealing.
> 
> > A related problem is that if I type in an incorrectly spelled word
> > like 'testx', it will be flagged by the spell-checker, but no
> > alternative is suggested. Note that these errors occur in a
> > completely new Lyx file, just created, with only one word in it, and
> > only default settings.
> 
> Other users have reported issues with the spell checker on the Mac.
> This might be related:
> http://www.lyx.org/trac/ticket/9351

Hi Peter,

I just wanted to make sure you received the above message.

Best,

Scott


signature.asc
Description: PGP signature


RE: LyX math --> svg?

2017-10-25 Thread Bernt Lie
Thanks, Ricardo.

I received perfect help from the developer of WriteTeX… I needed to install a 
load of dlls related to pdf2svd, and include the directory in the path… I’m not 
a “computer scientist” – but managed to figure it out.

-B

From: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] On Behalf Of 
Ricardo Berlasso
Sent: Wednesday, October 25, 2017 17:18
To: lyx-users@lists.lyx.org
Subject: Re: LyX math --> svg?

2017-10-24 12:57 GMT+02:00 Bernt Lie 
<bernt@usn.no<mailto:bernt@usn.no>>:
I'm using LyX 2.2.2 on Windows 10 (64 bit).

Question:
* Is there a way to copy some math expression from LyX and paste it into, say, 
Inkscape, as svg?
* If not, any other way to produce svg files? (I have tried to install WriteTeX 
as an extension in Inkscape, but this doesn't work properly at the moment.)

It's possible to create cropped PDF files and then convert them to SVG with 
external utilities like pdf2svg (it's available on Linux, not sure about other 
OSs).

If you go to File → New from template you'll find the PDF-cropped.lyx template: 
use it to create your expression and then save the resulting PDF. Then you can 
use pdf2svg the following way

pdf2svg input.pdf output.svg

to get the SVG file.

Regards,
Ricardo




Thanks,
BL



Re: LyX math --> svg?

2017-10-25 Thread Ricardo Berlasso
2017-10-24 12:57 GMT+02:00 Bernt Lie <bernt@usn.no>:

> I'm using LyX 2.2.2 on Windows 10 (64 bit).
>
> Question:
> * Is there a way to copy some math expression from LyX and paste it into,
> say, Inkscape, as svg?
> * If not, any other way to produce svg files? (I have tried to install
> WriteTeX as an extension in Inkscape, but this doesn't work properly at the
> moment.)
>

It's possible to create cropped PDF files and then convert them to SVG with
external utilities like pdf2svg (it's available on Linux, not sure about
other OSs).

If you go to File → New from template you'll find the PDF-cropped.lyx
template: use it to create your expression and then save the resulting PDF.
Then you can use pdf2svg the following way

pdf2svg input.pdf output.svg

to get the SVG file.

Regards,
Ricardo




>
> Thanks,
> BL
>
>


LyX math --> svg?

2017-10-25 Thread Bernt Lie
I'm using LyX 2.2.2 on Windows 10 (64 bit).

Question: 
* Is there a way to copy some math expression from LyX and paste it into, say, 
Inkscape, as svg?
* If not, any other way to produce svg files? (I have tried to install WriteTeX 
as an extension in Inkscape, but this doesn't work properly at the moment.)

Thanks,
BL



Re: Videos (animated GIF on LyX)

2017-10-11 Thread Paul A. Rubin

On 10/11/2017 05:35 PM, Carlos Knauer wrote:

Hi.

Is there way to I put an animated GIF in a LyX document ? For exemplo 
an image of one spinor rotating. Is it possible ? How ?


Thanks,

Carlos Fernando Knauer


As far as I know, inserting an animated GIF in a LyX document is no 
different than inserting an ordinary GIF. The problem comes after you 
compile the document. If you compile to HTML, with the intent of having 
it viewed in a web browser, I suspect you will be okay (although I've 
never tried it). If you compile to PDF, I'm fairly certain it will not 
work. I don't think the PDF specification supports animated GIFs, and so 
I don't think that PDF viewers will. The general consensus on the web 
seems to be that you would need to convert the GIF to a movie format and 
embed that. Most posts I saw suggest either MOV or SWF (Flash).


Paul



Videos (animated GIF on LyX)

2017-10-11 Thread Carlos Knauer
Hi.

Is there way to I put an animated GIF in a LyX document ? For exemplo an
image of one spinor rotating. Is it possible ? How ?

Thanks,

Carlos Fernando Knauer


Re: LyX 2.3 with QT5

2017-10-10 Thread F M Salter
attention: Jean-Marc Lasgouttes

    I do have pkg-config installed.

Regards
Frank

On 10/10/17 10:50, Jean-Marc Lasgouttes wrote:
> Le 10/10/2017 à 11:50, F M Salter a écrit :
>
> attention:  Jean-Marc Lasgouttes
>      I installed qtdeclaratives-dev, but the failure continues.
>
>      However  find qglobal.h gives
>
> /usr/include/qt4/Qt/qglobal.h
> /usr/include/qt4/QtCore/qglobal.h
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h
>
>   This may explain why the problem occurs.
>
> You are right, I have to look at this more closely. Another thing that
> I do here is to install pkg-config (which helps finding libraries). Do
> you have it?
> This may explain why I do not experience the same problem.
>
> JMarc
>
>     However  find qglobal.h gives
>  
> /usr/include/qt4/Qt/qglobal.h
> /usr/include/qt4/QtCore/qglobal.h
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h
>
>  This may explain why the problem occurs.
> Regards
> Frank
>
> On 10/10/17, Jean-Marc Lasgouttes wrote:
>> Le 09/10/2017 à 19:03, F M Salter a écrit :
>>
>> conftest.cpp:38:22: fatal error: qglobal.h: No such file or directory
>>#include 
>>
>> This seems weird. Did you install also the xxx-dev packages needed
>> to build a qt program? It looks like the build-essential package
>> installs whatever is needed to build all debian packages, but it may
>> be a bit too much.Some people advise to install qtdeclarative5-dev,
>> which installs whatever other packages are required for qt5.
>> JMarc
>> 
>>
>



Re: LyX 2.3 with QT5

2017-10-10 Thread Jean-Marc Lasgouttes

Le 10/10/2017 à 11:50, F M Salter a écrit :

attention:  Jean-Marc Lasgouttes
     I installed qtdeclaratives-dev, but the failure continues.

     However  find qglobal.h gives

/usr/include/qt4/Qt/qglobal.h
/usr/include/qt4/QtCore/qglobal.h
/usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h

  This may explain why the problem occurs.


You are right, I have to look at this more closely. Another thing that I 
do here is to install pkg-config (which helps finding libraries). Do you 
have it?


This may explain why I do not experience the same problem.

JMarc


Re: LyX 2.3 with QT5

2017-10-10 Thread Kornel Benko
Am Dienstag, 10. Oktober 2017 um 10:50:26, schrieb F M Salter 

> attention:  Jean-Marc Lasgouttes
> I installed qtdeclaratives-dev, but the failure continues.
> 
> However  find qglobal.h gives
>  
> /usr/include/qt4/Qt/qglobal.h
> /usr/include/qt4/QtCore/qglobal.h
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h
> 
>  This may explain why the problem occurs.
> Regards
> Frank
> 
> On 10/10/17, Jean-Marc Lasgouttes wrote:
> > Le 09/10/2017 à 19:03, F M Salter a écrit :
> >
> > conftest.cpp:38:22: fatal error: qglobal.h: No such file or directory
> >#include 
> >
> > This seems weird. Did you install also the xxx-dev packages needed
> > to build a qt program? It looks like the build-essential package
> > installs whatever is needed to build all debian packages, but it may
> > be a bit too much.Some people advise to install qtdeclarative5-dev,
> > which installs whatever other packages are required for qt5.
> > JMarc
> > 
> >

If nothing helps, you could try to configure with cmake.
(Since qt5 comes together with cmake config files, this may work)

Kornel

signature.asc
Description: This is a digitally signed message part.


Re: LyX 2.3 with QT5

2017-10-10 Thread F M Salter
attention:  Jean-Marc Lasgouttes
    I installed qtdeclaratives-dev, but the failure continues.

    However  find qglobal.h gives
 
/usr/include/qt4/Qt/qglobal.h
/usr/include/qt4/QtCore/qglobal.h
/usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h

 This may explain why the problem occurs.
Regards
Frank

On 10/10/17, Jean-Marc Lasgouttes wrote:
> Le 09/10/2017 à 19:03, F M Salter a écrit :
>
> conftest.cpp:38:22: fatal error: qglobal.h: No such file or directory
>#include 
>
> This seems weird. Did you install also the xxx-dev packages needed
> to build a qt program? It looks like the build-essential package
> installs whatever is needed to build all debian packages, but it may
> be a bit too much.Some people advise to install qtdeclarative5-dev,
> which installs whatever other packages are required for qt5.
> JMarc
> 
>



Re: LyX 2.3 with QT5

2017-10-10 Thread Jean-Marc Lasgouttes

Le 09/10/2017 à 19:03, F M Salter a écrit :

conftest.cpp:38:22: fatal error: qglobal.h: No such file or directory
   #include 


This seems weird. Did you install also the xxx-dev packages needed to 
build a qt program? It looks like the build-essential package installs 
whatever is needed to build all debian packages, but it may be a bit too 
much.


Some people advise to install qtdeclarative5-dev, which installs 
whatever other packages are required for qt5.


JMarc


Re: LyX 2.3 with QT5

2017-10-09 Thread F M Salter
attention: Juergen Spitzmueller

    Sorry I sent the wrong log.  Correct one and the configure output
are attached.
<https://www.mail-archive.com/search?l=lyx-users@lists.lyx.org=from:%22J%C3%BCrgen+Spitzm%C3%BCller%22>


On 09/10/17 16:30, F M Salter wrote:
> Hi,
>
>     I am enclosing the config.log file
>
> 
>

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by LyX configure 2.3.0beta1, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ../lyx-2.3.0beta1/configure --enable-qt5

## - ##
## Platform. ##
## - ##

hostname = cosmos
uname -m = x86_64
uname -r = 4.9.0-4-amd64
uname -s = Linux
uname -v = #1 SMP Debian 4.9.51-1 (2017-09-28)

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch  = unknown
/usr/bin/arch -k   = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo  = unknown
/bin/machine   = unknown
/usr/bin/oslevel   = unknown
/bin/universe  = unknown

PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/local/games
PATH: /usr/games


## --- ##
## Core tests. ##
## --- ##

configure:2904: checking for build type
configure:2922: result: prerelease
configure:2934: checking for version suffix
configure:2953: result: 
configure:2957: checking whether Qt5 is requested
configure:2966: result: yes
configure:2975: checking build system type
configure:2989: result: x86_64-pc-linux-gnu
configure:3009: checking host system type
configure:3022: result: x86_64-pc-linux-gnu
configure:3042: checking target system type
configure:3055: result: x86_64-pc-linux-gnu
configure:3081: checking what packaging should be used
configure:3098: result: posix
configure:3198: checking whether to enable maintainer-specific portions of Makefiles
configure:3207: result: no
configure:3231: checking whether make supports nested variables
configure:3248: result: yes
configure:3279: checking for a BSD-compatible install
configure:3347: result: /usr/bin/install -c
configure:3358: checking whether build environment is sane
configure:3413: result: yes
configure:3564: checking for a thread-safe mkdir -p
configure:3603: result: /bin/mkdir -p
configure:3610: checking for gawk
configure:3640: result: no
configure:3610: checking for mawk
configure:3626: found /usr/bin/mawk
configure:3637: result: mawk
configure:3648: checking whether make sets $(MAKE)
configure:3670: result: yes
configure:3757: checking whether UID '1000' is supported by ustar format
configure:3760: result: yes
configure:3767: checking whether GID '1000' is supported by ustar format
configure:3770: result: yes
configure:3778: checking how to create a ustar tar archive
configure:3789: tar --version
tar (GNU tar) 1.29
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.
configure:3792: $? = 0
configure:3832: tardir=conftest.dir && eval tar --format=ustar -chf - "$tardir" >conftest.tar
configure:3835: $? = 0
configure:3839: tar -xf - = 2.7.0 or 3.3.0
configure:4031: python -c import sys version = sys.version_info[:3] sys.exit(not ((2,7,0) <= version < (3,0,0) or version >= (3,3,0)))
configure:4034: $? = 0
configure:4040: result: python
configure:4048: checking for python
configure:4066: found /usr/bin/python
configure:4078: result: /usr/bin/python
configure:4158: checking for python version
configure:4165: result: 2.7
configure:4177: checking for python platform
configure:4184: result: linux2
configure:4210: checking for python script directory
configure:4245: result: ${prefix}/lib/python2.7/dist-packages
configure:4254: checking for python extension module directory
configure:4289: result: ${exec_prefix}/lib/python2.7/dist-packages
configure:4316: checking for style of include used by make
configure:4344: result: GNU
configure:4415: checking for gcc
configure:4431: found /usr/bin/gcc
configure:4442: result: gcc
configure:4671: checking for C compiler version
configure:4680: gcc --version >&5
gcc (Debian 6.3.0-18) 6.3.0 20170516
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:4691: $? = 0
configure:4680: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-18' --with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-6 --program-prefix=x86_64-linux-gnu

Re: LyX 2.3 with QT5

2017-10-09 Thread Jürgen Spitzmüller
2017-10-09 17:30 GMT+02:00 F M Salter <fmsal...@blueyonder.co.uk>:

> I am enclosing the config.log file
>
>
... which reveals that you didn't use --enable-qt5 for configure:

  $ ../lyx-2.3.0beta1/configure
>

[...]

configure:2957: checking whether Qt5 is requested
>
configure:2966: result: no
>

Jürgen


Re: LyX 2.3 with QT5

2017-10-09 Thread F M Salter
Hi,

    I am enclosing the config.log file




This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by LyX configure 2.3.0beta1, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ../lyx-2.3.0beta1/configure 

## - ##
## Platform. ##
## - ##

hostname = cosmos
uname -m = x86_64
uname -r = 4.9.0-4-amd64
uname -s = Linux
uname -v = #1 SMP Debian 4.9.51-1 (2017-09-28)

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch  = unknown
/usr/bin/arch -k   = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo  = unknown
/bin/machine   = unknown
/usr/bin/oslevel   = unknown
/bin/universe  = unknown

PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/local/games
PATH: /usr/games


## --- ##
## Core tests. ##
## --- ##

configure:2904: checking for build type
configure:2922: result: prerelease
configure:2934: checking for version suffix
configure:2953: result: 
configure:2957: checking whether Qt5 is requested
configure:2966: result: no
configure:2975: checking build system type
configure:2989: result: x86_64-pc-linux-gnu
configure:3009: checking host system type
configure:3022: result: x86_64-pc-linux-gnu
configure:3042: checking target system type
configure:3055: result: x86_64-pc-linux-gnu
configure:3081: checking what packaging should be used
configure:3098: result: posix
configure:3198: checking whether to enable maintainer-specific portions of Makefiles
configure:3207: result: no
configure:3231: checking whether make supports nested variables
configure:3248: result: yes
configure:3279: checking for a BSD-compatible install
configure:3347: result: /usr/bin/install -c
configure:3358: checking whether build environment is sane
configure:3413: result: yes
configure:3564: checking for a thread-safe mkdir -p
configure:3603: result: /bin/mkdir -p
configure:3610: checking for gawk
configure:3640: result: no
configure:3610: checking for mawk
configure:3626: found /usr/bin/mawk
configure:3637: result: mawk
configure:3648: checking whether make sets $(MAKE)
configure:3670: result: yes
configure:3757: checking whether UID '1000' is supported by ustar format
configure:3760: result: yes
configure:3767: checking whether GID '1000' is supported by ustar format
configure:3770: result: yes
configure:3778: checking how to create a ustar tar archive
configure:3789: tar --version
tar (GNU tar) 1.29
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.
configure:3792: $? = 0
configure:3832: tardir=conftest.dir && eval tar --format=ustar -chf - "$tardir" >conftest.tar
configure:3835: $? = 0
configure:3839: tar -xf - = 2.7.0 or 3.3.0
configure:4031: python -c import sys version = sys.version_info[:3] sys.exit(not ((2,7,0) <= version < (3,0,0) or version >= (3,3,0)))
configure:4034: $? = 0
configure:4040: result: python
configure:4048: checking for python
configure:4066: found /usr/bin/python
configure:4078: result: /usr/bin/python
configure:4158: checking for python version
configure:4165: result: 2.7
configure:4177: checking for python platform
configure:4184: result: linux2
configure:4210: checking for python script directory
configure:4245: result: ${prefix}/lib/python2.7/dist-packages
configure:4254: checking for python extension module directory
configure:4289: result: ${exec_prefix}/lib/python2.7/dist-packages
configure:4316: checking for style of include used by make
configure:4344: result: GNU
configure:4415: checking for gcc
configure:4431: found /usr/bin/gcc
configure:4442: result: gcc
configure:4671: checking for C compiler version
configure:4680: gcc --version >&5
gcc (Debian 6.3.0-18) 6.3.0 20170516
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:4691: $? = 0
configure:4680: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-18' --with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --dis

Re: LyX 2.3 with QT5

2017-10-09 Thread Jean-Marc Lasgouttes

Le 09/10/2017 à 14:14, F M Salter a écrit :

JMarc

     Thank you for your prompt response.

     I believe I have installed all the development packages of which I
am aware.  I did use  --enable-qt5, without success.

     I have also noticed that the included boost libraries were used even
though system-wide boost libraries and headers are available.  This
seems to suggest that the configuration is not picking the required
libraries.


Boost is particular, we use the included ones by defaults. As reason is 
that it is necessary to use run-time checking of bounds, which is useful 
on development versions. You can use --without-included-boost if you do 
not like that.


Could you send your config.log file?

JMarc



Re: LyX 2.3 with QT5

2017-10-09 Thread F M Salter
JMarc

    Thank you for your prompt response.

    I believe I have installed all the development packages of which I
am aware.  I did use  --enable-qt5, without success.

    I have also noticed that the included boost libraries were used even
though system-wide boost libraries and headers are available.  This
seems to suggest that the configuration is not picking the required
libraries.

Regards

Frank


On 09/10/17 12:28, Jean-Marc Lasgouttes wrote:
> Le 09/10/2017 à 13:13, Jürgen Spitzmüller a écrit :
>> Do you have all necessary qt5-devel packages installed?
>>
>> Do you use --enable-qt5?
>
> If you do those two things, you should not need to set any directories
> (at least for a first try).
>
> JMarc



Re: LyX 2.3 with QT5

2017-10-09 Thread Jean-Marc Lasgouttes

Le 09/10/2017 à 13:13, Jürgen Spitzmüller a écrit :

Do you have all necessary qt5-devel packages installed?

Do you use --enable-qt5?


If you do those two things, you should not need to set any directories 
(at least for a first try).


JMarc


Re: LyX 2.3 with QT5

2017-10-09 Thread Jürgen Spitzmüller
Do you have all necessary qt5-devel packages installed?

Do you use --enable-qt5?

If this is all true, please post some more information (exact error
message, used options for configure)

Jürgen

Am Montag, den 09.10.2017, 11:59 +0100 schrieb F M Salter:
> Hi,
> 
> I am attempting and failing to compile 2.3 with QT5 in Debian
> Stretch.  Setting QTDIR to all directories-qt5 in turn produces the
> same
> configuration failure, suggesting QT5DIR is set incorrectly.
> 
> Has anyone done this successfully?  If so would you please
> explain
> what needs to be done to use QT5.
> 
> Regards
> 
> Frank Salter
> 
> 
> 

signature.asc
Description: This is a digitally signed message part


LyX 2.3 with QT5

2017-10-09 Thread F M Salter
Hi,

    I am attempting and failing to compile 2.3 with QT5 in Debian
Stretch.  Setting QTDIR to all directories-qt5 in turn produces the same
configuration failure, suggesting QT5DIR is set incorrectly.

    Has anyone done this successfully?  If so would you please explain
what needs to be done to use QT5.

Regards

Frank Salter





Re: Backtick in LyX's "LyX-Code" mode

2017-10-05 Thread Scott Kostyshak
On Thu, Sep 28, 2017 at 08:48:13AM +, Guenter Milde wrote:
> On 2017-09-27, Bruce Momjian wrote:
> > On Wed, Sep 27, 2017 at 12:41:27PM -0400, Scott Kostyshak wrote:
> >> On Mon, Sep 25, 2017 at 10:24:47PM +, Bruce Momjian wrote:
> >> > I am using LyX 2.1.2 on Ubuntu 14.04.
> >> > 
> >> > If I enter this:
> >> > 
> >> >   ab'c de`f
> >> > 
> >> > in "Standard" mode I get PDF output with proper left/right single
> >> > quotes.  However, if I switch to LyX-Code mode for that text, I get as
> >> > PDF output:
> >> > 
> >> >  ab'c de'f
> 
> >> Testing on 2.1.0 and on 2.3.0dev, I get the following as PDF output:
> 
> >>   ab’c de‘f
> 
> >> which is different from what you get, but also not what you want.
> 
> > Actually, that would be fine output, as long as they look different.
> 
> >> > This is a problem for text of shell scripts.  I the want backticks
> >> > because backtick means 'execute' in the shell.
> >> > 
> >> > What I have done instead to get literal backticks output is to use a
> >> > TeX Code URT (Ugly Red Text) block inside the "LyX-Code mode" block and
> >> > used \char18, which properly outputs the backtick.
> >> > 
> >> > Is this expected behavior?  Is that the recommended solution for this?
> 
> >> I have not seen a report of this, but I haven't seen an indication that
> >> a lot of people are using LyX-Code, so I'm not sure if is known.
> 
> > OK, not sure what could be the cause then.  I am using ps2pdf to produce
> > the PDF.
> 
> The view in PDF depends on the selected fonts rather than export route. I
> get identic results with PDF (pdflatex) and PDF (ps2pdf).
> 
> You may experiment with different fonts, as well as checking the result of
> drag-and-drop from the PDF. Here, it is
>  ab'c de`f  with PDF(pdflatex) and ab' de`f with PDF(ps2pdf).
> 
> > What I have done as a work-around is to warn in my Makefile if a
> > backquote is used in the LyX document.
> 
> Did you try with listings?

Hi Bruce,

I just wanted to make sure that you saw Günter's message (pasted above),
since he had a good idea, to experiment with different fonts.

Best,

Scott


signature.asc
Description: PGP signature


RE: LyX & BibTeX & complex author names

2017-10-05 Thread Bernt Lie
Wolfgang,

Thanks a lot for giving the BibTeX syntax rule... I have always (?) used 
“Firstname Surname”…

-Bernt

From: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] On Behalf Of 
Wolfgang Engelmann
Sent: torsdag 5. oktober 2017 16.26
To: lyx-users@lists.lyx.org
Subject: Re: LyX & BibTeX & complex author names




Am 05.10.2017 um 16:19 schrieb Wolfgang Engelmann:



Am 05.10.2017 um 15:55 schrieb Bernt Lie:

I use LyX 2.2.2 on 64 bits Windows 10. Should probably upgrade to the latest 
LyX, but then again my set-up mostly works.



I'm using JabRef to handle BibTeX, and struggle to correctly handle authors 
"Arthur E. Bryson, Jr. and Yu-Chi Ho". I use a Harvard reference style.



What is the correct way to write the author name in the author field of 
BibTeX/JabRef? I have tried with:



"Arthur E. {Bryson, Jr.} and Yu-Chi Ho" -- which leads to "Bryson, Jr., A.E., & 
Ho, Y.-Ch." In the typeset bibliography list. Perhaps ok (although I'd like 
"and" instead of "&" -- "&" looks too much like "Donald Duck & Co"...)



However, in LyX, this pops up as "Arthur E. Bryson and Ho (1975)". If I skip 
the comma in the braces ({Bryson, Jr.} --> {Bryson Jr.}), it appears as "Jr. 
and Ho (1975)" in LyX...

--

So -- what is the "correct" way to handle such a slightly complicated name?

-

BL
Have you tried to mouse-click on the author field and select
normalize to BibTex name format
? You might also choose a different style file. Tell us, how you would like to 
have your citation.
Wolfgang
see also
https://tex.stackexchange.com/questions/223817/how-to-deal-with-an-author-name-with-jr-in-bibliography
which boils down to

If a name has "Junior" component (and no "von" component), it needs to be 
entered as SurnameComponent, JuniorComponent, FirstNameComponent. Note that 
there are now two commas, not one. This is a BibTeX syntax rule that's 
independent of the bibliography style you employ.

Hence, you need to enter the second author's name as Bassett, Jr., Gilbert.


Re: LyX & BibTeX & complex author names

2017-10-05 Thread Wolfgang Engelmann



Am 05.10.2017 um 16:19 schrieb Wolfgang Engelmann:




Am 05.10.2017 um 15:55 schrieb Bernt Lie:

I use LyX 2.2.2 on 64 bits Windows 10. Should probably upgrade to the latest 
LyX, but then again my set-up mostly works.

I'm using JabRef to handle BibTeX, and struggle to correctly handle authors "Arthur 
E. Bryson, Jr. and Yu-Chi Ho". I use a Harvard reference style.

What is the correct way to write the author name in the author field of 
BibTeX/JabRef? I have tried with:

"Arthur E. {Bryson, Jr.} and Yu-Chi Ho" -- which leads to "Bryson, Jr., A.E., & Ho, Y.-Ch." In the typeset bibliography list. 
Perhaps ok (although I'd like "and" instead of "&" -- "&" looks too much like "Donald Duck & Co"...)

However, in LyX, this pops up as "Arthur E. Bryson and Ho (1975)". If I skip the comma in 
the braces ({Bryson, Jr.} --> {Bryson Jr.}), it appears as "Jr. and Ho (1975)" in LyX...
--
So -- what is the "correct" way to handle such a slightly complicated name?
-
BL

Have you tried to mouse-click on the author field and select
/normalize to BibTex name format/
? You might also choose a different style file. Tell us, how you would 
like to have your citation.

Wolfgang

see also
https://tex.stackexchange.com/questions/223817/how-to-deal-with-an-author-name-with-jr-in-bibliography
which boils down to

If a name has "Junior" component (and no "von" component), it needs to 
be entered as |SurnameComponent, JuniorComponent, FirstNameComponent|. 
Note that there are now two commas, not one. This is a BibTeX syntax 
rule that's independent of the bibliography style you employ.


Hence, you need to enter the second author's name as |Bassett, Jr., 
Gilbert|.




Re: LyX & BibTeX & complex author names

2017-10-05 Thread Wolfgang Engelmann



Am 05.10.2017 um 15:55 schrieb Bernt Lie:

I use LyX 2.2.2 on 64 bits Windows 10. Should probably upgrade to the latest 
LyX, but then again my set-up mostly works.

I'm using JabRef to handle BibTeX, and struggle to correctly handle authors "Arthur 
E. Bryson, Jr. and Yu-Chi Ho". I use a Harvard reference style.

What is the correct way to write the author name in the author field of 
BibTeX/JabRef? I have tried with:

"Arthur E. {Bryson, Jr.} and Yu-Chi Ho" -- which leads to "Bryson, Jr., A.E., & Ho, Y.-Ch." In the typeset bibliography list. 
Perhaps ok (although I'd like "and" instead of "&" -- "&" looks too much like "Donald Duck & Co"...)

However, in LyX, this pops up as "Arthur E. Bryson and Ho (1975)". If I skip the comma in 
the braces ({Bryson, Jr.} --> {Bryson Jr.}), it appears as "Jr. and Ho (1975)" in LyX...
--
So -- what is the "correct" way to handle such a slightly complicated name?
-
BL

Have you tried to mouse-click on the author field and select
/normalize to BibTex name format/
? You might also choose a different style file. Tell us, how you would 
like to have your citation.

Wolfgang


LyX & BibTeX & complex author names

2017-10-05 Thread Bernt Lie
I use LyX 2.2.2 on 64 bits Windows 10. Should probably upgrade to the latest 
LyX, but then again my set-up mostly works.

I'm using JabRef to handle BibTeX, and struggle to correctly handle authors 
"Arthur E. Bryson, Jr. and Yu-Chi Ho". I use a Harvard reference style.

What is the correct way to write the author name in the author field of 
BibTeX/JabRef? I have tried with:

"Arthur E. {Bryson, Jr.} and Yu-Chi Ho" -- which leads to "Bryson, Jr., A.E., & 
Ho, Y.-Ch." In the typeset bibliography list. Perhaps ok (although I'd like 
"and" instead of "&" -- "&" looks too much like "Donald Duck & Co"...)

However, in LyX, this pops up as "Arthur E. Bryson and Ho (1975)". If I skip 
the comma in the braces ({Bryson, Jr.} --> {Bryson Jr.}), it appears as "Jr. 
and Ho (1975)" in LyX...
--
So -- what is the "correct" way to handle such a slightly complicated name?
-
BL 


Re: Problems of pagebackref in LyX

2017-10-04 Thread Jürgen Spitzmüller
2017-10-04 14:49 GMT+02:00:

> Dear all,
>
> I found that chapterbib is not supported in LyX.
>

The good news is that it will be supported by LyX 2.3.0, which is almost
ready.


> Although multiple bibliographies can be easily realized in LyX using
> bibtopic, the pagebackref can not be used.
>
> Are there possible solutions to the problem of pagebackref?
>

Up to LyX 2.2, chapterbib can be used with some workaround:
http://wiki.lyx.org/BibTeX/Tips#toc4

Jürgen


> Thank you so much.
>
> Sincerely,
>
> kc cao
>
>
>


Problems of pagebackref in LyX

2017-10-04 Thread caokecai
Dear all,

I found that chapterbib is not supported in LyX.

Although multiple bibliographies can be easily realized in LyX using
bibtopic, the pagebackref can not be used.

Are there possible solutions to the problem of pagebackref? 

Thank you so much.

Sincerely,

kc cao

 



Re: LyX without classes

2017-09-28 Thread Carlos Knauer
All classes.

Em 28 de set de 2017 14:25, "Paul A. Rubin"  escreveu:

> On 09/28/2017 07:10 AM, Carlos Knauer wrote:
>
>> Windows 7
>>
>> Are you missing all classes, or just certain ones? The key test is
> whether you can use the basic article class.
>
>
>


Re: LyX without classes

2017-09-28 Thread Paul A. Rubin

On 09/28/2017 07:10 AM, Carlos Knauer wrote:

Windows 7

Are you missing all classes, or just certain ones? The key test is 
whether you can use the basic article class.





Re: LyX without classes

2017-09-28 Thread Paul A. Rubin

On 09/28/2017 07:10 AM, Carlos Knauer wrote:

Windows 7

Did you install LaTeX on the notebook?



Re: LyX without classes

2017-09-28 Thread Carlos Knauer
Windows 7


On Thu, Sep 28, 2017 at 12:15 AM, Joel Kulesza <jkule...@gmail.com> wrote:

> On Wed, Sep 27, 2017 at 9:12 PM, Carlos Knauer <carlos.kna...@gmail.com>
> wrote:
>
>> I had to install LyX 2.2.3 on my notebook and classes dont come . Why ?
>>
>
> Are you using a Mac?  If so, I wonder if this could be the issue:
> https://www.lyx.org/trac/ticket/10671
>
> - Joel
>
>


Re: Backtick in LyX's "LyX-Code" mode

2017-09-28 Thread Guenter Milde
On 2017-09-27, Bruce Momjian wrote:
> On Wed, Sep 27, 2017 at 12:41:27PM -0400, Scott Kostyshak wrote:
>> On Mon, Sep 25, 2017 at 10:24:47PM +, Bruce Momjian wrote:
>> > I am using LyX 2.1.2 on Ubuntu 14.04.
>> > 
>> > If I enter this:
>> > 
>> > ab'c de`f
>> > 
>> > in "Standard" mode I get PDF output with proper left/right single
>> > quotes.  However, if I switch to LyX-Code mode for that text, I get as
>> > PDF output:
>> > 
>> >ab'c de'f

>> Testing on 2.1.0 and on 2.3.0dev, I get the following as PDF output:

>>   ab’c de‘f

>> which is different from what you get, but also not what you want.

> Actually, that would be fine output, as long as they look different.

>> > This is a problem for text of shell scripts.  I the want backticks
>> > because backtick means 'execute' in the shell.
>> > 
>> > What I have done instead to get literal backticks output is to use a
>> > TeX Code URT (Ugly Red Text) block inside the "LyX-Code mode" block and
>> > used \char18, which properly outputs the backtick.
>> > 
>> > Is this expected behavior?  Is that the recommended solution for this?

>> I have not seen a report of this, but I haven't seen an indication that
>> a lot of people are using LyX-Code, so I'm not sure if is known.

> OK, not sure what could be the cause then.  I am using ps2pdf to produce
> the PDF.

The view in PDF depends on the selected fonts rather than export route. I
get identic results with PDF (pdflatex) and PDF (ps2pdf).

You may experiment with different fonts, as well as checking the result of
drag-and-drop from the PDF. Here, it is
 ab'c de`f  with PDF(pdflatex) and ab' de`f with PDF(ps2pdf).

> What I have done as a work-around is to warn in my Makefile if a
> backquote is used in the LyX document.

Did you try with listings?


Günter



Re: LyX without classes

2017-09-27 Thread Joel Kulesza
On Wed, Sep 27, 2017 at 9:12 PM, Carlos Knauer <carlos.kna...@gmail.com>
wrote:

> I had to install LyX 2.2.3 on my notebook and classes dont come . Why ?
>

Are you using a Mac?  If so, I wonder if this could be the issue:
https://www.lyx.org/trac/ticket/10671

- Joel


LyX without classes

2017-09-27 Thread Carlos Knauer
I had to install LyX 2.2.3 on my notebook and classes dont come . Why ?


Re: Setting LyX font size [FIXED]

2017-09-27 Thread Rich Shepard

On Mon, 25 Sep 2017, Rich Shepard wrote:


Now, the LyX frame and menu font size has shrunk. The document display
font remains the same, it's the application frame and menus that have
changed.

 Is there a place where I can change this?


  Found the solution in the wiki: qtconfig is the tool to use.

  The LyX menu font size had shrunk to ~6pt. I reset it to 9pt and it's once
again readable.

Rich


Re: Backtick in LyX's "LyX-Code" mode

2017-09-27 Thread Bruce Momjian
On Wed, Sep 27, 2017 at 12:41:27PM -0400, Scott Kostyshak wrote:
> On Mon, Sep 25, 2017 at 10:24:47PM +, Bruce Momjian wrote:
> > I am using LyX 2.1.2 on Ubuntu 14.04.
> > 
> > If I enter this:
> > 
> >  ab'c de`f
> > 
> > in "Standard" mode I get PDF output with proper left/right single
> > quotes.  However, if I switch to LyX-Code mode for that text, I get as
> > PDF output:
> > 
> > ab'c de'f
> 
> Testing on 2.1.0 and on 2.3.0dev, I get the following as PDF output:
> 
>   ab’c de‘f
> 
> which is different from what you get, but also not what you want.

Actually, that would be fine output, as long as they look different.

> > This is a problem for text of shell scripts.  I the want backticks
> > because backtick means 'execute' in the shell.
> > 
> > What I have done instead to get literal backticks output is to use a
> > TeX Code URT (Ugly Red Text) block inside the "LyX-Code mode" block and
> > used \char18, which properly outputs the backtick.
> > 
> > Is this expected behavior?  Is that the recommended solution for this?
> 
> I have not seen a report of this, but I haven't seen an indication that
> a lot of people are using LyX-Code, so I'm not sure if is known.

OK, not sure what could be the cause then.  I am using ps2pdf to produce
the PDF.

What I have done as a work-around is to warn in my Makefile if a
backquote is used in the LyX document.

-- 
  Bruce Momjian  <br...@momjian.us>http://momjian.us
  EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+  Ancient Roman grave inscription +


Re: Backtick in LyX's "LyX-Code" mode

2017-09-27 Thread Scott Kostyshak
On Mon, Sep 25, 2017 at 10:24:47PM +, Bruce Momjian wrote:
> I am using LyX 2.1.2 on Ubuntu 14.04.
> 
> If I enter this:
> 
>ab'c de`f
> 
> in "Standard" mode I get PDF output with proper left/right single
> quotes.  However, if I switch to LyX-Code mode for that text, I get as
> PDF output:
> 
>   ab'c de'f

Testing on 2.1.0 and on 2.3.0dev, I get the following as PDF output:

  ab’c de‘f

which is different from what you get, but also not what you want.

> This is a problem for text of shell scripts.  I the want backticks
> because backtick means 'execute' in the shell.
> 
> What I have done instead to get literal backticks output is to use a
> TeX Code URT (Ugly Red Text) block inside the "LyX-Code mode" block and
> used \char18, which properly outputs the backtick.
> 
> Is this expected behavior?  Is that the recommended solution for this?

I have not seen a report of this, but I haven't seen an indication that
a lot of people are using LyX-Code, so I'm not sure if is known.

Scott


signature.asc
Description: PGP signature


Re: Backtick in LyX's "LyX-Code" mode

2017-09-26 Thread Guenter Milde
On 2017-09-25, Bruce Momjian wrote:
> I am using LyX 2.1.2 on Ubuntu 14.04.

> If I enter this:

>ab'c de`f

> in "Standard" mode I get PDF output with proper left/right single
> quotes. 

This is a feature of LaTeX fonts: the ASCII quote and backtick are mapped
to "typographical" quotes u2019 and u2018:  ab’c de‘f

> However, if I switch to LyX-Code mode for that text, I get as
> PDF output:

>   ab'c de'f

Here, I get the "typographical" quotes u2019 and u2018 in a teletype
font: ab’c de‘f

With Document>Settings>Fonts>non-TeX fonts, the PDF output is as expected: 
ab'c de`f

> This is a problem for text of shell scripts.  I the want backticks
> because backtick means 'execute' in the shell.

> What I have done instead to get literal backticks output is to use a
> TeX Code URT (Ugly Red Text) block inside the "LyX-Code mode" block and
> used \char18, which properly outputs the backtick.

In case using Unicode fonts is not an option, you may also try the
"listings" package (Insert>Program listing) with the options

  upquote=true
  basicstyle=\ttfamily

in Document>Settings>Program listings. In a minimal document, you may
need to add \usepackage{textcomp} to the LaTeX preamble.


A a last ressort, you can use the macro \textasciigrave (instead of
\char18) in raw LaTeX (ERT).


Günter





Setting LyX font size

2017-09-25 Thread Rich Shepard

  Using font manager I deleted a bunch of typefaces that I have never used
nor will use in the future. Many are look-alikes (to me, at least) of serif
and sanserig type faces. Now, the LyX frame and menu font size has shrunk.
The document display font remains the same, it's the application frame and
menus that have changed.

  Is there a place where I can change this? I don't find it on the Tools ->
Preferences -> Display menu.

TIA,

Rich


Backtick in LyX's "LyX-Code" mode

2017-09-25 Thread Bruce Momjian
I am using LyX 2.1.2 on Ubuntu 14.04.

If I enter this:

 ab'c de`f

in "Standard" mode I get PDF output with proper left/right single
quotes.  However, if I switch to LyX-Code mode for that text, I get as
PDF output:

ab'c de'f

This is a problem for text of shell scripts.  I the want backticks
because backtick means 'execute' in the shell.

What I have done instead to get literal backticks output is to use a
TeX Code URT (Ugly Red Text) block inside the "LyX-Code mode" block and
used \char18, which properly outputs the backtick.

Is this expected behavior?  Is that the recommended solution for this?

-- 
  Bruce Momjian  <br...@momjian.us>http://momjian.us
  EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+  Ancient Roman grave inscription +


Re: Lyx Babel issue

2017-09-22 Thread Guenter Milde
On 2017-09-22, Peter Drummond wrote:

> I get the following problem running
> LyX Version 2.2.3 on a Mac with OSX El Capitan 10.11.6.

> If I simply open the Lyx program with a new file, type in 'test', and try
> to view the results, I get an error message in the log panel that opens:

> `Package babel Error: Unknown language `english'. Either you have'

...

> Note that these errors occur in a completely new Lyx file, just
> created, with only one word in it, and only default settings.

The default settings can be configured via a "defaults.lyx" template
in one of the LyX-Dirs. Could you send the minimal test LyX file?

> Similar spellcheck/babel errors occur in almost every other Lyx file I try.
> Many are more serious than this, and don't allow me to proceed. This
> creates problems with files shared with other researchers, who create Lyx
> files that I edit.

> I do not get this problem on other Macs I have access to, with the same
> version of Lyx. However, there is no obvious clue to what is causing
> it. Presumably a language setting either in Lyx or the Mac is
> incorrect, but I have no idea what it could be. Whatever it is, the
> error message is not very useful.

It may also be a problem with the LaTeX installation/setup.
Does a LyX file produced on other Macs run on the "faulty" one?
Does a failing LyX file run on the other Macs?

Günter



Re: Lyx Babel issue

2017-09-22 Thread Jürgen Spitzmüller
Am Freitag, den 22.09.2017, 10:22 +1000 schrieb Peter Drummond:
> `Package babel Error: Unknown language `english'. Either you have'
> 
> In the next pane, I have: 
> 
> `\selectlanguage{english}
> You may proceed, but expect unexpected results'
> 
> In the Document Settings, I  find the Language package is always set
> to 'Automatic'. If I then reset this to 'Always Babel', the error
> goes away. I discovered this by trial and error. It is certainly not
> remotely obvious. Why would a babel package error go away when one
> sets the language package to 'babel'? I would have expected that if
> the language package was set to 'Automatic', then it would either
> choose 'babel' or some other package. If it chose 'babel', I might
> get 'babel' errors, but they would surely remain if I set the option
> to 'Always Babel'!

That's strange indeed. The only expected thing that might happen with
automatic is that polyglossia is used rather than babel if you use
"non-TeX fonts" and specific languages.

How does the LaTeX preamble (in View Source) in the two variants look
like? Also the LaTeX log could be revealing.

> A related problem is that if I type in an incorrectly spelled word
> like 'testx', it will be flagged by the spell-checker, but no
> alternative is suggested. Note that these errors occur in a
> completely new Lyx file, just created, with only one word in it, and
> only default settings.

Other users have reported issues with the spell checker on the Mac.
This might be related:
http://www.lyx.org/trac/ticket/9351

HTH
Jürgen

signature.asc
Description: This is a digitally signed message part


Lyx Babel issue

2017-09-21 Thread Peter Drummond
I get the following problem running


LyX Version 2.2.3 on a Mac with OSX El Capitan 10.11.6.


If I simply open the Lyx program with a new file, type in 'test', and try
to view the results, I get an error message in the log panel that opens:

`Package babel Error: Unknown language `english'. Either you have'

In the next pane, I have:

`\selectlanguage{english}

You may proceed, but expect unexpected results'


In the Document Settings, I  find the Language package is always set to
'Automatic'. If I then reset this to 'Always Babel', the error goes away. I
discovered this by trial and error. It is certainly not remotely obvious.
Why would a babel package error go away when one sets the language package
to 'babel'? I would have expected that if the language package was set to
'Automatic', then it would either choose 'babel' or some other package. If
it chose 'babel', I might get 'babel' errors, but they would surely remain
if I set the option to 'Always Babel'!


The documentation in the Help file gives no hint as to why a babel error
would occur with automatic settings, but not with the 'Always Babel'
setting.


A related problem is that if I type in an incorrectly spelled word like
'testx', it will be flagged by the spell-checker, but no alternative is
suggested. Note that these errors occur in a completely new Lyx file, just
created, with only one word in it, and only default settings.


Similar spellcheck/babel errors occur in almost every other Lyx file I try.
Many are more serious than this, and don't allow me to proceed. This
creates problems with files shared with other researchers, who create Lyx
files that I edit.


I do not get this problem on other Macs I have access to, with the same
version of Lyx. However, there is no obvious clue to what is causing it.
Presumably a language setting either in Lyx or the Mac is incorrect, but I
have no idea what it could be. Whatever it is, the error message is not
very useful.


Hope someone can help -


Peter Drummond


LyX - Luminati SDK

2017-09-15 Thread Yuval Cohen
Hi,

​​My name is Yuval and I lead the SDK partnerships at Luminati.​ I assume your
software earns money by charging users for a premium subscription or by showing
ads - both models do not pay out much and harm the user experience.

We now offer you a third option.

Luminati’s monetization SDK for Windows desktop provides your users the option
to use the software for free, and in exchange we pay you $30,000 USD per month,
for every 1M daily active users.
More information is available on http://luminati.io/sdk_win.

I’d like to schedule a 15 minute call to let you know how we can start. Are you
available tomorrow at 12:30pm your local time?

Best Regards,
-- 
Yuval Cohen | Business Development Manager, Luminati SDK | Skype: yuval__cohen
http://luminati.io/sdk_win


Re: LyX version 2.3.0 (beta 1)

2017-08-29 Thread Liviu Andronic
On Thu, Aug 17, 2017 at 8:25 PM, Scott Kostyshak <skost...@lyx.org> wrote:

> Public release of LyX version 2.3.0beta1
> 
>
>
Ubuntu 'lyx2.3pre' packages are now available on the Development PPA:
https://launchpad.net/~lyx-devel/+archive/ubuntu/daily

The packages install independently of your existing stable 2.2.x
installation.

Regards,
Liviu



> We are proud to announce the first public beta of the new LyX 2.3 series.
> This pre-release is meant for testing and should not be used for serious
> work.
> For curious users who would like to test in order to help catch bugs before
> the 2.3.0 release, please back up all of your documents and be prepared for
> the worst to happen. Most users (who desire a stable LyX version) should
> not
> use this pre-release.
>
> The 2.3 series has a rich set of new features compared to the current
> stable
> series. An overview of the new features can be found here:
>
>   http://wiki.lyx.org/LyX/NewInLyX23
>
> You can download LyX 2.3.0beta1 from ftp://ftp.lyx.org/pub/lyx/devel/.
>
> We appreciate your help in testing this pre-release!
>
> The file lib/RELEASE-NOTES lists some known issues and problems compared
> to the current stable releases (LyX 2.2.x). We strongly recommend that
> packagers of LyX on various platforms and distributions read this file.
>
> As with any major release, this one comes with a lot of new features but
> also some bugs. If you think you have found a bug in LyX 2.3.0beta1, either
> email the LyX developers' mailing list (lyx-devel at lists.lyx.org),
> or open a bug report at https://www.lyx.org/trac/wiki/BugTrackerHome.
> Please specify if the behavior you are reporting is different from behavior
> in a previous LyX version.
>
> If you have trouble using LyX or have a question, consult the
> documentation that comes with LyX (under Help) and the LyX wiki, which you
> will find at https://wiki.lyx.org/. You can also send email to the LyX
> users'
> list (lyx-users at lists.lyx.org).
>
> The LyX team.
> https://www.lyx.org
>
>


Re: LyX Cross-reference Label Default Content Inquiry

2017-08-28 Thread Richard Heck
On 08/28/2017 03:07 PM, Joel Kulesza wrote:
> Colleagues:
>
> Is there a mechanism for modifying how Insert -> Labels are
> automatically populated?  
>
> It appears to populate with the name of the associated entity, with
> spaces changed to dashes, up to a certain character limit.  
>
> Can this character limit be raised?  Can the space->dash conversion be
> modified?
>
> My ultimate goal is to provide more context in the labels themselves
> (mostly through NOT truncating them).  I usually just copy/paste the
> associated information of the default label; however, it would be
> convenient if something like this outcome could be made automatic. 
> That said, I'm glad the clickable UI element is truncated...

Short of modifying the source code, no, there's no way to customize
this. But you can of course patch the source for your own purposes if
you wish. The routine in question is Text::getPossibleLabel, in Text.cpp.

It probably would not be that hard to add preferences to control length
and what spaces get replaced with, though we're sometimes reluctant to
add too many preferences

Richard



LyX Cross-reference Label Default Content Inquiry

2017-08-28 Thread Joel Kulesza
Colleagues:

Is there a mechanism for modifying how Insert -> Labels are automatically
populated?

It appears to populate with the name of the associated entity, with spaces
changed to dashes, up to a certain character limit.

Can this character limit be raised?  Can the space->dash conversion be
modified?

My ultimate goal is to provide more context in the labels themselves
(mostly through NOT truncating them).  I usually just copy/paste the
associated information of the default label; however, it would be
convenient if something like this outcome could be made automatic.  That
said, I'm glad the clickable UI element is truncated...

My apologies if such functionality is there and I've overlooked it (e.g.,
Section 6.1 of the User's Guide).

Thank you,
Joel


Re: texlive2017 and lyx SOLVED for me

2017-08-26 Thread Wolfgang Engelmann



Am 26.08.2017 um 16:09 schrieb Kornel Benko:

Am Samstag, 26. August 2017 um 15:59:20, schrieb Wolfgang Engelmann 
<engelm...@uni-tuebingen.de>

Am 26.08.2017 um 12:20 schrieb Kornel Benko:

Am Samstag, 26. August 2017 um 10:31:49, schrieb Wolfgang Engelmann 
<engelm...@uni-tuebingen.de>

What worked for me: I started |tlmgr| in gui mode with

|sudo env PATH="$PATH" tlmgr --gui |

That's the way it should work, if you install as root.


and then in the third menu chose the last item but one (in my German
menu, that is menu "Aktionen" (actions?) and item "Verwaltung der
symbolischen Links" (administration of symbolic links?). In the
ensuing dialogue window I clicked the button "Symbolische Links
erneuern" (renew symbolic links?). Now

|sudo tlmgr --OPTIONS |

works without problems. I'm sure there's also a command line way of
doing this

---

and another note:

You really don't have to add the directory of |tlmgr| to the path. A
simple quick solution is using |which|, e.g.:

|sudo $(which tlmgr) update --list  |

It should be like the previous, you have to set PATH
# sudo env PATH="$PATH" tlmgr update --list


Both proposals are not working for me. In the first proposal the actions
menu is grayed out, in the second: update command not found
Wolfgang

What I would suggest (if you are user engelmann) is:
# cd /usr/local/texlive
# sudo chown -R engelmann.engelmann .
But that is dangerous, if you are not alone on your system. It is up to you to 
decide.
If you do this, then from now on you should not use 'sudo' anymore in 
connection with texlive.

Kornel

Thanks again, Kornel,
I used your chown suggestion and it worked (by the way, why is
engelmann.engelmann used?). After reconfigure I can now work with lyx
again. That's good.

I supposed your username is "engelmann" and the group you own is  "engelmann" 
too.
The chown as used sets user and group to all files.


Wolfgang

Kornel

Thanks for explaining, Wolfgang


Re: texlive2017 and lyx SOLVED for me

2017-08-26 Thread Kornel Benko
Am Samstag, 26. August 2017 um 15:59:20, schrieb Wolfgang Engelmann 
<engelm...@uni-tuebingen.de>
> 
> Am 26.08.2017 um 12:20 schrieb Kornel Benko:
> > Am Samstag, 26. August 2017 um 10:31:49, schrieb Wolfgang Engelmann 
> > <engelm...@uni-tuebingen.de>
> >>> What worked for me: I started |tlmgr| in gui mode with
> >>>
> >>> |sudo env PATH="$PATH" tlmgr --gui |
> > That's the way it should work, if you install as root.
> >
> >>> and then in the third menu chose the last item but one (in my German
> >>> menu, that is menu "Aktionen" (actions?) and item "Verwaltung der
> >>> symbolischen Links" (administration of symbolic links?). In the
> >>> ensuing dialogue window I clicked the button "Symbolische Links
> >>> erneuern" (renew symbolic links?). Now
> >>>
> >>> |sudo tlmgr --OPTIONS |
> >>>
> >>> works without problems. I'm sure there's also a command line way of
> >>> doing this
> >>>
> >>> ---
> >>>
> >>> and another note:
> >>>
> >>> You really don't have to add the directory of |tlmgr| to the path. A
> >>> simple quick solution is using |which|, e.g.:
> >>>
> >>> |sudo $(which tlmgr) update --list  |
> > It should be like the previous, you have to set PATH
> > # sudo env PATH="$PATH" tlmgr update --list
> >
> >> Both proposals are not working for me. In the first proposal the actions
> >> menu is grayed out, in the second: update command not found
> >> Wolfgang
> > What I would suggest (if you are user engelmann) is:
> > # cd /usr/local/texlive
> >     # sudo chown -R engelmann.engelmann .
> > But that is dangerous, if you are not alone on your system. It is up to you 
> > to decide.
> > If you do this, then from now on you should not use 'sudo' anymore in 
> > connection with texlive.
> >
> > Kornel
> Thanks again, Kornel,
> I used your chown suggestion and it worked (by the way, why is 
> engelmann.engelmann used?). After reconfigure I can now work with lyx 
> again. That's good.

I supposed your username is "engelmann" and the group you own is  "engelmann" 
too.
The chown as used sets user and group to all files.

> Wolfgang

Kornel

signature.asc
Description: This is a digitally signed message part.


Re: texlive2017 and lyx SOLVED for me

2017-08-26 Thread Wolfgang Engelmann



Am 26.08.2017 um 12:20 schrieb Kornel Benko:

Am Samstag, 26. August 2017 um 10:31:49, schrieb Wolfgang Engelmann 
<engelm...@uni-tuebingen.de>

What worked for me: I started |tlmgr| in gui mode with

|sudo env PATH="$PATH" tlmgr --gui |

That's the way it should work, if you install as root.


and then in the third menu chose the last item but one (in my German
menu, that is menu "Aktionen" (actions?) and item "Verwaltung der
symbolischen Links" (administration of symbolic links?). In the
ensuing dialogue window I clicked the button "Symbolische Links
erneuern" (renew symbolic links?). Now

|sudo tlmgr --OPTIONS |

works without problems. I'm sure there's also a command line way of
doing this

---

and another note:

You really don't have to add the directory of |tlmgr| to the path. A
simple quick solution is using |which|, e.g.:

|sudo $(which tlmgr) update --list  |

It should be like the previous, you have to set PATH
# sudo env PATH="$PATH" tlmgr update --list


Both proposals are not working for me. In the first proposal the actions
menu is grayed out, in the second: update command not found
Wolfgang

What I would suggest (if you are user engelmann) is:
# cd /usr/local/texlive
# sudo chown -R engelmann.engelmann .
But that is dangerous, if you are not alone on your system. It is up to you to 
decide.
If you do this, then from now on you should not use 'sudo' anymore in 
connection with texlive.

Kornel

Thanks again, Kornel,
I used your chown suggestion and it worked (by the way, why is 
engelmann.engelmann used?). After reconfigure I can now work with lyx 
again. That's good.

Wolfgang


Re: texlive2017 and lyx

2017-08-26 Thread Kornel Benko
Am Samstag, 26. August 2017 um 10:31:49, schrieb Wolfgang Engelmann 

> > What worked for me: I started |tlmgr| in gui mode with
> >
> > |sudo env PATH="$PATH" tlmgr --gui |

That's the way it should work, if you install as root.

> > and then in the third menu chose the last item but one (in my German 
> > menu, that is menu "Aktionen" (actions?) and item "Verwaltung der 
> > symbolischen Links" (administration of symbolic links?). In the 
> > ensuing dialogue window I clicked the button "Symbolische Links 
> > erneuern" (renew symbolic links?). Now
> >
> > |sudo tlmgr --OPTIONS |
> >
> > works without problems. I'm sure there's also a command line way of 
> > doing this 
> >
> > ---
> >
> > and another note:
> >
> > You really don't have to add the directory of |tlmgr| to the path. A 
> > simple quick solution is using |which|, e.g.:
> >
> > |sudo $(which tlmgr) update --list  |

It should be like the previous, you have to set PATH
# sudo env PATH="$PATH" tlmgr update --list

> Both proposals are not working for me. In the first proposal the actions 
> menu is grayed out, in the second: update command not found
> Wolfgang

What I would suggest (if you are user engelmann) is:
# cd /usr/local/texlive
# sudo chown -R engelmann.engelmann .
But that is dangerous, if you are not alone on your system. It is up to you to 
decide.
If you do this, then from now on you should not use 'sudo' anymore in 
connection with texlive.

Kornel


signature.asc
Description: This is a digitally signed message part.


Re: texlive2017 and lyx

2017-08-26 Thread Wolfgang Engelmann



Am 26.08.2017 um 10:15 schrieb Wolfgang Engelmann:




Am 26.08.2017 um 09:26 schrieb Wolfgang Engelmann:



Am 25.08.2017 um 21:28 schrieb Kornel Benko:
Am Freitag, 25. August 2017 um 20:30:47, schrieb Wolfgang Engelmann 


Am 25.08.2017 um 19:15 schrieb Kornel Benko:
Am Freitag, 25. August 2017 um 16:09:14, schrieb Wolfgang 
Engelmann 

Am 25.08.2017 um 15:46 schrieb Kornel Benko:
Am Freitag, 25. August 2017 um 15:20:57, schrieb Wolfgang 
Engelmann 

I was too quick: The tlmgr is from an earlier texlive which is in
/usr/share/texlive2016.
How do I get the tlmgr from
/usr/local/texlive/2017/bin/x86_64-linux
working? Do I have to set a path? How? Which one?
sorra for silly questions, but I got stuck here
Wolfgang
Why don't you set your PATH so that 
"/usr/local/texlive/2017/bin/x86_64-linux" is before "/usr/bin"?


Kornel

Isn't, what I have? >>
#paths for texlive2017
PATH=/usr/local/texlive/2017/bin/i386-linux:$PATH; export PATH
MANPATH=/usr/local/texlive/2017/texmf-dist/doc/man:$MANPATH; 
export MANPATH
INFOPATH=/usr/local/texlive/2017/texmf-dist/doc/info:$INFOPATH; 
export

INFOPATH
Wolfgang

WRONG PATH, change "i386-linux" to "x86_64-linux"

If you do this, then what does
# which tlmgr
or
# where tlmgr
say?

Is /usr/local/texlive/2017/bin/x86_64-linux/tlmgr executable?

Kornel

Thanks, Kornel, I have changed to what you wrote. How would I on the
command line change the rights for the tlmgr.pl, which are right now
user=root and group=root?

This is OK, if you installed as root (which you have apparently)


Unfortunately I have uninstalled the 2016 texlive and have no tlmgr
available

tlmgr is part of TL2017 as well.
Here:
#which tlmgr
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
# ls -l /usr/local/texlive/2017/bin/x86_64-linux/tlmgr

~/Downloads$ which tlmgr
  >no response

Means that the PATH is not OK.
Check
# ls -l /usr/local/texlive/2017/bin/x86_64-linux/tlmgr
lrwxrwxrwx 1 kornel kornel 41 nov 25  2016 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr -> 
../../texmf-dist/scripts/texlive/tlmgr.pl

# ls -lL /usr/local/texlive/2017/bin/x86_64-linux/tlmgr
-rwxr-xr-x 1 kornel kornel 300762 júl 18 01:59 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr


(I installed it as user kornel, so I am not forced to be root for 
instance for updates)



we@wolfgang-Mr-Whisper-Ultra-SSD-II:~/Downloads$ where tlmgr
bash: where: Kommando nicht gefunden.

Where is csh built-in command, sorry, try using csh or tcsh


I tried also ~/Downloads$ whereis tlmgr
tlmgr:
no further output.
Its a mess with me!

whereis does not respect PATH, so its output is not relevant.


Wolfgang

Kornel

Thanks, Kornel, for your patience.
Here are the outputs; I see no difference to yours:
we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$ which tlmgr
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$ ls -l 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
lrwxrwxrwx 1 root root 41 Nov 25  2016 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr -> 
../../texmf-dist/scripts/texlive/tlmgr.pl
we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$ ls -l 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
lrwxrwxrwx 1 root root 41 Nov 25  2016 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr -> 
../../texmf-dist/scripts/texlive/tlmgr.pl
we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$ ls -lL 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
-rwxr-xr-x 1 root root 299941 Mai 19 17:07 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr

we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$

where tlmgr
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local/texlive/2017/texmf-dist/scripts 



if I start as user
tlmgr gui
I get the menus but are told I have no rights and most of the 
selections are grayed out.

If I start as root, the command is not found.
# tlmgr gui
bash: tlmgr: Kommando nicht gefunden.

do I need different PATH settings for the root?

Confused: Wolfgang

I found under

https://askubuntu.com/questions/66498/setting-tex-live-path-for-root

What worked for me: I started |tlmgr| in gui mode with

|sudo env PATH="$PATH" tlmgr --gui |

and then in the third menu chose the last item but one (in my German 
menu, that is menu "Aktionen" (actions?) and item "Verwaltung der 
symbolischen Links" (administration of symbolic links?). In the 
ensuing dialogue window I clicked the button "Symbolische Links 
erneuern" (renew symbolic links?). Now


|sudo tlmgr --OPTIONS |

works without problems. I'm sure there's also a command line way of 
doing this ;)


---

and another note:

You really don't have to add the directory of |tlmgr| to the path. A 
simple quick solution is using |which|, e.g.:


|sudo $(which tlmgr) update --list  |
Both proposals are not working for me. In the first proposal the 

Re: texlive2017 and lyx

2017-08-26 Thread Wolfgang Engelmann



Am 26.08.2017 um 09:26 schrieb Wolfgang Engelmann:



Am 25.08.2017 um 21:28 schrieb Kornel Benko:
Am Freitag, 25. August 2017 um 20:30:47, schrieb Wolfgang Engelmann 


Am 25.08.2017 um 19:15 schrieb Kornel Benko:
Am Freitag, 25. August 2017 um 16:09:14, schrieb Wolfgang Engelmann 


Am 25.08.2017 um 15:46 schrieb Kornel Benko:
Am Freitag, 25. August 2017 um 15:20:57, schrieb Wolfgang 
Engelmann 

I was too quick: The tlmgr is from an earlier texlive which is in
/usr/share/texlive2016.
How do I get the tlmgr from
/usr/local/texlive/2017/bin/x86_64-linux
working? Do I have to set a path? How? Which one?
sorra for silly questions, but I got stuck here
Wolfgang
Why don't you set your PATH so that 
"/usr/local/texlive/2017/bin/x86_64-linux" is before "/usr/bin"?


Kornel

Isn't, what I have? >>
#paths for texlive2017
PATH=/usr/local/texlive/2017/bin/i386-linux:$PATH; export PATH
MANPATH=/usr/local/texlive/2017/texmf-dist/doc/man:$MANPATH; 
export MANPATH
INFOPATH=/usr/local/texlive/2017/texmf-dist/doc/info:$INFOPATH; 
export

INFOPATH
Wolfgang

WRONG PATH, change "i386-linux" to "x86_64-linux"

If you do this, then what does
# which tlmgr
or
# where tlmgr
say?

Is /usr/local/texlive/2017/bin/x86_64-linux/tlmgr executable?

Kornel

Thanks, Kornel, I have changed to what you wrote. How would I on the
command line change the rights for the tlmgr.pl, which are right now
user=root and group=root?

This is OK, if you installed as root (which you have apparently)


Unfortunately I have uninstalled the 2016 texlive and have no tlmgr
available

tlmgr is part of TL2017 as well.
Here:
#which tlmgr
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
# ls -l /usr/local/texlive/2017/bin/x86_64-linux/tlmgr

~/Downloads$ which tlmgr
  >no response

Means that the PATH is not OK.
Check
# ls -l /usr/local/texlive/2017/bin/x86_64-linux/tlmgr
lrwxrwxrwx 1 kornel kornel 41 nov 25  2016 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr -> 
../../texmf-dist/scripts/texlive/tlmgr.pl

# ls -lL /usr/local/texlive/2017/bin/x86_64-linux/tlmgr
-rwxr-xr-x 1 kornel kornel 300762 júl 18 01:59 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr


(I installed it as user kornel, so I am not forced to be root for 
instance for updates)



we@wolfgang-Mr-Whisper-Ultra-SSD-II:~/Downloads$ where tlmgr
bash: where: Kommando nicht gefunden.

Where is csh built-in command, sorry, try using csh or tcsh


I tried also ~/Downloads$ whereis tlmgr
tlmgr:
no further output.
Its a mess with me!

whereis does not respect PATH, so its output is not relevant.


Wolfgang

Kornel

Thanks, Kornel, for your patience.
Here are the outputs; I see no difference to yours:
we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$ which tlmgr
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$ ls -l 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
lrwxrwxrwx 1 root root 41 Nov 25  2016 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr -> 
../../texmf-dist/scripts/texlive/tlmgr.pl
we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$ ls -l 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
lrwxrwxrwx 1 root root 41 Nov 25  2016 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr -> 
../../texmf-dist/scripts/texlive/tlmgr.pl
we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$ ls -lL 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
-rwxr-xr-x 1 root root 299941 Mai 19 17:07 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr

we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$

where tlmgr
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local/texlive/2017/texmf-dist/scripts 



if I start as user
tlmgr gui
I get the menus but are told I have no rights and most of the 
selections are grayed out.

If I start as root, the command is not found.
# tlmgr gui
bash: tlmgr: Kommando nicht gefunden.

do I need different PATH settings for the root?

Confused: Wolfgang

I found under

https://askubuntu.com/questions/66498/setting-tex-live-path-for-root

What worked for me: I started |tlmgr| in gui mode with

|sudo env PATH="$PATH" tlmgr --gui |

and then in the third menu chose the last item but one (in my German 
menu, that is menu "Aktionen" (actions?) and item "Verwaltung der 
symbolischen Links" (administration of symbolic links?). In the ensuing 
dialogue window I clicked the button "Symbolische Links erneuern" (renew 
symbolic links?). Now


|sudo tlmgr --OPTIONS |

works without problems. I'm sure there's also a command line way of 
doing this ;)


---

and another note:

You really don't have to add the directory of |tlmgr| to the path. A 
simple quick solution is using |which|, e.g.:


|sudo $(which tlmgr) update --list  |



Re: texlive2017 and lyx

2017-08-26 Thread Wolfgang Engelmann



Am 25.08.2017 um 21:28 schrieb Kornel Benko:

Am Freitag, 25. August 2017 um 20:30:47, schrieb Wolfgang Engelmann 


Am 25.08.2017 um 19:15 schrieb Kornel Benko:

Am Freitag, 25. August 2017 um 16:09:14, schrieb Wolfgang Engelmann 


Am 25.08.2017 um 15:46 schrieb Kornel Benko:

Am Freitag, 25. August 2017 um 15:20:57, schrieb Wolfgang Engelmann 


I was too quick: The tlmgr is from an earlier texlive which is in
/usr/share/texlive2016.
How do I get the tlmgr from
/usr/local/texlive/2017/bin/x86_64-linux
working? Do I have to set a path? How? Which one?
sorra for silly questions, but I got stuck here
Wolfgang

Why don't you set your PATH so that "/usr/local/texlive/2017/bin/x86_64-linux" is before 
"/usr/bin"?

Kornel

Isn't, what I have? >>
#paths for texlive2017
PATH=/usr/local/texlive/2017/bin/i386-linux:$PATH; export PATH
MANPATH=/usr/local/texlive/2017/texmf-dist/doc/man:$MANPATH; export MANPATH
INFOPATH=/usr/local/texlive/2017/texmf-dist/doc/info:$INFOPATH; export
INFOPATH
Wolfgang

WRONG PATH, change "i386-linux" to "x86_64-linux"

If you do this, then what does
# which tlmgr
or
# where tlmgr
say?

Is /usr/local/texlive/2017/bin/x86_64-linux/tlmgr executable?

Kornel

Thanks, Kornel, I have changed to what you wrote. How would I on the
command line change the rights for the tlmgr.pl, which are right now
user=root and group=root?

This is OK, if you installed as root (which you have apparently)


Unfortunately I have uninstalled the 2016 texlive and have no tlmgr
available

tlmgr is part of TL2017 as well.
Here:
#which tlmgr
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
# ls -l /usr/local/texlive/2017/bin/x86_64-linux/tlmgr

~/Downloads$ which tlmgr
  >no response

Means that the PATH is not OK.
Check
# ls -l /usr/local/texlive/2017/bin/x86_64-linux/tlmgr
lrwxrwxrwx 1 kornel kornel 41 nov 25  2016 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr -> 
../../texmf-dist/scripts/texlive/tlmgr.pl
# ls -lL /usr/local/texlive/2017/bin/x86_64-linux/tlmgr
-rwxr-xr-x 1 kornel kornel 300762 júl 18 01:59 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr

(I installed it as user kornel, so I am not forced to be root for instance for 
updates)


we@wolfgang-Mr-Whisper-Ultra-SSD-II:~/Downloads$ where tlmgr
bash: where: Kommando nicht gefunden.

Where is csh built-in command, sorry, try using csh or tcsh


I tried also ~/Downloads$ whereis tlmgr
tlmgr:
no further output.
Its a mess with me!

whereis does not respect PATH, so its output is not relevant.


Wolfgang

Kornel

Thanks, Kornel, for your patience.
Here are the outputs; I see no difference to yours:
we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$ which tlmgr
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$ ls -l 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
lrwxrwxrwx 1 root root 41 Nov 25  2016 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr -> 
../../texmf-dist/scripts/texlive/tlmgr.pl
we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$ ls -l 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
lrwxrwxrwx 1 root root 41 Nov 25  2016 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr -> 
../../texmf-dist/scripts/texlive/tlmgr.pl
we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$ ls -lL 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
-rwxr-xr-x 1 root root 299941 Mai 19 17:07 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr

we@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local$

where tlmgr
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local/texlive/2017/texmf-dist/scripts

if I start as user
tlmgr gui
I get the menus but are told I have no rights and most of the selections 
are grayed out.

If I start as root, the command is not found.
# tlmgr gui
bash: tlmgr: Kommando nicht gefunden.

do I need different PATH settings for the root?

Confused: Wolfgang


Re: texlive2017 and lyx

2017-08-25 Thread Kornel Benko
Am Freitag, 25. August 2017 um 20:30:47, schrieb Wolfgang Engelmann 

> 
> Am 25.08.2017 um 19:15 schrieb Kornel Benko:
> > Am Freitag, 25. August 2017 um 16:09:14, schrieb Wolfgang Engelmann 
> > 
> >> Am 25.08.2017 um 15:46 schrieb Kornel Benko:
> >>> Am Freitag, 25. August 2017 um 15:20:57, schrieb Wolfgang Engelmann 
> >>> 
>  I was too quick: The tlmgr is from an earlier texlive which is in
>  /usr/share/texlive2016.
>  How do I get the tlmgr from
>  /usr/local/texlive/2017/bin/x86_64-linux
>  working? Do I have to set a path? How? Which one?
>  sorra for silly questions, but I got stuck here
>  Wolfgang
> >>> Why don't you set your PATH so that 
> >>> "/usr/local/texlive/2017/bin/x86_64-linux" is before "/usr/bin"?
> >>>
> >>>   Kornel
> >> Isn't, what I have? >>
> >> #paths for texlive2017
> >> PATH=/usr/local/texlive/2017/bin/i386-linux:$PATH; export PATH
> >> MANPATH=/usr/local/texlive/2017/texmf-dist/doc/man:$MANPATH; export MANPATH
> >> INFOPATH=/usr/local/texlive/2017/texmf-dist/doc/info:$INFOPATH; export
> >> INFOPATH
> >> Wolfgang
> > WRONG PATH, change "i386-linux" to "x86_64-linux"
> >
> > If you do this, then what does
> > # which tlmgr
> > or
> > # where tlmgr
> > say?
> >
> > Is /usr/local/texlive/2017/bin/x86_64-linux/tlmgr executable?
> >
> > Kornel
> Thanks, Kornel, I have changed to what you wrote. How would I on the 
> command line change the rights for the tlmgr.pl, which are right now 
> user=root and group=root?

This is OK, if you installed as root (which you have apparently)

> Unfortunately I have uninstalled the 2016 texlive and have no tlmgr 
> available

tlmgr is part of TL2017 as well.
Here:
#which tlmgr
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr
# ls -l /usr/local/texlive/2017/bin/x86_64-linux/tlmgr
> ~/Downloads$ which tlmgr
>  >no response

Means that the PATH is not OK.
Check
# ls -l /usr/local/texlive/2017/bin/x86_64-linux/tlmgr
lrwxrwxrwx 1 kornel kornel 41 nov 25  2016 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr -> 
../../texmf-dist/scripts/texlive/tlmgr.pl
# ls -lL /usr/local/texlive/2017/bin/x86_64-linux/tlmgr
-rwxr-xr-x 1 kornel kornel 300762 júl 18 01:59 
/usr/local/texlive/2017/bin/x86_64-linux/tlmgr

(I installed it as user kornel, so I am not forced to be root for instance for 
updates)

> we@wolfgang-Mr-Whisper-Ultra-SSD-II:~/Downloads$ where tlmgr
> bash: where: Kommando nicht gefunden.

Where is csh built-in command, sorry, try using csh or tcsh

> I tried also ~/Downloads$ whereis tlmgr
> tlmgr:
> no further output.
> Its a mess with me!

whereis does not respect PATH, so its output is not relevant.

> Wolfgang

Kornel

signature.asc
Description: This is a digitally signed message part.


Re: texlive2017 and lyx

2017-08-25 Thread Wolfgang Engelmann



Am 25.08.2017 um 20:30 schrieb Wolfgang Engelmann:



Am 25.08.2017 um 19:15 schrieb Kornel Benko:
Am Freitag, 25. August 2017 um 16:09:14, schrieb Wolfgang Engelmann 


Am 25.08.2017 um 15:46 schrieb Kornel Benko:
Am Freitag, 25. August 2017 um 15:20:57, schrieb Wolfgang Engelmann 


I was too quick: The tlmgr is from an earlier texlive which is in
/usr/share/texlive2016.
How do I get the tlmgr from
/usr/local/texlive/2017/bin/x86_64-linux
working? Do I have to set a path? How? Which one?
sorra for silly questions, but I got stuck here
Wolfgang
Why don't you set your PATH so that 
"/usr/local/texlive/2017/bin/x86_64-linux" is before "/usr/bin"?


Kornel

Isn't, what I have? >>
#paths for texlive2017
PATH=/usr/local/texlive/2017/bin/i386-linux:$PATH; export PATH
MANPATH=/usr/local/texlive/2017/texmf-dist/doc/man:$MANPATH; export 
MANPATH

INFOPATH=/usr/local/texlive/2017/texmf-dist/doc/info:$INFOPATH; export
INFOPATH
Wolfgang

WRONG PATH, change "i386-linux" to "x86_64-linux"

If you do this, then what does
# which tlmgr
or
# where tlmgr
say?

Is /usr/local/texlive/2017/bin/x86_64-linux/tlmgr executable?

Kornel
Thanks, Kornel, I have changed to what you wrote. How would I on the 
command line change the rights for the tlmgr.pl, which are right now 
user=root and group=root?
Unfortunately I have uninstalled the 2016 texlive and have no tlmgr 
available

~/Downloads$ which tlmgr
>no response
we@wolfgang-Mr-Whisper-Ultra-SSD-II:~/Downloads$ where tlmgr
bash: where: Kommando nicht gefunden.
I tried also ~/Downloads$ whereis tlmgr
tlmgr:
no further output.
Its a mess with me!
Wolfgang


I used chmod a+rx tlmgr.pl
but the response to which and where/wheris has not changed
Wolfgang


Re: texlive2017 and lyx

2017-08-25 Thread Wolfgang Engelmann



Am 25.08.2017 um 19:15 schrieb Kornel Benko:

Am Freitag, 25. August 2017 um 16:09:14, schrieb Wolfgang Engelmann 


Am 25.08.2017 um 15:46 schrieb Kornel Benko:

Am Freitag, 25. August 2017 um 15:20:57, schrieb Wolfgang Engelmann 


I was too quick: The tlmgr is from an earlier texlive which is in
/usr/share/texlive2016.
How do I get the tlmgr from
/usr/local/texlive/2017/bin/x86_64-linux
working? Do I have to set a path? How? Which one?
sorra for silly questions, but I got stuck here
Wolfgang

Why don't you set your PATH so that "/usr/local/texlive/2017/bin/x86_64-linux" is before 
"/usr/bin"?

Kornel

Isn't, what I have? >>
#paths for texlive2017
PATH=/usr/local/texlive/2017/bin/i386-linux:$PATH; export PATH
MANPATH=/usr/local/texlive/2017/texmf-dist/doc/man:$MANPATH; export MANPATH
INFOPATH=/usr/local/texlive/2017/texmf-dist/doc/info:$INFOPATH; export
INFOPATH
Wolfgang

WRONG PATH, change "i386-linux" to "x86_64-linux"

If you do this, then what does
# which tlmgr
or
# where tlmgr
say?

Is /usr/local/texlive/2017/bin/x86_64-linux/tlmgr executable?

Kornel
Thanks, Kornel, I have changed to what you wrote. How would I on the 
command line change the rights for the tlmgr.pl, which are right now 
user=root and group=root?
Unfortunately I have uninstalled the 2016 texlive and have no tlmgr 
available

~/Downloads$ which tlmgr
>no response
we@wolfgang-Mr-Whisper-Ultra-SSD-II:~/Downloads$ where tlmgr
bash: where: Kommando nicht gefunden.
I tried also ~/Downloads$ whereis tlmgr
tlmgr:
no further output.
Its a mess with me!
Wolfgang



Re: texlive2017 and lyx

2017-08-25 Thread Kornel Benko
Am Freitag, 25. August 2017 um 16:09:14, schrieb Wolfgang Engelmann 

> 
> Am 25.08.2017 um 15:46 schrieb Kornel Benko:
> > Am Freitag, 25. August 2017 um 15:20:57, schrieb Wolfgang Engelmann 
> > 
> >> I was too quick: The tlmgr is from an earlier texlive which is in
> >> /usr/share/texlive2016.
> >> How do I get the tlmgr from
> >> /usr/local/texlive/2017/bin/x86_64-linux
> >> working? Do I have to set a path? How? Which one?
> >> sorra for silly questions, but I got stuck here
> >> Wolfgang
> > Why don't you set your PATH so that 
> > "/usr/local/texlive/2017/bin/x86_64-linux" is before "/usr/bin"?
> >
> > Kornel
> Isn't, what I have? >>
> #paths for texlive2017
> PATH=/usr/local/texlive/2017/bin/i386-linux:$PATH; export PATH
> MANPATH=/usr/local/texlive/2017/texmf-dist/doc/man:$MANPATH; export MANPATH
> INFOPATH=/usr/local/texlive/2017/texmf-dist/doc/info:$INFOPATH; export 
> INFOPATH
> Wolfgang

WRONG PATH, change "i386-linux" to "x86_64-linux"

If you do this, then what does
# which tlmgr
or
# where tlmgr
say?

Is /usr/local/texlive/2017/bin/x86_64-linux/tlmgr executable?

Kornel

signature.asc
Description: This is a digitally signed message part.


Re: texlive2017 and lyx

2017-08-25 Thread Wolfgang Engelmann



Am 25.08.2017 um 15:46 schrieb Kornel Benko:

Am Freitag, 25. August 2017 um 15:20:57, schrieb Wolfgang Engelmann 


I was too quick: The tlmgr is from an earlier texlive which is in
/usr/share/texlive2016.
How do I get the tlmgr from
/usr/local/texlive/2017/bin/x86_64-linux
working? Do I have to set a path? How? Which one?
sorra for silly questions, but I got stuck here
Wolfgang

Why don't you set your PATH so that "/usr/local/texlive/2017/bin/x86_64-linux" is before 
"/usr/bin"?

Kornel

Isn't, what I have? >>
#paths for texlive2017
PATH=/usr/local/texlive/2017/bin/i386-linux:$PATH; export PATH
MANPATH=/usr/local/texlive/2017/texmf-dist/doc/man:$MANPATH; export MANPATH
INFOPATH=/usr/local/texlive/2017/texmf-dist/doc/info:$INFOPATH; export 
INFOPATH

Wolfgang


Re: texlive2017 and lyx

2017-08-25 Thread Kornel Benko
Am Freitag, 25. August 2017 um 15:20:57, schrieb Wolfgang Engelmann 

> I was too quick: The tlmgr is from an earlier texlive which is in 
> /usr/share/texlive2016.
> How do I get the tlmgr from
> /usr/local/texlive/2017/bin/x86_64-linux
> working? Do I have to set a path? How? Which one?
> sorra for silly questions, but I got stuck here
> Wolfgang

Why don't you set your PATH so that "/usr/local/texlive/2017/bin/x86_64-linux" 
is before "/usr/bin"?

Kornel

signature.asc
Description: This is a digitally signed message part.


Re: texlive2017 and lyx

2017-08-25 Thread Wolfgang Engelmann



Am 25.08.2017 um 14:50 schrieb Wolfgang Engelmann:



Am 25.08.2017 um 14:11 schrieb Wolfgang Engelmann:



Am 25.08.2017 um 13:48 schrieb Wolfgang Engelmann:



Am 25.08.2017 um 13:16 schrieb Steve Litt:

On Fri, 25 Aug 2017 11:34:25 +0200
Wolfgang Engelmann  wrote:


Two questions:

What do I have to do to get the texlive2017 working

If your older texlive is working (like 2016), I'd imagine there's a
tlmgr command to bring everything up to 2017.


I have installed texlive2017 from the CTAN DVD on my PC with debian
Jessie at /usr/local/

Unless you have no reasonable speed Internet access and can't go
somewhere else that has such access, I'd use the proper tlmgr command.

SteveT

thanks, Steve,
tlmgr update --self
(running on Debian, switching to user mode!)
Unknown directive ...containerchecksum 
06c8c1fff8b025f6f55f8629af6e41a6dd695e13bbdfe8b78b678e9cb0cfa509826355f4ece20d8a99b49bcee3c5931b8d766f0fc3dae0d6a645303d487600b0... 
, please fix it! at /usr/share/texlive/tlpkg/TeXLive/TLPOBJ.pm line 
210, <$retfh> line 5761.
is this something I could fix easily or is it better to install a 
new tlmgr?

Wolfgang

I checked for tlmgr in my system, and it is supposed to be in 
/usr/bin, where I, however, do not find it; and secondly in 
/usr/local/texlive/2017/bin/x86_64-linux where it is found.

How should I proceed?
Wolfgang
I managed to set the pathes and to get tlmgr. Trying now to become 
familiar with this gui.

Thanks for the pointer,
Wolfgang
I was too quick: The tlmgr is from an earlier texlive which is in 
/usr/share/texlive2016.

How do I get the tlmgr from
/usr/local/texlive/2017/bin/x86_64-linux
working? Do I have to set a path? How? Which one?
sorra for silly questions, but I got stuck here
Wolfgang


Re: texlive2017 and lyx

2017-08-25 Thread Wolfgang Engelmann



Am 25.08.2017 um 14:11 schrieb Wolfgang Engelmann:



Am 25.08.2017 um 13:48 schrieb Wolfgang Engelmann:



Am 25.08.2017 um 13:16 schrieb Steve Litt:

On Fri, 25 Aug 2017 11:34:25 +0200
Wolfgang Engelmann  wrote:


Two questions:

What do I have to do to get the texlive2017 working

If your older texlive is working (like 2016), I'd imagine there's a
tlmgr command to bring everything up to 2017.


I have installed texlive2017 from the CTAN DVD on my PC with debian
Jessie at /usr/local/

Unless you have no reasonable speed Internet access and can't go
somewhere else that has such access, I'd use the proper tlmgr command.

SteveT

thanks, Steve,
tlmgr update --self
(running on Debian, switching to user mode!)
Unknown directive ...containerchecksum 
06c8c1fff8b025f6f55f8629af6e41a6dd695e13bbdfe8b78b678e9cb0cfa509826355f4ece20d8a99b49bcee3c5931b8d766f0fc3dae0d6a645303d487600b0... 
, please fix it! at /usr/share/texlive/tlpkg/TeXLive/TLPOBJ.pm line 
210, <$retfh> line 5761.
is this something I could fix easily or is it better to install a new 
tlmgr?

Wolfgang

I checked for tlmgr in my system, and it is supposed to be in 
/usr/bin, where I, however, do not find it; and secondly in 
/usr/local/texlive/2017/bin/x86_64-linux where it is found.

How should I proceed?
Wolfgang
I managed to set the pathes and to get tlmgr. Trying now to become 
familiar with this gui.

Thanks for the pointer,
Wolfgang


Re: texlive2017 and lyx

2017-08-25 Thread Wolfgang Engelmann



Am 25.08.2017 um 13:48 schrieb Wolfgang Engelmann:



Am 25.08.2017 um 13:16 schrieb Steve Litt:

On Fri, 25 Aug 2017 11:34:25 +0200
Wolfgang Engelmann  wrote:


Two questions:

What do I have to do to get the texlive2017 working

If your older texlive is working (like 2016), I'd imagine there's a
tlmgr command to bring everything up to 2017.


I have installed texlive2017 from the CTAN DVD on my PC with debian
Jessie at /usr/local/

Unless you have no reasonable speed Internet access and can't go
somewhere else that has such access, I'd use the proper tlmgr command.

SteveT

thanks, Steve,
tlmgr update --self
(running on Debian, switching to user mode!)
Unknown directive ...containerchecksum 
06c8c1fff8b025f6f55f8629af6e41a6dd695e13bbdfe8b78b678e9cb0cfa509826355f4ece20d8a99b49bcee3c5931b8d766f0fc3dae0d6a645303d487600b0... 
, please fix it! at /usr/share/texlive/tlpkg/TeXLive/TLPOBJ.pm line 
210, <$retfh> line 5761.
is this something I could fix easily or is it better to install a new 
tlmgr?

Wolfgang

I checked for tlmgr in my system, and it is supposed to be in /usr/bin, 
where I, however, do not find it; and secondly in 
/usr/local/texlive/2017/bin/x86_64-linux where it is found.

How should I proceed?
Wolfgang


Re: texlive2017 and lyx

2017-08-25 Thread Wolfgang Engelmann



Am 25.08.2017 um 13:16 schrieb Steve Litt:

On Fri, 25 Aug 2017 11:34:25 +0200
Wolfgang Engelmann  wrote:


Two questions:

What do I have to do to get the texlive2017 working

If your older texlive is working (like 2016), I'd imagine there's a
tlmgr command to bring everything up to 2017.


I have installed texlive2017 from the CTAN DVD on my PC with debian
Jessie at /usr/local/

Unless you have no reasonable speed Internet access and can't go
somewhere else that has such access, I'd use the proper tlmgr command.

SteveT

thanks, Steve,
tlmgr update --self
(running on Debian, switching to user mode!)
Unknown directive ...containerchecksum 
06c8c1fff8b025f6f55f8629af6e41a6dd695e13bbdfe8b78b678e9cb0cfa509826355f4ece20d8a99b49bcee3c5931b8d766f0fc3dae0d6a645303d487600b0... 
, please fix it! at /usr/share/texlive/tlpkg/TeXLive/TLPOBJ.pm line 210, 
<$retfh> line 5761.

is this something I could fix easily or is it better to install a new tlmgr?
Wolfgang



Re: texlive2017 and lyx

2017-08-25 Thread Steve Litt
On Fri, 25 Aug 2017 11:34:25 +0200
Wolfgang Engelmann  wrote:

> Two questions:
> 
> What do I have to do to get the texlive2017 working

If your older texlive is working (like 2016), I'd imagine there's a
tlmgr command to bring everything up to 2017.

> 
> I have installed texlive2017 from the CTAN DVD on my PC with debian 
> Jessie at /usr/local/

Unless you have no reasonable speed Internet access and can't go
somewhere else that has such access, I'd use the proper tlmgr command.

SteveT


texlive2017 and lyx

2017-08-25 Thread Wolfgang Engelmann

Two questions:

What do I have to do to get the texlive2017 working

How do I find out which texlive my lyx 2.3obeta1 is using

Wolfgang

For details see the following:

I have installed texlive2017 from the CTAN DVD on my PC with debian 
Jessie at /usr/local/


After

1 >> root@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local# umask 002 ./texlive

and

2 >> For the PATH I put  in /etc/profile.d a file texlive.sh
---
# TeX Live 2017 initialization script (sh)
TEXLIVEDIR=/usr/local/texlive/2017
if ! echo ${PATH} | /bin/grep -q ${TEXLIVEDIR}/bin/x86_64-linux ; then
   PATH=${TEXLIVEDIR}/bin/x86_64-linux:${PATH}
fi
if ! echo ${MANPATH} | /bin/grep -q ${TEXLIVEDIR}/texmf-dist/doc/man ; then
   MANPATH=${TEXLIVEDIR}/texmf-dist/doc/man:${MANPATH}
fi
if ! echo ${INFOPATH} | /bin/grep -q ${TEXLIVEDIR}/texmf-dist/doc/info ; 
then

   INFOPATH=${TEXLIVEDIR}/texmf-dist/doc/info:${INFOPATH}
fi
-

and

3>> root@wolfgang-Mr-Whisper-Ultra-SSD-II:/usr/local# texhash
texhash: Updating /usr/local/share/texmf/ls-R...
texhash: Updating /var/lib/texmf/ls-R-TEXLIVEDIST...
texhash: Updating /var/lib/texmf/ls-R-TEXMFMAIN...
texhash: Updating /var/lib/texmf/ls-R...
texhash: Done.

I tried

tex --version

but get
TeX 3.14159265 (TeX Live 2015/dev/Debian)
kpathsea version 6.2.1dev

instead of TeX Live 2017

Help very much appreciated by

Wolfgang



LyX version 2.3.0 (beta 1)

2017-08-17 Thread Scott Kostyshak
Public release of LyX version 2.3.0beta1


We are proud to announce the first public beta of the new LyX 2.3 series.
This pre-release is meant for testing and should not be used for serious work.
For curious users who would like to test in order to help catch bugs before
the 2.3.0 release, please back up all of your documents and be prepared for
the worst to happen. Most users (who desire a stable LyX version) should not
use this pre-release.

The 2.3 series has a rich set of new features compared to the current stable
series. An overview of the new features can be found here:

  http://wiki.lyx.org/LyX/NewInLyX23

You can download LyX 2.3.0beta1 from ftp://ftp.lyx.org/pub/lyx/devel/.

We appreciate your help in testing this pre-release!

The file lib/RELEASE-NOTES lists some known issues and problems compared
to the current stable releases (LyX 2.2.x). We strongly recommend that
packagers of LyX on various platforms and distributions read this file.

As with any major release, this one comes with a lot of new features but
also some bugs. If you think you have found a bug in LyX 2.3.0beta1, either
email the LyX developers' mailing list (lyx-devel at lists.lyx.org),
or open a bug report at https://www.lyx.org/trac/wiki/BugTrackerHome.
Please specify if the behavior you are reporting is different from behavior
in a previous LyX version.

If you have trouble using LyX or have a question, consult the
documentation that comes with LyX (under Help) and the LyX wiki, which you
will find at https://wiki.lyx.org/. You can also send email to the LyX users'
list (lyx-users at lists.lyx.org).

The LyX team.
https://www.lyx.org



signature.asc
Description: PGP signature


no PDF when using classicthesis-LyX-v4.2_biblatex_biber / ..._biblatex_bibtex8

2017-08-15 Thread Michael Berger

Dear Lyxers,

my Linguistic Thesis at first written in classicthesis-LyX-v4.1 converts 
to PDF in both versions of classicthesis-LyX-v4.2 but only after having 
removed all letters used to typeset African Languages as shown in Table 
7 of the Comprehensive LaTeX Symbol List by Scott Pakin.


While my Thesis successfully handles the languages Turkish, Indonesian, 
Serbo-Croatian and Tamil it fails compilation to PDF as long as any of 
the two African languages Asante-Twi and/or Limbum remains present.


This was tried with classicthesis-LyX-v4.2 and using two different 
systems namely openSUSE Leap 14.2 and Mageia 6 - both do show the same 
behavior.


The package fc is in place with all its elements (fclfont.sty, 
fcuse.sty, t4cmr.fd, t4cmss.fd, fclfont.sty_old, t4cmtt.fd, t4enc.def, 
t4fcr.fd and t4phonet.sty).


\usepackage[T4]{fontenc} is present in the preamble.

Using other document classes e. g. Koma-Script do compile without 
problems as long as \usepackage[T4]{fontenc} is part of the preamble.


Am I doing something wrong or could it be that classicthesis-LyX-v4.2 is 
not yet fit?


Any help or comment is highly appreciated.

Thanks and cheers!

Michael



Re: LyX native format stuck in the middle

2017-08-12 Thread Steve Litt
On Fri, 11 Aug 2017 09:23:06 +0100
José Abílio Matos <jama...@lyx.org> wrote:

> On Monday, 31 July 2017 18.30.31 WEST Steve Litt wrote:
> > I know what I'm asking for is monsterously difficult, and I know I
> > certainly don't have the technical chops to do it. But when it gets
> > done, LyX will be a brand new world,  finally living up to its
> > promise of write once, deploy everywhere.
> > 
> > Thanks,
> > 
> > SteveT  
> 
> The main technical problems of this enterprise are the math insets.
> Should they also be converted to an xml like format?

Hi José,

You ask two different questions:

1) Should math insets be well formed XML?

2) MUST math insets be well formed XML?

To #1, yes, it would be nice, and then math insets could be handled via
an XML parser. This is something we'd want to work toward at some
point in the future.

To #2, HECKNO! The perfect is the enemy of the good, so it would be
silly to hold up the rest of the XMLization just for math insets. As
long as you can encapsulate the math insets in an XML tag in a way that
they won't cause an XML parser to choke or abort, that's wonderful: The
XML parser can hand the application programmer the encasing XML node,
and the application programmer can parse apart the math insets
herhimself.

SteveT


Re: LyX native format stuck in the middle

2017-08-11 Thread Richard Heck
On 08/11/2017 04:23 AM, José Abílio Matos wrote:
>
> On Monday, 31 July 2017 18.30.31 WEST Steve Litt wrote:
>
> > I know what I'm asking for is monsterously difficult, and I know I
>
> > certainly don't have the technical chops to do it. But when it gets
>
> > done, LyX will be a brand new world, finally living up to its promise
>
> > of write once, deploy everywhere.
>
> >
>
> > Thanks,
>
> >
>
> > SteveT
>
>  
>
> The main technical problems of this enterprise are the math insets.
> Should they also be converted to an xml like format?
>

Personally, I don't think that would be necessary. There's no payoff for
doing that, so
far as I can see. Any more, say, than special encoding of the contents
of TeX Code.

Richard



Re: LyX native format stuck in the middle

2017-08-11 Thread José Abílio Matos
On Monday, 31 July 2017 18.30.31 WEST Steve Litt wrote:
> I know what I'm asking for is monsterously difficult, and I know I
> certainly don't have the technical chops to do it. But when it gets
> done, LyX will be a brand new world,  finally living up to its promise
> of write once, deploy everywhere.
> 
> Thanks,
> 
> SteveT

The main technical problems of this enterprise are the math insets. Should 
they also be converted to an xml like format?

Regards,
-- 
José Abílio


Re: lyx to lyx on the Mac command line

2017-08-09 Thread Dr Eberhard Lisse
Jose,

great, thanks.

Do I need to file a request for feature?


el

On 2017-08-09 16:30 , José Abílio Matos wrote:
> On Wednesday, 9 August 2017 09.56.31 WEST Dr Eberhard Lisse wrote:
[...]
>> lyx2lyx is a python script, so I am wondering whether there is not
>> perhaps a way of doing this inside the script, perhaps with something
>> like --upgrade-in-place (so it's not used by accident) and do this
>> inside the script?
> 
>  
> 
> That can be done. The option could be -i or --in-place for compatibility
> with sed, perl and company.
> 
>  
> 
> Honestly now it is not be best moment, since we are stabilizing the
> release for 2.3 to be out.
> 
>  
> 
> I have added this task for my 2.4 to do list. If we can test the result
> this could be possibly be back-ported to 2.3.
[...]




Re: lyx to lyx on the Mac command line

2017-08-09 Thread José Abílio Matos
On Wednesday, 9 August 2017 09.56.31 WEST Dr Eberhard Lisse wrote:
> Jose,
> 
> thanks, but still no error checking :-)-O
> 
> lyx2lyx is a python script, so I am wondering whether there is not
> perhaps a way of doing this inside the script, perhaps with something
> like --upgrade-in-place (so it's not used by accident) and do this
> inside the script?

That can be done. The option could be -i or --in-place for compatibility with 
sed, perl and 
company.

Honestly now it is not be best moment, since we are stabilizing the release for 
2.3 to be out.

I have added this task for my 2.4 to do list. If we can test the result this 
could be possibly be 
back-ported to 2.3.

> Don't know python myself, unfortunately :-)-O
> 
> el

Regards,
-- 
José Abílio


Re: lyx to latex

2017-08-09 Thread Dr Eberhard Lisse
Patrick,

fix cavity-e.bib, perhaps?

el

On 04/08/2017 19:10, Patrick Dupre wrote:
> Thank for the advises.
> 
> One question, 
> BibTeX error: Repeated entry---line 1055 of file cavity-e.bib
> 
> How can I force latex to ignore the warning?
> 
> It is possible when I generate a pdf file, but not when I 
> generate a rtf file.
> 
> Thank.
[...]




Re: lyx to lyx on the Mac command line

2017-08-09 Thread Dr Eberhard Lisse
Jose,

thanks, but still no error checking :-)-O

lyx2lyx is a python script, so I am wondering whether there is not
perhaps a way of doing this inside the script, perhaps with something
like --upgrade-in-place (so it's not used by accident) and do this
inside the script?

Don't know python myself, unfortunately :-)-O

el

On 08/08/2017 20:30, José Abílio Matos wrote:
[...]
> Using bash in one line we have (backup file.lyx -> file.old.lyx):
> 
>  
> 
> for lfile in $(find . -name '*lyx' -print); do
> ofile=${lfile%%.lyx}.old.lyx; lyx2lyx < $ofile -o $lfile; done
[...]



Re: lyx to lyx on the Mac command line

2017-08-09 Thread Dr Eberhard Lisse
Stephan,

thanks, but I keep it right there :-)-O

el

On 08/08/2017 22:36, Stephan Witt wrote:
[...]
> On Mac you may have multiple LyX applications on your system.
> The standard location is the folder /Applications and the name
> is LyX.app. There it is located in Contents/Resources/lyx2lyx/.
> 
> So, the standard is 
> /Applications/LyX.app/Contents/Resources/lyx2lyx/lyx2lyx
> 
> But the application bundle is completely relocatable. It is up
> to the owner of the Mac to know where the „current“ LyX.app is
> located.
> 
> Stephan
[...]





Re: lyx to lyx on the Mac command line

2017-08-08 Thread Stephan Witt
Am 08.08.2017 um 17:07 schrieb José Abílio Matos <jama...@lyx.org>:
> 
> On Tuesday, 8 August 2017 15.50.28 WEST Dr Eberhard Lisse wrote:
>> Hi,
>> 
>> is there a way of changing a lyx file from an older version to the
>> current one on the command line, like opening the file, making a
>> modification to trigger the saving allowed and saving it under the old
>> filename?
>> 
>>  find . -name '*lyx' -exec whatever {} \;
>> 
>> 
>> I wouldn't mind even a Apple Script :-)-O
>> 
>> greetings, el
> 
> I do not use macs, last time I did it was running linux as opposed to macos 
> 9. :-)
> 
> In any case the script responsible for converting the lyx files to a newer 
> format is called lyx2lyx.
> 
> If you get its path (e.g. here on linux it is /usr/share/lyx/lyx2lyx/lyx2lyx) 
> then you can call it directly. It has several options for command line call 
> and it even supports compressed lyx files directly.

On Mac you may have multiple LyX applications on your system.
The standard location is the folder /Applications and the name
is LyX.app. There it is located in Contents/Resources/lyx2lyx/.

So, the standard is 
/Applications/LyX.app/Contents/Resources/lyx2lyx/lyx2lyx

But the application bundle is completely relocatable. It is up
to the owner of the Mac to know where the „current“ LyX.app is
located.

Stephan

> 
> I can help further if you need.
> 
> Regards,
> -- 
> José Abílio



Re: lyx to lyx on the Mac command line

2017-08-08 Thread José Abílio Matos
On Tuesday, 8 August 2017 17.24.30 WEST Dr Eberhard Lisse wrote:
> José
> 
> thank you, but it lyx2lyx does not do what I need.
> 
>   lyx2lyx file.lyx -o file.lyx
> 
> clobbers file.lyx
> 
> Something like
> 
>   PID=$$
>   cp file.lyx file.$PID.lyx
>   lyx2lyx file.$PID.lyx file.lyx
> 
> doesn't fit on the command line so needs refinement as a bash script to
> take arguments and do further error checking...
> 
> not what would call 'one the command line'
> 
> 
> el

Using bash in one line we have (backup file.lyx -> file.old.lyx):

for lfile in $(find . -name '*lyx' -print); do ofile=${lfile%%.lyx}.old.lyx; 
lyx2lyx < $ofile -o $lfile; 
done

:-)
-- 
José Abílio


Re: lyx to lyx on the Mac command line

2017-08-08 Thread Dr Eberhard Lisse
José

thank you, but it lyx2lyx does not do what I need.

lyx2lyx file.lyx -o file.lyx

clobbers file.lyx

Something like

PID=$$
cp file.lyx file.$PID.lyx
lyx2lyx file.$PID.lyx file.lyx

doesn't fit on the command line so needs refinement as a bash script to
take arguments and do further error checking...

not what would call 'one the command line'


el

On 08/08/2017 16:07, José Abílio Matos wrote:
> On Tuesday, 8 August 2017 15.50.28 WEST Dr Eberhard Lisse wrote:
> 
>> Hi,
> 
>>
> 
>> is there a way of changing a lyx file from an older version to the
> 
>> current one on the command line, like opening the file, making a
> 
>> modification to trigger the saving allowed and saving it under the old
> 
>> filename?
> 
>>
> 
>> find . -name '*lyx' -exec whatever {} \;
> 
>>
> 
>>
> 
>> I wouldn't mind even a Apple Script :-)-O
> 
>>
> 
>> greetings, el
> 
>  
> 
> I do not use macs, last time I did it was running linux as opposed to
> macos 9. :-)
> 
>  
> 
> In any case the script responsible for converting the lyx files to a
> newer format is called lyx2lyx.
> 
>  
> 
> If you get its path (e.g. here on linux it is
> /usr/share/lyx/lyx2lyx/lyx2lyx) then you can call it directly. It has
> several options for command line call and it even supports compressed
> lyx files directly.
> 
>  
> 
> I can help further if you need.
> 
>  
> 
> Regards,
> 
> -- 
> 
> José Abílio
> 




Re: lyx to lyx on the Mac command line

2017-08-08 Thread José Abílio Matos
On Tuesday, 8 August 2017 15.50.28 WEST Dr Eberhard Lisse wrote:
> Hi,
> 
> is there a way of changing a lyx file from an older version to the
> current one on the command line, like opening the file, making a
> modification to trigger the saving allowed and saving it under the old
> filename?
> 
>   find . -name '*lyx' -exec whatever {} \;
> 
> 
> I wouldn't mind even a Apple Script :-)-O
> 
> greetings, el

I do not use macs, last time I did it was running linux as opposed to macos 9. 
:-)

In any case the script responsible for converting the lyx files to a newer 
format is called lyx2lyx.

If you get its path (e.g. here on linux it is /usr/share/lyx/lyx2lyx/lyx2lyx) 
then you can call it 
directly. It has several options for command line call and it even supports 
compressed lyx files 
directly.

I can help further if you need.

Regards,
-- 
José Abílio


lyx to lyx on the Mac command line

2017-08-08 Thread Dr Eberhard Lisse
Hi,

is there a way of changing a lyx file from an older version to the
current one on the command line, like opening the file, making a
modification to trigger the saving allowed and saving it under the old
filename?

find . -name '*lyx' -exec whatever {} \;


I wouldn't mind even a Apple Script :-)-O

greetings, el



Re: LyX native format stuck in the middle

2017-08-05 Thread Bob Alvarez
I would like to second Steve Litt's plea for a well-formed Lyx native 
format. I wrote a script to create a package to submit to a journal from 
my paper's Lyx file. The package includes a tex file with the 
bibliography and figure files renamed with standardized names such as 
fig1.eps. It makes copies of the re-named figure files in a subdirectory.


As it stands now, the code will break if I upgrade from my current 
version of Lyx. If there were a well formed native format, my script 
could be written once and used with new versions. I could distribute it 
to Lyx users who need to do this common task.


This is just one example of the Lyx add-ons that Steve envisions.

Bob Alvarez


Re: lyx to latex

2017-08-04 Thread Patrick Dupre
Thank for the advises.

One question, 
BibTeX error: Repeated entry---line 1055 of file cavity-e.bib

How can I force latex to ignore the warning?

It is possible when I generate a pdf file, but not when I 
generate a rtf file.

Thank.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


> Sent: Friday, August 04, 2017 at 8:12 AM
> From: "Guenter Milde" <mi...@users.sf.net>
> To: lyx-users@lists.lyx.org
> Subject: Re: lyx to latex
>
> On 2017-08-03, Patrick Dupre wrote:
> 
> > When I generate the pdf file from lyx, every thing is OK.
> > If I generate a tex file (plain latex), and then, if I compile it
> > with latex, I get:
> 
> > ! LaTeX Error: File `Pictures/17ubar_pub.eps.bb' not found.
> ...
> > l.1163 ...raphics[scale=0.51]{Pictures/17ubar_pub}
> 
> > The issue is with the pictures.
> 
> Yes. Different latex "flavours" accept different graphics formats:
> 
> `latex` accepts EPS but no PDF
> `pdflatex` accepts PDF, JPEG, PNG, ... but no EPS
> 
> What is the original format of the picture 17ubar_pub?
> 
> If it is PDF or PNG, then try to export to "LaTeX (pdflatex)" and compile
> with pdflatex.
> 
> 
> > What does lyx, that latex does not do?
> 
> * LyX runs latex and, if required auxiliary commands like bibtex,
>   makeindex, ... and again latex (up to three times).
> 
> * LyX converts pictures so it is accepted by the converter program
>   (latex, pdflatex, xelatex, or lualatex).
> 
> * LyX runs postprocessors like ps2pdf to get a PDF from the Postscript
>   document generated by "plain" latex.
> 
> * ...
> 
> In short, everything required to generate the output document.
> There are advanced LaTeX editors that do the same.
> 
> 
> 
> Günter
> 
>


Re: lyx to rtf

2017-08-04 Thread Paul A. Rubin

On 08/03/2017 06:04 PM, Patrick Dupre wrote:

Version 2.2.3
But the  my other concern is about the fact that I can easily get the 
pdf file

from lyx, but not from teh .tex file generated by lyx.
Does lyx use a special option of latex?

As Guenter pointed out in your other thread, it makes a difference how 
you generate the PDF within LyX. Depending on what LaTeX programs you 
have installed, you can get LyX to generate a PDF using pdflatex, 
dvipdfm, LuaTeX, XeTeX or ps2pdf (maybe other choices I don't know 
about). If viewing or exporting (as PDF) using pdflatex works from LyX, 
but you try exporting as LaTeX (plain) and then running latex against 
that file, something may go amiss. Even worse, if you export as LaTeX 
(pdflatex) and then run latex (or LuaTeX or whatever) against that file, 
a mismatch may occur.


As to special options, if you go to Tools > Preferences... > File 
Handling > Converters and pick one of the LaTeX to something converters 
(e.g., LaTeX(pdflatex) -> PDF (pdflatex)), you'll see the command being 
issued and any extra options (flags) that are set.


Paul



Re: lyx to latex

2017-08-04 Thread Guenter Milde
On 2017-08-03, Patrick Dupre wrote:

> When I generate the pdf file from lyx, every thing is OK.
> If I generate a tex file (plain latex), and then, if I compile it
> with latex, I get:

> ! LaTeX Error: File `Pictures/17ubar_pub.eps.bb' not found.
...
> l.1163 ...raphics[scale=0.51]{Pictures/17ubar_pub}

> The issue is with the pictures.

Yes. Different latex "flavours" accept different graphics formats:

`latex` accepts EPS but no PDF
`pdflatex` accepts PDF, JPEG, PNG, ... but no EPS

What is the original format of the picture 17ubar_pub?

If it is PDF or PNG, then try to export to "LaTeX (pdflatex)" and compile
with pdflatex.


> What does lyx, that latex does not do?

* LyX runs latex and, if required auxiliary commands like bibtex,
  makeindex, ... and again latex (up to three times).

* LyX converts pictures so it is accepted by the converter program
  (latex, pdflatex, xelatex, or lualatex).

* LyX runs postprocessors like ps2pdf to get a PDF from the Postscript
  document generated by "plain" latex.

* ...

In short, everything required to generate the output document.
There are advanced LaTeX editors that do the same.



Günter



Re: lyx to rtf

2017-08-03 Thread Patrick Dupre
Version 2.2.3
 

But the  my other concern is about the fact that I can easily get the pdf file

from lyx, but not from teh .tex file generated by lyx.

 

Does lyx use a special option of latex?

 

Thank.

 

===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===

 
 

Sent: Thursday, August 03, 2017 at 8:58 PM
From: "Paul A. Rubin" <parubi...@gmail.com>
To: "Patrick Dupre" <pdu...@gmx.com>, lyx <lyx-users@lists.lyx.org>
Subject: Re: lyx to rtf



On 08/03/2017 02:42 PM, Patrick Dupre wrote:


Hello,

When I trie to generate a rtf file from lyx, I do not get
any thing.
I can generate a tex file from lyx (plain latex), but then
I use latex2rtf and I get:
Formalism_NL_v5.tex:1774 Unknown command '\bm'
Formalism_NL_v5.tex:1783 Cannot open 'Formalism_NL_v5.bbl'
Formalism_NL_v5.tex:1783 Cannot open bibliography file.  Create Formalism_NL_v5.bbl using BibTeXSegmentation fault (core dumped)

Note that the pdf file generated by lyx is fine.




What version of latex2rtf do you have installed (and which OS)? I found a page on SourceForge indicating that support for the bm package was added in version 2.3.14. The page seems to be for the Win 64 version. Canonical's repository is only on version 2.3.8, so maybe support for bm hasn't reach the Linux version yet?

Paul
 






Re: lyx to rtf

2017-08-03 Thread Paul A. Rubin

On 08/03/2017 02:42 PM, Patrick Dupre wrote:

Hello,

When I trie to generate a rtf file from lyx, I do not get
any thing.
I can generate a tex file from lyx (plain latex), but then
I use latex2rtf and I get:
Formalism_NL_v5.tex:1774 Unknown command '\bm'
Formalism_NL_v5.tex:1783 Cannot open 'Formalism_NL_v5.bbl'
Formalism_NL_v5.tex:1783 Cannot open bibliography file.  Create 
Formalism_NL_v5.bbl using BibTeXSegmentation fault (core dumped)

Note that the pdf file generated by lyx is fine.


What version of latex2rtf do you have installed (and which OS)? I found 
a page on SourceForge 
<https://sourceforge.net/projects/latex2rtf/files/latex2rtf-win64/> 
indicating that support for the bm package was added in version 2.3.14. 
The page seems to be for the Win 64 version. Canonical's repository is 
only on version 2.3.8, so maybe support for bm hasn't reach the Linux 
version yet?


Paul



lyx to latex

2017-08-03 Thread Patrick Dupre
Hello,

When I generate the pdf file from lyx, every thing is OK.
If I generate a tex file (plain latex), and then, if I compile it
with latex, I get:

! LaTeX Error: File `Pictures/17ubar_pub.eps.bb' not found.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...  
  
l.1163 ...raphics[scale=0.51]{Pictures/17ubar_pub}


The issue is with the pictures.

What does lyx, that latex does not do?

Thank for your help.


===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


lyx to rtf

2017-08-03 Thread Patrick Dupre
Hello,

When I trie to generate a rtf file from lyx, I do not get
any thing.
I can generate a tex file from lyx (plain latex), but then
I use latex2rtf and I get:
Formalism_NL_v5.tex:1774 Unknown command '\bm'
Formalism_NL_v5.tex:1783 Cannot open 'Formalism_NL_v5.bbl'
Formalism_NL_v5.tex:1783 Cannot open bibliography file.  Create 
Formalism_NL_v5.bbl using BibTeXSegmentation fault (core dumped)

Note that the pdf file generated by lyx is fine.

Do you have some ideas?


Thank.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


Re: cannot produce PDF from classicthesis-Lyx-v4.2_biblatex-biber in Mageia6

2017-07-31 Thread Michael Berger

Günter,

thanks for your comment and tips, I'm not giving up yet.

I experienced exactly the same in openSUSE Leap, first neither the 
bibtex-version nor the biber-version worked until all in a sudden both 
did out of the blue.


Obviously there are few people using Miede's thesis. It produces 
beautiful documents - I use it for Linguistic papers.


If successful I will revert back to you.

Cheers and thanks again.

Michael


Am 31.07.2017 um 22:33 schrieb Guenter Milde:

On 2017-07-31, Michael Berger wrote:


Hi Günter,
let me recall: with 'Tools > Reconfigure' done I still see
in 'Documents > Settings > Bibliography > Bibliography Generation >
  > Processor'
   * Default
   * bibtex
   * bibtex8
wheras I should have
   * Default
   * biber
   * bibtex
   * bibtex8
Is 'biber' installed or not: see the screenshot

The screenshot and it does not help. I don't have any idea about Mageia6.

But if reconfigure does not make "biber" appear, biber is not installed---at
least not in at a place where LyX can find it.


I have Mageia 6, KDE

You may try in a terminal the commands `biber --help`
and `which biber` to see whether it works and where it is installed (if it
is).
   
Ultimatively, you should look for help with someone knowing Mageia and TeX

at Mageia.

Günter





Re: cannot produce PDF from classicthesis-Lyx-v4.2_biblatex-biber in Mageia6

2017-07-31 Thread Guenter Milde
On 2017-07-31, Michael Berger wrote:

> Hi Günter,

> let me recall: with 'Tools > Reconfigure' done I still see
> in 'Documents > Settings > Bibliography > Bibliography Generation >
>  > Processor'

>   * Default
>   * bibtex
>   * bibtex8

> wheras I should have

>   * Default
>   * biber
>   * bibtex
>   * bibtex8

> Is 'biber' installed or not: see the screenshot

The screenshot and it does not help. I don't have any idea about Mageia6.

But if reconfigure does not make "biber" appear, biber is not installed---at
least not in at a place where LyX can find it.

> I have Mageia 6, KDE

You may try in a terminal the commands `biber --help`
and `which biber` to see whether it works and where it is installed (if it
is).
  
Ultimatively, you should look for help with someone knowing Mageia and TeX
at Mageia.

Günter



LyX native format stuck in the middle

2017-07-31 Thread Steve Litt
Hi all,

I just commented, in another post, about how difficult it would make it
on people to change the LyX native format. And yet it *does* change.

Must have been about 10 years ago, the developers started transitioning
the LyX native format to XML, and began by making it much more XML
like, which made homegrown shellscript parsing more difficult. But
thanks to outside-XML use of whitespace in LyX's pidgeon XML, it's
still fairly script parsable.

For some reason, in the last several years, the change to XML bogged
down. LyX "XML" is still neither valid nor well-formed. Which means you
can't use an XML parser and hierarchy methods on it, the way you could
if it were real XML.

The example I brought up in the past was ePub export. Although Alex
Fernandez did a spectacular job with his eLyXer XHTML export, which
produced HTML with the same appearance as PDF exports of a file, his
export and that of the LyX team that built their own both produced
(X)HTML inappropriate for ePub.

ELyXer was 10K lines of code. If LyX were a single well formed and
valid XML hierarchy, I could probably write the right XHTML export in
1000 lines. A person wanting an XHTML for a different purpose could do
likewise. A whole cottage industry of LyX addons would spring up, now
that anyone with Python and one of the Python XML parsers could
manipulate the document to his/her heart's content.

I know what I'm asking for is monsterously difficult, and I know I
certainly don't have the technical chops to do it. But when it gets
done, LyX will be a brand new world,  finally living up to its promise
of write once, deploy everywhere.

Thanks,

SteveT

Steve Litt 
July 2017 featured book: Quit Joblessness: Start Your Own Business
http://www.troubleshooters.com/startbiz


Re: cannot produce PDF from classicthesis-Lyx-v4.2_biblatex-biber in Mageia6

2017-07-31 Thread Kornel Benko
Am Montag, 31. Juli 2017 um 17:43:46, schrieb Michael Berger 
> 
> Is 'biber' installed or not: see the screenshot
> 

Your screenshot does not show if biber is installed.
And, if it is, we cannot see if your PATH setting is correct.

Kornel

signature.asc
Description: This is a digitally signed message part.


Re: cannot produce PDF from classicthesis-Lyx-v4.2_biblatex-biber in Mageia6

2017-07-31 Thread Michael Berger

Hi Günter,

let me recall: with 'Tools > Reconfigure' done I still see
in 'Documents > Settings > Bibliography > Bibliography Generation >
 > Processor'

 * Default
 * bibtex
 * bibtex8

wheras I should have

 * Default
 * biber
 * bibtex
 * bibtex8

Is 'biber' installed or not: see the screenshot

I have Mageia 6, KDE

As a layman I have no idea if this info is helpfull. If it is I still 
don't know what to do.


Michael


Am 31.07.2017 um 10:07 schrieb Guenter Milde:

On 2017-07-31, Michael Berger wrote:

..
..

Making "biber" available in Mageia6 is not the task of LyX developers.
Maybe it is alredy available but not installed as LyX dependency, maybe it
is missing. Ask the distribution packagers or file a bug to Mageia6.


...

Günter

...

classicthesis-Lyx-v4.2_biblatex-biber did compile to PDF.
Cheers and thanks,
Michael
[-- Skipped Type: text/html --]





Re: cannot produce PDF of classicthesis-Lyx-v4.2_biblatex-biber in Mageia6

2017-07-31 Thread Michael Berger

Thanks Günter,

I did 'Reconfigure' several times. And for sure, the complete texlive 
(as offered under Mageia6) is installed. I will further check if biber 
is missing/installed on my system.


Michael


Am 31.07.2017 um 10:07 schrieb Guenter Milde:

On 2017-07-31, Michael Berger wrote:


I found that classicthesis-Lyx-v4.2_biblatex-bibtex8 compiles to PDF in
Mageia6  whereas classicthesis-Lyx-v4.2_biblatex-biber does not.
'Documents > Settings > Bibliography > Bibliography Generation >
Processor' is expected to show
   * Default
   * biber
   * bibtex
   * bibtex8
This is what I see in openSUSE Leap 42.2 and accordingly
classicthesis-Lyx-v4.2_biblatex-biber produces a perfect PDF.
Whereas in Mageia6 I can only see
   * Default
   * bibtex
   * bibtex8
so, 'biber' is (still) missing and therefor (in my opinion as an
ordinary user) no PDF output is generated.

The list shows what is (was) available on the system the last time you run
"(re)configure".


Are the developers aware of this and will "biber" be made available in
Mageia6 soon?

Making "biber" available in Mageia6 is not the task of LyX developers.
Maybe it is alredy available but not installed as LyX dependency, maybe it
is missing. Ask the distribution packagers or file a bug to Mageia6.

After installing "biber", you must make LyX aware of this: open LyX and run
Tools>Reconfigure.

Günter






I should mention that in the earlier days of openSUSE Leap 42.2 neither
classicthesis-Lyx-v4.2_biblatex-bibtex8 nor
classicthesis-Lyx-v4.2_biblatex-biber did compile to PDF.
Cheers and thanks,
Michael
[-- Skipped Type: text/html --]




Re: cannot produce PDF of classicthesis-Lyx-v4.2_biblatex-biber in Mageia6

2017-07-31 Thread Guenter Milde
On 2017-07-31, Michael Berger wrote:

> I found that classicthesis-Lyx-v4.2_biblatex-bibtex8 compiles to PDF in 
> Mageia6  whereas classicthesis-Lyx-v4.2_biblatex-biber does not.

> 'Documents > Settings > Bibliography > Bibliography Generation > 
> Processor' is expected to show

>   * Default
>   * biber
>   * bibtex
>   * bibtex8

> This is what I see in openSUSE Leap 42.2 and accordingly 
> classicthesis-Lyx-v4.2_biblatex-biber produces a perfect PDF.

> Whereas in Mageia6 I can only see

>   * Default
>   * bibtex
>   * bibtex8

> so, 'biber' is (still) missing and therefor (in my opinion as an 
> ordinary user) no PDF output is generated.

The list shows what is (was) available on the system the last time you run
"(re)configure".

> Are the developers aware of this and will "biber" be made available in 
> Mageia6 soon?

Making "biber" available in Mageia6 is not the task of LyX developers.
Maybe it is alredy available but not installed as LyX dependency, maybe it
is missing. Ask the distribution packagers or file a bug to Mageia6.

After installing "biber", you must make LyX aware of this: open LyX and run
Tools>Reconfigure.

Günter


> I should mention that in the earlier days of openSUSE Leap 42.2 neither 
> classicthesis-Lyx-v4.2_biblatex-bibtex8 nor 
> classicthesis-Lyx-v4.2_biblatex-biber did compile to PDF.

> Cheers and thanks,
> Michael

> [-- Skipped Type: text/html --]



cannot produce PDF of classicthesis-Lyx-v4.2_biblatex-biber in Mageia6

2017-07-31 Thread Michael Berger

Hello,

I found that classicthesis-Lyx-v4.2_biblatex-bibtex8 compiles to PDF in 
Mageia6  whereas classicthesis-Lyx-v4.2_biblatex-biber does not.


'Documents > Settings > Bibliography > Bibliography Generation > 
Processor' is expected to show


 * Default
 * biber
 * bibtex
 * bibtex8

This is what I see in openSUSE Leap 42.2 and accordingly 
classicthesis-Lyx-v4.2_biblatex-biber produces a perfect PDF.


Whereas in Mageia6 I can only see

 * Default
 * bibtex
 * bibtex8

so, 'biber' is (still) missing and therefor (in my opinion as an 
ordinary user) no PDF output is generated.


Are the developers aware of this and will "biber" be made available in 
Mageia6 soon?


I should mention that in the earlier days of openSUSE Leap 42.2 neither 
classicthesis-Lyx-v4.2_biblatex-bibtex8 nor 
classicthesis-Lyx-v4.2_biblatex-biber did compile to PDF.


Cheers and thanks,
Michael


Re: LyX truncates spacing in Local Layout and in Listings

2017-07-30 Thread Richard Heck
On 07/28/2017 05:21 AM, haim.ros...@gmail.com wrote:
>
> I noticed that whenever I enter contents to
>
> * Document -> Settings -> Local Layout
>
> * Document -> Settings -> Listings
>
> * Program Listings Inset -> Settings -> Advanced
>
> All the leading tabs are deleted by the validation. This disturbs the
> reading of this content. Is there any solution for this?
>

It works with spaces, but not with tabs. Same problem with the preamble,
actually.

JMarc, this seems to be because Lexer::getLongString trips leading tabs.
Is there an easy way around that?

> Another issue is that the tab stops are fairly far away from each
> other. I think that cutting them to two thirds is much better.
>

If we get tabs working, it will be easy to fix this. (Note to self:
tabstop width property = 40.)

Richard



Compilación automática en Lyx Windows con Latexmk

2017-07-30 Thread Johnny Flores
buenas tardes amigos.


el presente es para solicitarles ayuda en lo respectivo a la instalación y
uso del paquete latexmk (o bien algún otro método existente) para lograr
que mi documento se compile automáticamente sin la necesidad de estarlo
haciendo yo. Yo trabajo en Windows 10, Lyx 2.2.2, Miktex 2.9.6100,

Agradezco cualquier ayuda y/o sugerencia para solucionar mi propósito.


Re: classicthesis-Lyx-v4.2_biblatex_biber

2017-07-30 Thread Michael Berger

Hi Jürgen, hi Philip,

in openSUSE Leap 42.2 I've tried countless times to produce PDF outputs 
with both, classicthesis-Lyx-v4.2_biblatex-biber and 
classicthesis-Lyx-v4.2_biblatex-bibtex8  but always ended up in endless 
loops.


After two weeks I tried openSUSE Leap 42.2 once more last night (out of 
desperation and frustration) and to my surprise both, biblatex-biber and 
biblatex-bibtex8, generated perfect PDF outputs - and very quickly.


In Documents > Settings > Bibliography > Bibliography Generation > 
Processor it offers


 * Default
 * biber !
 * bibtex
 * bibtex8

while in Mageia6 'biber' is still missing.
So, looks like one must wait till "biber" is made available in Mageia6 
and working.


Thanks a lot for your continuous support, and cheers!

Michael


Am 29.07.2017 um 18:06 schrieb Michael Berger:


Jürgen,

I did as you told me

- I installed all the groups of texlive packages Mageia is offering 
but I don't know for certain whether or not "biber" is installed; I 
find no way to look for a single package called texlive-biber or 
texlive-biblatex


- I did reconfigure several times

- I cannot set the Bibliography Processor to "biber" in Documents 
Settings because it is not a choice - all I see is: Default, bibtex, 
bibtex8. And in Tools > Preferences > Output > LaTeX > Processor I see 
only Custom, bibtex, bibtex8.


I hope I am not too stupid and sorry for bothering you!

Michael

Am 29.07.2017 um 13:51 schrieb Jürgen Spitzmüller:
Am 29.07.2017 10:42 vorm. schrieb "Michael Berger" <id...@online.de 
<mailto:id...@online.de>>:


BibTeX error: I found no \bibstyle command-while reading file
ClassicThesis.aux

If I force the PDf output everything looks fine except that there
is no bibliography shown

LogType LaTeX shows some warnings but no errors
LogType BibTex shows some warnings but no errors


Obviously, you need to install biber, then reconfigure LyX and 
repeate the procedure I described.



I have Mageia6, KDE


Look for a package called texlive-biber or texlive-biblatex.

    Document Settings Module: Linguistics

Funny enough, classicthesis-LyX-v4.2_biblatex_bibtex8 outputs a
perfect PDF, even if I completely remove/replace the LaTeX Preamble.


That's not funny, it is expected, if bibtex8 is installed.

Jürgen


Thanks and Best,
Michael








  1   2   3   4   5   6   7   8   9   10   >