On 2016-01-08, Kornel Benko wrote: > Am Freitag, 8. Januar 2016 um 12:21:44, schrieb Scott Kostyshak > <skost...@lyx.org> >> On Fri, Jan 08, 2016 at 07:09:44AM +0000, Guenter Milde wrote:
... >> > * FreeSans seems to provide the correct script-support info not to >> > trigger the false-positive error http://www.lyx.org/trac/ticket/8035 >> > >> > However, setting all of "mainfont", "sansfont", and "monofont" to >> > FreeSans seems "hackish" to me. > No it is not hackish IMHO. The test should show, that with a suitable > font this file is compilable. It is a remnant from the times we had > defined fonts for texF only. If the non-tex font is defined in the > document, it will be used. There are two points here: * The font replacement in the test machinery was a justified workaround to test export when setting both tex and non-tex fonts in the source was not possible. With LyX 2.2, this is no longer needed and should be replaced by a font setting in the source. This allows easier verification of problems "by hand". * Setting both, mainfont and sansfont to the same sans-serif font to prevent a false positive error and get a working export instead of a test failure due to a reported bug is imo not the right thing. Günter
