Am Mittwoch, den 28.12.2016, 11:41 +0000 schrieb Guenter Milde: > I see. But as the tests should correspond to "normal" LyX behaviour, > we > should rather > > a) fix the document: we can set a custom non-tex font that contains > the > missing characters. This way a user just clicking "use non-TeX > fonts" and > compiling will get the correct result. > There are no side-effects with the default (TeX-fonts) setting. > > If there is a free suitable font, this is my preference.
I doubt you will find a free suitable font that is expected to be installed on every user's box so that "a user just clicking "'use non- TeX fonts' and compiling will get the correct result." But, after all, this is not something the UG is designed for (and neither the CJK quotation marks). > b) invert the test: as the document is not required to work with non- > TeX > fonts but only reused for tests of all export formats, the failing > test > does not mean there is a problem in LyX and can be ignored. However, the UG is a quite good test file. It would be a pity to take it off the set just because the glyphs are missing. Ignoring the missing glyphs warning strikes me a better alternative. > > -1 the document can no longer be used to test export with Unicode > fonts. > > If there is no suitable Unicode font, this is the correct way. > For test with Unicode fonts, we could add a modified copy to the > "dedicated test samples folder" autotests/export/latex/. Then you would need to maintain that copy and update it every time the UG is updated. I doubt this will work. Jürgen > > Günter >
signature.asc
Description: This is a digitally signed message part
