hi,
ok, i'm still using lyx 1.0.1, which is a bit outdated, but maybe the
bug is present in newer versions also. it is easy to reproduce:
C-m ^ k [<-] [<-] \ a [BS] [BS]
^ Crash here
^ Cursor left^ Display goes weird here
it takes about a second, the
A new italian dictionary for ispell is at
ftp://ftp.pluto.linux.it/pub/pluto/ildp/apps/ispell/
Claudio
--
Visit my home page http://www.geocities.com/Paris/Lights/8645/
---
Do you want really WRITE your document ?? Just use LyX on
PS. Sorry if htis got cross posted to the users list!
I am happy to hear LyX 1.0.4 is out. Thanks to all for great work.
I have been interested in the DocBook support, and I understand it needs
sgml-tools v2.0. I use Red Hat, thus RPM. Can anyone tell me where to find
sgml-tools 2.0 RPMS? Or
On Wed, Sep 29, 1999 at 08:59:47PM +0200, Lars Gullik Bjønnes wrote:
>
> Finally we have LyX version 1.0.4 ready.
>
> [...]
>
> We will put binary packages on ftp.lyx.org when we get them.
Hi Lars,
Here are the binary packages:
ftp://ftp.sylvan.com/pub/lyx/lyx-1.0.4-1.i386.rpm
Finally we have LyX version 1.0.4 ready.
Highlights for this release:
- several bugfixes.
- DocBook support
- new layouts
- better handling of custom pagesizes.
- more document files translated to other languages.
See CHANGES in the distribution for ever
On 29 Sep 1999, Lars Gullik Bjønnes wrote:
> Does -fno-exceptions and -fno-rtti work with gcc 2.7.x
cc1: Invalid option `-fno-exceptions'
> Or do you mean that we should not even _think_ about doing this for
> 1.0.4?
Yes, that's what I mean.
Alejandro
Alejandro Aguilar Sierra <[EMAIL PROTECTED]> writes:
| > Will it work both for egcs g++ 2.7 and g++ 2.95?
|
| IMHO 1.0.4 should be as easy to compile and with the same compilers as
| 1.0.3.
_That_ was not the question.
Does -fno-exceptions and -fno-rtti work with gcc 2.7.x
Or do you mean tha
On 29 Sep 1999, Lars Gullik Bjønnes wrote:
> Do we really want to compile 1.0.4 with exceptions and rtti turned on?
>
> Where/What do we have to change to turn this off for g++?
>
> Will it work both for egcs g++ 2.7 and g++ 2.95?
IMHO 1.0.4 should be as easy to compile and with the same comp
Do we really want to compile 1.0.4 with exceptions and rtti turned on?
Where/What do we have to change to turn this off for g++?
Will it work both for egcs g++ 2.7 and g++ 2.95?
Lgb
On Wed, 29 Sep 1999, Jose Abilio Oliveira Matos wrote:
> It seems to me that this need further thought, so I have delayed this for
> a later version. So for now all the quotes are translated as english quotes.
> As it seems to me the neutral style.
>
> There are several output results that
On Wed, Sep 29, 1999 at 04:32:10PM +0100, Horst G Kausch wrote:
>
> Just to clarify my previous comments on double quotes in docbook:
>
> As far as I could see the type of quotes used (at least in the docbook
> class) is not determined by the document language. I inserted different
> types of qu
On Wed, 29 Sep 1999, Jose Abilio Oliveira Matos wrote:
> It fix some quotes issues, for now all the quotes are english quotes,
> as soon as I understand the specific issues related with each language,
> I will change the present scheme.
>
> For future versions I will pass the document lan
On Wed, Sep 29, 1999 at 04:40:02PM +0200, Lars Gullik Bjønnes wrote:
> Juergen Vigna <[EMAIL PROTECTED]> writes:
>
> | - did you get updated po files for the various language translations?
>
> Only for polish. But I will not wait for others.
>
> | - did you try to load the docbook_example.lyx f
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| Juergen> Right again so let's start :)
|
| I guess we should realse a version with new directory structure and
| new strings first. Wasn't this the plan?
Yes.
I thimk we should switch to the debugstream as well.
but we will have a release bef
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| Instead, we should have "string toString(int);"
Wa already have that in lstrings.h.
string tostr(int);
Lgb
Juergen Vigna <[EMAIL PROTECTED]> writes:
| - did you get updated po files for the various language translations?
Only for polish. But I will not wait for others.
| - did you try to load the docbook_example.lyx file? I think we should
| try to fix the problem with the figure not loading in th
Uwe> Another point is
Uwe> cross-platform availability for both Linux/Unix and Win32.
Just a quick remark on this: The support is there, so that FLTK
applications *wrok* on Win32, but they are not nice Win32 applications.
They do not behave like other applications on Win32, and I find that
subop
> "Uwe" == Uwe Walschus <[EMAIL PROTECTED]> writes:
Uwe> Hello, I'm not a developer and so it's easy for me to give the
Uwe> following advice: How about switching the GUI toolkit which LyX
Uwe> is build on from XForms to FLTK ? FLTK (http://www.fltk.org) is
Uwe> LGPL-ed, and even more, it pro
Hello,
I'm not a developer and so it's easy for me to give the following
advice:
How about switching the GUI toolkit which LyX is build on from XForms to
FLTK ? FLTK (http://www.fltk.org) is LGPL-ed, and even more, it provides
some kind of XForms- compatibility through a alternative xforms.h (but
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
Juergen> On 28-Sep-99 Jean-Marc Lasgouttes wrote:
>> Two things:
>>
>> 1/ 0.89 is ot out for all architectures and is probably a bit
>> unstable now.
>>
Juergen> You're right, but by the time we are finished with lyx-devel
Juergen> a
> I just did a checkout of the std:string lyx-devel tree and compile it.
> I got an error in paragraph.C as the function operator+(int) is private
> in lyxstring.h and is not implemented. What should we do? Remove the
> string + int call in paragraph.C or implement as public operator+(int)
> in l
Hi!
I just did a checkout of the std:string lyx-devel tree and compile it.
I got an error in paragraph.C as the function operator+(int) is private
in lyxstring.h and is not implemented. What should we do? Remove the
string + int call in paragraph.C or implement as public operator+(int)
in lyxstri
22 matches
Mail list logo
