Am Freitag, 3. Dezember 2004 22:42 schrieb Rainer Dorsch:
- When I append a row in a tabular, LyX adds an additional hline, when
the
cursor is in the last row (which I usually have to remove again). This
is a
usability issue. Or did I miss something. If not, should I enter this
as a
Am Freitag, 3. Dezember 2004 22:42 schrieb Rainer Dorsch:
> - When I append a row in a tabular, LyX adds an additional hline, when
the
> cursor is in the last row (which I usually have to remove again). This
is a
> usability issue. Or did I miss something. If not, should I enter this
as a
>
Hello,
I am wondering since a while about these two issues:
- When I append a row in a tabular, LyX adds an additional hline, when the
cursor is in the last row (which I usually have to remove again). This is a
usability issue. Or did I miss something. If not, should I enter this as a
Hello,
I am wondering since a while about these two issues:
- When I append a row in a tabular, LyX adds an additional hline, when the
cursor is in the last row (which I usually have to remove again). This is a
usability issue. Or did I miss something. If not, should I enter this as a
"Asger K. Alstrup Nielsen" [EMAIL PROTECTED] writes:
| On 9 Jan 2001, Lars Gullik Bjnnes wrote:
|
| I will remove () that has no value when I see them.
|
| - two points:
|- () without meaning kindo shows that the coder does not know the
| precedence rules
|
| I'm sure you
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| On 9 Jan 2001, Lars Gullik Bjønnes wrote:
|
| > I will remove () that has no value when I see them.
| >
| > - two points:
| > - () without meaning kindo shows that the coder does not know the
| > precedence rules
|
| I'm
On Mon, Jan 08, 2001 at 05:07:32PM +0100, Jean-Marc Lasgouttes wrote:
What about the fact that keyword are in mixed-case? Is this considered
good xml practice? I seem to remember that xml is case-sensitive.
Since we just changed the new tabular format, and we have two read methods
for the new
"Dekel" == Dekel Tsur [EMAIL PROTECTED] writes:
Dekel On Mon, Jan 08, 2001 at 05:07:32PM +0100, Jean-Marc Lasgouttes
Dekel wrote:
What about the fact that keyword are in mixed-case? Is this
considered good xml practice? I seem to remember that xml is
case-sensitive.
Dekel Since we just
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| "Dekel" == Dekel Tsur [EMAIL PROTECTED] writes:
|
| Dekel On Mon, Jan 08, 2001 at 05:07:32PM +0100, Jean-Marc Lasgouttes
| Dekel wrote:
| What about the fact that keyword are in mixed-case? Is this
| considered good xml practice? I seem to
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes:
Lars I think we should go for lowercase.
I think so... Now, who will do the change if Juergen is not available?
JMarc
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| "Lars" == Lars Gullik Bjnnes [EMAIL PROTECTED] writes:
|
| Lars I think we should go for lowercase.
|
| I think so... Now, who will do the change if Juergen is not available?
should be easy enough.. .I'll do it.
Lgb
On Mon, Jan 08, 2001 at 05:07:32PM +0100, Jean-Marc Lasgouttes wrote:
> What about the fact that keyword are in mixed-case? Is this considered
> good xml practice? I seem to remember that xml is case-sensitive.
Since we just changed the new tabular format, and we have two read methods
for the
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> On Mon, Jan 08, 2001 at 05:07:32PM +0100, Jean-Marc Lasgouttes
Dekel> wrote:
>> What about the fact that keyword are in mixed-case? Is this
>> considered good xml practice? I seem to remember that xml is
>> case-sensitive.
Dekel>
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
|
| Dekel> On Mon, Jan 08, 2001 at 05:07:32PM +0100, Jean-Marc Lasgouttes
| Dekel> wrote:
| >> What about the fact that keyword are in mixed-case? Is this
| >> considered good xml
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> I think we should go for lowercase.
I think so... Now, who will do the change if Juergen is not available?
JMarc
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> I think we should go for lowercase.
|
| I think so... Now, who will do the change if Juergen is not available?
should be easy enough.. .I'll do it.
Lgb
On 08-Jan-2001 Dekel Tsur wrote:
On Mon, Jan 08, 2001 at 05:15:10PM +0100, Juergen Vigna wrote:
Also, in the new format, the numbers are negative (e.g. endfoot="-3"). Is this
intentional ?
Yes it is intentional!
What is the difference between positive and negative value ?
There was a
Here it is (I also fixed the first problem).
I don't know why you didn't leave the int-reading-routine as it was.
Are you sure that strToint("123abc") == 123? Is this defined? I really
No, strToint("123abc") = 0.
would like to have this!
Why ?
On Tue, Jan 09, 2001 at 09:27:30AM +0100, Juergen Vigna wrote:
What is the difference between positive and negative value ?
There was a limitation before in this stuff and it was if the bottom line
should be added to the row or not. So I thought that we could decide this
So store this
On 09-Jan-2001 Dekel Tsur wrote:
would like to have this!
Why ?
Well good question #:O). Is because I coded it reason enough, hmmm, dada,
I guess not ;)
I'll apply your patch!
What would you say to write bools as "true"/"false" instead of "1"/"0"?
Jrgen
--
On 09-Jan-2001 Dekel Tsur wrote:
There was a limitation before in this stuff and it was if the bottom line
should be added to the row or not. So I thought that we could decide this
So store this information using a different attribute.
Yes, I've to find out (decide) how!
Jrgen
--
On Tue, Jan 09, 2001 at 11:30:31AM +0100, Juergen Vigna wrote:
Well good question #:O). Is because I coded it reason enough, hmmm, dada,
I guess not ;)
I'll apply your patch!
Here is a slightly better patch:
getTokenValue(..., int num) will not change num if the call to
getTokenValue(...,
On 09-Jan-2001 Dekel Tsur wrote:
Here is a slightly better patch:
getTokenValue(..., int num) will not change num if the call to
getTokenValue(..., tmp) returned false.
I already applied the other patch :( and did already modify the source
so I cannot safely apply the patch. Could you
On 09-Jan-2001 Dekel Tsur wrote:
Here is a slightly better patch:
getTokenValue(..., int num) will not change num if the call to
getTokenValue(..., tmp) returned false.
Don't bother to send a patch I already did this in a other way as
I need also to translate the strings to different
On Tue, Jan 09, 2001 at 12:33:39PM +0100, Juergen Vigna wrote:
On 09-Jan-2001 Dekel Tsur wrote:
Here is a slightly better patch:
getTokenValue(..., int num) will not change num if the call to
getTokenValue(..., tmp) returned false.
I already applied the other patch :( and did
On 09-Jan-2001 Dekel Tsur wrote:
Here are the changes from the previous patch.
Well thanks I did it already (a bit different). One thing I noticed and
I would ask you to not do it is remove my () around expressions, that is
my coding style and I like to see them where they are.
Jrgen
Juergen Vigna [EMAIL PROTECTED] writes:
| On 09-Jan-2001 Dekel Tsur wrote:
|
| Here are the changes from the previous patch.
|
| Well thanks I did it already (a bit different). One thing I noticed and
| I would ask you to not do it is remove my () around expressions, that is
| my coding
On 09-Jan-2001 Lars Gullik Bjnnes wrote:
I will remove () that has no value when I see them.
I will add () if I find expressions better to read when I need them.
- two points:
- () without meaning kindo shows that the coder does not know the
precedence rules
da da da
Juergen Vigna [EMAIL PROTECTED] writes:
| On 09-Jan-2001 Lars Gullik Bjnnes wrote:
|
| I will remove () that has no value when I see them.
|
|
| I will add () if I find expressions better to read when I need them.
So that you will be able to parse the above sentence? :-)
| - two
Hi!
I changed the tabular format for the version 1.1.6. This means your not
able anymore to read your 1.1.6 saved tabular if you don't activate the
define in tabular.C (USE_OLD_READFORMAT). If you do this you can read your
old files and write the new format. Obviously you're then not able to
Juergen Vigna [EMAIL PROTECTED] writes:
| Hi!
|
| I changed the tabular format for the version 1.1.6. This means your not
| able anymore to read your 1.1.6 saved tabular if you don't activate the
| define in tabular.C (USE_OLD_READFORMAT). If you do this you can read your
| old files and write
On 09-Jan-2001 Lars Gullik Bjnnes wrote:
Are we compatible with pre2/3?
If not that has to change.
These prereleases were put forward to the general public and to change
the format so that pre cannot be read is not acceptable.
Well nice from you that you come forward now and did not
Juergen Vigna [EMAIL PROTECTED] writes:
| On 09-Jan-2001 Lars Gullik Bjnnes wrote:
|
| Are we compatible with pre2/3?
|
| If not that has to change.
|
| These prereleases were put forward to the general public and to change
| the format so that pre cannot be read is not acceptable.
|
On Tue, Jan 09, 2001 at 08:19:47PM +0100, Lars Gullik Bjnnes wrote:
Well, then I wan tto do this:
- bump version number to "2"
It doesn't make sense to store the tabular format in each tabular.
The global \lyxformat suffices, so I suggest changing the lyxformat to
2.18 and remove the
Dekel Tsur [EMAIL PROTECTED] writes:
| On Tue, Jan 09, 2001 at 08:19:47PM +0100, Lars Gullik Bjnnes wrote:
|
| Well, then I wan tto do this:
| - bump version number to "2"
|
| It doesn't make sense to store the tabular format in each tabular.
| The global \lyxformat suffices, so I
On 08-Jan-2001 Dekel Tsur wrote:
> On Mon, Jan 08, 2001 at 05:15:10PM +0100, Juergen Vigna wrote:
>> > Also, in the new format, the numbers are negative (e.g. endfoot="-3"). Is this
>> > intentional ?
>> Yes it is intentional!
>
> What is the difference between positive and negative value ?
>
> > Here it is (I also fixed the first problem).
>
> I don't know why you didn't leave the int-reading-routine as it was.
> Are you sure that strToint("123abc") == 123? Is this defined? I really
No, strToint("123abc") = 0.
> would like to have this!
Why ?
On Tue, Jan 09, 2001 at 09:27:30AM +0100, Juergen Vigna wrote:
> > What is the difference between positive and negative value ?
> >
>
> There was a limitation before in this stuff and it was if the bottom line
> should be added to the row or not. So I thought that we could decide this
So
On 09-Jan-2001 Dekel Tsur wrote:
>> would like to have this!
>
> Why ?
Well good question #:O). Is because I coded it reason enough, hmmm, dada,
I guess not ;)
I'll apply your patch!
What would you say to write bools as "true"/"false" instead of "1"/"0"?
Jürgen
--
On 09-Jan-2001 Dekel Tsur wrote:
>> There was a limitation before in this stuff and it was if the bottom line
>> should be added to the row or not. So I thought that we could decide this
>
> So store this information using a different attribute.
Yes, I've to find out (decide) how!
On Tue, Jan 09, 2001 at 11:30:31AM +0100, Juergen Vigna wrote:
> Well good question #:O). Is because I coded it reason enough, hmmm, dada,
> I guess not ;)
>
> I'll apply your patch!
Here is a slightly better patch:
getTokenValue(..., int & num) will not change num if the call to
On 09-Jan-2001 Dekel Tsur wrote:
>
> Here is a slightly better patch:
> getTokenValue(..., int & num) will not change num if the call to
> getTokenValue(..., tmp) returned false.
>
I already applied the other patch :( and did already modify the source
so I cannot safely apply the patch. Could
On 09-Jan-2001 Dekel Tsur wrote:
> Here is a slightly better patch:
> getTokenValue(..., int & num) will not change num if the call to
> getTokenValue(..., tmp) returned false.
Don't bother to send a patch I already did this in a other way as
I need also to translate the strings to different
On Tue, Jan 09, 2001 at 12:33:39PM +0100, Juergen Vigna wrote:
>
> On 09-Jan-2001 Dekel Tsur wrote:
> >
> > Here is a slightly better patch:
> > getTokenValue(..., int & num) will not change num if the call to
> > getTokenValue(..., tmp) returned false.
> >
>
> I already applied the other
On 09-Jan-2001 Dekel Tsur wrote:
>
> Here are the changes from the previous patch.
Well thanks I did it already (a bit different). One thing I noticed and
I would ask you to not do it is remove my () around expressions, that is
my coding style and I like to see them where they are.
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 09-Jan-2001 Dekel Tsur wrote:
| >
| > Here are the changes from the previous patch.
|
| Well thanks I did it already (a bit different). One thing I noticed and
| I would ask you to not do it is remove my () around expressions, that is
| my coding
On 09-Jan-2001 Lars Gullik Bjønnes wrote:
>
> I will remove () that has no value when I see them.
>
I will add () if I find expressions better to read when I need them.
> - two points:
> - () without meaning kindo shows that the coder does not know the
> precedence rules
da
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 09-Jan-2001 Lars Gullik Bjønnes wrote:
| >
| > I will remove () that has no value when I see them.
| >
|
| I will add () if I find expressions better to read when I need them.
So that you will be able to parse the above sentence? :-)
| > - two
Hi!
I changed the tabular format for the version 1.1.6. This means your not
able anymore to read your 1.1.6 saved tabular if you don't activate the
define in tabular.C (USE_OLD_READFORMAT). If you do this you can read your
old files and write the new format. Obviously you're then not able to
Juergen Vigna <[EMAIL PROTECTED]> writes:
| Hi!
|
| I changed the tabular format for the version 1.1.6. This means your not
| able anymore to read your 1.1.6 saved tabular if you don't activate the
| define in tabular.C (USE_OLD_READFORMAT). If you do this you can read your
| old files and
On 09-Jan-2001 Lars Gullik Bjønnes wrote:
>
> Are we compatible with pre2/3?
>
> If not that has to change.
>
> These prereleases were put forward to the general public and to change
> the format so that pre cannot be read is not acceptable.
Well nice from you that you come forward now and
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 09-Jan-2001 Lars Gullik Bjønnes wrote:
| >
| > Are we compatible with pre2/3?
| >
| > If not that has to change.
| >
| > These prereleases were put forward to the general public and to change
| > the format so that pre cannot be read is not
On Tue, Jan 09, 2001 at 08:19:47PM +0100, Lars Gullik Bjnnes wrote:
>
> Well, then I wan tto do this:
> - bump version number to "2"
It doesn't make sense to store the tabular format in each tabular.
The global \lyxformat suffices, so I suggest changing the lyxformat to
2.18 and remove
Dekel Tsur <[EMAIL PROTECTED]> writes:
| On Tue, Jan 09, 2001 at 08:19:47PM +0100, Lars Gullik Bjønnes wrote:
| >
| > Well, then I wan tto do this:
| > - bump version number to "2"
|
| It doesn't make sense to store the tabular format in each tabular.
| The global \lyxformat suffices,
On Mon, Jan 08, 2001 at 04:50:00PM +0100, Juergen Vigna wrote:
On 08-Jan-2001 Dekel Tsur wrote:
- Incorrect reading of longtable options
Now Dekel you wrote an email about this earlier, but I'm afraid it got
lost. Was the OLD-FORMAT-READ wrong or also the NEW-FORMAT-READ about
them?
On 08-Jan-2001 Dekel Tsur wrote:
Both.
Also, in the new format, the numbers are negative (e.g. endfoot="-3"). Is this
intentional ?
Yes it is intentional!
What about combining LyXTabular and Features ?
IMO no but if other think we should ok!
And using alignmet=center instead of
On Mon, Jan 08, 2001 at 05:15:10PM +0100, Juergen Vigna wrote:
Also, in the new format, the numbers are negative (e.g. endfoot="-3"). Is this
intentional ?
Yes it is intentional!
What is the difference between positive and negative value ?
- The table rotate attribute is not being read
On Mon, Jan 08, 2001 at 04:50:00PM +0100, Juergen Vigna wrote:
>
> On 08-Jan-2001 Dekel Tsur wrote:
>
> > - Incorrect reading of longtable options
>
> Now Dekel you wrote an email about this earlier, but I'm afraid it got
> lost. Was the OLD-FORMAT-READ wrong or also the NEW-FORMAT-READ about
On 08-Jan-2001 Dekel Tsur wrote:
>
> Both.
> Also, in the new format, the numbers are negative (e.g. endfoot="-3"). Is this
> intentional ?
>
Yes it is intentional!
> What about combining and ?
IMO no but if other think we should ok!
> And using alignmet=center instead of alignment=8 ?
>
On Mon, Jan 08, 2001 at 05:15:10PM +0100, Juergen Vigna wrote:
> > Also, in the new format, the numbers are negative (e.g. endfoot="-3"). Is this
> > intentional ?
> Yes it is intentional!
What is the difference between positive and negative value ?
> > - The table rotate attribute is not being
60 matches
Mail list logo
