Le 27/03/2018 à 18:23, Scott Kostyshak a écrit :
On Tue, Mar 27, 2018 at 04:10:43PM +0000, Jean-Pierre Chrétien wrote:
Le 16/09/2017 à 20:44, Jean-Pierre a écrit :
Le 16 septembre 2017 6:39:06 PM Scott Kostyshak <skost...@lyx.org> a écrit :
On Sun, Aug 13, 2017 at 06:39:16PM +0200, Jean-Pierre Chrétien wrote:
Le 09/08/2017 à 10:00, Scott Kostyshak a écrit :
Thanks for looking into this, Jean-Pierre. Note that after a tlmgr
upgrade I see the following test failures:
6221 - export/templates/lettre_dvi3_systemF (Failed)
6226 - export/templates/lettre_pdf4_systemF (Failed)
6228 - export/templates/lettre_pdf5_systemF (Failed)
I see the errors when I run xelatex manually, seems en polyglossia problem,
I will investigate.
Jean-Pierre, did you have time to investigate? Anything you think we
should do for 2.3.0 on this? I have not tried to see if a tlmgr update
magically made these issues go away.
Sorry, I'm away from my desktop right now, ans I was busy with translations
before.
I will check when I'm back.
Sorry again, it took me some time to come back to this.
No problem, thanks for tackling this annoying issue.
There is a quite intricate problem with polyglossia in the additional preamble
code.
If I force babel as linguistic package, the three exports work manually.
However there are error/warnings from the dvi viewer which need further
investigation;
I might suggest to not even investigate dvi issues, if all PDF exports
are working well, unless you think it could be incorrect code written by
LyX.
Thes errors are font management errors, might disappear with other fonts than
FreeSans. I'll check later.
[...]
In your commit message could you give a few details and maybe link to
this ML thread? This way if someone in two years wants to know why babel
was forced (e.g. from git log lettre.lyx or git blame), they will
quickly find this discussion.
Oups, I put the link in the file itself, sorry.
--
Jean-Pierre
