On 2018-01-30, Scott Kostyshak wrote: > On Tue, Jan 30, 2018 at 09:42:14AM +0000, Guenter Milde wrote: >> On 2018-01-29, Jürgen Spitzmüller wrote: >> > Am Montag, den 29.01.2018, 10:55 +0100 schrieb S. Noble:
>> >> Thanks, Scott and Günter, for your quick, helpful replies. >> >> I had followed Scott’s advice and found the offending character. It >> >> was indeed the lower-case Greek letter “sigma”, not in a word-final >> >> position (i.e., “σ”). (There was just one of them in the document). >> >> I was then puzzling over LyX’s error message — “There is no v in font >> >> LinLibertineT-osf-lgr”. >> > That's not LyX's error message, but LaTeX's (or polyglossia's for that >> > matter). >> While Polyglossia is known for a lot of false positives when checking >> character support, it is not to blame here. Polyglossia tests for script >> support in the used fonts, relying on often missing information in the >> font metadata and gives errors (not just warnings). >> The "There is no … in font …" warnings are from TeX. > Do you think it is worthwhile to report bugs regarding missing > information in the font metadata, or in your experience is it not likely > to lead to fixes? I suppose I would need to find the upstream font > definitions and report them there, for each individual issue? This is about Polyglossia and system fonts, so one may try this but it may be any font on your computer... More important would be a fix for the test (making it a warning only) in Polyglossia. Günter
