Re: Bug report for lyx-1.0.2pre1

1999-04-22 Thread Pawel Dziekonski

On Thu, Apr 22, 1999 at 07:23:34PM +0200, Jean-Marc Lasgouttes wrote:
> > "Pawel" == Pawel Dziekonski <[EMAIL PROTECTED]> writes:
> 
> Pawel> Yes I know ;-) but I've just translated english string to
> Pawel> polish.  I'm not programming in C/C++, but can it be that one
> Pawel> label in other language breaks whole f**cking prog??? 8-O You
> Pawel> know - I'm not using reLyX :-), but sent bug report because
> Pawel> somebody told me that this happens. And it happens also for me,
> Pawel> so it is not only my 'local' problem...
> 
> Since it happens in the code for multiple references in strings
> (i.e. several identical strings are at the same place), it might be
> triggered because in your translation two strings which used to be
> different are now identical. It seems weird, but I cannot think of
> something else...
> 
> JMarc

You are definitely right! I've fixed it in pl.po and now it works OK.

Also I've realized that pl.po in lyx-1.0.2pre1.tgz is the old one (for
1.0.1pre4), not that which I uploded some time ago to
ftp.devel.lyx.org/pub/incoming.  I'm sending new one to you in next message
(not on the lyx-devel list).

best regards, Pawel

-- 
Pawel Dziekonski, call me Dzieko  http://ozon.ch.pwr.wroc.pl/dzieko
email: [EMAIL PROTECTED] | email: [EMAIL PROTECTED]
University of Bristol, ENGLAND  |  Wroclaw University of Technology, POLAND
Physical/Theoretical Chemistry  |   Molecular Modelling Lab



Re: Bug report for lyx-1.0.2pre1

1999-04-22 Thread Jean-Marc Lasgouttes

> "Pawel" == Pawel Dziekonski <[EMAIL PROTECTED]> writes:

Pawel> Yes I know ;-) but I've just translated english string to
Pawel> polish.  I'm not programming in C/C++, but can it be that one
Pawel> label in other language breaks whole f**cking prog??? 8-O You
Pawel> know - I'm not using reLyX :-), but sent bug report because
Pawel> somebody told me that this happens. And it happens also for me,
Pawel> so it is not only my 'local' problem...

Since it happens in the code for multiple references in strings
(i.e. several identical strings are at the same place), it might be
triggered because in your translation two strings which used to be
different are now identical. It seems weird, but I cannot think of
something else...

JMarc



Re: Bug report for lyx-1.0.2pre1

1999-04-22 Thread Pawel Dziekonski

On Thu, Apr 22, 1999 at 12:33:06PM -0400, Amir Karger wrote:
> (2) Dzieko, can you see if things break when you try to set your language
> to, say, french?
No - it works very well:
export LANG=fr
export LC_ALL=fr_FR
lyx
export LANG=de
export LC_ALL=de_DE
lyx
protos:~/lyx-1.0.2pre1/po >rpm -q glibc 
glibc-2.0.7-19
protos:~/lyx-1.0.2pre1/po >rpm -q gettext
gettext-0.10-5

> Also, once you've translated to polish using relyx on the
> command line, are you able to edit etc. normally within lyx?
I'm not sure if I understand you correctly, but
here ya go:

(setup env for polish)
reLyX -f -o . $LYXDIR/reLyX/test.ltx
lyx test.lyx

and everything was all right.

> That is, are we
> sure that it's the "Import LaTeX" popup or some interface with the reLyX
> command that is causing the error? Is it possible that the polish menus
> somehow reference the wrong command? It looks like you translated the menus,
> so you should know :)
Yes I know ;-) but I've just translated english string to polish.
I'm not programming in C/C++, but can it be that one label in other language
breaks whole f**cking prog??? 8-O
You know - I'm not using reLyX :-), but sent bug report because somebody told
me that this happens. And it happens also for me, so it is not only my
'local' problem...

regards, Dzieko

-- 
Pawel Dziekonski, call me Dzieko  http://ozon.ch.pwr.wroc.pl/dzieko
email: [EMAIL PROTECTED] | email: [EMAIL PROTECTED]
University of Bristol, ENGLAND  |  Wroclaw University of Technology, POLAND
Physical/Theoretical Chemistry  |   Molecular Modelling Lab



Re: Bug report for lyx-1.0.2pre1

1999-04-22 Thread Jean-Marc Lasgouttes

> "Dzieko" == Pawel Dziekonski <[EMAIL PROTECTED]> writes:

Dzieko> Hi, I'm using LyX 1.0.2pre1 and it crashes after following
Dzieko> steps: 0. compile and install in very standart way 1. setup
Dzieko> environment to polish localisation: export LANG=pl export
Dzieko> LC_ALL=pl_PL 2. then run it: lyx-1.0.2pre1/src/lyx 3. and try
Dzieko> to do File->Import->Latex

Hello,

Could you try to set a breakpoint in Menus::ShowFileMenu2 and see
exactly at what point the program breaks? The backtrace given by gdb
does not help much... 

JMarc



Re: CVS update: lyx-1_0_x/src

1999-04-22 Thread Jean-Marc Lasgouttes

> "lasgouttes" == lasgouttes  <[EMAIL PROTECTED]> writes:

lasgouttes> Date: Thursday April 22, 1999 @ 18:56 Author: lasgouttes

lasgouttes> Update of /usr/local/lyxsrc/cvsroot/lyx-1_0_x/src In
lasgouttes> directory nazgul.lyx.org:/tmp/cvs-serv14781/src

lasgouttes> Modified Files: LaTeXFeatures.C buffer.C layout.C layout.h
lasgouttes> lyx_sty.C lyxlex.C Log Message: Fix a bad interaction
lasgouttes> between amslatex and makeidx.sty and a bug in the
lasgouttes> initialization of the tags table in layout.C

This fixes two problems:

1/ amsart.cls defines the index commands which makeidx.sty provide, so
we cannot input both together. To solve this, I introduced a new
layout tag ProvidesMakeidx which is set to 1 in amsxxx classes. Doing
that, I discovered that the handling of amsmath.sty was hackish (like
in ``if the class name starts with ams, then it uses amsmath'' %-|)
and added ProviedsAmsmath to solve that in a cleaner way.

2/ Doing that, I discovered that the parsing of layout files did not
work anymore. It turned out that the tag table for lyxlex was
initialized with bad values...

The reason I write all these uninteresting informations is not to tell
you what I did this afternoon, but just to get a couple of you to
actually try out the latest cvs and see whether I broke anything...

JMarc



Re: Bug report for lyx-1.0.2pre1

1999-04-22 Thread Amir Karger

On Wed, Apr 21, 1999 at 10:19:18PM +0100, Pawel Dziekonski wrote:
> 
> On Wed, Apr 21, 1999 at 08:27:57PM +0100, Etienne Grossmann wrote:
> >   Hello,
> >   just to say that importing a .tex file with 1.0.2pre1 does not 
> > crash systematically : here, I just get the perl messages, but the
> > program survives. Both in Polish and English.
> >   Etienne
> > etienne@anonimo: uname -a
> > Linux anonimo 2.0.36 #12 Thu Mar 4 09:08:33 WET 1999 i686 unknown
> 
> I've got strace logs for both cases so if you need them - tell me.
> Dzieko
> 

Well, I wouldn't know what to do with an strace log. So:

(1) can someone who knows what an strace log is try to get some more info
from Dzieko?

(2) Dzieko, can you see if things break when you try to set your language
to, say, french? Also, once you've translated to polish using relyx on the
command line, are you able to edit etc. normally within lyx? That is, are we
sure that it's the "Import LaTeX" popup or some interface with the reLyX
command that is causing the error? Is it possible that the polish menus
somehow reference the wrong command? It looks like you translated the menus,
so you should know :)

(3) Could other people try setting polish to be their language and trying to
import latex documents?

Hm. I don't seem to be doing anything in this scenario. OK, I'll head out
for a beer; let me know if you find anything.

-Amir



docs list

1999-04-22 Thread Mate Wierdl

Sorry guys, I did not have time to do this earlier. 

I just set up the lists

[EMAIL PROTECTED]
[EMAIL PROTECTED]

Subscribe the usual way: 

echo | mail [EMAIL PROTECTED] 
echo | mail [EMAIL PROTECTED]


The list is archived; when you subscribe, you'll get instructions how
to retrieve messages.

www archive is at 

http://www.mail-archive.com/lyx-docs@lists.lyx.org

Problems:

[EMAIL PROTECTED]


Mate



Re: Compile error for lyx-1.0.2pre1

1999-04-22 Thread Jean-Marc Lasgouttes

> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:

Angus> ps I'll take the opportunity to report that the math_iter.C
Angus> optimization problem on Alphas running OSF/1 (and presumably
Angus> Linux Alpha) still exists when the code is compiled with
Angus> egcs-1.1.2.  A.

:(

I really do not know how to solve this. It is really unfortunate...

JMarc



Re: Compile error for lyx-1.0.2pre1

1999-04-22 Thread Angus Leeming

Many thanks, Jean-Marc. Problem solved.
Angus

ps I'll take the opportunity to report that the math_iter.C optimization
problem on Alphas running OSF/1 (and presumably Linux Alpha) still exists when
the code is compiled with egcs-1.1.2.
A.

On Thu, 22 Apr 1999, you wrote:
> Hello,
> 
> This bug is already fixed in cvs. Basically, change at line 403 of
> insetbib.C
>   while (! feof(file)) {
> to
>   while (! feof(file())) {
> 
> This is an obscure interaction in the definition of feof() as a macro
> on OSF/1.
> 
> JMarc



Re: Compile error for lyx-1.0.2pre1

1999-04-22 Thread Jean-Marc Lasgouttes

> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:

Angus> Hi!  compiling lyx-1.0.2pre1 on a Dec Alpha OSF/1 v3.2 with
Angus> egcs-1.1.2 fails with:

Angus> g++ -c -g -O2 -I. -I. -I../images insetbib.C insetbib.C: In
Angus> method `class LString InsetBibtex::getKeys()': insetbib.C:403:
Angus> base operand of `->' has non-pointer type `FilePtr' make: ***
Angus> [insetbib.o] Error 1

Hello,

This bug is already fixed in cvs. Basically, change at line 403 of
insetbib.C
while (! feof(file)) {
to
while (! feof(file())) {

This is an obscure interaction in the definition of feof() as a macro
on OSF/1.

JMarc



Compile error for lyx-1.0.2pre1

1999-04-22 Thread Angus Leeming

Hi!
compiling lyx-1.0.2pre1 on a Dec Alpha OSF/1 v3.2 with egcs-1.1.2 fails with:

g++ -c -g -O2 -I. -I. -I../images   insetbib.C
insetbib.C: In method `class LString InsetBibtex::getKeys()':
insetbib.C:403: base operand of `->' has non-pointer type `FilePtr'
make: *** [insetbib.o] Error 1

Can you help?
Best wishes,
Angus

ps please reply direct; I'm not subscribed.



Re: Documentation Style Sheet, v2.0

1999-04-22 Thread Jean-Marc Lasgouttes

> "John" == John Weiss <[EMAIL PROTECTED]> writes:

John> Attached is the completed, new version of the LyX Documentation
John> Style Sheet.  Every documenter should read the new version
John> immediately.  The current LyX DocTeam should comb the primary
John> manuals for violations, things that do not conform to the new
John> Style Sheet.  All violations should be fixed.

And what should we do wih the violators? Report their names to you, so
that you can take appropriate action? 

It seems the documentation police will be pretty active in the next
days... :)

JMarc

PS: I commited the update to cvs. You did not ask for it, but I guess
it was the intent.