Tarballs for LyX 2.2.0 are on FTP

[Scott Kostyshak]

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/

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.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] * lib/RELEASE-NOTES

[Scott Kostyshak]

On Tue, May 24, 2016 at 01:03:28AM +0100, Guillaume Munch wrote:
> Le 24/05/2016 00:06, Scott Kostyshak a écrit :
> > On Mon, May 23, 2016 at 11:51:11PM +0100, Guillaume Munch wrote:
> > > Le 23/05/2016 23:12, Scott Kostyshak a écrit :
> > > > On Wed, May 11, 2016 at 10:36:13AM -0700, Pavel Sanda wrote:
> > > > > Pavel Sanda wrote:
> > > > > > commit 518876b370ac00f4ee5840a65d40c1d79d0ed2ad
> > > > > > Author: Pavel Sanda 
> > > > > > Date:   Wed May 11 10:31:59 2016 -0700
> > > > > > 
> > > > > >   * lib/RELEASE-NOTES
> > > > > 
> > > > > It would be nice if someone involved in numerous dicussions about
> > > > > various bugs under different Qt 5.x versions wrote summary 
> > > > > paragraph...
> > > > 
> > > > We have the following in RELEASE-NOTES:
> > > > 
> > > > * LyX 2.2.0 and the following 2.2.x releases will continue to work well 
> > > > with
> > > > Qt 4.5 (and later Qt 4.x) but will also support Qt 5.6, which 
> > > > brings some
> > > > advantages most notably for users with HiDPI displays. Note that if 
> > > > you
> > > > compile LyX with a Qt 5 release before 5.6 you are likely to run 
> > > > into
> > > > several regressions with respect to Qt 4.x. See #9215 for a list of 
> > > > bugs
> > > > related to compiling LyX with different versions of Qt.
> > > > 
> > > > I think it is sufficient. The nice thing is that we can add more
> > > > information to #9215 after release if we want since we reference it.
> > > > 
> > > 
> > > Do you know any other bug on Linux+qt5.5.1 than
> > > http://www.lyx.org/trac/ticket/9731 ?
> > 
> > Not offhand but I'm sure there are some that I cannot remember. I might
> > look through our bugs with "qtbug" keyword and improve #9215.
> > 
> > > 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.
> > 
> > Is the above with 4.8.6? Is there a chance that 4.8.7 has improved
> > something?
> 
> I noticed this starting with 4.8.7.

Dang. Good to know.

Scott

> > > I wonder whether
> > > LyX 2.2 should not be built with qt >= 5.5.1 on Linux when possible.
> > 
> > > 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
> > 
> > Note that Ubuntu 16.04 shipped Qt 5.5.1 and that will be around for a
> > while. It would be nice to test our LyX with that Qt version as well.
> 
> Yes, one can expect feedback from this version as well.


signature.asc
Description: PGP signature

Re: [LyX/master] * lib/RELEASE-NOTES

[Guillaume Munch]

Le 24/05/2016 00:06, Scott Kostyshak a écrit :

On Mon, May 23, 2016 at 11:51:11PM +0100, Guillaume Munch wrote:

Le 23/05/2016 23:12, Scott Kostyshak a écrit :

On Wed, May 11, 2016 at 10:36:13AM -0700, Pavel Sanda wrote:

Pavel Sanda wrote:

commit 518876b370ac00f4ee5840a65d40c1d79d0ed2ad
Author: Pavel Sanda 
Date:   Wed May 11 10:31:59 2016 -0700

  * lib/RELEASE-NOTES


It would be nice if someone involved in numerous dicussions about
various bugs under different Qt 5.x versions wrote summary paragraph...


We have the following in RELEASE-NOTES:

* LyX 2.2.0 and the following 2.2.x releases will continue to work well with
Qt 4.5 (and later Qt 4.x) but will also support Qt 5.6, which brings some
advantages most notably for users with HiDPI displays. Note that if you
compile LyX with a Qt 5 release before 5.6 you are likely to run into
several regressions with respect to Qt 4.x. See #9215 for a list of bugs
related to compiling LyX with different versions of Qt.

I think it is sufficient. The nice thing is that we can add more
information to #9215 after release if we want since we reference it.



Do you know any other bug on Linux+qt5.5.1 than
http://www.lyx.org/trac/ticket/9731 ?


Not offhand but I'm sure there are some that I cannot remember. I might
look through our bugs with "qtbug" keyword and improve #9215.


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.


Is the above with 4.8.6? Is there a chance that 4.8.7 has improved
something?


I noticed this starting with 4.8.7.




I wonder whether
LyX 2.2 should not be built with qt >= 5.5.1 on Linux when possible.



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

Note that Ubuntu 16.04 shipped Qt 5.5.1 and that will be around for a
while. It would be nice to test our LyX with that Qt version as well.


Yes, one can expect feedback from this version as well.

Re: #10145: Lyx 2.2rc1 Mac not opening

[Stephan Witt]

Am 20.05.2016 um 18:05 schrieb Stephan Witt :
> 
> Am 20.05.2016 um 17:56 schrieb Bryan Brown :
>> 
>> Thanks for the prompt response.
>> 
>> I backed up and deleted the preferences file and Lxy 2.2 came right up.  
>> When i tried to open a document it reported “cannot load basic module” and a 
>> lot of associated problems.
>> 
>> I then deleted the Lyx 2.2 app and Lyx-2.2 directory in ~/Library and then 
>> ran my 2.1.4 installation.  I then renamed the 2.1.4 app to OldLyx and 
>> reinstalled by copying Lyx 2.2 to Applications.  It seems to be working.  I 
>> have no idea why it works now but didn’t before.  That is pretty much what I 
>> did before.
>> 
>> I will now try to get my laptop installation to work.  It had the same 
>> problem.
> 
> Hi Bill,
> 
> if possible, please make an archive of the contents of the folder 
> ~/Library/Application\ Support/LyX-2.1 first.
> It would be of great help to know what went wrong while doing the upgrade. 
> Thanks.

Hi Bill,

did you get your laptop installation to work? If yes, how did you do it?

Are you able to provide the contents of the LyX-2.1 folder?

Stephan

Re: [LyX/master] * lib/RELEASE-NOTES

[Scott Kostyshak]

On Mon, May 23, 2016 at 11:51:11PM +0100, Guillaume Munch wrote:
> Le 23/05/2016 23:12, Scott Kostyshak a écrit :
> > On Wed, May 11, 2016 at 10:36:13AM -0700, Pavel Sanda wrote:
> > > Pavel Sanda wrote:
> > > > commit 518876b370ac00f4ee5840a65d40c1d79d0ed2ad
> > > > Author: Pavel Sanda 
> > > > Date:   Wed May 11 10:31:59 2016 -0700
> > > > 
> > > >  * lib/RELEASE-NOTES
> > > 
> > > It would be nice if someone involved in numerous dicussions about
> > > various bugs under different Qt 5.x versions wrote summary paragraph...
> > 
> > We have the following in RELEASE-NOTES:
> > 
> > * LyX 2.2.0 and the following 2.2.x releases will continue to work well with
> >Qt 4.5 (and later Qt 4.x) but will also support Qt 5.6, which brings some
> >advantages most notably for users with HiDPI displays. Note that if you
> >compile LyX with a Qt 5 release before 5.6 you are likely to run into
> >several regressions with respect to Qt 4.x. See #9215 for a list of bugs
> >related to compiling LyX with different versions of Qt.
> > 
> > I think it is sufficient. The nice thing is that we can add more
> > information to #9215 after release if we want since we reference it.
> > 
> 
> Do you know any other bug on Linux+qt5.5.1 than
> http://www.lyx.org/trac/ticket/9731 ?

Not offhand but I'm sure there are some that I cannot remember. I might
look through our bugs with "qtbug" keyword and improve #9215.

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

Is the above with 4.8.6? Is there a chance that 4.8.7 has improved
something?

> I wonder whether
> LyX 2.2 should not be built with qt >= 5.5.1 on Linux when possible.

> 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

Note that Ubuntu 16.04 shipped Qt 5.5.1 and that will be around for a
while. It would be nice to test our LyX with that Qt version as well.

Scott


signature.asc
Description: PGP signature

Re: [LyX/master] * lib/RELEASE-NOTES

[Guillaume Munch]

Le 23/05/2016 23:12, Scott Kostyshak a écrit :

On Wed, May 11, 2016 at 10:36:13AM -0700, Pavel Sanda wrote:

Pavel Sanda wrote:

commit 518876b370ac00f4ee5840a65d40c1d79d0ed2ad
Author: Pavel Sanda 
Date:   Wed May 11 10:31:59 2016 -0700

 * lib/RELEASE-NOTES


It would be nice if someone involved in numerous dicussions about
various bugs under different Qt 5.x versions wrote summary paragraph...


We have the following in RELEASE-NOTES:

* LyX 2.2.0 and the following 2.2.x releases will continue to work well with
   Qt 4.5 (and later Qt 4.x) but will also support Qt 5.6, which brings some
   advantages most notably for users with HiDPI displays. Note that if you
   compile LyX with a Qt 5 release before 5.6 you are likely to run into
   several regressions with respect to Qt 4.x. See #9215 for a list of bugs
   related to compiling LyX with different versions of Qt.

I think it is sufficient. The nice thing is that we can add more
information to #9215 after release if we want since we reference it.



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.


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.

Re: [LyX/master] * lib/RELEASE-NOTES

[Scott Kostyshak]

On Wed, May 11, 2016 at 10:36:13AM -0700, Pavel Sanda wrote:
> Pavel Sanda wrote:
> > commit 518876b370ac00f4ee5840a65d40c1d79d0ed2ad
> > Author: Pavel Sanda 
> > Date:   Wed May 11 10:31:59 2016 -0700
> > 
> > * lib/RELEASE-NOTES
> 
> It would be nice if someone involved in numerous dicussions about 
> various bugs under different Qt 5.x versions wrote summary paragraph...

We have the following in RELEASE-NOTES:

* LyX 2.2.0 and the following 2.2.x releases will continue to work well with
  Qt 4.5 (and later Qt 4.x) but will also support Qt 5.6, which brings some
  advantages most notably for users with HiDPI displays. Note that if you
  compile LyX with a Qt 5 release before 5.6 you are likely to run into
  several regressions with respect to Qt 4.x. See #9215 for a list of bugs
  related to compiling LyX with different versions of Qt.

I think it is sufficient. The nice thing is that we can add more
information to #9215 after release if we want since we reference it.

Scott


signature.asc
Description: PGP signature

Re: Minor last minute edits in fr.po

[Scott Kostyshak]

On Mon, May 23, 2016 at 11:59:04PM +0100, Jean-Pierre Chrétien wrote:
> Le 23/05/2016 22:54, Scott Kostyshak a écrit :
> > On Mon, May 23, 2016 at 11:22:02PM +0100, Jean-Pierre Chrétien wrote:
> > > 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
> > > ?
> > 
> > Go ahead. Thanks for the fixes.
> 
> Done

Thanks,

Scott

> 
> -- 
> Jean-Pierre
> 
> 


signature.asc
Description: PGP signature

Re: Using xmllint to test our LyXHTML export

[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?
> 
> Did you check for the failure reasons?
> 
> 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).




signature.asc
Description: PGP signature

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

[Scott Kostyshak]

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.

Scott

> 
> JMarc
> 
> > diff --git a/lib/RELEASE-NOTES b/lib/RELEASE-NOTES
> > index d3ac4c4..4fab9b7 100644
> > --- a/lib/RELEASE-NOTES
> > +++ b/lib/RELEASE-NOTES
> > @@ -118,6 +118,9 @@
> >several regressions with respect to Qt 4.x. See #9215 for a list of bugs
> >related to compiling LyX with different versions of Qt.
> > 
> > +* The Qt libraries must have support for the SVG graphic format, because
> > +  LyX now uses svg icons. If this support is lacking, icons cannot be 
> > shown.
> > +
> >  * If compiling LyX on Windows with Qt 5.6, it is recommended to use MSVC 
> > 2015
> >update 2 to avoid #9892.
> 


signature.asc
Description: PGP signature

Re: Minor last minute edits in fr.po

[Jean-Pierre Chrétien]

Le 23/05/2016 22:54, Scott Kostyshak a écrit :

On Mon, May 23, 2016 at 11:22:02PM +0100, Jean-Pierre Chrétien wrote:

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
?


Go ahead. Thanks for the fixes.


Done

--
Jean-Pierre

Re: Minor last minute edits in fr.po

[Scott Kostyshak]

On Mon, May 23, 2016 at 11:22:02PM +0100, Jean-Pierre Chrétien wrote:
> 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
> ?

Go ahead. Thanks for the fixes.

Scott

> 
> -- 
> Jean-Pierre
> 
> commit 9e5198f4f59a1059b116381bb75070cbcf20bc82
> Author: jpc 
> Date:   Mon May 23 23:15:10 2016 +0100
> 
> * One more shortcut conflict solved
> * fr.gmo updated
> 
> diff --git a/po/fr.gmo b/po/fr.gmo
> index 84ebb9e..7f59870 100644
> Binary files a/po/fr.gmo and b/po/fr.gmo differ
> diff --git a/po/fr.po b/po/fr.po
> index 3dd65b2..dc434d0 100644
> --- a/po/fr.po
> +++ b/po/fr.po
> @@ -311,14 +311,14 @@
>  # 22 avril 2016 : dernière revue avant 2.2.0
>  # --
>  # 23 mai 2016 : correction d'une erreur de traduction (tailles d'icônes)
> -#   et d'un conflit de raccourcis
> +#   et de conflits de raccourcis
>  # --
>  msgid ""
>  msgstr ""
>  "Project-Id-Version: LyX 2.2\n"
>  "Report-Msgid-Bugs-To: lyx-devel@lists.lyx.org\n"
>  "POT-Creation-Date: 2016-04-22 18:34+0100\n"
> -"PO-Revision-Date: 2016-05-23 22:37+0100\n"
> +"PO-Revision-Date: 2016-05-23 23:13+0100\n"
>  "Last-Translator: Jean-Pierre Chrétien \n"
>  "Language-Team: lyxfr\n"
>  "Language: fr\n"
> @@ -30147,7 +30147,7 @@ msgstr "Ajouter au dictionnaire personnel|j"
> 
>  #: src/frontends/qt4/Menus.cpp:844
>  msgid "Ignore all|I"
> -msgstr "Tout ignorer|o"
> +msgstr "Tout ignorer|T"
> 
>  #: src/frontends/qt4/Menus.cpp:852
>  msgid "Remove from personal dictionary|r"
> 
> commit f5146e729bb9ef3124056c675e7bdbb1afbc85de
> Author: jpc 
> Date:   Mon May 23 22:43:39 2016 +0100
> 
> * Edit translation mistakes for icon sizes
> * Resolve a shortcut conflict
> * Provide fr.gmo using msgfmt
> 
> diff --git a/po/fr.gmo b/po/fr.gmo
> index 869041d..84ebb9e 100644
> Binary files a/po/fr.gmo and b/po/fr.gmo differ
> diff --git a/po/fr.po b/po/fr.po
> index 8f235de..3dd65b2 100644
> --- a/po/fr.po
> +++ b/po/fr.po
> @@ -310,12 +310,15 @@
>  # --
>  # 22 avril 2016 : dernière revue avant 2.2.0
>  # --
> +# 23 mai 2016 : correction d'une erreur de traduction (tailles d'icônes)
> +#   et d'un conflit de raccourcis
> +# --
>  msgid ""
>  msgstr ""
>  "Project-Id-Version: LyX 2.2\n"
>  "Report-Msgid-Bugs-To: lyx-devel@lists.lyx.org\n"
>  "POT-Creation-Date: 2016-04-22 18:34+0100\n"
> -"PO-Revision-Date: 2016-04-22 18:46+0100\n"
> +"PO-Revision-Date: 2016-05-23 22:37+0100\n"
>  "Last-Translator: Jean-Pierre Chrétien \n"
>  "Language-Team: lyxfr\n"
>  "Language: fr\n"
> @@ -29621,11 +29624,11 @@ msgstr "Icônes de grande taille"
> 
>  #: src/frontends/qt4/GuiView.cpp:361
>  msgid "Huge-sized icons"
> -msgstr "Icônes de grande taille"
> +msgstr "Icônes de taille énorme"
> 
>  #: src/frontends/qt4/GuiView.cpp:368
>  msgid "Giant-sized icons"
> -msgstr "Icônes de très grande taille"
> +msgstr "Icônes de taille gigantesque"
> 
>  #: src/frontends/qt4/GuiView.cpp:639
>  #, c-format
> @@ -30140,7 +30143,7 @@ msgstr "Autres suggestions orthographiques"
> 
>  #: src/frontends/qt4/Menus.cpp:842
>  msgid "Add to personal dictionary|n"
> -msgstr "Ajouter au dictionnaire personnel|A"
> +msgstr "Ajouter au dictionnaire personnel|j"
> 
>  #: src/frontends/qt4/Menus.cpp:844
>  msgid "Ignore all|I"


signature.asc
Description: PGP signature

Minor last minute edits in fr.po

[Jean-Pierre Chrétien]

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 ?


--
Jean-Pierre

commit 9e5198f4f59a1059b116381bb75070cbcf20bc82
Author: jpc 
Date:   Mon May 23 23:15:10 2016 +0100

* One more shortcut conflict solved
* fr.gmo updated

diff --git a/po/fr.gmo b/po/fr.gmo
index 84ebb9e..7f59870 100644
Binary files a/po/fr.gmo and b/po/fr.gmo differ
diff --git a/po/fr.po b/po/fr.po
index 3dd65b2..dc434d0 100644
--- a/po/fr.po
+++ b/po/fr.po
@@ -311,14 +311,14 @@
 # 22 avril 2016 : dernière revue avant 2.2.0
 # --
 # 23 mai 2016 : correction d'une erreur de traduction (tailles d'icônes)
-#   et d'un conflit de raccourcis
+#   et de conflits de raccourcis
 # --
 msgid ""
 msgstr ""
 "Project-Id-Version: LyX 2.2\n"
 "Report-Msgid-Bugs-To: lyx-devel@lists.lyx.org\n"
 "POT-Creation-Date: 2016-04-22 18:34+0100\n"
-"PO-Revision-Date: 2016-05-23 22:37+0100\n"
+"PO-Revision-Date: 2016-05-23 23:13+0100\n"
 "Last-Translator: Jean-Pierre Chrétien \n"
 "Language-Team: lyxfr\n"
 "Language: fr\n"
@@ -30147,7 +30147,7 @@ msgstr "Ajouter au dictionnaire personnel|j"

 #: src/frontends/qt4/Menus.cpp:844
 msgid "Ignore all|I"
-msgstr "Tout ignorer|o"
+msgstr "Tout ignorer|T"

 #: src/frontends/qt4/Menus.cpp:852
 msgid "Remove from personal dictionary|r"

commit f5146e729bb9ef3124056c675e7bdbb1afbc85de
Author: jpc 
Date:   Mon May 23 22:43:39 2016 +0100

* Edit translation mistakes for icon sizes
* Resolve a shortcut conflict
* Provide fr.gmo using msgfmt

diff --git a/po/fr.gmo b/po/fr.gmo
index 869041d..84ebb9e 100644
Binary files a/po/fr.gmo and b/po/fr.gmo differ
diff --git a/po/fr.po b/po/fr.po
index 8f235de..3dd65b2 100644
--- a/po/fr.po
+++ b/po/fr.po
@@ -310,12 +310,15 @@
 # --
 # 22 avril 2016 : dernière revue avant 2.2.0
 # --
+# 23 mai 2016 : correction d'une erreur de traduction (tailles d'icônes)
+#   et d'un conflit de raccourcis
+# --
 msgid ""
 msgstr ""
 "Project-Id-Version: LyX 2.2\n"
 "Report-Msgid-Bugs-To: lyx-devel@lists.lyx.org\n"
 "POT-Creation-Date: 2016-04-22 18:34+0100\n"
-"PO-Revision-Date: 2016-04-22 18:46+0100\n"
+"PO-Revision-Date: 2016-05-23 22:37+0100\n"
 "Last-Translator: Jean-Pierre Chrétien \n"
 "Language-Team: lyxfr\n"
 "Language: fr\n"
@@ -29621,11 +29624,11 @@ msgstr "Icônes de grande taille"

 #: src/frontends/qt4/GuiView.cpp:361
 msgid "Huge-sized icons"
-msgstr "Icônes de grande taille"
+msgstr "Icônes de taille énorme"

 #: src/frontends/qt4/GuiView.cpp:368
 msgid "Giant-sized icons"
-msgstr "Icônes de très grande taille"
+msgstr "Icônes de taille gigantesque"

 #: src/frontends/qt4/GuiView.cpp:639
 #, c-format
@@ -30140,7 +30143,7 @@ msgstr "Autres suggestions orthographiques"

 #: src/frontends/qt4/Menus.cpp:842
 msgid "Add to personal dictionary|n"
-msgstr "Ajouter au dictionnaire personnel|A"
+msgstr "Ajouter au dictionnaire personnel|j"

 #: src/frontends/qt4/Menus.cpp:844
 msgid "Ignore all|I"

Re: de-UserGuide improvements

[Guenter Milde]

On 2016-05-09, mn wrote:
> On 07.05.16 20:20, Guenter Milde wrote:


>>> For English doc/UserGuide.lyx.

>>> [Since I prefer direct input I am also in favor of rephrasing this to
>>> “can use”.]

>> Also missing is a sentence about the possibility to reset the "smart
>> quote" key-binding if you prefer to insert the ASCII quote with " and
>> typographical quotes via system shortcuts.

> Nice. I hold that to be ideal.

Have a look at the commit in the 2.3-staging branch. Is this what you
intended?

>> The User-Guide is "interactive", i.e. it adapts the description to the
>> current configuration. This is intended.

> As I commented previously, I noticed that en-UserGuide employs this
> \shortcut-macro – also in other parts of the doc; in turn leading to
> possible problems with the page margins.

>> These side-effects should be either disregarded or handled by some
>> means other than reversing the interactivity (e.g. "\sloppy" line
>> wrapping).

> If some of these side-effects are margin violations?
> These cannot be ignored, imho.

Why not? Margin violations are also common for "normal" teletyped text.
I agree it would be better to avoid them, though but this is fine tuning
where there is more important work to do...

> The adaption is nifty indeed.

> Come to think of it, this adaptability might also add a little confusion
> for newbies switching platforms. LyX is multi platform (to avoid
> -independent). But these key-bindings are clearly not identical on
> different OSes.

> Would a little footnote explaining this behavior clear things up?
> These problems might arise if you actually print out the manuals, reuse
> PDFs from a different platform or download the PDFs from the LyX-site.

I believe that this is usual for software manuals - keybindings may be
different due to localization or a different OS or version...

Where would you put the footnote?

> And even after googling for it again I do not know how this
> macro is created within LyX (since it does not show itself as
> ERT).

 It is expanded within LyX and not by LaTeX. I.e. the tex source
 already contains the expanded version (similar to the
 substitution of Unicode characters by LICR macros).

>>> This explains how the shortcut-inset is handled once it is in a
>>> LyX document. How does one create it in LyX?

>> M-x info-insert

>> It is not custom (created by a layout) but hard-coded in LyX.

> I was asking this howto since I was not able to manipulate this
> inset/macro on my own. It is missing in de-UserGuide.

It is missing there because this is regarded a "develper tool". Most
end-users will never need it.


> But there seems to be a slight anomaly?
> Meta (Alt) on linux worked out of the box.
> On Mac this Meta is switched to Ctrl.
> But I tried Alt-x first, which produces just the following character: ≈

Are you sure this was Alt-x and not AltGr-x?

> Now, after that,
> Ctrl-x ceases functionality for the rest of the session.

Strange indeed.

The UserGuide in branch "master" has now Unicode characters instead of
the "quote inset" :-)

Günter

Re: Using xmllint to test our LyXHTML export

[Guenter Milde]

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?

Do you have a list of failing tests?

Did you check for the failure reasons?

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).

Günter

Re: Using xmllint to test our LyXHTML export

[Kornel Benko]

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?
>
> > These tests would be fast (compared to the LaTeX compilation tests we
> > have). I think our current XHTML tests just check that the exit code is
> > zero. We can extend these tests to work as follows:
>
> > 1. Export to .xhtml and check the exit code.
> > 2. Check the terminal output from LyX (I think we do this for other tests, 
> > such
> > as the lyx2lyx tests).
> > 3. Use xmllint or something similar and check exit code.
>
> This would be a great improvement of the tests indeed.
>
> (I remember that there used to be more case of invalid xhtml and I am not
> sure whether we fixed everything...)
>
> > I know nothing about XHTML. Does anyone have experience with xmllint or
> > any other tool? The only other tool I saw mentioned when searching is
> > XMLStarlet. If someone does have experience, which tool do you
> > recommend? Also, I'd be curious which options you think should be used.
> > It seems to me that we would not want a very strict validation, and
> > basically want to check whether the file is expected to open in a
> > webbrowser without parser errors.
>
> We could start with a basic check and get more strict later...
>
>
> Günter
>

I have a patch ready. But now many of xhtml export tests are failing.

Kornel

signature.asc
Description: This is a digitally signed message part.
diff --git a/development/autotests/ExportTests.cmake b/development/autotests/ExportTests.cmake
index f448d80..562c639 100644
--- a/development/autotests/ExportTests.cmake
+++ b/development/autotests/ExportTests.cmake
@@ -27,6 +27,7 @@
 #
 
 find_package(Perl)
+find_program(XMLLINT_EXECUTABLE xmllint)
 
 if(PERL_FOUND)
   set(DVI_FORMATS "dvi" "dvi3")
@@ -401,6 +402,7 @@ foreach(libsubfolderx autotests/export lib/doc lib/examples lib/templates autote
 -Dinverted=${inverted}
 -DTOP_SRC_DIR=${TOP_SRC_DIR}
 -DPERL_EXECUTABLE=${PERL_EXECUTABLE}
+-DXMLLINT_EXECUTABLE=${XMLLINT_EXECUTABLE}
 -P "${TOP_SRC_DIR}/development/autotests/export.cmake")
   setmarkedtestlabel(${TestName} ${mytestlabel}) # check for suspended pdf/dvi exports
 endif()
diff --git a/development/autotests/export.cmake b/development/autotests/export.cmake
index 29487d4..4668ccd 100755
--- a/development/autotests/export.cmake
+++ b/development/autotests/export.cmake
@@ -25,6 +25,7 @@
 #   -Dinverted=[01] \
 #   -DTOP_SRC_DIR=${TOP_SRC_DIR}
 #   -DPERL_EXECUTABLE=${PERL_EXECUTABLE}
+#   -DXMLLINT_EXECUTABLE=${XMLLINT_EXECUTABLE}
 #   -P "${TOP_SRC_DIR}/development/autotests/export.cmake"
 #
 
@@ -138,6 +139,24 @@ else()
   set(_err -1)
 else()
   message(STATUS "Expected result file \"${result_file_name}\" exists")
+  if (format MATCHES "xhtml")
+if (XMLLINT_EXECUTABLE)
+  # check the created xhtml file
+  execute_process(
+COMMAND ${XMLLINT_EXECUTABLE} --noout --html --valid "${result_file_name}"
+ERROR_VARIABLE xmlerr
+RESULT_VARIABLE _err)
+  if (NOT _err)
+# check if error output not empty
+if (NOT xmlerr STREQUAL "")
+  # Here, the check shows errors although the process
+  # exited with "0"
+  message(STATUS ${xmlerr})
+  set(_err -1)
+endif()
+  endif()
+endif()
+  endif()
 endif()
   endif()
 endif()
@@ -147,7 +166,7 @@ if(inverted)
 else()
   string(COMPARE NOTEQUAL  ${_err} 0 _erg)
 endif()
-execute_process(COMMAND ${CMAKE_COMMAND} -E remove_directory "${TempDir}")
+#execute_process(COMMAND ${CMAKE_COMMAND} -E remove_directory "${TempDir}")
 if(_erg)
   message(STATUS "Exporting ${file}.lyx to ${format}")
   message(FATAL_ERROR "Export failed")

Re: We will have to change our output for newest LuaTeX

[Guenter Milde]

On 2016-05-22, Scott Kostyshak wrote:
> On Sun, May 22, 2016 at 07:22:12PM +, Guenter Milde wrote:
>> On 2016-05-22, Scott Kostyshak wrote:
...
>> >> > > On 2016-05-20, Scott Kostyshak wrote:
>> >> > 
>> >> > >> There have been some changes in the luatex engine that will be
>> >> > >> shipped with TeX Live 2016 that cause many of our tests to fail
>> >> > >> (500 something instead of 100 something on TL 2015). The root
>> >> > >> issue is discussed on the LuaTeX mailing list at [1].

>> >> > >> There is a transitional package available, luatex85, that should
>> >> > >> make our current LuaTeX code work. A reasonable approach for now
>> >> > >> would be to use the package if it is available and to not use it
>> >> > >> if not, keeping the rest of our LuaTeX export code the same.
>> >> > ...
>> >> > > We could just add
>> >> > ...
>> >> >  \IfFileExists{luatex85.sty}{\usepackage{luatex85}}{}
>> >> > ...
>> >> > 
>> >> > >> Should we do this only when we use code that we think needs it? Or
>> >> > >> should we just add it to all of our LuaTeX exports?
>> >> > 
>> >> > I propose to do this with every LuaTeX export

>> After reading the luatex85 documentation I changed my mind.

>> Unless LyX uses the offending commands directly, this is a LaTeX issue.

LyX uses the offending commands directly (see below), so we have to do
something.

>> Can you specify which tests fail?

> I think the root issue for the failing tests is the following:

> 1. Start a new document.
> 2. Go to Document > Settings > Page Layout and select A4 format. Save
> settings.
> 3. Compile with LuaTeX

> An undefined control sequence error is given.

> Would you prefer the list of tests that fail or is the above MWE good
> enough?

It is fine. Even without the new luatex, I see that the offending part is
the use of:

%% LyX specific LaTeX commands.
\pdfpageheight\paperheight
\pdfpagewidth\paperwidth


in case a non-standard paper size is set.

IMO, LyX should write

%% LyX specific LaTeX commands.
\IfFileExists{luatex85.sty}{\usepackage{luatex85}}{}
\pdfpageheight\paperheight
\pdfpagewidth\paperwidth

if exporting to LuaTeX and \pdfpage* commands are required.
(With a comment in the code to change this to the new syntax next year or
so...)

Günter

Re: Using xmllint to test our LyXHTML export

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

> These tests would be fast (compared to the LaTeX compilation tests we
> have). I think our current XHTML tests just check that the exit code is
> zero. We can extend these tests to work as follows:

> 1. Export to .xhtml and check the exit code.
> 2. Check the terminal output from LyX (I think we do this for other tests, 
> such
> as the lyx2lyx tests).
> 3. Use xmllint or something similar and check exit code.

This would be a great improvement of the tests indeed.

(I remember that there used to be more case of invalid xhtml and I am not
sure whether we fixed everything...)

> I know nothing about XHTML. Does anyone have experience with xmllint or
> any other tool? The only other tool I saw mentioned when searching is
> XMLStarlet. If someone does have experience, which tool do you
> recommend? Also, I'd be curious which options you think should be used.
> It seems to me that we would not want a very strict validation, and
> basically want to check whether the file is expected to open in a
> webbrowser without parser errors.

We could start with a basic check and get more strict later...


Günter

Re: LyX does work with ImageMagick 7

[Guenter Milde]

On 2016-05-23, Uwe Stöhr wrote:
> Am 21.05.2016 um 11:27 schrieb Georg Baum:

...

>> 2) LyX works perfectly with Imagemagick 7. I tested that without the
>> convert symlink. I could not see any difference to IM 6 (and I made sure
>> I deleted the image cache and reconfigured). I guess what might have
>> lead to the assumption that IM 7 does not work is the fact that the info
>> inset produces text output for .svgz images, but an image link for .png
>> images. This should be changed, modern browsers support svg (but may
>> need uncompressing, I don't know).

> Yes, the latest Firefox can display SVG but not SVGZ. Googling around it 
> turns out that this is the same for IE and Safari.
> I only found this as solution:
> http://graphicdesign.stackexchange.com/questions/24797/when-should-i-use-svg-or-svgz-for-my-web-graphics

IMO, LyX's HTML export should convert svgz to svg then.

We could also consider to convert other vector graphics like PDF to SVG.


Günter