Am Mittwoch, den 28.12.2016, 09:58 +0100 schrieb Jürgen Spitzmüller:
> For the sake of the tests, we could just add something like the
> following to the preamble that intentionally ignores these missing
> chars:
>
> \AtBeginDocument{%
> \usepackage{newunicodechar}
> \newcommand\lyxbypasschar[2]{%
> \newunicodechar{#1}{\iffontchar\font`#1 #1\else{\textbf{<missing
> char:
> #2>}}\fi}}
> \lyxbypasschar{「}{0x300c}
> \lyxbypasschar{」}{0x300d}
> \lyxbypasschar{『}{0x300e}
> \lyxbypasschar{』}{0x300f}
> \lyxbypasschar{《}{0x300a}
> \lyxbypasschar{》}{0x300b}
> \lyxbypasschar{〈}{0x3008}
> \lyxbypasschar{〉}{0x3009}
> }
>
> However, I am reluctant to include it in the UG's preamble just for
> the
> sake of making the tests happy.A more general and probably generally useful solution is to add a command line option that makes LyX (again) proceed despite the missing glyphs warning (and just report the warning). Then the tests could use this option. Jürgen
signature.asc
Description: This is a digitally signed message part
