On Sat, Feb 13, 2016 at 08:54:57PM +0000, Guenter Milde wrote:
> On 2016-02-13, Scott Kostyshak wrote:
> > On Tue, Oct 20, 2015 at 07:16:44PM +0200, Günter Milde wrote:
> >> commit 1523fc6023440f10ca0d82a681ded5c060d8fd33
> >> Author: Günter Milde <mi...@lyx.org>
> >> Date:   Tue Oct 20 19:14:39 2015 +0200
> 
> >>     Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems".
> 
> >>     Fixes output for 3 of the 4 test lyx-files.
> 
> >>     Includes "FIXME"s at places where further action is required to get 
> >> the XeTeX
> >>     export right but I don't know how.
> 
> > After this commit, when I run the command
> 
> >   lyx -e luatex lib/doc/he/Intro.lyx
> 
> > it either fails to produce Intro.tex or (on current master) it produces
> > a Intro.tex with gibberish where there should be Hebrew (at least this
> > is what Vim shows me).
> 
> Are you sure this has to do with this (partial) fix?

No. I did a git bisect that led me to this commit, but there were
various types of "failing" which makes me less confident that the
problem was linear and thus less likely the bisect works. By multiple
types of failings, I mean that either the Intro.tex file would not even
be created or it would but would not contain Hebrew. So I would not be
too surprised if the git bisect worked. I can do a manual check (compile
just before), but first I want to check if something is indeed wrong.

> In suspiciousTests, I see:
> 
> # Hebrew docs do not currently work with LuaTeX (will be fixed in
> TeXLive-16) # TODO: set working system fonts in the lyx sources
> export/.*/he/.*(dvi3|pdf5).*
> 
> > Is this expected? 
> 
> So, until further notice of a fix, I expect problems with Hebrew and
> LuaTeX with both, tex- and unicode-fonts.
> 
> > I know you put FIXMEs and one of them talks about ASCII encoding, so
> > I'm guessing it is indeed expected, but I want to make sure. 
> 
> ASCII is required for XeTeX, LuaTeX can work with encoded source using
> luainputenc.
> 
> > If it is expected, do we have a bug report?
> 
> No, as Luatex+Hebrew failing is an upstream bug.

But I am just talking about exporting to .tex and opening in a text
editor. LuaTeX does not even have a chance if our export to .tex
corrupts the Hebrew. To be clear, attached are splash_good.tex and
splash_bad.tex. Do you think it is OK that we now produce splash_bad.tex
and before we produced splash_good.tex? If you tell me this is fine and
that there is no encoding issue, then I trust your judgment since I
know nothing about encoding.

Scott

Attachment: splash_good.tex
Description: TeX document

Attachment: splash_bad.tex
Description: TeX document

Attachment: signature.asc
Description: PGP signature

Reply via email to