2015-06-18 11:01 GMT+02:00 Kornel Benko :
> Until now we did not use polyglossia for luatex.
>
Erm, yes. I knew this.
Jürgen
Am Donnerstag, 18. Juni 2015 um 10:49:36, schrieb Jürgen Spitzmüller
> 2015-06-18 10:31 GMT+02:00 Scott Kostyshak:
>
> > OK, I will not push any further because I trust you on these issues much
> > more than myself since you know a lot more than I do and thus are best
> > positioned to balance t
On Thu, Jun 18, 2015 at 10:49:36AM +0200, Jürgen Spitzmüller wrote:
> 2015-06-18 10:31 GMT+02:00 Scott Kostyshak:
>
> > OK, I will not push any further because I trust you on these issues much
> > more than myself since you know a lot more than I do and thus are best
> > positioned to balance the
2015-06-18 10:31 GMT+02:00 Scott Kostyshak:
> OK, I will not push any further because I trust you on these issues much
> more than myself since you know a lot more than I do and thus are best
> positioned to balance the advantages against the disadvantages. I will
> just say two more things: altho
On Thu, Jun 18, 2015 at 10:17:15AM +0200, Jürgen Spitzmüller wrote:
> 2015-06-18 9:50 GMT+02:00 Scott Kostyshak :
>
> > > Not if they are set up properly.
> >
> > Do you think that the pre-requisites for triggering #9633 are rare?
> > That bug seems to have bit many of our own documents.
> >
>
>
2015-06-18 9:50 GMT+02:00 Scott Kostyshak :
> > Not if they are set up properly.
>
> Do you think that the pre-requisites for triggering #9633 are rare?
> That bug seems to have bit many of our own documents.
>
No, I mean that if the language package is properly set, the document will
continue to
On Tue, Jun 16, 2015 at 08:33:41AM +0200, Jürgen Spitzmüller wrote:
> 2015-06-16 1:23 GMT+02:00 Scott Kostyshak :
>
> > Am I correct
> > that the disadvantage of such a change is that the documents of users
> > might suddenly fail to compile?
> >
>
> Not if they are set up properly.
Do you think
On Thu, Jun 18, 2015 at 09:29:49AM +0200, Jürgen Spitzmüller wrote:
> 2015-06-18 8:18 GMT+02:00 Scott Kostyshak :
>
> > OK thanks for the explanation. Do we have a trac report for this? I
> > searched and could not find one.
> >
>
> I don't know. I was aware of the bug and remember we discussed i
2015-06-18 8:18 GMT+02:00 Scott Kostyshak :
> OK thanks for the explanation. Do we have a trac report for this? I
> searched and could not find one.
>
I don't know. I was aware of the bug and remember we discussed it already.
But maybe nobody bothered to file a ticket.
Jürgen
>
> Scott
>
On Wed, Jun 17, 2015 at 11:32:25AM +0200, Jürgen Spitzmüller wrote:
> 2015-06-17 11:03 GMT+02:00 Scott Kostyshak:
>
> > You are right. It does not. But it never has (as far as I recall).
> > However, before the polyglossia commit, it did work with LuaTeX. If I
> > understand correctly, you are say
Am Mittwoch, 17. Juni 2015 um 02:36:25, schrieb Scott Kostyshak
> On Tue, Jun 16, 2015 at 08:33:41AM +0200, Jürgen Spitzmüller wrote:
> > 2015-06-16 1:23 GMT+02:00 Scott Kostyshak :
> >
> > > On Sun, May 17, 2015 at 04:23:14PM +0200, Jürgen Spitzmüller wrote:
> > > > 2015-05-17 15:48 GMT+02:00 Ko
2015-06-17 11:03 GMT+02:00 Scott Kostyshak:
> You are right. It does not. But it never has (as far as I recall).
> However, before the polyglossia commit, it did work with LuaTeX. If I
> understand correctly, you are saying that because it does not work with
> XeTeX it is not a problem that export
On Wed, Jun 17, 2015 at 10:26:47AM +0200, Jürgen Spitzmüller wrote:
> 2015-06-17 8:36 GMT+02:00 Scott Kostyshak :
>
> > Are you sure? I only double-checked the first one you referenced
> > (eu_Additional_pdf5_systemF), but for me, the test is broken by the
> > polyglossia commit. I get the followi
2015-06-17 8:36 GMT+02:00 Scott Kostyshak :
> Are you sure? I only double-checked the first one you referenced
> (eu_Additional_pdf5_systemF), but for me, the test is broken by the
> polyglossia commit. I get the following error:
>
> ! LaTeX Error: \begin{otherlanguage} on input line 5994 ended by
On Tue, Jun 16, 2015 at 08:33:41AM +0200, Jürgen Spitzmüller wrote:
> 2015-06-16 1:23 GMT+02:00 Scott Kostyshak :
>
> > On Sun, May 17, 2015 at 04:23:14PM +0200, Jürgen Spitzmüller wrote:
> > > 2015-05-17 15:48 GMT+02:00 Kornel Benko :
> > >
> > > >
> > > Conclusio: LuaTeX + polyglossia introduces
On Tue, Jun 16, 2015 at 08:49:17AM +0200, Jürgen Spitzmüller wrote:
> 2015-06-16 8:33 GMT+02:00 Jürgen Spitzmüller :
>
> > Alas, I do not have time to check the other ones.
> >
>
> However, it would help a lot if you could check whether any of these
> documents fail for you with LuaTeX, but _not_
2015-06-16 8:33 GMT+02:00 Jürgen Spitzmüller :
> Alas, I do not have time to check the other ones.
>
However, it would help a lot if you could check whether any of these
documents fail for you with LuaTeX, but _not_ with XeTeX.
Jürgen
2015-06-16 1:23 GMT+02:00 Scott Kostyshak :
> On Sun, May 17, 2015 at 04:23:14PM +0200, Jürgen Spitzmüller wrote:
> > 2015-05-17 15:48 GMT+02:00 Kornel Benko :
> >
> > >
> > Conclusio: LuaTeX + polyglossia introduces no new problems in the tested
> > files.
>
> Jürgen, the commit broke the followi
2015-05-26 16:42 GMT+02:00 Kornel Benko :
> > So, shall I put it in?
> > (it seems to be the right moment now, to give it some testing before
> 2.2.0;
> > and it's a small change that can easily be reverted.)
> >
> > Jürgen
>
> +1
>
I've done that. Let's see...
Jürgen
>
> Kornel
Am Dienstag, 26. Mai 2015 um 16:38:44, schrieb Jürgen Spitzmüller
> 2015-05-17 16:23 GMT+02:00 Jürgen Spitzmüller:
>
> >
> > Conclusio: LuaTeX + polyglossia introduces no new problems in the tested
> > files.
> >
>
> So, shall I put it in?
> (it seems to be the right moment now, to give it some
2015-05-17 16:23 GMT+02:00 Jürgen Spitzmüller:
>
> Conclusio: LuaTeX + polyglossia introduces no new problems in the tested
> files.
>
So, shall I put it in?
(it seems to be the right moment now, to give it some testing before 2.2.0;
and it's a small change that can easily be reverted.)
Jürgen
2015-05-17 15:48 GMT+02:00 Kornel Benko :
>
> > Thank you. Could you also post a list of all files which fail to export
> > using polyglossia + XETEX + system fonts? This would allow to concentrate
> > on those who are not related to polyglossia, but the polyglossia/LuaTeX
> > couple.
>
> Sure, at
Am Sonntag, 17. Mai 2015 um 15:22:18, schrieb Jürgen Spitzmüller
> 2015-05-17 15:13 GMT+02:00 Kornel Benko:
>
> > For completeness, here the list of all files which fail to export using
> > polyglossia + lualatex + system fonts
> > doc/Customization.lyx
> > doc/Math.lyx
> >
2015-05-17 15:13 GMT+02:00 Kornel Benko:
> For completeness, here the list of all files which fail to export using
> polyglossia + lualatex + system fonts
> doc/Customization.lyx
> doc/Math.lyx
> doc/attic/eu/Additional.lyx
> doc/attic/eu/UserGuide.lyx
> doc
Am Sonntag, 17. Mai 2015 um 14:20:33, schrieb Jürgen Spitzmüller
> 2015-05-17 14:04 GMT+02:00 Jürgen Spitzmüller:
>
> > This does not work with XeTeX/polyglossia either, so I suspect the class
> > is not compatible with polyglossia.
> >
>
> The culprit is this definition in aastex.cls:
>
> \new
2015-05-17 14:24 GMT+02:00 Kornel Benko:
> Do we need a new entry in layout files?
> Like
> AllowsPolyglossia 0
>
Don't think so. For the classes that really rely on babel (and load it
internally), we have
Provides babel 1
The one in question rather calls for a bug report to the c
Am Sonntag, 17. Mai 2015 um 14:04:10, schrieb Jürgen Spitzmüller
> 2015-05-17 13:41 GMT+02:00 Kornel Benko :
>
> >
> > Ok, such cases can be corrected.
> >
>
> This is the correct code, IMHO:
>
> % increase link area for cross-references and autoname them,
> \AtBeginDocument{\renewcommand{\ref}
2015-05-17 14:04 GMT+02:00 Jürgen Spitzmüller:
> This does not work with XeTeX/polyglossia either, so I suspect the class
> is not compatible with polyglossia.
>
The culprit is this definition in aastex.cls:
\newcommand\notetoeditor[1]{%
\stepcounter{editornote}%
\begingroup
\def\protect{\no
2015-05-17 13:41 GMT+02:00 Kornel Benko :
>
> Ok, such cases can be corrected.
>
This is the correct code, IMHO:
% increase link area for cross-references and autoname them,
\AtBeginDocument{\renewcommand{\ref}[1]{\mbox{\autoref{#1}}}
\@ifundefined{extrasenglish}{}{%
\addto\extrasenglish{%
\ren
Am Sonntag, 17. Mai 2015 um 13:17:47, schrieb Jürgen Spitzmüller
> 2015-05-17 12:23 GMT+02:00 Jürgen Spitzmüller :
>
> > 2015-05-17 12:10 GMT+02:00 Scott Kostyshak :
> >
> >> > Summarizing it
> >> >
> >> > Your patch cures 12 tests which previously didn't pass. (they are
> >> flagged as INVERTED
2015-05-17 13:16 GMT+02:00 Kornel Benko:
> I refer only to the fact, that lualatex + polyglossia + tex fonts don't
> fail
> in our test cases.
>
Since polyglossia loads fontspec internally (and hence activates non-tex
fonts), there is not such a case than
lualatex + polyglossia + tex fonts
altho
2015-05-17 12:23 GMT+02:00 Jürgen Spitzmüller :
> 2015-05-17 12:10 GMT+02:00 Scott Kostyshak :
>
>> > Summarizing it
>> >
>> > Your patch cures 12 tests which previously didn't pass. (they are
>> flagged as INVERTED to pass)
>> > and has 21 new failing cases.
>> > All new failed cases use system f
Am Sonntag, 17. Mai 2015 um 13:12:00, schrieb Jürgen Spitzmüller
> 2015-05-17 12:54 GMT+02:00 Kornel Benko:
>
> > We could enable polyglossia for tex fonts.
> >
>
> I do not understand how this solves the failing tests.
> Also, note that polyglossia relies on fontspec and thus is not intended to
2015-05-17 12:54 GMT+02:00 Kornel Benko:
> We could enable polyglossia for tex fonts.
>
I do not understand how this solves the failing tests.
Also, note that polyglossia relies on fontspec and thus is not intended to
be used with tex fonts.
Jürgen
Am Sonntag, 17. Mai 2015 um 12:23:09, schrieb Jürgen Spitzmüller
> 2015-05-17 12:10 GMT+02:00 Scott Kostyshak :
>
> > > Summarizing it
> > >
> > > Your patch cures 12 tests which previously didn't pass. (they are
> > flagged as INVERTED to pass)
> > > and has 21 new failing cases.
> > > All new f
2015-05-17 12:10 GMT+02:00 Scott Kostyshak :
> > Summarizing it
> >
> > Your patch cures 12 tests which previously didn't pass. (they are
> flagged as INVERTED to pass)
> > and has 21 new failing cases.
> > All new failed cases use system fonts (cases with latex fonts pass).
> >
> > Examples are d
On Sun, May 17, 2015 at 6:03 AM, Kornel Benko wrote:
>
> The following tests FAILED:
> 1644 - export/examples/FeynmanDiagrams_pdf5_texF (Failed)
> 1645 - export/examples/FeynmanDiagrams_pdf5_systemF (Failed)
> 2793 - export/examples/de/FeynmanDiagrams_pdf5_texF (Failed)
>
Am Sonntag, 17. Mai 2015 um 11:37:47, schrieb Jürgen Spitzmüller
> 2015-05-17 11:31 GMT+02:00 Kornel Benko :
>
> >
> > Tested with
> > # ctest -j8 -R 'export.*pdf5'
> > -->
> > 92% tests passed, 51 tests failed out of 620
> >
> > 12 tests failed because they are INVERTED, that is
2015-05-17 11:31 GMT+02:00 Kornel Benko :
>
> Tested with
> # ctest -j8 -R 'export.*pdf5'
> -->
> 92% tests passed, 51 tests failed out of 620
>
> 12 tests failed because they are INVERTED, that is good, since they
> actually pass.
> 1112 - INVERTED_SEE-README.ctest_export/
Am Sonntag, 17. Mai 2015 um 10:20:36, schrieb Jürgen Spitzmüller
> 2015-05-17 2:06 GMT+02:00 Scott Kostyshak:
>
> > Would it be helpful to run our export tests on our documents with
> > LuaTeX and polyglossia? I do not know when I would take the time to do
> > this, but just curious if the result
2015-05-17 2:06 GMT+02:00 Scott Kostyshak:
> Would it be helpful to run our export tests on our documents with
> LuaTeX and polyglossia? I do not know when I would take the time to do
> this, but just curious if the result would be interesting to you.
>
Sure.
Jürgen
>
> Scott
>
On Sat, May 16, 2015 at 8:18 AM, Jürgen Spitzmüller wrote:
> Polyglossia also supports LuaTeX since some time (at least as of 2014/05/21
> v1.33.5).
>
> Should we reflect this in LyX 2.2 (see attached patch)?
Would it be helpful to run our export tests on our documents with
LuaTeX and polyglossia
42 matches
Mail list logo
