Re: beta2?

[Georg Baum]

Scott Kostyshak wrote:

> I agree that it would be nice to remove unnecessary files. As far as
> figuring out which files are unnecessary, I volunteer to take any
> experimental patch, build a tar ball, and send it to Uwe to see if he
> has time to build the test tar ball so we can see if he gets an error.

The files are already missing from the beta2 tarball (because they are not 
listed in Makefile.am). If Uwe can build from it, we can remove them from 
git.


Georg

Re: beta2?

[Peter Kümmel]

Am 13.02.2016 um 10:57 schrieb Georg Baum:

Scott Kostyshak wrote:


I agree that it would be nice to remove unnecessary files. As far as
figuring out which files are unnecessary, I volunteer to take any
experimental patch, build a tar ball, and send it to Uwe to see if he
has time to build the test tar ball so we can see if he gets an error.


The files are already missing from the beta2 tarball (because they are not
listed in Makefile.am). If Uwe can build from it, we can remove them from
git.


No, beta2 does not build on Windows because of missing

3rdparty/boost/boost/numeric/conversion/detail/preprocessed/numeric_cast_traits_common.hpp
3rdparty/boost/boost/numeric/conversion/detail/preprocessed/numeric_cast_traits_long_long.hpp

Peter




Georg

Re: Printer missing in 2.2.0beta1

[Richard Heck]

On 02/12/2016 03:46 AM, Jean-Marc Lasgouttes wrote:
> Le 12/02/2016 09:38, Stephan Witt a écrit :
>> But this doesn’t solve the problem how to print individual chapters.
>
> What do you mean?
>
> BTW Richard, what happened with the idea of reusing the Ctrl+P binding
> for some printing-like activity?

As far as I remember, we never made a final decision. And then I moved.

Richard

Re: beta2?

[Scott Kostyshak]

On Sat, Feb 13, 2016 at 12:34:26PM +0100, Peter Kümmel wrote:
> Am 13.02.2016 um 10:57 schrieb Georg Baum:
> >Scott Kostyshak wrote:
> >
> >>I agree that it would be nice to remove unnecessary files. As far as
> >>figuring out which files are unnecessary, I volunteer to take any
> >>experimental patch, build a tar ball, and send it to Uwe to see if he
> >>has time to build the test tar ball so we can see if he gets an error.
> >
> >The files are already missing from the beta2 tarball (because they are not
> >listed in Makefile.am). If Uwe can build from it, we can remove them from
> >git.
> 
> No, beta2 does not build on Windows because of missing
> 
> 3rdparty/boost/boost/numeric/conversion/detail/preprocessed/numeric_cast_traits_common.hpp
> 3rdparty/boost/boost/numeric/conversion/detail/preprocessed/numeric_cast_traits_long_long.hpp
> 
> Peter

Thanks for testing, Peter. I'll wait for a fix, and then I suppose we
move to beta3?

Scott


signature.asc
Description: PGP signature

Re: Printer missing in 2.2.0beta1

[Scott Kostyshak]

On Sat, Feb 13, 2016 at 09:53:58AM -0500, Richard Heck wrote:
> On 02/12/2016 03:46 AM, Jean-Marc Lasgouttes wrote:
> > Le 12/02/2016 09:38, Stephan Witt a écrit :
> >> But this doesn’t solve the problem how to print individual chapters.
> >
> > What do you mean?
> >
> > BTW Richard, what happened with the idea of reusing the Ctrl+P binding
> > for some printing-like activity?
> 
> As far as I remember, we never made a final decision. And then I moved.

Was the idea to bind it to preview? So would we bind it to the same
function as ctrl+R currently?

Scott


signature.asc
Description: PGP signature

Re: [PATCH] Re: Update boost in 2.1 branch?

[Scott Kostyshak]

On Thu, Jan 21, 2016 at 04:53:34PM -0500, Scott Kostyshak wrote:
> On Thu, Jan 21, 2016 at 04:40:56PM -0500, Richard Heck wrote:
> > On 01/21/2016 04:07 PM, Pavel Sanda wrote:
> > > Jean-Marc Lasgouttes wrote:
> > >> So is it a problem that compiling in C++11 mode is broken with gcc 4.6? 
> > >> I 
> > >> would guess not.
> > > I guess it also depends how much space for error we have...
> > > Richard, do you plan to release one intermediate 2.1.x or you just 
> > > waiting for the final one?
> > 
> > How far out do we realistically think 2.2.0 is? I am thinking end of
> > February, but if it gets delayed any further we might think about an
> > intermediate release.
> 
> I think end of February is realistic. Beta should be soon, just need
> Guillaume's set of patches to git a final review, and Georg also is
> trying to look into an issue that Stephan has reported. After beta I do
> not think developers are planning many non-trivial commits so whether we
> achieve end of February for a final release will depend on what issues
> our beta testers find and on how long it takes us to fix those issues.

Richard, I just wanted to give an update that I no longer think the end
of February is realistic for the final release. The good news is that
soon it will be possible to compile on Windows from the tar ball, which
is nice to have fixed. I think we will need to release a beta3 in order
to fix one more set of these issues. Then, I will do some advertising
of beta3 on various sites. I imagine we want at least a couple of weeks
of testing, and I also imagine we will need to fix some issues that are
revealed from that testing.

Scott


signature.asc
Description: PGP signature

Re: Printer missing in 2.2.0beta1

[Jean-Marc Lasgouttes]

Yes, and we could use the "print preview" icon for it.

JMarc

Le 13 février 2016 18:06:15 GMT+01:00, Scott Kostyshak  a 
écrit :
>Was the idea to bind it to preview? So would we bind it to the same
>function as ctrl+R currently?
>
>Scott

Re: Printer missing in 2.2.0beta1

[Uwe Stöhr]

Am 12.02.2016 um 09:38 schrieb Stephan Witt:


But this doesn’t solve the problem how to print individual chapters.


I don't understand the discussion. You can export to a format you like 
then use the printer dialog of your preferred viewer to print what you 
like. If you only like to print one chapter, then do this. See also 
LyX's thesis template which uses separate LyX files for every chapters.


regards Uwe

Re: Printer missing in 2.2.0beta1

[Liviu Andronic]

On Sat, Feb 13, 2016 at 6:38 PM, Uwe Stöhr  wrote:
> Am 12.02.2016 um 09:38 schrieb Stephan Witt:
>
>> But this doesn’t solve the problem how to print individual chapters.
>
>
> I don't understand the discussion. You can export to a format you like then
> use the printer dialog of your preferred viewer to print what you like. If
> you only like to print one chapter, then do this. See also LyX's thesis
> template which uses separate LyX files for every chapters.
>
One thing you cannot do from an exported PS or PDF file is print e.g.
LyX Notes. But I'm not sure if this is common practice among users.

Liviu


> regards Uwe



-- 
Do you think you know what math is?
http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02
Or what it means to be intelligent?
http://www.ideasroadshow.com/issues/john-duncan-2013-08-30
Think again:
http://www.ideasroadshow.com/library

Re: beta2?

[Liviu Andronic]

On Sat, Feb 13, 2016 at 6:01 PM, Scott Kostyshak  wrote:
> On Sat, Feb 13, 2016 at 12:34:26PM +0100, Peter Kümmel wrote:
>> Am 13.02.2016 um 10:57 schrieb Georg Baum:
>> >Scott Kostyshak wrote:
>> >
>> >>I agree that it would be nice to remove unnecessary files. As far as
>> >>figuring out which files are unnecessary, I volunteer to take any
>> >>experimental patch, build a tar ball, and send it to Uwe to see if he
>> >>has time to build the test tar ball so we can see if he gets an error.
>> >
>> >The files are already missing from the beta2 tarball (because they are not
>> >listed in Makefile.am). If Uwe can build from it, we can remove them from
>> >git.
>>
>> No, beta2 does not build on Windows because of missing
>>
>> 3rdparty/boost/boost/numeric/conversion/detail/preprocessed/numeric_cast_traits_common.hpp
>> 3rdparty/boost/boost/numeric/conversion/detail/preprocessed/numeric_cast_traits_long_long.hpp
>>
>> Peter
>
> Thanks for testing, Peter. I'll wait for a fix, and then I suppose we
> move to beta3?
>
We could also do e.g. beta2.1, beta2.2, etc. until the Windows build
issues are sorted out...

Liviu


> Scott



-- 
Do you think you know what math is?
http://www.ideasroadshow.com/issues/ian-stewart-2013-08-02
Or what it means to be intelligent?
http://www.ideasroadshow.com/issues/john-duncan-2013-08-30
Think again:
http://www.ideasroadshow.com/library

Re: beta2?

[Peter Kümmel]

Am 13.02.2016 um 18:01 schrieb Scott Kostyshak:

On Sat, Feb 13, 2016 at 12:34:26PM +0100, Peter Kümmel wrote:

Am 13.02.2016 um 10:57 schrieb Georg Baum:

Scott Kostyshak wrote:


I agree that it would be nice to remove unnecessary files. As far as
figuring out which files are unnecessary, I volunteer to take any
experimental patch, build a tar ball, and send it to Uwe to see if he
has time to build the test tar ball so we can see if he gets an error.


The files are already missing from the beta2 tarball (because they are not
listed in Makefile.am). If Uwe can build from it, we can remove them from
git.


No, beta2 does not build on Windows because of missing

3rdparty/boost/boost/numeric/conversion/detail/preprocessed/numeric_cast_traits_common.hpp
3rdparty/boost/boost/numeric/conversion/detail/preprocessed/numeric_cast_traits_long_long.hpp

Peter


Thanks for testing, Peter. I'll wait for a fix, and then I suppose we
move to beta3?


OK, files now are part of the tar.



Scott

Re: beta2?

[Uwe Stöhr]

Am 13.02.2016 um 18:01 schrieb Scott Kostyshak:


Thanks for testing, Peter. I'll wait for a fix, and then I suppose we
move to beta3?


Sorry, but why do we act like beginners?

I wrote what is missing in the tarball. So why not add these files, send 
me the tarball by private mail to check and then announce a new beta? I 
also don't understand why a change in a makefile to add missing files 
deserves a new beta release.


I copied the boost folder from master to the tarball folder and built beta2:
http://ftp.lyx.de/LyX%202.2.0beta-2/

regards Uwe

Re: Printer missing in 2.2.0beta1

[Uwe Stöhr]

Am 13.02.2016 um 18:42 schrieb Liviu Andronic:


One thing you cannot do from an exported PS or PDF file is print e.g.
LyX Notes.


Well, LyX notes are supposed to be in LyX only. If you want to have them 
in the output, turn them into greyed-out notes (and adjust the font 
color if you don't like gray)


regards Uwe

Re: beta2?

[Scott Kostyshak]

On Sat, Feb 13, 2016 at 07:11:48PM +0100, Uwe Stöhr wrote:
> Am 13.02.2016 um 18:01 schrieb Scott Kostyshak:
> 
> >Thanks for testing, Peter. I'll wait for a fix, and then I suppose we
> >move to beta3?
> 
> Sorry, but why do we act like beginners?
> 
> I wrote what is missing in the tarball. So why not add these files, send me
> the tarball by private mail to check and then announce a new beta

You are right that this is what I should have done for beta2. I will do
this now before releasing beta3. I'll build the tar and send it to you
privately. After you confirm that you can compile the Windows build from
only the tar, I will post the tar and push the git tag and git commits.

> I also
> don't understand why a change in a makefile to add missing files deserves a
> new beta release.

Because we changed the code. We want the betax tar to be the tar that is
produced from checking out the betax tag of git. Also, I uploaded the
tar so now we must make the assumption to be safe that it has been
picked up by others. We would not want two different betax tars floating
around.

Scott


signature.asc
Description: PGP signature

Re: beta2?

[Scott Kostyshak]

On Sat, Feb 13, 2016 at 01:24:20PM -0500, Scott Kostyshak wrote:
> On Sat, Feb 13, 2016 at 07:11:48PM +0100, Uwe Stöhr wrote:
> > Am 13.02.2016 um 18:01 schrieb Scott Kostyshak:
> > 
> > >Thanks for testing, Peter. I'll wait for a fix, and then I suppose we
> > >move to beta3?
> > 
> > Sorry, but why do we act like beginners?
> > 
> > I wrote what is missing in the tarball. So why not add these files, send me
> > the tarball by private mail to check and then announce a new beta
> 
> You are right that this is what I should have done for beta2. I will do
> this now before releasing beta3. I'll build the tar and send it to you
> privately. After you confirm that you can compile the Windows build from
> only the tar, I will post the tar and push the git tag and git commits.

I've sent the tars to you privately. Can you do a fresh build from them?

Thanks,

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems".

[Scott Kostyshak]

On Tue, Oct 20, 2015 at 07:16:44PM +0200, Günter Milde wrote:
> commit 1523fc6023440f10ca0d82a681ded5c060d8fd33
> Author: Günter Milde 
> 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).

Is this expected? 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. If it is expected, do we have a bug report?

Scott


signature.asc
Description: PGP signature

Re: 2.2.0 beta 1: Xetex not working

[Guenter Milde]

On 2016-02-11, Jürgen Lange wrote:
> The PDF Producer changed from Xetex 0.2 in 2.1.4. to MikTex-xdvipdfmx  
> (20150315) in 2.2.0beta1.

This is rather due to an MikTex update. xdvipdfmx is the part of XeTeX that
transforms the intermediate format (XDVI) to PDF.

Günter

Re: [LyX/master] Make ja/splash.lyx compilable again.

[Guenter Milde]

On 2016-02-09, Uwe Stöhr wrote:
> Am 08.02.2016 um 22:38 schrieb Kornel Benko:

>> I am not sure why do you think I had changed anything in the Japanese text.
>> Sure, I cannot understand the written text, but I felt able to compare the 
>> pdf-output with the
>> appearance of text in lyx window.

> You changed the babel settings that were changed by Koji:
> http://www.lyx.org/trac/changeset/49b6a89a14a87abcbd9cc6d5f8c2d3ebd4bf9685/lyxgit

> The only thing I know is that platex is different in its language 
> handling. Thus I cannot tell if this change might cause problems with 
> platex.

The question is: did Kornel compile with platex? I think so and as far as I
remember, LyX has special-casing to handle this platex/babel problem.

Günter

Re: [LyX/master] Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems".

[Guenter Milde]

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 
>> 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?

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.

Günter

Re: Printer missing in 2.2.0beta1

[Stephan Witt]

Am 13.02.2016 um 18:38 schrieb Uwe Stöhr :
> 
> Am 12.02.2016 um 09:38 schrieb Stephan Witt:
> 
>> But this doesn’t solve the problem how to print individual chapters.
> 
> I don't understand the discussion. You can export to a format you like then 
> use the printer dialog of your preferred viewer to print what you like. If 
> you only like to print one chapter, then do this. See also LyX's thesis 
> template which uses separate LyX files for every chapters.

The original question was were the print dialog has gone because Miguel used it 
to print parts of a document. The answer was to use export to printer. IMO, 
this missed the point how to print a document partially only.

Stephan

Re: [LyX/master] Make ja/splash.lyx compilable again.

[Kornel Benko]

Am Samstag, 13. Februar 2016 um 20:46:13, schrieb Guenter Milde 

> On 2016-02-09, Uwe Stöhr wrote:
> > Am 08.02.2016 um 22:38 schrieb Kornel Benko:
> 
> >> I am not sure why do you think I had changed anything in the Japanese text.
> >> Sure, I cannot understand the written text, but I felt able to compare the 
> >> pdf-output with the
> >> appearance of text in lyx window.
> 
> > You changed the babel settings that were changed by Koji:
> > http://www.lyx.org/trac/changeset/49b6a89a14a87abcbd9cc6d5f8c2d3ebd4bf9685/lyxgit
> 
> > The only thing I know is that platex is different in its language 
> > handling. Thus I cannot tell if this change might cause problems with 
> > platex.
> 
> The question is: did Kornel compile with platex? I think so and as far as I
> remember, LyX has special-casing to handle this platex/babel problem.

Sure I did.

> Günter

Kornel

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

Re: [LyX/master] Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems".

[Scott Kostyshak]

On Sat, Feb 13, 2016 at 08:54:57PM +, 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 
> >> 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


splash_good.tex
Description: TeX document


splash_bad.tex
Description: TeX document


signature.asc
Description: PGP signature