Am Samstag, 9. Januar 2016 um 17:51:06, schrieb Guenter Milde <mi...@users.sf.net> > On 2016-01-08, Scott Kostyshak wrote: > > > [-- Type: text/plain, Encoding: quoted-printable --] > > > On Fri, Jan 08, 2016 at 08:11:19PM +0100, 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. > > > I agree with Kornel that it is not hackish of the tests. > > I agree, that testing with system fonts is not bad. As long as this > requires a hack (like changing fonts or the "useNonTeXfonts" setting > "secretly" in a test script, this is not bad either. > > However, it remains a hack and could/should be replaced if a better way of > operating is available. > > Currently, if I want to check a failure with .*systemF, I have to > > a) change it to use non-TeX fonts, > b) eventually set alternative system fonts > (which may or may not be the same as the "secretly" used ones by the test > machinery). > > Since 2.2, step b) is no longer necessary, we can store alternative system > fonts in the source. > > > > I think what Günter's main underlying point (please correct me if I'm > > wrong) is to make it clear that *LyX* (not the tests) should have a > > better framework for encouraging system fonts by default for XeTeX and > > LuaTeX. > > This is a different point. With a new config value "automatic" for "use > non-TeX fonts" (second part of ticket #9744), also step a) would no longer > be required. > > > But since LyX does not do that, my opinion is that it is a great idea > > for the tests to do the best job they can at testing the use of system > > fonts. > > Yes, as long as LyX cannot do that, we need the workaround. > > However, "the best job they can" (for me) does not imply using a sans > serif font for all three:, serif, sans serif, and monospaced.
I wonder what makes you think that the test uses sans serif only?
(Yes, there is one condition which does it that way, but other cases do not)
> I agree that I have a personal interest, as these replacements vitiate
> one of the use cases in #8035 (while there are alternative serif fonts
> that would work if #8035 were solved).
>
> Günter
Kornel
signature.asc
Description: This is a digitally signed message part.
