Re: Wiki password
Joost Verburg wrote: Could someone send me the password for editing protected pages on the wiki? Done. Jürgen
Re: No Mouse scrolling in LyX 2.0 - Mac?
Jean-Marc LASGOUTTES wrote: Jean-Marc LASGOUTTES wrote: Really cool! It works with one small correction: the convert() function cannot handle the double value. I changed the patch accordingly and attach it again. Very good. I applied it. Am I right that this is needed in 1.6.x too? Seems so. OK, I saw the message on lyx-users and applied the fix to branch. The message I referred to turned out to be a misunderstanding (the user used trunk and thought it was branch). Nevertheless, the commit seems appropriate. Jürgen
Re: No Mouse scrolling in LyX 2.0 - Mac?
Jürgen Spitzmüller sp...@lyx.org writes: Jean-Marc LASGOUTTES wrote: Really cool! It works with one small correction: the convert() function cannot handle the double value. I changed the patch accordingly and attach it again. Very good. I applied it. Am I right that this is needed in 1.6.x too? Seems so. OK, I saw the message on lyx-users and applied the fix to branch. JMarc
Re: No Mouse scrolling in LyX 2.0 - Mac?
Jürgen Spitzmüller sp...@lyx.org writes: The message I referred to turned out to be a misunderstanding (the user used trunk and thought it was branch). Doh! Indeed. Nevertheless, the commit seems appropriate. I hope so. It _looks_ safe, but one never knows... JMarc
Re: No Mouse scrolling in LyX 2.0 - Mac?
Jean-Marc LASGOUTTES wrote: Nevertheless, the commit seems appropriate. I hope so. It looks safe, but one never knows... So everybody please test mouse scrolling in branch. (it still works here) Jürgen
Re: confusion of tongues
FYI these installers are now online. Jürgen I'm using the alternate installer and I've also found, that the UI language option is ignored. This installer has not been updated yet. However, I've found that the following batch file (inside 'bin' directory) gives me an English UI: set LANG=en_EN LyxLauncher.exe %* Regards, Michał Skrzypek
platex as the default latex command?
Hi, First of all, I'd like to mention I'm no Lyx user (just never got to test it), but a maintainer of TeX Live. Recently, we got an report [1] from a Lyx user that some of his documents stopped working after upgrading from TeX Live 2009 to 2010-pretest. [1] http://tug.org/pipermail/tex-live/2010-July/026815.html The report (and further discussion) isn't very clear, but the problem seems to be that platex is used to typeset the document, while the user apparently didn't ask for it. It would explain why the same document worked with TL 2009: platex wasn't provided, so Lyx didn't try to use it. Out of curiosity, I installed Lyx (1.6.7) on my box. In ~/.lyx/lyxrc.defaults, I see the following line: \converter latex dviplatex latex so I'm under the impression that platex is indeed the default command for the latex format. The problem is, platex isn't a drop-in replacement for the classic latex command at all. For example, pTeX doesn't have e-TeX extensions (which explains the original problem with Koma-script) provided by pdfTeX (used by the latex command) and expected by and increasing number of packages and classes. So, I'd like to strongly suggest you switch back to using the latex command (ie pdftex engine) as a default even if platex is available, and use platex only when specifically needed. Otherwise, there may be a lot of problems like the above when people migrate to TeX Live 2010 which provides platex. If I misunderstood something and platex isn't currently the default when available, then keep it this way and please accept my apologies for the noise. Thanks, Manuel. PS: I didn't subscribe to the list, so please keep me cc-ed if you need more details or otherwise want me to follow the discussion.
Re: platex as the default latex command?
Manuel Pégourié-Gonnard wrote: First of all, I'd like to mention I'm no Lyx user (just never got to test it), but a maintainer of TeX Live. Recently, we got an report [1] from a Lyx user that some of his documents stopped working after upgrading from TeX Live 2009 to 2010-pretest. [1] http://tug.org/pipermail/tex-live/2010-July/026815.html Yes, I can confirm this behaviour with TL 2010. And yes, this is of course a bug. LyX should only use platex for Japanese documents. The reason is to be found around line 215 of configure.py. Jürgen
Re: platex as the default latex command?
Jürgen Spitzmüller wrote: First of all, I'd like to mention I'm no Lyx user (just never got to test it), but a maintainer of TeX Live. Recently, we got an report [1] from a Lyx user that some of his documents stopped working after upgrading from TeX Live 2009 to 2010-pretest. [1] http://tug.org/pipermail/tex-live/2010-July/026815.html Yes, I can confirm this behaviour with TL 2010. And yes, this is of course a bug. LyX should only use platex for Japanese documents. The reason is to be found around line 215 of configure.py. The attached patch strikes me like the correct fix. Koji, does Japanese still work with this? Jürgen Index: lib/configure.py === --- lib/configure.py (Revision 35038) +++ lib/configure.py (Arbeitskopie) @@ -198,7 +198,7 @@ def checkLatex(dtl_tools): ''' Check latex, return lyx_check_config ''' -path, LATEX = checkProg('a Latex2e program', ['latex $$i', 'platex $$i', 'latex2e $$i']) +path, LATEX = checkProg('a Latex2e program', ['latex $$i', 'latex2e $$i']) path, PPLATEX = checkProg('a DVI postprocessing program', ['pplatex $$i']) #- path, PLATEX = checkProg('pLaTeX, the Japanese LaTeX', ['platex $$i']) @@ -212,7 +212,6 @@ if cmdOutput(PLATEX + ' chklatex.ltx').find('pLaTeX2e') != -1: # We have the Japanese pLaTeX2e addToRC(r'\converter platex dvi %s latex' % PLATEX) -LATEX = PLATEX else: PLATEX = '' removeFiles(['chklatex.ltx', 'chklatex.log'])
Re: platex as the default latex command?
Jürgen Spitzmüller sp...@lyx.org writes: Jürgen Spitzmüller wrote: First of all, I'd like to mention I'm no Lyx user (just never got to test it), but a maintainer of TeX Live. Recently, we got an report [1] from a Lyx user that some of his documents stopped working after upgrading from TeX Live 2009 to 2010-pretest. [1] http://tug.org/pipermail/tex-live/2010-July/026815.html Yes, I can confirm this behaviour with TL 2010. And yes, this is of course a bug. LyX should only use platex for Japanese documents. The reason is to be found around line 215 of configure.py. The attached patch strikes me like the correct fix. -path, LATEX = checkProg('a Latex2e program', ['latex $$i', 'platex $$i', 'latex2e $$i']) +path, LATEX = checkProg('a Latex2e program', ['latex $$i', 'latex2e $$i']) Does this mean that 'latex' is not found with texlive 2010? JMarc
Re: Improvements to Lyx user interface
On 29. juli 2010 20:58, Alberto Malagoli wrote: Hi all, I'd like to share with you some ideas about Lyx user interface, and how can be improved... I made a presentation with the explanation of my thoughts, you can find it here: https://docs.google.com/present/view?id=dckbsjn9_41f57jwcdh I also attached the user interface files I made with Qt Designer, so you can see it and try it in real time :) Let me know what do you think about, and don't hesitate with criticism! As you say yourself - dock widgets waste a lot of space. That is a problem. My work PC has a big screen and an extra monitor. But my travel PC has a tiny 8 screen. Current LyX is fine with that, but I have no room for any extra toolbars. And definitely not something docked on the side. It is nice having a LyX that works well on small screens. And of course, on big screen computers I don't wan't LyX to take up all the room either. It is nice having room for a web browser or an extra LyX, without overlap. Helge Hafting
Re: platex as the default latex command?
Jean-Marc LASGOUTTES wrote: The attached patch strikes me like the correct fix. -path, LATEX = checkProg('a Latex2e program', ['latex $$i', 'platex $$i', 'latex2e $$i']) +path, LATEX = checkProg('a Latex2e program', ['latex $$i', 'latex2e $$i']) Does this mean that 'latex' is not found with texlive 2010? No. latex is found and ascribed to the LATEX variable. But later (line 215), is is replaced by platex (given that platex was found): if cmdOutput(PLATEX + ' chklatex.ltx').find('pLaTeX2e') != -1: # We have the Japanese pLaTeX2e addToRC(r'\converter platex dvi %s latex' % PLATEX) LATEX = PLATEX I suppose this is a remainder of the time when we did not yet separate platex from latex (and supposed that if platex is installed, it should be used). Jürgen
Re: r35040 - lyx-devel/trunk/src/frontends/qt4
spitz wrote: Author: spitz Date: Mon Aug 2 18:38:41 2010 New Revision: 35040 URL: http://www.lyx.org/trac/changeset/35040 Log: * GuiLog.cpp: refine warning detection: - detect LaTeX Font Warning - detect Class X Warning - package warnings can contain dots (Package pdftex.def Warning) I intend to backport this to branch if there are no objections. Jürgen
Re: r35040 - lyx-devel/trunk/src/frontends/qt4
Log: * GuiLog.cpp: refine warning detection: - detect LaTeX Font Warning - detect Class X Warning - package warnings can contain dots (Package pdftex.def Warning) -QRegExp exprWarning(^(LaTeX Warning|Package \\w+ Warning).*$); +QRegExp exprWarning(^(LaTeX Warning|LaTeX Font Warning|Package [\\w \\.]+ Warning|Class \\w+ Warning).*$); Why not factor Warning out of the parenthesis? JMarc
Re: platex as the default latex command?
Le 2 août 10 à 17:58, Jürgen Spitzmüller a écrit : No. latex is found and ascribed to the LATEX variable. But later (line 215), is is replaced by platex (given that platex was found): if cmdOutput(PLATEX + ' chklatex.ltx').find('pLaTeX2e') != -1: # We have the Japanese pLaTeX2e addToRC(r'\converter platex dvi %s latex' % PLATEX) LATEX = PLATEX I suppose this is a remainder of the time when we did not yet separate platex from latex (and supposed that if platex is installed, it should be used). OK, then your patch seems fine. JMarc
Re: r35040 - lyx-devel/trunk/src/frontends/qt4
Jean-Marc Lasgouttes wrote: -QRegExp exprWarning(^(LaTeX Warning|Package \\w+ Warning).*$); +QRegExp exprWarning(^(LaTeX Warning|LaTeX Font Warning|Package [\\w \\.]+ Warning|Class \\w+ Warning).*$); Why not factor Warning out of the parenthesis? You mean QRegExp exprWarning(^(LaTeX|LaTeX Font|Package [\\w\\.]+|Class \\w+) Warning.*$); ? (sorry, I'm not so good at regexing). Jürgen
Re: Beta plans (again)
Am 02.08.2010 um 01:55 schrieb Jean-Marc Lasgouttes: Le 26 juil. 10 à 14:30, Stephan Witt a écrit : My next target (for beta phase?) would be to check the installation issues on mac to make the application working out-of-the-box. What about removing the complicated mac-specific code in aspell now that it is not needed anymore? I'm a little bit sorrowful that the native spell checker is not fast enough for continuously checking when doing it word-wise. So we are not ready to switch off aspell :( Currently I have no time to improve the situation. You're back in Paris? Yesterday evening I crossed the Rue de Clignancourt :-) Tomorrow I'll leave Paris and go to Orleans. Stephan
Re: r35040 - lyx-devel/trunk/src/frontends/qt4
Le 2 août 10 à 19:29, Jürgen Spitzmüller a écrit : Why not factor Warning out of the parenthesis? You mean QRegExp exprWarning(^(LaTeX|LaTeX Font|Package [\\w\\.]+|Class \\w+) Warning.*$); ? (sorry, I'm not so good at regexing). Yes, but if you find the first solution more readable, you can keep it... (now that I see it, I am not sure that it is much of a gain) JMarc
Re: Beta plans (again)
Le 2 août 10 à 20:57, Stephan Witt a écrit : I'm a little bit sorrowful that the native spell checker is not fast enough for continuously checking when doing it word-wise. So we are not ready to switch off aspell :( Currently I have no time to improve the situation. I think I hqve some. I'll see what I can do. You're back in Paris? Yesterday evening I crossed the Rue de Clignancourt :-) Tomorrow I'll leave Paris and go to Orleans. Too bad, I arrived yesterday evening and I am here until 13/08. JMarc
Re: [patch] revtex 4.1 support
On 01/08/2010 3:54 AM, Jürgen Spitzmüller wrote: Julien Rioux wrote: Here is a patch against latest trunk for a REVTeX 4.1 layout and template file. Could you briefly decribe the changes wrt ReVTeX 4, or are there too many? Jürgen The changes to the latex class are described here: [1]. On the layout side, changes include: - Use of categories - Added support for ruledtabular, subequations, turnpage, and widetext environments. - Support for video float, \setfloatlink, \lowercase and \surname commands (those are specific to 4.1). Revtex 4.1 was designed in conjunction with the developer of natbib and this lead to natbib 8.31 which also brings new features. These are at the moment unsupported by LyX: - multiple references in a single bibliography entry, e.g. \cite{ref1,*ref2} becomes [1] in text and in the reference list: [1] Author1, ref1 (year1); author2, ref2 (year2). - prepending/appending text to a bibliography entry, e.g. \cite{[, and references therein.]ref3} becomes: [2] Author3, ref3 (year3), and references therein. You can edit a LyX file to hack this sort of syntax into a citation inset, and it will work, but there is currently no UI. I didn't attempt to tackle this. -- Julien [1] https://authors.aps.org/revtex4/revtex4_faq.html#c1
Re: [patch] revtex 4.1 support
When I said edit a LyX file I meant with an external plain text editor. It confuses the LyX GUI a bit but compiles fine with the expected result. -- Julien
Re: No Mouse scrolling in LyX 2.0 - Mac?
Am 02.08.2010 um 12:41 schrieb Jürgen Spitzmüller: Jean-Marc LASGOUTTES wrote: Nevertheless, the commit seems appropriate. I hope so. It looks safe, but one never knows... So everybody please test mouse scrolling in branch. (it still works here) Works for me with scroll pad on mac. Stephan
Re: [patch] layout dependencies
On 2010-07-30, Julien Rioux wrote: This is a multi-part message in MIME format. --030503040800070104030405 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi LyX developers, LyX 2.0 now has a new mechanism for relaying layout dependencies to the user, such as the class filename. Most LaTeX classes also rely on certain packages to be installed. It could be argued that this information should be provided to LyX in the layout files. This patch address this. With these additions, it would be nice if the reported error for nonavailable dependencies would be changed from Not available: to Missing dependencies: ... Günter
Re: Beta plans (again)
Le 2 août 10 à 20:57, Stephan Witt a écrit : I'm a little bit sorrowful that the native spell checker is not fast enough for continuously checking when doing it word-wise. So we are not ready to switch off aspell :( Currently I have no time to improve the situation. I do not manage to get the native spellchecker to work. The situation is that I do not use the binary-release.sh script, but only the plain configure script. I found that I have to set MACOSX_DEPLOYMENT_TARGET and SDKROOT before running make. I plan to eventually move this to configure.ac (the idea is that plan configure should be enough in general, and the full script is for packagers) The situation I am in is that no language seems to be recognized. For example, in hasLanguageAppleSpeller, [speller-checker availableLanguages] returns an empty list. Do you have an idea about what could be the cause? I am on Leopard (10.5), BTW. JMarc PS: Gino: echo $MACOSX_DEPLOYMENT_TARGET 10.4 Gino: echo $SDKROOT /Developer/SDKs/MacOSX10.5.sdk
Re: Wiki password
Joost Verburg wrote: > Could someone send me the password for editing protected pages on the wiki? Done. Jürgen
Re: No Mouse scrolling in LyX 2.0 - Mac?
Jean-Marc LASGOUTTES wrote: > > Jean-Marc LASGOUTTES wrote: > >> > Really cool! It works with one small correction: the convert() > >> > function cannot handle the double value. I changed the patch > >> > accordingly and attach it again. > >> > >> > >> > >> Very good. I applied it. Am I right that this is needed in 1.6.x too? > > > > Seems so. > > OK, I saw the message on lyx-users and applied the fix to branch. The message I referred to turned out to be a misunderstanding (the user used trunk and thought it was branch). Nevertheless, the commit seems appropriate. Jürgen
Re: No Mouse scrolling in LyX 2.0 - Mac?
Jürgen Spitzmüllerwrites: > Jean-Marc LASGOUTTES wrote: >> > Really cool! It works with one small correction: the convert() function >> > cannot handle the double value. I changed the patch accordingly and >> > attach it again. >> >> Very good. I applied it. Am I right that this is needed in 1.6.x too? > > Seems so. OK, I saw the message on lyx-users and applied the fix to branch. JMarc
Re: No Mouse scrolling in LyX 2.0 - Mac?
Jürgen Spitzmüllerwrites: > The message I referred to turned out to be a misunderstanding (the user used > trunk and thought it was branch). Doh! Indeed. > Nevertheless, the commit seems appropriate. I hope so. It _looks_ safe, but one never knows... JMarc
Re: No Mouse scrolling in LyX 2.0 - Mac?
Jean-Marc LASGOUTTES wrote: > > Nevertheless, the commit seems appropriate. > > I hope so. It looks safe, but one never knows... So everybody please test mouse scrolling in branch. (it still works here) Jürgen
Re: confusion of tongues
> FYI these installers are now online. > > Jürgen I'm using the alternate installer and I've also found, that the UI language option is ignored. This installer has not been updated yet. However, I've found that the following batch file (inside 'bin' directory) gives me an English UI: set LANG=en_EN LyxLauncher.exe %* Regards, Michał Skrzypek
platex as the default latex command?
Hi, First of all, I'd like to mention I'm no Lyx user (just never got to test it), but a maintainer of TeX Live. Recently, we got an report [1] from a Lyx user that some of his documents stopped working after upgrading from TeX Live 2009 to 2010-pretest. [1] http://tug.org/pipermail/tex-live/2010-July/026815.html The report (and further discussion) isn't very clear, but the problem seems to be that platex is used to typeset the document, while the user apparently didn't ask for it. It would explain why the same document worked with TL 2009: platex wasn't provided, so Lyx didn't try to use it. Out of curiosity, I installed Lyx (1.6.7) on my box. In ~/.lyx/lyxrc.defaults, I see the following line: \converter latex dvi"platex" "latex" so I'm under the impression that platex is indeed the default command for the latex format. The problem is, platex isn't a drop-in replacement for the "classic" latex command at all. For example, pTeX doesn't have e-TeX extensions (which explains the original problem with Koma-script) provided by pdfTeX (used by the "latex" command) and expected by and increasing number of packages and classes. So, I'd like to strongly suggest you switch back to using the "latex" command (ie pdftex engine) as a default even if platex is available, and use platex only when specifically needed. Otherwise, there may be a lot of problems like the above when people migrate to TeX Live 2010 which provides platex. If I misunderstood something and platex isn't currently the default when available, then keep it this way and please accept my apologies for the noise. Thanks, Manuel. PS: I didn't subscribe to the list, so please keep me cc-ed if you need more details or otherwise want me to follow the discussion.
Re: platex as the default latex command?
Manuel Pégourié-Gonnard wrote: > First of all, I'd like to mention I'm no Lyx user (just never got to test > it), but a maintainer of TeX Live. Recently, we got an report [1] from a > Lyx user that some of his documents stopped working after upgrading from > TeX Live 2009 to 2010-pretest. > > [1] http://tug.org/pipermail/tex-live/2010-July/026815.html Yes, I can confirm this behaviour with TL 2010. And yes, this is of course a bug. LyX should only use platex for Japanese documents. The reason is to be found around line 215 of configure.py. Jürgen
Re: platex as the default latex command?
Jürgen Spitzmüller wrote: > > First of all, I'd like to mention I'm no Lyx user (just never got to test > > it), but a maintainer of TeX Live. Recently, we got an report [1] from a > > Lyx user that some of his documents stopped working after upgrading from > > TeX Live 2009 to 2010-pretest. > > > > > > > > [1] http://tug.org/pipermail/tex-live/2010-July/026815.html > > Yes, I can confirm this behaviour with TL 2010. And yes, this is of course > a bug. LyX should only use platex for Japanese documents. > > The reason is to be found around line 215 of configure.py. The attached patch strikes me like the correct fix. Koji, does Japanese still work with this? Jürgen Index: lib/configure.py === --- lib/configure.py (Revision 35038) +++ lib/configure.py (Arbeitskopie) @@ -198,7 +198,7 @@ def checkLatex(dtl_tools): ''' Check latex, return lyx_check_config ''' -path, LATEX = checkProg('a Latex2e program', ['latex $$i', 'platex $$i', 'latex2e $$i']) +path, LATEX = checkProg('a Latex2e program', ['latex $$i', 'latex2e $$i']) path, PPLATEX = checkProg('a DVI postprocessing program', ['pplatex $$i']) #- path, PLATEX = checkProg('pLaTeX, the Japanese LaTeX', ['platex $$i']) @@ -212,7 +212,6 @@ if cmdOutput(PLATEX + ' chklatex.ltx').find('pLaTeX2e') != -1: # We have the Japanese pLaTeX2e addToRC(r'\converter platex dvi "%s" "latex"' % PLATEX) -LATEX = PLATEX else: PLATEX = '' removeFiles(['chklatex.ltx', 'chklatex.log'])
Re: platex as the default latex command?
Jürgen Spitzmüllerwrites: > Jürgen Spitzmüller wrote: >> > First of all, I'd like to mention I'm no Lyx user (just never got to test >> > it), but a maintainer of TeX Live. Recently, we got an report [1] from a >> > Lyx user that some of his documents stopped working after upgrading from >> > TeX Live 2009 to 2010-pretest. >> > >> > >> > >> > [1] http://tug.org/pipermail/tex-live/2010-July/026815.html >> >> Yes, I can confirm this behaviour with TL 2010. And yes, this is of course >> a bug. LyX should only use platex for Japanese documents. >> >> The reason is to be found around line 215 of configure.py. > > The attached patch strikes me like the correct fix. > -path, LATEX = checkProg('a Latex2e program', ['latex $$i', 'platex $$i', > 'latex2e $$i']) > +path, LATEX = checkProg('a Latex2e program', ['latex $$i', 'latex2e > $$i']) Does this mean that 'latex' is not found with texlive 2010? JMarc
Re: Improvements to Lyx user interface
On 29. juli 2010 20:58, Alberto Malagoli wrote: Hi all, I'd like to share with you some ideas about Lyx user interface, and how can be improved... I made a presentation with the explanation of my thoughts, you can find it here: https://docs.google.com/present/view?id=dckbsjn9_41f57jwcdh I also attached the user interface files I made with Qt Designer, so you can see it and try it in real time :) Let me know what do you think about, and don't hesitate with criticism! As you say yourself - dock widgets waste a lot of space. That is a problem. My work PC has a big screen and an extra monitor. But my "travel PC" has a tiny 8" screen. Current LyX is fine with that, but I have no room for any extra toolbars. And definitely not something docked on the side. It is nice having a LyX that works well on small screens. And of course, on big screen computers I don't wan't LyX to take up all the room either. It is nice having room for a web browser or an extra LyX, without overlap. Helge Hafting
Re: platex as the default latex command?
Jean-Marc LASGOUTTES wrote: > > The attached patch strikes me like the correct fix. > > -path, LATEX = checkProg('a Latex2e program', ['latex $$i', 'platex > > $$i', 'latex2e $$i']) +path, LATEX = checkProg('a Latex2e program', > > ['latex $$i', 'latex2e $$i']) > > Does this mean that 'latex' is not found with texlive 2010? No. "latex" is found and ascribed to the LATEX variable. But later (line 215), is is replaced by "platex" (given that platex was found): if cmdOutput(PLATEX + ' chklatex.ltx').find('pLaTeX2e') != -1: # We have the Japanese pLaTeX2e addToRC(r'\converter platex dvi "%s" "latex"' % PLATEX) LATEX = PLATEX I suppose this is a remainder of the time when we did not yet separate platex from latex (and supposed that if platex is installed, it should be used). Jürgen
Re: r35040 - lyx-devel/trunk/src/frontends/qt4
spitz wrote: > Author: spitz > Date: Mon Aug 2 18:38:41 2010 > New Revision: 35040 > URL: http://www.lyx.org/trac/changeset/35040 > > Log: > * GuiLog.cpp: refine warning detection: > - detect "LaTeX Font Warning" > - detect "Class X Warning" > - package warnings can contain dots ("Package pdftex.def Warning") I intend to backport this to branch if there are no objections. Jürgen
Re: r35040 - lyx-devel/trunk/src/frontends/qt4
Log: * GuiLog.cpp: refine warning detection: - detect "LaTeX Font Warning" - detect "Class X Warning" - package warnings can contain dots ("Package pdftex.def Warning") -QRegExp exprWarning("^(LaTeX Warning|Package \\w+ Warning).*$"); +QRegExp exprWarning("^(LaTeX Warning|LaTeX Font Warning|Package [\\w \\.]+ Warning|Class \\w+ Warning).*$"); Why not factor " Warning" out of the parenthesis? JMarc
Re: platex as the default latex command?
Le 2 août 10 à 17:58, Jürgen Spitzmüller a écrit : No. "latex" is found and ascribed to the LATEX variable. But later (line 215), is is replaced by "platex" (given that platex was found): if cmdOutput(PLATEX + ' chklatex.ltx').find('pLaTeX2e') != -1: # We have the Japanese pLaTeX2e addToRC(r'\converter platex dvi "%s" "latex"' % PLATEX) LATEX = PLATEX I suppose this is a remainder of the time when we did not yet separate platex from latex (and supposed that if platex is installed, it should be used). OK, then your patch seems fine. JMarc
Re: r35040 - lyx-devel/trunk/src/frontends/qt4
Jean-Marc Lasgouttes wrote: > > -QRegExp exprWarning("^(LaTeX Warning|Package \\w+ Warning).*$"); > > +QRegExp exprWarning("^(LaTeX Warning|LaTeX Font Warning|Package [\\w > > \\.]+ Warning|Class \\w+ Warning).*$"); > > Why not factor " Warning" out of the parenthesis? You mean QRegExp exprWarning("^(LaTeX|LaTeX Font|Package [\\w\\.]+|Class \\w+) Warning.*$"); ? (sorry, I'm not so good at regexing). Jürgen
Re: Beta plans (again)
Am 02.08.2010 um 01:55 schrieb Jean-Marc Lasgouttes: > Le 26 juil. 10 à 14:30, Stephan Witt a écrit : >> My next target (for beta phase?) would be to check the installation issues >> on mac to make the application working out-of-the-box. > > What about removing the complicated mac-specific code in aspell now that it > is not needed anymore? I'm a little bit sorrowful that the native spell checker is not fast enough for continuously checking when doing it word-wise. So we are not ready to switch off aspell :( Currently I have no time to improve the situation. You're back in Paris? Yesterday evening I crossed the Rue de Clignancourt :-) Tomorrow I'll leave Paris and go to Orleans. Stephan
Re: r35040 - lyx-devel/trunk/src/frontends/qt4
Le 2 août 10 à 19:29, Jürgen Spitzmüller a écrit : Why not factor " Warning" out of the parenthesis? You mean QRegExp exprWarning("^(LaTeX|LaTeX Font|Package [\\w\\.]+|Class \\w+) Warning.*$"); ? (sorry, I'm not so good at regexing). Yes, but if you find the first solution more readable, you can keep it... (now that I see it, I am not sure that it is much of a gain) JMarc
Re: Beta plans (again)
Le 2 août 10 à 20:57, Stephan Witt a écrit : I'm a little bit sorrowful that the native spell checker is not fast enough for continuously checking when doing it word-wise. So we are not ready to switch off aspell :( Currently I have no time to improve the situation. I think I hqve some. I'll see what I can do. You're back in Paris? Yesterday evening I crossed the Rue de Clignancourt :-) Tomorrow I'll leave Paris and go to Orleans. Too bad, I arrived yesterday evening and I am here until 13/08. JMarc
Re: [patch] revtex 4.1 support
On 01/08/2010 3:54 AM, Jürgen Spitzmüller wrote: Julien Rioux wrote: Here is a patch against latest trunk for a REVTeX 4.1 layout and template file. Could you briefly decribe the changes wrt ReVTeX 4, or are there too many? Jürgen The changes to the latex class are described here: [1]. On the layout side, changes include: - Use of categories - Added support for ruledtabular, subequations, turnpage, and widetext environments. - Support for video float, \setfloatlink, \lowercase and \surname commands (those are specific to 4.1). Revtex 4.1 was designed in conjunction with the developer of natbib and this lead to natbib 8.31 which also brings new features. These are at the moment unsupported by LyX: - multiple references in a single bibliography entry, e.g. \cite{ref1,*ref2} becomes [1] in text and in the reference list: [1] Author1, ref1 (year1); author2, ref2 (year2). - prepending/appending text to a bibliography entry, e.g. \cite{[, and references therein.]ref3} becomes: [2] Author3, ref3 (year3), and references therein. You can edit a LyX file to hack this sort of syntax into a citation inset, and it will work, but there is currently no UI. I didn't attempt to tackle this. -- Julien [1] https://authors.aps.org/revtex4/revtex4_faq.html#c1
Re: [patch] revtex 4.1 support
When I said "edit a LyX file" I meant with an external plain text editor. It confuses the LyX GUI a bit but compiles fine with the expected result. -- Julien
Re: No Mouse scrolling in LyX 2.0 - Mac?
Am 02.08.2010 um 12:41 schrieb Jürgen Spitzmüller: > Jean-Marc LASGOUTTES wrote: >>> Nevertheless, the commit seems appropriate. >> >> I hope so. It looks safe, but one never knows... > > So everybody please test mouse scrolling in branch. > (it still works here) Works for me with scroll pad on mac. Stephan
Re: [patch] layout dependencies
On 2010-07-30, Julien Rioux wrote: > This is a multi-part message in MIME format. > --030503040800070104030405 > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > Content-Transfer-Encoding: 7bit > Hi LyX developers, > LyX 2.0 now has a new mechanism for relaying layout dependencies to the > user, such as the class filename. Most LaTeX classes also rely on > certain packages to be installed. It could be argued that this > information should be provided to LyX in the layout files. This patch > address this. With these additions, it would be nice if the reported error for nonavailable dependencies would be changed from Not available: to Missing dependencies: ... Günter
Re: Beta plans (again)
Le 2 août 10 à 20:57, Stephan Witt a écrit : I'm a little bit sorrowful that the native spell checker is not fast enough for continuously checking when doing it word-wise. So we are not ready to switch off aspell :( Currently I have no time to improve the situation. I do not manage to get the native spellchecker to work. The situation is that I do not use the binary-release.sh script, but only the plain configure script. I found that I have to set MACOSX_DEPLOYMENT_TARGET and SDKROOT before running make. I plan to eventually move this to configure.ac (the idea is that plan configure should be enough in general, and the full script is for packagers) The situation I am in is that no language seems to be recognized. For example, in hasLanguageAppleSpeller, [speller->checker availableLanguages] returns an empty list. Do you have an idea about what could be the cause? I am on Leopard (10.5), BTW. JMarc PS: Gino: echo $MACOSX_DEPLOYMENT_TARGET 10.4 Gino: echo $SDKROOT /Developer/SDKs/MacOSX10.5.sdk