Re: Problem using tex2lyx Unicode char \u8:�in not set up for use with LaTeX.
On 2010-05-27, Jean-Marc Lasgouttes wrote: b) When converting to PDF via pdflatex I ran into several problems: b1) (a lot of them) wrong input encoding: ! Package inputenc Error: Unicode char \u8:=EF=BF=BDin not set up for use w= ith LaTeX. The standard unicode input encoding (utf8) is rather limited. LyX has a more comprehensive translation table, so setting the output encoding to language default (in DocumentSettingsLanguage) might solve this problem. However the question is to know why the encoding is set to utf8 by tex2lyx. Most probably because the original file used it. However, in this case the question is, how the non-translable Unicode character came into the file: * Does tex2lyx do reverse engineering of LaTeX commands to unicode characters? * or, maybe the OP did insert it after the conversion to LyX? A minimal example file would help. Günter
save as latex file: displaymath instead of \[, newline
Hello When I save a LyX document to Latex (using 1.6.2) the resulting Latex file looks like: , | | this is a test | | \[ | \int\] | | and then ` Couldn't it be saved as , | this is a test | \[ | \int | \] | and then ` an empty line between this is a test and \[ causes unnecessary spaces. The \int\] instead of \int \] makes reading it more difficult. Another point is instead of using \[, using displaymath , | this is a test | \begin{displaymath} | \int | \end{displaymath} | and then ` The reason for displaymath is: using displaymath the code is nicely displayed in (X)emacs. Uwe Brauer
feature proposal: show latex code: allow to manipulate the latex code: reveal code
Hello One of the things I like in LyX is that the source code is shown. It is a little like reveal code in wordperfect, which I recently discovered. However sometimes lyx is doing things I don't want like inserting a new line. Would it be possible to manipulate directly the source code window, that would to obtain even better control about the final document. Uwe Brauer
Re: feature proposal: show latex code: allow to manipulate the latex code: reveal code
On 05/28/2010 06:13 AM, Uwe Brauer wrote: Hello One of the things I like in LyX is that the source code is shown. It is a little like reveal code in wordperfect, which I recently discovered. However sometimes lyx is doing things I don't want like inserting a new line. Would it be possible to manipulate directly the source code window, that would to obtain even better control about the final document. This is a long-standing request. You can find it on trac, if you look. Unfortunately, it is not at all easy to do. Richard
Re: save as latex file: displaymath instead of \[, newline
an empty line between this is a test and \[ causes unnecessary spaces. That's a matter of taste. Some users prefer the space to make it better readable for humans. We cannot satisfy everybody's wishes in this respect but have to find a compromise. Another point is instead of using \[, using displaymath. The reason for displaymath is: using displaymath the code is nicely displayed in (X)emacs. \[\] is the standard LaTeX formula environment and should therefore be recognized by every LaTeX editor. If not, request this feature from the developers of your preferred editor. We cannot simply change this because then other third-party programs like converters might have problems. Whe therefore try to keep the LaTeX output as stable as possible. regards Uwe
Re: save as latex file: displaymath instead of \[, newline
On Fri, 28 May 2010 15:21:44 +0200, Uwe Stöhr uwesto...@web.de wrote: That's a matter of taste. Some users prefer the space to make it better readable for humans. We cannot satisfy everybody's wishes in this respect but have to find a compromise. ok \[\] is the standard LaTeX formula environment and should therefore be recognized by every LaTeX editor. If not, request this feature from the developers of your preferred editor. Well I thought \begin{displaymath} is the standard, but I take your word. We cannot simply change this because then other third-party programs like converters might have problems. Whe therefore try to keep the LaTeX output as stable as possible. ok But what's about my third complain, namely the feature \] text I don't see the benefit of it and it is really annoying. So saving it as \] text is preferable. Don't you agree? regards Uwe
Child encodings
LyX 1.6.5, then 1.6.6 Windows MiKTeX 2.8 Included some child documents with different encodings and got the following: !! Package inputenc Error: Keyboard character used is undefined !! As found, the solution for TeX is to insert \inputencoding{foo} The problem seems to be that LyX exports child documents to TeX with no information on encoding. Yet adding an ERT inset with that code is also a solution. -- Dionysios
spreadsheet capability?
Has anybody ever tried to provide lyx with some spreadsheet capability, exploiting its symbolic computation backends? thank you ---P
Re: save as latex file: displaymath instead of \[, newline
On Fri, May 28, 2010 at 12:10:39PM +0200, Uwe Brauer wrote: an empty line between this is a test and \[ causes unnecessary spaces. This happens because you hit the Enter key before the equation. If you go to Preferences-LookFeel-Display and select Mark end of paragraphs, you will see a pilcrow marking the end of a paragraph. Positioning the cursor just before the equation and hitting the backspace key, the pilcrow marker should disappear and you will not get the extra space on output. The \int\] instead of \int \] makes reading it more difficult. This is more tricky than you imagine, because there's a risk of introducing an end of paragraph not easily eliminable as in the previous case. However, I think that it is possible to output %\n\\] instead of \\] such that you would get \int% \] without risking obscure bugs. -- Enrico
LyX 1.6.6.1
I've set up a new tarball, labelled lyx-1.6.6.1, that just consists of a fix to #6708 (spellchecker misses every second word after you corrected the first one). This is in fact Lyx 1.6.6 with r33567 reverted. None of the new stuff in branch is included. Also, I have not yet reverted r33567 in branch. I leave that to Jean-Marc. Please find the tarballs here: ftp://ftp.devel.lyx.org/pub/lyx/stable/lyx-1.6.6.1.tar.gz ftp://ftp.devel.lyx.org/pub/lyx/stable/lyx-1.6.6.1.tar.bz2 Due to the annonyance factor of this spellchecker issue, I'd like to release Lyx 1.6.6.1 as soon as possible. This does of course not exclude a soonish release of LyX 1.6.7, if this is judged by the further progress in branch. Objections? Jürgen
Next change in child document
Hello, we have a document with child documents embedded and we use change tracking. Is there a way for LyX to look into child documents, when I do Navigate - Next Change ? Thanks, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ signature.asc Description: This is a digitally signed message part.
Re: spreadsheet capability?
On 2010-05-28, xPol wrote: Has anybody ever tried to provide lyx with some spreadsheet capability, exploiting its symbolic computation backends? Not to my knowledge. However, the Gnumeric spreadsheet has a LaTeX export feature, so one could possibly write an external inset wrapper for it. Günter
Re: LyX 1.6.6.1
On Fri, May 28, 2010 at 12:58 PM, Jürgen Spitzmüller sp...@lyx.org wrote: I've set up a new tarball, labelled lyx-1.6.6.1, that just consists of a fix to #6708 (spellchecker misses every second word after you corrected the first one). This is in fact Lyx 1.6.6 with r33567 reverted. None of the new stuff in branch is included. Also, I have not yet reverted r33567 in branch. I leave that to Jean-Marc. Please find the tarballs here: ftp://ftp.devel.lyx.org/pub/lyx/stable/lyx-1.6.6.1.tar.gz ftp://ftp.devel.lyx.org/pub/lyx/stable/lyx-1.6.6.1.tar.bz2 Due to the annonyance factor of this spellchecker issue, I'd like to release Lyx 1.6.6.1 as soon as possible. This does of course not exclude a soonish release of LyX 1.6.7, if this is judged by the further progress in branch. Mac universal binary can be found here: http://edisk.fandm.edu/bennett.helm/lyx/LyX-1.6.6.1-Mac-Universal.dmg BH
Re: spreadsheet capability?
On Fri, May 28, 2010 at 8:23 PM, Guenter Milde mi...@users.berlios.de wrote: However, the Gnumeric spreadsheet has a LaTeX export feature, so one could possibly write an external inset wrapper for it. Apparently there is a patch [1] by Helge Hafting. More info on the subject in this thread [2] and on the wiki [3]. Liviu PS Would the devels consider including the patch in LyX 2.0? [1] http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg132049.html [2] http://www.mail-archive.com/lyx-us...@lists.lyx.org/msg75702.html [3] http://wiki.lyx.org/Tips/CopyTablesFromSpreadsheets
Code Review: Next step to provide spellchecker with dictionaries included
Dear LyX developers, I've prepared a patch to change hunspell and myThes wrappers to be ready for included dictionaries. Please have a look at the patch and point me to typos and thinkos. With the changes the binary searches the data files in this order: 1. user path from configuration 2. user support directory and 3. system support directory - there will the shipped data files live. The next steps on my agenda are * apple spell checker * aspell fix (if possible) * dictionary collection Regards, Stephan Index: development/LyX-Mac-binary-release.sh === --- development/LyX-Mac-binary-release.sh (Revision 34532) +++ development/LyX-Mac-binary-release.sh (Arbeitskopie) @@ -9,12 +9,27 @@ # Prerequisite: # * a decent checkout of LyX sources (probably you have it already) -# * Qt4 - build with shared or static libraries for the used platforms (i386 and ppc) +# * Qt4 - build with shared or static libraries for the used platforms (default: i386 and ppc) +#or - an unpacked source tree of Qt4 in $QT4SOURCEDIR or in the sibling directory (variable Qt4SourceVersion) # * for aspell support: # the aspell sources placed in a sibling directory (variable ASpellSourceVersion) +# * for hunspell support: +# the hunspell sources placed in a sibling directory (variable HunSpellSourceVersion) +# * for dictionary deployment: +# - aspell: the dictionary files of macports (in /opt/local/share/aspell and /opt/local/lib/aspell-0.60) +# - hunspell: the dictionary files in the sibling directory Dictionaries/dict +# - mythes: the data and idx files in the sibling directory Dictionaries/thes -ConfigureOptions=--enable-warnings --enable-optimization=-Os --with-included-gettext -dict_deployment=yes +LyXConfigureOptions=--enable-warnings --enable-optimization=-Os --with-included-gettext +AspellConfigureOptions=--enable-warnings --disable-nls --enable-compile-in-filters --disable-pspell-compatibility +HunspellConfigureOptions=--with-warnings --disable-nls --with-included-gettext --disable-static +Qt4ConfigureOptions=-opensource -silent -shared -release -fast -no-exceptions +Qt4ConfigureOptions=${Qt4ConfigureOptions} -no-webkit -no-qt3support -no-javascript-jit -no-dbus +Qt4ConfigureOptions=${Qt4ConfigureOptions} -nomake examples -nomake demos -nomake docs -nomake tools + +aspell_deployment=yes +hunspell_deployment=yes +thesaurus_deployment=yes qt4_deployment=yes MACOSX_DEPLOYMENT_TARGET=10.4 # Tiger support is default @@ -22,15 +37,15 @@ echo Build script for LyX on Mac OS X echo echo Optional arguments: - echo --tiger-support=yes|no . default yes - echo --dict-deployment=yes|no ... default yes + echo --aspell-deployment=yes|no . default yes echo --qt4-deployment=yes|no default yes + echo --with-macosx-target=TARGET default 10.4 (Tiger) echo --with-arch=ARCH ... default ppc,i386 echo --with-build-path=PATH . default \${lyx-src-dir}/../lyx-build echo --with-dmg-location=PATH ... default \${build-path} echo echo All other arguments with -- are passed to configure - echo including the defaults: ${ConfigureOptions} + echo including the defaults: ${LyXConfigureOptions} echo exit 0 } @@ -41,15 +56,22 @@ QTDIR=`echo ${1}|cut -d= -f2` shift ;; - --tiger-support=[Nn][Oo]) - MACOSX_DEPLOYMENT_TARGET= - MYCFLAGS= + --with-macosx-target=*) + MACOSX_DEPLOYMENT_TARGET=`echo ${1}|cut -d= -f2` shift ;; - --dict-deployment=*) - dict_deployment=`echo ${1}|cut -d= -f2` + --aspell-deployment=*) + aspell_deployment=`echo ${1}|cut -d= -f2` shift ;; + --hunspell-deployment=*) + hunspell_deployment=`echo ${1}|cut -d= -f2` + shift + ;; + --thesaurus-deployment=*) + thesaurus_deployment=`echo ${1}|cut -d= -f2` + shift + ;; --qt4-deployment=*) qt4_deployment=`echo ${1}|cut -d= -f2` shift @@ -70,8 +92,18 @@ --help) usage ;; + --without-aspell) + LyXConfigureOptions=${LyXConfigureOptions} ${1} + aspell_deployment=no + shift + ;; + --without-hunspell) + LyXConfigureOptions=${LyXConfigureOptions} ${1} + hunspell_deployment=no + shift + ;; --*) - ConfigureOptions=${ConfigureOptions} ${1} + LyXConfigureOptions=${LyXConfigureOptions} ${1} shift ;; *) @@ -90,6 +122,9 @@ QtInstallDir=${QTDIR:-/opt/qt4} QtFrameworkVersion=4
Re: spreadsheet capability?
Liviu Andronic wrote: On Fri, May 28, 2010 at 8:23 PM, Guenter Milde mi...@users.berlios.de wrote: However, the Gnumeric spreadsheet has a LaTeX export feature, so one could possibly write an external inset wrapper for it. Apparently there is a patch [1] by Helge Hafting. More info on the subject in this thread [2] and on the wiki [3]. Liviu PS Would the devels consider including the patch in LyX 2.0? please do you have any idea whether is safe to use blindly ssconvert or gnumeric in the sense that attacker can't write eg some excel macro-virus which would get executed via ssconvert or gnumeric? we have already rejected gnuplot support because of the fact that somebody could embed script like ! rm -rf / into .lyx file... pavel
Re: Code Review: Next step to provide spellchecker with dictionaries included
Stephan Witt wrote: The next steps on my agenda are * dictionary collection this is mac only thing or other archs need something similar? +#define MAX_SELECTOR 3 +string dictPath(int selector) +{ + switch (selector) { + case 2: return addName(lyx::support::package().system_support().absFileName(),HUNSPELL_DICT) ; break ; + case 1: return addName(lyx::support::package().user_support().absFileName(),HUNSPELL_DICT) ; break ; whitespaces pavel
Re: Problem using tex2lyx "Unicode char \u8:�in not set up for use with LaTeX."
On 2010-05-27, Jean-Marc Lasgouttes wrote: >>> b) When converting to PDF via pdflatex I ran into several problems: >>> b1) (a lot of them) wrong input encoding: >>> ! Package inputenc Error: Unicode char \u8:=EF=BF=BDin not set up >>> for use w= >>> ith LaTeX. >> The standard unicode input encoding (utf8) is rather limited. LyX >> has a >> more comprehensive translation table, so setting the output encoding >> to >> "language default" (in Document>Settings>Language) might solve this >> problem. > However the question is to know why the encoding is set to utf8 by > tex2lyx. Most probably because the original file used it. However, in this case the question is, how the non-translable Unicode character came into the file: * Does tex2lyx do "reverse engineering" of LaTeX commands to unicode characters? * or, maybe the OP did insert it after the conversion to LyX? A minimal example file would help. Günter
save as latex file: displaymath instead of \[, newline
Hello When I save a LyX document to Latex (using 1.6.2) the resulting Latex file looks like: , | | this is a test | | \[ | \int\] | | and then ` Couldn't it be saved as , | this is a test | \[ | \int | \] | and then ` an empty line between this is a test and \[ causes unnecessary spaces. The \int\] instead of \int \] makes reading it more difficult. Another point is instead of using \[, using displaymath , | this is a test | \begin{displaymath} | \int | \end{displaymath} | and then ` The reason for displaymath is: using displaymath the code is nicely displayed in (X)emacs. Uwe Brauer
feature proposal: show latex code: allow to manipulate the latex code: reveal code
Hello One of the things I like in LyX is that the source code is shown. It is a little like reveal code in wordperfect, which I recently discovered. However sometimes lyx is doing things I don't want like inserting a new line. Would it be possible to manipulate directly the source code window, that would to obtain even better control about the final document. Uwe Brauer
Re: feature proposal: show latex code: allow to manipulate the latex code: reveal code
On 05/28/2010 06:13 AM, Uwe Brauer wrote: Hello One of the things I like in LyX is that the source code is shown. It is a little like reveal code in wordperfect, which I recently discovered. However sometimes lyx is doing things I don't want like inserting a new line. Would it be possible to manipulate directly the source code window, that would to obtain even better control about the final document. This is a long-standing request. You can find it on trac, if you look. Unfortunately, it is not at all easy to do. Richard
Re: save as latex file: displaymath instead of \[, newline
> an empty line between this is a test and \[ causes > unnecessary spaces. That's a matter of taste. Some users prefer the space to make it better readable for humans. We cannot satisfy everybody's wishes in this respect but have to find a compromise. > Another point is instead of using \[, using displaymath. > The reason for displaymath is: using displaymath the code is nicely > displayed in (X)emacs. \[\] is the standard LaTeX formula environment and should therefore be recognized by every LaTeX editor. If not, request this feature from the developers of your preferred editor. We cannot simply change this because then other third-party programs like converters might have problems. Whe therefore try to keep the LaTeX output as stable as possible. regards Uwe
Re: save as latex file: displaymath instead of \[, newline
> On Fri, 28 May 2010 15:21:44 +0200, Uwe Stöhrwrote: > That's a matter of taste. Some users prefer the space to make it > better readable for humans. We cannot satisfy everybody's wishes in > this respect but have to find a compromise. ok > \[\] is the standard LaTeX formula environment and should therefore be > recognized by every LaTeX editor. If not, request this feature from > the developers of your preferred editor. Well I thought \begin{displaymath} is the standard, but I take your word. > We cannot simply change this because then other third-party programs > like converters might have problems. Whe therefore try to keep the > LaTeX output as stable as possible. ok But what's about my third complain, namely the feature \] text I don't see the benefit of it and it is really annoying. So saving it as \] text is preferable. Don't you agree? regards Uwe
Child encodings
LyX 1.6.5, then 1.6.6 Windows MiKTeX 2.8 Included some child documents with different encodings and got the following: !! Package inputenc Error: Keyboard character used is undefined !! As found, the solution for TeX is to insert \inputencoding{foo} The problem seems to be that LyX exports child documents to TeX with no information on encoding. Yet adding an ERT inset with that code is also a solution. -- Dionysios
spreadsheet capability?
Has anybody ever tried to provide lyx with some spreadsheet capability, exploiting its symbolic computation backends? thank you ---P
Re: save as latex file: displaymath instead of \[, newline
On Fri, May 28, 2010 at 12:10:39PM +0200, Uwe Brauer wrote: > an empty line between this is a test and \[ causes > unnecessary spaces. This happens because you hit the Enter key before the equation. If you go to "Preferences->Look>Display" and select "Mark end of paragraphs", you will see a pilcrow marking the end of a paragraph. Positioning the cursor just before the equation and hitting the backspace key, the pilcrow marker should disappear and you will not get the extra space on output. > The \int\] instead of > \int > \] > makes reading it more difficult. This is more tricky than you imagine, because there's a risk of introducing an end of paragraph not easily eliminable as in the previous case. However, I think that it is possible to output "%\n\\]" instead of "\\]" such that you would get \int% \] without risking obscure bugs. -- Enrico
LyX 1.6.6.1
I've set up a new tarball, labelled lyx-1.6.6.1, that just consists of a fix to #6708 (spellchecker misses every second word after you corrected the first one). This is in fact Lyx 1.6.6 with r33567 reverted. None of the new stuff in branch is included. Also, I have not yet reverted r33567 in branch. I leave that to Jean-Marc. Please find the tarballs here: ftp://ftp.devel.lyx.org/pub/lyx/stable/lyx-1.6.6.1.tar.gz ftp://ftp.devel.lyx.org/pub/lyx/stable/lyx-1.6.6.1.tar.bz2 Due to the annonyance factor of this spellchecker issue, I'd like to release Lyx 1.6.6.1 as soon as possible. This does of course not exclude a soonish release of LyX 1.6.7, if this is judged by the further progress in branch. Objections? Jürgen
Next change in child document
Hello, we have a document with child documents embedded and we use change tracking. Is there a way for LyX to look into child documents, when I do "Navigate" -> "Next Change" ? Thanks, Rainer -- Rainer Dorsch Lärchenstr. 6 D-72135 Dettenhausen 07157-734133 email: rdor...@web.de jabber: rdor...@jabber.org GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F 8F59 E3A8 C538 7519 141E Full GPG key: http://pgp.mit.edu/ signature.asc Description: This is a digitally signed message part.
Re: spreadsheet capability?
On 2010-05-28, xPol wrote: > Has anybody ever tried to provide lyx with some spreadsheet capability, > exploiting its symbolic computation backends? Not to my knowledge. However, the Gnumeric spreadsheet has a LaTeX export feature, so one could possibly write an "external inset" wrapper for it. Günter
Re: LyX 1.6.6.1
On Fri, May 28, 2010 at 12:58 PM, Jürgen Spitzmüllerwrote: > I've set up a new tarball, labelled lyx-1.6.6.1, that just consists of a fix > to #6708 (spellchecker misses every second word after you corrected the first > one). This is in fact Lyx 1.6.6 with r33567 reverted. None of the new stuff in > branch is included. Also, I have not yet reverted r33567 in branch. I leave > that to Jean-Marc. > > Please find the tarballs here: > ftp://ftp.devel.lyx.org/pub/lyx/stable/lyx-1.6.6.1.tar.gz > ftp://ftp.devel.lyx.org/pub/lyx/stable/lyx-1.6.6.1.tar.bz2 > > Due to the annonyance factor of this spellchecker issue, I'd like to release > Lyx 1.6.6.1 as soon as possible. This does of course not exclude a soonish > release of LyX 1.6.7, if this is judged by the further progress in branch. Mac universal binary can be found here: http://edisk.fandm.edu/bennett.helm/lyx/LyX-1.6.6.1-Mac-Universal.dmg BH
Re: spreadsheet capability?
On Fri, May 28, 2010 at 8:23 PM, Guenter Mildewrote: > However, the Gnumeric spreadsheet has a LaTeX export feature, so one > could possibly write an "external inset" wrapper for it. > Apparently there is a patch [1] by Helge Hafting. More info on the subject in this thread [2] and on the wiki [3]. Liviu PS Would the devels consider including the patch in LyX 2.0? [1] http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg132049.html [2] http://www.mail-archive.com/lyx-us...@lists.lyx.org/msg75702.html [3] http://wiki.lyx.org/Tips/CopyTablesFromSpreadsheets
Code Review: Next step to provide spellchecker with dictionaries included
Dear LyX developers, I've prepared a patch to change hunspell and myThes wrappers to be ready for included dictionaries. Please have a look at the patch and point me to typos and thinkos. With the changes the binary searches the data files in this order: 1. user path from configuration 2. user support directory and 3. system support directory - there will the shipped data files live. The next steps on my agenda are * apple spell checker * aspell fix (if possible) * dictionary collection Regards, Stephan Index: development/LyX-Mac-binary-release.sh === --- development/LyX-Mac-binary-release.sh (Revision 34532) +++ development/LyX-Mac-binary-release.sh (Arbeitskopie) @@ -9,12 +9,27 @@ # Prerequisite: # * a decent checkout of LyX sources (probably you have it already) -# * Qt4 - build with shared or static libraries for the used platforms (i386 and ppc) +# * Qt4 - build with shared or static libraries for the used platforms (default: i386 and ppc) +#or - an unpacked source tree of Qt4 in $QT4SOURCEDIR or in the sibling directory (variable Qt4SourceVersion) # * for aspell support: # the aspell sources placed in a sibling directory (variable ASpellSourceVersion) +# * for hunspell support: +# the hunspell sources placed in a sibling directory (variable HunSpellSourceVersion) +# * for dictionary deployment: +# - aspell: the dictionary files of macports (in /opt/local/share/aspell and /opt/local/lib/aspell-0.60) +# - hunspell: the dictionary files in the sibling directory Dictionaries/dict +# - mythes: the data and idx files in the sibling directory Dictionaries/thes -ConfigureOptions="--enable-warnings --enable-optimization=-Os --with-included-gettext" -dict_deployment="yes" +LyXConfigureOptions="--enable-warnings --enable-optimization=-Os --with-included-gettext" +AspellConfigureOptions="--enable-warnings --disable-nls --enable-compile-in-filters --disable-pspell-compatibility" +HunspellConfigureOptions="--with-warnings --disable-nls --with-included-gettext --disable-static" +Qt4ConfigureOptions="-opensource -silent -shared -release -fast -no-exceptions" +Qt4ConfigureOptions="${Qt4ConfigureOptions} -no-webkit -no-qt3support -no-javascript-jit -no-dbus" +Qt4ConfigureOptions="${Qt4ConfigureOptions} -nomake examples -nomake demos -nomake docs -nomake tools" + +aspell_deployment="yes" +hunspell_deployment="yes" +thesaurus_deployment="yes" qt4_deployment="yes" MACOSX_DEPLOYMENT_TARGET="10.4" # Tiger support is default @@ -22,15 +37,15 @@ echo Build script for LyX on Mac OS X echo echo Optional arguments: - echo " --tiger-support=yes|no ." default yes - echo " --dict-deployment=yes|no ..." default yes + echo " --aspell-deployment=yes|no ." default yes echo " --qt4-deployment=yes|no " default yes + echo " --with-macosx-target=TARGET " default 10.4 "(Tiger)" echo " --with-arch=ARCH ..." default ppc,i386 echo " --with-build-path=PATH ." default \${lyx-src-dir}/../lyx-build echo " --with-dmg-location=PATH ..." default \${build-path} echo echo "All other arguments with -- are passed to configure" - echo "including the defaults: ${ConfigureOptions}" + echo "including the defaults: ${LyXConfigureOptions}" echo exit 0 } @@ -41,15 +56,22 @@ QTDIR=`echo ${1}|cut -d= -f2` shift ;; - --tiger-support=[Nn][Oo]) - MACOSX_DEPLOYMENT_TARGET="" - MYCFLAGS="" + --with-macosx-target=*) + MACOSX_DEPLOYMENT_TARGET=`echo ${1}|cut -d= -f2` shift ;; - --dict-deployment=*) - dict_deployment=`echo ${1}|cut -d= -f2` + --aspell-deployment=*) + aspell_deployment=`echo ${1}|cut -d= -f2` shift ;; + --hunspell-deployment=*) + hunspell_deployment=`echo ${1}|cut -d= -f2` + shift + ;; + --thesaurus-deployment=*) + thesaurus_deployment=`echo ${1}|cut -d= -f2` + shift + ;; --qt4-deployment=*) qt4_deployment=`echo ${1}|cut -d= -f2` shift @@ -70,8 +92,18 @@ --help) usage ;; + --without-aspell) + LyXConfigureOptions="${LyXConfigureOptions} ${1}" + aspell_deployment="no" + shift + ;; + --without-hunspell) + LyXConfigureOptions="${LyXConfigureOptions} ${1}" + hunspell_deployment="no" + shift + ;; --*) - ConfigureOptions="${ConfigureOptions} ${1}" + LyXConfigureOptions="${LyXConfigureOptions} ${1}" shift ;; *) @@ -90,6
Re: spreadsheet capability?
Liviu Andronic wrote: > On Fri, May 28, 2010 at 8:23 PM, Guenter Mildewrote: > > However, the Gnumeric spreadsheet has a LaTeX export feature, so one > > could possibly write an "external inset" wrapper for it. > > > Apparently there is a patch [1] by Helge Hafting. More info on the > subject in this thread [2] and on the wiki [3]. > Liviu > > PS Would the devels consider including the patch in LyX 2.0? please do you have any idea whether is safe to use blindly ssconvert or gnumeric in the sense that attacker can't write eg some excel macro-virus which would get executed via ssconvert or gnumeric? we have already rejected gnuplot support because of the fact that somebody could embed script like "! rm -rf /" into .lyx file... pavel
Re: Code Review: Next step to provide spellchecker with dictionaries included
Stephan Witt wrote: > The next steps on my agenda are > * dictionary collection this is mac only thing or other archs need something similar? > +#define MAX_SELECTOR 3 > +string dictPath(int selector) > +{ > + switch (selector) { > + case 2: return > addName(lyx::support::package().system_support().absFileName(),HUNSPELL_DICT) > ; break ; > + case 1: return > addName(lyx::support::package().user_support().absFileName(),HUNSPELL_DICT) ; > break ; whitespaces pavel