On 10/12/21 3:01 PM, Rich Shepard wrote:
On Tue, 12 Oct 2021, Rich Shepard wrote:
The current one is shown in the attached .png. There was no 'complete
log'
produced when I clicked that button.
Darn! It's on this one.
Rich
Rich,
I would use a command line tool to scan the document source file (.lyx)
for a non-ASCII or non-UTF8 character. If that turned up nothing, I
would scan the .bib file (if any) and any included text files.
As I recall, you're on Linux. You might try
grep -axv '.*' <source file>
first. It should find lines that are not in whatever encoding your
system uses by default (UTF-8 in my case). It can also be done using
'iconv'. I've had to jump through similar hoops in the past.
Paul
--
lyx-users mailing list
[email protected]
http://lists.lyx.org/mailman/listinfo/lyx-users
