Re: doc/ar/Shortcuts.lyx uncompilable
Am Montag, den 10.09.2018, 14:00 +0200 schrieb Kornel Benko: > Thanks Jürgen. Using the listings-backup with > # tlmgr restore listings 37534 > and your latest commit, the Arabic files are now compilable again. and fixed upstream with new bidi release: https://sourceforge.net/p/persian-tex-dist/tickets/9/ Jürgen > > Kornel signature.asc Description: This is a digitally signed message part
Re: doc/ar/Shortcuts.lyx uncompilable
Am Montag, 10. September 2018 12:42:40 CEST schrieb Jürgen Spitzmüller : > Am Sonntag, den 09.09.2018, 11:37 +0200 schrieb Kornel Benko: > > > Bisect leads to 2d4ac90f. > > > > > > Scott > > > > > > > I got something different: > > 652ca5f578c1 > > There are two issues involved. One is a consequence of 2d4ac90f. This > should be fixed now. > > The other one is caused by the latest listings update in TL 2018. It > seems this is not compatible with bidi-listings. Reverting the listings > update (via tlmgr or tlcockpit) solves the issue. I fear we need to > hope for a fix in bidi (I just dropped them a note). > > Jürgen > Thanks Jürgen. Using the listings-backup with # tlmgr restore listings 37534 and your latest commit, the Arabic files are now compilable again. Kornel signature.asc Description: This is a digitally signed message part.
Re: doc/ar/Shortcuts.lyx uncompilable
Am Sonntag, den 09.09.2018, 11:37 +0200 schrieb Kornel Benko: > > Bisect leads to 2d4ac90f. > > > > Scott > > > > I got something different: > 652ca5f578c1 There are two issues involved. One is a consequence of 2d4ac90f. This should be fixed now. The other one is caused by the latest listings update in TL 2018. It seems this is not compatible with bidi-listings. Reverting the listings update (via tlmgr or tlcockpit) solves the issue. I fear we need to hope for a fix in bidi (I just dropped them a note). Jürgen signature.asc Description: This is a digitally signed message part
Re: doc/ar/Shortcuts.lyx uncompilable
Am Samstag, 8. September 2018 20:04:53 CEST schrieb Scott Kostyshak : > On Sat, Sep 08, 2018 at 06:51:09PM -0400, Scott Kostyshak wrote: > > On Sat, Sep 08, 2018 at 04:29:38PM +0200, Kornel Benko wrote: > > > I was unable to find the reason. > > > > I can reproduce. I can do a bisect if it would help. > > Bisect leads to 2d4ac90f. > > Scott > I got something different: 652ca5f578c1b4854a12833da50ea31e37ac552e is the first bad commit Nonetheless, attached a minimal example (from Shortcuts.lyx) behaving wrong. Removing the listings part it compiles. Kornel ar_listings_error.lyx Description: application/lyx signature.asc Description: This is a digitally signed message part.
Re: doc/ar/Shortcuts.lyx uncompilable
On Sat, Sep 08, 2018 at 06:51:09PM -0400, Scott Kostyshak wrote: > On Sat, Sep 08, 2018 at 04:29:38PM +0200, Kornel Benko wrote: > > I was unable to find the reason. > > I can reproduce. I can do a bisect if it would help. Bisect leads to 2d4ac90f. Scott signature.asc Description: PGP signature
Re: doc/ar/Shortcuts.lyx uncompilable
On Sat, Sep 08, 2018 at 04:29:38PM +0200, Kornel Benko wrote: > I was unable to find the reason. I can reproduce. I can do a bisect if it would help. Thanks for all of your help checking the tests, Kornel. I have been ignoring them. I would like to get back in the habit of regularly running the tests. Scott signature.asc Description: PGP signature
doc/ar/Shortcuts.lyx uncompilable
I was unable to find the reason.
Apart from 'Missing glyph', there are also some messages like
! Package Listings Error: direction textdirection unknown.
l.43 ...ror{Listings}{direction #1 unknown}\@ehc}}
...
Missing character: There is no
in font Scheherazade/OT:script=latn;language=DFLT;mapping=tex-text;!
! Argument of \@gobble has an extra }.
\par
l.34 \setdefaultlanguage{arabic}
I've run across a `}' that doesn't seem to match anything.
For example, `\def\a#1{...}' and `\a}' would produce
this error. If you simply proceed now, the `\par' that
I've just inserted will cause me to report a runaway
argument that might be the root of the problem. But if
your `}' was spurious, just type `2' and it will go away.
Runaway argument?
! Paragraph ended before \@gobble was complete.
...
Missing character: There is no
in font Scheherazade/OT:script=latn;language=DFLT;mapping=tex-text;!
Missing character: There is no
in font Scheherazade/OT:script=latn;language=DFLT;mapping=tex-text;!
! Argument of \lst@MakeCaption has an extra }.
\par
l.42 \begin{document}
..
ar/UserGuide.lyx shows different symptoms, and is at least able to create a pdf.
Argument of \verbatim@ has an extra }.
\par
l.3762 }
I suspect you've forgotten a `}', causing me to apply this
control sequence to too much text. How can we recover?
My plan is to forget the whole thing and hope for the best.
...
! Extra }, or forgotten \endgroup.
\@ensure@LTR #1->\if@RTL \LRE {#1}
\else #1\fi
l.3762 }
...
[202])
! Emergency stop.
<*> UserGuide.tex
*** (job aborted, no legal \end found)
..
Kornel
signature.asc
Description: This is a digitally signed message part.
