Re: new installer for LyX 2.1.4 available

2016-05-26 Thread Uwe Stöhr 

Am 26.05.2016 um 16:07 schrieb Uwe Stöhr:


everything is now ready. Please put the new installer for LyX 2.1.4 to
the ftp server:
http://ftp.lyx.de/LyX%202.1.4/


I uploaded there version a new version 7 of the installer for 2.1.4 to 
avoid confusions the the version 6 that I released more than a week ago 
(that I stopped because of MiKTeX issues).


Please put the version 7 on the LyX FTP server.

many thanks and regards
Uwe

Re: retracting the installer: was: Tarballs for LyX 2.2.0 are on FTP

2016-05-26 Thread Uwe Stöhr 

Am 27.05.2016 um 01:03 schrieb Scott Kostyshak:


I will try to release a new version withing 2 hours or so.


It was more tricky than I thought. However, I solved the problems and 
uploaded a new version:


http://ftp.lyx.de/LyX%202.2.0/

sorry and regards
Uwe

Re: retracting the installer: was: Tarballs for LyX 2.2.0 are on FTP

2016-05-26 Thread Scott Kostyshak 
On Thu, May 26, 2016 at 11:30:03PM +0200, Uwe Stöhr wrote:
> Am 26.05.2016 um 16:05 schrieb Uwe Stöhr:
> 
> > Here it is:
> > http://ftp.lyx.de/LyX%202.2.0/
> 
> As always a release without testing is very bad. I only had an hour but
> fortunately have now time to test it and there are some errors and mistakes
> if Lyx is installed the first time and without admin privileges. I will try
> to release a new version withing 2 hours or so.

OK.

> For now, please remove the
> installer I sent.

Done.

Scott


signature.asc
Description: PGP signature

retracting the installer: was: Tarballs for LyX 2.2.0 are on FTP

2016-05-26 Thread Uwe Stöhr 

Am 26.05.2016 um 16:05 schrieb Uwe Stöhr:


Here it is:
http://ftp.lyx.de/LyX%202.2.0/


As always a release without testing is very bad. I only had an hour but 
fortunately have now time to test it and there are some errors and 
mistakes if Lyx is installed the first time and without admin 
privileges. I will try to release a new version withing 2 hours or so. 
For now, please remove the installer I sent.


regards Uwe

Re: Using xmllint to test our LyXHTML export

2016-05-26 Thread Scott Kostyshak 
On Thu, May 26, 2016 at 06:44:39PM +0200, Kornel Benko wrote:
> Am Mittwoch, 25. Mai 2016 um 16:48:58, schrieb Kornel Benko 
> > Am Montag, 23. Mai 2016 um 18:03:27, schrieb Scott Kostyshak 
> > 
> > > On Mon, May 23, 2016 at 03:55:59PM +, Guenter Milde wrote:
> > > > On 2016-05-23, Kornel Benko wrote:
> > > > > Am Montag, 23. Mai 2016 um 07:36:53, schrieb Guenter Milde 
> > > > > 
> > > > >> On 2016-05-22, Scott Kostyshak wrote:
> > > > 
> > > > >> > Uwe and Georg have recently found and fixed a bug in our internal 
> > > > >> > XHTML
> > > > >> > export. Why not test the export automatically?
> > > > 
> > > > ...
> > > > 
> > > > > I have a patch ready. 
> > > > 
> > > > Fine, thanks.
> > > > 
> > > > > But now many of xhtml export tests are failing.
> > > > 
> > > > This should not deter us from proper testing, should it?
> > > 
> > > In my opinion, the important thing is to make sure no new tests go from
> > > passsing to failinig. It is possible to easily catch future regressions
> > > with the tests. I agree with you (below) that inverting a lot of tests
> > > makes sense. This way, we can (1) catch new regressions and (2) if
> > > someone does come along and wants to give some love to the HTML export
> > > we can easily provide them with some places to start (in addition to the
> > > trac bugs we have).
> > > 
> > > Scott
> > > 
> > > > 
> > > > Do you have a list of failing tests?
> > 
> > Yes, I have. But the list is huge.
> > 48% tests passed, 186 tests failed out of 356
> > 
> > > > Did you check for the failure reasons?
> > 
> > Some of them are really bad, like in doc/MergedManuals.xhtml:9270
> > < class="verbatim"> > class="verbatim_item">This is Verbatim.
> > 
> > others are OK in firefox.
> > 
> > > > I may be we have to invert a lot of tests until the HTML export is 
> > > > fixed.
> > > > Maybe we can also introduce a flag for "half-OK" (not passing the 
> > > > xmllint test
> > > > but opening OK in a browser).
> > > 
> > 
> > No, for this the number of failures is too big IMHO.
> 
> Hm, using xmllint with the '--sax' parameter shows no errors. Still 
> MergedManuals.xhtml is erroneous (e.g. not displayable in firefox).
> Checking the includes, the error is in UserGuide.lyx.
> It turns out that our xhtml cannot handle verbatim environment.
> 
> Attached a minimal example:
> 
> Richard could you have a look at it?

Josh (now CC'ed), I remember that at some point you made some fixes to
our XHTML export. Are you by chance interested in working on it further?
We are considering implementing tests for our XHTML export but they are
only useful if we have someone who might be interested in fixing bugs
that our tests find. No pressure at all, just curious if that would be
fun for you.

Scott


signature.asc
Description: PGP signature

Re: Handling of \SpecialChar

2016-05-26 Thread Scott Kostyshak 
On Thu, May 26, 2016 at 02:17:11PM +0100, José Abílio Matos wrote:
> On Wednesday, May 25, 2016 1:39:56 PM WEST Scott Kostyshak wrote:
> > I'm still curious someone has thoughts on the above idea. The main
> > question I have is do we usually know when we are not producing
> > equivalent documents (and thus it is easy to issue a warning)? I assumed
> > so but I don't have experience with this.
> > 
> > Scott
> 
> lyx2lyx can emit warnings but we do not process them in lyx. So for the 
> moment 
> that will not work. If the code follows the usual conventions the warning 
> messages are easy to catch and process.

I see.

> We should put things in perspective, for most of the features the convertion 
> is seamless. The backport is an added bonus that allows users to read 
> documents from the next version.

I don't think that the users understand that it is an added bonus and
might not work in many cases and that we knowingly allow for data loss.
On the other hand, I do not remember a single bug report from a user
complaining about exporting to an older version so perhaps my concern is
indeed not worth it.

> Ideally this should a last resort scheme 
> because we do not test for back and forth convertions to guarantee a stable 
> cycle.

There has been some progress towards such tests, but the tests are not
unit tests.

> IMHO the ROI return of investment for this is so small that it is not 
> worth, that is the amount of work required is so large for a so small benefit.
> 
> And just as in the case of the question of qt4 vs qt5 as long as the code to 
> convert back covers all the (relevant) cases we fulfill our promisses. :-)
> 
> Again I reiterate that this is my humble opinion. :-)

Makes sense, thanks for the explanation.

Scott


signature.asc
Description: PGP signature

Re: Wrong file path in MergedMauals.lyx

2016-05-26 Thread Kornel Benko 
Am Donnerstag, 26. Mai 2016 um 16:30:28, schrieb Scott Kostyshak 

> On Thu, May 26, 2016 at 07:00:37PM +0200, Kornel Benko wrote:
> > 
> > Subject says it all.
> > Commit?
> 
> Yes, to 2.3-staging I think. It is actually in a LyX note along with
> another example file. I'm not sure why they are in MergedManuals.lyx.
> 
> Scott
> 

Done at de2e5a7

Kornel

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

Re: Wrong file path in MergedMauals.lyx

2016-05-26 Thread Scott Kostyshak 
On Thu, May 26, 2016 at 07:00:37PM +0200, Kornel Benko wrote:
> 
> Subject says it all.
> Commit?

Yes, to 2.3-staging I think. It is actually in a LyX note along with
another example file. I'm not sure why they are in MergedManuals.lyx.

Scott

> 
>   Kornel




> diff --git a/lib/doc/MergedManuals.lyx b/lib/doc/MergedManuals.lyx
> index 44cbae8..cf72312 100644
> --- a/lib/doc/MergedManuals.lyx
> +++ b/lib/doc/MergedManuals.lyx
> @@ -233,7 +233,7 @@ filename "../examples/linguistics.lyx"
>  \begin_layout Plain Layout
>  \begin_inset CommandInset include
>  LatexCommand include
> -filename "../lib/examples/xypic.lyx"
> +filename "../examples/xypic.lyx"
>  
>  \end_inset
>  



signature.asc
Description: PGP signature

Re: Tarballs for LyX 2.2.0 are on FTP

2016-05-26 Thread Scott Kostyshak 
On Thu, May 26, 2016 at 04:05:24PM +0200, Uwe Stöhr wrote:
> Am 25.05.2016 um 00:29 schrieb Uwe Stöhr:
> 
> > Despite of the warning the compilation run fine and I have an installer
> > ready.
> 
> Here it is:
> http://ftp.lyx.de/LyX%202.2.0/

Thanks they are uploaded.

> It contains the fresh MiKTeX release from yesterday. However, I did not yet
> have the time to test new installation of LyX/MiKTeX with the installer for
> 2.2.0.

We have to wait for the mirrors before announcing anyway. Will you by
chance have time today to do a test today?

Scott


signature.asc
Description: PGP signature

Wrong file path in MergedMauals.lyx

2016-05-26 Thread Kornel Benko 

Subject says it all.
Commit?

Kornel

signature.asc
Description: This is a digitally signed message part.
diff --git a/lib/doc/MergedManuals.lyx b/lib/doc/MergedManuals.lyx
index 44cbae8..cf72312 100644
--- a/lib/doc/MergedManuals.lyx
+++ b/lib/doc/MergedManuals.lyx
@@ -233,7 +233,7 @@ filename "../examples/linguistics.lyx"
 \begin_layout Plain Layout
 \begin_inset CommandInset include
 LatexCommand include
-filename "../lib/examples/xypic.lyx"
+filename "../examples/xypic.lyx"
 
 \end_inset

Re: Using xmllint to test our LyXHTML export

2016-05-26 Thread Kornel Benko 
Am Mittwoch, 25. Mai 2016 um 16:48:58, schrieb Kornel Benko 
> Am Montag, 23. Mai 2016 um 18:03:27, schrieb Scott Kostyshak 
> 
> > On Mon, May 23, 2016 at 03:55:59PM +, Guenter Milde wrote:
> > > On 2016-05-23, Kornel Benko wrote:
> > > > Am Montag, 23. Mai 2016 um 07:36:53, schrieb Guenter Milde 
> > > > 
> > > >> On 2016-05-22, Scott Kostyshak wrote:
> > >
> > > >> > Uwe and Georg have recently found and fixed a bug in our internal 
> > > >> > XHTML
> > > >> > export. Why not test the export automatically?
> > >
> > > ...
> > >
> > > > I have a patch ready.
> > >
> > > Fine, thanks.
> > >
> > > > But now many of xhtml export tests are failing.
> > >
> > > This should not deter us from proper testing, should it?
> >
> > In my opinion, the important thing is to make sure no new tests go from
> > passsing to failinig. It is possible to easily catch future regressions
> > with the tests. I agree with you (below) that inverting a lot of tests
> > makes sense. This way, we can (1) catch new regressions and (2) if
> > someone does come along and wants to give some love to the HTML export
> > we can easily provide them with some places to start (in addition to the
> > trac bugs we have).
> >
> > Scott
> >
> > >
> > > Do you have a list of failing tests?
>
> Yes, I have. But the list is huge.
> 48% tests passed, 186 tests failed out of 356
>
> > > Did you check for the failure reasons?
>
> Some of them are really bad, like in doc/MergedManuals.xhtml:9270
>   < class="verbatim"> class="verbatim_item">This is Verbatim.
>
> others are OK in firefox.
>
> > > I may be we have to invert a lot of tests until the HTML export is fixed.
> > > Maybe we can also introduce a flag for "half-OK" (not passing the xmllint 
> > > test
> > > but opening OK in a browser).
> >
>
> No, for this the number of failures is too big IMHO.

Hm, using xmllint with the '--sax' parameter shows no errors. Still 
MergedManuals.xhtml is erroneous (e.g. not displayable in firefox).
Checking the includes, the error is in UserGuide.lyx.
It turns out that our xhtml cannot handle verbatim environment.

Attached a minimal example:

Richard could you have a look at it?

Kornel

testVerbatim.lyx
Description: application/lyx


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

Re: Tarballs for LyX 2.2.0 are on FTP

2016-05-26 Thread Georg Baum 
Uwe Stöhr wrote:

> Am 25.05.2016 um 00:37 schrieb Richard Heck:
> 
>> We have lots of warnings like this. They are usually fixed by doing the
>> conversion explicitly, so probably nothing really needs to be done for
>> the release.
> 
> This is suspicious to me because usually MSVC has good reasons for
> issuing a dataloss warning. Moreover I only get this single warning when
> compiling the LyX 2.2 tarball (except of third-party code).
> 
> 
> Thus I would like to have this fixed if not for 2.2.0 then asap for 2.2.1.

As it was explained in an earlier message the fix would be to silence the 
warning by an explicit cast, as it is done in other lines of code nearby. 
The resulting binary code would exactly be the same.

I agree that warnings should be taken seriously, but in this case it is 
wanted to cast from a double to an int, so there is no urgency to do 
something for 2.2.0.


Georg

Re: Tarballs for LyX 2.2.0 are on FTP

2016-05-26 Thread Guillaume Munch 

Le 26/05/2016 15:12, Uwe Stöhr a écrit :

Am 25.05.2016 um 00:37 schrieb Richard Heck:


We have lots of warnings like this. They are usually fixed by doing the
conversion explicitly, so probably nothing really needs to be done for
the release.


This is suspicious to me because usually MSVC has good reasons for
issuing a dataloss warning. Moreover I only get this single warning when
compiling the LyX 2.2 tarball (except of third-party code).


Thus I would like to have this fixed if not for 2.2.0 then asap for 2.2.1.

thanks and regards
Uwe




Thank you for your message. I do not know why you sent it to me.

Guillaume

Re: Tarballs for LyX 2.2.0 are on FTP

2016-05-26 Thread Uwe Stöhr 

Am 25.05.2016 um 00:37 schrieb Richard Heck:


We have lots of warnings like this. They are usually fixed by doing the
conversion explicitly, so probably nothing really needs to be done for
the release.


This is suspicious to me because usually MSVC has good reasons for 
issuing a dataloss warning. Moreover I only get this single warning when 
compiling the LyX 2.2 tarball (except of third-party code).



Thus I would like to have this fixed if not for 2.2.0 then asap for 2.2.1.

thanks and regards
Uwe

Re: new installer for LyX 2.1.4 available

2016-05-26 Thread Uwe Stöhr 

Am 17.05.2016 um 23:13 schrieb Uwe Stöhr:


The MiKTeX developer said  me that...
he will release this week a new installer that fixes several MiKTeX
issues affecting new installations. So I will include this and then
release version 6 of the installer for LyX 2.1.4.


Hi Richard,

everything is now ready. Please put the new installer for LyX 2.1.4 to 
the ftp server:

http://ftp.lyx.de/LyX%202.1.4/

many thanks and regards
Uwe

Re: Tarballs for LyX 2.2.0 are on FTP

2016-05-26 Thread Uwe Stöhr 

Am 25.05.2016 um 00:29 schrieb Uwe Stöhr:


Despite of the warning the compilation run fine and I have an installer
ready.


Here it is:
http://ftp.lyx.de/LyX%202.2.0/

It contains the fresh MiKTeX release from yesterday. However, I did not 
yet have the time to test new installation of LyX/MiKTeX with the 
installer for 2.2.0.


regards Uwe

Re: Handling of \SpecialChar

2016-05-26 Thread José Abílio Matos 
On Wednesday, May 25, 2016 1:39:56 PM WEST Scott Kostyshak wrote:
> I'm still curious someone has thoughts on the above idea. The main
> question I have is do we usually know when we are not producing
> equivalent documents (and thus it is easy to issue a warning)? I assumed
> so but I don't have experience with this.
> 
> Scott

lyx2lyx can emit warnings but we do not process them in lyx. So for the moment 
that will not work. If the code follows the usual conventions the warning 
messages are easy to catch and process.

We should put things in perspective, for most of the features the convertion 
is seamless. The backport is an added bonus that allows users to read 
documents from the next version. Ideally this should a last resort scheme 
because we do not test for back and forth convertions to guarantee a stable 
cycle. IMHO the ROI return of investment for this is so small that it is not 
worth, that is the amount of work required is so large for a so small benefit.

And just as in the case of the question of qt4 vs qt5 as long as the code to 
convert back covers all the (relevant) cases we fulfill our promisses. :-)

Again I reiterate that this is my humble opinion. :-)

Regards,
-- 
José Abílio

Re: Tarballs for LyX 2.2.0 are on FTP

2016-05-26 Thread José Abílio Matos 
On Wednesday, May 25, 2016 7:11:14 PM WEST Jürgen Spitzmüller wrote:
> Congratulations. And thanks for the excellent management job, Scott.
> 
> Jürgen

I agree. :-)

Well done.
-- 
José Abílio

Re: Basic test of alpha1 tar

2016-05-26 Thread Jean-Marc Lasgouttes 

Le 24/05/2016 23:37, Pavel Sanda a écrit :

I only tried 2.2, so I did not really compare. I do not have 2.0 here. I
can try to have a look at 2.1 vs 2.2 later.


Please try, we should see whether the problem is reproducible at all...


Since you were asking in different thread, ping :)


When I looked at that, I did not find much. I'll have to return to it.

JMarc

Re: [LyX/master] Add note about required svg support in Qt.

2016-05-26 Thread Jean-Marc Lasgouttes 

Le 24/05/2016 23:41, Enrico Forestieri a écrit :

We already check for the presence of the QtSvg (or Qt5Svg) library.
Other than that, I don't know how to check whether the gui libraries
actually have support for loading svg images compiled in.


OK, thanks.

JMarc

Re: Tarballs for LyX 2.2.0 are on FTP

2016-05-26 Thread Jean-Marc Lasgouttes 

Le 25/05/2016 19:11, Jürgen Spitzmüller a écrit :

Thanks to everyone for all the help with the final steps in the
release
process.


Congratulations. And thanks for the excellent management job, Scott.


Indeed. You did it much more thoroughly than I would have been able to.

Time to think about the release date of 2.3.0 now ;)

JMarc

Re: Tarballs for LyX 2.2.0 are on FTP

2016-05-26 Thread Scott Kostyshak 
On Tue, May 24, 2016 at 08:50:14PM -0400, Scott Kostyshak wrote:
> On Wed, May 25, 2016 at 12:29:04AM +0200, Uwe Stöhr wrote:
> > Am 24.05.2016 um 04:32 schrieb Scott Kostyshak:
> > 
> > > As usual I'll wait before announcing the release until after uploading
> > > the binaries and providing some time for the mirrors.
> > 
> > Great job Scott! Many thanks for all your patient work.
> > 
> > I built it now and noticed 2 things:
> > 
> > - There is a dataloss warning that should be fixed before the final release:
> > 
> > D:\LyXGit\LyX22\src\insets\InsetSeparator.cpp(213): warning C4244: '+=':
> > conversion from 'double' to 'int', possible loss of data
> 
> Thanks for finding this. I agree with Richard that it is not urgent.
> 
> > Guillaume could you please have a look?
> 
> Does Guillaume seem so bored? :)
> Unless I misunderstood, the code was introduced at d4ca8d74.
> 
> Looking at the code, there are explicit conversions to int a few lines
> down and a few lines up, so a conversion to int is probably intended
> here also. Attached is a patch.
> 
> > - There is no batch build script for building LyX 2.2 with MSVC 2015. May I
> > add one?
> > 
> > Despite of the warning the compilation run fine and I have an installer
> > ready.
> 
> Good news! I think we can move forward with the installer despite the
> warning you discovered.

Sorry, Uwe, I forgot to CC you when I sent the above email. We can go
ahead despite the warning you found. Can you send the installers?

Thanks,

Scott

> 
> Scott
> 
> > Concerning the installer: The MiKTeX maintainer works hard to iron out some
> > long standing bugs and thus releases currently almost every day a new
> > version. Unfortunately he did not yet release a new installer so that new
> > installations of MiKTeX and LyX will require at least 3 update cycles to be
> > up to date. I try to convince him for a new installer. If this is not
> > possible, I would like to release a new installer as soon as the MiKTeX
> > installer is available.
> > 
> > best regards Uwe

> diff --git a/src/insets/InsetSeparator.cpp b/src/insets/InsetSeparator.cpp
> index a759f1f..27aeb7c 100644
> --- a/src/insets/InsetSeparator.cpp
> +++ b/src/insets/InsetSeparator.cpp
> @@ -210,7 +210,7 @@ void InsetSeparator::draw(PainterInfo & pi, int x, int y) 
> const
>   pi.pain.lines(xp, yp, 2, ColorName());
>  
>   if (params_.kind == InsetSeparatorParams::PARBREAK) {
> - yp[0] += 0.25 * asc * 0.75;
> + yp[0] += int(0.25 * asc * 0.75);
>   yp[1] = yp[0];
>   pi.pain.lines(xp, yp, 2, ColorName());
>   }





signature.asc
Description: PGP signature