On 2016-09-22, Scott Kostyshak wrote: > [-- Type: text/plain, Encoding: quoted-printable --]
> On Thu, Sep 22, 2016 at 11:54:52PM +0200, Günter Milde wrote: >> commit 11a036b87145b1fdaa216e238f0a6b1f5d36c3c0 >> Author: Günter Milde <mi...@lyx.org> >> Date: Thu Sep 22 23:54:18 2016 +0200 >> ctests: found reason for "seminar" failure. >> --- >> +#10394 Do not error on missing characters in "nullfont". >> +# "LaTeXing" seminar fails (except for LuaTeX) with >> +# Missing character: There is no 0 in font nullfont! >> +# due to a bug in PGF (https://sourceforge.net/p/pgf/bugs/314/) > Thanks for referencing the bug report. It says it was fixed a year ago. > It did not make it into TL 2016? Sorry, I mixed it up. Should have been the new bug reported by me yesterday: https://sourceforge.net/p/pgf/bugs/401/ The closed/fixed PGF bug 314 is similar but the problem leading to the seminar failure is in another file. (PGF uses "nullfont" as a *feature* for suppressing output, so we should expect more of these warnings and handle them: This is LyX bug #10394 Do not error on missing characters in "nullfont". http://www.lyx.org/trac/ticket/10394 ) My (still untested) patch for the latter is diff --git a/src/LaTeX.cpp b/src/LaTeX.cpp index cfa6e1d..e5815ca 100644 --- a/src/LaTeX.cpp +++ b/src/LaTeX.cpp @@ -899,9 +899,11 @@ int LaTeX::scanLogFile(TeXErrors & terr) from_local8bit("pdfTeX Error"), from_local8bit(token), child_name); - } else if (prefixIs(token, "Missing character: There is no ")) { - // XeTeX/LuaTeX error about missing glyph in selected font - // (bug 9610) + } else if (prefixIs(token, "Missing character: There is no ") + && !contains(token, "nullfont")) { + // Warning about missing glyph in selected font + // may be dataloss (bug 9610). + // but can be ignored for 'nullfont' (bug 10394) retval |= LATEX_ERROR; terr.insertError(0, from_local8bit("Missing glyphs!"), Günter
