Re: fr/beamer.lyx + system fonts + Xe/Lua fails

[Enrico Forestieri]

On Mon, Sep 19, 2016 at 10:49:15PM -0400, Scott Kostyshak wrote:

> I wonder if this is the language nesting issue?
> 
> Attached is a more minimal example that gives the same error, which is
> the following:
> 
> -
> Runaway argument?
> \let \AtEndDocument \@firstofone \@enddocumenthook \@checkend {docume\ETC.
> ! File ended while scanning use of \beamer@collect@@body.
>  
> \par 
> <*> beamer.tex
>   
> I suspect you have forgotten a `}', causing me
> to read past where you wanted me to stop.
> I'll try to recover; but if the error is serious,
> you'd better type `E' or `X' now and fix your file.
> 
> ! Emergency stop.
> <*> beamer.tex
> -
> 
> Any ideas?

LyX was making a real mess when switching languages with polyglossia.
I attach here a couple of simple test cases demonstrating it.
Should be fixed at 3bc08a76.

-- 
Enrico


langnest-1.lyx
Description: application/lyx


langnest-9.lyx
Description: application/lyx

Re: [RFC][PATCH] Set window title according to platform UI

[Enrico Forestieri]

On Fri, Sep 23, 2016 at 11:26:31AM +0200, Jean-Marc Lasgouttes wrote:
> 
> Actually, most of the used of getPixmap are like
>   QIcon(getPixmap(...)).pixmap(somesize);
> 
> It looks like a strange code path to me. What does getPixmap return in the
> case of a svg? Some rasterized version of the svg? Then how does it help to
> go through a QIcon and then back to QPixmap?

I am not really an expert, but QIcon takes care of loading, scaling and
post-processing of the image. Moreover, QIcon may contain multiple images
with different sizes (most probably some common used sizes). So, when you
request a certain size, it probably gives you a scaled version of the nearest
precomputed size. This may explain the better quality.

> It would look better to me to have a getIcon function which returns a QIcon,
> so that we can directly render the svg at the right size. Or did I
> misunderstand how this works?

Seemingly, QIcon already provides multiple images with different sizes, such
that the best fit is chosen depending on the size to be used. But, I repeat,
I am not really an expert and mine are speculations rather than facts.

-- 
Enrico

Re: 2 compilation errors in TexRow.cpp

[Uwe Stöhr]

Am 24.09.2016 um 00:52 schrieb Guillaume Munch:


Should be fixed now.


Many thanks Guillaume. It works now.

regards Uwe

Re: 2 compilation errors in TexRow.cpp

[Guillaume Munch]

Le 24/09/2016 à 00:40, Uwe Stöhr a écrit :

with today's git master i get this:

  TexRow.cpp
D:\LyXGit\Master\src\TexRow.cpp(68): error C3861: 'back_inserter':
identifier not found [D:\LyXGit\Master\compile-2015\src\LyX.vcxproj]
D:\LyXGit\Master\src\TexRow.cpp(185): error C3861: 'back_inserter':
identifier not found [D:\LyXGit\Master\compile-2015\src\LyX.vcxproj]

regards Uwe



Should be fixed now.

Re: 2 compilation errors in TexRow.cpp

[Guillaume Munch]

Le 24/09/2016 à 00:40, Uwe Stöhr a écrit :

with today's git master i get this:

  TexRow.cpp
D:\LyXGit\Master\src\TexRow.cpp(68): error C3861: 'back_inserter':
identifier not found [D:\LyXGit\Master\compile-2015\src\LyX.vcxproj]
D:\LyXGit\Master\src\TexRow.cpp(185): error C3861: 'back_inserter':
identifier not found [D:\LyXGit\Master\compile-2015\src\LyX.vcxproj]

regards Uwe




Ah which compiler version? MSVC 2015?

2 compilation errors in TexRow.cpp

[Uwe Stöhr]

with today's git master i get this:

  TexRow.cpp
D:\LyXGit\Master\src\TexRow.cpp(68): error C3861: 'back_inserter': 
identifier not found [D:\LyXGit\Master\compile-2015\src\LyX.vcxproj]
D:\LyXGit\Master\src\TexRow.cpp(185): error C3861: 'back_inserter': 
identifier not found [D:\LyXGit\Master\compile-2015\src\LyX.vcxproj]


regards Uwe

Re: Mark line(s) on Reverse search instead of close position

[Guillaume Munch]

Le 29/08/2016 à 12:33, racoon a écrit :

On Reverse search LyX puts the cursor at a position only *close* to but
not exactly at the position chosen in the pdf document. It is a bit
tricky for me to always find the former position in my document. Since
it is anyway not the exact position maybe it is possible to select the
whole line(s) rather than a close position?



You can try it in master after 5fbbf0f2.

Re: [LyX/master] ctests: update labeling patterns.

[Guenter Milde]

On 2016-09-23, Kornel Benko wrote:
> Am Freitag, 23. September 2016 um 07:29:14, schrieb Guenter Milde 
> 
>> On 2016-09-22, Kornel Benko wrote:
>> > Am Donnerstag, 22. September 2016 um 21:25:07, schrieb Guenter Milde 
>> > 
>> >> On 2016-09-22, Kornel Benko wrote:

>> >> > Now, export/doc/es/Additional_pdf4_texF in under label lyxbugs and
>> >> > under label ert in invertedTests. At the same time in
>> >> > unreliableTests (mask = export/doc/es/.*_(pdf[45]|dvi3)_texF) under
>> >> > label wrong_output.

...

>> > You could use for instance
>> >Sublabel: wrong_output ert lyxbugs

>> This would mean, 3 regexp patterns instead of 2 simpler ones
>> to single out the test case that currently matches for both:

> Yes, you have your points ...

> In ideal case however, the (inverted|suspended|unreliable)Tests should
> be empty.

Don't strife for this "ideal"
Rather, the (inverted|suspended|unreliable)Tests is comparable to track
issues: no open track issues would usually signalize the project is
dead...

As long as we are working on LyX, both track and *Tests-files are a valuable
buffer that allows us to prioritise which problems to solve first.


>> Currently, we have two "orthogonal" clauses:

>> 1. for a problem common to all "Additional.lyx" exports in
>>invertedTests:

>>  #9871 LyX sends invalid Unicode to iconv when converting to ASCII
>>  # most probably due to BabelPreamble code (language specific headings 
>> for
>>  # theorems, problems , ... are written in the language's default 
>> encoding 
>>  # if they contain non-ASCII characters)
>>  export/doc/(es|fr)/Additional_pdf4_texF

>> 2. for a problem common to all Spanish documents with 8-bit fonts and
>>Xe/LuaTeX:

>>  # Babel-Spanish uses Babel's "strings" feature to define
>>  # separate auto-strings using UTF-8 literals.
>>  # Babel uses the "unicode" strings if it detects XeTeX or LuaTeX.
>>  # This is wrong for Xe/Lua with 8-bit TeX-fonts.
>>  # set inputenc to utf8?
>>  # (Changing the default in lib/languages requires more tests for utf8 
>> first.)
>>  export/examples/es/linguistics_pdf4_texF
>>  export/doc/es/.*_(pdf[45]|dvi3)_texF


>> -1 Making an exception for Additonal.lyx in the second pattern complicates
>>the regexp considerably.

> If we could considerably reduce the number of failings, we can also
> omit regexes and instead use full test names.

If we could solve all track issues within two weeks, we would not need
keywords, importance levels and the like...


Considerably reducing the number of failings would require one of the
following ugly options:

  * spend most developing time on minor cases instead of moving forward
  
  * use ugly hacks (either in documentation or in the LyX code) just to get
export working

  * reduce the number of tests (don't test corner cases like *.texF)
  
  * don't support "tricky" or rarely used packages, combinations, ...

I strongly prefer to adapt the test system to work well with a large
number sorted and well-commented lists of "known failures".



>> -1 When one of the two problems is solved, there must be edits at two
>> places.

> True :(

>> -1 The two independent problems belong do different "*Test" labeling files.
>>Where should the third clause for wrong_output ert lyxbugs go?


>> It is a quite common case, that documents have more than one "orthogonal"
>> problem. 

> Yes, unfortunately we cannot make tests selective to specific failure.

>> It is also a quite common case that a document currently fails to export
>> but we know that even if it compiles fine the output will be wrong.

>> I think we need to change the test system to care for this.

>> One possibility would be run the "invertedtests" filter also for test-cases
>> matching "unreliableTests" and give them two labels.

> This contradicts our intent for unreliableTests. To be clear, I have no
> better idea.

It is exactly what I have in mind with unreliableTests:

  # Regular expressions for tests that do not work as expected
  # (either unreliable or invalid).

When handling "unreliable" independent of inversion, we can still:

-> Skip these tests with `-LE unreliable`

-> Run with e.g. `-L nonstandard` if you have the extra requirements 
   or with -L wrong_output if you want to check...

-> If running the complete suite, don't care for failures of unreliable tests
   unless you know what you are doing.
   
   A report to the list would say something like
   
There are 13 failures: 1 regression, 2 inverted tests that now work,
and 10 unreliable tests.


Günter  

change tracking for example file update?

[Guenter Milde]

Dear Lyxdevelopers,

the seminar example file lib/examples/seminar.lyx is outdated.

There is a French translation in lib/examples/fr/seminar.lyx

I wrote the original and would volunteer to update it.

Should I use change tracking for an example file update?

The Development.lyx guide only speaks about lib/doc/...


Günter

document class with landscape orientation

[Guenter Milde]

Dear LyX-developers,

is there a layout key/value to tell LyX that a document class (or package)
uses paper orientation "landscape" as default?

Currently, seminar requires custom options for paper orientation switch:

   orientation   LyX writes  seminar expects
     ==  
   
   landscape landscape   
   
   portrait portrait
   


Thanks,

Günter   

Re: Fwd: two indexes: one has black and the other blue page numbers

[Jürgen Spitzmüller]

Am Freitag, den 23.09.2016, 16:50 +0200 schrieb Michael Berger:
>   in ~/,lyx/layouts I have not a single module but the file 
> 'lyxmodules-lst' which declares modules and their associated
> definition 
> files.

Hm, this file should actually be in ~./lyx, not ~/.lyx/layouts/

> In my system 'fixme.sty' is found here: 
> /usr/share/texmf-dist/tex/latex/fixme/fixme.sty
> and the other modules likewise.

These are LaTeX packages, not LyX modules.

> Lyx 2.1.3; Mageia5 up to date;

Aha, this is the relevant information! This is quite an old version of
LyX. This does not include the fixme module yet, so you must have it
stored somewhere. Search for the file fixme.module

I bet you have an outdated, buggy version.

Replace it with this one:
http://www.lyx.org/trac/raw-attachment/ticket/8868/fixme.module

Jürgen

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

Re: Fwd: two indexes: one has black and the other blue page numbers

[Michael Berger]

On 09/23/2016 10:42 AM, Jürgen Spitzmüller wrote:

Am Freitag, den 23.09.2016, 09:37 +0200 schrieb Michael Berger:

Dear Jürgen,
I trust this new mini example will serve your purpose.
It is on Koma-Script Article and not on classicthesis.
However, its behavior is identical - removing the module 'FiXme'
produces a correct PDF output with colored page numbers in both index
lists.

I get correct colors also with these modules. I suspect you have old
versions of these modules in your personal LyX directory
(~/.lyx/layouts). Remove them and I bet it will work (all those modules
are now included in the LyX distribution).

HTH
Jürgen


Thanks and cheers!
Michael

Dear Jürgen,
 in ~/,lyx/layouts I have not a single module but the file 
'lyxmodules-lst' which declares modules and their associated definition 
files.

I checked and found 'fixme.sty' and all the other modules listed in there.

In my system 'fixme.sty' is found here: 
/usr/share/texmf-dist/tex/latex/fixme/fixme.sty

and the other modules likewise.

Lyx 2.1.3; Mageia5 up to date;
There are seven texlive bundles of version 20130530

I am not in real need of using FiXme and could go on without using it. 
So, please, you should not invest more of your time unless, of course, 
you have other good reasons to. ;-)


Cheers,
Michael

PS: I never encountered problems in using other modules

Re: [LyX/master] ctests: found reason for "seminar" failure.

[Guenter Milde]

On 2016-09-23, Kornel Benko wrote:
> Am Freitag, 23. September 2016 um 12:25:12, schrieb Kornel Benko 
> 
>> Am Freitag, 23. September 2016 um 08:38:52, schrieb Guenter Milde 
>> 

>> > The patch is tested and applied now and the inversion of "seminar"
>> > ctests lifted. -> fixedinmaster
>> > 
>> > It may be that this solved also other export errors and some
>> > inverted tests now fail.

>> Unfortunately no. All inverted export tests 'pass'. Here at least.

At least, it will prevent issues like 


> There are some UNRELIABLE (e.g. not inverted) which pass now, but they
> are labelled as 'wrong_output'.

>   UNRELIABLE.WRONG_OUTPUT_export/examples/seminar_pdf5_texF
>   UNRELIABLE.WRONG_OUTPUT_export/examples/seminar_pdf5_systemF
>   UNRELIABLE.WRONG_OUTPUT_export/examples/fr/seminar_dvi
>   UNRELIABLE.WRONG_OUTPUT_export/examples/fr/seminar_dvi3_texF
>   UNRELIABLE.WRONG_OUTPUT_export/examples/fr/seminar_dvi3_systemF
>   UNRELIABLE.WRONG_OUTPUT_export/examples/fr/seminar_pdf5_texF
>   UNRELIABLE.WRONG_OUTPUT_export/examples/fr/seminar_pdf5_systemF

I am working on an update for the seminar example and update the
"un-/reliability" accordingly.

Thank you for looking into this...

Günter

Re: Enable View master document even if there are no child documents

[Guenter Milde]

On 2016-09-23, Jean-Marc Lasgouttes wrote:
> Le 22/09/2016 à 00:43, Guillaume Munch a écrit :
>> The attached patch does what you want.

>> The only problem is that now "View/Update Master Document" is always
>> shown.

> What about renaming master-buffer-view to buffer-view and buffer-view to 
> child-buffer-view ("View only child", or something).

> As I understand it, racoon's idea is that viewing master is the norm and 
> viewing the child the exception. Currently, we do the opposite.

There are use-cases for both:

* A book with chapters in separate files with heavy cross-linking.

  - with include/includeonly  -> view := view-child
  - with input-> view := view-master

* Stand-alone documents that also have a "wapper" document

  -> view := view-child
  
* Beamer presentations with master == beamer article  

  -> view := view-child


I don't think there is a strong case for change (never touch a running
system). OTOH, users with a strong preference for 
   view := view-master or view-standalon
should be able to customize LyX.

However, the most important is to keep View and Export preferences in
sync. It would be a bad surprise to View the master as default but export
would only work from the master buffer!


Günter

Re: [LyX/master] Cmake package: Correct description.

[Kornel Benko]

Am Freitag, 23. September 2016 um 13:43:41, schrieb Kornel Benko 

> commit 5e3ceee8d5832ff3a13e0f40a03b8540810a3df0
> Author: Kornel Benko 
> Date:   Fri Sep 23 13:39:23 2016 +0200
> 
> Cmake package: Correct description.
> 
> The new cmake 3.6 now also inserts correctly
> this file into its control-file. But the syntax of the control-file
> expects the description lines be indented by a space.
> Also empty lines (only spaces) are not allowed.
> ---
>  development/cmake/LyX_description.txt |   37 +++-
>  1 files changed, 17 insertions(+), 20 deletions(-)
> 

Richard, this should go to 2.2.x too. For older cmake versions it has no effect,
but the new cmake version (today compiled)  would create invalid package.

Kornel

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

Re: Enable View master document even if there are no child documents

[Guillaume Munch]

Le 23/09/2016 à 11:31, Jean-Marc Lasgouttes a écrit :

Le 22/09/2016 à 00:43, Guillaume Munch a écrit :

The attached patch does what you want.

The only problem is that now "View/Update Master Document" is always
shown.


What about renaming master-buffer-view to buffer-view and buffer-view to
child-buffer-view ("View only child", or something).

As I understand it, racoon's idea is that viewing master is the norm and
viewing the child the exception. Currently, we do the opposite.



I would support such a patch.

Re: [LyX/master] ctests: found reason for "seminar" failure.

[Kornel Benko]

Am Freitag, 23. September 2016 um 12:25:12, schrieb Kornel Benko 

> Am Freitag, 23. September 2016 um 08:38:52, schrieb Guenter Milde 
> 
> > On 2016-09-23, Guenter Milde wrote:
> > > On 2016-09-22, Scott Kostyshak wrote:
> > 
> > 
> > >>> ctests: found reason for "seminar" failure.
> > 
> > ...
> > 
> > > (PGF uses "nullfont" as a *feature* for suppressing output, so we should
> > > expect more of these warnings and handle them:
> > > This is LyX bug #10394 Do not error on missing characters in "nullfont".
> > > http://www.lyx.org/trac/ticket/10394
> > 
> > ...
> > 
> > > My (still untested) patch for the latter is
> > 
> > The patch is tested and applied now and the inversion of "seminar" ctests
> > lifted. -> fixedinmaster
> > 
> > It may be that this solved also other export errors and some
> > inverted tests now fail.
> 
> Unfortunately no. All inverted export tests 'pass'. Here at least.
> 

There are some UNRELIABLE (e.g. not inverted) which pass now, but they are 
labelled as 'wrong_output'.
 
UNRELIABLE.WRONG_OUTPUT_export/examples/seminar_pdf5_texF
UNRELIABLE.WRONG_OUTPUT_export/examples/seminar_pdf5_systemF
UNRELIABLE.WRONG_OUTPUT_export/examples/fr/seminar_dvi
UNRELIABLE.WRONG_OUTPUT_export/examples/fr/seminar_dvi3_texF
UNRELIABLE.WRONG_OUTPUT_export/examples/fr/seminar_dvi3_systemF
UNRELIABLE.WRONG_OUTPUT_export/examples/fr/seminar_pdf5_texF
UNRELIABLE.WRONG_OUTPUT_export/examples/fr/seminar_pdf5_systemF

> > Günter
> 
Kornel

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

Re: [LyX/master] ctests: update labeling patterns.

[Kornel Benko]

Am Freitag, 23. September 2016 um 07:29:14, schrieb Guenter Milde 

> Dear Kornel,
> 
> On 2016-09-22, Kornel Benko wrote:
> > Am Donnerstag, 22. September 2016 um 21:25:07, schrieb Guenter Milde 
> > 
> >> On 2016-09-22, Kornel Benko wrote:
> 
> >> > Now, export/doc/es/Additional_pdf4_texF in under label lyxbugs and
> >> > under label ert in invertedTests. At the same time in
> >> > unreliableTests (mask = export/doc/es/.*_(pdf[45]|dvi3)_texF) under
> >> > label wrong_output.
> 
> >> > Which of the labels should it be? (now it is wrong_output)
> 
> >> Actually both, because this are independent issues:
> 
> >> * we know export fails currently (like for de/Additional_pdf4_texF)
> >>   due to nonASCII in an ERT inset
> 
> >> * we know Spanish has problems with pdf[45]|dvi3)_texF leading to wrong
> >>   output without (but not export failure).
> 
> >>   # Babel uses the "unicode" strings if it detects XeTeX or LuaTeX.
> >>   # This is wrong for Xe/Lua with 8-bit TeX-fonts.
> 
> >> Please keep both patterns, even if currently it is not possible to have
> >> both labels. This way, the correct label will be applied if one of the
> >> issues is solved and the related pattern removed.
> 
> 
> > But that is simply not correct.
> 
> > You could use for instance
> > Sublabel: wrong_output ert lyxbugs
> 
> This would mean, 3 regexp patterns instead of 2 simpler ones
> to single out the test case that currently matches for both:

Yes, you have your points ...
In ideal case however, the (inverted|suspended|unreliable)Tests should be empty.

> Currently, we have two "orthogonal" clauses:
> 
> 1. for a problem common to all "Additional.lyx" exports in
>invertedTests:
> 
>  #9871 LyX sends invalid Unicode to iconv when converting to ASCII
>  # most probably due to BabelPreamble code (language specific headings for
>  # theorems, problems , ... are written in the language's default 
> encoding 
>  # if they contain non-ASCII characters)
>  export/doc/(es|fr)/Additional_pdf4_texF
> 
> 2. for a problem common to all Spanish documents with 8-bit fonts and
>Xe/LuaTeX:
> 
>  # Babel-Spanish uses Babel's "strings" feature to define
>  # separate auto-strings using UTF-8 literals.
>  # Babel uses the "unicode" strings if it detects XeTeX or LuaTeX.
>  # This is wrong for Xe/Lua with 8-bit TeX-fonts.
>  # set inputenc to utf8?
>  # (Changing the default in lib/languages requires more tests for utf8 
> first.)
>  export/examples/es/linguistics_pdf4_texF
>  export/doc/es/.*_(pdf[45]|dvi3)_texF
> 
> 
> -1 Making an exception for Additonal.lyx in the second pattern complicates
>the regexp considerably.

If we could considerably reduce the number of failings, we can also omit 
regexes and instead use full test names.

> -1 When one of the two problems is solved, there must be edits at two places.

True :(

> -1 The two independent problems belong do different "*Test" labeling files.
>Where should the third clause for wrong_output ert lyxbugs go?
>
> 
> It is a quite common case, that documents have more than one "orthogonal"
> problem. 

Yes, unfortunately we cannot make tests selective to specific failure.

> It is also a quite common case that a document currently fails to export
> but we know that even if it compiles fine the output will be wrong.
> 
> I think we need to change the test system to care for this.
> 
> One possibility would be run the "invertedtests" filter also for test-cases
> matching "unreliableTests" and give them two labels.

This contradicts our intent for unreliableTests. To be clear, I have no better 
idea.

> Günter
> 

Kornel

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

Re: [LyX/master] ctests: found reason for "seminar" failure.

[Kornel Benko]

Am Freitag, 23. September 2016 um 08:38:52, schrieb Guenter Milde 

> On 2016-09-23, Guenter Milde wrote:
> > On 2016-09-22, Scott Kostyshak wrote:
> 
> 
> >>> ctests: found reason for "seminar" failure.
> 
> ...
> 
> > (PGF uses "nullfont" as a *feature* for suppressing output, so we should
> > expect more of these warnings and handle them:
> > This is LyX bug #10394 Do not error on missing characters in "nullfont".
> > http://www.lyx.org/trac/ticket/10394
> 
> ...
> 
> > My (still untested) patch for the latter is
> 
> The patch is tested and applied now and the inversion of "seminar" ctests
> lifted. -> fixedinmaster
> 
> It may be that this solved also other export errors and some
> inverted tests now fail.

Unfortunately no. All inverted export tests 'pass'. Here at least.

> 
> Günter

Kornel

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

Re: Enable View master document even if there are no child documents

[Jean-Marc Lasgouttes]

Le 22/09/2016 à 00:43, Guillaume Munch a écrit :

The attached patch does what you want.

The only problem is that now "View/Update Master Document" is always
shown.


What about renaming master-buffer-view to buffer-view and buffer-view to 
child-buffer-view ("View only child", or something).


As I understand it, racoon's idea is that viewing master is the norm and 
viewing the child the exception. Currently, we do the opposite.


JMarc

Re: [RFC][PATCH] Set window title according to platform UI

[Jean-Marc Lasgouttes]

Le 22/09/2016 à 04:06, Enrico Forestieri a écrit :

Would something like that work for us? That looks good.


Yep, that seems producing an image with same quality. The patch would be
the attached one. Please, apply if you like it.


Thaks for the patch, I pushed it. I was tempted to do the same for the 
banner, but decided to wait a bit.


Actually, most of the used of getPixmap are like
  QIcon(getPixmap(...)).pixmap(somesize);

It looks like a strange code path to me. What does getPixmap return in 
the case of a svg? Some rasterized version of the svg? Then how does it 
help to go through a QIcon and then back to QPixmap?


It would look better to me to have a getIcon function which returns a 
QIcon, so that we can directly render the svg at the right size. Or did 
I misunderstand how this works?


JMarc

Re: Fwd: two indexes: one has black and the other blue page numbers

[Jürgen Spitzmüller]

Am Freitag, den 23.09.2016, 09:37 +0200 schrieb Michael Berger:
> Dear Jürgen,
> I trust this new mini example will serve your purpose.
> It is on Koma-Script Article and not on classicthesis.
> However, its behavior is identical - removing the module 'FiXme' 
> produces a correct PDF output with colored page numbers in both index
> lists.

I get correct colors also with these modules. I suspect you have old
versions of these modules in your personal LyX directory
(~/.lyx/layouts). Remove them and I bet it will work (all those modules
are now included in the LyX distribution).

HTH
Jürgen

> 
> Thanks and cheers!
> Michael

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

Re: [LyX/master] ctests: found reason for "seminar" failure.

[Guenter Milde]

On 2016-09-23, Guenter Milde wrote:
> On 2016-09-22, Scott Kostyshak wrote:


>>> ctests: found reason for "seminar" failure.

...

> (PGF uses "nullfont" as a *feature* for suppressing output, so we should
> expect more of these warnings and handle them:
> This is LyX bug #10394 Do not error on missing characters in "nullfont".
> http://www.lyx.org/trac/ticket/10394

...

> My (still untested) patch for the latter is

The patch is tested and applied now and the inversion of "seminar" ctests
lifted. -> fixedinmaster

It may be that this solved also other export errors and some
inverted tests now fail.


Günter

Re: Fwd: two indexes: one has black and the other blue page numbers

[Michael Berger]

On 09/22/2016 08:22 AM, Jürgen Spitzmüller wrote:

Am Donnerstag, den 22.09.2016, 05:08 +0200 schrieb Michael Berger:

Dear Jürgen,
talking to an expert always rewards - in one way or another.
In the course of making the mini file 'less complex' I removed all
loaded modules except 'Linguistics'.
And that solved the problem. Loading the module FiXme again had the
problem return.
Removing FiXme in my real document solved the problem there as well.

I found 'fixme.sty ... modified 28.01.2013' - is this of relevance?

Maybe, but as long as you do not provide a real minimal example, I
cannot really help.

Jürgen


Thanks again and cheers!
Michael

Dear Jürgen,
I trust this new mini example will serve your purpose.
It is on Koma-Script Article and not on classicthesis.
However, its behavior is identical - removing the module 'FiXme' 
produces a correct PDF output with colored page numbers in both index lists.


Thanks and cheers!
Michael


indexcolor.lyx
Description: application/lyx

Re: [LyX/master] ctests: update labeling patterns.

[Guenter Milde]

Dear Kornel,

On 2016-09-22, Kornel Benko wrote:
> Am Donnerstag, 22. September 2016 um 21:25:07, schrieb Guenter Milde 
> 
>> On 2016-09-22, Kornel Benko wrote:

>> > Now, export/doc/es/Additional_pdf4_texF in under label lyxbugs and
>> > under label ert in invertedTests. At the same time in
>> > unreliableTests (mask = export/doc/es/.*_(pdf[45]|dvi3)_texF) under
>> > label wrong_output.

>> > Which of the labels should it be? (now it is wrong_output)

>> Actually both, because this are independent issues:

>> * we know export fails currently (like for de/Additional_pdf4_texF)
>>   due to nonASCII in an ERT inset

>> * we know Spanish has problems with pdf[45]|dvi3)_texF leading to wrong
>>   output without (but not export failure).

>>   # Babel uses the "unicode" strings if it detects XeTeX or LuaTeX.
>>   # This is wrong for Xe/Lua with 8-bit TeX-fonts.

>> Please keep both patterns, even if currently it is not possible to have
>> both labels. This way, the correct label will be applied if one of the
>> issues is solved and the related pattern removed.


> But that is simply not correct.

> You could use for instance
>   Sublabel: wrong_output ert lyxbugs

This would mean, 3 regexp patterns instead of 2 simpler ones
to single out the test case that currently matches for both:

Currently, we have two "orthogonal" clauses:

1. for a problem common to all "Additional.lyx" exports in
   invertedTests:

 #9871 LyX sends invalid Unicode to iconv when converting to ASCII
 # most probably due to BabelPreamble code (language specific headings for
 # theorems, problems , ... are written in the language's default encoding 
 # if they contain non-ASCII characters)
 export/doc/(es|fr)/Additional_pdf4_texF

2. for a problem common to all Spanish documents with 8-bit fonts and
   Xe/LuaTeX:

 # Babel-Spanish uses Babel's "strings" feature to define
 # separate auto-strings using UTF-8 literals.
 # Babel uses the "unicode" strings if it detects XeTeX or LuaTeX.
 # This is wrong for Xe/Lua with 8-bit TeX-fonts.
 # set inputenc to utf8?
 # (Changing the default in lib/languages requires more tests for utf8 
first.)
 export/examples/es/linguistics_pdf4_texF
 export/doc/es/.*_(pdf[45]|dvi3)_texF


-1 Making an exception for Additonal.lyx in the second pattern complicates
   the regexp considerably.

-1 When one of the two problems is solved, there must be edits at two places.

-1 The two independent problems belong do different "*Test" labeling files.
   Where should the third clause for wrong_output ert lyxbugs go?
   

It is a quite common case, that documents have more than one "orthogonal"
problem. 

It is also a quite common case that a document currently fails to export
but we know that even if it compiles fine the output will be wrong.

I think we need to change the test system to care for this.

One possibility would be run the "invertedtests" filter also for test-cases
matching "unreliableTests" and give them two labels.

Günter

Re: [LyX/master] ctests: found reason for "seminar" failure.

[Guenter Milde]

On 2016-09-22, Scott Kostyshak wrote:

> [-- Type: text/plain, Encoding: quoted-printable --]

> On Thu, Sep 22, 2016 at 11:54:52PM +0200, Günter Milde wrote:
>> commit 11a036b87145b1fdaa216e238f0a6b1f5d36c3c0
>> Author: Günter Milde 
>> Date:   Thu Sep 22 23:54:18 2016 +0200

>> ctests: found reason for "seminar" failure.
>> ---

>> +#10394 Do not error on missing characters in "nullfont".
>> +# "LaTeXing" seminar fails (except for LuaTeX) with 
>> +#Missing character: There is no 0 in font nullfont!
>> +# due to a bug in PGF (https://sourceforge.net/p/pgf/bugs/314/)

> Thanks for referencing the bug report. It says it was fixed a year ago.
> It did not make it into TL 2016?

Sorry, I mixed it up. Should have been the new bug reported by me yesterday:
https://sourceforge.net/p/pgf/bugs/401/

The closed/fixed PGF bug 314 is similar but the
problem leading to the seminar failure is in another file.

(PGF uses "nullfont" as a *feature* for suppressing output, so we should
expect more of these warnings and handle them:
This is LyX bug #10394 Do not error on missing characters in "nullfont".
http://www.lyx.org/trac/ticket/10394
)

My (still untested) patch for the latter is


diff --git a/src/LaTeX.cpp b/src/LaTeX.cpp
index cfa6e1d..e5815ca 100644
--- a/src/LaTeX.cpp
+++ b/src/LaTeX.cpp
@@ -899,9 +899,11 @@ int LaTeX::scanLogFile(TeXErrors & terr)
 from_local8bit("pdfTeX Error"),
 from_local8bit(token),
 child_name);
-   } else if (prefixIs(token, "Missing character: There is 
no ")) {
-   // XeTeX/LuaTeX error about missing glyph in 
selected font
-   // (bug 9610)
+   } else if (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)
retval |= LATEX_ERROR;
terr.insertError(0,
 from_local8bit("Missing 
glyphs!"),


Günter