Am Mittwoch, 20. Februar 2019 16:45:29 CET schrieb Guenter Milde 
<mi...@users.sf.net>:
> On 2019-02-16, Kornel Benko wrote:
> > Am Freitag, 15. Februar 2019 22:57:53 CET schrieb Guenter Milde 
> > <mi...@users.sf.net>:
> >> On 2019-02-15, Kornel Benko wrote:
> >> > Am Freitag, 15. Februar 2019 06:47:00 CET schrieb Guenter Milde 
> >> > <mi...@users.sf.net>:
> 
> > ...
> 
> >> This leaves the following tests affected by my changes useSystemFonts.py:
> 
> >> > Remaining tests now:
> >> >  1771 - export/doc/attic/eu_Customization_dvi3_systemF (Failed)
> >> >  1776 - export/doc/attic/eu_Customization_pdf4_systemF (Failed)
> >> >  1778 - export/doc/attic/eu_Customization_pdf5_systemF (Failed)
> 
> > I don't get it. They compile here fine with TL18 _and_ TL17
> 
> ... but you reported them as failing with my (now reverted) changes to
> useSystemFonts.pl.

It's the other way around. They failed to compile before you reverted.

> 
> >> "Hand-compiling" the document with XeTeX and "default" non-TeX fonts works
> >> here. 
> 
> >> This would mean that some side-effect of my changes (that did not
> >> include changes to documents with lang == eu) changed the document from
> >> working to failing.
> 
> > Yes, the default in font seems to be not working here. Hand-compiling
> > gives:
> > Missing character: There is no ȧ (U+0227) in font 
> > [lmroman10-regular]:+tlig;!
> > ] [73] [74] [75] (./eu_Customization.aux
> > Language basque already loaded; id is 4))
> 
> >> Also, this would mean that getting rid of the "hidden" font replacement
> >> alltogether should not harm in this "attic" case!
> 
> Checking again, I could reproduce the failure, so it seems we would need
> a dedicated test version of this document with non-tex fonts or keep the
> script based font replacement for this specific case.

Yes.

> 
> >> >  6320 - export/examples/sr/Braille_dvi3_systemF (Failed)
> >> >  6325 - export/examples/sr/Braille_pdf4_systemF (Failed)
> 
> >> Hand-compiling works fine with the default (i.e. LatinModern) system fonts,
> >> so there is no need for font changes.
> 
> > Hand-compiling here gives:
> > ! Package polyglossia Error: The current roman font does not contain the 
> > Cyrill
> > ic script!
> > (polyglossia)                Please define \cyrillicfont with 
> > \newfontfamily.
> 
> > See the polyglossia package documentation for explanation.
> 
> > This is with TL18 _and_ TL17
> 
> This is actually a Polyglossia bug: the document language is "Serbian
> (Latin Script)" yet Polyglossia throws an error (despite there is no
> character missing and there is no need for a Cyrillic-supporting font).
> Solving #8035 would also work around this Polyglossia bug, so I suggest
> to invert sr/Braille_pdf4_systemF referencing lyxissue #8035 instead of
> replacing the font.
> 
> I will look into this over the next weeks.
> 
> 
> Günter
>

        Thanks,
                Kornel

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to