On Sun, Jan 28, 2018 at 04:03:24PM +0000, S. Noble wrote:
> Hello, List Members, 
> 
> I'm experiencing strange issues with LyX's "Libertine" font when I
> attempt to compile a document. I'm now using LyX 2.2.2 on Mac OSX
> 10.11.6 (El Cap.). I didn't have these issues in the past, when I first
> created the documents. (I can't remember on which version of LyX they
> were created, but it was't that long ago).
> 
> One of the documents, for example, is in French and German, with French
> being the main language. When I hit "View" or "Update", LyX gives me the
> following error:
> 
> - "Missing Glyphs!"
> 
> with the following description:
> 
> - "Missing character: There is no v in font LinLibertineT-osf-lgr!"
> 
> I've tried to scan the source code, but can't find the offending
> character(s).
> 
> If I chose "Show Output Anyway", the document appears to compile
> correctly, although the document is long and complex and I can't run the
> risk of a missing character in a footnote somewhere.

Dear S. Noble, thanks for all of the details you give. I do not how to
fix the issue. However, it is possible that you had the same issue as
you did before upgrading LyX, it's just that LyX did not report the
error. The reason is that starting as of 2.2.0, LyX started reporting
this missing characters as errors, partly because of the reason you
mention in the paragraph above (if you are missing a character e.g. in a
footnote somewhere you likely won't realize on your own).

This change in LyX's behavior was documented in the release notes of LyX
2.2.0:

  https://wiki.lyx.org/LyX/ReleaseNotes#toc2

Although I don't know how to fix the problem, I can give you a better
idea of how to find it:

  1. backup your document
  2. delete half of your document
  3. if you still get an error, go to step 2.
  4. if you do not get an error after deleting half of your document,
  undo deleting. Go to step 2 and delete the *other* half of your
  document.

Using the above approach you can narrow your document down and find
which character is causing the issue.

Best,

Scott

Attachment: signature.asc
Description: PGP signature

Reply via email to