Re: Language change within Flex inset exports wrong babel construct

Le 03/06/11 02:07, Enrico Forestieri a écrit : See attached patch. I am not sure I understand the patch, but how come one has to decide based on isMainText()? What about a Flex inset in a Note? What would the situation be different? JMarc

Re: r38939 - lyx-devel/branches/BRANCH_2_0_X/po

sa...@lyx.org wrote: Author: sanda Date: Fri Jun 3 10:16:49 2011 New Revision: 38939 URL: http://www.lyx.org/trac/changeset/38939 Log: * zh_CN.po backport Modified: lyx-devel/branches/BRANCH_2_0_X/po/zh_CN.po we have double entry in status file for ui updates. i would actually

Re: Language change within Flex inset exports wrong babel construct

Enrico Forestieri forenr at lyx.org writes: See attached patch. Tested with trunk, as it belongs to it, and it solves the problem both in Customization.lyx and in my simple test example. I created a ticket http://www.lyx.org/trac/ticket/7607 -- Jean-Pierre

Re: r38939 - lyx-devel/branches/BRANCH_2_0_X/po

Pavel Sanda wrote: we have double entry in status file for ui updates. i would actually prefer the new one added by Richard. But it belongs to Updates, not Bug fixes, IMHO. Jürgen

Re: Language change within Flex inset exports wrong babel construct

Jean-Marc Lasgouttes wrote: See attached patch. I am not sure I understand the patch, but how come one has to decide based on isMainText()? What about a Flex inset in a Note? What would the situation be different? I am not sure either. I often face such problems for environments

Re: r38939 - lyx-devel/branches/BRANCH_2_0_X/po

Jürgen Spitzmüller wrote: Pavel Sanda wrote: we have double entry in status file for ui updates. i would actually prefer the new one added by Richard. But it belongs to Updates, not Bug fixes, IMHO. yes. pavel

Re: Language change within Flex inset exports wrong babel construct

On Fri, Jun 03, 2011 at 09:47:35AM +0200, Jean-Marc Lasgouttes wrote: Le 03/06/11 02:07, Enrico Forestieri a écrit : See attached patch. I am not sure I understand the patch, but how come one has to decide based on isMainText()? What about a Flex inset in a Note? What would the situation

Re: Language change within Flex inset exports wrong babel construct

Le 03/06/11 14:26, Enrico Forestieri a écrit : As \selectlanguage introduces spurious white space, it should not be used in inline content. As \selectlanguage is only used when the language is changed at the very beginning of a LyX paragraph, checking isMainText() ensures that it is used only at

Re: Language change within Flex inset exports wrong babel construct

On Fri, Jun 03, 2011 at 02:32:16PM +0200, Jean-Marc Lasgouttes wrote: Le 03/06/11 14:26, Enrico Forestieri a écrit : As \selectlanguage introduces spurious white space, it should not be used in inline content. As \selectlanguage is only used when the language is changed at the very beginning

Re: Bug in configure.py

On 03/06/2011 9:31 AM, Michal wrote: On Wed, 1 Jun 2011 19:49:47 +0200 Enrico Forestierifor...@lyx.org wrote: [...] The point is that if the TeX engine does not support spaces in filenames the check is going to fail. Now, recent MikTeX versions support spaces in filenames, but old ones do

Re: Bug in configure.py

On Fri, 03 Jun 2011 13:02:25 -0400 Julien Rioux jri...@physics.utoronto.ca wrote: [...] I didn't follow the thread but I am just wondering about your suggested user hint. Do you suggest that such a message should appear in a popup window when configure.py fails, or that it should appear as

Re: Bug in configure.py

On 03/06/2011 2:11 PM, Michal wrote: On Fri, 03 Jun 2011 13:02:25 -0400 Julien Riouxjri...@physics.utoronto.ca wrote: [...] I didn't follow the thread but I am just wondering about your suggested user hint. Do you suggest that such a message should appear in a popup window when configure.py

Patches for Case environment

Hi all, There's a (minor?) bug in the Case environment as coded in four include files (theorems.inc, theorems-ams.inc, theorems-bytype.inc and theorems-ams-bytype.inc). The problem occurs when a case environment is nested inside another case environment: since only one counter for cases is

Re: Adv FR Issue on Mac Win.

Il 29/05/2011 12:11, Enrico Forestieri ha scritto: On Fri, May 27, 2011 at 08:26:21PM -0400, BH wrote: I've tried searching for \alpha and x^2 in both files provided with the bug report, and I cannot reproduce the bug with trunk r38856 or r38870. That's on MacOSX 10.6.7. Am I missing anything?

Re: first step of merging the Win installers

Am 23.05.2011 12:18, schrieb Edwin Leuven: when i use your installer it gets stuck at the checking stage. i killed it after 30mins. I'll have a closer look soon. thanks and regards Uwe

Re: first step of merging the Win installers

Am 23.05.2011 20:34, schrieb Joost Verburg: - you installed LyX's sty-files always to MiKTeX's user folder. But when LyX is installed for all users, we need to install them to MiKTeX's main folder to be available for all users What if the user is not the administrator and only installs

Re: Language change within Flex inset exports wrong babel construct

Le 03/06/11 02:07, Enrico Forestieri a écrit : See attached patch. I am not sure I understand the patch, but how come one has to decide based on isMainText()? What about a Flex inset in a Note? What would the situation be different? JMarc

Re: r38939 - lyx-devel/branches/BRANCH_2_0_X/po

sa...@lyx.org wrote: > Author: sanda > Date: Fri Jun 3 10:16:49 2011 > New Revision: 38939 > URL: http://www.lyx.org/trac/changeset/38939 > > Log: > * zh_CN.po backport > > Modified: >lyx-devel/branches/BRANCH_2_0_X/po/zh_CN.po we have double entry in status file for ui updates. i would

Re: Language change within Flex inset exports wrong babel construct

Enrico Forestieri lyx.org> writes: > > See attached patch. > Tested with trunk, as it belongs to it, and it solves the problem both in Customization.lyx and in my simple test example. I created a ticket http://www.lyx.org/trac/ticket/7607 -- Jean-Pierre

Re: r38939 - lyx-devel/branches/BRANCH_2_0_X/po

Pavel Sanda wrote: > we have double entry in status file for ui updates. > i would actually prefer the new one added by Richard. But it belongs to "Updates", not "Bug fixes", IMHO. Jürgen

Re: Language change within Flex inset exports wrong babel construct

Jean-Marc Lasgouttes wrote: > > See attached patch. > > I am not sure I understand the patch, but how come one has to decide > based on isMainText()? What about a Flex inset in a Note? What would the > situation be different? I am not sure either. I often face such problems for environments

Re: r38939 - lyx-devel/branches/BRANCH_2_0_X/po

Jürgen Spitzmüller wrote: > Pavel Sanda wrote: > > we have double entry in status file for ui updates. > > i would actually prefer the new one added by Richard. > > But it belongs to "Updates", not "Bug fixes", IMHO. yes. pavel

Re: Language change within Flex inset exports wrong babel construct

On Fri, Jun 03, 2011 at 09:47:35AM +0200, Jean-Marc Lasgouttes wrote: > Le 03/06/11 02:07, Enrico Forestieri a écrit : > >See attached patch. > > I am not sure I understand the patch, but how come one has to decide > based on isMainText()? What about a Flex inset in a Note? What would > the

Re: Language change within Flex inset exports wrong babel construct

Le 03/06/11 14:26, Enrico Forestieri a écrit : As \selectlanguage introduces spurious white space, it should not be used in "inline" content. As \selectlanguage is only used when the language is changed at the very beginning of a LyX paragraph, checking isMainText() ensures that it is used only

Re: Language change within Flex inset exports wrong babel construct

On Fri, Jun 03, 2011 at 02:32:16PM +0200, Jean-Marc Lasgouttes wrote: > Le 03/06/11 14:26, Enrico Forestieri a écrit : > >As \selectlanguage introduces spurious white space, it should not be used > >in "inline" content. As \selectlanguage is only used when the language is > >changed at the very

Re: Bug in configure.py

On 03/06/2011 9:31 AM, Michal wrote: On Wed, 1 Jun 2011 19:49:47 +0200 Enrico Forestieri wrote: [...] The point is that if the TeX engine does not support spaces in filenames the check is going to fail. Now, recent MikTeX versions support spaces in filenames, but old ones do

Re: Bug in configure.py

On Fri, 03 Jun 2011 13:02:25 -0400 Julien Rioux wrote: > [...] > I didn't follow the thread but I am just wondering about your > suggested user hint. Do you suggest that such a message should appear > in a popup window when configure.py fails, or that it should

Re: Bug in configure.py

On 03/06/2011 2:11 PM, Michal wrote: On Fri, 03 Jun 2011 13:02:25 -0400 Julien Rioux wrote: [...] I didn't follow the thread but I am just wondering about your suggested user hint. Do you suggest that such a message should appear in a popup window when

Patches for Case environment

Hi all, There's a (minor?) bug in the Case environment as coded in four include files (theorems.inc, theorems-ams.inc, theorems-bytype.inc and theorems-ams-bytype.inc). The problem occurs when a case environment is nested inside another case environment: since only one counter for cases is

Re: Adv F Issue on Mac & Win.

Il 29/05/2011 12:11, Enrico Forestieri ha scritto: On Fri, May 27, 2011 at 08:26:21PM -0400, BH wrote: I've tried searching for \alpha and x^2 in both files provided with the bug report, and I cannot reproduce the bug with trunk r38856 or r38870. That's on MacOSX 10.6.7. Am I missing anything?

Re: first step of merging the Win installers

Am 23.05.2011 12:18, schrieb Edwin Leuven: when i use your installer it gets stuck at the checking stage. i killed it after 30mins. I'll have a closer look soon. thanks and regards Uwe

Re: first step of merging the Win installers

Am 23.05.2011 20:34, schrieb Joost Verburg: >- you installed LyX's sty-files always to MiKTeX's user folder. But when LyX is installed for all users, we need to install them to MiKTeX's main folder to be available for all users What if the user is not the administrator and only