Re: 2.2

Am 16.05.2015 um 00:37 schrieb Enrico Forestieri for...@lyx.org: On Fri, May 15, 2015 at 04:58:24PM +0200, Stephan Witt wrote: Am 15.05.2015 um 16:48 schrieb Enrico Forestieri for...@lyx.org: On Fri, May 15, 2015 at 04:31:05PM +0200, Stephan Witt wrote: This results in the following

Re: Make RELEASE-NOTES accessible from GUI (#8616)

On Mon, May 18, 2015 at 12:49 PM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Le 18/05/2015 12:04, Jürgen Spitzmüller a écrit : 2015-05-18 11:58 GMT+02:00 Jean-Marc Lasgouttes: Did you consider the possibility to have a LyX file that we would just export to text? If it is

Re: Understanding the /origin parameter

Am 18.05.2015 um 09:17 schrieb Enrico Forestieri for...@lyx.org: On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: Scott Kostyshak wrote: When I am working on the documentation, any save now adds the following: +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ Do we

Re: Understanding the /origin parameter

Am 18.05.2015 um 10:09 schrieb Stephan Witt st.w...@gmx.net: Am 18.05.2015 um 09:17 schrieb Enrico Forestieri for...@lyx.org: On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: Scott Kostyshak wrote: When I am working on the documentation, any save now adds the following:

Re: [LyX/master] Correctly load documents moved elsewhere after save.

Le 16/05/2015 19:52, Enrico Forestieri a écrit : commit 62d36bf04d436c83ddace8aeaf4dbd493d674cdf Author: Enrico Forestieri for...@lyx.org Date: Sat May 16 19:51:53 2015 +0200 Correctly load documents moved elsewhere after save. Now clang complains because of the new

Re: Understanding the /origin parameter

Le 18/05/2015 09:17, Enrico Forestieri a écrit : Do we really have to ship author/login used in the machine? I thought we have big fight already that we do not want to put such kind of things without explicit permission on the user side. There will not be any author/login used in the machine.

Re: Compilation error with gcc 4.6

On 05/18/2015 12:17 PM, Jean-Marc Lasgouttes wrote: Since this week-end, I have compilation errors with gcc 4.6. I am not sure from where to start to diagnose this. This is the same error I reported earlier https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg187530.html with gcc 4.9. I

Re: Compilation error with gcc 4.6

2015-05-18 19:24 GMT+02:00 Richard Heck: On 05/18/2015 12:17 PM, Jean-Marc Lasgouttes wrote: Since this week-end, I have compilation errors with gcc 4.6. I am not sure from where to start to diagnose this. This is the same error I reported earlier

Re: Understanding the /origin parameter

On 05/18/2015 05:09 AM, Jean-Marc Lasgouttes wrote: Le 18/05/2015 11:02, Enrico Forestieri a écrit : Yes, but user files will contain this information... Isn't there a way to avoid it at least when it is not useful? The user files already contain this information when storing absolute paths.

Re: Compilation error with gcc 4.6

2015-05-18 19:29 GMT+02:00 Jürgen Spitzmüller sp...@lyx.org: 2015-05-18 19:24 GMT+02:00 Richard Heck: On 05/18/2015 12:17 PM, Jean-Marc Lasgouttes wrote: Since this week-end, I have compilation errors with gcc 4.6. I am not sure from where to start to diagnose this. This is the same

Compilation error with gcc 4.6

Since this week-end, I have compilation errors with gcc 4.6. I am not sure from where to start to diagnose this. JMarc In file included from /usr/include/c++/4.6/bits/concept_check.h:55:0, from /usr/include/c++/4.6/bits/move.h:34, from

Re: 2.2

Le 18/05/2015 17:06, Stephan Witt a écrit : I'm unsure - with the previous code returning a pixmap missing pixmaps are ignored silently. With the change proposed by Enrico it is easy to add a error or warning message. The price is the change of many files containing a call to the getPixmap()

Re: Understanding the /origin parameter

On Mon, May 18, 2015 at 11:14:19AM +0200, Jean-Marc Lasgouttes wrote: Le 18/05/2015 11:07, Enrico Forestieri a écrit : Anyway, I am ready to revert everything if this is wanted. I do not know whether reverting everything is what is needed. I do not feel very at ease with a solution where

Re: [patch] support for \fcolorbox and \colorbox

Am Sonntag, 17. Mai 2015 um 14:35:57, schrieb Georg Baum georg.b...@post.rwth-aachen.de Uwe Stöhr wrote: Am 16.05.2015 um 11:17 schrieb Georg Baum: tex2lyx produces broken documents now. Running the tests gives lots of Lexer.cpp (936): Missing 'framecolor'-tag in

Re: 2.2

Jean-Marc Lasgouttes schreef op 13-5-2015 om 10:42: Hi there, The ritual question: what is still needed for 2.2? I guess we are still waiting for some python 3.3 goodness from José, but what else? It seems to me that publishing a beta version soon is very desirable. Consider that for 2.1

Re: boost update?

Georg Baum schreef op 16-5-2015 om 10:19: Hi, I tested LyX with boost 1.58, and it compiles and runs fine. Shall I update the included boost? This would get rid of some compiler warnings, and since 2.2 will live for a while I guess it is good to start with a recent boost, since a boost update

Re: Make RELEASE-NOTES accessible from GUI (#8616)

Jean-Marc Lasgouttes wrote: Le 18/05/2015 12:04, Jürgen Spitzmüller a écrit : If you prefer this approach, go ahead. I don't know, what do other people think? As I filed the bug I am very glad that it is being worked on, and I don't need to do it myself;-) Concerning the format and

Re: Make RELEASE-NOTES accessible from GUI (#8616)

Le 18/05/15 22:08, Georg Baum a écrit : Concerning the format and location I cannot really make up my mind. The argument in favour of LyX format is that we produce a document processor, and therefore it is natural to use it also for this kind of text. However, I agree with Jürgen that the About

Re: 2.2

Am 18.05.2015 um 18:11 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: Le 18/05/2015 17:06, Stephan Witt a écrit : I'm unsure - with the previous code returning a pixmap missing pixmaps are ignored silently. With the change proposed by Enrico it is easy to add a error or warning message.

Re: [LyX/master] tex2lyx/text.cpp: support for the commands \fboxsep etc.

Uwe Stöhr wrote: diff --git a/src/tex2lyx/test/box-color-size-space-align.tex b/src/tex2lyx/test/box-color-size-space-align.tex index ab658c6..b004eed 100644 --- a/src/tex2lyx/test/box-color-size-space-align.tex +++ b/src/tex2lyx/test/box-color-size-space-align.tex @@ -157,6 +157,18 @@

Re: boost update?

Le 18 mai 2015 22:24:54 CEST, Vincent van Ravesteijn v...@lyx.org a écrit : Op 18 mei 2015 22:20 schreef Georg Baum georg.b...@post.rwth-aachen.de: Vincent van Ravesteijn wrote: I remember losing my way in many boost::next errors and ununderstandable paragraph iterators. Let's see tomorrow

Re: boost update?

Op 18 mei 2015 22:20 schreef Georg Baum georg.b...@post.rwth-aachen.de: Vincent van Ravesteijn wrote: Last time I tried (not so long ago), I hit a lot of new compiler errors, which I didn't know how to fix. Thank you for fixing those.. It was easy, it was only one: b596330093d. Maybe

Re: boost update?

Vincent van Ravesteijn wrote: Last time I tried (not so long ago), I hit a lot of new compiler errors, which I didn't know how to fix. Thank you for fixing those.. It was easy, it was only one: b596330093d. Maybe our code has some self- healing capabilities:-) Georg

make problem

Dear lyx Team after i update lyx from git, i got error msg when i make lyx: make[6]: *** [GuiBox.o] Error 1 make[6]: Leaving directory '/home/alpha/lyx/src/frontends/qt4' Makefile:819: recipe for target 'all' failed make[5]: *** [all] Error 2 make[5]: Leaving directory

RE: problem in the menu

Dear JMarc thank you English text does not contain a |O (in po string). best regards Hatim Date: Mon, 18 May 2015 12:56:04 +0200 From: lasgout...@lyx.org To: lyx-devel@lists.lyx.org; dr.ha...@hotmail.com Subject: Re: problem in the menu Le 17/05/2015 04:55, hatim ali a écrit : when i

Re: 2.2

Am 18.05.2015 um 22:13 schrieb Stephan Witt st.w...@gmx.net: Am 18.05.2015 um 18:11 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: Le 18/05/2015 17:06, Stephan Witt a écrit : I'm unsure - with the previous code returning a pixmap missing pixmaps are ignored silently. With the change

Fix broadway layout

Broadway layout must have been broken for quite a while. Whenever you hit enter you get abstract environment instead of dialogue. Moving Input clauses down to the end of layout as is in hollywood layout fixes it. I would appreciate if anyone more experienced in our layout machinery gives me ack

Re: Understanding the /origin parameter

Enrico Forestieri wrote: It's magic and it's very predictable. An alternative to reverting would be introducing a preference to allow storing the \origin tag in the file. Without that tag, everything would go as before. I'm fine with any of the alternatives above. Pavel

Re: [LyX/master] GuiBox.cpp: assure that the parameters are not empty

Uwe StĂśhr wrote: commit a5cc5dce3cf009d621685f01a885cfb0a02a50fb Author: Uwe Stöhr uwesto...@lyx.org Date: Fri May 15 03:51:11 2015 +0200 GuiBox.cpp: assure that the parameters are not empty frontends/qt4/GuiBox.cpp: thicknessED-setText(0.4); frontends/qt4/GuiBox.cpp:

Re: Understanding the /origin parameter

Scott Kostyshak wrote: When I am working on the documentation, any save now adds the following: +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ Do we really have to ship author/login used in the machine? I thought we have big fight already that we do not want to put such kind of

Re: Understanding the /origin parameter

Am 18.05.2015 um 08:54 schrieb Pavel Sanda sa...@lyx.org: Scott Kostyshak wrote: When I am working on the documentation, any save now adds the following: +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ Do we really have to ship author/login used in the machine? I thought we

Re: Understanding the /origin parameter

On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: Scott Kostyshak wrote: When I am working on the documentation, any save now adds the following: +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ Do we really have to ship author/login used in the machine? I thought

Re: Understanding the /origin parameter

On Sun, May 17, 2015 at 09:11:32PM -0400, Scott Kostyshak wrote: When I am working on the documentation, any save now adds the following: +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ I just want to confirm that when I commit, it is correct that this will be added to the LyX

Re: 2.2

Le 17/05/2015 18:36, Jürgen Spitzmüller a écrit : Note that it's mostly the German dictionaries that increase the size that much (they have seen some huge changes). The alternative would be to proceed with probably pretty outdated German support. A long-term solution would make it possible to

Re: Understanding the /origin parameter

On Mon, May 18, 2015 at 10:09:42AM +0200, Stephan Witt wrote: Am 18.05.2015 um 09:17 schrieb Enrico Forestieri for...@lyx.org: On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: Scott Kostyshak wrote: When I am working on the documentation, any save now adds the following:

Re: Understanding the /origin parameter

Le 18/05/2015 11:02, Enrico Forestieri a écrit : Yes, but user files will contain this information... Isn't there a way to avoid it at least when it is not useful? The user files already contain this information when storing absolute paths. If I recall correctly, you strongly wanted absolute

Re: Understanding the /origin parameter

On Mon, May 18, 2015 at 11:09:25AM +0200, Jean-Marc Lasgouttes wrote: Le 18/05/2015 11:02, Enrico Forestieri a écrit : Yes, but user files will contain this information... Isn't there a way to avoid it at least when it is not useful? The user files already contain this information when

Re: Understanding the /origin parameter

On Mon, May 18, 2015 at 09:50:00AM +0200, Jean-Marc Lasgouttes wrote: Le 18/05/2015 09:17, Enrico Forestieri a écrit : Do we really have to ship author/login used in the machine? I thought we have big fight already that we do not want to put such kind of things without explicit permission on

Re: Compilation Failure

2015-05-17 21:54 GMT+02:00 Richard Heck rgh...@lyx.org: Commit is causing compilation to fail here: I have reverted the refactoring. Does it compile now? Jürgen

Re: Understanding the /origin parameter

Le 18/05/2015 11:07, Enrico Forestieri a écrit : Sorry, I am not familiar about how things work on Mac. If you have an installer, you could replace those lines when they get installed but, again, I know nothing about Macs. The idea on Mac is to avoid having an installer, although it is

Re: about our lyx2lyx reversion policy

Le 14/05/2015 14:20, Uwe Stöhr a écrit : Current policy: - Assume that you have LyX 2.2 and your collaborator has 2.1. You add a box with a 10 pt thick frame and export the document to the format of LyX 2.1. As result you will get some TeX code. To be able to collaborate you will have to live

Make RELEASE-NOTES accessible from GUI (#8616)

I have a patch ready for this issue (display the RELEASE-NOTES in the AboutLyX dialog). It needs two changes to the file itself, though: * It must be moved to lib/ * It should use (moderate) Wiki markdown (see attached example) Is this change OK? Jürgen RELEASE-NOTES Description: Binary data

Re: Make RELEASE-NOTES accessible from GUI (#8616)

Le 18/05/2015 11:35, Jürgen Spitzmüller a écrit : I have a patch ready for this issue (display the RELEASE-NOTES in the AboutLyX dialog). It needs two changes to the file itself, though: * It must be moved to lib/ * It should use (moderate) Wiki markdown (see attached example) Is this change

Re: Make RELEASE-NOTES accessible from GUI (#8616)

2015-05-18 11:58 GMT+02:00 Jean-Marc Lasgouttes: Did you consider the possibility to have a LyX file that we would just export to text? If it is possible, it would be the best solution IMO. I'd prefer to have it in the AboutLyX dialog. It'd be the place where I would look for such

Re: [LyX/master] pdfcomment.module: uniform whitespace

Am Montag, 18. Mai 2015 um 12:16:19, schrieb Jürgen Spitzmüller sp...@lyx.org 2015-05-03 14:30 GMT+02:00 Jürgen Spitzmüller: 2015-04-30 19:35 GMT+02:00 Jürgen Spitzmüller: Further testing revealed that this is a change that needs careful testing. I have learned that readParToken also

Re: problem in arabic languge (menu)

On Sat, May 16, 2015 at 9:08 PM, hatim ali dr.ha...@hotmail.com wrote: after i opened lyx from terminal, when i change the interface language to arabic, i got this msg containt 100 line like this: Menus.cpp (729): Menu warning: menu entry لتيك (بسيط)... does not contain shortcut `L'.

Re: Make RELEASE-NOTES accessible from GUI (#8616)

Le 18/05/2015 12:04, Jürgen Spitzmüller a écrit : 2015-05-18 11:58 GMT+02:00 Jean-Marc Lasgouttes: Did you consider the possibility to have a LyX file that we would just export to text? If it is possible, it would be the best solution IMO. I'd prefer to have it in the AboutLyX

Re: [LyX/master] Fix up GuiBox (use proper data/view separation and clean up)

2015-05-18 12:51 GMT+02:00 Uwe Stöhr: since the count values change when you add a new item to the combo, whereas the value stays stable, no matter what you do with the combo. Note that the only .count() I used counts the fixed QList containing the possible combobox item. I also mean

Re: [LyX/master] pdfcomment.module: uniform whitespace

2015-05-03 14:30 GMT+02:00 Jürgen Spitzmüller: 2015-04-30 19:35 GMT+02:00 Jürgen Spitzmüller: Further testing revealed that this is a change that needs careful testing. I have learned that readParToken also uses getDocString() in order to read normal paragraph lines, and thus obviously must

Re: 2.2

Am 18.05.2015 um 11:34 schrieb Jean-Marc Lasgouttes lasgout...@lyx.org: Le 17/05/2015 18:36, Jürgen Spitzmüller a écrit : Note that it's mostly the German dictionaries that increase the size that much (they have seen some huge changes). The alternative would be to proceed with probably

Re: [LyX/master] Fix up GuiBox (use proper data/view separation and clean up)

On Sun, May 17, 2015 at 10:30 AM, Jürgen Spitzmüller sp...@lyx.org wrote: This is how collaboaratve coding works, Uwe. Observe how often my contributions are improved by others. This does not imply that I am a thir class coder (although I most certainly am), but it rather improves LyX's

Re: problem in the menu

Le 17/05/2015 04:55, hatim ali a écrit : when i change the interface language to Arabic language, i go this msg: Menus.cpp (729): Menu warning: menu entry لتيك (بسيط)... does not contain shortcut `L'. Menus.cpp (729): Menu warning: menu entry نص بسيط... does not contain shortcut `a'. Dear

Re: [LyX/master] GuiBox.cpp: assure that the parameters are not empty

Uwe StĂśhr wrote: > commit a5cc5dce3cf009d621685f01a885cfb0a02a50fb > Author: Uwe Stöhr > Date: Fri May 15 03:51:11 2015 +0200 > > GuiBox.cpp: assure that the parameters are not empty frontends/qt4/GuiBox.cpp: thicknessED->setText("0.4");

Re: Understanding the /origin parameter

Scott Kostyshak wrote: > When I am working on the documentation, any save now adds the following: > > +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ Do we really have to ship author/login used in the machine? I thought we have big fight already that we do not want to put such kind of

Re: Understanding the /origin parameter

On Sun, May 17, 2015 at 09:11:32PM -0400, Scott Kostyshak wrote: > When I am working on the documentation, any save now adds the following: > > +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ > > I just want to confirm that when I commit, it is correct that this > will be added to the

Re: Understanding the /origin parameter

Am 18.05.2015 um 08:54 schrieb Pavel Sanda : > Scott Kostyshak wrote: >> When I am working on the documentation, any save now adds the following: >> >> +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ > > Do we really have to ship author/login used in the machine? > I

Re: Understanding the /origin parameter

On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: > Scott Kostyshak wrote: > > When I am working on the documentation, any save now adds the following: > > > > +\origin /home/scott/lyxbuilds/master/repo/lib/templates/ > > Do we really have to ship author/login used in the machine? > I

Re: Understanding the /origin parameter

Le 18/05/2015 09:17, Enrico Forestieri a écrit : Do we really have to ship author/login used in the machine? I thought we have big fight already that we do not want to put such kind of things without explicit permission on the user side. There will not be any author/login used in the machine.

Re: Understanding the /origin parameter

Am 18.05.2015 um 09:17 schrieb Enrico Forestieri : > On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: >> Scott Kostyshak wrote: >>> When I am working on the documentation, any save now adds the following: >>> >>> +\origin

Re: Understanding the /origin parameter

Am 18.05.2015 um 10:09 schrieb Stephan Witt : > Am 18.05.2015 um 09:17 schrieb Enrico Forestieri : > >> On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: >>> Scott Kostyshak wrote: When I am working on the documentation, any save now adds the

Re: [LyX/master] Correctly load documents moved elsewhere after save.

Le 16/05/2015 19:52, Enrico Forestieri a écrit : commit 62d36bf04d436c83ddace8aeaf4dbd493d674cdf Author: Enrico Forestieri Date: Sat May 16 19:51:53 2015 +0200 Correctly load documents moved elsewhere after save. Now clang complains because of the new

Re: Understanding the /origin parameter

On Mon, May 18, 2015 at 09:50:00AM +0200, Jean-Marc Lasgouttes wrote: > Le 18/05/2015 09:17, Enrico Forestieri a écrit : > >>Do we really have to ship author/login used in the machine? > >>I thought we have big fight already that we do not want to put > >>such kind of things without explicit

Re: Understanding the /origin parameter

On Mon, May 18, 2015 at 10:09:42AM +0200, Stephan Witt wrote: > Am 18.05.2015 um 09:17 schrieb Enrico Forestieri : > > > On Sun, May 17, 2015 at 11:54:41PM -0700, Pavel Sanda wrote: > >> Scott Kostyshak wrote: > >>> When I am working on the documentation, any save now adds the

Re: Understanding the /origin parameter

Le 18/05/2015 11:02, Enrico Forestieri a écrit : Yes, but user files will contain this information... Isn't there a way to avoid it at least when it is not useful? The user files already contain this information when storing absolute paths. If I recall correctly, you strongly wanted absolute

Re: Compilation Failure

2015-05-17 21:54 GMT+02:00 Richard Heck : > > Commit is causing compilation to fail here: > I have reverted the refactoring. Does it compile now? Jürgen

Re: Understanding the /origin parameter

On Mon, May 18, 2015 at 11:09:25AM +0200, Jean-Marc Lasgouttes wrote: > Le 18/05/2015 11:02, Enrico Forestieri a écrit : > >>Yes, but user files will contain this information... Isn't there a way to > >>avoid it at least when it is not useful? > > > >The user files already contain this information

Re: Understanding the /origin parameter

Le 18/05/2015 11:07, Enrico Forestieri a écrit : Sorry, I am not familiar about how things work on Mac. If you have an installer, you could replace those lines when they get installed but, again, I know nothing about Macs. The idea on Mac is to avoid having an installer, although it is

Re: about our lyx2lyx reversion policy

Le 14/05/2015 14:20, Uwe Stöhr a écrit : Current policy: - Assume that you have LyX 2.2 and your collaborator has 2.1. You add a box with a 10 pt thick frame and export the document to the format of LyX 2.1. As result you will get some TeX code. To be able to collaborate you will have to live

Re: 2.2

Le 17/05/2015 18:36, Jürgen Spitzmüller a écrit : Note that it's mostly the German dictionaries that increase the size that much (they have seen some huge changes). The alternative would be to proceed with probably pretty outdated German support. A long-term solution would make it possible to

Make RELEASE-NOTES accessible from GUI (#8616)

I have a patch ready for this issue (display the RELEASE-NOTES in the AboutLyX dialog). It needs two changes to the file itself, though: * It must be moved to lib/ * It should use (moderate) Wiki markdown (see attached example) Is this change OK? Jürgen RELEASE-NOTES Description: Binary data

Re: Make RELEASE-NOTES accessible from GUI (#8616)

Le 18/05/2015 11:35, Jürgen Spitzmüller a écrit : I have a patch ready for this issue (display the RELEASE-NOTES in the AboutLyX dialog). It needs two changes to the file itself, though: * It must be moved to lib/ * It should use (moderate) Wiki markdown (see attached example) Is this change

Re: Make RELEASE-NOTES accessible from GUI (#8616)

2015-05-18 11:58 GMT+02:00 Jean-Marc Lasgouttes: > Did you consider the possibility to have a LyX file that we would just > export to text? If it is possible, it would be the best solution IMO. > I'd prefer to have it in the AboutLyX dialog. It'd be the place where I would look for such

Re: [LyX/master] pdfcomment.module: uniform whitespace

2015-05-03 14:30 GMT+02:00 Jürgen Spitzmüller: > 2015-04-30 19:35 GMT+02:00 Jürgen Spitzmüller: > >> Further testing revealed that this is a change that needs careful >> testing. I have learned that readParToken also uses getDocString() in order >> to read normal paragraph lines, and thus

Re: [LyX/master] pdfcomment.module: uniform whitespace

Am Montag, 18. Mai 2015 um 12:16:19, schrieb Jürgen Spitzmüller > 2015-05-03 14:30 GMT+02:00 Jürgen Spitzmüller: > > > 2015-04-30 19:35 GMT+02:00 Jürgen Spitzmüller: > > > >> Further testing revealed that this is a change that needs careful > >> testing. I have learned that

Re: 2.2

Am 18.05.2015 um 11:34 schrieb Jean-Marc Lasgouttes : > Le 17/05/2015 18:36, Jürgen Spitzmüller a écrit : >> Note that it's mostly the German dictionaries that increase the size >> that much (they have seen some huge changes). >> >> The alternative would be to proceed with

Re: problem in arabic languge (menu)

On Sat, May 16, 2015 at 9:08 PM, hatim ali wrote: > after i opened lyx from terminal, when i change the interface language to > arabic, i got this msg containt 100 line like this: > > > > Menus.cpp (729): Menu warning: menu entry "لتيك (بسيط)..." does not > contain shortcut

Re: Make RELEASE-NOTES accessible from GUI (#8616)

Le 18/05/2015 12:04, Jürgen Spitzmüller a écrit : 2015-05-18 11:58 GMT+02:00 Jean-Marc Lasgouttes: Did you consider the possibility to have a LyX file that we would just export to text? If it is possible, it would be the best solution IMO. I'd prefer to have it in the AboutLyX

Re: [LyX/master] Fix up GuiBox (use proper data/view separation and clean up)

On Sun, May 17, 2015 at 10:30 AM, Jürgen Spitzmüller wrote: > > This is how collaboaratve coding works, Uwe. Observe how often my > contributions are improved by others. This does not imply that I am a thir > class coder (although I most certainly am), but it rather improves

Re: problem in the menu

Le 17/05/2015 04:55, hatim ali a écrit : when i change the interface language to Arabic language, i go this msg: Menus.cpp (729): Menu warning: menu entry "لتيك (بسيط)..." does not contain shortcut `L'. Menus.cpp (729): Menu warning: menu entry "نص بسيط..." does not contain shortcut `a'. Dear

Re: [LyX/master] Fix up GuiBox (use proper data/view separation and clean up)

2015-05-18 12:51 GMT+02:00 Uwe Stöhr: > > > since the count values change when you add a new item to the combo, >> whereas the value stays stable, no matter what you do with the combo. >> > > Note that the only .count() I used counts the fixed QList containing the > possible combobox item. > I

Re: Make RELEASE-NOTES accessible from GUI (#8616)

On Mon, May 18, 2015 at 12:49 PM, Jean-Marc Lasgouttes wrote: > Le 18/05/2015 12:04, Jürgen Spitzmüller a écrit : >> >> 2015-05-18 11:58 GMT+02:00 Jean-Marc Lasgouttes: >> >> Did you consider the possibility to have a LyX file that we would >> just export to text? If

Re: 2.2

Am 16.05.2015 um 00:37 schrieb Enrico Forestieri : > On Fri, May 15, 2015 at 04:58:24PM +0200, Stephan Witt wrote: > >> Am 15.05.2015 um 16:48 schrieb Enrico Forestieri : >> >>> On Fri, May 15, 2015 at 04:31:05PM +0200, Stephan Witt wrote: This results

Re: 2.2

Le 18/05/2015 17:06, Stephan Witt a écrit : I'm unsure - with the previous code returning a pixmap missing pixmaps are ignored silently. With the change proposed by Enrico it is easy to add a error or warning message. The price is the change of many files containing a call to the getPixmap()

Compilation error with gcc 4.6

Since this week-end, I have compilation errors with gcc 4.6. I am not sure from where to start to diagnose this. JMarc In file included from /usr/include/c++/4.6/bits/concept_check.h:55:0, from /usr/include/c++/4.6/bits/move.h:34, from

Re: Compilation error with gcc 4.6

On 05/18/2015 12:17 PM, Jean-Marc Lasgouttes wrote: Since this week-end, I have compilation errors with gcc 4.6. I am not sure from where to start to diagnose this. This is the same error I reported earlier https://www.mail-archive.com/lyx-devel@lists.lyx.org/msg187530.html with gcc 4.9. I

Re: Compilation error with gcc 4.6

2015-05-18 19:24 GMT+02:00 Richard Heck: > On 05/18/2015 12:17 PM, Jean-Marc Lasgouttes wrote: > >> >> Since this week-end, I have compilation errors with gcc 4.6. I am not >> sure from where to start to diagnose this. >> > > This is the same error I reported earlier >

Re: Understanding the /origin parameter

On 05/18/2015 05:09 AM, Jean-Marc Lasgouttes wrote: Le 18/05/2015 11:02, Enrico Forestieri a écrit : Yes, but user files will contain this information... Isn't there a way to avoid it at least when it is not useful? The user files already contain this information when storing absolute paths.

Re: Compilation error with gcc 4.6

2015-05-18 19:29 GMT+02:00 Jürgen Spitzmüller : > 2015-05-18 19:24 GMT+02:00 Richard Heck: > >> On 05/18/2015 12:17 PM, Jean-Marc Lasgouttes wrote: >> >>> >>> Since this week-end, I have compilation errors with gcc 4.6. I am not >>> sure from where to start to diagnose this. >>> >>

Re: Understanding the /origin parameter

On Mon, May 18, 2015 at 11:14:19AM +0200, Jean-Marc Lasgouttes wrote: > Le 18/05/2015 11:07, Enrico Forestieri a écrit : > > >Anyway, I am ready to revert everything if this is wanted. > > I do not know whether reverting everything is what is needed. I do not feel > very at ease with a solution

Re: [patch] support for \fcolorbox and \colorbox

Am Sonntag, 17. Mai 2015 um 14:35:57, schrieb Georg Baum > Uwe Stöhr wrote: > > > Am 16.05.2015 um 11:17 schrieb Georg Baum: > > > >> tex2lyx produces broken documents now. Running the tests gives lots of > >> > >> Lexer.cpp (936): Missing 'framecolor'-tag in

Re: 2.2

Jean-Marc Lasgouttes schreef op 13-5-2015 om 10:42: Hi there, The ritual question: what is still needed for 2.2? I guess we are still waiting for some python 3.3 goodness from José, but what else? It seems to me that publishing a beta version soon is very desirable. Consider that for 2.1

Re: boost update?

Georg Baum schreef op 16-5-2015 om 10:19: Hi, I tested LyX with boost 1.58, and it compiles and runs fine. Shall I update the included boost? This would get rid of some compiler warnings, and since 2.2 will live for a while I guess it is good to start with a recent boost, since a boost update

Re: Make RELEASE-NOTES accessible from GUI (#8616)

Jean-Marc Lasgouttes wrote: > Le 18/05/2015 12:04, Jürgen Spitzmüller a écrit : >> If you prefer this approach, go ahead. > > I don't know, what do other people think? As I filed the bug I am very glad that it is being worked on, and I don't need to do it myself;-) Concerning the format and

Re: Make RELEASE-NOTES accessible from GUI (#8616)

Le 18/05/15 22:08, Georg Baum a écrit : Concerning the format and location I cannot really make up my mind. The argument in favour of LyX format is that we produce a document processor, and therefore it is natural to use it also for this kind of text. However, I agree with Jürgen that the About

Re: 2.2

Am 18.05.2015 um 18:11 schrieb Jean-Marc Lasgouttes : > Le 18/05/2015 17:06, Stephan Witt a écrit : >> I'm unsure - with the previous code returning a pixmap missing pixmaps are >> ignored silently. >> With the change proposed by Enrico it is easy to add a error or warning

Re: [LyX/master] tex2lyx/text.cpp: support for the commands \fboxsep etc.

Uwe Stöhr wrote: > diff --git a/src/tex2lyx/test/box-color-size-space-align.tex > b/src/tex2lyx/test/box-color-size-space-align.tex index ab658c6..b004eed > 100644 --- a/src/tex2lyx/test/box-color-size-space-align.tex > +++ b/src/tex2lyx/test/box-color-size-space-align.tex > @@ -157,6 +157,18 @@

Re: boost update?

Vincent van Ravesteijn wrote: > Last time I tried (not so long ago), I hit a lot of new compiler errors, > which I didn't know how to fix. > > Thank you for fixing those.. It was easy, it was only one: b596330093d. Maybe our code has some self- healing capabilities:-) Georg

Re: boost update?

Op 18 mei 2015 22:20 schreef "Georg Baum" : > > Vincent van Ravesteijn wrote: > > > Last time I tried (not so long ago), I hit a lot of new compiler errors, > > which I didn't know how to fix. > > > > Thank you for fixing those.. > > It was easy, it was only one:

Re: 2.2

Am 18.05.2015 um 22:13 schrieb Stephan Witt : > Am 18.05.2015 um 18:11 schrieb Jean-Marc Lasgouttes : > >> Le 18/05/2015 17:06, Stephan Witt a écrit : >>> I'm unsure - with the previous code returning a pixmap missing pixmaps are >>> ignored silently. >>>

Re: boost update?

Le 18 mai 2015 22:24:54 CEST, Vincent van Ravesteijn a écrit : >Op 18 mei 2015 22:20 schreef "Georg Baum" >: >> >> Vincent van Ravesteijn wrote: >> >I remember losing my way in many boost::next errors and >ununderstandable >paragraph iterators.

  1   2   >