> "Michal" == Michal Kara <[EMAIL PROTECTED]> writes:
Michal> That was it. I had libc5 version of XForms sitting on
Michal> "priviledged" place. Linker even gives warning about that,
Michal> but I did make; make install, so I didn't see it :( Anyway, it
Michal> is strange, that it worked
On Wed, 16 Jun 1999, Asger Alstrup Nielsen wrote:
> So it's time to dig out the old documents about the EBNF proposal, and
> reread those. I now see that you don't agree that we should use it for
> parsing, but only for production. I can live with that, but I always
> thought that you disliked th
> Ok, can you give me a deadline? I also saw that 1.1.x uses "string"
> instead of LString and a different syntax for error streams. I have coded
> for 1.1.x, will 1.0.4 be based on that or on the 1.0.3 code?
As Jean-Marc noticed, 1.0.4 will be based on the 1.0.3 code (or specifically,
on the ly
> My suggestion, outlined here several years ago, was to remove completely
> the writting methods from insets, but all insets would have an id key so
> the specific document language writer would get a syntax definition and
> write the corresponding code. Of course the inset still has to
> give i
> I considered several possible solutions, but all have their drawbacks.
>
> First note, using the present implementation is possible to write a lyx
> file that gives this result without any ERT (lyx jargon ;-).
> But both and should be empty environments with the
> other and nested i
> My code modifications consist of the file linked_list.h, that I attach to
> this mail, and the following changes:
The linked_list.h file is missing.
I had a quick look at the patch, and could not see what is wrong.
Maybe you could try to generate a complete, cleaned up patch with the makepatc
> Docs seem to indicate that somebody out of frustration - instead of
> checking available tools - re-invented, in a form of 'chktex', a long
> existing - for years and years, predating initial versions of LyX -
> and well working wheel known as 'lacheck' and that LyX team is not aware
> of that.
> Michal> Hello all! I have upgraded from LyX 1.0.2 to 1.0.3, using
> Michal> source package. I used configure, make, make install. No
> Michal> other change, no problem. But when I run LyX, it gives message
> Michal> "LyX wasn't able to find its layout descriptions" in dialog
> Michal> box
Hi Michael,
I've incorporated your changes for alpha into my relocatable package
spec file.
Here is the new version:
LyX spec file
---Kayvan
--
Kayvan Aghaiepour Sylvan | Proud husband of | Father to my kids:
Sylvan Associates, Inc. | Laura Isabella Sylvan
Jean-Marc Lasgouttes escribió:
> > "Edgardo" == Edgardo Szulsztein <[EMAIL PROTECTED]> writes:
>
> Edgardo> Hi Excuse my english, I'm a Spanish speaker :-)
>
> Hello,
>
> Don;t worry, we are a lot of non-english speakers around here ;)
>
> Edgardo> I'm using the lyx processor to write my thes
On Tue, 15 Jun 1999 12:59:28 +0200, Asger Alstrup Nielsen wrote:
> LString sh = "";
>
>is sub-optimal. Just do
>
> LString sh;
>
>LString is default constructible, and defaults to the empty string.
AAhh, yes:
I see, C++ is so much more intelligent than C. Unfortunately I've no
ide
On 15 Jun 1999, Lars Gullik Bjønnes wrote:
> Stop looking to hard at the code in 1.0.x, it has been removed in
> 1.1.x.
OK, I'll wait for your (thought) comments about a new inset model.
Alejandro
Alejandro Aguilar Sierra <[EMAIL PROTECTED]> writes:
| On Tue, 15 Jun 1999, Jose Abilio Oliveira Matos wrote:
| > InsetLatex is the only exception as I think it is completly obsolete.
|
| I agree. Why it has not been removed?
Stop looking to hard at the code in 1.0.x, it has been removed in
1.
On Tue, 15 Jun 1999, Jose Abilio Oliveira Matos wrote:
> Although I agree with you in several points I should say that, here,
> almost all the cases where the definition is empty are used as
> placeholders for future improvement.
I don't like it but it's not your fault. Finally we are discussin
On Tue, 15 Jun 1999, Asger Alstrup Nielsen wrote:
> Some time ago, we did discuss this problem briefly. I proposed that we
> had only one method for all writers, but that it was kept inside the
> Insets. The improvement compared to now is that we don't have to
> introduce a new method for a new
> Richard> oh, well. I though someone fixed it a few months ago, and
> Richard> figured it had krept back in.
> What I fixed recently is that any inset matched a space in
> Find/Replace.
awe :(
> Richard> I had to fight with this for the mailmerge, too. iirc, it
> Richard> was a matter of
On Tue, Jun 15, 1999 at 04:12:57PM +0200, Asger Alstrup Nielsen wrote:
[...]
> > I tried to mimic the latex counterpart in those cases...
>
> As Jean-Marc pointed out, there is probably no bug there after all. I was
> mistaken, and you did the right thing.
Ok.
Warning: from here it follow pos
"Asger Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| On the other hand, exceptions are not easy to emulate, so I think we should
| avoid using those.
Well, I don't agree. (I agree as for now).
But we need to be very concious about using eceptions, it is not
something you just throw in.
Much
After some e-mail discussions with Jean-Marc Lasgoutt and Allan Rae
(thanks, guys!) it transpired that I should read more of INSTALL
file and that 'lyx.spec' file supplied with lyx-1.0.3 is basically
broken.
A general problem with it, beyond a wrong version number, is that it
has BUGS file is li
> > I found a few easy bugs in InsetLabel::DocBook. It should not return 0, but
the
> > width of the string.
>
> I tried to mimic the latex counterpart in those cases...
As Jean-Marc pointed out, there is probably no bug there after all. I was
mistaken, and you did the right thing.
> The header
> Yes, -malign-jumps=4 -malign-functions=4 is what any i486 really needs.
>
> I like the 20% smaller executable; a performance change isn't so
> obvious on my old box (classic pentium). Your mileage may differ.
When it comes to executable size, you save a lot more in LyX 1.0.x by adding
the flag
On 15 Jun 1999 06:44:07 +0900, [EMAIL PROTECTED] wrote:
>> limited testing. Its fast. Only the old inline image bug seems to
>> remain here.
>
>As far as I remember, the last report of yours suggested it was really
>a bug in the temporary path handling in LyX. Will you please send
>the output of
On 15 Jun 1999 06:44:28 +0900, [EMAIL PROTECTED] wrote:
>> No, the problem is upper/lower case difference in:
>> if (!sh.contains("sh") && !sh.contains("SH"))
>
>Thanks for finding the bug. But you have to use lowercase() here.
>Consider "Cmd", "Sh" etc.
Well, it may even
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> Hmmm, are you sure? I thought those methods were supposed to return
>> a number of newlines, not a number of characters. Besides, if we
>> want the width of the string, we can get it by reading the string
>> itself.
Asger> No,
> Hmmm, are you sure? I thought those methods were supposed to return a
> number of newlines, not a number of characters. Besides, if we want
> the width of the string, we can get it by reading the string itself.
No, I'm not sure. I probably had a temporary cerebral haemorrhage. Sorry.
Greets,
> "Andre'" == Andre' Poenitz <[EMAIL PROTECTED]> writes:
Andre'> lyx/po/Makefile contains the line 35
Andre'> XGETTEXT = PATH=../src:$$PATH cp ${srcdir}/lyx.pot
Andre'> ./${PACKAGE}.po ; :
Andre'> which looks a bit odd. The same line is contained in
Andre'> lyx/po/Makefile.in and the XGETTE
Asger Alstrup Nielsen writes:
> > I have ported the docbook support to a recent CVS, without
> > Juergen's last patch, but as I don't touch that file, there should
> > be no problem.
>
> Fantastic!
>
> I found a few easy bugs in InsetLabel::DocBook. It should not return 0, but the
> wid
> If you check the File (Fichero) menu everything works...
>
> but if you have a document opened, and leiter you check the File menu,
> you find it in English!
>
> This is happening to the Catalan version that I'm doing, also.
>
> But in the French version everithing seems OK.
>
> Does anybod
> Hmm.. that's the only thing I disliked. Having to write a new method for
> every new document language we want to export, and most times to do
> nothing (as with most insets in this case), reflect a not exactly smart
> design... of the current inset model.
I agree that this is bad design, but w
> I would like to know how to submit a new version of LyX, with the Catalan
> language included...
Just attach the po-file, and any translated documents, to a mail to this list,
or alternatively, put them up on the web and post the link here. I'm sure
someone (such as the ever diligent Jean-Mar
> Because of this I changed in the file buffer.C, the function
> getReferenceList. Instead of just add LStrings to the list variable, I
> use an ordered linked list to store the references, then I copy them
> to the list variable. It works fine. However, the program causes a
> Segmentation faut
> // OS/2 cmd.exe has another use for '&'
> if (!wait) {
> LString sh = "";
> sh = getenv("EMXSHELL");
> if (sh.empty())
> sh = getenv("COMSPEC");
>
Alejandro Aguilar Sierra writes:
> On Mon, 14 Jun 1999, Jose Abilio Oliveira Matos wrote:
>
> [..]
> > PS: There are several places where the support could be improved, the
> > support for some of the insets is basic, and since the support for the
> > insets is modular this can be worked l
Once again I followed the instructions given on the
"LyX - getting the source with CVS" - page.
When running make I get the following error:
- snip ---
gcc -c -DLOCALEDIR=\"/usr/X11R6/share/locale\"
-DGNULOCALEDIR=\"/usr/X11R6/share
/locale\" -DLOCALE_AL
> "Jose" == Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes:
Jose> PS: There are several places where the support could be
Jose> improved, the support for some of the insets is basic, and since
Jose> the support for the insets is modular this can be worked later.
Hi!
I am currently c
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> I think we should apply this right away, and get lots of people
Asger> to test it, find the other bugs, and polish the implementation.
Asger> We need to introduce more of the special DocBook environments,
Asger> and documen
> "Edgardo" == Edgardo Szulsztein <[EMAIL PROTECTED]> writes:
Edgardo> Hi Excuse my english, I'm a Spanish speaker :-)
Hello,
Don;t worry, we are a lot of non-english speakers around here ;)
Edgardo> I'm using the lyx processor to write my thesis, and I found
Edgardo> it great (I installed
> "Jean-Marc" == Jean-Marc Lasgouttes writes:
Kayvan> I'll abide by the group's decision and create RH 6.0 packages
Kayvan> with whatever the official spec file is. I'll continue using
Kayvan> my /usr-based spec file myself. ;-)
Jean-Marc> It would be nice to make sure that the rpm is
Jean-M
On 15-Jun-99 Asger Alstrup Nielsen wrote:
>
> I found a few easy bugs in InsetLabel::DocBook. It should not return 0, but the
> width of the string. Similar in InsetLatex::DocBook,
> InsetLatexAccent::DocBook, InsetQuotes::DocBook, InsetRef::DocBook,
> InsetSpecialChar::DocBook, InsetTOC::DocBo
> "Francesc" == Francesc Burrull i Mestres <[EMAIL PROTECTED]> writes:
Francesc> Hi, I'm doing the Catalan version, and I have a problem that
Francesc> I detected in the spanish version too.
Francesc> When: export LANG=es; lyx&
Francesc> appears LyX in Spanish.
Francesc> If you check the F
> "Francesc" == Francesc Burrull i Mestres <[EMAIL PROTECTED]> writes:
Francesc> Hi, I would like to know how to submit a new version of LyX,
Francesc> with the Catalan language included...
Just send the po file (gzipped and encoded, so that no information is
lost) to the list (or to me). Or
> "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes:
Richard> jmarc jmentioned,
>> > "Richard" == Richard E Hawkins <[EMAIL PROTECTED]>
>> writes:
>>
Richard> I found that I had several loose spaces before commas. I
Richard> tried to use find/replace to replace " ," with ",", bu
> "Michal" == Michal Kara <[EMAIL PROTECTED]> writes:
Michal> Hello all! I have upgraded from LyX 1.0.2 to 1.0.3, using
Michal> source package. I used configure, make, make install. No
Michal> other change, no problem. But when I run LyX, it gives message
Michal> "LyX wasn't able to fin
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> I have ported the docbook support to a recent CVS, without
>> Juergen's last patch, but as I don't touch that file, there should
>> be no problem.
Asger> Fantastic!
Asger> I found a few easy bugs in InsetLabel::DocBook. It sh
> I have ported the docbook support to a recent CVS, without
> Juergen's last patch, but as I don't touch that file, there should
> be no problem.
Fantastic!
I found a few easy bugs in InsetLabel::DocBook. It should not return 0, but the
width of the string. Similar in InsetLatex::DocBook,
Ins
45 matches
Mail list logo
