Re: Tarballs for LyX 2.2.0 are on FTP
Am Dienstag, 24. Mai 2016 um 21:16:33, schrieb Georg Baum > Scott Kostyshak wrote: > > > Hi all, > > > > The tarballs for LyX 2.2.0 can be found at > > > > ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/lyx-2.2.0/ > > Builds and runs fine on debian 8.1, except when configuring with version > suffix: http://www.lyx.org/trac/ticket/10159. Since this also happens with > 2.1.4 it is no regression. > > > As usual I'll wait before announcing the release until after uploading > > the binaries and providing some time for the mirrors. > > > > Thanks to everyone for all the help with the final steps in the release > > process. > > Thank you for all the work you did as release manager! > > > Georg Good work :) Kornel signature.asc Description: This is a digitally signed message part.
Re: [LyX/master] * lib/RELEASE-NOTES
On Tue, May 24, 2016 at 10:05:59PM +0200, Jean-Marc Lasgouttes wrote: > Le 24/05/16 à 22:01, Scott Kostyshak a écrit : > > > I guess that one problem will be with the UI files. > > > > I don't understand. Why would the UI files cause a problem? Do you mean > > because if we have to choose between a .ui that looks good on Qt 4 or > > looks good on Qt 5 we will choose Qt 5 and cannot use guards like in cpp > > files? > > I thought that UI files produced with Qt5 qtdesigner would not be usable > with Qt4.8. I would be glad to be wrong. I did not find a definitive source on this topic. It does seem that we experienced an issue with backwards compatibility between 4.2 and 4.3: http://lyx-devel.lyx.narkive.com/7ui1juCT/compilation-problem-with-ui-files Scott signature.asc Description: PGP signature
Re: Tarballs for LyX 2.2.0 are on FTP
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.
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
Translations for 2.1.5
With 2.2.0 suddenly by-passing RC2 and being released, I'm afraid I'm a bit behind asking for translations for 2.1.5, the final release in the 2.1.x series. Please prepare translations as soon as you are able: by Friday, 3 June, if at all possible. Let me know if that timeline is too tight. Richard Heck Branch Maintainer
Re: Tarballs for LyX 2.2.0 are on FTP
On 05/24/2016 06:29 PM, 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 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. > 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. I'll presumably be in charge of 2.2.x by then. And that's fine. rh
Re: Tarballs for LyX 2.2.0 are on FTP
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 Guillaume could you please have a look? - 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. 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
Re: [LyX/master] Add note about required svg support in Qt.
On Tue, May 24, 2016 at 08:58:02AM +0200, Jean-Marc Lasgouttes wrote: > Le 24/05/2016 00:00, Scott Kostyshak a écrit : > >On Mon, May 23, 2016 at 12:22:36PM +0200, Jean-Marc Lasgouttes wrote: > >>Le 23/05/2016 à 03:05, Enrico Forestieri a écrit : > >>>commit 63153b89376cf120a1a9ba818624f36f9d23f292 > >>>Author: Enrico Forestieri > >>>Date: Mon May 23 03:04:55 2016 +0200 > >>> > >>> Add note about required svg support in Qt. > >> > >>Is there something that can be done about that in autoconf? > > > >I'm not planning to worry about this for 2.2.0. Let me know if you > >disagree. > > No problem. 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. -- Enrico
Re: Basic test of alpha1 tar
Pavel Sanda wrote: > Jean-Marc Lasgouttes wrote: > > Le 12/01/2016 10:15, Pavel Sanda a écrit : > >> Jean-Marc Lasgouttes wrote: > More important is - can you reproduce the behaviour? It's pretty clear > on my > machine without trying any special conditions, just high repeat rate of > the > keyboard is needed. > > > > 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 :) > Pavel
Re: cygwin installer for 2.2.0
On Tue, May 24, 2016 at 11:27:04PM +0200, Enrico Forestieri wrote: > On Tue, May 24, 2016 at 04:39:15PM -0400, Scott Kostyshak wrote: > > Do we wait for a cygwin installer before announcing? Is Enrico the one > > who takes care of this? I had forgotten that we provided cygwin > > installers for the final realize until I looked at > > ftp://ftp.lyx.org/pub/lyx/bin/2.1.0/ > > The official cygwin repository already provides a package for lyx: > https://cygwin.com/cgi-bin2/package-grep.cgi?grep=lyx.exe&arch=x86 > The package we provide differs from the official one for the fact > that a X11 server is not needed. I don't think that the lack of > a cygwin package should cause a delay. OK. > The official cygwin > package will be updated when the maintainer wants to, while our > own package will be provided when I find some time to build it. Sounds good. > Frankly, I don't know whether our own package is actually used > because of the lack of specific bug reports. So, either it is bug > free or nobody uses it... It would be nice to have download statistics. I think we tried once to get them but did not succeed. Scott signature.asc Description: PGP signature
Re: cygwin installer for 2.2.0
On Tue, May 24, 2016 at 04:39:15PM -0400, Scott Kostyshak wrote: > Do we wait for a cygwin installer before announcing? Is Enrico the one > who takes care of this? I had forgotten that we provided cygwin > installers for the final realize until I looked at > ftp://ftp.lyx.org/pub/lyx/bin/2.1.0/ The official cygwin repository already provides a package for lyx: https://cygwin.com/cgi-bin2/package-grep.cgi?grep=lyx.exe&arch=x86 The package we provide differs from the official one for the fact that a X11 server is not needed. I don't think that the lack of a cygwin package should cause a delay. The official cygwin package will be updated when the maintainer wants to, while our own package will be provided when I find some time to build it. Frankly, I don't know whether our own package is actually used because of the lack of specific bug reports. So, either it is bug free or nobody uses it... -- Enrico
Re: Minor last minute edits in fr.po
Le 24/05/2016 16:03, Richard Heck a écrit : On 05/24/2016 04:02 AM, Jean-Pierre Chrétien wrote: Richard, one shortcut conflict resolution should be backported to 2.1.5. Okay to push ? Yes, that's fine. Done -- Jean-Pierre
cygwin installer for 2.2.0
Do we wait for a cygwin installer before announcing? Is Enrico the one who takes care of this? I had forgotten that we provided cygwin installers for the final realize until I looked at ftp://ftp.lyx.org/pub/lyx/bin/2.1.0/ Scott signature.asc Description: PGP signature
Re: [LyX/master] * lib/RELEASE-NOTES
Le 24/05/16 à 22:01, Scott Kostyshak a écrit : I guess that one problem will be with the UI files. I don't understand. Why would the UI files cause a problem? Do you mean because if we have to choose between a .ui that looks good on Qt 4 or looks good on Qt 5 we will choose Qt 5 and cannot use guards like in cpp files? I thought that UI files produced with Qt5 qtdesigner would not be usable with Qt4.8. I would be glad to be wrong. JMarc
Re: [LyX/master] * lib/RELEASE-NOTES
On Tue, May 24, 2016 at 09:40:46PM +0200, Jean-Marc Lasgouttes wrote: > Le 24/05/16 à 21:31, Georg Baum a écrit : > > > For these reasons as well, I am hoping that for 2.3 the community of LyX > > > developers will choose to focus on qt >= 5.6. > > > > +1 > > > > However, I also agree with Jean-Marc: As long as keeping LyX compilable with > > qt 4.8 is close to zero effort we should support 4.8 as in "LyX compiles and > > does not crash immediately". > > In the foreseeable future, I will compile and use 4.8.x. Actually, I have no > real incentive to switch to Qt5 in Linux, so I will act as the resident > old-timer, until the cost is too high. > > I guess that one problem will be with the UI files. I don't understand. Why would the UI files cause a problem? Do you mean because if we have to choose between a .ui that looks good on Qt 4 or looks good on Qt 5 we will choose Qt 5 and cannot use guards like in cpp files? Scott signature.asc Description: PGP signature
Re: [LyX/master] * lib/RELEASE-NOTES
Le 24/05/16 à 21:31, Georg Baum a écrit : For these reasons as well, I am hoping that for 2.3 the community of LyX developers will choose to focus on qt >= 5.6. +1 However, I also agree with Jean-Marc: As long as keeping LyX compilable with qt 4.8 is close to zero effort we should support 4.8 as in "LyX compiles and does not crash immediately". In the foreseeable future, I will compile and use 4.8.x. Actually, I have no real incentive to switch to Qt5 in Linux, so I will act as the resident old-timer, until the cost is too high. I guess that one problem will be with the UI files. JMarc
Re: [LyX/master] * lib/RELEASE-NOTES
Guillaume Munch wrote: > Because on the other hand with qt4 there is the critical > http://www.lyx.org/trac/ticket/9362. I also noticed that lyx is very > slow with qt4 now, with profiling showing that most of the time is spent > in QTextLine::setLineWidth() below GuiFontMetrics::breakAt(). In fact I > find it more annoying than #9731, so much that I switched to 5.5.1. I > wonder whether LyX 2.2 should not be built with qt >= 5.5.1 on Linux > when possible. On linux most people do not compile qt themselves, and simply use the preinstalled version, because it is so much easier. Those who do compile qt are experts, I trust them to choose a good version. > For these reasons as well, I am hoping that for 2.3 the community of LyX > developers will choose to focus on qt >= 5.6. +1 However, I also agree with Jean-Marc: As long as keeping LyX compilable with qt 4.8 is close to zero effort we should support 4.8 as in "LyX compiles and does not crash immediately". Georg
Re: Tarballs for LyX 2.2.0 are on FTP
Scott Kostyshak wrote: > Hi all, > > The tarballs for LyX 2.2.0 can be found at > > ftp://ftp.lyx.org/pub/lyx/devel/lyx-2.2/lyx-2.2.0/ Builds and runs fine on debian 8.1, except when configuring with version suffix: http://www.lyx.org/trac/ticket/10159. Since this also happens with 2.1.4 it is no regression. > As usual I'll wait before announcing the release until after uploading > the binaries and providing some time for the mirrors. > > Thanks to everyone for all the help with the final steps in the release > process. Thank you for all the work you did as release manager! Georg
Re: Minor last minute edits in fr.po
On 05/24/2016 04:02 AM, Jean-Pierre Chrétien wrote: > Le 23/05/2016 23:22, Jean-Pierre Chrétien a écrit : >> Hello, >> >> Jean-Marc pointed out to me a mistake and a shortcut conflict, I have >> 2 commits >> ready fot these. Should this wait for 2.2.1 or may I push to master ? >> > > Richard, one shortcut conflict resolution should be backported to 2.1.5. > Okay to push ? Yes, that's fine. rh
Re: [LyX/master] * lib/RELEASE-NOTES
Le 24/05/2016 à 00:51, Guillaume Munch a écrit : Do you know any other bug on Linux+qt5.5.1 than http://www.lyx.org/trac/ticket/9731 ? Because on the other hand with qt4 there is the critical http://www.lyx.org/trac/ticket/9362. I also noticed that lyx is very slow with qt4 now, with profiling showing that most of the time is spent in QTextLine::setLineWidth() below GuiFontMetrics::breakAt(). In fact I find it more annoying than #9731, so much that I switched to 5.5.1. I wonder whether LyX 2.2 should not be built with qt >= 5.5.1 on Linux when possible. Could you give more details? I do all my development in 4.8, so I am a bit surprised. Or maybe I missed how fast it is now with 5.6 :) Anyway, the new code is faster for me with 4.8 than the old one. For these reasons as well, I am hoping that for 2.3 the community of LyX developers will choose to focus on qt >= 5.6. With Ubuntu 14.04 offering 5.2.1 and 16.04 offering 5.5.1, this seems premature to me, especially when the cost of supporting 4.8 is low for now as far as I can see. We shall of course remove support for Qt < 4.8. JMarc
Re: Minor last minute edits in fr.po
Le 23/05/2016 23:22, Jean-Pierre Chrétien a écrit : Hello, Jean-Marc pointed out to me a mistake and a shortcut conflict, I have 2 commits ready fot these. Should this wait for 2.2.1 or may I push to master ? Richard, one shortcut conflict resolution should be backported to 2.1.5. Okay to push ? -- Jean-Pierre commit 975f8ab1cb1c0c92925a1c4a8192e62a147afd9d Author: jpc Date: Tue May 24 08:57:54 2016 +0100 * Backporting one shortcut conflict solution from master * fr.gmo update diff --git a/po/fr.gmo b/po/fr.gmo index d1bf65b..457182b 100644 Binary files a/po/fr.gmo and b/po/fr.gmo differ diff --git a/po/fr.po b/po/fr.po index 19bf97e..b4d92a6 100644 --- a/po/fr.po +++ b/po/fr.po @@ -322,14 +322,17 @@ # 24 mars 2016 : revue des raccourcis clavier de la fenêtre de citation #suite à une revue similaire pour 2.2 # Mise à jour du numéro de projet : lyx-2.1.5 -# au leiu de 1.6.0 +# au lieu de 1.6.0 +# -- +# 24 mai 2016 : importation d'une résolution de conflit de raccourci +# de la dernière mise à jour pour 2.2.0 # -- msgid "" msgstr "" "Project-Id-Version: LyX 2.1.5\n" "Report-Msgid-Bugs-To: lyx-devel@lists.lyx.org\n" "POT-Creation-Date: 2016-03-24 14:06+\n" -"PO-Revision-Date: 2016-03-24 14:49-\n" +"PO-Revision-Date: 2016-05-24 08:57+0100\n" "Last-Translator: Jean-Pierre Chrétien \n" "Language-Team: lyxfr\n" "Language: fr\n" @@ -29040,7 +29043,7 @@ msgstr "Autres suggestions orthographiques" #: src/frontends/qt4/Menus.cpp:844 msgid "Add to personal dictionary|n" -msgstr "Ajouter au dictionnaire personnel|A" +msgstr "Ajouter au dictionnaire personnel|j" #: src/frontends/qt4/Menus.cpp:846 msgid "Ignore all|I"
