Re: problems with pdf-quality and fontenc-package

Steve Litt writes: > > slitt mydesk:/d/at/books/mental$ pdffonts pthrive.pdf > name type emb sub uni object ID > - --- --- --- - > Courier-Bold Type 1

Re: problems with pdf-quality and fontenc-package

Sebastian Guttenberg gutte...@... writes: Well, it's one thing to optimize a file for the pdf-output and another that I am working usually with dvi and ps, but from time to time need to produce a pdf-version of it to somebody (who might use acroread on windows). It cannot be that the

Re: problems with pdf-quality and fontenc-package

Sebastian Guttenberg writes: > > Well, it's one thing to optimize a file for the pdf-output and another > that I am working usually with dvi and ps, but from time to time need > to produce a pdf-version of it to somebody (who might use acroread on > windows). It cannot be that the

Re: UserGuide and EmbeddedObjects compilations fail in French

Uwe Stöhr a écrit : Result in lyx-users: 5 success, 3 failures, clearly related to the TeXLive version (failure is with TeXLive 2007). I myself upgraded TeXLive to 2008 with success (without and with my patch). OK so it is a bug in TeXLive 2007. TeXLive 2008 and MiKTeX 2.7 and 2.8

Re: UserGuide and EmbeddedObjects compilations fail in French

Jürgen Spitzmüller sp...@... writes: Jean-Pierre Chrétien wrote: OK, but this LaTeX bug affects 37.5% of the installations, from the statistics on the Users' list... It's a quite bold idea to call the response of 8 people statistics and to deduce such a general percentage from

Re: UserGuide and EmbeddedObjects compilations fail in French

Jürgen Spitzmüller sp...@... writes: How hard will it be for affected people to upgrade the respective packages? Not hard, but needs patience. Here is the procedure on Linux to install TeXLive 2008: 1) Download the netinstaller (e.g. in /tmp) cd /tmp wget

Re: UserGuide and EmbeddedObjects compilations fail in French

Uwe Stöhr a écrit : > Result in lyx-users: 5 success, 3 failures, clearly related to the TeXLive version (failure is > with TeXLive 2007). > > I myself upgraded TeXLive to 2008 with success (without and with my patch). OK so it is a bug in TeXLive 2007. TeXLive 2008 and MiKTeX 2.7 and

Re: UserGuide and EmbeddedObjects compilations fail in French

Jürgen Spitzmüller <sp...@...> writes: > > Jean-Pierre Chrétien wrote: > > OK, but this LaTeX bug affects 37.5% of the installations, from the > > statistics on the Users' list... > > It's a quite bold idea to call the response of 8 people "statisti

Re: UserGuide and EmbeddedObjects compilations fail in French

Jürgen Spitzmüller writes: > > How hard will it be for affected people to upgrade the respective packages? Not hard, but needs patience. Here is the procedure on Linux to install TeXLive 2008: 1) Download the netinstaller (e.g. in /tmp) cd /tmp wget

Re: UserGuide and EmbeddedObjects compilations fail in French

Uwe Stöhr a écrit : [...] OK to assure that this hardcoding doesn't introduce new problems, can you please prepare a small LyX example file that fails for you and ask on the french-users and lyx-users mailing list who is able to compile the file with LyX 1.6.4 and who not. We need to know what

Re: UserGuide and EmbeddedObjects compilations fail in French

Uwe Stöhr a écrit : [...] OK to assure that this hardcoding doesn't introduce new problems, can you please prepare a small LyX example file that fails for you and ask on the french-users and lyx-users mailing list who is able to compile the file with LyX 1.6.4 and who not. We need to know what

Re: UserGuide and EmbeddedObjects compilations fail in French

Uwe Stöhr a écrit : Jean-Pierre Chrétien schrieb: [...] Can you please try to add this to the document preamble: \AtBeginDocument{\usepackage{nameref}} I did already try... no way, nameref should be added before varioref (otherwise I wouldn't have changed the LyX code itself). In fact

Re: UserGuide and EmbeddedObjects compilations fail in French

Uwe Stöhr a écrit : Jean-Pierre Chrétien schrieb: [...] Can you please try to add this to the document preamble: \AtBeginDocument{\usepackage{nameref}} I did already try... no way, nameref should be added before varioref (otherwise I wouldn't have changed the LyX code itself). In fact

Re: UserGuide and EmbeddedObjects compilations fail in French

Uwe Stöhr a écrit : With my Debian Lenny, doc/fr/Userguide.lyx and doc/fr/EmbeddedObjects.lyx compilations fail because character : is active in French. This is nowadays OK with most packages, but not with varioref, which version here is the last one according to CTAN: [2006/05/13

Re: UserGuide and EmbeddedObjects compilations fail in French

Uwe Stöhr a écrit : Jean-Pierre Chrétien schrieb: [...] The problem you have is a problem with LaTeX packages not with LyX. We try to avoid to introduce hard coded hacks into LyX to fix bugs in LaTeX packages. Only when such a problem is not fixable or when the package manuals explicitly

Re: UserGuide and EmbeddedObjects compilations fail in French

Uwe Stöhr a écrit : > With my Debian Lenny, doc/fr/Userguide.lyx and doc/fr/EmbeddedObjects.lyx > compilations fail because character ":" is active in French. This is nowadays OK > with most packages, but not with varioref, which version here is the last one > according to CTAN: >

Re: UserGuide and EmbeddedObjects compilations fail in French

Uwe Stöhr a écrit : Jean-Pierre Chrétien schrieb: [...] The problem you have is a problem with LaTeX packages not with LyX. We try to avoid to introduce hard coded hacks into LyX to fix bugs in LaTeX packages. Only when such a problem is not fixable or when the package manuals explicitly

UserGuide and EmbeddedObjects compilations fail in French

Hello, With my Debian Lenny, doc/fr/Userguide.lyx and doc/fr/EmbeddedObjects.lyx compilations fail because character : is active in French. This is nowadays OK with most packages, but not with varioref, which version here is the last one according to CTAN: [2006/05/13 v1.4p package for

UserGuide and EmbeddedObjects compilations fail in French

Hello, With my Debian Lenny, doc/fr/Userguide.lyx and doc/fr/EmbeddedObjects.lyx compilations fail because character ":" is active in French. This is nowadays OK with most packages, but not with varioref, which version here is the last one according to CTAN: [2006/05/13 v1.4p package for

iconv fails on Unicode dashes

Hello, I recently discovered that I could not convert some docs from UTF to latin1 with iconv, which stops on message: iconv: illegal input sequence at position 851 The reason is the Unicode encoding of dashes, e.g. emdash (exported all right in LaTeX as \textemdash), iconv does not seem to be

iconv fails on Unicode dashes

Hello, I recently discovered that I could not convert some docs from UTF to latin1 with iconv, which stops on message: iconv: illegal input sequence at position 851 The reason is the Unicode encoding of dashes, e.g. emdash (exported all right in LaTeX as \textemdash), iconv does not seem to be

Untranslated warning

Hello, I installed on Debian a preference file that I used for Solaris and I got this: GuiPrefs.cpp(303): FAILED to find the default font: 'Adobe', 'Times' GuiPrefs.cpp(303): FAILED to find the default font: 'Adobe', 'Helvetica' GuiPrefs.cpp(303): FAILED to find the default font: 'Adobe',

Untranslated warning

Hello, I installed on Debian a preference file that I used for Solaris and I got this: GuiPrefs.cpp(303): FAILED to find the default font: 'Adobe', 'Times' GuiPrefs.cpp(303): FAILED to find the default font: 'Adobe', 'Helvetica' GuiPrefs.cpp(303): FAILED to find the default font: 'Adobe',

Re: TeX capacity exceeded: sorry, main memory [main memory size=1500000]

rgheck rgh...@... writes: Waluyo Adi Siswanto wrote: Actually I have a problem (in LyX 1.6.2) when I want to set the page without number under the Part environment using ERT \thispagestyle{empty}. The document class is book(koma-script). [...] The difference is that hyperref is turned

Re: TeX capacity exceeded: sorry, main memory [main memory size=1500000]

rgheck writes: > > Waluyo Adi Siswanto wrote: > > Actually I have a problem (in LyX 1.6.2) when I want to set the page > > without number under the Part environment using ERT > > \thispagestyle{empty}. The document class is book(koma-script). [...] > The difference is that hyperref

beta4 on Solaris

Hello, Compilation stops with this on stderr: Qt resource compiler Usage: /usr/local/qt-4.3.4//bin/rcc [options] inputs Options: -o file write output to file rather than stdout -name namecreate an external initialization function with name -threshold level threshold to

Re: beta4 on Solaris

Jean-Marc Lasgouttes [EMAIL PROTECTED] writes: Jean-Pierre Chrétien [EMAIL PROTECTED] writes: Compilation stops with this on stderr: Qt resource compiler Usage: /usr/local/qt-4.3.4//bin/rcc [options] inputs What is the command that gets passed to rcc? Is that with gnu make? Oops

beta4 on Solaris

Hello, Compilation stops with this on stderr: Qt resource compiler Usage: /usr/local/qt-4.3.4//bin/rcc [options] Options: -o file write output to file rather than stdout -name namecreate an external initialization function with name -threshold level threshold to

Re: beta4 on Solaris

Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > > Jean-Pierre Chrétien <[EMAIL PROTECTED]> writes: > > Compilation stops with this on stderr: > > > > Qt resource compiler > > Usage: /usr/local/qt-4.3.4//bin/rcc [options] > > What is the c

Cryptic message

Hello, I tried to import a 1.4.5 beamer presentation in Lyx-1.5.5. Worked OK, but when I tried to view PDF, an error window opened with a message Conversion failed which was explained in the bottom subwindow by boost::filesystem::last_write_time It took me a while to understand that a figure was

Cryptic message

Hello, I tried to import a 1.4.5 beamer presentation in Lyx-1.5.5. Worked OK, but when I tried to view PDF, an error window opened with a message "Conversion failed" which was explained in the bottom subwindow by boost::filesystem::last_write_time It took me a while to understand that a figure

Re: Beta 2 (private announcement)

José Matos [EMAIL PROTECTED] writes: Hi all, as discussed during the weekend and in order to fix the problems that appeared with beta 1 I have tagged a new release (beta 2). As it happened previously I am asking for help to guarantee that there are no embarrassing bugs. I

Re: Platform-dependent Menu Structure ? [Was: LyX Menu Structure]

Konrad Hofbauer [EMAIL PROTECTED] writes: [...] So my big question is: *** Should the menu stucture be platform-specific ? *** *** PROS *** + Consistency accross different applications. + Things are where the user expects them. + LyX can better conform to the platform HIG. + Overall

Re: Beta 2 (private announcement)

José Matos <[EMAIL PROTECTED]> writes: > > Hi all, > as discussed during the weekend and in order to fix the problems that > appeared with beta 1 I have tagged a new release (beta 2). > > As it happened previously I am asking for help to guarantee that there > are no >

Re: Platform-dependent Menu Structure ? [Was: LyX Menu Structure]

Konrad Hofbauer <[EMAIL PROTECTED]> writes: [...] > > So my big question is: > > *** Should the menu stucture be platform-specific ? *** > > *** PROS *** > + Consistency accross different applications. > + Things are where the user expects them. > + LyX can better conform to the platform HIG. >

Bug 2529

Hello, Will this bug be solved in 1.6 ? Stopping/restarting the spellchecker is an effective workaround, but it's quite boring. -- Jean-Pierre

Bug 2529

Hello, Will this bug be solved in 1.6 ? Stopping/restarting the spellchecker is an effective workaround, but it's quite boring. -- Jean-Pierre

Re: 1.5.5

Juergen Spitzmueller [EMAIL PROTECTED] writes: [...] I don't think so. Do you refer to the 1.5.4 release? Note that assertions are disabled in our release versions, so this might be the reason it didn't hit you. The good news is that it won't probably hit you on the 1.5.5 release either,

Re: 1.5.5

Juergen Spitzmueller <[EMAIL PROTECTED]> writes: [...] > > I don't think so. Do you refer to the 1.5.4 release? Note that assertions > are disabled in our release versions, so this might be the reason it didn't > hit you. > > The good news is that it won't probably hit you on the 1.5.5 release

Re: 1.5.5

Juergen Spitzmueller [EMAIL PROTECTED] writes: Jean-Pierre Chrétien wrote: I'm afraid I was optimistic: LyX compiles fines, but I have again an assertion when I leave LyX, and more critically (as it aborts LyX), when I copy a string Assertion failed: __pos size(), fichier /usr

Re: 1.5.5

Juergen Spitzmueller <[EMAIL PROTECTED]> writes: > > Jean-Pierre Chrétien wrote: > > > I'm afraid I was optimistic: LyX compiles fines, but I have again > > an assertion when I leave LyX, and more critically (as it aborts LyX), > > when I copy a string > &

Re: 1.5.5

Jürgen Spitzmüller [EMAIL PROTECTED] writes: I'll put CC: to lyx-devel, so others might comment as well. Jean-Pierre Chretien wrote: Jürgen Spitzmüller wrote: Jean-Pierre Chretien wrote: 1.5.5svn compiles fine on Solaris with qt-4.3.4, but I get a lot of warnings. I guess they

Re: 1.5.5

Jürgen Spitzmüller <[EMAIL PROTECTED]> writes: > > I'll put CC: to lyx-devel, so others might comment as well. > > Jean-Pierre Chretien wrote: > > Jürgen Spitzmüller wrote: > > > Jean-Pierre Chretien wrote: > > > > 1.5.5svn compiles fine on Solaris with qt-4.3.4, but I get > > > > a lot of

Re: Discrepnacies between fils upgraded to 1.6 from 1.5.4

José Matos [EMAIL PROTECTED] writes: On Thursday 27 March 2008 17:36:34 Jean-Pierre Chrétien wrote: This seems harmless as both files can be edited in lyx-1.6svn, but does it deserve an entry in bugzilla ? Yes, it does. This means that some of the previous lyx2lyx convertions

Re: Discrepnacies between fils upgraded to 1.6 from 1.5.4

José Matos <[EMAIL PROTECTED]> writes: > > On Thursday 27 March 2008 17:36:34 Jean-Pierre Chrétien wrote: > > This seems harmless as both files can be edited in lyx-1.6svn, but > > does it deserve an entry in bugzilla ? > > Yes, it does. This means tha

Discrepnacies between fils upgraded to 1.6 from 1.5.4

Hello, I converted lyx-1.5.4/doc/Intro.lyx in two ways: - open in lyx-1.6svn, save as /tmp/opensave/Intro.lyx - command line using lyx2lyx: #/usr/local/share/lyx-devel/lyx2lyx/lyx2lyx -t 321 \ -o /tmp/commandline/Intro.lyx /usr/local/share/lyx-1.5.4/doc/Intro.lyx There are differences between

Re: Discrepnacies between fils upgraded to 1.6 from 1.5.4

Jean-Pierre Chrétien [EMAIL PROTECTED] writes: Hello, [...] There are differences between the two files, mostly about the name of the Standard layout, which has been changed in the opensave version, details here http://www.cert.fr/lyxfr/Intro.diff This file will be visible after 7 pm

Discrepnacies between fils upgraded to 1.6 from 1.5.4

Hello, I converted lyx-1.5.4/doc/Intro.lyx in two ways: - open in lyx-1.6svn, save as /tmp/opensave/Intro.lyx - command line using lyx2lyx: #/usr/local/share/lyx-devel/lyx2lyx/lyx2lyx -t 321 \ -o /tmp/commandline/Intro.lyx /usr/local/share/lyx-1.5.4/doc/Intro.lyx There are differences between

Re: Discrepnacies between fils upgraded to 1.6 from 1.5.4

Jean-Pierre Chrétien <[EMAIL PROTECTED]> writes: > > Hello, [...] > There are differences between the two files, mostly about the name > of the Standard layout, which has been changed in the opensave version, > details here > http://www.cert.fr/lyxfr/Intro.diff This file

Re: LyX - 1.6.0 (alpha 1) Easter edition

Pavel Sanda [EMAIL PROTECTED] writes: [...] make[4]: *** No rule to make target `ui_AboutUi.h', needed by `all'. Stop. Here on Solaris 8 with gcc-3.4.6 and qt-4.3.3 I don't go that far: cite make[3]: Entering directory `/tmp/lyx-1.6.0alpha1/po' make[3]: *** No rule to make target

Re: LyX - 1.6.0 (alpha 1) Easter edition

Jean-Pierre Chretien [EMAIL PROTECTED] writes: [...] cite make[3]: Entering directory `/tmp/lyx-1.6.0alpha1/po' make[3]: *** No rule to make target `../src/frontends/qt4/ui/*.ui', needed by `qt4_l10n.pot'. Stop. /cite You probably need gmake (although I think we should work at

Re: LyX - 1.6.0 (alpha 1) Easter edition

Pavel Sanda <[EMAIL PROTECTED]> writes: [...] > > make[4]: *** No rule to make target `ui_AboutUi.h', needed by `all'. Stop. Here on Solaris 8 with gcc-3.4.6 and qt-4.3.3 I don't go that far: make[3]: Entering directory `/tmp/lyx-1.6.0alpha1/po' make[3]: *** No rule to make target

Re: LyX - 1.6.0 (alpha 1) Easter edition

Jean-Pierre Chretien <[EMAIL PROTECTED]> writes: >[...] > >>> > >>> make[3]: Entering directory `/tmp/lyx-1.6.0alpha1/po' > >>> make[3]: *** No rule to make target `../src/frontends/qt4/ui/*.ui', > >>> needed by > >>> `qt4_l10n.pot'. Stop. > >>> > >> > >>You probably need gmake (although I

Name field in the Inset-Reference popup

Hello, I guess that this field allows to insert manually a text to reference the label. It is inactivated (and seems undocumented). What should be done to activate it ? Load some package ? -- Jean-Pierre

Name field in the Inset->Reference popup

Hello, I guess that this field allows to insert manually a text to reference the label. It is inactivated (and seems undocumented). What should be done to activate it ? Load some package ? -- Jean-Pierre

amsmaths.inc

Hello, While creating a new layout, I had an error (\theoremstyle missing). Jean-Marc pointed out that this was defined in amsthm.sty. Checking AMS in Document-Settings is useless, this does not load amsthm, only amsmath and amsfonts. I guess that this patch --- amsmaths.inc.orig 2008-03-07

amsmaths.inc

Hello, While creating a new layout, I had an error (\theoremstyle missing). Jean-Marc pointed out that this was defined in amsthm.sty. Checking AMS in Document->Settings is useless, this does not load amsthm, only amsmath and amsfonts. I guess that this patch --- amsmaths.inc.orig 2008-03-07

.mo files portability

Hello, I've detected a remaining shortcut conflict in fr.po. I've updated lyx-1.5.4.mo on my server, but is this .mo file portable on any platform ? If it is, I can publish it on the lyx-fr website. Where are located the .mo files ? Here on Solaris, they are in

.mo files portability

Hello, I've detected a remaining shortcut conflict in fr.po. I've updated lyx-1.5.4.mo on my server, but is this .mo file portable on any platform ? If it is, I can publish it on the lyx-fr website. Where are located the .mo files ? Here on Solaris, they are in

NewInLyX16

Hello, I've just parsed the wiki page about the subject. I am very much impressed, you have done a great work! Thanks a lot again for making (La)TeX so easy to control. -- Jean-Pierre

NewInLyX16

Hello, I've just parsed the wiki page about the subject. I am very much impressed, you have done a great work! Thanks a lot again for making (La)TeX so easy to control. -- Jean-Pierre

Gmane display is not threaded anymore

Hello, The subject says all :-( Gmane stalled some time last week, is this connected ? Do I miss something ? Regards -- Jean-Pierre

Re: Gmane display is not threaded anymore

Paul A. Rubin [EMAIL PROTECTED] writes: [...] Are you referring to the web interface? Yes, I follow devel with it, subscribing overwhelms my box. I always go in through the search engine. Once I find an article in the right thread, if I click the subject, I get a new view using

Gmane display is not threaded anymore

Hello, The subject says all :-( Gmane stalled some time last week, is this connected ? Do I miss something ? Regards -- Jean-Pierre

Re: Gmane display is not threaded anymore

Paul A. Rubin <[EMAIL PROTECTED]> writes: [...] > > Are you referring to the web interface? Yes, I follow devel with it, subscribing overwhelms my box. >I always go in through the > search engine. Once I find an article in the right thread, if I click > the subject, I get a new view using

Re: r19659 - /lyx-devel/trunk/src/frontends/qt4/ui/CitationUi.ui

Abdelrazak Younes [EMAIL PROTECTED] writes: [...] Jean-Pierre, if you have problem with Qt, then I suggest to report this to the Qt-interest mailing list. There is a news interface too. My experience is that they are pretty responsive. Sure, I'm already in the process of subscribing.

Re: r19659 - /lyx-devel/trunk/src/frontends/qt4/ui/CitationUi.ui

Abdelrazak Younes <[EMAIL PROTECTED]> writes: [...] > > Jean-Pierre, if you have problem with Qt, then I suggest to report this > to the Qt-interest mailing list. There is a news interface too. My > experience is that they are pretty responsive. Sure, I'm already in the process of

OPenin a 1.5 doc fails with lyx-1.4.5, lyx2lyx works

Hello, While creating a lyx template for ifac conferences, I had this behaviour: - build the layout and template for 1.4.5 - upgrade the layout for 1.5, read the template and save with 1.5.1 At this stage I have a 1.5 compatible layout and template. When I try to reopen the template with

OPenin a 1.5 doc fails with lyx-1.4.5, lyx2lyx works

Hello, While creating a lyx template for ifac conferences, I had this behaviour: - build the layout and template for 1.4.5 - upgrade the layout for 1.5, read the template and save with 1.5.1 At this stage I have a 1.5 compatible layout and template. When I try to reopen the template with

Re: LyX tables dont compile.

Anders Ekberg [EMAIL PROTECTED] writes: [... I get a LaTex error already with test.lyx (on 1.5.1 on Mac PPC): LaTeX Error: Command \Telefon already defined. with the details: \newcommand\Telefon{\mvchr{84}} Your command was ignored. Type I command return to replace it with another

Re: LyX tables dont compile.

Anders Ekberg <[EMAIL PROTECTED]> writes: [... > > > I get a LaTex error already with test.lyx (on 1.5.1 on Mac PPC): > > LaTeX Error: Command \Telefon already defined. > > with the details: > > \newcommand\Telefon{\mvchr{84}} > Your command was ignored. > Type Ito replace it with another

Re: [Feature request] export to openoffice

Jürgen Spitzmüller [EMAIL PROTECTED] writes: Richard Heck wrote: You can also just use `oolatex'---at least on Linux. However, TeXLive 2007 does not ship the oolatex script. Therefore I'd prefer the verbose command. Right, it's up to the user to create oolatex and friends with mk4ht.

Re: [PATCH] export to openoffice

Richard Heck [EMAIL PROTECTED] writes: Jean-Pierre Chrétien wrote: [..] OK, thanks. Does this sound good to other people? If so, I'll commit the change. There is a problem of return signal with mk4ht :-( I recommended the syntax because I mostly use it from a shell for tex4ht testing

Re: [Feature request] export to openoffice

Jürgen Spitzmüller <[EMAIL PROTECTED]> writes: > > Richard Heck wrote: > > You can also just use `oolatex'---at least on Linux. > > However, TeXLive 2007 does not ship the oolatex script. Therefore I'd prefer > the verbose command. Right, it's up to the user to create oolatex and friends with

Re: [PATCH] export to openoffice

Richard Heck <[EMAIL PROTECTED]> writes: > > Jean-Pierre Chrétien wrote: [..] > > > OK, thanks. Does this sound good to other people? If so, I'll commit the > change. There is a problem of return signal with mk4ht :-( I recommended the syntax because I mostly use it

Re: w2l parameters (odt-lyx)

Pavel Sanda [EMAIL PROTECTED] writes: [...] it starts to import, however i'm not sure whether this is the correct solution because intermediate .tex file remain in the current directory. did the previous parameter worked for you or is this bug ? Here on Solaris w2l 0.5b2 works like w2l

Re: w2l parameters (odt->lyx)

Pavel Sanda <[EMAIL PROTECTED]> writes: [...] > > it starts to import, however i'm not sure whether this is the correct > solution because intermediate .tex file remain in the current directory. > > did the previous parameter worked for you or is this bug ? Here on Solaris w2l 0.5b2 works like

Re: Elsart class complex frontmatter

Darren Freeman [EMAIL PROTECTED] writes: On Wed, 2007-07-25 at 07:28 +0100, José Matos wrote: On Wednesday 25 July 2007 06:41:38 Jürgen Spitzmüller wrote: You have to set OptionalArgs1 in the style definitions (in the layout file), then you can use Insert-Short Title.

Re: Elsart class complex frontmatter

Darren Freeman <[EMAIL PROTECTED]> writes: > > On Wed, 2007-07-25 at 07:28 +0100, José Matos wrote: > > On Wednesday 25 July 2007 06:41:38 Jürgen Spitzmüller wrote: > > > You have to set > > > OptionalArgs1 > > > in the style definitions (in the layout file), then you can use > > >

Re: plastex

Neal Becker [EMAIL PROTECTED] writes: Not sure how this could be of use, but it certainly looks interesting: http://plastex.sourceforge.net/ Sure, as it has a parser included. Tried it on a tex export of example_lyxified.lyx, doesnt't seem to like babel however... -- Jean-Pierre

Re: plastex

Neal Becker <[EMAIL PROTECTED]> writes: > > Not sure how this could be of use, but it certainly looks interesting: > > http://plastex.sourceforge.net/ > > Sure, as it has a parser included. Tried it on a tex export of example_lyxified.lyx, doesnt't seem to like babel however... --

Re: Assertion when leaving LyX

Jean-Pierre Chrétien [EMAIL PROTECTED] writes: you have to use --with-qt4-dir Thanks for pointing this out, but it does make a change. I meant it does not make a change, sorry -- Jean-Pierre

Re: Exception when opening Document-settings on Solaris

Pavel Sanda [EMAIL PROTECTED] writes: are you sure you havent frontend_helpers.cpp patched by some previous work ? looking into source i dont see how this can happen. I might have messed things up, but I'm pretty sure. I applied Enrico's last patch (try/catch solution) with success.

Re: Assertion when leaving LyX

Jean-Pierre Chrétien <[EMAIL PROTECTED]> writes: > > > > you have to use --with-qt4-dir > > Thanks for pointing this out, but > it does make a change. > I meant it does not make a change, sorry -- Jean-Pierre

Re: Exception when opening Document->settings on Solaris

Pavel Sanda <[EMAIL PROTECTED]> writes: > > are you sure you havent frontend_helpers.cpp patched by some previous > work ? looking into source i dont see how this can happen. I might have messed things up, but I'm pretty sure. > > > I applied Enrico's last patch (try/catch solution) with

Re: Exception when opening Document-settings on Solaris

Jürgen Spitzmüller [EMAIL PROTECTED] writes: José Matos wrote: OK then. Enrico earlier agreed with this and then we will have more time to fix this properly. Done. I've also reopened the bug report with a comment. I updated from svn on July 17 evening, and the GCC3 bug is still there.

Re: Assertion when leaving LyX

Jean-Pierre Chrétien [EMAIL PROTECTED] writes: Abdelrazak Younes younes.a at ... writes: [...] We need the full context to help you. Please recompile in debug mode and send us the full backtrace. [...] That's all what I get With this problem, I can't use lyx in production

Re: Assertion when leaving LyX

Jürgen Spitzmüller [EMAIL PROTECTED] writes: Jean-Pierre Chrétien wrote: Here are the conditions: env LD_OPTIONS=-R/usr/local/lib ./configure \ --with-version-suffix=-$VERS \ --with-frontend=qt4 --with-qt-dir=/usr/local/qt-4.2.1 \ you have to use --with-qt4-dir Thanks

Re: Exception when opening Document->settings on Solaris

Jürgen Spitzmüller <[EMAIL PROTECTED]> writes: > > José Matos wrote: > > OK then. Enrico earlier agreed with this and then we will have more time to > > fix this properly. > > Done. I've also reopened the bug report with a comment. I updated from svn on July 17 evening, and the GCC3 bug is

Re: Assertion when leaving LyX

Jean-Pierre Chrétien <[EMAIL PROTECTED]> writes: > > Abdelrazak Younes ...> writes: > [...] > > > > We need the full context to help you. Please recompile > > in debug mode and > > send us the full backtrace. [...] > > That's all what I get

Re: Assertion when leaving LyX

Jürgen Spitzmüller <[EMAIL PROTECTED]> writes: > > Jean-Pierre Chrétien wrote: > > Here are the conditions: > > > > env LD_OPTIONS=-R/usr/local/lib ./configure \ > > --with-version-suffix=-$VERS \ > > --with-frontend=qt4 --with-qt-dir=/usr/local/qt-4

tex2lyx segfaults on Solaris

Solaris again... Create a simple file with lyx-svn (as of July 11), say tex2lyx.tex Export as latex and reimport in lyx: (gdb) ... Starting program: /usr/local/bin/tex2lyx-svn tex2lyx.tex [New LWP 1] [New LWP 2] [New LWP 3] [New LWP 4] Program received signal SIGSEGV, Segmentation fault.

Re: Assertion when leaving LyX

Jean-Pierre Chrétien [EMAIL PROTECTED] writes: Solaris again, here is what I get when I leave LyX. Not much boring, but... ^^^ Perfectly boring, sorry: happens when I close a doc (an thus when I revert to saved version), when

Re: Assertion when leaving LyX

Abdelrazak Younes [EMAIL PROTECTED] writes: [...] We need the full context to help you. Please recompile in debug mode and send us the full backtrace. Here are the conditions: env LD_OPTIONS=-R/usr/local/lib ./configure \ --with-version-suffix=-$VERS \ --with-frontend=qt4

tex2lyx segfaults on Solaris

Solaris again... Create a simple file with lyx-svn (as of July 11), say tex2lyx.tex Export as latex and reimport in lyx: (gdb) ... Starting program: /usr/local/bin/tex2lyx-svn tex2lyx.tex [New LWP 1] [New LWP 2] [New LWP 3] [New LWP 4] Program received signal SIGSEGV, Segmentation fault.

Re: Assertion when leaving LyX

Jean-Pierre Chrétien <[EMAIL PROTECTED]> writes: > > > Solaris again, here is what I get when I leave LyX. Not much boring, but... ^^^ Perfectly boring, sorry: happens when I close a doc (an thus when I revert t

Re: Assertion when leaving LyX

Abdelrazak Younes <[EMAIL PROTECTED]> writes: [...] > > We need the full context to help you. Please recompile > in debug mode and > send us the full backtrace. Here are the conditions: env LD_OPTIONS=-R/usr/local/lib ./configure \ --with-version-suffix=-$VERS \ --with-frontend=qt4

Re: Exception when opening Document-settings on Solaris

Enrico Forestieri [EMAIL PROTECTED] writes: Yes, this is r18988 striking again :( I don't think that this is related to the platform but rather to the compiler version. I think that gcc 3.x is missing some locale facets. Jean-Pierre, does the attached patch solve the bug for you?

Re: Exception when opening Document->settings on Solaris

Enrico Forestieri <[EMAIL PROTECTED]> writes: > > > Yes, this is r18988 striking again :( > > I don't think that this is related to the platform but rather to the > compiler version. I think that gcc 3.x is missing some locale facets. > > Jean-Pierre, does the attached patch solve the bug for

Exception when opening Document-settings on Solaris

Hello, All is OK with 1.5.0rc2, but with 1.5.0-svn, when I want to edit the settings of a template document on Solaris 2.8/Qt4.3.1, I get this: Caught normal exception: locale::facet::_S_create_c_locale name not valid Program received signal SIGABRT, Aborted. 0xfdf592f0 in __sigprocmask ()

<    3   4   5   6   7   8   9   10   >