Re: [LyX/master] ctests: update inversion patterns.

[Kornel Benko]

Am Donnerstag, 23. Februar 2017 um 10:16:59, schrieb Jürgen Spitzmüller 

> Am Dienstag, den 21.02.2017, 12:01 +0100 schrieb Kornel Benko:
> > But now fails also (which previously passed)
> > 301 - export/export/latex/arabic_simple_pdf4_systemF (Failed)
> > Missing character: There is no ∗ in font
> > Scheherazade/OT:script=arab;language=DFLT;mapping=tex-text;!
> > 1771 - export/doc/ar/Intro_pdf4_systemF (Failed)
> > Missing character: There is no ∗ in font
> > Scheherazade/OT:script=arab;language=DFLT;mapping=tex-text;!
> 
> This one seems fixed with recent TL.

Confirmed.

> But there is another error with arabic and LuaTeX (don't if it it has
> been there before).

Yes, it was already included in invertedTests:104

> Jürgen

Kornel


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

Re: [LyX/master] ctests: update inversion patterns.

[Jürgen Spitzmüller]

Am Dienstag, den 21.02.2017, 12:01 +0100 schrieb Kornel Benko:
> But now fails also (which previously passed)
>   301 - export/export/latex/arabic_simple_pdf4_systemF (Failed)
>   Missing character: There is no ∗ in font
> Scheherazade/OT:script=arab;language=DFLT;mapping=tex-text;!
>   1771 - export/doc/ar/Intro_pdf4_systemF (Failed)
>   Missing character: There is no ∗ in font
> Scheherazade/OT:script=arab;language=DFLT;mapping=tex-text;!

This one seems fixed with recent TL.

But there is another error with arabic and LuaTeX (don't if it it has
been there before).

Jürgen

> 
>   Kornel

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

Re: [LyX/master] ctests: update inversion patterns.

[Scott Kostyshak]

On Wed, Feb 22, 2017 at 11:22:11AM +0100, Kornel Benko wrote:
> Am Mittwoch, 22. Februar 2017 um 10:56:53, schrieb Jürgen Spitzmüller 
> 
> > Am Mittwoch, den 22.02.2017, 10:18 +0100 schrieb Kornel Benko:
> > > Now I am confused. What is your proposal?
> > >   a.) Add these tests to the chain of "missing glyph"
> > 
> > This.
> 
> Good. Will do it. Please don't forget to apply your patch for 
> src/BufferParams.cpp.

I had already forgot about this possibility. This is indeed much better
than inverted.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] ctests: update inversion patterns.

[Jürgen Spitzmüller]

Am Mittwoch, den 22.02.2017, 11:22 +0100 schrieb Kornel Benko:
> Good. Will do it. Please don't forget to apply your patch for
> src/BufferParams.cpp.

Done now.

Jürgen

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

Re: [LyX/master] ctests: update inversion patterns.

[Kornel Benko]

Am Mittwoch, 22. Februar 2017 um 10:56:53, schrieb Jürgen Spitzmüller 

> Am Mittwoch, den 22.02.2017, 10:18 +0100 schrieb Kornel Benko:
> > Now I am confused. What is your proposal?
> > a.) Add these tests to the chain of "missing glyph"
> 
> This.

Good. Will do it. Please don't forget to apply your patch for 
src/BufferParams.cpp.

Kornel

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

Re: [LyX/master] ctests: update inversion patterns.

[Jürgen Spitzmüller]

Am Mittwoch, den 22.02.2017, 10:18 +0100 schrieb Kornel Benko:
> Now I am confused. What is your proposal?
>   a.) Add these tests to the chain of "missing glyph"

This.

> or
>   b.) Add code to the preamble of the two files
> ?

This was just an explanation of the problem (as far as I understand
it).

Jürgen

> 
> > Jürgen
> > 
> > > 
> > > Scott
> 
>   Kornel

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

Re: [LyX/master] ctests: update inversion patterns.

[Kornel Benko]

Am Mittwoch, 22. Februar 2017 um 09:37:54, schrieb Jürgen Spitzmüller 

> Am Dienstag, den 21.02.2017, 10:35 -0500 schrieb Scott Kostyshak:
> > If you think your patch is a step forward, and these tests were just
> > passing by chance before, then in my opinion the correct way to
> > proceed
> > is to apply your patch and invert these two tests. 
> 
> OK. Note that the two tests need not to be inverted. Since it is just a
> "missing glyph" problem, we can include them in the chain that ignores
> missing glyphs errors.

That would have been my suggestion too.

> > Can you perhaps add
> > some information on why you these two tests are expected to have
> > problems with xunicode? We can add this information where we invert
> > the
> > tests. By adding comments in invertedTests file, we can easily see
> > why
> > certain tests are inverted.
> 
> They do not have problems with xunicode, but without. The reason is
> that the asterisk glyph is not included in the arabic font
> (Scheherazade), but apparently, xunicode defines an extra asterisk
> glyph (for a different purpose) that is being used here. Clearly the
> problem should be fixed somewhere else. A workaround is to redefine the
> thanks command and to use \ast instead of the plain *:
> 
> \renewcommand*{\@fnsymbol}[1]{\ensuremath{\ifcase#1\or \ast\or   
>   \dagger\or \ddagger\or\mathsection\or \mathparagraph\or \|\or 
>   \ast\ast\or \dagger\dagger\or \ddagger\ddagger \else\@ctrerr\fi}}

Now I am confused. What is your proposal?
a.) Add these tests to the chain of "missing glyph"
or
b.) Add code to the preamble of the two files
?

> Jürgen
> 
> > 
> > Scott

Kornel

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

Re: [LyX/master] ctests: update inversion patterns.

[Jürgen Spitzmüller]

Am Dienstag, den 21.02.2017, 10:35 -0500 schrieb Scott Kostyshak:
> If you think your patch is a step forward, and these tests were just
> passing by chance before, then in my opinion the correct way to
> proceed
> is to apply your patch and invert these two tests. 

OK. Note that the two tests need not to be inverted. Since it is just a
"missing glyph" problem, we can include them in the chain that ignores
missing glyphs errors.

> Can you perhaps add
> some information on why you these two tests are expected to have
> problems with xunicode? We can add this information where we invert
> the
> tests. By adding comments in invertedTests file, we can easily see
> why
> certain tests are inverted.

They do not have problems with xunicode, but without. The reason is
that the asterisk glyph is not included in the arabic font
(Scheherazade), but apparently, xunicode defines an extra asterisk
glyph (for a different purpose) that is being used here. Clearly the
problem should be fixed somewhere else. A workaround is to redefine the
thanks command and to use \ast instead of the plain *:

\renewcommand*{\@fnsymbol}[1]{\ensuremath{\ifcase#1\or \ast\or   
  \dagger\or \ddagger\or\mathsection\or \mathparagraph\or \|\or 
  \ast\ast\or \dagger\dagger\or \ddagger\ddagger \else\@ctrerr\fi}}

Jürgen

> 
> Scott

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

Re: [LyX/master] ctests: update inversion patterns.

[Scott Kostyshak]

On Tue, Feb 21, 2017 at 12:46:14PM +0100, Jürgen Spitzmüller wrote:

> > But now fails also (which previously passed)
> > 301 - export/export/latex/arabic_simple_pdf4_systemF (Failed)
> > Missing character: There is no ∗ in font
> > Scheherazade/OT:script=arab;language=DFLT;mapping=tex-text;!
> > 1771 - export/doc/ar/Intro_pdf4_systemF (Failed)
> > Missing character: There is no ∗ in font
> > Scheherazade/OT:script=arab;language=DFLT;mapping=tex-text;!
> 
> This is the star from the thanks footnote. Not sure what to do about
> that. AFAICS the fact that this works with xunicode is just a pure
> coincidence.

If you think your patch is a step forward, and these tests were just
passing by chance before, then in my opinion the correct way to proceed
is to apply your patch and invert these two tests. Can you perhaps add
some information on why you these two tests are expected to have
problems with xunicode? We can add this information where we invert the
tests. By adding comments in invertedTests file, we can easily see why
certain tests are inverted.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] ctests: update inversion patterns.

[Scott Kostyshak]

On Tue, Feb 21, 2017 at 02:15:08PM +0100, Jürgen Spitzmüller wrote:
> Am Dienstag, den 21.02.2017, 12:57 +0100 schrieb Kornel Benko:
> > Sure, because 'inverted' means "invert the test result".
> > This means, the tests actually passed. This was previously not the
> > case.
> 
> I see. Thanks.

For exports that fail, we do not want to keep them as is because the
output of running all the tests will be confusing (e.g. "wait, did that
test fail before or is it a new failure?") and it will be more difficult
to see what is a regression.

If we just omit the failing export from running (which we can do, see
ignoredTests file), then we won't know if the export goes from failing
to passing. By "inverting" it, we solve this problem: the test
technically passes (although the name indicates that the export
actually fails) so it does not complicate the output, and if the
inverted test "fails", we will see it because it shows up in our failing
test results.

Thus, once we see that we cannot easily fix the underlying cause of a
failed export, we document why the test fails and invert it.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] ctests: update inversion patterns.

[Jürgen Spitzmüller]

Am Dienstag, den 21.02.2017, 12:57 +0100 schrieb Kornel Benko:
> Sure, because 'inverted' means "invert the test result".
> This means, the tests actually passed. This was previously not the
> case.

I see. Thanks.

Jürgen

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

Re: [LyX/master] ctests: update inversion patterns.

[Kornel Benko]

Am Dienstag, 21. Februar 2017 um 12:46:14, schrieb Jürgen Spitzmüller 

> Am Dienstag, den 21.02.2017, 12:01 +0100 schrieb Kornel Benko:
> > With applied patch and current master (cdc9176 Add some notes about
> > ipa with fontspec.)
> > Tested on all pdf* and dvi* exports. Following tests fail
> > 2196 - INVERTED.TEXISSUES_export/doc/es/UserGuide_dvi3_systemF
> > (Failed)
> > 2203 - INVERTED.TEXISSUES_export/doc/es/UserGuide_pdf5_systemF
> > (Failed)
> > 3443 -
> > INVERTED.TEXISSUES_export/examples/linguistics_dvi3_systemF (Failed)
> > 3450 -
> > INVERTED.TEXISSUES_export/examples/linguistics_pdf5_systemF (Failed)
> > 4446 -
> > INVERTED.TEXISSUES_export/examples/de/linguistics_dvi3_systemF
> > (Failed)
> > 4453 -
> > INVERTED.TEXISSUES_export/examples/de/linguistics_pdf5_systemF
> > (Failed)
> > 4629 -
> > INVERTED.TEXISSUES_export/examples/es/linguistics_dvi3_systemF
> > (Failed)
> > 4636 -
> > INVERTED.TEXISSUES_export/examples/es/linguistics_pdf5_systemF
> > (Failed)
> > 4923 -
> > INVERTED.TEXISSUES_export/examples/fr/linguistics_dvi3_systemF
> > (Failed)
> > 4930 -
> > INVERTED.TEXISSUES_export/examples/fr/linguistics_pdf5_systemF
> > (Failed)
> > This is OK, they can be removed from invertedTests.
> 
> Can you elaborate why this is OK?

Sure, because 'inverted' means "invert the test result".
This means, the tests actually passed. This was previously not the case.

Kornel

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

Re: [LyX/master] ctests: update inversion patterns.

[Jürgen Spitzmüller]

Am Dienstag, den 21.02.2017, 12:01 +0100 schrieb Kornel Benko:
> With applied patch and current master (cdc9176 Add some notes about
> ipa with fontspec.)
> Tested on all pdf* and dvi* exports. Following tests fail
>   2196 - INVERTED.TEXISSUES_export/doc/es/UserGuide_dvi3_systemF
> (Failed)
>   2203 - INVERTED.TEXISSUES_export/doc/es/UserGuide_pdf5_systemF
> (Failed)
>   3443 -
> INVERTED.TEXISSUES_export/examples/linguistics_dvi3_systemF (Failed)
>   3450 -
> INVERTED.TEXISSUES_export/examples/linguistics_pdf5_systemF (Failed)
>   4446 -
> INVERTED.TEXISSUES_export/examples/de/linguistics_dvi3_systemF
> (Failed)
>   4453 -
> INVERTED.TEXISSUES_export/examples/de/linguistics_pdf5_systemF
> (Failed)
>   4629 -
> INVERTED.TEXISSUES_export/examples/es/linguistics_dvi3_systemF
> (Failed)
>   4636 -
> INVERTED.TEXISSUES_export/examples/es/linguistics_pdf5_systemF
> (Failed)
>   4923 -
> INVERTED.TEXISSUES_export/examples/fr/linguistics_dvi3_systemF
> (Failed)
>   4930 -
> INVERTED.TEXISSUES_export/examples/fr/linguistics_pdf5_systemF
> (Failed)
> This is OK, they can be removed from invertedTests.

Can you elaborate why this is OK?

> But now fails also (which previously passed)
>   301 - export/export/latex/arabic_simple_pdf4_systemF (Failed)
>   Missing character: There is no ∗ in font
> Scheherazade/OT:script=arab;language=DFLT;mapping=tex-text;!
>   1771 - export/doc/ar/Intro_pdf4_systemF (Failed)
>   Missing character: There is no ∗ in font
> Scheherazade/OT:script=arab;language=DFLT;mapping=tex-text;!

This is the star from the thanks footnote. Not sure what to do about
that. AFAICS the fact that this works with xunicode is just a pure
coincidence.

Jürgen

> 
>   Kornel

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

Re: [LyX/master] ctests: update inversion patterns.

[Kornel Benko]

Am Dienstag, 21. Februar 2017 um 09:49:55, schrieb Jürgen Spitzmüller 

> Am Dienstag, den 21.02.2017, 09:12 +0100 schrieb Jürgen Spitzmüller:
> > > Sounds good to me.
> > 
> > I'll have a go at that.
> 
> Could you try the attached patch? This should be tested against all
> test files, since it omits loading of xunicode if tipa is not required.
> 
> Thanks
> Jürgen

With applied patch and current master (cdc9176 Add some notes about ipa with 
fontspec.)
Tested on all pdf* and dvi* exports. Following tests fail
2196 - INVERTED.TEXISSUES_export/doc/es/UserGuide_dvi3_systemF (Failed)
2203 - INVERTED.TEXISSUES_export/doc/es/UserGuide_pdf5_systemF (Failed)
3443 - INVERTED.TEXISSUES_export/examples/linguistics_dvi3_systemF 
(Failed)
3450 - INVERTED.TEXISSUES_export/examples/linguistics_pdf5_systemF 
(Failed)
4446 - INVERTED.TEXISSUES_export/examples/de/linguistics_dvi3_systemF 
(Failed)
4453 - INVERTED.TEXISSUES_export/examples/de/linguistics_pdf5_systemF 
(Failed)
4629 - INVERTED.TEXISSUES_export/examples/es/linguistics_dvi3_systemF 
(Failed)
4636 - INVERTED.TEXISSUES_export/examples/es/linguistics_pdf5_systemF 
(Failed)
4923 - INVERTED.TEXISSUES_export/examples/fr/linguistics_dvi3_systemF 
(Failed)
4930 - INVERTED.TEXISSUES_export/examples/fr/linguistics_pdf5_systemF 
(Failed)
This is OK, they can be removed from invertedTests.

But now fails also (which previously passed)
301 - export/export/latex/arabic_simple_pdf4_systemF (Failed)
Missing character: There is no ∗ in font 
Scheherazade/OT:script=arab;language=DFLT;mapping=tex-text;!
1771 - export/doc/ar/Intro_pdf4_systemF (Failed)
Missing character: There is no ∗ in font 
Scheherazade/OT:script=arab;language=DFLT;mapping=tex-text;!

Kornel

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

Re: [LyX/master] ctests: update inversion patterns.

[Jürgen Spitzmüller]

Am Dienstag, den 21.02.2017, 09:12 +0100 schrieb Jürgen Spitzmüller:
> > Sounds good to me.
> 
> I'll have a go at that.

Could you try the attached patch? This should be tested against all
test files, since it omits loading of xunicode if tipa is not required.

Thanks
Jürgendiff --git a/src/BufferParams.cpp b/src/BufferParams.cpp
index a4c3a80dc1..a725068792 100644
--- a/src/BufferParams.cpp
+++ b/src/BufferParams.cpp
@@ -2176,12 +2176,19 @@ bool BufferParams::writeLaTeX(otexstream & os, LaTeXFeatures & features,
 		os << "}\n";
 	}
 
-	// xunicode needs to be loaded at least after amsmath, amssymb,
+	// xunicode only needs to be loaded if tipa is used
+	// (the rest is obsoleted by the new TU encoding).
+	// It needs to be loaded at least after amsmath, amssymb,
 	// esint and the other packages that provide special glyphs
-	// The package only supports XeTeX currently.
-	if (features.runparams().flavor == OutputParams::XETEX
-	&& useNonTeXFonts)
+	if (features.mustProvide("tipa") && useNonTeXFonts) {
+		// The package officially only supports XeTeX, but also works
+		// with LuaTeX. Thus we work around its XeTeX test.
+		if (features.runparams().flavor != OutputParams::XETEX) {
+			os << "% Pretend to xunicode that we are XeTeX\n"
+			   << "\\def\\XeTeXpicfile{}\n";
+		}
 		os << "\\usepackage{xunicode}\n";
+	}
 
 	// Polyglossia must be loaded last ...
 	if (use_polyglossia) {


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

Re: [LyX/master] ctests: update inversion patterns.

[Jürgen Spitzmüller]

Am Dienstag, den 21.02.2017, 02:34 -0500 schrieb Scott Kostyshak:
> On Tue, Feb 21, 2017 at 08:00:45AM +0100, Jürgen Spitzmüller wrote:
> > Am Montag, den 20.02.2017, 20:45 -0500 schrieb Scott Kostyshak:
> > At the moment, option 2 seems the preferable workaround to me.
> 
> Sounds good to me.

I'll have a go at that.

> > > Perhaps we have to do load the tipa package if \textipa is not
> > > defined?
> > > This might work on both old and new TeX Live.
> > 
> > No, TIPA does not work with fontspec.
> 
> I'm glad you are around to stop me from experimenting like this
> without
> knowing what I'm doing.
> 
> Thank you for this detailed explanation! We should link to this email
> in
> our ctests (although hopefully it will be fixed and we can remove the
> inversion).

I have filed a report at fontspec (although this is probably not the
right address):
https://github.com/wspr/fontspec/issues/280

Jürgen

> 
> Scott

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

Re: [LyX/master] ctests: update inversion patterns.

[Scott Kostyshak]

On Tue, Feb 21, 2017 at 08:00:45AM +0100, Jürgen Spitzmüller wrote:
> Am Montag, den 20.02.2017, 20:45 -0500 schrieb Scott Kostyshak:

> At the moment, option 2 seems the preferable workaround to me.

Sounds good to me.

> > Perhaps we have to do load the tipa package if \textipa is not
> > defined?
> > This might work on both old and new TeX Live.
> 
> No, TIPA does not work with fontspec.

I'm glad you are around to stop me from experimenting like this without
knowing what I'm doing.

Thank you for this detailed explanation! We should link to this email in
our ctests (although hopefully it will be fixed and we can remove the
inversion).

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] ctests: update inversion patterns.

[Jürgen Spitzmüller]

Am Montag, den 20.02.2017, 20:45 -0500 schrieb Scott Kostyshak:
> On Wed, Feb 15, 2017 at 09:23:19AM +, Guenter Milde wrote:
> 
> > Missing \textipa could be intentional -- maybe this is "outsourced"
> > to a
> > Luatex package (for XeTeX, \textipa support is in xunicode.sty). 
> 
> Jürgen, do you have an idea? To reproduce on an updated TeX
> Live, compile the linguistics manual with LuaTeX and system fonts.

The reason is this. Up to v. 2.6, fontspec internally loaded xunicode
which defines the tipa environments. Although xunicode is only written
for XeTeX and terminates with a warning if XeTeX is not used, fontspec
pretended that XeTeX is used also for LuaTeX, by cheating on xunicode's
test (it just tests whether \XeTeXpicfile is defined. If it is, XeTeX
is assumed).

As of fontspec 2.6 and the introduction of the new TU font encodings,
xunicode is no longer loaded. Why does TIPA work nevertheless for us
with XeTeX? Since we (LyX) load xunicode ourselves for XeTeX+fontspec
(which we probably should not do anymore).

Workarounds:

1. Load fontspec with the "euenc" option. This loads the old
experimental unicode encodings (EU1 for XeTeX, EU2 for LuaTeX). This
also loads fontspec. The drawback is that the new TU encodings are not
used.

2. Load xunicode if TIPA is required. For LuaTeX, just do what fontspec
did -- cheat xunicode:

\def\XeTeXpicfile{}
\usepackage{xunicode}

This might break at some point (I don't know whether and where TU
encoding and xunicode will clash).

At the moment, option 2 seems the preferable workaround to me.

A real fix needs to be done upstream. I suppose a package specifically
for tipa with fontspec (derived from xunicode) or, even better, an
integration into the tipa package, would be desired. However, tipa has
not seen updates for a long time (it does not include all glyphs from
recent IPA revisions), so it is not very likely.

Note also that xunicode's tipa support has some flaws. For instance
\textbottomtiebar does not really work, as seen in the linguistics
manual (first IPA chunk).

> Perhaps we have to do load the tipa package if \textipa is not
> defined?
> This might work on both old and new TeX Live.

No, TIPA does not work with fontspec.

Jürgen

> 
> Scott

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

Re: [LyX/master] ctests: update inversion patterns.

[Scott Kostyshak]

On Wed, Feb 15, 2017 at 09:23:19AM +, Guenter Milde wrote:

> Missing \textipa could be intentional -- maybe this is "outsourced" to a
> Luatex package (for XeTeX, \textipa support is in xunicode.sty). 

Jürgen, do you have an idea? To reproduce on an updated TeX
Live, compile the linguistics manual with LuaTeX and system fonts.

Perhaps we have to do load the tipa package if \textipa is not defined?
This might work on both old and new TeX Live.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] ctests: update inversion patterns.

[Scott Kostyshak]

On Wed, Feb 15, 2017 at 09:23:19AM +, Guenter Milde wrote:

> No, I did not even find out where to report...
> So, if you want to take aktion I would be glad.

No thanks :)

> Anyway, the Babel-bug is low priority, as using Xe/LuaTeX with 8-bit
> fonts is a rare cornercase. Also, the simple and obvious workaround is to
> set the input encoding to utf8.

Makes sense.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] ctests: update inversion patterns.

[Guenter Milde]

On 2017-02-15, Scott Kostyshak wrote:
> On Tue, Feb 14, 2017 at 10:34:25PM +0100, Günter Milde wrote:
>> commit b863fb0723104bf702e4b4d8b967a7ce0c2255b5
>> Author: Günter Milde 
>> Date:   Tue Feb 14 22:31:12 2017 +0100

>> ctests: update inversion patterns.

>> The new TeXLive uses font encoding TU for Unicode fonts with Xe- and 
>> LuaTeX.
>> The command \textquotedbl for straight quotes is no longer supported,
>> \textipa no longer supported with LuaTeX.

Missing \textquotedbl is clearly a bug as this is the standard way to get
straight double quotes with fonts supporting the "TeX ligatures".

Missing \textipa could be intentional -- maybe this is "outsourced" to a
Luatex package (for XeTeX, \textipa support is in xunicode.sty). 


>> Problems with Spanish Babel and Xe/LuaTeX with 8-bit fonts lead to new 
>> errors
>> in some cases.

> Did you by chance file a bug report? If so, we should link to it in the
> invertedTests comments.

No, I did not even find out where to report...
So, if you want to take aktion I would be glad.

Anyway, the Babel-bug is low priority, as using Xe/LuaTeX with 8-bit
fonts is a rare cornercase. Also, the simple and obvious workaround is to
set the input encoding to utf8.

We could simply *ignore* all Russian, Ukrainean, and Spanish documents with
.*_texF because they produce either wrong output or fail.

In the long run, LyX should use utf8 as default inputenc for these languages.



Thanks,

Günter

Re: [LyX/master] ctests: update inversion patterns.

[Scott Kostyshak]

On Tue, Feb 14, 2017 at 10:34:25PM +0100, Günter Milde wrote:
> commit b863fb0723104bf702e4b4d8b967a7ce0c2255b5
> Author: Günter Milde 
> Date:   Tue Feb 14 22:31:12 2017 +0100
> 
> ctests: update inversion patterns.
> 
> The new TeXLive uses font encoding TU for Unicode fonts with Xe- and 
> LuaTeX.
> The command \textquotedbl for straight quotes is no longer supported,
> \textipa no longer supported with LuaTeX.
> Problems with Spanish Babel and Xe/LuaTeX with 8-bit fonts lead to new 
> errors
> in some cases.

Did you by chance file a bug report? If so, we should link to it in the
invertedTests comments.

Scott


signature.asc
Description: PGP signature