On 2015-12-03, Kornel Benko wrote:
> Am 3. Dezember 2015 um 15:49:26, schrieb Guenter Milde <mi...@users.sf.net>
>> On 2015-12-03, Kornel Benko wrote:

>> ... We removed the problematic preamble code
>> and set PSNFSS fonts for the "basic" manuals ...
and LatinModern for the others.


...

>> >    722 - MANUALS_export/doc/el/Intro_pdf2 (Failed)
>> >    726 - MANUALS_export/doc/el/Intro_pdf5_texF (Failed)
>> >    727 - MANUALS_export/doc/el/Intro_pdf5_systemF (Failed)

>> Greek.
>> There are several alternatives to solve this.
>> See my last posting about LyX manual fonts.

> I had read it. If you know a good solution please correct, check that
> it compiles and commit. I am frustrated enough.

There are several acceptable solutions.
I think Uwe should select the best (he is the documentation maintainer).

...


>> >    847 - MANUALS_export/doc/es/Tutorial_pdf5_systemF (Failed)

>> > Compiling es/Tutorial_pdf5_systemF gives

>> > [27]
>> > ! You can't use `\char' after \the.
>> > \EU1\i ->\char 
>> >                "0131\relax 
>> > l.1089 ... escribir <<$\cos^{2}\theta$>> o <<$\lim
>> >                                                   _{n\rightarrow\infty}$>>.
>> ...

>> It’s a Babel-Spanish bug: Babel-Spanish tries to set the lim operator with
>> accent: lím. This seems to be implemented in an 8-bit specific way.

>> Using polyglossia with non-TeX fonts by 
>> setting "language package" from "Always Babel" to "Automatic" 
>> helps 
...
to get rid of this problem. 

However, "Always Babel" is set for a reason: there is one example for the
math-command \sen defined by Babel-Spanish. This fails with Polyglossia.

This means, this document fails with non-TeX fonts because of a
Babel-Spanish bug.

What can we do?

Restore the preamble code? No! Loading lmodern.sty is wrong and unstable
with non-TeX fonts. It leads to the use of T1-encoded 8-bit fonts
(selected in the preamble overwriting the fonts selected by fontspec) but
XeTeX/LuaTeX expect an Unicode font.  Even if it does not currently lead
to an compiling error with this document, it would fail when adding some
character above the 8-bit limit, e.g. an mdash. Also, some characters in
the 129-256 range (latin extended) come out wrong without warning or
error!

Until Babel-Spanish is fixed, I suggest the patch:

diff --git a/lib/doc/es/Tutorial.lyx b/lib/doc/es/Tutorial.lyx
index 05eab1a..f565bd5 100644
@@ -14,13 +14,9 @@
 % the documentation team
 % email: lyx-d...@lists.lyx.org
 
-\usepackage{ifpdf} % part of the hyperref bundle
-\ifpdf % if pdflatex is used
+% Work around a bug in Babel-Spanish with \lim if non-TeX fonts are used:
+\@ifpackageloaded{fontspec}{\unaccentedoperators}{}
 
- % set fonts for nicer pdf view
- \IfFileExists{lmodern.sty}{\usepackage{lmodern}}{}
-
-\fi % end if pdflatex is used
 
 % the pages of the TOC is numbered roman


this fixes also 

   export/doc/es/Tutorial_pdf4_systemF

. Shall I commit?

Typical example of long-running but hithero hidden non-LyX problem with
non-standard export method.



>> >    1054 - MANUALS_export/doc/he/Tutorial_dvi (Failed)
>> >    1057 - MANUALS_export/doc/he/Tutorial_pdf (Failed)
>> >    1058 - MANUALS_export/doc/he/Tutorial_pdf2 (Failed)
>> >    1059 - MANUALS_export/doc/he/Tutorial_pdf3 (Failed)
>> >    1061 - MANUALS_export/doc/he/Tutorial_pdf4_systemF (Failed)

>> Strange, I cannot see any change on this document during the last
>> time, nor any problematic code. Cannot test as I don't have Hebrew,
>> though.

> commit 52c623a558ccbf32c84dc5cac8fcea26478fb59d
> Author: Uwe Stöhr <uwesto...@lyx.org>
> Date:   Thu Dec 3 02:08:31 2015 +0100

>     UserGuide.lyx: change fonts as discussed

I see it now. 
Again, the commit is just removing problematic preamble code. The font
setting is left at default. Most likely this revealed a hidden problem.
What is the error output?

...


>> >    1447 - MANUALS_export/doc/zh_CN/Tutorial_dvi (Failed)
>> >    1450 - MANUALS_export/doc/zh_CN/Tutorial_pdf (Failed)
>> >    1451 - MANUALS_export/doc/zh_CN/Tutorial_pdf2 (Failed)
>> >    1452 - MANUALS_export/doc/zh_CN/Tutorial_pdf3 (Failed)

> They compile now. After reverting some 'unneded' removed code.

This is a true example where the tests helped prevent a regression
(Failure in the intended output format). 
Thanks!

...



>> Don't know why this works and why it failed previously:

>> >    1846 - INVERTED.EXAMPLES_export/examples/powerdot-example_pdf (Failed)
>> >    2893 - INVERTED.EXAMPLES_export/examples/fr/exemple-powerdot_pdf 
>> > (Failed)

Now I see:

SuspiciousTests:
 # These started failing after we implemented tests for formats
 # that are in the complement set to the default format (7ecbb068).

So, maybe your format update in 2f4233721 solved it.
Or a texlive update solved a LaTeX bug.

...


>> Mind, that 

>>  MANUALS_export/doc/es/Tutorial_pdf5_TeXF

>> does not fail but has some wrong characters in the output!
>> (Problem with Spanish-Babel, Lua/XeTeX and TeX-fonts.)

>> Do we already have a category for this type of problems?

> Not yet.

Invert and suspend with sublabel "wrong-output"?



Günter

Reply via email to