Log Parser misses lost chars

[Markvy]

Steps to reproduce the problem: Compile this:

\documentclass[12pt]{article}
\begin{document}
Résumé
\end{document}

Expected output: The log file has warnings that the font does not contain these characters. This is an easy error to make when copy/pasting the name of a foreign author from a webpage or something. It would be nice if the LogParser caught these. This is a scary mistake because the tex file "looks right". Only by inspecting the output are you likely to catch the mistake.

Actual output: It doesn't catch them.

TeXworks version: 0.4.6 TeXworks obtained from: MikTeX Operating system: Win10

[stloeffler]

Thanks for reporting.

@antoniomacri: Actually, this message does not seem to appear on the console (which is what the log parser is currently parsing), but only in the actual log file (and there only with respect to the pdf output page, not with respect to the input line the problem actually originated at). We could try parsing the log in addition to stdout to catch such problems (note, though, that the log may be incomplete or even empty in case of errors and subsequent abortion of the typesetting process - so parsing the log file is no alternative to parsing stdout). However, we'd need to filter out duplicates then, too.

[Markvy]

Can the log really be empty, unless it gets deleted? This may be a more complex feature request than I intended to make. I thought parsing the log was mostly a good substitute for the console. (Although you wouldn't catch BibTex errors and such that way, but currently you don't look for those anyway.)