Re: Small poll - download speed of LyX installers

$ time wget 'ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.3/lyx-2.3.0rc2/LyX-2.3.0rc2+qt5-x86_64-cocoa.dmg' Am 16.02.2018 um 21:32 schrieb Pavel Sanda: Pavel Sanda wrote: Ok, updating US(CA); 1.88MB/s; academic network;M: UCSD(89.4MB/s), PL(6.83M/s), SA(8.85M/s), GR (6.36M/s) US(OR);

Re: Text output encodings

On 02/19/2018 04:43 PM, Daniel Kian Mc Kiernan wrote: On 02/19/2018 10:44 AM, F M Salter wrote: To explain in more detail.    LyX uses utf-8.   utf-8 is standard on most operating systems. RTF is obsolescent and is not a text file. If I insert utf-8 italic characters into a

Re: Text output encodings

On 02/19/2018 04:43 PM, Daniel Kian Mc Kiernan wrote: On 02/19/2018 10:44 AM, F M Salter wrote: To explain in more detail.    LyX uses utf-8.   utf-8 is standard on most operating systems. RTF is obsolescent and is not a text file. If I insert utf-8 italic characters into a

Re: LyX version 2.3.0rc2 available

On 1/30/18, Scott Kostyshak wrote: > Public release of LyX version 2.3.0rc2 > > Ubuntu packages are now available on the PPA: https://launchpad.net/~lyx-devel/+archive/ubuntu/daily Regards, Liviu > We are proud to announce the second

Re: Cannot determine size of graphic

On Mon, Feb 19, 2018 at 07:13:29PM +, a...@andreashegenbart.de wrote: > And now I tested it myself again and it works; my fault, sorry, I put the > file in an different folder and then it lost the reference to the graphics. > The notices lead me to the wrong error tracking. > Thanks a lot

Re: Text output encodings

On 02/19/2018 10:44 AM, F M Salter wrote:     To explain in more detail.    LyX uses utf-8.   utf-8 is standard on most operating systems.     RTF is obsolescent and is not a text file.     If I insert utf-8 italic characters into a LyX file, the plain text output contains italic

Re: older lyx file (around 2009) gives error in lyx2.3.0beta1

On 02/19/2018 10:40 AM, Jürgen Spitzmüller wrote: > Am Montag, den 19.02.2018, 13:01 +0100 schrieb Kornel Benko: >> OK, got it down to this: > Excellent. Here is my analysis. > > Since this is a very old document, it has "\layout Standard" in insets. > Now as of format 315 (for LyX 1.6), we

AW: Cannot determine size of graphic

-Ursprüngliche Nachricht- Von: a...@andreashegenbart.de [mailto:a...@andreashegenbart.de] Gesendet: Montag, 19. Februar 2018 19:48 An: 'Wolfgang Engelmann' ; 'lyx-users@lists.lyx.org' Betreff: AW: Cannot determine size of graphic

Re: Cannot determine size of graphic

Am 19.02.2018 um 19:47 schrieb a...@andreashegenbart.de: -Ursprüngliche Nachricht- Von: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] Im Auftrag von Wolfgang Engelmann Gesendet: Montag, 19. Februar 2018 19:19 An: lyx-users@lists.lyx.org Betreff: Re: Cannot determine size of

AW: Cannot determine size of graphic

-Ursprüngliche Nachricht- Von: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] Im Auftrag von Wolfgang Engelmann Gesendet: Montag, 19. Februar 2018 19:19 An: lyx-users@lists.lyx.org Betreff: Re: Cannot determine size of graphic Am 19.02.2018 um 17:53 schrieb

Re: Text output encodings

On 19/02/18 07:55, F M Salter wrote: > Hi > >     When plain text is used as output, emphasised text loses emphasis. > >     Is there any way by which text output may be specified with utf-8 > encoding?   Emphasis could then be maintained. > > Regards > > Frank Salter > ... ...     To explain in

Re: Cannot determine size of graphic

Am 19.02.2018 um 17:53 schrieb a...@andreashegenbart.de: Dear Scott, thanks a lot und I hope the attachment is what you mean: .lyx-file reduced and .txt-file with an extract of the assumed problematic commands. Best, Andreas -Ursprüngliche Nachricht- Von: lyx-users@lists.lyx.org

AW: Cannot determine size of graphic

Dear Scott, thanks a lot und I hope the attachment is what you mean: .lyx-file reduced and .txt-file with an extract of the assumed problematic commands. Best, Andreas -Ursprüngliche Nachricht- Von: lyx-users@lists.lyx.org [mailto:lyx-users@lists.lyx.org] Im Auftrag von Scott

Re: older lyx file (around 2009) gives error in lyx2.3.0beta1

Am Montag, 19. Februar 2018 16:58:51 CET schrieb Jürgen Spitzmüller : > Am Montag, den 19.02.2018, 16:40 +0100 schrieb Jürgen Spitzmüller: > > I am not sure if there is an easy fix for this. The "real" fix would > > be > > to actually change Standard to PlainLayout in 315, but I

Re: older lyx file (around 2009) gives error in lyx2.3.0beta1

Am Montag, den 19.02.2018, 16:40 +0100 schrieb Jürgen Spitzmüller: > I am not sure if there is an easy fix for this. The "real" fix would > be > to actually change Standard to PlainLayout in 315, but I suppose > there > were reasons for not doing that. I am not sure if the check in >

Re: older lyx file (around 2009) gives error in lyx2.3.0beta1

Am Montag, den 19.02.2018, 13:01 +0100 schrieb Kornel Benko: > OK, got it down to this: Excellent. Here is my analysis. Since this is a very old document, it has "\layout Standard" in insets. Now as of format 315 (for LyX 1.6), we switched to "\begin_layout PlainLayout" and shortly afterwards

Re: older lyx file (around 2009) gives error in lyx2.3.0beta1

Am Montag, 19. Februar 2018 10:54:25 CET schrieb Jürgen Spitzmüller : > Am Montag, den 19.02.2018, 10:35 +0100 schrieb Wolfgang Engelmann: > > Kornel, Jürgen, I went back to an older lyx file (another book) and > > found that this can not be processed by lyx2.3.0.beta1. > > I could

Re: Text output encodings

On 02/19/2018 02:25 AM, F M Salter wrote: On 19/02/18 08:06, Daniel Kian Mc Kiernan wrote: The very definition of “plain text” precludes what you're hoping toget. The closest thing of which I know to what you want is RTF(rich-text format) Plain text is the export option offered by LyX.

Re: quantifiers in lyx

On 18/02/2018 22:12, Richard Heck wrote: On 02/18/2018 04:48 PM, Jean-Marc Lasgouttes wrote: Le 18/02/2018 à 13:37, mike a écrit : Dear list Is there a way to get quantifiers without ERT? Hello, What kind of quantifiers do you have in mind? Probably he means logical quantifiers, like ∀ and

Re: Text output encodings

F M Salter wrote: > On 19/02/18 08:06, Daniel Kian Mc Kiernan wrote: > > The very definition of ???plain text??? precludes what you're hoping > > to get. The closest thing of which I know to what you want is > > RTF (rich-text format) > > > Plain text is the export option offered by LyX. > There

Re: Text output encodings

On 19/02/18 08:06, Daniel Kian Mc Kiernan wrote: > The very definition of “plain text” precludes what you're hoping > to get. The closest thing of which I know to what you want is > RTF (rich-text format) > Plain text is the export option offered by LyX. There is no RTF option! Regards Frank

Re: older lyx file (around 2009) gives error in lyx2.3.0beta1

Am Montag, den 19.02.2018, 10:35 +0100 schrieb Wolfgang Engelmann: > Kornel, Jürgen, I went back to an older lyx file (another book) and > found that this can not be processed by lyx2.3.0.beta1. > I could send the old lyx file (1999) which was: > #This file was created by Thu Sep 30 18:13:25

Re: older lyx file (around 2009) gives error in lyx2.3.0beta1

Am Montag, 19. Februar 2018 10:35:17 CET schrieb Wolfgang Engelmann : > Am 19.02.2018 um 09:42 schrieb Jürgen Spitzmüller: > > Am Montag, den 19.02.2018, 09:28 +0100 schrieb Kornel Benko: > >> OK, created MWE. > > > > But this MWE already contains the latexpar

Re: older lyx file (around 2009) gives error in lyx2.3.0beta1

Am 19.02.2018 um 09:42 schrieb Jürgen Spitzmüller: Am Montag, den 19.02.2018, 09:28 +0100 schrieb Kornel Benko: OK, created MWE. But this MWE already contains the latexpar separator. And the crucial question is how this was added in the first place. Jürgen Kornel Kornel, Jürgen, I

Re: older lyx file (around 2009) gives error in lyx2.3.0beta1

Am Montag, den 19.02.2018, 09:28 +0100 schrieb Kornel Benko: > OK, created MWE. But this MWE already contains the latexpar separator. And the crucial question is how this was added in the first place. Jürgen > > Kornel signature.asc Description: This is a digitally signed message part

Re: older lyx file (around 2009) gives error in lyx2.3.0beta1

Am Montag, 19. Februar 2018 08:38:44 CET schrieb Wolfgang Engelmann : > Is this sufficient? OK, created MWE. Kornel test2.lyx Description: application/lyx

Re: older lyx file (around 2009) gives error in lyx2.3.0beta1

Am Montag, den 19.02.2018, 07:46 +0100 schrieb Wolfgang Engelmann: > The ORIGINAL (old) file: > > \begin_layout Standard > If you look at White Clover > \begin_inset Index idx > status collapsed > > \begin_layout Plain Layout > White Clover > \begin_inset Separator latexpar > \end_inset So the

Re: Text output encodings

The very definition of “plain text” precludes what you're hoping to get. The closest thing of which I know to what you want is RTF (rich-text format). On 02/18/2018 11:55 PM, F M Salter wrote: Hi     When plain text is used as output, emphasised text loses emphasis.     Is there any way