http://bugzilla.suse.com/show_bug.cgi?id=1040434 Leon Meier changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|Other |x86-64 OS|Other |openSUSE 42.2 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1040434 Chenzi Cao changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |werner@suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1040434 http://bugzilla.suse.com/show_bug.cgi?id=1040434#c3 Leon Meier changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Leon.Meier@yandex | |.ru) | --- Comment #3 from Leon Meier --- Tested that fontspec version. No change; the bug still occurs if fontspec, xetex, amsmath, unicode-math, and computer modern are updated from http://download.opensuse.org/repositories/Publishing:/TeXLive/openSUSE_Leap_... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1040434 http://bugzilla.suse.com/show_bug.cgi?id=1040434#c5 Leon Meier changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(werner@suse.com) --- Comment #5 from Leon Meier --- Retried. Now I have fontspec 2.6a. The \texttt bug is still there: [ xdvipdfmx:fatal: This font using the "seac" command for accented characters... ] However, there is one more warning: [ ************************************************* * fontspec warning: "tu-clash" * * I have found the tuenc.def encoding definition file but the TU encoding is * not defined by the LaTeX2e kernel; attempting to correct but you really * should update to the latest version of LaTeX2e. ************************************************* ] I thought, this is because I have not updated all the packages from publishing. So, I updated texlive-latex, texlive-latex-bin, texlive-latex-bin-bin, texlive-unicode-data, texlive-unicode-data-doc, texlive-xunicode texlive-xunicode-doc, and texlive-collection-latexrecommended (which installed quite a lot of junk anew). The "seac" bug is still present, but I am still getting the additional warning above. Should I now update the remaining LaTeX packages to try to get this warning away or do something else (and, if so, what exactly?) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1040434 http://bugzilla.suse.com/show_bug.cgi?id=1040434#c7 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #7 from Dr. Werner Fink --- (In reply to Leon Meier from comment #6)

I've just updated texlive-collection-xetex (which updated a lot of packages). Same result.

Then I can not help you ... next try is final TeXLive 2017 if you have a solution at your own you might reopen -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1040434 http://bugzilla.suse.com/show_bug.cgi?id=1040434#c9 --- Comment #9 from Dr. Werner Fink --- (In reply to Leon Meier from comment #8)

Hm. Are saying that the fontspec warning "tu-clash" is unrelated to the bug?

Don't know and I'll not hunt this down .. the freeze for TeXLive 2017 is on as Karl Berry had written at May 19 2017 ;) http://tug.org/pipermail/tex-live/2017-May/040157.html -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1040434 http://bugzilla.suse.com/show_bug.cgi?id=1040434#c11 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(werner@suse.com) | --- Comment #11 from Dr. Werner Fink --- (In reply to Leon Meier from comment #10)

How is the freeze for TeXLive 2017 related to this problem?

Freeze means no patches with new features, packages nor new features are accepted ... only fixes are allowed upto TeXLive 2017 are allowed upto the point where the release takes. Common way to finalize a huge software package/collection. I do not know if this is related to this problem not I'm interested in ... the only question is if the problem might be resolved. Beside security fixes or paid contract work I'll not put work force into the old package anymore as I have to find the time to get the new TeXLive 2017 up and running. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1040434 http://bugzilla.suse.com/show_bug.cgi?id=1040434#c13 --- Comment #13 from Dr. Werner Fink --- (In reply to Leon Meier from comment #12)

I don't really know. But I'm under the impression be that if you organize the search for the font CMU TypeWriter Text (e.g. by a particular directory structure) in TL 2017 the same way you did organize it for TL 2016, you might get the same bug in TL 2017.

I'm playing around with luaotfload-tool and luatools. Beside this, this bug is still on my radar. What I've found is that luaotfload does no handle pfb well, that is I see luaotfload | db : Unknown format: "pfb", skipping. for TeXLive 2016 which seems to be upstream -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1040434 http://bugzilla.suse.com/show_bug.cgi?id=1040434#c15 --- Comment #15 from Dr. Werner Fink --- I'm going to revert the fontspec update simply because fontspec update without updating the engines like LaTeX doesnot work as I've been told. That the bug report boo#1039951 is invalid as it want an update which can not work at all. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1040434 http://bugzilla.suse.com/show_bug.cgi?id=1040434#c17 --- Comment #17 from Leon Meier --- Well, there is apparently an interconnection between fontspec and other components of texlive which I was not aware of when filing that bug. It seems to me that the update of fontspec was a necessary step but not a sufficient one. After all, Debian with TL 2016 seems to have done its packaging job properly such that the bug does not occur there. There are dozens of differences between their packaging and OpenSuse packaging, and the most striking one is their newer version of fontspec. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1040434 http://bugzilla.suse.com/show_bug.cgi?id=1040434#c19 --- Comment #19 from Dr. Werner Fink --- (In reply to Leon Meier from comment #17)

Well, there is apparently an interconnection between fontspec and other components of texlive which I was not aware of when filing that bug. It seems to me that the update of fontspec was a necessary step but not a sufficient one. After all, Debian with TL 2016 seems to have done its packaging job properly such that the bug does not occur there. There are dozens of differences between their packaging and OpenSuse packaging, and the most striking one is their newer version of fontspec.

Debian does use follow upstream at each update as the Norbert has the time to do this. I've not. And yes the original fontspec of the original TeXLive 2016 is not perfect but fits the definition found in the LaTeX kernel engine. Even packaging is open source and you might help here to get more perfect -- You are receiving this mail because: You are on the CC list for the bug.