Re: 11 ctests fail after TL update

[Guenter Milde]

On 2016-03-06, Kornel Benko wrote:
> Am Samstag, 5. März 2016 um 21:36:43, schrieb Guenter Milde 
> 
>> On 2016-02-27, Guenter Milde wrote:

Dear Kornel,

>> >>> >> >> I've updated TL for the first time in a while and now the
>> >>> >> >> following 11 tests fail for me:

>> Did you manage to fix the problem or are the tests still failing?

>> It works here:

>> /src/lyxtest > ctest -R .*/ru/Intro_pdf4_systemF
>> Test project /usr/local/src/lyxtest
>> Start 1655: MANUALS_export/doc/ru/Intro_pdf4_systemF
>> 1/1 Test #1655: MANUALS_export/doc/ru/Intro_pdf4_systemF ...   Passed   
>> 15.72 sec


> Passes here too now.

Fine. How did you solve this?

...

>> >>> > ! Package polyglossia Error: The current roman font does not contain 
>> >>> > the Cyrill
>> >>> > ic script!
>> >>> > (polyglossia)Please define \cyrillicfont with 
>> >>> > \newfontfamily.

>> >>> Thanks, this establishes the problem as an instance of:
>> >>> http://www.lyx.org/trac/ticket/8035

>> >>> We had this already!
>> >>> See http://www.lyx.org/trac/ticket/8035#comment:11

>> > * there is a problem at some places, not all
>> > * this is a latex issue (polyglossia)
>> > * we have a LyX bug report

>> > -> Suggestion: 
>> ...
>> >* add the patterns as an instance of unreliable:lyxbugs, or 
>> >* add the patterns as an instance of unreliable:texissue.

>> * If DejaVu fails on your site, but FreeFonts work, you could also change the
>>   test script to use FreeFonts.

> Neither DejaVu nor FreeFont are working with ru/uk.

Still a mystery, as both are working here.
But which font is working at your site?

Günter

Re: 11 ctests fail after TL update

[Kornel Benko]

Am Samstag, 5. März 2016 um 21:36:43, schrieb Guenter Milde 
> On 2016-02-27, Guenter Milde wrote:
> > On 2016-02-26, Kornel Benko wrote:
> >> Am Freitag, 26. Februar 2016 um 19:08:33, schrieb Guenter Milde 
> >> 
> >>> On 2016-02-26, Kornel Benko wrote:
> 
> Dear Kornel,
> 
> >>> >> >> I've updated TL for the first time in a while and now the
> >>> >> >> following 11 tests fail for me:
> 
> Did you manage to fix the problem or are the tests still failing?
> 
> It works here:
> 
> /src/lyxtest > ctest -R .*/ru/Intro_pdf4_systemF
> Test project /usr/local/src/lyxtest
> Start 1655: MANUALS_export/doc/ru/Intro_pdf4_systemF
> 1/1 Test #1655: MANUALS_export/doc/ru/Intro_pdf4_systemF ...   Passed   15.72 
> sec
> 

Passes here too now.

> >>> ...
> 
> >>> The common  feature of these is (as regexp):
> 
> >>>   .*/ru/.*systemF
> >>>   .*/uk/.*systemF
> 
> 
> >>> >> Looks like a problem with either Cyrillic fonts or polyglossia.
> 
> >>> > ! Package polyglossia Error: The current roman font does not contain 
> >>> > the Cyrill
> >>> > ic script!
> >>> > (polyglossia)Please define \cyrillicfont with 
> >>> > \newfontfamily.
> 
> >>> Thanks, this establishes the problem as an instance of:
> >>> http://www.lyx.org/trac/ticket/8035
> 
> >>> We had this already!
> >>> See http://www.lyx.org/trac/ticket/8035#comment:11
> 
> > * there is a problem at some places, not all
> > * this is a latex issue (polyglossia)
> > * we have a LyX bug report
> 
> > -> Suggestion: 
> ...
> >* add the patterns as an instance of unreliable:lyxbugs, or 
> >* add the patterns as an instance of unreliable:texissue.
> 
> * If DejaVu fails on your site, but FreeFonts work, you could also change the
>   test script to use FreeFonts.

Neither DejaVu nor FreeFont are working with ru/uk.

> After all, this is a know upstream bug, not a "real" LyX issue (although LyX
> may add a workaround as suggested in #8035).  
> 
> 
> 
> Günter  

Kornel

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

Re: 11 ctests fail after TL update

[Guenter Milde]

On 2016-02-27, Guenter Milde wrote:
> On 2016-02-26, Kornel Benko wrote:
>> Am Freitag, 26. Februar 2016 um 19:08:33, schrieb Guenter Milde 
>> 
>>> On 2016-02-26, Kornel Benko wrote:

Dear Kornel,

>>> >> >> I've updated TL for the first time in a while and now the
>>> >> >> following 11 tests fail for me:

Did you manage to fix the problem or are the tests still failing?

It works here:

/src/lyxtest > ctest -R .*/ru/Intro_pdf4_systemF
Test project /usr/local/src/lyxtest
Start 1655: MANUALS_export/doc/ru/Intro_pdf4_systemF
1/1 Test #1655: MANUALS_export/doc/ru/Intro_pdf4_systemF ...   Passed   15.72 
sec


>>> ...

>>> The common  feature of these is (as regexp):

>>>   .*/ru/.*systemF
>>>   .*/uk/.*systemF


>>> >> Looks like a problem with either Cyrillic fonts or polyglossia.

>>> > ! Package polyglossia Error: The current roman font does not contain the 
>>> > Cyrill
>>> > ic script!
>>> > (polyglossia)Please define \cyrillicfont with 
>>> > \newfontfamily.

>>> Thanks, this establishes the problem as an instance of:
>>> http://www.lyx.org/trac/ticket/8035

>>> We had this already!
>>> See http://www.lyx.org/trac/ticket/8035#comment:11

> * there is a problem at some places, not all
> * this is a latex issue (polyglossia)
> * we have a LyX bug report

> -> Suggestion: 
...
>* add the patterns as an instance of unreliable:lyxbugs, or 
>* add the patterns as an instance of unreliable:texissue.

* If DejaVu fails on your site, but FreeFonts work, you could also change the
  test script to use FreeFonts.
  
After all, this is a know upstream bug, not a "real" LyX issue (although LyX
may add a workaround as suggested in #8035).  



Günter  

Re: 11 ctests fail after TL update

[Scott Kostyshak]

On Sat, Feb 27, 2016 at 07:50:31PM +, Guenter Milde wrote:
> On 2016-02-27, Scott Kostyshak wrote:
> > On Sat, Feb 27, 2016 at 10:35:13AM +, Guenter Milde wrote:
> >> On 2016-02-26, Kornel Benko wrote:
> 
> >> I insisted on a "hand export" as a means to get a helpfull error report.
> >> Just saying: "export fails" is no starting point for an investigation.
> 
> >> Unfortunately,
> 
> >> * the tests cannot tell more
> >> * the tests use "hidden" replacements that you need to recreate when
> >>   exporting "by hand".
> 
> >> This leads to many frustration and misunderstandings, so I hope for
> >> improvement.
> 
> > And from what I understand, the improvement you suggest is:
> > http://www.lyx.org/trac/ticket/9744
> 
> * A first step is is to use the first half of the suggested fixes there
>   (storing of Unicode and TeX font setting in the lyx file) to replace
>   the "hidden" font replacement in the test scripts with a font setting
>   in the source document.
>   
>   Then you still need to manually set "use non-TeX fonts", but no longer
>   guess which font is actually used in the tests.
>   
> * A proper fix would be to fix Ticket #9931 (command line option to
>   use/keep specified tempdir) and use this in the test scripts, so that
>   the test would not just say: "there is an error" but also log the
>   actuall reason for this error.

Makes sense. These improvements would be nice.

Scott


signature.asc
Description: PGP signature

Re: 11 ctests fail after TL update

[Guenter Milde]

On 2016-02-27, Scott Kostyshak wrote:
> On Sat, Feb 27, 2016 at 10:35:13AM +, Guenter Milde wrote:
>> On 2016-02-26, Kornel Benko wrote:

>> I insisted on a "hand export" as a means to get a helpfull error report.
>> Just saying: "export fails" is no starting point for an investigation.

>> Unfortunately,

>> * the tests cannot tell more
>> * the tests use "hidden" replacements that you need to recreate when
>>   exporting "by hand".

>> This leads to many frustration and misunderstandings, so I hope for
>> improvement.

> And from what I understand, the improvement you suggest is:
> http://www.lyx.org/trac/ticket/9744

* A first step is is to use the first half of the suggested fixes there
  (storing of Unicode and TeX font setting in the lyx file) to replace
  the "hidden" font replacement in the test scripts with a font setting
  in the source document.
  
  Then you still need to manually set "use non-TeX fonts", but no longer
  guess which font is actually used in the tests.
  
* A proper fix would be to fix Ticket #9931 (command line option to
  use/keep specified tempdir) and use this in the test scripts, so that
  the test would not just say: "there is an error" but also log the
  actuall reason for this error.
  
Günter  

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Samstag, 27. Februar 2016 um 11:21:19, schrieb Scott Kostyshak 

> On Sat, Feb 27, 2016 at 02:51:25PM +0100, Kornel Benko wrote:
> > Am Samstag, 27. Februar 2016 um 01:35:41, schrieb Scott Kostyshak 
> > 
> > > On Fri, Feb 26, 2016 at 01:31:43PM +, Guenter Milde wrote:
> > > > On 2016-02-26, Scott Kostyshak wrote:
> > > > > On Fri, Feb 26, 2016 at 07:50:19AM +0100, Kornel Benko wrote:
> > > > >> Am Donnerstag, 25. Februar 2016 um 23:44:17, schrieb Scott Kostyshak 
> > > > >> 
> > > > >> > On Wed, Feb 24, 2016 at 09:51:12PM +0100, Kornel Benko wrote:
> > > > >> > > Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde 
> > > > >> > > 
> > > > >> > 
> > > > >> > > > BTW: my version of the "system font" is 
> > > > ...
> > > > >> > > > Version: 4.5.0~dfsg-1
> > > > 
> > > > ...
> > > > 
> > > > > Ah it is because I have it installed from tlmgr. I just assumed that 
> > > > > we
> > > > > were talking about apt packages because it wasn't in TL.
> > > > 
> > > > While pdftex and luatex use the version installed by TeXLive, xetex uses
> > > > the system-wide installed version for all fonts. This led to the
> > > > xetex-problem (due to the system-wide installed font missing one
> > > > character at Kornels system).
> > > > 
> > > > Independent of this, a generic luatex problem remains
> > > > (see suspiciousTests).
> > > 
> > > Ah this makes sense. I now remember that I make all TL fonts available
> > > as system fonts. Second mystery (at least for me) is also solved now.
> > 
> > Interesting. How did you make TL fonts available to system?
> > 
> > I tried it with creating /etc/fonts/conf.d/09-texlive-fonts.conf (with 
> > contents of /texmf-var/fonts/conf/texlive-fontconfig.conf),
> > but after using 'fc-cache -fsv' I lost some DejaVu fonts in lyx.
> > They appear in lyx only as unknown in the list of selectable system fonts;
> 
> I followed the instructions here:
> http://tex.stackexchange.com/questions/1092/how-to-install-vanilla-texlive-on-debian-or-ubuntu/95373#95373
> 
> Is there something listed there that might help?

YES. Especially this one:
gksudo gedit /etc/fonts/conf.d/09-texlive.conf
Remove the line containing type1 and save
Thanks.

> Scott

Kornel

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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Scott Kostyshak]

On Sat, Feb 27, 2016 at 02:51:25PM +0100, Kornel Benko wrote:
> Am Samstag, 27. Februar 2016 um 01:35:41, schrieb Scott Kostyshak 
> 
> > On Fri, Feb 26, 2016 at 01:31:43PM +, Guenter Milde wrote:
> > > On 2016-02-26, Scott Kostyshak wrote:
> > > > On Fri, Feb 26, 2016 at 07:50:19AM +0100, Kornel Benko wrote:
> > > >> Am Donnerstag, 25. Februar 2016 um 23:44:17, schrieb Scott Kostyshak 
> > > >> 
> > > >> > On Wed, Feb 24, 2016 at 09:51:12PM +0100, Kornel Benko wrote:
> > > >> > > Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde 
> > > >> > > 
> > > >> > 
> > > >> > > > BTW: my version of the "system font" is 
> > > ...
> > > >> > > > Version: 4.5.0~dfsg-1
> > > 
> > > ...
> > > 
> > > > Ah it is because I have it installed from tlmgr. I just assumed that we
> > > > were talking about apt packages because it wasn't in TL.
> > > 
> > > While pdftex and luatex use the version installed by TeXLive, xetex uses
> > > the system-wide installed version for all fonts. This led to the
> > > xetex-problem (due to the system-wide installed font missing one
> > > character at Kornels system).
> > > 
> > > Independent of this, a generic luatex problem remains
> > > (see suspiciousTests).
> > 
> > Ah this makes sense. I now remember that I make all TL fonts available
> > as system fonts. Second mystery (at least for me) is also solved now.
> 
> Interesting. How did you make TL fonts available to system?
> 
> I tried it with creating /etc/fonts/conf.d/09-texlive-fonts.conf (with 
> contents of /texmf-var/fonts/conf/texlive-fontconfig.conf),
> but after using 'fc-cache -fsv' I lost some DejaVu fonts in lyx.
> They appear in lyx only as unknown in the list of selectable system fonts;

I followed the instructions here:
http://tex.stackexchange.com/questions/1092/how-to-install-vanilla-texlive-on-debian-or-ubuntu/95373#95373

Is there something listed there that might help?

Scott


signature.asc
Description: PGP signature

Re: 11 ctests fail after TL update

[Scott Kostyshak]

On Sat, Feb 27, 2016 at 10:35:13AM +, Guenter Milde wrote:
> On 2016-02-26, Kornel Benko wrote:

> I insisted on a "hand export" as a means to get a helpfull error report.
> Just saying: "export fails" is no starting point for an investigation.
> 
> Unfortunately,
> 
> * the tests cannot tell more
> * the tests use "hidden" replacements that you need to recreate when
>   exporting "by hand".
> 
> This leads to many frustration and misunderstandings, so I hope for
> improvement.

And from what I understand, the improvement you suggest is:
http://www.lyx.org/trac/ticket/9744

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Samstag, 27. Februar 2016 um 01:35:41, schrieb Scott Kostyshak 

> On Fri, Feb 26, 2016 at 01:31:43PM +, Guenter Milde wrote:
> > On 2016-02-26, Scott Kostyshak wrote:
> > > On Fri, Feb 26, 2016 at 07:50:19AM +0100, Kornel Benko wrote:
> > >> Am Donnerstag, 25. Februar 2016 um 23:44:17, schrieb Scott Kostyshak 
> > >> 
> > >> > On Wed, Feb 24, 2016 at 09:51:12PM +0100, Kornel Benko wrote:
> > >> > > Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde 
> > >> > > 
> > >> > 
> > >> > > > BTW: my version of the "system font" is 
> > ...
> > >> > > > Version: 4.5.0~dfsg-1
> > 
> > ...
> > 
> > > Ah it is because I have it installed from tlmgr. I just assumed that we
> > > were talking about apt packages because it wasn't in TL.
> > 
> > While pdftex and luatex use the version installed by TeXLive, xetex uses
> > the system-wide installed version for all fonts. This led to the
> > xetex-problem (due to the system-wide installed font missing one
> > character at Kornels system).
> > 
> > Independent of this, a generic luatex problem remains
> > (see suspiciousTests).
> 
> Ah this makes sense. I now remember that I make all TL fonts available
> as system fonts. Second mystery (at least for me) is also solved now.

Interesting. How did you make TL fonts available to system?

I tried it with creating /etc/fonts/conf.d/09-texlive-fonts.conf (with contents 
of /texmf-var/fonts/conf/texlive-fontconfig.conf),
but after using 'fc-cache -fsv' I lost some DejaVu fonts in lyx.
They appear in lyx only as unknown in the list of selectable system fonts;

Checking with 'fontmatrix' I can see they are known.
Also creating output with lyx shows no problem.

> Scott

Kornel

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

Re: 11 ctests fail after TL update

[Guenter Milde]

On 2016-02-26, Kornel Benko wrote:
> Am Freitag, 26. Februar 2016 um 19:08:33, schrieb Guenter Milde 
> 
>> On 2016-02-26, Kornel Benko wrote:


>> >> >> I've updated TL for the first time in a while and now the following 11
>> >> >> tests fail for me:

>> ...

>> The common  feature of these is (as regexp):

>>   .*/ru/.*systemF
>>   .*/uk/.*systemF


>> >> Looks like a problem with either Cyrillic fonts or polyglossia.

>> >> Could you export at least one example "per hand" and post the
>> >> error, please?


>> > Errors creating PDF-luatex with system fonts:

>> > ... 13 times ...
>> > ! Package polyglossia Error: The current roman font does not contain the 
>> > Cyrill
>> > ic script!
>> > (polyglossia)Please define \cyrillicfont with 
>> > \newfontfamily.

>> Thanks, this establishes the problem as an instance of:
>> http://www.lyx.org/trac/ticket/8035

>> We had this already!
>> See http://www.lyx.org/trac/ticket/8035#comment:11

* there is a problem at some places, not all
* this is a latex issue (polyglossia)
* we have a LyX bug report

-> Suggestion: Either 
   * solve the bug,
   * add the patterns as an instance of unreliable:lyxbugs, or 
   * add the patterns as an instance of unreliable:texissue.


---

>> > ...
>> > Missing character: There is no В (U+0412) in font 
>> > "file:lmroman17-regular:scrip
>> > t=latn;+trep;+tlig;"!
>> ...
>> > And so on ... about 1000 lines

>> This is due to the hidden font change in the test but not for
>> hand-exporting. 
>> *Latin* modern has no Cyrillic characters.

> Please reread. This was manually done, no font change, lyx is using defaults.

I read carefully but formulated misleading:

-> the reason you see the "missing character" errors now but not in the ctest
   is ...
>> the hidden font change in the test but not for
>> hand-exporting. 

>> > If using DejaVu fonts (as with ctest), there are only 3 errors
>> > ! Package polyglossia Error: The current roman font does not contain the 
>> > Cyrill
>> > ic script!

>> > and no missing glyphs.

> And this one was with font change. 

Yes. With DejaVu instead of LatinModern.

To solve the riddle of the new failures, we need to know:

* Which font was/is used in the tests? DejaVu or FreeSans? (Both provide 
  Cyrillic characters.)

* Does this font announce support for Cyrillic script in a way understood by
  polyglossia?

* Did it so before?

...



> Why do you insist on test making something wrong? 

I don't. There is a misunderstanding.

> Using DejaVu here is done because of your suggestion.  With the test we
> get 3 errors and the created pdf is readable. I am able to read
> cyrilic, so I think, I can judge. Exporting manually (no test, the only
> change is use non-tex font in the lyx gui) gives zillion errors.

I insisted on a "hand export" as a means to get a helpfull error report.
Just saying: "export fails" is no starting point for an investigation.

Unfortunately,

* the tests cannot tell more
* the tests use "hidden" replacements that you need to recreate when
  exporting "by hand".

This leads to many frustration and misunderstandings, so I hope for
improvement.


Günter  
  




>   Kornel
> [-- Skipped Type: application/pgp-signature, Filename: signature.asc --]

Re: 11 ctests fail after TL update

[Scott Kostyshak]

On Fri, Feb 26, 2016 at 10:50:02PM +0100, Kornel Benko wrote:
> Am Freitag, 26. Februar 2016 um 19:08:33, schrieb Guenter Milde 
> <mi...@users.sf.net>

> > This is why I argue in 
> > http://www.lyx.org/trac/ticket/8035#comment:7
> > to ignore the polyglossia error: LyX's check for missing characters is more
> > accurate and fully sufficient.

Interesting. I no longer have the computer with me on which I updated.
But I did a quick manual test and I got errors, and then I compiled
again after getting the errors and there was a successful compilation.

> > OK. As this is a long existing polyglossia problem, it may be rather be a
> > font update or some other chagne in your setup or the test setup not
> > related to the TL update.

I was careful to do the following, and nothing in-between:

clean build
ctest
tlmgr update
clean build
ctest

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Scott Kostyshak]

On Fri, Feb 26, 2016 at 01:31:43PM +, Guenter Milde wrote:
> On 2016-02-26, Scott Kostyshak wrote:
> > On Fri, Feb 26, 2016 at 07:50:19AM +0100, Kornel Benko wrote:
> >> Am Donnerstag, 25. Februar 2016 um 23:44:17, schrieb Scott Kostyshak 
> >> 
> >> > On Wed, Feb 24, 2016 at 09:51:12PM +0100, Kornel Benko wrote:
> >> > > Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde 
> >> > > 
> >> > 
> >> > > > BTW: my version of the "system font" is 
> ...
> >> > > > Version: 4.5.0~dfsg-1
> 
> ...
> 
> > Ah it is because I have it installed from tlmgr. I just assumed that we
> > were talking about apt packages because it wasn't in TL.
> 
> While pdftex and luatex use the version installed by TeXLive, xetex uses
> the system-wide installed version for all fonts. This led to the
> xetex-problem (due to the system-wide installed font missing one
> character at Kornels system).
> 
> Independent of this, a generic luatex problem remains
> (see suspiciousTests).

Ah this makes sense. I now remember that I make all TL fonts available
as system fonts. Second mystery (at least for me) is also solved now.

Scott


signature.asc
Description: PGP signature

Re: 11 ctests fail after TL update

[Kornel Benko]

Am Freitag, 26. Februar 2016 um 19:08:33, schrieb Guenter Milde 
<mi...@users.sf.net>
> On 2016-02-26, Kornel Benko wrote:
> > Am Freitag, 26. Februar 2016 um 13:26:43, schrieb Guenter Milde 
> > <mi...@users.sf.net>
> >> On 2016-02-26, Kornel Benko wrote:
> >> > Am Freitag, 26. Februar 2016 um 01:15:52, schrieb Scott Kostyshak 
> >> > <skost...@lyx.org>
> >> >> I've updated TL for the first time in a while and now the following 11
> >> >> tests fail for me:
> 
> ...
> 
> The common  feature of these is (as regexp):
> 
>   .*/ru/.*systemF
>   .*/uk/.*systemF
> 
> 
> >> Looks like a problem with either Cyrillic fonts or polyglossia.
> 
> >> Could you export at least one example "per hand" and post the error, 
> >> please?
> 
> 
> > Errors creating PDF-luatex with system fonts:
> 
> > ... 13 times ...
> > ! Package polyglossia Error: The current roman font does not contain the 
> > Cyrill
> > ic script!
> > (polyglossia)Please define \cyrillicfont with 
> > \newfontfamily.
> 
> Thanks, this establishes the problem as an instance of:
> http://www.lyx.org/trac/ticket/8035
> 
> We had this already!
> See http://www.lyx.org/trac/ticket/8035#comment:11
> 
> > ...
> > Missing character: There is no В (U+0412) in font 
> > "file:lmroman17-regular:scrip
> > t=latn;+trep;+tlig;"!
> ...
> > And so on ... about 1000 lines
>  
> This is due to the hidden font change in the test but not for
> hand-exporting. 
> *Latin* modern has no Cyrillic characters.

Please reread. This was manually done, no font change, lyx is using defaults.

> > If using DejaVu fonts (as with ctest), there are only 3 errors
> > ! Package polyglossia Error: The current roman font does not contain the 
> > Cyrill
> > ic script!
> 
> > and no missing glyphs.
> 
> 
> This is why I argue in 
> http://www.lyx.org/trac/ticket/8035#comment:7
> to ignore the polyglossia error: LyX's check for missing characters is more
> accurate and fully sufficient.

And this one was with font change. 

> >> Also, the version of polyglossia/gloss-russian.ldf and the polyglossia
> >> changelog might give a hint.
> 
> > It is always the newest available for TL15.
> 
> OK. As this is a long existing polyglossia problem, it may be rather be a
> font update or some other chagne in your setup or the test setup not
> related to the TL update.
> 

Why do you insist on test making something wrong? Using DejaVu here is done 
because of your suggestion. 
With the test we get 3 errors and the created pdf is readable. I am able to 
read cyrilic, so I
think, I can judge.
Exporting manually (no test, the only change is use non-tex font in the lyx 
gui) gives zillion errors.

> Günter

Kornel

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

Re: 11 ctests fail after TL update

[Guenter Milde]

On 2016-02-26, Kornel Benko wrote:
> Am Freitag, 26. Februar 2016 um 13:26:43, schrieb Guenter Milde 
> <mi...@users.sf.net>
>> On 2016-02-26, Kornel Benko wrote:
>> > Am Freitag, 26. Februar 2016 um 01:15:52, schrieb Scott Kostyshak 
>> > <skost...@lyx.org>
>> >> I've updated TL for the first time in a while and now the following 11
>> >> tests fail for me:

...

The common  feature of these is (as regexp):

  .*/ru/.*systemF
  .*/uk/.*systemF


>> Looks like a problem with either Cyrillic fonts or polyglossia.

>> Could you export at least one example "per hand" and post the error, please?


> Errors creating PDF-luatex with system fonts:

> ... 13 times ...
> ! Package polyglossia Error: The current roman font does not contain the 
> Cyrill
> ic script!
> (polyglossia)Please define \cyrillicfont with \newfontfamily.

Thanks, this establishes the problem as an instance of:
http://www.lyx.org/trac/ticket/8035

We had this already!
See http://www.lyx.org/trac/ticket/8035#comment:11

> ...
> Missing character: There is no В (U+0412) in font 
> "file:lmroman17-regular:scrip
> t=latn;+trep;+tlig;"!
...
> And so on ... about 1000 lines
 
This is due to the hidden font change in the test but not for
hand-exporting. 
*Latin* modern has no Cyrillic characters.

> If using DejaVu fonts (as with ctest), there are only 3 errors
> ! Package polyglossia Error: The current roman font does not contain the 
> Cyrill
> ic script!

> and no missing glyphs.


This is why I argue in 
http://www.lyx.org/trac/ticket/8035#comment:7
to ignore the polyglossia error: LyX's check for missing characters is more
accurate and fully sufficient.

>> Also, the version of polyglossia/gloss-russian.ldf and the polyglossia
>> changelog might give a hint.

> It is always the newest available for TL15.

OK. As this is a long existing polyglossia problem, it may be rather be a
font update or some other chagne in your setup or the test setup not
related to the TL update.


Günter

Re: 11 ctests fail after TL update

[Kornel Benko]

Am Freitag, 26. Februar 2016 um 13:26:43, schrieb Guenter Milde 

> On 2016-02-26, Kornel Benko wrote:
> 
> > [-- Type: text/plain, Encoding: 7bit --]
> 
> > Am Freitag, 26. Februar 2016 um 01:15:52, schrieb Scott Kostyshak 
> > 
> >> I've updated TL for the first time in a while and now the following 11
> >> tests fail for me:
> 
> >> ctest -R 
> >> "MANUALS_export/doc/ru/Intro_dvi3_systemF|MANUALS_export/doc/ru/Intro_pdf5_systemF|
> > confirmed
> 
> >> MANUALS_export/doc/uk/Intro_dvi3_systemF|MANUALS_export/doc/uk/Intro_pdf5_systemF|
> > confirmed
> 
> >> EXAMPLES_export/examples/ru/splash_dvi3_systemF|EXAMPLES_export/examples/ru/splash_pdf5_systemF|
> > confirmed
> 
> >> EXAMPLES_export/examples/uk/splash_dvi3_systemF|EXAMPLES_export/examples/uk/splash_pdf5_systemF|
> > confirmed
> 
> >> TEMPLATES_export/templates/slides_dvi3_systemF|TEMPLATES_export/templates/slides_pdf4_systemF|
> >>  TEMPLATES_export/templates/slides_pdf5_systemF"
> > confirmed
> 
> 
> Looks like a problem with either Cyrillic fonts or polyglossia.
> 
> Could you export at least one example "per hand" and post the error, please?

Errors creating PDF-luatex with system fonts:

... 13 times ...
! Package polyglossia Error: The current roman font does not contain the Cyrill
ic script!
(polyglossia)Please define \cyrillicfont with \newfontfamily.

...
Missing character: There is no В (U+0412) in font "file:lmroman17-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no в (U+0432) in font "file:lmroman17-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no е (U+0435) in font "file:lmroman17-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no д (U+0434) in font "file:lmroman17-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no е (U+0435) in font "file:lmroman17-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no н (U+043D) in font "file:lmroman17-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no и (U+0438) in font "file:lmroman17-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no е (U+0435) in font "file:lmroman17-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no в (U+0432) in font "file:lmroman17-regular:scrip
t=latn;+trep;+tlig;"!
{/usr9/local/texlive/2015/texmf-var/fonts/map/pdftex/updmap/pdftex.map}
Missing character: There is no а (U+0430) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no в (U+0432) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no т (U+0442) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no о (U+043E) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no р (U+0440) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no к (U+043A) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no о (U+043E) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no м (U+043C) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no а (U+0430) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no н (U+043D) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no д (U+0434) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no а (U+0430) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no р (U+0440) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no а (U+0430) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no з (U+0437) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no р (U+0440) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no а (U+0430) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no б (U+0431) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!
Missing character: There is no о (U+043E) in font "file:lmroman12-regular:scrip
t=latn;+trep;+tlig;"!


And so on ... about 1000 lines

If using DejaVu fonts (as with ctest), there are only 3 errors
! Package polyglossia Error: The current roman font does not contain the Cyrill
ic script!

and no missing glyphs.

> Also, the version of polyglossia/gloss-russian.ldf and the polyglossia
> changelog might give a hint.

It is always the newest available for TL15.
Could not see a version spec in .ldf. In polyglossia is 
'\ProvidesPackage{polyglossia}[2015/08/06 v1.42.0
  Alternative to Babel for XeLaTeX and LuaLaTeX]'
Where can I find the changelog?

> Günter

Kornel

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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Guenter Milde]

On 2016-02-26, Scott Kostyshak wrote:
> On Fri, Feb 26, 2016 at 07:50:19AM +0100, Kornel Benko wrote:
>> Am Donnerstag, 25. Februar 2016 um 23:44:17, schrieb Scott Kostyshak 
>> 
>> > On Wed, Feb 24, 2016 at 09:51:12PM +0100, Kornel Benko wrote:
>> > > Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde 
>> > > 
>> > 
>> > > > BTW: my version of the "system font" is 
...
>> > > > Version: 4.5.0~dfsg-1

...

> Ah it is because I have it installed from tlmgr. I just assumed that we
> were talking about apt packages because it wasn't in TL.

While pdftex and luatex use the version installed by TeXLive, xetex uses
the system-wide installed version for all fonts. This led to the
xetex-problem (due to the system-wide installed font missing one
character at Kornels system).

Independent of this, a generic luatex problem remains
(see suspiciousTests).

Günter

Re: 11 ctests fail after TL update

[Guenter Milde]

On 2016-02-26, Kornel Benko wrote:

> [-- Type: text/plain, Encoding: 7bit --]

> Am Freitag, 26. Februar 2016 um 01:15:52, schrieb Scott Kostyshak 
> 
>> I've updated TL for the first time in a while and now the following 11
>> tests fail for me:

>> ctest -R 
>> "MANUALS_export/doc/ru/Intro_dvi3_systemF|MANUALS_export/doc/ru/Intro_pdf5_systemF|
> confirmed

>> MANUALS_export/doc/uk/Intro_dvi3_systemF|MANUALS_export/doc/uk/Intro_pdf5_systemF|
> confirmed

>> EXAMPLES_export/examples/ru/splash_dvi3_systemF|EXAMPLES_export/examples/ru/splash_pdf5_systemF|
> confirmed

>> EXAMPLES_export/examples/uk/splash_dvi3_systemF|EXAMPLES_export/examples/uk/splash_pdf5_systemF|
> confirmed

>> TEMPLATES_export/templates/slides_dvi3_systemF|TEMPLATES_export/templates/slides_pdf4_systemF|
>>  TEMPLATES_export/templates/slides_pdf5_systemF"
> confirmed


Looks like a problem with either Cyrillic fonts or polyglossia.

Could you export at least one example "per hand" and post the error, please?

Also, the version of polyglossia/gloss-russian.ldf and the polyglossia
changelog might give a hint.

Günter

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Freitag, 26. Februar 2016 um 03:14:10, schrieb Scott Kostyshak 

> On Fri, Feb 26, 2016 at 07:50:19AM +0100, Kornel Benko wrote:
> > Am Donnerstag, 25. Februar 2016 um 23:44:17, schrieb Scott Kostyshak 
> > 
> > > On Wed, Feb 24, 2016 at 09:51:12PM +0100, Kornel Benko wrote:
> > > > Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde 
> > > > 
> > > 
> > > > > BTW: my version of the "system font" is 
> > > > > 
> > > > > Paket: fonts-font-awesome
> > > > > Zustand: Installiert
> > > > > Automatisch installiert: ja
> > > > > Multi-Arch: foreign
> > > > > Version: 4.5.0~dfsg-1
> > > > > 
> > > > 
> > > > Thanks, that was the culprit. I downloaded this newest package. No 
> > > > problem anymore.
> > > 
> > > I did not follow this thread, but I have:
> > > 
> > > $ apt-cache policy fonts-font-awesome
> > > fonts-font-awesome:
> > >   Installed: (none)
> > >   Candidate: 4.2.0~dfsg-1
> > >   Version table:
> > >  4.2.0~dfsg-1 0
> > > 500 http://us.archive.ubuntu.com/ubuntu/ vivid/universe amd64 
> > > Packages
> > > $ 
> > > 
> > > Is there still a mystery then of why the test passes for me?
> > 
> > No mystery anymore, my version was even lesser. 4.0.0~dfsg-1.
> 
> Ah it is because I have it installed from tlmgr.

I doubt that this is the reason. I have installed it in tlmgr too.

> I just assumed that we
> were talking about apt packages because it wasn't in TL.

We did. But you probably has a newer OS. My Mint 17 is still based on ubuntu 
14.04

> $ tlmgr info fontawesome
> package: fontawesome
> category:Package
> shortdesc:   Font containing web-related icons
> longdesc:The package offers access to the large number of
> web-related icons provided by the included font. The package requires
> the package, fontspec, if run with XeTeX or LuaTeX.
> installed:   Yes
> revision:38051
> sizes:   doc: 249k, run: 417k
> relocatable: Yes
> cat-version: 4.4.0
> cat-date:2015-08-03 05:43:12 +0200
> cat-license: lppl1.3
> cat-topics:  font font-supp-symbol font-symbol font-otf font-type1
> collection:  collection-fontsextra
> $

Here it is the same.

> Scott

Kornel

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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Scott Kostyshak]

On Fri, Feb 26, 2016 at 07:50:19AM +0100, Kornel Benko wrote:
> Am Donnerstag, 25. Februar 2016 um 23:44:17, schrieb Scott Kostyshak 
> 
> > On Wed, Feb 24, 2016 at 09:51:12PM +0100, Kornel Benko wrote:
> > > Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde 
> > > 
> > 
> > > > BTW: my version of the "system font" is 
> > > > 
> > > > Paket: fonts-font-awesome
> > > > Zustand: Installiert
> > > > Automatisch installiert: ja
> > > > Multi-Arch: foreign
> > > > Version: 4.5.0~dfsg-1
> > > > 
> > > 
> > > Thanks, that was the culprit. I downloaded this newest package. No 
> > > problem anymore.
> > 
> > I did not follow this thread, but I have:
> > 
> > $ apt-cache policy fonts-font-awesome
> > fonts-font-awesome:
> >   Installed: (none)
> >   Candidate: 4.2.0~dfsg-1
> >   Version table:
> >  4.2.0~dfsg-1 0
> > 500 http://us.archive.ubuntu.com/ubuntu/ vivid/universe amd64 
> > Packages
> > $ 
> > 
> > Is there still a mystery then of why the test passes for me?
> 
> No mystery anymore, my version was even lesser. 4.0.0~dfsg-1.

Ah it is because I have it installed from tlmgr. I just assumed that we
were talking about apt packages because it wasn't in TL.

$ tlmgr info fontawesome
package: fontawesome
category:Package
shortdesc:   Font containing web-related icons
longdesc:The package offers access to the large number of
web-related icons provided by the included font. The package requires
the package, fontspec, if run with XeTeX or LuaTeX.
installed:   Yes
revision:38051
sizes:   doc: 249k, run: 417k
relocatable: Yes
cat-version: 4.4.0
cat-date:2015-08-03 05:43:12 +0200
cat-license: lppl1.3
cat-topics:  font font-supp-symbol font-symbol font-otf font-type1
collection:  collection-fontsextra
$

Scott


signature.asc
Description: PGP signature

Re: 11 ctests fail after TL update

[Kornel Benko]

Am Freitag, 26. Februar 2016 um 01:15:52, schrieb Scott Kostyshak 

> I've updated TL for the first time in a while and now the following 11
> tests fail for me:
> 
> ctest -R 
> "MANUALS_export/doc/ru/Intro_dvi3_systemF|MANUALS_export/doc/ru/Intro_pdf5_systemF|
confirmed

> MANUALS_export/doc/uk/Intro_dvi3_systemF|MANUALS_export/doc/uk/Intro_pdf5_systemF|
confirmed

> EXAMPLES_export/examples/ru/splash_dvi3_systemF|EXAMPLES_export/examples/ru/splash_pdf5_systemF|
confirmed

> EXAMPLES_export/examples/uk/splash_dvi3_systemF|EXAMPLES_export/examples/uk/splash_pdf5_systemF|
confirmed

> TEMPLATES_export/templates/slides_dvi3_systemF|TEMPLATES_export/templates/slides_pdf4_systemF|
>  TEMPLATES_export/templates/slides_pdf5_systemF"
confirmed

> 
> Can anyone confirm?
> 
> Scott

Kornel



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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Donnerstag, 25. Februar 2016 um 23:44:17, schrieb Scott Kostyshak 

> On Wed, Feb 24, 2016 at 09:51:12PM +0100, Kornel Benko wrote:
> > Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde 
> > 
> 
> > > BTW: my version of the "system font" is 
> > > 
> > > Paket: fonts-font-awesome
> > > Zustand: Installiert
> > > Automatisch installiert: ja
> > > Multi-Arch: foreign
> > > Version: 4.5.0~dfsg-1
> > > 
> > 
> > Thanks, that was the culprit. I downloaded this newest package. No problem 
> > anymore.
> 
> I did not follow this thread, but I have:
> 
> $ apt-cache policy fonts-font-awesome
> fonts-font-awesome:
>   Installed: (none)
>   Candidate: 4.2.0~dfsg-1
>   Version table:
>  4.2.0~dfsg-1 0
> 500 http://us.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
> $ 
> 
> Is there still a mystery then of why the test passes for me?

No mystery anymore, my version was even lesser. 4.0.0~dfsg-1.

> Scott

Kornel

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

11 ctests fail after TL update

[Scott Kostyshak]

I've updated TL for the first time in a while and now the following 11
tests fail for me:

ctest -R 
"MANUALS_export/doc/ru/Intro_dvi3_systemF|MANUALS_export/doc/ru/Intro_pdf5_systemF|MANUALS_export/doc/uk/Intro_dvi3_systemF|MANUALS_export/doc/uk/Intro_pdf5_systemF|EXAMPLES_export/examples/ru/splash_dvi3_systemF|EXAMPLES_export/examples/ru/splash_pdf5_systemF|EXAMPLES_export/examples/uk/splash_dvi3_systemF|EXAMPLES_export/examples/uk/splash_pdf5_systemF|TEMPLATES_export/templates/slides_dvi3_systemF|TEMPLATES_export/templates/slides_pdf4_systemF|TEMPLATES_export/templates/slides_pdf5_systemF"

Can anyone confirm?

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Scott Kostyshak]

On Wed, Feb 24, 2016 at 09:51:12PM +0100, Kornel Benko wrote:
> Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde 
> 

> > BTW: my version of the "system font" is 
> > 
> > Paket: fonts-font-awesome
> > Zustand: Installiert
> > Automatisch installiert: ja
> > Multi-Arch: foreign
> > Version: 4.5.0~dfsg-1
> > 
> 
> Thanks, that was the culprit. I downloaded this newest package. No problem 
> anymore.

I did not follow this thread, but I have:

$ apt-cache policy fonts-font-awesome
fonts-font-awesome:
  Installed: (none)
  Candidate: 4.2.0~dfsg-1
  Version table:
 4.2.0~dfsg-1 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
$ 

Is there still a mystery then of why the test passes for me?

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Mittwoch, 24. Februar 2016 um 20:20:10, schrieb Guenter Milde 

> On 2016-02-24, Kornel Benko wrote:
> 
> > [-- Type: text/plain, Encoding: 7bit --]
> 
> > Am Mittwoch, 24. Februar 2016 um 15:52:48, schrieb Guenter Milde 
> > 
> >> On 2016-02-24, Kornel Benko wrote:
> 
> > ...
> 
> >> > But you have a point, libreoffice doesn't show characters above U+F195
> >> > in private area.
> 
> >> This may be a limitation of libreoffice, not the font. Maybe some other
> >> font-viewer (I use "fontmatrix") will help...
> 
> 
> > Thanks for the pointer. Nice tool. But here too, no glyphs above U+f500. 
> > The last 10
> > glyphs U+f196 -- U+f500 are without a glyph.
> 
> > So probably _my_ font is missing something.
> 
> Maybe. I have been able to see the "private use" characters in fontforge
> (but did not find the time to search for mobile phone...).
> 
> BTW: my version of the "system font" is 
> 
> Paket: fonts-font-awesome
> Zustand: Installiert
> Automatisch installiert: ja
> Multi-Arch: foreign
> Version: 4.5.0~dfsg-1
> 

Thanks, that was the culprit. I downloaded this newest package. No problem 
anymore.

Kornel

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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Guenter Milde]

On 2016-02-24, Kornel Benko wrote:

> [-- Type: text/plain, Encoding: 7bit --]

> Am Mittwoch, 24. Februar 2016 um 15:52:48, schrieb Guenter Milde 
> 
>> On 2016-02-24, Kornel Benko wrote:

> ...

>> > But you have a point, libreoffice doesn't show characters above U+F195
>> > in private area.

>> This may be a limitation of libreoffice, not the font. Maybe some other
>> font-viewer (I use "fontmatrix") will help...


> Thanks for the pointer. Nice tool. But here too, no glyphs above U+f500. The 
> last 10
> glyphs U+f196 -- U+f500 are without a glyph.

> So probably _my_ font is missing something.

Maybe. I have been able to see the "private use" characters in fontforge
(but did not find the time to search for mobile phone...).

BTW: my version of the "system font" is 

Paket: fonts-font-awesome
Zustand: Installiert
Automatisch installiert: ja
Multi-Arch: foreign
Version: 4.5.0~dfsg-1

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Mittwoch, 24. Februar 2016 um 15:52:48, schrieb Guenter Milde 

> On 2016-02-24, Kornel Benko wrote:

...

> > But you have a point, libreoffice doesn't show characters above U+F195
> > in private area.
>
> This may be a limitation of libreoffice, not the font. Maybe some other
> font-viewer (I use "fontmatrix") will help...
>

Thanks for the pointer. Nice tool. But here too, no glyphs above U+f500. The 
last 10
glyphs U+f196 -- U+f500 are without a glyph.

So probably _my_ font is missing something.

> >> Otherwise, if you cannot solve this problem, I suggest to add a pattern
> >> for the test(s) that fail at your site to unreliableTests with a telling
> >> comment.
>
> >:(
>
> Unfortunately, I cant help more.
>
>
> I may give a hand to attempt a fix for the "seminar" issue. It is
> something where I am personally interested. (It also works here and for
> Scott but not at your site...)

Hoping the best.

Kornel


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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Guenter Milde]

On 2016-02-24, Kornel Benko wrote:
> Am Mittwoch, 24. Februar 2016 um 09:49:34, schrieb Guenter Milde 
> 
>> On 2016-02-23, Kornel Benko wrote:
>> > Am Dienstag, 23. Februar 2016 um 20:06:05, schrieb Guenter Milde 
>> > 
>> >> On 2016-02-20, Guenter Milde wrote:
>> >> > On 2016-02-20, Kornel Benko wrote:
>> >> >> Am Samstag, 20. Februar 2016 um 16:34:50, schrieb Guenter Milde 
>> >> >> 

>> >> Dear Kornel, 

...

>> >> The edit of the example "unearthed" a dependency problem with
>> >> moderncv.layout that can occure when

>> >> * compiling with XeTeX,
>> >> * fonts awesome installed for LaTeX but not declared a system font. 

...

>> Maybe a different version as system font and TeX font?

> That may be. The system font is from package fonts-font-awesome,
> claiming to have version 4.0.0~dfsg-1 , while the tex font is from
> TL15-package fontawesome, version 38051 (4.4.0)
> OTOH using the same system from lualatex works, so I doubt that this is
> the reason.

see below

...

>> > I already have the newest fontawesome.sty in TL, so no need to add it to
>> > some project dir.

>> While pdftex uses a local, customized 8-bit encoded version of the font
>> and luatex uses the version installed by TL via its own font loading
>> mechanism, XeTeX loads fonts via the OS.

> OK, that looks like a good explanation.

>> Could you check with some font listing program or LibreOffice or
>> similar, whether the missing character is present in the font "as seen
>> by the system"?

> Lualatex finds it, is that not evident enough?

No:

>> luatex uses the version installed by TL via its own font loading
>> mechanism, XeTeX loads fonts via the OS.

Also, luatex works but xetex not.

Maybe you can find version numbers for the font file in the detailed logs.

> But you have a point, libreoffice doesn't show characters above U+F195
> in private area.

This may be a limitation of libreoffice, not the font. Maybe some other
font-viewer (I use "fontmatrix") will help...


>> Otherwise, if you cannot solve this problem, I suggest to add a pattern
>> for the test(s) that fail at your site to unreliableTests with a telling
>> comment.

>:(

Unfortunately, I cant help more.


I may give a hand to attempt a fix for the "seminar" issue. It is
something where I am personally interested. (It also works here and for
Scott but not at your site...)

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Mittwoch, 24. Februar 2016 um 09:49:34, schrieb Guenter Milde 

> On 2016-02-23, Kornel Benko wrote:
> > Am Dienstag, 23. Februar 2016 um 20:06:05, schrieb Guenter Milde 
> > 
> >> On 2016-02-20, Guenter Milde wrote:
> >> > On 2016-02-20, Kornel Benko wrote:
> >> >> Am Samstag, 20. Februar 2016 um 16:34:50, schrieb Guenter Milde 
> >> >> 
> 
> >> Dear Kornel, 
> 
> ...
> >> >>> >> > I installed fonts-font-awesome, now the font is found. 
> 
> >> ... it is loaded in the tex output -- however, this is due to the
> >> line
> 
> >> #  
> >> \DeclareLaTeXClass[moderncv,ebgaramond.sty,fancyhdr.sty,fontawesome.sty,ifpdf.sty,marvosym.sty]{Modern
> >>  CV}
> 
> >> in moderncv.layout.
> 
> >> The edit of the example "unearthed" a dependency problem with
> >> moderncv.layout that can occure when
> 
> >> * compiling with XeTeX,
> >> * fonts awesome installed for LaTeX but not declared a system font. 
> 
> >> See answer 2 in 
> >> http://tex.stackexchange.com/questions/132888/fontawesome-font-not-found
> 
> > I have different problem with xelatex. The 'broken' example in this
> > link compiles fine here, so xelatex finds the font already.
> 
> Maybe a different version as system font and TeX font?

That may be. The system font is from package fonts-font-awesome, claiming to 
have version 4.0.0~dfsg-1 ,
while the tex font is from TL15-package fontawesome, version 38051 (4.4.0)
OTOH using the same system from lualatex works, so I doubt that this is the 
reason.

...
> >>   -- https://coderwall.com/p/r67dyq/using-font-awesome-with-xe-latex
> 
> >> I am not sure whether this is a good idea, but here you are...
> 
> > I don't understand. 
> 
> This was an aside: I don't know whether it is a good idea to create a font
> with all characters in the private use area, but this is what the designers
> of "Awesome" did. The moderncv author seems to like the idea (or just the
> font) and hence used it in the package...
> 
> 
> 
> > I already have the newest fontawesome.sty in TL, so no need to add it to
> > some project dir.
> 
> While pdftex uses a local, customized 8-bit encoded version of the font
> and luatex uses the version installed by TL via its own font loading
> mechanism, XeTeX loads fonts via the OS.

OK, that looks like a good explanation.

> Could you check with some font listing program or LibreOffice or similar,
> whether the missing character is present in the font "as seen by the system"?

Lualatex finds it, is that not evident enough?
But you have a point, libreoffice doesn't show characters above U+F195 in 
private area.

> Otherwise, if you cannot solve this problem, I suggest to add a pattern
> for the test(s) that fail at your site to unreliableTests with a telling
> comment.

:(

> Günter
>

Kornel

Kornel

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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Guenter Milde]

On 2016-02-23, Kornel Benko wrote:
> Am Dienstag, 23. Februar 2016 um 20:06:05, schrieb Guenter Milde 
> 
>> On 2016-02-20, Guenter Milde wrote:
>> > On 2016-02-20, Kornel Benko wrote:
>> >> Am Samstag, 20. Februar 2016 um 16:34:50, schrieb Guenter Milde 
>> >> 

>> Dear Kornel, 

...
>> >>> >> > I installed fonts-font-awesome, now the font is found. 

>> ... it is loaded in the tex output -- however, this is due to the
>> line

>> #  
>> \DeclareLaTeXClass[moderncv,ebgaramond.sty,fancyhdr.sty,fontawesome.sty,ifpdf.sty,marvosym.sty]{Modern
>>  CV}

>> in moderncv.layout.

>> The edit of the example "unearthed" a dependency problem with
>> moderncv.layout that can occure when

>> * compiling with XeTeX,
>> * fonts awesome installed for LaTeX but not declared a system font. 

>> See answer 2 in 
>> http://tex.stackexchange.com/questions/132888/fontawesome-font-not-found

> I have different problem with xelatex. The 'broken' example in this
> link compiles fine here, so xelatex finds the font already.

Maybe a different version as system font and TeX font?

>> >>> >> > But there are still missing glyphs.
>> ...
>> >>> > Output of xelatex (system font + tex font):
>> >>> > Missing character: There is no  in font FontAwesome/OT!

>> > Do you mean the literal character between "no" and "in font"?

>> > My editor says this is:

>> > Character '' (61868, 0xF1AC)

>> > which is in:

>> > @@ E000Private Use AreaF8FF
>> > @+ This range of 6400 code points is dedicated to private use.

>> It is actually a non-standard character in the private use area:

>>   Font Awesome is a free (CC-BY-3.0) icon font from GitHub, that contains
>>   several different icons for various purposes. It is designed for web
>>   usage, and thus all the characters are defined in the private unicode
>>   range to avoid confusing screen readers.

>>   -- https://coderwall.com/p/r67dyq/using-font-awesome-with-xe-latex

>> I am not sure whether this is a good idea, but here you are...

> I don't understand. 

This was an aside: I don't know whether it is a good idea to create a font
with all characters in the private use area, but this is what the designers
of "Awesome" did. The moderncv author seems to like the idea (or just the
font) and hence used it in the package...



> I already have the newest fontawesome.sty in TL, so no need to add it to
> some project dir.

While pdftex uses a local, customized 8-bit encoded version of the font
and luatex uses the version installed by TL via its own font loading
mechanism, XeTeX loads fonts via the OS.

Could you check with some font listing program or LibreOffice or similar,
whether the missing character is present in the font "as seen by the system"?


Otherwise, if you cannot solve this problem, I suggest to add a pattern
for the test(s) that fail at your site to unreliableTests with a telling
comment.

Günter




Günter

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Dienstag, 23. Februar 2016 um 20:06:05, schrieb Guenter Milde 

> On 2016-02-20, Guenter Milde wrote:
> > On 2016-02-20, Kornel Benko wrote:
> >> Am Samstag, 20. Februar 2016 um 16:34:50, schrieb Guenter Milde 
> >> 
> 
> Dear Kornel, 
> 
> I hope to have solved the "XeTeX + Awesome" mystery:
> 
> >>> >> >> Strange: It works here, both "per hand" and via ctest...
> 
> >>> >> > I installed fonts-font-awesome, now the font is found. 
> 
> >>> I can't see where font Awesome is loaded - the font selectiong GUI
> >>> shows all is set to "default". This seems to be some internal font
> >>> setting of the modernCV package (or its style options). Nothing to
> >>> blame the document edits.
> 
> OK, now I see it is loaded in the tex output -- however, this is due to the
> line
> 
> #  
> \DeclareLaTeXClass[moderncv,ebgaramond.sty,fancyhdr.sty,fontawesome.sty,ifpdf.sty,marvosym.sty]{Modern
>  CV}
> 
> in moderncv.layout.
> 
> The edit of the example "unearthed" a dependency problem with moderncv.layout
> that can occure when
> 
> * compiling with XeTeX,
> * fonts awesome installed for LaTeX but not declared a system font. 
> 
> See answer 2 in 
> http://tex.stackexchange.com/questions/132888/fontawesome-font-not-found

I have different problem with xelatex. The 'broken' example in this link 
compiles fine here, so xelatex finds the font already.

> >>> >> > But there are still missing glyphs.
> ...
> >>> > Output of xelatex (system font + tex font):
> >>> > Missing character: There is no  in font FontAwesome/OT!
> 
> > Do you mean the literal character between "no" and "in font"?
> 
> > My editor says this is:
> 
> > Character '' (61868, 0xF1AC)
> 
> > which is in:
> 
> > @@  E000Private Use AreaF8FF
> > @+  This range of 6400 code points is dedicated to private use.
> 
> It is actually a non-standard character in the private use area:
> 
>   Font Awesome is a free (CC-BY-3.0) icon font from GitHub, that contains
>   several different icons for various purposes. It is designed for web
>   usage, and thus all the characters are defined in the private unicode
>   range to avoid confusing screen readers.
> 
>   -- https://coderwall.com/p/r67dyq/using-font-awesome-with-xe-latex
> 
> I am not sure whether this is a good idea, but here you are...

I don't understand. I already have the newest fontawesome.sty in TL, so no need 
to add it to some project dir.

> > However, it is not the same as the one(s) missing in LuaTeX:
> 
> Indeed, the LuaTeX problem is different, it does not depend on moderncv or
> the awesome font.
> 
> Günter

Kornel

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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Guenter Milde]

On 2016-02-20, Guenter Milde wrote:
> On 2016-02-20, Kornel Benko wrote:
>> Am Samstag, 20. Februar 2016 um 16:34:50, schrieb Guenter Milde 
>> 

Dear Kornel, 

I hope to have solved the "XeTeX + Awesome" mystery:

>>> >> >> Strange: It works here, both "per hand" and via ctest...

>>> >> > I installed fonts-font-awesome, now the font is found. 

>>> I can't see where font Awesome is loaded - the font selectiong GUI
>>> shows all is set to "default". This seems to be some internal font
>>> setting of the modernCV package (or its style options). Nothing to
>>> blame the document edits.

OK, now I see it is loaded in the tex output -- however, this is due to the
line

#  
\DeclareLaTeXClass[moderncv,ebgaramond.sty,fancyhdr.sty,fontawesome.sty,ifpdf.sty,marvosym.sty]{Modern
 CV}

in moderncv.layout.

The edit of the example "unearthed" a dependency problem with moderncv.layout
that can occure when

* compiling with XeTeX,
* fonts awesome installed for LaTeX but not declared a system font. 

See answer 2 in 
http://tex.stackexchange.com/questions/132888/fontawesome-font-not-found


>>> >> > But there are still missing glyphs.
...
>>> > Output of xelatex (system font + tex font):
>>> > Missing character: There is no  in font FontAwesome/OT!

> Do you mean the literal character between "no" and "in font"?

> My editor says this is:

> Character '' (61868, 0xF1AC)

> which is in:

> @@E000Private Use AreaF8FF
> @+This range of 6400 code points is dedicated to private use.

It is actually a non-standard character in the private use area:

  Font Awesome is a free (CC-BY-3.0) icon font from GitHub, that contains
  several different icons for various purposes. It is designed for web
  usage, and thus all the characters are defined in the private unicode
  range to avoid confusing screen readers.

  -- https://coderwall.com/p/r67dyq/using-font-awesome-with-xe-latex

I am not sure whether this is a good idea, but here you are...



> However, it is not the same as the one(s) missing in LuaTeX:

Indeed, the LuaTeX problem is different, it does not depend on moderncv or
the awesome font.

Günter

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Montag, 22. Februar 2016 um 23:20:21, schrieb Kornel Benko 
> > Did you try? It fails here. (Cf. lyx test file below.)
> > 
> 
> I tried the lyx file you sent. Luatex has no problem with deactivated 1st 
> branch.
> I.e. if '${a}_{\mbox{a}}$' is active.
> 

Outch. I had overseen '\text' in the second branch. You are right.

Kornel

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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Montag, 22. Februar 2016 um 21:17:44, schrieb Guenter Milde 

> On 2016-02-21, Kornel Benko wrote:
> > Am Sonntag, 21. Februar 2016 um 16:07:20, schrieb Guenter Milde 
> > 
> >> On 2016-02-21, Kornel Benko wrote:
> 
> >> >> I investigated a little. Trying to compile manually (export as luatex,
> >> >> use bibtex, use lualatex) I found what is causing lualatex/bibtex to
> >> >> misbehave.
> 
> >> >> 1.) bibtex does not like the string 'jacsat' (biblioExample.bib:61,
> >> >> entry Arduengo1994). Enclosing it in '{}' cures it. E.g. 'journal =
> >> >> {jacsat},'.
> 
> >> This is new. It worked fine here.
> 
> > You can it see only if manually calling bibtex. It is a warning
> > otherwise which lyx and luatex ignore.
> 
> However, did you also test that putting it into {} does not change the output?
> Is it the same for 8-bit tex vs. luatex and for {jacsat} vs. jacsat ?
> 
> I assume this is supposed to be a pre-defined string but the definition may
> be missing...
> 
> >> >> 2.) lualatex does not like the construct (biblioExample.bib:36, entry: 
> >> >> Eisenstein2005)
> >> >> $\mbox{IrH}_{\mbox{5}}(\mbox{PPh}_{\mbox{3}})_{\mbox{2}}$
> >> >> in title. Especially the last '_' is causing trouble. So for instance
> >> >> $\mbox{IrH}_{\mbox{5}}(\mbox{PPh}_{\mbox{3}}){\mbox{2}}$
> >> >> is OK.
> 
> >> This resembles the description in suspiciousTests (the result of my
> >> experiments):
> 
> >> # LuaTeX fails for an \mbox in an index, e.g. $a_{\mbox{a}}$.
> >> # This construct appears in the included bib file biblioExample.bib in
> >> # the entry Eisenstein2005. Error message is
> >> #   Missing character: There is no (U+6035) in font rm-lmr12!
> >> # (with system fonts: 602D and 6039)
> >> export/examples/(|es/)(europe|modern)CV_(dvi3|pdf5)_(texF|systemF)
> 
> > Ah, yes. Did not think of looking at the description.
> > But, using your example,  ${a}_{\mbox{a}}$ would work.
> 
> Did you try? It fails here. (Cf. lyx test file below.)
> 

I tried the lyx file you sent. Luatex has no problem with deactivated 1st 
branch.
I.e. if '${a}_{\mbox{a}}$' is active.

> >> >> So, what to do with this biblio entry?
> 
> >> Mailing the patch to the upstream author?
> 
> >> Reporting the "mbox in index" problem to the LuaTeX authors?
> 
> > This is not about \mbox I think. 
> 
> > This patch fixes the luatex testcase for me. (But not xelatex)
> 
> There is still the mystery, why xelatex works here but not at your site.

Sure.

> The error report (missing character with some "strange" Unicode point) seems
> to point to a similar problem.

Unfortunately not similar. In case of xetex there is a problem to display the 
glyph used for phone type.
Changing the phone type to e.g. 'mobile' or 'fixed' ==> no problem with xelatex.
Luatex has no problems here.

> Günter

Kornel



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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Guenter Milde]

On 2016-02-21, Kornel Benko wrote:
> Am Sonntag, 21. Februar 2016 um 16:07:20, schrieb Guenter Milde 
> 
>> On 2016-02-21, Kornel Benko wrote:

>> >> I investigated a little. Trying to compile manually (export as luatex,
>> >> use bibtex, use lualatex) I found what is causing lualatex/bibtex to
>> >> misbehave.

>> >> 1.) bibtex does not like the string 'jacsat' (biblioExample.bib:61,
>> >> entry Arduengo1994). Enclosing it in '{}' cures it. E.g. 'journal =
>> >> {jacsat},'.

>> This is new. It worked fine here.

> You can it see only if manually calling bibtex. It is a warning
> otherwise which lyx and luatex ignore.

However, did you also test that putting it into {} does not change the output?
Is it the same for 8-bit tex vs. luatex and for {jacsat} vs. jacsat ?

I assume this is supposed to be a pre-defined string but the definition may
be missing...

>> >> 2.) lualatex does not like the construct (biblioExample.bib:36, entry: 
>> >> Eisenstein2005)
>> >>   $\mbox{IrH}_{\mbox{5}}(\mbox{PPh}_{\mbox{3}})_{\mbox{2}}$
>> >> in title. Especially the last '_' is causing trouble. So for instance
>> >>   $\mbox{IrH}_{\mbox{5}}(\mbox{PPh}_{\mbox{3}}){\mbox{2}}$
>> >> is OK.

>> This resembles the description in suspiciousTests (the result of my
>> experiments):

>> # LuaTeX fails for an \mbox in an index, e.g. $a_{\mbox{a}}$.
>> # This construct appears in the included bib file biblioExample.bib in
>> # the entry Eisenstein2005. Error message is
>> #   Missing character: There is no (U+6035) in font rm-lmr12!
>> # (with system fonts: 602D and 6039)
>> export/examples/(|es/)(europe|modern)CV_(dvi3|pdf5)_(texF|systemF)

> Ah, yes. Did not think of looking at the description.
> But, using your example,  ${a}_{\mbox{a}}$ would work.

Did you try? It fails here. (Cf. lyx test file below.)


>> >> So, what to do with this biblio entry?

>> Mailing the patch to the upstream author?

>> Reporting the "mbox in index" problem to the LuaTeX authors?

> This is not about \mbox I think. 

> This patch fixes the luatex testcase for me. (But not xelatex)

There is still the mystery, why xelatex works here but not at your site.
The error report (missing character with some "strange" Unicode point) seems
to point to a similar problem.


Günter




#LyX 2.2 created this file. For more info see http://www.lyx.org/
\lyxformat 506
\begin_document
\begin_header
\save_transient_properties true
\origin unavailable
\textclass article
\use_default_options true
\maintain_unincluded_children false
\language english
\language_package default
\inputencoding auto
\fontencoding global
\font_roman "default" "default"
\font_sans "default" "default"
\font_typewriter "default" "default"
\font_math "auto" "auto"
\font_default_family default
\use_non_tex_fonts true
\font_sc false
\font_osf false
\font_sf_scale 100 100
\font_tt_scale 100 100
\graphics default
\default_output_format pdf5
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 1
\use_package cancel 1
\use_package esint 1
\use_package mathdots 1
\use_package mathtools 1
\use_package mhchem 1
\use_package stackrel 1
\use_package stmaryrd 1
\use_package undertilde 1
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 1
\branch with mbox
\selected 1
\filename_suffix 0
\color #faf0e6
\end_branch
\branch with \text
\selected 0
\filename_suffix 0
\color #faf0e6
\end_branch
\branch with \mbox
\selected 1
\filename_suffix 0
\color #faf0e6
\end_branch
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header

\begin_body

\begin_layout Standard
Ah, yes.
 Did not think of looking at the description.
\end_layout

\begin_layout Standard
But, using your example, 
\begin_inset Branch with \mbox
status open

\begin_layout Standard
\begin_inset Formula ${a}_{\mbox{a}}$
\end_inset


\end_layout

\end_inset

 
\begin_inset Branch with \text
status open

\begin_layout Standard
\begin_inset Formula ${a}_{\text{a}}$
\end_inset


\end_layout

\end_inset

would work.
\end_layout

\end_body
\end_document

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Sonntag, 21. Februar 2016 um 16:07:20, schrieb Guenter Milde 

> On 2016-02-21, Kornel Benko wrote:
> 
> >> I investigated a little. Trying to compile manually (export as luatex,
> >> use bibtex, use lualatex) I found what is causing lualatex/bibtex to
> >> misbehave.
> 
> >> 1.) bibtex does not like the string 'jacsat' (biblioExample.bib:61,
> >> entry Arduengo1994). Enclosing it in '{}' cures it. E.g. 'journal =
> >> {jacsat},'.
> 
> This is new. It worked fine here.

You can it see only if manually calling bibtex. It is a warning otherwise which 
lyx and luatex ignore.

> >> 2.) lualatex does not like the construct (biblioExample.bib:36, entry: 
> >> Eisenstein2005)
> >>$\mbox{IrH}_{\mbox{5}}(\mbox{PPh}_{\mbox{3}})_{\mbox{2}}$
> >> in title. Especially the last '_' is causing trouble. So for instance
> >>$\mbox{IrH}_{\mbox{5}}(\mbox{PPh}_{\mbox{3}}){\mbox{2}}$
> >> is OK.
> 
> This resembles the description in suspiciousTests (the result of my
> experiments):
> 
> # LuaTeX fails for an \mbox in an index, e.g. $a_{\mbox{a}}$.
> # This construct appears in the included bib file biblioExample.bib in
> # the entry Eisenstein2005. Error message is
> #   Missing character: There is no (U+6035) in font rm-lmr12!
> # (with system fonts: 602D and 6039)
> export/examples/(|es/)(europe|modern)CV_(dvi3|pdf5)_(texF|systemF)

Ah, yes. Did not think of looking at the description.
But, using your example,  ${a}_{\mbox{a}}$ would work.

> >> Also if using '{}' instead of '()' there is no problem.
> 
> >> So, what to do with this biblio entry?
> 
> Mailing the patch to the upstream author?
> 
> Reporting the "mbox in index" problem to the LuaTeX authors?

This is not about \mbox I think. 

> > This patch fixes the luatex testcase for me. (But not xelatex)
> 
> 
> Günter
> 

Kornel

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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Guenter Milde]

On 2016-02-21, Kornel Benko wrote:

>> I investigated a little. Trying to compile manually (export as luatex,
>> use bibtex, use lualatex) I found what is causing lualatex/bibtex to
>> misbehave.

>> 1.) bibtex does not like the string 'jacsat' (biblioExample.bib:61,
>> entry Arduengo1994). Enclosing it in '{}' cures it. E.g. 'journal =
>> {jacsat},'.

This is new. It worked fine here.

>> 2.) lualatex does not like the construct (biblioExample.bib:36, entry: 
>> Eisenstein2005)
>>  $\mbox{IrH}_{\mbox{5}}(\mbox{PPh}_{\mbox{3}})_{\mbox{2}}$
>> in title. Especially the last '_' is causing trouble. So for instance
>>  $\mbox{IrH}_{\mbox{5}}(\mbox{PPh}_{\mbox{3}}){\mbox{2}}$
>> is OK.

This resembles the description in suspiciousTests (the result of my
experiments):

# LuaTeX fails for an \mbox in an index, e.g. $a_{\mbox{a}}$.
# This construct appears in the included bib file biblioExample.bib in
# the entry Eisenstein2005. Error message is
#   Missing character: There is no (U+6035) in font rm-lmr12!
# (with system fonts: 602D and 6039)
export/examples/(|es/)(europe|modern)CV_(dvi3|pdf5)_(texF|systemF)

>> Also if using '{}' instead of '()' there is no problem.

>> So, what to do with this biblio entry?

Mailing the patch to the upstream author?

Reporting the "mbox in index" problem to the LuaTeX authors?


> This patch fixes the luatex testcase for me. (But not xelatex)


Günter

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Sonntag, 21. Februar 2016 um 13:24:02, schrieb Kornel Benko 
> Am Samstag, 20. Februar 2016 um 20:52:23, schrieb Guenter Milde 
> 
> >
> > OTOH, I am pretty sure this has something to do with some of the used
> > LaTeX packages not beeing fit for Xe/LuaTeX. Maybe you can bisect or we
> > need to compare the complete list of included packages and their
> > versions.
> >
>
> I investigated a little. Trying to compile manually (export as luatex, use 
> bibtex, use lualatex) I found what is causing lualatex/bibtex to misbehave.
>
> 1.) bibtex does not like the string 'jacsat' (biblioExample.bib:61, entry 
> Arduengo1994). Enclosing it in '{}' cures it. E.g. 'journal = {jacsat},'.
> 2.) lualatex does not like the construct (biblioExample.bib:36, entry: 
> Eisenstein2005)
>   $\mbox{IrH}_{\mbox{5}}(\mbox{PPh}_{\mbox{3}})_{\mbox{2}}$
> in title. Especially the last '_' is causing trouble. So for instance
>   $\mbox{IrH}_{\mbox{5}}(\mbox{PPh}_{\mbox{3}}){\mbox{2}}$
> is OK.
> Also if using '{}' instead of '()' there is no problem.
>
> So, what to do with this biblio entry?
>

This patch fixes the luatex testcase for me. (But not xelatex)

Korneldiff --git a/lib/examples/biblioExample.bib b/lib/examples/biblioExample.bib
index bfed96f..f966626 100644
--- a/lib/examples/biblioExample.bib
+++ b/lib/examples/biblioExample.bib
@@ -33,7 +33,7 @@
 	and Clot, Eric and Eisenstein, Odile and Crabtree, Robert H.},
   title = {{A}n anion-dependent switch in selectivity results from a change
 	of {C}---{H} activation mechanism in the reaction of an imidazolium
-	salt with $\mbox{IrH}_{\mbox{5}}(\mbox{PPh}_{\mbox{3}})_{\mbox{2}}$},
+	salt with $\mbox{IrH}_{\mbox{5}}{(\mbox{PPh}_{\mbox{3}})}_{\mbox{2}}$},
   journal = {{J}.~{A}m.\ {C}hem. {S}oc.},
   year = {2005},
   volume = {127},
@@ -58,7 +58,7 @@
   author = {Arduengo, III, Anthony J. and Siegfried F. Gamper and Joseph C. Calabrese
 	and Fredric Davidson},
   title = {{L}ow-coordinate carbene complexes of nickel(0) and platinum(0)},
-  journal = jacsat,
+  journal = {jacsat},
   year = {1994},
   volume = {116},
   pages = {4391--4394},


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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Samstag, 20. Februar 2016 um 20:52:23, schrieb Guenter Milde 

> 
> OTOH, I am pretty sure this has something to do with some of the used
> LaTeX packages not beeing fit for Xe/LuaTeX. Maybe you can bisect or we
> need to compare the complete list of included packages and their
> versions.
> 

I investigated a little. Trying to compile manually (export as luatex, use 
bibtex, use lualatex) I found what is causing lualatex/bibtex to misbehave.

1.) bibtex does not like the string 'jacsat' (biblioExample.bib:61, entry 
Arduengo1994). Enclosing it in '{}' cures it. E.g. 'journal = {jacsat},'.
2.) lualatex does not like the construct (biblioExample.bib:36, entry: 
Eisenstein2005)
$\mbox{IrH}_{\mbox{5}}(\mbox{PPh}_{\mbox{3}})_{\mbox{2}}$
in title. Especially the last '_' is causing trouble. So for instance
$\mbox{IrH}_{\mbox{5}}(\mbox{PPh}_{\mbox{3}}){\mbox{2}}$
is OK.
Also if using '{}' instead of '()' there is no problem.

So, what to do with this biblio entry?

Kornel

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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Guenter Milde]

On 2016-02-20, Uwe Stöhr wrote:
> Am 19.02.2016 um 10:44 schrieb Kornel Benko:

>> This comment seems misleading. With pdflatex it was compilable also
>> before this commit.

> It was only compilable with many hacks in the preamble. That file was 
> not compilable in the current modernCV version because of a babel issue 
> with Spanish. We found now a solution (the preamble line) and could 
> update the file.

OK, then this would be the more accurate description.
I am glad you found a way to clean up the document.


>> Now 2 more testcases fail.

>> 6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF 
>> ..***Failed   61.93 sec
>> 7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF 
>> .***Failed   61.93 sec

>> I know, you don't care.

> I still don't understand your goal. The user should be able to click on 
> the view button and get a nice PDF. Ignacio assures this and as long as 
> this works we can be happy.


> The play with different export methods might be nice for experts while 
> the average user don't care about how his PDF was internally created. I 
> don't say that it is bad to play around but it is not important for the 
> user, only for us to uncover possible bugs.

I agree with this regarding changes that lead to a "cleaner" (less hackisch,
less ERT, less preamble) document.

OTOH, I think it is good to make documents "robust" by ensuring they compile
with a variety of export routes - not only for finding bugs but also as a
bonus for the user. But, as a bonus means this is on top of the primary
purpose of compilable, clean and simple user documentation/templates.


> Nevertheless special text classes like e.g. the CVs are not designed to 
> work with all engines nor to be translatable nor to work with babel 
> and/polyglossia so I am wondering that our tests expect that.

Well, if you look at moderncv, you will see that it is actually designed to
work with pdftex, xetex, and luatex. However, the design is hidden in the
class and may interfere with LyX's way to handle the differences.
Especially, it tries to automate things and internally calls "fontspec"
whenever xetex or luatex is detected. 

This may clash with manually setting fonts in LyX -- something that should
be expored and described.

Günter

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Guenter Milde]

On 2016-02-20, Kornel Benko wrote:

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

> Am Samstag, 20. Februar 2016 um 16:34:50, schrieb Guenter Milde 
> <mi...@users.sf.net>
>> On 2016-02-20, Kornel Benko wrote:
>> > Am Samstag, 20. Februar 2016 um 15:40:54, schrieb Guenter Milde 
>> > <mi...@users.sf.net>
>> >> On 2016-02-20, Kornel Benko wrote:
>> >> > Am Freitag, 19. Februar 2016 um 21:32:22, schrieb Guenter Milde 
>> >> > <mi...@users.sf.net>
>> >> >> On 2016-02-19, Kornel Benko wrote:
>> >> >> > Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr 
>> >> >> > <uwesto...@lyx.org>
>> >> >> >> commit ba28f504b5b674debe137b45301ced2edc5eeb33
>> >> >> >> Author: Uwe Stöhr <uwesto...@lyx.org>
>> >> >> >> Date:   Fri Feb 19 02:16:36 2016 +0100

>> >> >> >> Spanish modernCV.lyx: update the file and make it compilable

>> >> >> > This comment seems misleading. With pdflatex it was compilable also
>> >> >> > before this commit. Now 2 more testcases fail.

>> >> >> > 6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF 
>> >> >> > ..***Failed   61.93 sec
>> >> >> > 7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF 
>> >> >> > .***Failed   61.93 sec

>> >> >> Strange: It works here, both "per hand" and via ctest...

>> >> > I installed fonts-font-awesome, now the font is found. 

>> I can't see where font Awesome is loaded - the font selectiong GUI shows all
>> is set to "default". This seems to be some internal font setting of the
>> modernCV package (or its style options). Nothing to blame the document edits.

>> >> > But there are still missing glyphs.

>> >> Which? (You should be able to copy-paste from the "full log".)

>> > I suppose it is the glyph used for fax.  "\phone[fax]{+43(0)999 }"

> This one:

>> > Output of xelatex (system font + tex font):
>> > Missing character: There is no  in font FontAwesome/OT!

Do you mean the literal character between "no" and "in font"?

My editor says this is:

Character '' (61868, 0xF1AC)

which is in:

@@  E000Private Use AreaF8FF
@+  This range of 6400 code points is dedicated to private use.

However, it is not the same as the one(s) missing in LuaTeX:

>> > Output of lualatex (system font):
>> > Missing character: There is no 䫂 (U+4AC2) in font rm-lmr12!
>> > Output of lualatex (tex font):
>> > Missing character: There is no 䨢 (U+4A22) in font rm-lmr12!

So I still believe

>> Rather, there is some mix-up in the character selection internals.



> I'd rather know, what is missing here. 
> Scott and I have similar installations. If we would know the reason, we
> could describe it also in suspiciousTests.

I agree. It would be nice if you (or someone else) found the time to
investigate.

>> >> Still, it is strange that this fails at your place but runs fine here and
>> >> for Scott.

>> What is your version of moderncv.cls? Here it is

>> \ProvidesClass{moderncv}[2015/07/28 v2.0.0 modern curriculum vitae and 
>> letter document class]


> It is the same here.

OK.

OTOH, I am pretty sure this has something to do with some of the used
LaTeX packages not beeing fit for Xe/LuaTeX. Maybe you can bisect or we
need to compare the complete list of included packages and their
versions.

Günter

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Samstag, 20. Februar 2016 um 16:34:50, schrieb Guenter Milde 
<mi...@users.sf.net>
> On 2016-02-20, Kornel Benko wrote:
> > Am Samstag, 20. Februar 2016 um 15:40:54, schrieb Guenter Milde 
> > <mi...@users.sf.net>
> >> On 2016-02-20, Kornel Benko wrote:
> >> > Am Freitag, 19. Februar 2016 um 21:32:22, schrieb Guenter Milde 
> >> > <mi...@users.sf.net>
> >> >> On 2016-02-19, Kornel Benko wrote:
> >> >> > Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr 
> >> >> > <uwesto...@lyx.org>
> >> >> >> commit ba28f504b5b674debe137b45301ced2edc5eeb33
> >> >> >> Author: Uwe Stöhr <uwesto...@lyx.org>
> >> >> >> Date:   Fri Feb 19 02:16:36 2016 +0100
> 
> >> >> >> Spanish modernCV.lyx: update the file and make it compilable
> 
> >> >> > This comment seems misleading. With pdflatex it was compilable also
> >> >> > before this commit. Now 2 more testcases fail.
> 
> >> >> > 6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF 
> >> >> > ..***Failed   61.93 sec
> >> >> > 7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF 
> >> >> > .***Failed   61.93 sec
> 
> >> >> Strange: It works here, both "per hand" and via ctest...
> 
> >> > I installed fonts-font-awesome, now the font is found. 
> 
> I can't see where font Awesome is loaded - the font selectiong GUI shows all
> is set to "default". This seems to be some internal font setting of the
> modernCV package (or its style options). Nothing to blame the document edits.
> 
> >> > But there are still missing glyphs.
> 
> >> Which? (You should be able to copy-paste from the "full log".)
> 
> > I suppose it is the glyph used for fax.  "\phone[fax]{+43(0)999 }"

This one:

> > Output of xelatex (system font + tex font):
> > Missing character: There is no  in font FontAwesome/OT!
> 
> > Output of lualatex (system font):
> > Missing character: There is no 䫂 (U+4AC2) in font rm-lmr12!
> > Output of lualatex (tex font):
> > Missing character: There is no 䨢 (U+4A22) in font rm-lmr12!
> 
> There is no character starting with 4A.. in my Unicode list
> @@@   The Unicode Standard 8.0.0
> @@@+  U80M150527.lst
>   Unicode 8.0.0 final names list.
> 
> Only the heading
> 
> @@3400CJK Unified Ideographs Extension A  4DB5
> 
> I don't think there is a CJK Unified Ideograph in the Spanish CV.
> 
> Rather, there is some mix-up in the character selection internals.
> We had such strange "spurious" errors for other documents:
> 
>   # missing character: There is no ^^A in font [lmroman12-regular]
>   # and all the line down to ^^Z and beyond...
>   # XeTeX artifact? works with LuaTeX, explore:
>   export/doc/(|de/|es/|fr/)EmbeddedObjects_pdf4_systemF
> 
>   -- suspiciousTests
> 

I'd rather know, what is missing here. Scott and I have similar installations. 
If we would know the reason,
we could describe it also in suspiciousTests.

> >> Still, it is strange that this fails at your place but runs fine here and
> >> for Scott.
> 
> What is your version of moderncv.cls? Here it is
> 
> \ProvidesClass{moderncv}[2015/07/28 v2.0.0 modern curriculum vitae and letter 
> document class]
> 

It is the same here.

> Günter

Kornel

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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Guenter Milde]

On 2016-02-20, Kornel Benko wrote:
> Am Samstag, 20. Februar 2016 um 15:40:54, schrieb Guenter Milde 
> <mi...@users.sf.net>
>> On 2016-02-20, Kornel Benko wrote:
>> > Am Freitag, 19. Februar 2016 um 21:32:22, schrieb Guenter Milde 
>> > <mi...@users.sf.net>
>> >> On 2016-02-19, Kornel Benko wrote:
>> >> > Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr 
>> >> > <uwesto...@lyx.org>
>> >> >> commit ba28f504b5b674debe137b45301ced2edc5eeb33
>> >> >> Author: Uwe Stöhr <uwesto...@lyx.org>
>> >> >> Date:   Fri Feb 19 02:16:36 2016 +0100

>> >> >> Spanish modernCV.lyx: update the file and make it compilable

>> >> > This comment seems misleading. With pdflatex it was compilable also
>> >> > before this commit. Now 2 more testcases fail.

>> >> > 6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF 
>> >> > ..***Failed   61.93 sec
>> >> > 7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF 
>> >> > .***Failed   61.93 sec

>> >> Strange: It works here, both "per hand" and via ctest...

>> > I installed fonts-font-awesome, now the font is found. 

I can't see where font Awesome is loaded - the font selectiong GUI shows all
is set to "default". This seems to be some internal font setting of the
modernCV package (or its style options). Nothing to blame the document edits.

>> > But there are still missing glyphs.

>> Which? (You should be able to copy-paste from the "full log".)

> I suppose it is the glyph used for fax.  "\phone[fax]{+43(0)999 }"

> Output of xelatex (system font + tex font):
> Missing character: There is no  in font FontAwesome/OT!

> Output of lualatex (system font):
> Missing character: There is no 䫂 (U+4AC2) in font rm-lmr12!
> Output of lualatex (tex font):
> Missing character: There is no 䨢 (U+4A22) in font rm-lmr12!

There is no character starting with 4A.. in my Unicode list
@@@ The Unicode Standard 8.0.0
@@@+U80M150527.lst
Unicode 8.0.0 final names list.

Only the heading

@@  3400CJK Unified Ideographs Extension A  4DB5

I don't think there is a CJK Unified Ideograph in the Spanish CV.

Rather, there is some mix-up in the character selection internals.
We had such strange "spurious" errors for other documents:

  # missing character: There is no ^^A in font [lmroman12-regular]
  # and all the line down to ^^Z and beyond...
  # XeTeX artifact? works with LuaTeX, explore:
  export/doc/(|de/|es/|fr/)EmbeddedObjects_pdf4_systemF

  -- suspiciousTests


>> Still, it is strange that this fails at your place but runs fine here and
>> for Scott.

What is your version of moderncv.cls? Here it is

\ProvidesClass{moderncv}[2015/07/28 v2.0.0 modern curriculum vitae and letter 
document class]


Günter

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Samstag, 20. Februar 2016 um 15:40:54, schrieb Guenter Milde 
<mi...@users.sf.net>
> On 2016-02-20, Kornel Benko wrote:
> 
> > [-- Type: text/plain, Encoding: quoted-printable --]
> 
> > Am Freitag, 19. Februar 2016 um 21:32:22, schrieb Guenter Milde 
> > <mi...@users.sf.net>
> >> On 2016-02-19, Kornel Benko wrote:
> >> > Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr 
> >> > <uwesto...@lyx.org>
> >> >> commit ba28f504b5b674debe137b45301ced2edc5eeb33
> >> >> Author: Uwe Stöhr <uwesto...@lyx.org>
> >> >> Date:   Fri Feb 19 02:16:36 2016 +0100
> 
> >> >> Spanish modernCV.lyx: update the file and make it compilable
> 
> >> > This comment seems misleading. With pdflatex it was compilable also
> >> > before this commit. Now 2 more testcases fail.
> 
> >> > 6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF 
> >> > ..***Failed   61.93 sec
> >> > 7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF 
> >> > .***Failed   61.93 sec
> 
> >> Strange: It works here, both "per hand" and via ctest...
> 
> > I installed fonts-font-awesome, now the font is found. But there are still 
> > missing glyphs.
> 
> Which? (You should be able to copy-paste from the "full log".)

I suppose it is the glyph used for fax.  "\phone[fax]{+43(0)999 }"

Output of xelatex (system font + tex font):
Missing character: There is no  in font FontAwesome/OT!

Output of lualatex (system font):
Missing character: There is no 䫂 (U+4AC2) in font rm-lmr12!

Output of lualatex (tex font):
Missing character: There is no 䨢 (U+4A22) in font rm-lmr12!


> Still, it is strange that this fails at your place but runs fine here and
> for Scott.
> 
> Günter

Kornel

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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Guenter Milde]

On 2016-02-20, Kornel Benko wrote:

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

> Am Freitag, 19. Februar 2016 um 21:32:22, schrieb Guenter Milde 
> <mi...@users.sf.net>
>> On 2016-02-19, Kornel Benko wrote:
>> > Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr 
>> > <uwesto...@lyx.org>
>> >> commit ba28f504b5b674debe137b45301ced2edc5eeb33
>> >> Author: Uwe Stöhr <uwesto...@lyx.org>
>> >> Date:   Fri Feb 19 02:16:36 2016 +0100

>> >> Spanish modernCV.lyx: update the file and make it compilable

>> > This comment seems misleading. With pdflatex it was compilable also
>> > before this commit. Now 2 more testcases fail.

>> > 6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF 
>> > ..***Failed   61.93 sec
>> > 7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF 
>> > .***Failed   61.93 sec

>> Strange: It works here, both "per hand" and via ctest...

> I installed fonts-font-awesome, now the font is found. But there are still 
> missing glyphs.

Which? (You should be able to copy-paste from the "full log".)

Still, it is strange that this fails at your place but runs fine here and
for Scott.

Günter

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Uwe Stöhr]

Am 19.02.2016 um 10:44 schrieb Kornel Benko:


This comment seems misleading. With pdflatex it was compilable also before this 
commit.


It was only compilable with many hacks in the preamble. That file was 
not compilable in the current modernCV version because of a babel issue 
with Spanish. We found now a solution (the preamble line) and could 
update the file.



Now 2 more testcases fail.

6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF 
..***Failed   61.93 sec
7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF 
.***Failed   61.93 sec

I know, you don't care.


I still don't understand your goal. The user should be able to click on 
the view button and get a nice PDF. Ignacio assures this and as long as 
this works we can be happy.


The play with different export methods might be nice for experts while 
the average user don't care about how his PDF was internally created. I 
don't say that it is bad to play around but it is not important for the 
user, only for us to uncover possible bugs.
Nevertheless special text classes like e.g. the CVs are not designed to 
work with all engines nor to be translatable nor to work with babel 
and/polyglossia so I am wondering that our tests expect that.


regards Uwe

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Freitag, 19. Februar 2016 um 21:32:22, schrieb Guenter Milde 
<mi...@users.sf.net>
> On 2016-02-19, Kornel Benko wrote:
> > Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr 
> > <uwesto...@lyx.org>
> >> commit ba28f504b5b674debe137b45301ced2edc5eeb33
> >> Author: Uwe Stöhr <uwesto...@lyx.org>
> >> Date:   Fri Feb 19 02:16:36 2016 +0100
>
> >> Spanish modernCV.lyx: update the file and make it compilable
>
> > This comment seems misleading. With pdflatex it was compilable also
> > before this commit. Now 2 more testcases fail.
>
> > 6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF 
> > ..***Failed   61.93 sec
> > 7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF 
> > .***Failed   61.93 sec
>
> Strange: It works here, both "per hand" and via ctest...

I installed fonts-font-awesome, now the font is found. But there are still 
missing glyphs.

Attached the differing pdf snippet created with pdflatex (splash27, without 
error) and with xelatex (splash26).

Kornel

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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Scott Kostyshak]

On Fri, Feb 19, 2016 at 10:49:14PM +0100, Kornel Benko wrote:
> Am Freitag, 19. Februar 2016 um 21:32:22, schrieb Guenter Milde 
> <mi...@users.sf.net>
> > On 2016-02-19, Kornel Benko wrote:
> > > Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr 
> > > <uwesto...@lyx.org>
> > >> commit ba28f504b5b674debe137b45301ced2edc5eeb33
> > >> Author: Uwe Stöhr <uwesto...@lyx.org>
> > >> Date:   Fri Feb 19 02:16:36 2016 +0100
> > 
> > >> Spanish modernCV.lyx: update the file and make it compilable
> > 
> > > This comment seems misleading. With pdflatex it was compilable also
> > > before this commit. Now 2 more testcases fail.
> > 
> > > 6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF 
> > > ..***Failed   61.93 sec
> > > 7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF 
> > > .***Failed   61.93 sec
> > 
> > Strange: It works here, both "per hand" and via ctest...

All
ctest -R modernCV
tests pass here as well. So you are probably right that that we probably
have different fonts available.

Scott

> 
> You probably have the right font.
> I get:
> ...
> \listitemsymbolwidth=\skip75
> ! Font EU1/FontAwesome(0)/m/n/6=FontAwesome: at 6.0pt not loadable: Metric 
> (TFM
> ) file or installed font not found.
>  
>relax 
> l.46 ...dth{\listitemsymbolwidth}{\listitemsymbol}
>   
> I wasn't able to read the size data for this font,
> so I will ignore the font specification.
> [Wizards can fix TFM files using TFtoPL/PLtoTF.]
> You might try inserting a different font spec;
> e.g., type `I\font='.
> 
> Missing character: There is no  in font nullfont!
> \listitemcolumnwidth=\skip76
> ...
> > >> (a special preamble is necessary for Spanish)
> > >> Ignacio will translate it soon.
> > 
> > >> diff --git a/lib/examples/es/modernCV.lyx b/lib/examples/es/modernCV.lyx
> > 
> > Günter
> 
>   Kornel




signature.asc
Description: PGP signature

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Freitag, 19. Februar 2016 um 21:32:22, schrieb Guenter Milde 
<mi...@users.sf.net>
> On 2016-02-19, Kornel Benko wrote:
> > Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr 
> > <uwesto...@lyx.org>
> >> commit ba28f504b5b674debe137b45301ced2edc5eeb33
> >> Author: Uwe Stöhr <uwesto...@lyx.org>
> >> Date:   Fri Feb 19 02:16:36 2016 +0100
> 
> >> Spanish modernCV.lyx: update the file and make it compilable
> 
> > This comment seems misleading. With pdflatex it was compilable also
> > before this commit. Now 2 more testcases fail.
> 
> > 6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF 
> > ..***Failed   61.93 sec
> > 7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF 
> > .***Failed   61.93 sec
> 
> Strange: It works here, both "per hand" and via ctest...

You probably have the right font.
I get:
...
\listitemsymbolwidth=\skip75
! Font EU1/FontAwesome(0)/m/n/6=FontAwesome: at 6.0pt not loadable: Metric (TFM
) file or installed font not found.
 
   relax 
l.46 ...dth{\listitemsymbolwidth}{\listitemsymbol}
  
I wasn't able to read the size data for this font,
so I will ignore the font specification.
[Wizards can fix TFM files using TFtoPL/PLtoTF.]
You might try inserting a different font spec;
e.g., type `I\font='.

Missing character: There is no  in font nullfont!
\listitemcolumnwidth=\skip76
...
> >> (a special preamble is necessary for Spanish)
> >> Ignacio will translate it soon.
> 
> >> diff --git a/lib/examples/es/modernCV.lyx b/lib/examples/es/modernCV.lyx
> 
> Günter

Kornel

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

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Guenter Milde]

On 2016-02-19, Kornel Benko wrote:
> Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr 
> <uwesto...@lyx.org>
>> commit ba28f504b5b674debe137b45301ced2edc5eeb33
>> Author: Uwe Stöhr <uwesto...@lyx.org>
>> Date:   Fri Feb 19 02:16:36 2016 +0100

>> Spanish modernCV.lyx: update the file and make it compilable

> This comment seems misleading. With pdflatex it was compilable also
> before this commit. Now 2 more testcases fail.

> 6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF 
> ..***Failed   61.93 sec
> 7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF 
> .***Failed   61.93 sec

Strange: It works here, both "per hand" and via ctest...

>> (a special preamble is necessary for Spanish)
>> Ignacio will translate it soon.

>> diff --git a/lib/examples/es/modernCV.lyx b/lib/examples/es/modernCV.lyx

Günter

Re: [LyX/master] Spanish modernCV.lyx: update the file and make it compilable

[Kornel Benko]

Am Freitag, 19. Februar 2016 um 02:16:42, schrieb Uwe Stöhr <uwesto...@lyx.org>
> commit ba28f504b5b674debe137b45301ced2edc5eeb33
> Author: Uwe Stöhr <uwesto...@lyx.org>
> Date:   Fri Feb 19 02:16:36 2016 +0100
> 
> Spanish modernCV.lyx: update the file and make it compilable

This comment seems misleading. With pdflatex it was compilable also before this 
commit.
Now 2 more testcases fail.

6/7 Test #3357: EXAMPLES_export/examples/es/modernCV_pdf4_systemF 
..***Failed   61.93 sec
7/7 Test #3356: EXAMPLES_export/examples/es/modernCV_pdf4_texF 
.***Failed   61.93 sec

I know, you don't care.

> (a special preamble is necessary for Spanish)
> Ignacio will translate it soon.
> 
> diff --git a/lib/examples/es/modernCV.lyx b/lib/examples/es/modernCV.lyx

Kornel

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

Re: [PATCH] Re: Update boost in 2.1 branch?

[Scott Kostyshak]

On Thu, Jan 21, 2016 at 04:53:34PM -0500, Scott Kostyshak wrote:
> On Thu, Jan 21, 2016 at 04:40:56PM -0500, Richard Heck wrote:
> > On 01/21/2016 04:07 PM, Pavel Sanda wrote:
> > > Jean-Marc Lasgouttes wrote:
> > >> So is it a problem that compiling in C++11 mode is broken with gcc 4.6? 
> > >> I 
> > >> would guess not.
> > > I guess it also depends how much space for error we have...
> > > Richard, do you plan to release one intermediate 2.1.x or you just 
> > > waiting for the final one?
> > 
> > How far out do we realistically think 2.2.0 is? I am thinking end of
> > February, but if it gets delayed any further we might think about an
> > intermediate release.
> 
> I think end of February is realistic. Beta should be soon, just need
> Guillaume's set of patches to git a final review, and Georg also is
> trying to look into an issue that Stephan has reported. After beta I do
> not think developers are planning many non-trivial commits so whether we
> achieve end of February for a final release will depend on what issues
> our beta testers find and on how long it takes us to fix those issues.

Richard, I just wanted to give an update that I no longer think the end
of February is realistic for the final release. The good news is that
soon it will be possible to compile on Windows from the tar ball, which
is nice to have fixed. I think we will need to release a beta3 in order
to fix one more set of these issues. Then, I will do some advertising
of beta3 on various sites. I imagine we want at least a couple of weeks
of testing, and I also imagine we will need to fix some issues that are
revealed from that testing.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] New LFUN tabular-feature: update docs

[Georg Baum]

Jean-Marc Lasgouttes wrote:

> Le 09/02/2016 19:06, Scott Kostyshak a écrit :
>> diff --git a/lib/doc/LFUNs.lyx b/lib/doc/LFUNs.lyx
>> index ff4068a..fae083f 100644
>> --- a/lib/doc/LFUNs.lyx
>> +++ b/lib/doc/LFUNs.lyx
>> @@ -102,7 +102,7 @@ The \SpecialChar LyX
>>   \end_layout
>>
>>   \begin_layout Date
>> -2016-01-27
>> +2016-02-09
>>   \end_layout
>>
> 
> We should just get rid of the date and of the code that generates it.
> Nbody cares about that IMO. If devloppers want to know, git is their
> friend.

I think the date was important when updating the file was not part of the 
release procedure. Now that it is regenerated for each release I agree that 
it is not needed anymore.

Is the attached OK to go in?


Georgdiff --git a/development/tools/gen_lfuns.py b/development/tools/gen_lfuns.py
index 0fb9380..2c9c5ff 100755
--- a/development/tools/gen_lfuns.py
+++ b/development/tools/gen_lfuns.py
@@ -13,7 +13,6 @@
 # gen_lfuns.py  
 
 import sys,re,os.path
-from datetime import date
 
 def error(message):
 sys.stderr.write(message + '\n')
@@ -43,7 +42,7 @@ ID_DICT = dict(name=LFUN_NAME_ID, action=LFUN_ACTION_ID, notion=LFUN_NOTION_ID,
 syntax=LFUN_SYNTAX_ID, params=LFUN_PARAMS_ID, sample=LFUN_SAMPLE_ID, origin=LFUN_ORIGIN_ID)
 
 LFUNS_HEADER = """# gen_lfuns.py generated this file. For more info see http://www.lyx.org/
-\\lyxformat 504
+\\lyxformat 506
 \\begin_document
 \\begin_header
 \\save_transient_properties true
@@ -145,9 +144,6 @@ The \\SpecialChar LyX
  Team
 \\end_layout
 
-\\begin_layout Date""" + "\n" + str(date.today()) + """
-\\end_layout
-
 """
 
 LFUNS_INTRO ="""\\begin_layout Section*
diff --git a/lib/doc/LFUNs.lyx b/lib/doc/LFUNs.lyx
index ff4068a..9828cb2 100644
--- a/lib/doc/LFUNs.lyx
+++ b/lib/doc/LFUNs.lyx
@@ -101,10 +101,6 @@ The \SpecialChar LyX
  Team
 \end_layout
 
-\begin_layout Date
-2016-01-27
-\end_layout
-
 \begin_layout Section*
 About this manual
 \end_layout

Re: [LyX/master] New LFUN tabular-feature: update docs

[Scott Kostyshak]

On Thu, Feb 11, 2016 at 08:49:57PM +0100, Georg Baum wrote:
> Jean-Marc Lasgouttes wrote:
> 
> > Le 09/02/2016 19:06, Scott Kostyshak a écrit :
> >> diff --git a/lib/doc/LFUNs.lyx b/lib/doc/LFUNs.lyx
> >> index ff4068a..fae083f 100644
> >> --- a/lib/doc/LFUNs.lyx
> >> +++ b/lib/doc/LFUNs.lyx
> >> @@ -102,7 +102,7 @@ The \SpecialChar LyX
> >>   \end_layout
> >>
> >>   \begin_layout Date
> >> -2016-01-27
> >> +2016-02-09
> >>   \end_layout
> >>
> > 
> > We should just get rid of the date and of the code that generates it.
> > Nbody cares about that IMO. If devloppers want to know, git is their
> > friend.
> 
> I think the date was important when updating the file was not part of the 
> release procedure. Now that it is regenerated for each release I agree that 
> it is not needed anymore.
> 
> Is the attached OK to go in?

Yes, thanks.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] New LFUN tabular-feature: update docs

[Georg Baum]

Scott Kostyshak wrote:

> On Wed, Jan 27, 2016 at 06:53:04PM +0100, Guillaume Munch wrote:
>> commit 360742c515fcb74e6b8b5383f2e3002edb2d00cf
>> Author: Guillaume Munch <g...@lyx.org>
>> Date:   Wed Jan 27 18:35:10 2016 +0100
>> 
>> New LFUN tabular-feature: update docs
>> 
>> Simply run updatedocs.py
>> 
>> diff --git a/lib/doc/LFUNs.lyx b/lib/doc/LFUNs.lyx
>> index a529a0a..ff4068a 100644
>> --- a/lib/doc/LFUNs.lyx
>> +++ b/lib/doc/LFUNs.lyx
>> @@ -1,5 +1,5 @@
>> -# gen_lfuns.py generated this file. For more info see
>> http://www.lyx.org/ -\lyxformat 504
>> +#LyX 2.2 created this file. For more info see http://www.lyx.org/
>> +\lyxformat 506
> 
> (note: the comments below are more about 51d4036d than this commit but
> it is more convenient to discuss them here)
> 
> Is the above diff expected?

Yes, since gen_lfuns.py produces format 504. If it would produce the current 
format then this diff would not appear. What is missing here is a python 
library for producing .lyx files in current format which is part of lyx2lyx, 
so that scripts like gen_lfuns.py do not need to be adapted to ner versions.

> From what I understand, as of 51d4036d,
> updatedocs.py now handles LFUNs.lyx appropriately, which is nice. But do
> we want the header to say that "LyX 2.2 created this file" or do we still
> want to say that "gen_lfuns.py generated this file" ?

The latter.


Georg

Re: [LyX/master] New LFUN tabular-feature: update docs

[Scott Kostyshak]

On Thu, Feb 11, 2016 at 08:53:34PM +0100, Georg Baum wrote:
> Scott Kostyshak wrote:
> 
> > On Wed, Jan 27, 2016 at 06:53:04PM +0100, Guillaume Munch wrote:
> >> commit 360742c515fcb74e6b8b5383f2e3002edb2d00cf
> >> Author: Guillaume Munch <g...@lyx.org>
> >> Date:   Wed Jan 27 18:35:10 2016 +0100
> >> 
> >> New LFUN tabular-feature: update docs
> >> 
> >> Simply run updatedocs.py
> >> 
> >> diff --git a/lib/doc/LFUNs.lyx b/lib/doc/LFUNs.lyx
> >> index a529a0a..ff4068a 100644
> >> --- a/lib/doc/LFUNs.lyx
> >> +++ b/lib/doc/LFUNs.lyx
> >> @@ -1,5 +1,5 @@
> >> -# gen_lfuns.py generated this file. For more info see
> >> http://www.lyx.org/ -\lyxformat 504
> >> +#LyX 2.2 created this file. For more info see http://www.lyx.org/
> >> +\lyxformat 506
> > 
> > (note: the comments below are more about 51d4036d than this commit but
> > it is more convenient to discuss them here)
> > 
> > Is the above diff expected?
> 
> Yes, since gen_lfuns.py produces format 504. If it would produce the current 
> format then this diff would not appear. What is missing here is a python 
> library for producing .lyx files in current format which is part of lyx2lyx, 
> so that scripts like gen_lfuns.py do not need to be adapted to ner versions.

I see. I was more curious about the "LyX 2.2 created this file" addition, which
you address below.

> > From what I understand, as of 51d4036d,
> > updatedocs.py now handles LFUNs.lyx appropriately, which is nice. But do
> > we want the header to say that "LyX 2.2 created this file" or do we still
> > want to say that "gen_lfuns.py generated this file" ?
> 
> The latter.

OK, thanks.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Win installer: update language files

[Kornel Benko]

Am Donnerstag, 11. Februar 2016 um 23:29:55, schrieb Uwe Stöhr 

> diff --git a/development/Win32/packaging/installer/lang/slovak.nsh 
> b/development/Win32/packaging/installer/lang/slovak.nsh
> index 64a2879..abfef3e 100644
> --- a/development/Win32/packaging/installer/lang/slovak.nsh
> +++ b/development/Win32/packaging/installer/lang/slovak.nsh
> @@ -1,4 +1,3 @@
> -#-*-coding: windows-1250;-*-

May I ask, why did you remove this line? I need it on linux to edit with 
windows encoding.

Kornel

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

Re: [LyX/master] Win installer: update language files

[Uwe Stöhr]

Am 12.02.2016 um 01:03 schrieb Kornel Benko:


-#-*-coding: windows-1250;-*-


May I ask, why did you remove this line?


This should not happen. I reverted this now.

thanks and regards
Uwe

Re: [LyX/master] New LFUN tabular-feature: update docs

[Jean-Marc Lasgouttes]

Le 09/02/2016 19:06, Scott Kostyshak a écrit :

diff --git a/lib/doc/LFUNs.lyx b/lib/doc/LFUNs.lyx
index ff4068a..fae083f 100644
--- a/lib/doc/LFUNs.lyx
+++ b/lib/doc/LFUNs.lyx
@@ -102,7 +102,7 @@ The \SpecialChar LyX
  \end_layout

  \begin_layout Date
-2016-01-27
+2016-02-09
  \end_layout



We should just get rid of the date and of the code that generates it. 
Nbody cares about that IMO. If devloppers want to know, git is their friend.


JMarc

Re: [LyX/master] New LFUN tabular-feature: update docs

[Scott Kostyshak]

On Wed, Jan 27, 2016 at 06:53:04PM +0100, Guillaume Munch wrote:
> commit 360742c515fcb74e6b8b5383f2e3002edb2d00cf
> Author: Guillaume Munch <g...@lyx.org>
> Date:   Wed Jan 27 18:35:10 2016 +0100
> 
> New LFUN tabular-feature: update docs
> 
> Simply run updatedocs.py
> 
> diff --git a/lib/doc/LFUNs.lyx b/lib/doc/LFUNs.lyx
> index a529a0a..ff4068a 100644
> --- a/lib/doc/LFUNs.lyx
> +++ b/lib/doc/LFUNs.lyx
> @@ -1,5 +1,5 @@
> -# gen_lfuns.py generated this file. For more info see http://www.lyx.org/
> -\lyxformat 504
> +#LyX 2.2 created this file. For more info see http://www.lyx.org/
> +\lyxformat 506

(note: the comments below are more about 51d4036d than this commit but
it is more convenient to discuss them here)

Is the above diff expected? From what I understand, as of 51d4036d,
updatedocs.py now handles LFUNs.lyx appropriately, which is nice. But do we
want the header to say that "LyX 2.2 created this file" or do we still want to
say that "gen_lfuns.py generated this file" ?

>  \begin_document
>  \begin_header
>  \save_transient_properties true
> @@ -102,7 +102,7 @@ The \SpecialChar LyX
>  \end_layout
>  
>  \begin_layout Date
> -2016-01-15
> +2016-01-27

The above diff happens for me (and changes the date to the current date
today) even if a format change did not occur. Specifically, I get the
following diff if I run updatedocs.py:

diff --git a/lib/doc/LFUNs.lyx b/lib/doc/LFUNs.lyx
index ff4068a..fae083f 100644
--- a/lib/doc/LFUNs.lyx
+++ b/lib/doc/LFUNs.lyx
@@ -102,7 +102,7 @@ The \SpecialChar LyX
 \end_layout
 
 \begin_layout Date
-2016-01-27
+2016-02-09
 \end_layout
 
 \begin_layout Section*

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] acmsiggraph.layout: update layout for ACM siggraph 0.92

[Georg Baum]

Uwe Stöhr wrote:

> Am 29.01.2016 um 22:32 schrieb Georg Baum:
> 
>> Does anybody give a +1 subsequently for the ACM layout update? If yes, we
>> should update the version numbers of the tex2lyx tests. If not, I propose
>> that Uwe reverts the layout file changes and makes the 504-505 step an
>> empty conversion.
> 
> Why? So we want to ship a layout for ACM that nobody can use?
> OK, but then we should remove support for the ACM classes in general.

I did deliberately not mention the contents of the patch itself in this 
thread, please put it aside for a moment.

The problem I was discussing is a process problem: We all agreed that Scott 
is the release manager for 2.2.0. We also agreed that he has the power to 
set the commit rules until the release is out. The current rule is that any 
non-trivial change needs a +1 by another developer (the only exception being 
documentation and translations). If you do not agree with this rule, then 
you need to persuade Scott to change it, but until that is done the rule 
needs to be followed.

We cannot require Guillaume to go through a review process until he has a +1 
for each part of his patch, and let you put something in without having a 
+1. If we would allow this, then this would cause a lot of frustration.


Georg

Re: Final round: Request to update docs for LyX 2.2.0

[Koji Yokota]

Hi Uwe,

I attach the screenshot to this mail. It seems there is no corresponding
strings included in .nsh files.

Best regards,

Koji

On 2016年01月28日 08:26, Uwe Stöhr wrote:
> Am 27.01.2016 um 09:29 schrieb Koji Yokota:
>
>> I browsed the Windows installer for 2.2 alpha a little bit and found the
>> pane titled "Choose Users" is not translated yet.
>
> Hi Koji,
>
> I cannot find this. Could you please send me a screenshot?
>
> You find the translations for the installer in this Git folder:
> ~/development/Win32/packaging/installer/lang
>
> (
> http://www.lyx.org/trac/browser/lyxgit/development/Win32/packaging/installer/lang
> )
>
> There is one untranslated message. it would be nice if you could
> translate it. Please note that you must use the encoding "Shift_JIS"
> to edit the file japanese.nsh.
> (The required encodings are listed in the file Encodings.txt.)
>
> many thanks and best regards
> Uwe

Re: [PATCH] Re: Update boost in 2.1 branch?

[Jean-Marc Lasgouttes]

Le 25/01/2016 20:55, Georg Baum a écrit :

Jean-Marc Lasgouttes wrote:


Le 21/01/2016 15:42, Jean-Marc Lasgouttes a écrit :


Sigh. Now that I can test it with an older compiler (gcc 4.6, Ubuntu
12.04) I find that it does not compile in C++98 mode because of
boost::next/prior. This has been fixed already in master, so I
cherry-picked the commits (see attached).


So what shall I do with this patch? In my view it improves the
situation. The only reason for not pushing it would be if we revert the
boost update patch.


I did not reply since the original code is from me, so I am obviously
biased, but IMO this would be safe enough to apply.


Richard?
JMarc

Re: [LyX/master] acmsiggraph.layout: update layout for ACM siggraph 0.92

[Uwe Stöhr]

Am 29.01.2016 um 22:32 schrieb Georg Baum:


So what are we going to do now?

The tex2lyx tests are currently failing because of wrong versions (I guess
because Guillaume did resolve them with git and did not regenerate them
after merging his patches with the ACM layout update).


I don't understand all the discussion here. As I understand it:

- ACM did not work so I was fixing it.
- I did not change any source code so why should tex2lyx fail now?
- For me it does not fail. I checked this as described in our 
Develoment.lyx file. (MSVC did report any tex2lyx test errors when they 
were executed.)


So what is the problem? What is not working for you, can you please send 
a LyX example file to test?



Does anybody give a +1 subsequently for the ACM layout update? If yes, we
should update the version numbers of the tex2lyx tests. If not, I propose
that Uwe reverts the layout file changes and makes the 504-505 step an empty
conversion.


Why? So we want to ship a layout for ACM that nobody can use?
OK, but then we should remove support for the ACM classes in general.

regards Uwe

Re: [LyX/master] acmsiggraph.layout: update layout for ACM siggraph 0.92

[Uwe Stöhr]

Am 30.01.2016 um 02:11 schrieb Uwe Stöhr:


I propose
that Uwe reverts the layout file changes and makes the 504-505 step an
empty
conversion.


Why? So we want to ship a layout for ACM that nobody can use?


So in fact you are proposing to revert a valid fix the re-enable a 
feature of LyX.
Your tex2lyx tests might fail but they are not checking the reality. The 
reality is if TeX files can be imported to LyX _and_ if the result can 
be compiled. That and not more is what the user expects.
Since only a layout file for a certain document class was changed by me, 
it is not possible that tex2lyx gets broken for other files.


I now re-run the tex2lyx tests and it tells me that ALL tests fail. In 
fact this is wrong because Guillaume only forgot to update the 
fileformat of the tex2lyx test files.
Since tex2lyx itself works fine I doubt that the tex2lyx tests are that 
useful as they are. Why can't it handle that the fileformat was changed? 
I mean in version.h we stored the fileformat that tex2lyx can handle. So 
if the tex2lyx test is run, why are the testfiles not automatically 
updated to the new fileformat?


And for the tests I still miss the key feature that the resulting 
imported LyX files are compiled to PDF. Because what does it help the 
user that he gets a LyX file that he cannot compile. As long as he is no 
LaTeX expert it will then be very hard if not impossible to find out why 
it does not compile.


However, I won't discuss this again and again. As I promised I won't 
touch tex2lyx any more. however, please don't claim commit reversions 
only because of failing tex2lyx tests before it is clear that there is a 
real problem.


regards Uwe

Re: [LyX/master] acmsiggraph.layout: update layout for ACM siggraph 0.92

[Scott Kostyshak]

On Fri, Jan 29, 2016 at 10:32:23PM +0100, Georg Baum wrote:
> Scott Kostyshak wrote:
> 
> > On Wed, Jan 27, 2016 at 08:11:09AM +0100, Guillaume Munch wrote:
> >> 
> >> Am I mistaken or nobody gave Uwe the +1 to do this format increment?
> > 
> > As discussed in the other thread, you are correct.
> 
> So what are we going to do now?
> 
> The tex2lyx tests are currently failing because of wrong versions (I guess 
> because Guillaume did resolve them with git and did not regenerate them 
> after merging his patches with the ACM layout update).
> 
> Does anybody give a +1 subsequently for the ACM layout update? If yes, we 
> should update the version numbers of the tex2lyx tests. If not, I propose 
> that Uwe reverts the layout file changes and makes the 504-505 step an empty 
> conversion.

I agree. Unfortunately, our layout and lyx2lyx experts do not have much
time. Richard or Jürgen, do you have time to review the patch/commit?

> If we do none of the two options then I do not know what our rules are good 
> for.

Indeed.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] acmsiggraph.layout: update layout for ACM siggraph 0.92

[Georg Baum]

Scott Kostyshak wrote:

> On Wed, Jan 27, 2016 at 08:11:09AM +0100, Guillaume Munch wrote:
>> 
>> Am I mistaken or nobody gave Uwe the +1 to do this format increment?
> 
> As discussed in the other thread, you are correct.

So what are we going to do now?

The tex2lyx tests are currently failing because of wrong versions (I guess 
because Guillaume did resolve them with git and did not regenerate them 
after merging his patches with the ACM layout update).

Does anybody give a +1 subsequently for the ACM layout update? If yes, we 
should update the version numbers of the tex2lyx tests. If not, I propose 
that Uwe reverts the layout file changes and makes the 504-505 step an empty 
conversion.

If we do none of the two options then I do not know what our rules are good 
for.


Georg

Re: Final round: Request to update docs for LyX 2.2.0

[Uwe Stöhr]

Am 27.01.2016 um 09:29 schrieb Koji Yokota:


I browsed the Windows installer for 2.2 alpha a little bit and found the
pane titled "Choose Users" is not translated yet.


Hi Koji,

I cannot find this. Could you please send me a screenshot?

You find the translations for the installer in this Git folder:
~/development/Win32/packaging/installer/lang

( 
http://www.lyx.org/trac/browser/lyxgit/development/Win32/packaging/installer/lang 
)


There is one untranslated message. it would be nice if you could 
translate it. Please note that you must use the encoding "Shift_JIS" to 
edit the file japanese.nsh.

(The required encodings are listed in the file Encodings.txt.)

many thanks and best regards
Uwe

Re: [LyX/master] acmsiggraph.layout: update layout for ACM siggraph 0.92

[Scott Kostyshak]

On Wed, Jan 27, 2016 at 08:11:09AM +0100, Guillaume Munch wrote:
> Le 27/01/2016 01:58, Uwe Stöhr a écrit :
> >commit c1e0b24304e67ede19f30c2ee7498386bfcf6808
> >Author: Uwe Stöhr <uwesto...@lyx.org>
> >Date:   Wed Jan 27 01:58:13 2016 +0100
> >
> > acmsiggraph.layout: update layout for ACM siggraph 0.92
> >
> > fileformat change: update fileformat for all files
> >
> >diff --git a/development/FORMAT b/development/FORMAT
> >index cbd5064..0c8a98c 100644
> >--- a/development/FORMAT
> >+++ b/development/FORMAT
> >@@ -11,6 +11,11 @@ adjustments are made to tex2lyx and bugs are fixed in 
> >lyx2lyx.
> >
> >  ---
> >
> >+2016-01-26 Uwe Stöhr <uwesto...@web.de>
> >+* Format incremented to 505
> >+  No new parameters.
> >+  Convert acmsiggraph.layout to ACM siggraph version 0.92.
> >+
> 
> 
> Am I mistaken or nobody gave Uwe the +1 to do this format increment?

As discussed in the other thread, you are correct.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] acmsiggraph.layout: update layout for ACM siggraph 0.92

[Guillaume Munch]

Le 27/01/2016 01:58, Uwe Stöhr a écrit :

@@ -2239,10 +2343,12 @@ convert = [
 [501, [convert_fontsettings]],
 [502, []],
 [503, []],
-   [504, [convert_save_props]]
+   [504, [convert_save_props]],
+   [505, [convert_ACM_siggraph]]
]

  revert =  [
+   [504, [revert_save_props]],
 [503, [revert_save_props]],
 [502, [revert_verbatim_star]],
 [501, [revert_solution]],



Uwe, I am worried about this duplicate application of revert_save_props.

Please, apply the doc updates in a separate commit because they prevent
us from reading the commit log and spotting such errors.

Re: [LyX/master] acmsiggraph.layout: update layout for ACM siggraph 0.92

[Uwe Stöhr]

Am 27.01.2016 um 18:49 schrieb Guillaume Munch:


Uwe, I am worried about this duplicate application of revert_save_props.


Thanks, I fixed this now.


Please, apply the doc updates in a separate commit because they prevent
us from reading the commit log and spotting such errors.


OK.

regards Uwe

Re: [LyX/master] acmsiggraph.layout: update layout for ACM siggraph 0.92

[Uwe Stöhr]

Am 27.01.2016 um 08:11 schrieb Guillaume Munch:


Am I mistaken or nobody gave Uwe the +1 to do this format increment?


Scott reported it worked for him and I interpreted it ;-)


Yesterday I had updated my series of patches on tabular-feature from
format 504 to 505, going again carefully through the checklist, updating
and checking docs, doing the careful compilation tests patch-by-patch,
as well as a final test of the features. I had announced on the list
that I was going to commit the patches.


I mane a simple fileformat change without touching the source code. So 
why was it such a problem for you? Isn't it just to update the 
fileformat number and then run the 2 scripts to update the docs and the 
tex2lyx files? (Takes here 5 minutes.)


I am nevertheless sorry that I disturbed your work. This was not my 
plan. I was simply not following the thread of your patch.
Nevertheless it should not be that one cannot commit things because 
others plan certain work.


regards Uwe

Re: [LyX/master] acmsiggraph.layout: update layout for ACM siggraph 0.92

[Guillaume Munch]

Le 27/01/2016 01:58, Uwe Stöhr a écrit :

commit c1e0b24304e67ede19f30c2ee7498386bfcf6808
Author: Uwe Stöhr <uwesto...@lyx.org>
Date:   Wed Jan 27 01:58:13 2016 +0100

 acmsiggraph.layout: update layout for ACM siggraph 0.92

 fileformat change: update fileformat for all files

diff --git a/development/FORMAT b/development/FORMAT
index cbd5064..0c8a98c 100644
--- a/development/FORMAT
+++ b/development/FORMAT
@@ -11,6 +11,11 @@ adjustments are made to tex2lyx and bugs are fixed in 
lyx2lyx.

  ---

+2016-01-26 Uwe Stöhr <uwesto...@web.de>
+   * Format incremented to 505
+ No new parameters.
+ Convert acmsiggraph.layout to ACM siggraph version 0.92.
+



Am I mistaken or nobody gave Uwe the +1 to do this format increment?

Yesterday I had updated my series of patches on tabular-feature from
format 504 to 505, going again carefully through the checklist, updating
and checking docs, doing the careful compilation tests patch-by-patch,
as well as a final test of the features. I had announced on the list
that I was going to commit the patches. And right when everything is
ready and I am ready to push, I see that someone has made a ninja format
increase, leaving me with no choice but to start again! Then I decided
that it was better not to react on the spot and call it an evening.

If somebody reverts the unauthorized commit, I will be able to push
mines without further delay. Otherwise I will honestly have to look at
my schedule before I will be able to tell you when is the next time I
will be available to work on the patches.

Re: [PATCH] Re: Update boost in 2.1 branch?

[Georg Baum]

Jean-Marc Lasgouttes wrote:

> Le 25/01/2016 10:58, Kornel Benko a écrit :
>> Am Montag, 25. Januar 2016 um 10:43:15, schrieb Jean-Marc Lasgouttes
>> 
>>> Le 22/01/2016 17:15, Kornel Benko a écrit :
>> Even with this patch, I could not compile src/support/ForkedCalls.cpp
>> with gcc-4.8.4.
>
> This is in C++11 mode, right?

 Yes, it is set by checking if the compiler is able to use this mode.
>>>
>>> With autotools we let C++11 mode be disabled by default in 2.1 (and
>>> enabled by default in 2.2).
>>>
 I tried, and now it compiles.
 So what is the preferred solution?
 A.) Disable c++11 mode
 B.) Not set  LYX_USE_TR1
>>>
>>> I think TR1 should be limited to C++11 mode.
>>
>> But that is exactly the combination where the compilation fails.
> 
> Yes, but we do not really care about C++11 mode in 2.1, it is only for
> adventurous people. And it works for some compiler versions, in my
> testing.

In that case I would document the problem in NEWS and then forget about it.


Georg

Re: [PATCH] Re: Update boost in 2.1 branch?

[Georg Baum]

Jean-Marc Lasgouttes wrote:

> Le 21/01/2016 15:42, Jean-Marc Lasgouttes a écrit :
>>
>> Sigh. Now that I can test it with an older compiler (gcc 4.6, Ubuntu
>> 12.04) I find that it does not compile in C++98 mode because of
>> boost::next/prior. This has been fixed already in master, so I
>> cherry-picked the commits (see attached).
> 
> So what shall I do with this patch? In my view it improves the
> situation. The only reason for not pushing it would be if we revert the
> boost update patch.

I did not reply since the original code is from me, so I am obviously 
biased, but IMO this would be safe enough to apply.


Georg

Re: [PATCH] Re: Update boost in 2.1 branch?

[Jean-Marc Lasgouttes]

Le 22/01/2016 22:55, Georg Baum a écrit :

C++11 does not matter for 2.1 IMHO. Compilers will support C++98 much longer
than 2.1 will be relevant, and even if that means to enable it by special
command line options users can pass them to configure.


I guess the TR1 support is finally biting us back. We could let the code
in, but remove the #define LYX_USE_TR1 in conifg.h.


I would rather not touch it for gcc. Can we remove it just for clang?


We would have to have a check for libc++ in configure since the 
detection requires loading a STL header file.  Checking for clang is not 
enough since by default it uses libstdc++ with gcc.


We could also decide to use TR1 only in C++11 mode, since these are 
std:: constructs that we want there after all.


JMarc

Re: [PATCH] Re: Update boost in 2.1 branch?

[Jean-Marc Lasgouttes]

Le 22/01/2016 17:15, Kornel Benko a écrit :

Even with this patch, I could not compile src/support/ForkedCalls.cpp with 
gcc-4.8.4.


This is in C++11 mode, right?


Yes, it is set by checking if the compiler is able to use this mode.


With autotools we let C++11 mode be disabled by default in 2.1 (and 
enabled by default in 2.2).



I tried, and now it compiles.
So what is the preferred solution?
A.) Disable c++11 mode
B.) Not set  LYX_USE_TR1


I think TR1 should be limited to C++11 mode.

JMarc

Re: [PATCH] Re: Update boost in 2.1 branch?

[Kornel Benko]

Am Montag, 25. Januar 2016 um 10:43:15, schrieb Jean-Marc Lasgouttes 

> Le 22/01/2016 17:15, Kornel Benko a écrit :
> >>> Even with this patch, I could not compile src/support/ForkedCalls.cpp 
> >>> with gcc-4.8.4.
> >>
> >> This is in C++11 mode, right?
> >
> > Yes, it is set by checking if the compiler is able to use this mode.
> 
> With autotools we let C++11 mode be disabled by default in 2.1 (and 
> enabled by default in 2.2).
> 
> > I tried, and now it compiles.
> > So what is the preferred solution?
> > A.) Disable c++11 mode
> > B.) Not set  LYX_USE_TR1
> 
> I think TR1 should be limited to C++11 mode.

But that is exactly the combination where the compilation fails.

> JMarc

Kornel

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

Re: [PATCH] Re: Update boost in 2.1 branch?

[Jean-Marc Lasgouttes]

Le 21/01/2016 15:42, Jean-Marc Lasgouttes a écrit :

Le 14/01/2016 19:12, Jean-Marc Lasgouttes a écrit :

Le 09/01/2016 00:50, Richard Heck a écrit :

On 01/08/2016 05:06 AM, Jean-Marc Lasgouttes wrote:


Currently we use boost 1.53 in 2.1 branch. Would it be a good move to
update it to 1.60? I am getting loads of warnings with gcc 5.1.


Fine with me, and I see the same warnings.


OK, I pushed it.


Sigh. Now that I can test it with an older compiler (gcc 4.6, Ubuntu
12.04) I find that it does not compile in C++98 mode because of
boost::next/prior. This has been fixed already in master, so I
cherry-picked the commits (see attached).


So what shall I do with this patch? In my view it improves the 
situation. The only reason for not pushing it would be if we revert the 
boost update patch.


JMarc

Re: [PATCH] Re: Update boost in 2.1 branch?

[Jean-Marc Lasgouttes]

Le 25/01/2016 10:58, Kornel Benko a écrit :

Am Montag, 25. Januar 2016 um 10:43:15, schrieb Jean-Marc Lasgouttes 


Le 22/01/2016 17:15, Kornel Benko a écrit :

Even with this patch, I could not compile src/support/ForkedCalls.cpp with 
gcc-4.8.4.


This is in C++11 mode, right?


Yes, it is set by checking if the compiler is able to use this mode.


With autotools we let C++11 mode be disabled by default in 2.1 (and
enabled by default in 2.2).


I tried, and now it compiles.
So what is the preferred solution?
A.) Disable c++11 mode
B.) Not set  LYX_USE_TR1


I think TR1 should be limited to C++11 mode.


But that is exactly the combination where the compilation fails.


Yes, but we do not really care about C++11 mode in 2.1, it is only for 
adventurous people. And it works for some compiler versions, in my testing.


JMarc

Re: [PATCH] Re: Update boost in 2.1 branch?

[Kornel Benko]

Am Freitag, 22. Januar 2016 um 11:27:02, schrieb Jean-Marc Lasgouttes 

> Le 21/01/2016 22:40, Richard Heck a écrit :
> > On 01/21/2016 04:07 PM, Pavel Sanda wrote:
> >> I guess it also depends how much space for error we have...
> >> Richard, do you plan to release one intermediate 2.1.x or you just waiting 
> >> for the final one?
> >
> > How far out do we realistically think 2.2.0 is? I am thinking end of
> > February, but if it gets delayed any further we might think about an
> > intermediate release.
> >
> > Really, I should have done 2.1.5 back at the end of November, but I
> > thought 2.2 was closer.
> 
> One solution would be to have a 2.1.5 together with 2.2beta with an 
> updated lyx2lyx that reads 2.2beta format. A good occasion to make 
> people exercise this code.
> 
> And then 2.1.6 would just be the usual final version.
> 
> JMarc

Even with this patch, I could not compile src/support/ForkedCalls.cpp with 
gcc-4.8.4.
...
cd /usr/BUILD/BuildLyx2.1Git/src/support && /usr/bin/c++   
-DLYX_CALLSTACK_PRINTING -DQT_CORE_LIB -I/usr/BUILD/BuildLyx2.1Git 
-I/usr/src/lyx/lyx-2.0.x-git/src -I/usr/include/enchant 
-I/usr/src/lyx/lyx-2.0.x-git/boost -I/usr/src/lyx/lyx-2.0.x-git/src/support 
-I/usr/BUILD/BuildLyx2.1Git/src/support 
-I/usr/src/lyx/lyx-2.0.x-git/src/support/mythes -isystem 
/usr/BUILD/BuildQt5/5.5/gcc_64/include -isystem 
/usr/BUILD/BuildQt5/5.5/gcc_64/include/QtCore -isystem 
/usr/BUILD/BuildQt5/5.5/gcc_64/./mkspecs/linux-g++  -Wall -Wunused-parameter 
--std=gnu++11 -fno-strict-aliasing  -Wall -Wunused-parameter --std=gnu++11 
-fno-strict-aliasing -O0 -g3 -D_DEBUG   -DBOOST_USER_CONFIG="" -fPIC 
-o CMakeFiles/support.dir/ForkedCalls.cpp.o -c 
/usr/src/lyx/lyx-2.0.x-git/src/support/ForkedCalls.cpp
In file included from /usr/src/lyx/lyx-2.0.x-git/src/support/ForkedCalls.h:19:0,
 from /usr/src/lyx/lyx-2.0.x-git/src/support/ForkedCalls.cpp:17:
/usr/src/lyx/lyx-2.0.x-git/boost/boost/signal.hpp:17:4: warning: #warning 
"Boost.Signals is no longer being maintained and is now deprecated. Please 
switch to Boost.Signals2. To disable this warning message, define 
BOOST_SIGNALS_NO_DEPRECATION_WARNING." [-Wcpp]
 #  warning  "Boost.Signals is no longer being maintained and 
is now deprecated. Please switch to Boost.Signals2. To disable this warning 
message, define BOOST_SIGNALS_NO_DEPRECATION_WARNING."
^
In file included from 
/usr/src/lyx/lyx-2.0.x-git/boost/boost/function/detail/maybe_include.hpp:23:0,
 from 
/usr/src/lyx/lyx-2.0.x-git/boost/boost/function/function2.hpp:11,
 from 
/usr/src/lyx/lyx-2.0.x-git/boost/boost/signals/detail/named_slot_map.hpp:17,
 from 
/usr/src/lyx/lyx-2.0.x-git/boost/boost/signals/detail/signal_base.hpp:15,
 from 
/usr/src/lyx/lyx-2.0.x-git/boost/boost/signals/signal_template.hpp:22,
 from 
/usr/src/lyx/lyx-2.0.x-git/boost/boost/signals/signal0.hpp:24,
 from /usr/src/lyx/lyx-2.0.x-git/boost/boost/signal.hpp:27,
 from /usr/src/lyx/lyx-2.0.x-git/src/support/ForkedCalls.h:19,
 from /usr/src/lyx/lyx-2.0.x-git/src/support/ForkedCalls.cpp:17:
/usr/src/lyx/lyx-2.0.x-git/boost/boost/function/function_template.hpp: In 
instantiation of ‘static void 
boost::detail::function::void_function_obj_invoker2::invoke(boost::detail::function::function_buffer&, T0, T1) [with 
FunctionObj = std::tr1::_Bind, 
std::tr1::_Placeholder<2>))(int, int)>; R = void; T0 = int; T1 = int]’:
/usr/src/lyx/lyx-2.0.x-git/boost/boost/function/function_template.hpp:937:38:   
required from ‘void boost::function2::assign_to(Functor) [with 
Functor = std::tr1::_Bind, 
std::tr1::_Placeholder<2>))(int, int)>; R = void; T0 = int; T1 = int]’
/usr/src/lyx/lyx-2.0.x-git/boost/boost/function/function_template.hpp:727:7:   
required from ‘boost::function2::function2(Functor, typename 
boost::enable_if_c<(! boost::is_integral::value), int>::type) [with 
Functor = std::tr1::_Bind, 
std::tr1::_Placeholder<2>))(int, int)>; R = void; T0 = int; T1 = int; typename 
boost::enable_if_c<(! boost::is_integral::value), int>::type = int]’
/usr/src/lyx/lyx-2.0.x-git/boost/boost/function/function_template.hpp:1073:16:  
 required from ‘boost::function::function(Functor, typename 
boost::enable_if_c<(! boost::is_integral::value), int>::type) [with 
Functor = std::tr1::_Bind, 
std::tr1::_Placeholder<2>))(int, int)>; R = void; T0 = int; T1 = int; typename 
boost::enable_if_c<(! boost::is_integral::value), int>::type = int]’
/usr/src/lyx/lyx-2.0.x-git/boost/boost/signals/slot.hpp:111:122:   required 
from ‘boost::slot::slot(const F&) [with F = std::tr1::_Bind, std::tr1::_Placeholder<2>))(int, int)>; 
SlotFunction = boost::function]’
/usr/src/lyx/lyx-2.0.x-git/src/support/ForkedCalls.cpp:562:67:   required from 
here

Re: [PATCH] Re: Update boost in 2.1 branch?

[Georg Baum]

Jean-Marc Lasgouttes wrote:

> This is in C++11 mode, right? By default (c++98) it should just work
> IMO. I do not think that we have firm plans of making lyx 2.1 compile in
> C++11 mode.

C++11 does not matter for 2.1 IMHO. Compilers will support C++98 much longer 
than 2.1 will be relevant, and even if that means to enable it by special 
command line options users can pass them to configure.

> I guess the TR1 support is finally biting us back. We could let the code
> in, but remove the #define LYX_USE_TR1 in conifg.h.

I would rather not touch it for gcc. Can we remove it just for clang?


Georg

Re: [PATCH] Re: Update boost in 2.1 branch?

[Jean-Marc Lasgouttes]

Le 21/01/2016 22:40, Richard Heck a écrit :

On 01/21/2016 04:07 PM, Pavel Sanda wrote:

I guess it also depends how much space for error we have...
Richard, do you plan to release one intermediate 2.1.x or you just waiting for 
the final one?


How far out do we realistically think 2.2.0 is? I am thinking end of
February, but if it gets delayed any further we might think about an
intermediate release.

Really, I should have done 2.1.5 back at the end of November, but I
thought 2.2 was closer.


One solution would be to have a 2.1.5 together with 2.2beta with an 
updated lyx2lyx that reads 2.2beta format. A good occasion to make 
people exercise this code.


And then 2.1.6 would just be the usual final version.

JMarc

Re: [PATCH] Re: Update boost in 2.1 branch?

[Jean-Marc Lasgouttes]

Le 22/01/2016 16:15, Kornel Benko a écrit :

Am Freitag, 22. Januar 2016 um 11:27:02, schrieb Jean-Marc Lasgouttes 


Le 21/01/2016 22:40, Richard Heck a écrit :

On 01/21/2016 04:07 PM, Pavel Sanda wrote:

I guess it also depends how much space for error we have...
Richard, do you plan to release one intermediate 2.1.x or you just waiting for 
the final one?


How far out do we realistically think 2.2.0 is? I am thinking end of
February, but if it gets delayed any further we might think about an
intermediate release.

Really, I should have done 2.1.5 back at the end of November, but I
thought 2.2 was closer.


One solution would be to have a 2.1.5 together with 2.2beta with an
updated lyx2lyx that reads 2.2beta format. A good occasion to make
people exercise this code.

And then 2.1.6 would just be the usual final version.

JMarc


Even with this patch, I could not compile src/support/ForkedCalls.cpp with 
gcc-4.8.4.


This is in C++11 mode, right? By default (c++98) it should just work 
IMO. I do not think that we have firm plans of making lyx 2.1 compile in 
C++11 mode.


I guess the TR1 support is finally biting us back. We could let the code 
in, but remove the #define LYX_USE_TR1 in conifg.h.


JMarc

Re: [PATCH] Re: Update boost in 2.1 branch?

[Kornel Benko]

Am Freitag, 22. Januar 2016 um 17:01:11, schrieb Jean-Marc Lasgouttes 

> Le 22/01/2016 16:15, Kornel Benko a écrit :
> > Am Freitag, 22. Januar 2016 um 11:27:02, schrieb Jean-Marc Lasgouttes 
> > 
> >> Le 21/01/2016 22:40, Richard Heck a écrit :
> >>> On 01/21/2016 04:07 PM, Pavel Sanda wrote:
>  I guess it also depends how much space for error we have...
>  Richard, do you plan to release one intermediate 2.1.x or you just 
>  waiting for the final one?
> >>>
> >>> How far out do we realistically think 2.2.0 is? I am thinking end of
> >>> February, but if it gets delayed any further we might think about an
> >>> intermediate release.
> >>>
> >>> Really, I should have done 2.1.5 back at the end of November, but I
> >>> thought 2.2 was closer.
> >>
> >> One solution would be to have a 2.1.5 together with 2.2beta with an
> >> updated lyx2lyx that reads 2.2beta format. A good occasion to make
> >> people exercise this code.
> >>
> >> And then 2.1.6 would just be the usual final version.
> >>
> >> JMarc
> >
> > Even with this patch, I could not compile src/support/ForkedCalls.cpp with 
> > gcc-4.8.4.
> 
> This is in C++11 mode, right?

Yes, it is set by checking if the compiler is able to use this mode.

> By default (c++98) it should just work 
> IMO. I do not think that we have firm plans of making lyx 2.1 compile in 
> C++11 mode.

Should we disable it?

> I guess the TR1 support is finally biting us back. We could let the code 
> in, but remove the #define LYX_USE_TR1 in conifg.h.
This setting depends ATM on gnu-cxx version >= 4.4

I tried, and now it compiles.
So what is the preferred solution?
A.) Disable c++11 mode
B.) Not set  LYX_USE_TR1

> JMarc

Kornel


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

[PATCH] Re: Update boost in 2.1 branch?

[Jean-Marc Lasgouttes]

Le 14/01/2016 19:12, Jean-Marc Lasgouttes a écrit :

Le 09/01/2016 00:50, Richard Heck a écrit :

On 01/08/2016 05:06 AM, Jean-Marc Lasgouttes wrote:


Currently we use boost 1.53 in 2.1 branch. Would it be a good move to
update it to 1.60? I am getting loads of warnings with gcc 5.1.


Fine with me, and I see the same warnings.


OK, I pushed it.


Sigh. Now that I can test it with an older compiler (gcc 4.6, Ubuntu 
12.04) I find that it does not compile in C++98 mode because of 
boost::next/prior. This has been fixed already in master, so I 
cherry-picked the commits (see attached).


Yet, if I compile in C++11 mode I have issues with some tr1 code in 
ForkedCalls.cpp. We could cherry pick the code that removes tr1 support, 
but this is getting a bit too much for my taste.


My analysis is that updating our local boost library makes sense because 
at least Linux distribution want to compile with installed boost, and 
this may be a new one. We want the final 2.1 version to compile as long 
as possible.


So is it a problem that compiling in C++11 mode is broken with gcc 4.6? 
I would guess not.


So with the patch the Linux summary is as below. I tried to compile 
with/without c++11 and with/without included boost


gcc 4.6: OK except c++11 and included boost.

gcc 5.2: all OK

clang 3.6 with libstdc++: all OK

clang 3.6 with libc++: not OK because the code insists on using TR1, 
which does not make sense.


Does this last case correspond to recent mac systems? What shall we do 
from there?


JMarc
>From 6b5e887909e2422443449654e5aeca0221d27dd7 Mon Sep 17 00:00:00 2001
From: Georg Baum <b...@lyx.org>
Date: Sat, 16 May 2015 00:05:23 +0200
Subject: [PATCH] Fix compilation with boost 1.60

Newer boost versions use complicated type traits for boost::next and
boost::prior, which do not work with the RandomAccessList iterators.
The long term solution is to use std::next and std::prev, for now supply
simple replacements for compilers that do not support C++11 yet.

This is was cherry picked from b5963300 and 7e72c1d0d3.
---
 boost/extract.sh|1 -
 src/Compare.cpp |9 -
 src/Cursor.cpp  |2 +-
 src/CutAndPaste.cpp |   10 +-
 src/FontList.cpp|6 ++
 src/Text.cpp|   13 ++---
 src/Text2.cpp   |9 -
 src/Text3.cpp   |9 -
 src/lyxfind.cpp |1 -
 src/mathed/MathData.cpp |4 ++--
 src/output_docbook.cpp  |7 +++
 src/output_latex.cpp|   11 +--
 src/support/lyxalgo.h   |   26 ++
 13 files changed, 62 insertions(+), 46 deletions(-)

diff --git a/boost/extract.sh b/boost/extract.sh
index dbe280b..297cbc5 100755
--- a/boost/extract.sh
+++ b/boost/extract.sh
@@ -29,7 +29,6 @@ bcp --boost=$1 \
 	boost/function.hpp \
 	boost/functional.hpp \
 	boost/lexical_cast.hpp \
-	boost/next_prior.hpp \
 	boost/noncopyable.hpp \
 	boost/regex.hpp \
 	boost/scoped_array.hpp \
diff --git a/src/Compare.cpp b/src/Compare.cpp
index 1d72ebf..326eba2 100644
--- a/src/Compare.cpp
+++ b/src/Compare.cpp
@@ -19,11 +19,10 @@
 
 #include "insets/InsetText.h"
 
-#include "support/lassert.h"	
+#include "support/lassert.h"
+#include "support/lyxalgo.h"
 #include "support/qstring_helpers.h"
 
-#include 
-
 using namespace std;
 using namespace lyx::support;
 
@@ -420,8 +419,8 @@ static void getParagraphList(DocRange const & range,
 	pit_type startpit = range.from.pit();
 	pit_type endpit = range.to.pit();
 	ParagraphList const & ps_ = range.text()->paragraphs();
-	ParagraphList tmp_pars(boost::next(ps_.begin(), startpit),
-		boost::next(ps_.begin(), endpit + 1));
+	ParagraphList tmp_pars(lyx::next(ps_.begin(), startpit),
+	   lyx::next(ps_.begin(), endpit + 1));
 
 	// Remove the end of the last paragraph; afterwards, remove the
 	// beginning of the first paragraph. Keep this order - there may only
diff --git a/src/Cursor.cpp b/src/Cursor.cpp
index aed1414..746f980 100644
--- a/src/Cursor.cpp
+++ b/src/Cursor.cpp
@@ -132,7 +132,7 @@ bool bruteFind(Cursor & cursor,
 	// Get an iterator after the last paragraph in the cache
 	DocIterator et(inset);
 	et.push_back(CursorSlice(inset));
-	et.pit() = boost::prior(cache.end())->first;
+	et.pit() = lyx::prev(cache.end(), 1)->first;
 	if (et.pit() >= et.lastpit())
 		et = doc_iterator_end(inset);
 	else
diff --git a/src/CutAndPaste.cpp b/src/CutAndPaste.cpp
index e2ccf39..185cf79 100644
--- a/src/CutAndPaste.cpp
+++ b/src/CutAndPaste.cpp
@@ -60,13 +60,13 @@
 #include "support/lassert.h"
 #include "support/limited_stack.h"
 #include "support/lstrings.h"
+#include "support/lyxalgo.h"
 
 #include "frontends/alert.h"
 #include "frontends/Clipboard.h"
 #include "frontends/Selection.h"
 
 #include 
-#include 
 
 #include 
 
@@ -383,7 +383,7 @@ pasteSelectionHelper(

Re: [PATCH] Re: Update boost in 2.1 branch?

[Richard Heck]

On 01/21/2016 04:07 PM, Pavel Sanda wrote:
> Jean-Marc Lasgouttes wrote:
>> So is it a problem that compiling in C++11 mode is broken with gcc 4.6? I 
>> would guess not.
> I guess it also depends how much space for error we have...
> Richard, do you plan to release one intermediate 2.1.x or you just waiting 
> for the final one?

How far out do we realistically think 2.2.0 is? I am thinking end of
February, but if it gets delayed any further we might think about an
intermediate release.

Really, I should have done 2.1.5 back at the end of November, but I
thought 2.2 was closer.

Richard

Re: [PATCH] Re: Update boost in 2.1 branch?

[Scott Kostyshak]

On Thu, Jan 21, 2016 at 04:40:56PM -0500, Richard Heck wrote:
> On 01/21/2016 04:07 PM, Pavel Sanda wrote:
> > Jean-Marc Lasgouttes wrote:
> >> So is it a problem that compiling in C++11 mode is broken with gcc 4.6? I 
> >> would guess not.
> > I guess it also depends how much space for error we have...
> > Richard, do you plan to release one intermediate 2.1.x or you just waiting 
> > for the final one?
> 
> How far out do we realistically think 2.2.0 is? I am thinking end of
> February, but if it gets delayed any further we might think about an
> intermediate release.

I think end of February is realistic. Beta should be soon, just need
Guillaume's set of patches to git a final review, and Georg also is
trying to look into an issue that Stephan has reported. After beta I do
not think developers are planning many non-trivial commits so whether we
achieve end of February for a final release will depend on what issues
our beta testers find and on how long it takes us to fix those issues.
 
Scott


signature.asc
Description: PGP signature

Re: [PATCH] Re: Update boost in 2.1 branch?

[Pavel Sanda]

Jean-Marc Lasgouttes wrote:
> So is it a problem that compiling in C++11 mode is broken with gcc 4.6? I 
> would guess not.

I guess it also depends how much space for error we have...
Richard, do you plan to release one intermediate 2.1.x or you just waiting
for the final one?

Pavel

Re: [LyX/master] Update LFUNs.lyx to current format

[Jean-Marc Lasgouttes]

Le 16/01/16 12:48, Guenter Milde a écrit :

Or we remove this generated file from git (my preference).


This creates problems of its own, since now there are files in 
/lib.


JMarc

Re: [LyX/master] Update LFUNs.lyx to current format

[Guillaume Munch]

Le 16/01/2016 10:12, Georg Baum a écrit :

Guillaume Munch wrote:


I believe as well that we should not extend the already long checklist
for format changes. Updatedocs could take care of running gen_lfuns and
then update it to the latest format.


Good idea. I added the generation of LFUNs.lyx, the version updating did
exist already. However, I think we should stick to one generator of
LFUNs.lyx in git: Either we only submit files generated by gen_lfuns.py, and
not saved by LyX or lyx2lyx (this is done up to now), or we always open and
save the file with LyX after generation and before submit. Otherwise we get
lots of unwanted whitespace changes in the diffs.



Good. But if we go this way, Development.lyx has to be updated to inform
that this is now done automatically and in particular that one should
not necessarily worry if there are more changes than expected in LFUNs.lyx.

Re: [LyX/master] Update LFUNs.lyx to current format

[Georg Baum]

Guillaume Munch wrote:

> I believe as well that we should not extend the already long checklist
> for format changes. Updatedocs could take care of running gen_lfuns and
> then update it to the latest format.

Good idea. I added the generation of LFUNs.lyx, the version updating did 
exist already. However, I think we should stick to one generator of 
LFUNs.lyx in git: Either we only submit files generated by gen_lfuns.py, and 
not saved by LyX or lyx2lyx (this is done up to now), or we always open and 
save the file with LyX after generation and before submit. Otherwise we get 
lots of unwanted whitespace changes in the diffs.


Georg

Re: [LyX/master] Update LFUNs.lyx to current format

[Guenter Milde]

On 2016-01-16, Georg Baum wrote:
> Guillaume Munch wrote:

>> I believe as well that we should not extend the already long checklist
>> for format changes. Updatedocs could take care of running gen_lfuns and
>> then update it to the latest format.

> Good idea. I added the generation of LFUNs.lyx, the version updating did 
> exist already. However, I think we should stick to one generator of 
> LFUNs.lyx in git: Either we only submit files generated by gen_lfuns.py, and 
> not saved by LyX or lyx2lyx (this is done up to now), or we always open and 
> save the file with LyX after generation and before submit.

Or we remove this generated file from git (my preference).

Günter

Re: [LyX/master] Update LFUNs.lyx to current format

[Guillaume Munch]

Le 15/01/2016 20:32, Georg Baum a écrit :

commit 4c3b8bf7c7205e26b28b6562be11105558ec3250
Author: Georg Baum <b...@lyx.org>
Date:   Fri Jan 15 21:31:57 2016 +0100

 Update LFUNs.lyx to current format

diff --git a/development/tools/gen_lfuns.py b/development/tools/gen_lfuns.py
index 8e4bc88..0fb9380 100755
--- a/development/tools/gen_lfuns.py
+++ b/development/tools/gen_lfuns.py
@@ -43,9 +43,10 @@ ID_DICT = dict(name=LFUN_NAME_ID, action=LFUN_ACTION_ID, 
notion=LFUN_NOTION_ID,
  syntax=LFUN_SYNTAX_ID, params=LFUN_PARAMS_ID, 
sample=LFUN_SAMPLE_ID, origin=LFUN_ORIGIN_ID)

  LFUNS_HEADER = """# gen_lfuns.py generated this file. For more info see 
http://www.lyx.org/
-\\lyxformat 503
+\\lyxformat 504
  \\begin_document
  \\begin_header
+\\save_transient_properties true
  \\origin /systemlyxdir/doc/
  \\textclass article
  \\begin_preamble



Is a step in Development.lyx missing?

Re: [LyX/master] Update LFUNs.lyx to current format

[Georg Baum]

Guillaume Munch wrote:

> Is a step in Development.lyx missing?

IIRC we did not decide that yet. IMHO it is not required to update these 
files for each format change, but some time ago we decided that for a 
release all files should be up to date, and it is in the release checklist.


Georg

Re: [LyX/master] Update LFUNs.lyx to current format

[Guillaume Munch]

Le 15/01/2016 20:50, Georg Baum a écrit :

Guillaume Munch wrote:


Is a step in Development.lyx missing?


IIRC we did not decide that yet. IMHO it is not required to update these
files for each format change, but some time ago we decided that for a
release all files should be up to date, and it is in the release checklist.



I believe as well that we should not extend the already long checklist 
for format changes. Updatedocs could take care of running gen_lfuns and 
then update it to the latest format.

Re: Update boost in 2.1 branch?

[Jean-Marc Lasgouttes]

Le 09/01/2016 00:50, Richard Heck a écrit :

On 01/08/2016 05:06 AM, Jean-Marc Lasgouttes wrote:


Currently we use boost 1.53 in 2.1 branch. Would it be a good move to
update it to 1.60? I am getting loads of warnings with gcc 5.1.


Fine with me, and I see the same warnings.


OK, I pushed it.

JMarc

Re: Update boost in 2.1 branch?

[Jean-Marc Lasgouttes]

Le 11/01/2016 20:53, Georg Baum a écrit :

The few times I did run that script it worked fine. If you look at a few
files in the diff and see no peculiar change I'd say it is safe to commit.

One thing we should keep in mind is that this would also produce a 3 MB
2.1.4->2.1.5 patch.


Richard, is the 3MB patch a problem to you? I think it is a good idea to 
upgrade 2.1 boost version, so that we know that it compiles better in 
the future.


JMarc

Re: Update boost in 2.1 branch?

[Jean-Marc Lasgouttes]

Le 09/01/2016 00:50, Richard Heck a écrit :

On 01/08/2016 05:06 AM, Jean-Marc Lasgouttes wrote:


Currently we use boost 1.53 in 2.1 branch. Would it be a good move to
update it to 1.60? I am getting loads of warnings with gcc 5.1.


Fine with me, and I see the same warnings.


I ran the extract.sh script, and have a 3MB commit. Is that to be 
expected? It compiles without warning (using a small additional fix).


Shall I just push it? Does someone want to see it or have a go at it?

I attach just the stats below.

JMarc


commit 3ebe735cc32571c025e4c0ee4614761746c465ea
Author: Jean-Marc Lasgouttes <lasgout...@lyx.org>
Date:   Mon Jan 11 11:54:28 2016 +0100

Update to boost 1.60

Also fix a warning by backporting 43d75a07.

 boost/boost/align/align.hpp|   20 +
 boost/boost/align/detail/address.hpp   |   29 +
 boost/boost/align/detail/align.hpp |   40 +
 boost/boost/align/detail/align_cxx11.hpp   |   22 +
 boost/boost/align/detail/is_alignment.hpp  |   29 +
 boost/boost/aligned_storage.hpp|  181 --
 boost/boost/any.hpp|  184 +-
 boost/boost/assert.hpp |  112 +-
 boost/boost/bind.hpp   |   19 +-
 boost/boost/bind/arg.hpp   |   10 +-
 boost/boost/bind/bind.hpp  |  509 +++-
 boost/boost/bind/bind_mf_cc.hpp|  214 ++
 boost/boost/bind/placeholders.hpp  |   65 +-
 boost/boost/call_traits.hpp|6 +-
 boost/boost/checked_delete.hpp |   78 +-
 boost/boost/concept/assert.hpp |3 +-
 boost/boost/concept/detail/concept_def.hpp |   17 -
 boost/boost/concept/detail/general.hpp |4 +-
 boost/boost/concept/detail/msvc.hpp|9 +
 boost/boost/concept/usage.hpp  |8 -
 boost/boost/concept_check.hpp  |   51 +-
 boost/boost/config.hpp |   21 +-
 boost/boost/config/auto_link.hpp   |   18 +-
 boost/boost/config/compiler/borland.hpp|   43 +-
 boost/boost/config/compiler/clang.hpp  |  147 +-
 boost/boost/config/compiler/codegear.hpp   |   43 +-
 boost/boost/config/compiler/common_edg.hpp |   58 +-
 boost/boost/config/compiler/cray.hpp   |   39 +-
 boost/boost/config/compiler/digitalmars.hpp|   53 +-
 boost/boost/config/compiler/gcc.hpp|  230 +-
 boost/boost/config/compiler/gcc_xml.hpp|   47 +-
 boost/boost/config/compiler/hp_acc.hpp |   23 +-
 boost/boost/config/compiler/intel.hpp  |  391 ++-
 boost/boost/config/compiler/metrowerks.hpp |   55 +-
 boost/boost/config/compiler/mpw.hpp|   43 +-
 boost/boost/config/compiler/nvcc.hpp   |   12 -
 boost/boost/config/compiler/pathscale.hpp  |   40 +-
 boost/boost/config/compiler/pgi.hpp|   39 +-
 boost/boost/config/compiler/sunpro_cc.hpp  |   87 +-
 boost/boost/config/compiler/vacpp.hpp  |   62 +-
 boost/boost/config/compiler/visualc.hpp|  246 +-
 boost/boost/config/compiler/xlcpp.hpp  |  258 ++
 boost/boost/config/platform/cloudabi.hpp   |   18 +
 boost/boost/config/platform/haiku.hpp  |   31 +
 boost/boost/config/platform/linux.hpp  |2 +
 boost/boost/config/platform/macos.hpp  |2 +-
 boost/boost/config/platform/solaris.hpp|5 +-
 boost/boost/config/platform/vxworks.hpp|  368 ++-
 boost/boost/config/platform/win32.hpp  |   31 +-
 boost/boost/config/select_compiler_config.hpp  |   58 +-
 boost/boost/config/select_platform_config.hpp  |   32 +
 boost/boost/config/select_stdlib_config.hpp|   36 +-
 boost/boost/config/stdlib/dinkumware.hpp   |   73 +-
 boost/boost/config/stdlib/libcomo.hpp  |   15 +-
 boost/boost/config/stdlib/libcpp.hpp   |   43 +
 boost/boost/config/stdlib/libstdcpp3.hpp   |  144 +-
 boost/boost/config/stdlib/modena.hpp   |   13 +
 boost/boost/config/stdlib/msl.hpp  |   22 +-
 boost/boost/config/stdlib/roguewave.hpp|   12 +
 boost/boost/config/stdlib/sgi.hpp  |   18 +-
 boost/boost/config/stdlib/stlport.hpp  |   21 +-
 boost/boost/config/stdlib/vacpp.hpp|   16 +-
 boost/boost/config/suffix.hpp  |  243 +-
 boost/boost/config/user.hpp|   21 +-
 boost/boost/container/container_fwd.hpp|  246 +-
 boost/boost/container/detail/std_fwd.hpp   |   56 +
 boost/boost/core/addressof.hpp |  162 ++
 boost/boost/core/checked_delete.hpp|   69 +
 boost/boost/core/demang

Re: Update boost in 2.1 branch?

[Georg Baum]

Jean-Marc Lasgouttes wrote:

> I ran the extract.sh script, and have a 3MB commit. Is that to be
> expected? It compiles without warning (using a small additional fix).
> 
> Shall I just push it? Does someone want to see it or have a go at it?

The few times I did run that script it worked fine. If you look at a few 
files in the diff and see no peculiar change I'd say it is safe to commit.

One thing we should keep in mind is that this would also produce a 3 MB 
2.1.4->2.1.5 patch.


Georg

Re: Update boost in 2.1 branch?

[Richard Heck]

On 01/08/2016 05:06 AM, Jean-Marc Lasgouttes wrote:
>
> Currently we use boost 1.53 in 2.1 branch. Would it be a good move to
> update it to 1.60? I am getting loads of warnings with gcc 5.1.

Fine with me, and I see the same warnings.

Richard