Re: LyX 2.2 slowness

[Stephan Witt]

Am 10.01.2017 um 00:24 schrieb Stephan Witt :
> 
> Am 08.01.2017 um 19:09 schrieb Jean-Marc Lasgouttes :
>> 
>> Le 08/01/2017 à 18:59, Stephan Witt a écrit :
>>> Ok, I don’t see this with current 2.2.x. AFAIK, you did the backport and 
>>> applied it there too.
>>> The patch seems to be innocent :)
>> 
>> A bisect would be appreciated :) Note that I have noticed problems with math 
>> previews not updating in master, I do not know whether this is related.
> 
> I think it’s related.
> 
> Bisect is not easy. Many commits are uncompilable because of automake 
> incompatibilities or changes in compiler switches or simply compiler errors.
> 
> Change b917c4e compiles and the icons in text are drawn immediately but 
> included graphics not. HEAD of master seems to handle the icons like included 
> graphics.
> 
> But the current branch 2.2.x has the same problem. So it’s a long standing 
> problem now. I’ll continue my research.

I tried my old disk images and guess what - the same problem is present at 
least in LyX 1.6.7 already and in all subsequent versions I’ve tested.

Stephan

Re: LyX 2.2 slowness

[Stephan Witt]

Am 08.01.2017 um 19:09 schrieb Jean-Marc Lasgouttes :
> 
> Le 08/01/2017 à 18:59, Stephan Witt a écrit :
>> Ok, I don’t see this with current 2.2.x. AFAIK, you did the backport and 
>> applied it there too.
>> The patch seems to be innocent :)
> 
> A bisect would be appreciated :) Note that I have noticed problems with math 
> previews not updating in master, I do not know whether this is related.

I think it’s related.

Bisect is not easy. Many commits are uncompilable because of automake 
incompatibilities or changes in compiler switches or simply compiler errors.

Change b917c4e compiles and the icons in text are drawn immediately but 
included graphics not. HEAD of master seems to handle the icons like included 
graphics.

But the current branch 2.2.x has the same problem. So it’s a long standing 
problem now. I’ll continue my research.

Stephan

PS. To illustrate to problem I attach a screen shot. This is after waiting a 
long time and switching between windows (LyX and Mail) many times. The 
converted image is ready and placed in the cache but not drawn (because of a 
missing redraw event?).

Re: doc/UserGuide systemF tests failing

[Günter Milde]

On  9.01.17, Scott Kostyshak wrote:
> On Mon, Jan 09, 2017 at 03:23:47PM +0100, Jürgen Spitzmüller wrote:
> > Am Montag, den 09.01.2017, 09:12 -0500 schrieb Scott Kostyshak:
> > > On Mon, Jan 09, 2017 at 10:41:41AM +0100, Jürgen Spitzmüller wrote:
> > > > Am Sonntag, den 08.01.2017, 09:22 -0500 schrieb Scott Kostyshak:

> > > > Please try the attached patch. The lyx option 
> > > > --ignore-error-message missing_glyphs
> > > > does what you need.
> > > 
> > > The patch looks good.
> > 
> > So shall I commit?

> Let's first ask Kornel and Günter. Do you think we should turn this
> option on by default for the tests?

No. The "missing glyphs" warning-turned-error helped to find a whole range
of LyX bugs and LaTeX problems. We would throw away more than what we gain.
Remember that missing glyphs means data loss.

If Kornel thinks this is sensible and there is a straightforward way to turn
this option on for selected tests, so be it.

> If we don't turn it on by default for the ctests, it might still make
> sense to commit the patch for other use cases.

I am against an additional option without a convincing use case.

**

Rather than ignoring the missing glyphs, I propose to solve the issue of
"font combination" for Unicode fonts.

For CJK quotes, there are several options:

xeCJK: (only XeTeX, no LuaTeX)

  \usepackage{xeCJK}
  \setCJKmainfont{BABEL Unicode}
  
swallows whitespace after closing quote. Try to override:

  % don't ignore spaces: 
  \let\xeCJK@ignorespaces\relax
  
does not help for space after closing quote


luatexja:   did not test

  %\usepackage{luatexja-fontspec}
  %\setmainjfont{BABEL Unicode}



ucharclasses (only XeTeX, no LuaTeX):

  \usepackage[CJK]{ucharclasses}
  \newfontfamily\cjkfont{BABEL Unicode}
  \newfontfamily\defaultfont{Latin Modern Roman}
  \setTransitionsForCJK{\cjkfont{}}{\defaultfont{}}


The attached file works fine here with ucharclasses under XeTeX.

We can either add "cheating" preamble code with
\@ifpackageloaded{fontspec}{
  ...
}{}

or, with an enhancement ticket for a "font combi GUI", we can invert

  export/doc/(|de/|es/|fr/)UserGuide_.*_systemF
  
in the 

Sublabel: lyxbugs
# LyX bugs with a Trac number.

section and add a copy without CJK quotes to the autotests/export/latex/
samples.


Günter


CJK-quotes.lyx
Description: application/lyx

Re: doc/UserGuide systemF tests failing

[Kornel Benko]

Am Montag, 9. Januar 2017 um 17:07:01, schrieb Kornel Benko 
> Am Montag, 9. Januar 2017 um 10:55:06, schrieb Scott Kostyshak 
> 
> > On Mon, Jan 09, 2017 at 04:50:55PM +0100, Kornel Benko wrote:
> >
> > > I'd prefer to make the behaviour be document specific. Ignoring errors in 
> > > tests
> > > does not feel right if used in general.
> >
> > Sounds good to me. Seems like you and Jürgen agree on this. Kornel,
> > would it be difficult to incorporate this into our ctest framework in a
> > document-specific way? Would we just use a special label? Do you mind
> > doing the work?
>
> I will look into this.
>

Something like attached should work. Contents of the new file 
"ignoreMissingGlyphTests" is
"export/doc/UserGuide_(dvi3|pdf4|pdf5)_systemF"

Kornel
diff --git a/development/autotests/ExportTests.cmake b/development/autotests/ExportTests.cmake
index 7184994..837eec5 100644
--- a/development/autotests/ExportTests.cmake
+++ b/development/autotests/ExportTests.cmake
@@ -186,7 +186,7 @@ macro(maketestname testname inverted listinverted listignored listunreliable lis
   endif()
 endmacro()

-macro(loadTestList filename resList depth)
+macro(loadTestList filename resList depth splitlangs)
   # Create list of strings from a file without comments
   # ENCODING parameter is a new feature in cmake 3.1
   initLangVars(${resList})
@@ -218,8 +218,12 @@ macro(loadTestList filename resList depth)
 list(REMOVE_DUPLICATES mylabels)
 set(sublabel ${_newl})
   else()
-string(REGEX REPLACE "(\\/|\\||\\(|\\))" "  " _vxx ${_newl})
-string(REGEX MATCHALL " ([a-z][a-z](_[A-Z][A-Z])?) " _vx ${_vxx})
+	if (splitlangs)
+	  string(REGEX REPLACE "(\\/|\\||\\(|\\))" "  " _vxx ${_newl})
+	  string(REGEX MATCHALL " ([a-z][a-z](_[A-Z][A-Z])?) " _vx ${_vxx})
+	else()
+	  set(_vx OFF)
+	endif()
 if(_vx)
   foreach(_v ${_vx})
 string(REGEX REPLACE " " "" _v ${_v})
@@ -276,10 +280,11 @@ assignLabelDepth(1 "unreliable" "inverted")
 assignLabelDepth(2 "suspended")
 assignLabelDepth(-1 "examples" "manuals" "mathmacros" "templates" "autotests")

-loadTestList(invertedTests invertedTests 7)
-loadTestList(ignoredTests ignoredTests 0)
-loadTestList(suspendedTests suspendedTests 6)
-loadTestList(unreliableTests unreliableTests 5)
+loadTestList(invertedTests invertedTests 7 ON)
+loadTestList(ignoredTests ignoredTests 0 ON)
+loadTestList(suspendedTests suspendedTests 6 ON)
+loadTestList(unreliableTests unreliableTests 5 ON)
+loadTestList(ignoreMissingGlyphTests ignoreMissingGlyphTests 8 OFF)

 foreach(libsubfolderx autotests/export lib/doc lib/examples lib/templates autotests/mathmacros)
   set(testlabel "export")
@@ -417,6 +422,13 @@ foreach(libsubfolderx autotests/export lib/doc lib/examples lib/templates autote
   set(mytestlabel ${testlabel})
   maketestname(TestName inverted invertedTests ignoredTests unreliableTests mytestlabel)
   if(TestName)
+	set(missingLabels )	# will be ignored
+	findexpr(mfound TestName ignoreMissingGlyphTests missingLabels)
+	if (mfound)
+	  set(_ignoreMissingGlyphsError ON)
+	else()
+	  set(_ignoreMissingGlyphsError OFF)
+	endif()
 add_test(NAME ${TestName}
   WORKING_DIRECTORY "${CMAKE_CURRENT_BINARY_DIR}/${LYX_HOME}"
   COMMAND ${CMAKE_COMMAND} -DLYX_ROOT=${LIBSUB_SRC_DIR}
@@ -429,6 +441,7 @@ foreach(libsubfolderx autotests/export lib/doc lib/examples lib/templates autote
   -Dfile=${f}
   -Dinverted=${inverted}
   -DTOP_SRC_DIR=${TOP_SRC_DIR}
+	  -DIgnoreMissingGlyphsError=${_ignoreMissingGlyphsError}
   -DPERL_EXECUTABLE=${PERL_EXECUTABLE}
   -DXMLLINT_EXECUTABLE=${XMLLINT_EXECUTABLE}
   -DENCODING=${_enc2}
diff --git a/development/autotests/check_load.cmake b/development/autotests/check_load.cmake
index 0a0d351..860f1ff 100644
--- a/development/autotests/check_load.cmake
+++ b/development/autotests/check_load.cmake
@@ -28,7 +28,7 @@ execute_process(
   ERROR_VARIABLE lyxerr)

 message(STATUS "Error code of lyx = ${_err}")
-
+message(STATUS "lyxerr=${lyxerr}")
 #
 # Ignore messages between "reconfiguring user directory" and "LyX: Done!"
 # (Reconfigure-messages are not symptom of an error)
diff --git a/development/autotests/export.cmake b/development/autotests/export.cmake
index 08fd86e..74cf9d6 100755
--- a/development/autotests/export.cmake
+++ b/development/autotests/export.cmake
@@ -24,6 +24,7 @@
 #   -Dfile=xxx \
 #   -Dinverted=[01] \
 #   -DTOP_SRC_DIR=${TOP_SRC_DIR} \
+#   -DIgnoreMissingGlyphsError=(ON/OFF) \
 #   -DPERL_EXECUTABLE=${PERL_EXECUTABLE} \
 #   -DXMLLINT_EXECUTABLE=${XMLLINT_EXECUTABLE} \
 #   -DENCODING=xxx \
@@ -143,6 +144,9 @@ else()
   else()
 set(LatexDebugParam)
   endif()
+  if(IgnoreMissingGlyphsError)
+list(APPEND LatexDebugParam --ignore-error-message missing_glyphs)
+  

Re: pasted non-acceptable symbol

[Jean-Marc Lasgouttes]

Le 05/12/2016 à 09:50, Jean-Marc Lasgouttes a écrit :

Le 10/11/2016 à 10:19, Jean-Marc Lasgouttes a écrit :

So shall I apply it?


Yes, please.


Done in master at 6dfbab31. Richard, this is candidate for branch too,
since it leads to crashes.


Ping :) Richard, is this OK for branch?


Ping Ping. This is my monthly ping for including this in stable.

Richard, if you do not answer, I warn you that I will do it again on Feb 
9 ;)


JMarc

Re: doc/UserGuide systemF tests failing

[Kornel Benko]

Am Montag, 9. Januar 2017 um 10:55:06, schrieb Scott Kostyshak 

> On Mon, Jan 09, 2017 at 04:50:55PM +0100, Kornel Benko wrote:
> 
> > I'd prefer to make the behaviour be document specific. Ignoring errors in 
> > tests
> > does not feel right if used in general.
> 
> Sounds good to me. Seems like you and Jürgen agree on this. Kornel,
> would it be difficult to incorporate this into our ctest framework in a
> document-specific way? Would we just use a special label? Do you mind
> doing the work?

I will look into this.

> Scott

Kornel

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

Re: doc/UserGuide systemF tests failing

[Scott Kostyshak]

On Mon, Jan 09, 2017 at 04:50:55PM +0100, Kornel Benko wrote:

> I'd prefer to make the behaviour be document specific. Ignoring errors in 
> tests
> does not feel right if used in general.

Sounds good to me. Seems like you and Jürgen agree on this. Kornel,
would it be difficult to incorporate this into our ctest framework in a
document-specific way? Would we just use a special label? Do you mind
doing the work?

Scott


signature.asc
Description: PGP signature

Re: doc/UserGuide systemF tests failing

[Kornel Benko]

Am Montag, 9. Januar 2017 um 10:15:56, schrieb Scott Kostyshak 

> On Mon, Jan 09, 2017 at 03:23:47PM +0100, Jürgen Spitzmüller wrote:
> > Am Montag, den 09.01.2017, 09:12 -0500 schrieb Scott Kostyshak:
> > > On Mon, Jan 09, 2017 at 10:41:41AM +0100, Jürgen Spitzmüller wrote:
> > > > Am Sonntag, den 08.01.2017, 09:22 -0500 schrieb Scott Kostyshak:
> > > > > > Ignoring the
> > > > > > missing glyphs warning strikes me a better alternative.
> > > > > 
> > > > > Perhaps. Does anyone volunteer to do this work?
> > > > 
> > > > Please try the attached patch. The lyx option 
> > > > --ignore-error-message missing_glyphs
> > > > does what you need.
> > > 
> > > The patch looks good.
> > 
> > So shall I commit?
> 
> Let's first ask Kornel and Günter. Do you think we should turn this
> option on by default for the tests? I don't know too much about this,
> but it makes sense to me because it will help make the tests less
> sensitive to font choice.

I'd prefer to make the behaviour be document specific. Ignoring errors in tests
does not feel right if used in general.

> If we don't turn it on by default for the ctests, it might still make
> sense to commit the patch for other use cases.

Here I am not so sure. The user already has the possibility to use 'Show Output 
Anyway'.

> Scott

Kornel

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

Re: doc/UserGuide systemF tests failing

[Jürgen Spitzmüller]

Am Montag, den 09.01.2017, 10:15 -0500 schrieb Scott Kostyshak:
> Let's first ask Kornel and Günter. Do you think we should turn this
> option on by default for the tests? I don't know too much about this,
> but it makes sense to me because it will help make the tests less
> sensitive to font choice.

Actually, I thought you would just turn it on for he UserGuide.

Jürgen

> 
> If we don't turn it on by default for the ctests, it might still make
> sense to commit the patch for other use cases.
> 
> Scott

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

Re: doc/UserGuide systemF tests failing

[Scott Kostyshak]

On Mon, Jan 09, 2017 at 03:23:47PM +0100, Jürgen Spitzmüller wrote:
> Am Montag, den 09.01.2017, 09:12 -0500 schrieb Scott Kostyshak:
> > On Mon, Jan 09, 2017 at 10:41:41AM +0100, Jürgen Spitzmüller wrote:
> > > Am Sonntag, den 08.01.2017, 09:22 -0500 schrieb Scott Kostyshak:
> > > > > Ignoring the
> > > > > missing glyphs warning strikes me a better alternative.
> > > > 
> > > > Perhaps. Does anyone volunteer to do this work?
> > > 
> > > Please try the attached patch. The lyx option 
> > > --ignore-error-message missing_glyphs
> > > does what you need.
> > 
> > The patch looks good.
> 
> So shall I commit?

Let's first ask Kornel and Günter. Do you think we should turn this
option on by default for the tests? I don't know too much about this,
but it makes sense to me because it will help make the tests less
sensitive to font choice.

If we don't turn it on by default for the ctests, it might still make
sense to commit the patch for other use cases.

Scott


signature.asc
Description: PGP signature

Re: Biblatex

[Richard Heck]

On 01/09/2017 04:40 AM, Jean-Marc Lasgouttes wrote:
> Le 09/01/2017 à 10:22, Jürgen Spitzmüller a écrit :
>> Having said that, I agree that LyX 2.3 could be released rather soon
>> after this has settled. We also already have some other nice new
>> features and substantial code refactoring (esp. drawing improvements).
>>
>> But it's not my call.
>
> I would second that, although we still have some work to do to
> stabilize the math drawing stuff.
>
> What I'd like to see, actually is a tentative release date. It is
> better than deciding on a hunch that feature freeze is right now.

I was thinking the same thing. I have one new feature that I'm working
on (further extending support for refstyle). But we have enough to do a
new major version.

Maybe we should see if anyone wants to be release manager and find out
what their schedule is.

Richard

Re: Biblatex

[Richard Heck]

On 01/08/2017 10:03 PM, Andrew Parsloe wrote:
> On 9/01/2017 7:50 a.m., Richard Heck wrote:
>>
>> Thanks so much for doing this. I've not yet moved to biblatex myself,
>> but this will encourage me to give it a try.
>>
>> Richard
>>
>>
>> On 01/08/2017 04:14 AM, Jürgen Spitzmüller wrote:
>>> Biblatex support is ready over at the features/biblatex2 branch.
>>>
>>> Of course we do not support the whole range of biblatex's feature set
>>> natively, but we already support all that natbib/jurabib does and
>>> substially more (features I'd like to add eventually include
>>> refsection/refsegements and particularly so-called "qualified citation
>>> lists").
>>>
>>> Essentially, the current implementation introduces:
>>>
>>> * Scanning and detection of the relevant files (package, styles)
>>>
>>> * A GUI to
>>>- select biblatex engine(s) next to basic, jurabib, natbib,
>>>- set bibliography and citation style files (with default proposals)
>>>- set further biblatex package options (this field will later be
>>> also
>>>  used by natbib and jurabib, an old request)
>>>- set options to the \printbibliography command
>>>
>>> * Automatic setting of backend option if bibtex[8] is selected
>>>
>>> * Style files that define biblatex's citation styles for the GUI and
>>> xhtml output
>>>
>>> * Make the BibTeX inset biblatex-aware (i.e., output \printbibliography
>>> and optional argument in the body and pass the bib files to
>>> \addbibresource macros in the preamble)
>>>
>>> Along the way, I had to polish and extend our biblio-related code at
>>> many places in order to enable things. Consequently, nothing in the
>>> code is longer hardcoded to bibtex, natbib or jurabib, but generalized
>>> in a way that it can be adjusted in the respective style files to the
>>> needs of the respective engine. I was able to replace some ad-hoc
>>> additions for the sake of specific engines with general, transparent
>>> and extensible code (while keeping the functionality). This also
>>> allowed me to fix some bugs and implement some long-standing desiderata
>>> (such as the display of uppercased names and full author lists in the
>>> GUI), en passant.
>>>
>>> I have put most energy into a design that enables portability between
>>> the diverse citation engines as much as possible, so it should be very
>>> easy to switch an existing document from, say, natbib to biblatex and
>>> (to a limited degree, since the feature set is larger) back. This is
>>> why the citation styles use a common set of cmd names rather than just
>>> the corresponding latex name.
>>>
>>> If you want to try and play with it, check out the features/biblatex2
>>> branch (not the old features/biblatex branch).
>>>
>>> I propose to merge this to master rather soon, to give it more testing
>>> and iron out potential bugs.
>>>
>>> Jürgen
>>
> Given the age of this enhancement request and the number of people
> over the years who have enquired about biblatex support in LyX, I
> wonder if any thought has been given to its release? It feels more
> like the centrepiece of an accelerated 2.3 release than "tucked away"
> in a 2.2.x release.

This involved a format change, so it can't go into 2.2.x.

Richard

Re: doc/UserGuide systemF tests failing

[Jürgen Spitzmüller]

Am Montag, den 09.01.2017, 09:12 -0500 schrieb Scott Kostyshak:
> On Mon, Jan 09, 2017 at 10:41:41AM +0100, Jürgen Spitzmüller wrote:
> > Am Sonntag, den 08.01.2017, 09:22 -0500 schrieb Scott Kostyshak:
> > > > Ignoring the
> > > > missing glyphs warning strikes me a better alternative.
> > > 
> > > Perhaps. Does anyone volunteer to do this work?
> > 
> > Please try the attached patch. The lyx option 
> > --ignore-error-message missing_glyphs
> > does what you need.
> 
> The patch looks good.

So shall I commit?

Jürgen

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

tex2lyx tests are failing on master

[Scott Kostyshak]

tex2lyx tests are failing on recent master.

Scott


signature.asc
Description: PGP signature

Re: doc/UserGuide systemF tests failing

[Scott Kostyshak]

On Mon, Jan 09, 2017 at 10:41:41AM +0100, Jürgen Spitzmüller wrote:
> Am Sonntag, den 08.01.2017, 09:22 -0500 schrieb Scott Kostyshak:
> > > Ignoring the
> > > missing glyphs warning strikes me a better alternative.
> > 
> > Perhaps. Does anyone volunteer to do this work?
> 
> Please try the attached patch. The lyx option 
> --ignore-error-message missing_glyphs
> does what you need.

The patch looks good.

> --ignore-error-message can be expanded to other messages later, if this
>  is desired.

OK good.

> And the option is sufficiently painful to write to prevent people using
> it without thinking about what they are doing ;-)

Agreed.

Thanks,

Scott


signature.asc
Description: PGP signature

Re: doc/UserGuide systemF tests failing

[Jürgen Spitzmüller]

Am Sonntag, den 08.01.2017, 09:22 -0500 schrieb Scott Kostyshak:
> > Ignoring the
> > missing glyphs warning strikes me a better alternative.
> 
> Perhaps. Does anyone volunteer to do this work?

Please try the attached patch. The lyx option 
--ignore-error-message missing_glyphs
does what you need.

--ignore-error-message can be expanded to other messages later, if this
 is desired.

And the option is sufficiently painful to write to prevent people using
it without thinking about what they are doing ;-)

Jürgendiff --git a/src/LaTeX.cpp b/src/LaTeX.cpp
index c4f987014d..9faf20102e 100644
--- a/src/LaTeX.cpp
+++ b/src/LaTeX.cpp
@@ -18,6 +18,7 @@
 #include "BufferList.h"
 #include "LaTeX.h"
 #include "LyXRC.h"
+#include "LyX.h"
 #include "DepTable.h"
 
 #include "support/debug.h"
@@ -899,8 +900,9 @@ int LaTeX::scanLogFile(TeXErrors & terr)
 		 from_local8bit("pdfTeX Error"),
 		 from_local8bit(token),
 		 child_name);
-			} else if (prefixIs(token, "Missing character: There is no ")
-	   && !contains(token, "nullfont")) {
+			} else if (!ignore_missing_glyphs
+   && prefixIs(token, "Missing character: There is no ")
+   && !contains(token, "nullfont")) {
 // Warning about missing glyph in selected font
 // may be dataloss (bug 9610)
 // but can be ignored for 'nullfont' (bug 10394).
diff --git a/src/LyX.cpp b/src/LyX.cpp
index b10b60b122..e10fbebcb1 100644
--- a/src/LyX.cpp
+++ b/src/LyX.cpp
@@ -98,6 +98,13 @@ bool use_gui = true;
 bool verbose = false;
 
 
+// Do not treat the "missing glyphs" warning of fontspec as an error message.
+// The default is false and can be changed with the option
+// --ignore-error-message missing_glyphs
+// This is used in automated testing.
+bool ignore_missing_glyphs = false;
+
+
 // We default to open documents in an already running instance, provided that
 // the lyxpipe has been setup. This can be overridden either on the command
 // line or through preference settings.
@@ -1309,6 +1316,16 @@ int parse_verbose(string const &, string const &, string &)
 }
 
 
+int parse_ignore_error_message(string const & arg1, string const &, string &)
+{
+	if (arg1 == "missing_glyphs") {
+		ignore_missing_glyphs = true;
+		return 1;
+	}
+	return 0;
+}
+
+
 int parse_force(string const & arg, string const &, string &)
 {
 	if (arg == "all") {
@@ -1358,6 +1375,7 @@ void LyX::easyParse(int & argc, char * argv[])
 	cmdmap["--remote"] = parse_remote;
 	cmdmap["-v"] = parse_verbose;
 	cmdmap["--verbose"] = parse_verbose;
+	cmdmap["--ignore-error-message"] = parse_ignore_error_message;
 
 	for (int i = 1; i < argc; ++i) {
 		map::const_iterator it
diff --git a/src/LyX.h b/src/LyX.h
index 4b9c201e25..11c67a3118 100644
--- a/src/LyX.h
+++ b/src/LyX.h
@@ -52,6 +52,7 @@ enum OverwriteFiles {
 
 extern bool use_gui;
 extern bool verbose;
+extern bool ignore_missing_glyphs;
 extern RunMode run_mode;
 extern OverwriteFiles force_overwrite;
 


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

Re: Biblatex

[Jean-Marc Lasgouttes]

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

Having said that, I agree that LyX 2.3 could be released rather soon
after this has settled. We also already have some other nice new
features and substantial code refactoring (esp. drawing improvements).

But it's not my call.


I would second that, although we still have some work to do to stabilize 
the math drawing stuff.


What I'd like to see, actually is a tentative release date. It is better 
than deciding on a hunch that feature freeze is right now.


JMarc

Re: Biblatex

[Jürgen Spitzmüller]

Am Montag, den 09.01.2017, 16:03 +1300 schrieb Andrew Parsloe:
> Given the age of this enhancement request and the number of people
> over 
> the years who have enquired about biblatex support in LyX, I wonder
> if 
> any thought has been given to its release? It feels more like the 
> centrepiece of an accelerated 2.3 release than "tucked away" in a
> 2.2.x 
> release.

The implementation certainly needs some testing (it required quite some
code changes), and I'd like to add one or two missing things on top of
it.

Having said that, I agree that LyX 2.3 could be released rather soon
after this has settled. We also already have some other nice new
features and substantial code refactoring (esp. drawing improvements).

But it's not my call.

Jürgen



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