On 23-Oct-2001 Herbert Voss wrote:
seems to be that it's not interesting, maybe that there are
No I find it really interesting already by your description yesterday,
but I didn't find the time to have a look at it.
no problems with it ...
anyway, a small preview:
On Wed, Oct 24, 2001 at 09:08:18AM +0200, Juergen Vigna wrote:
[...]
It REALLY looks good. IMO we should change the ERT inset to this
type. Please I would like to hear opinions from others too! We would have
a nicer editor. On the other hand people who complained that they would like
to see
On Wed, Oct 24, 2001 at 09:08:18AM +0200, Juergen Vigna wrote:
It REALLY looks good. IMO we should change the ERT inset to this type.
Please I would like to hear opinions from others too! We would have a
nicer editor. On the other hand people who complained that they would
like to see the
Jose Abilio Oliveira Matos wrote:
On Wed, Oct 24, 2001 at 09:08:18AM +0200, Juergen Vigna wrote:
[...]
It REALLY looks good. IMO we should change the ERT inset to this
type. Please I would like to hear opinions from others too! We
would have a nicer editor. On the other hand people who
Jose Abilio Oliveira Matos wrote:
On Wed, Oct 24, 2001 at 09:08:18AM +0200, Juergen Vigna wrote:
[...]
It REALLY looks good. IMO we should change the ERT inset to this
type. Please I would like to hear opinions from others too! We would have
a nicer editor. On the other hand people who
On Tue, Oct 23, 2001 at 04:44:26PM +0100, Jose Abilio Oliveira Matos wrote:
On Mon, Oct 22, 2001 at 08:04:28PM +0200, ben wrote:
Hi,
Hi Ben, I think this discussion is better suited for the lyx-devel so I
have move it to here.
[...]
What do you think ?
Probably it will never be
On Tue, Oct 23, 2001 at 12:58:15PM -0400, Richard E. Hawkins wrote:
I cannot reproduce this, so maybe it got fixed in the meantime as 'road
kill'...
(gdb) bt
#0 0x28522574 in kill () from /usr/lib/libc.so.4
#1 0x2855fab9 in abort () from /usr/lib/libc.so.4
#2 0x82331eb in lyx::abort ()
Jose Abilio Oliveira Matos wrote:
On Wed, Oct 24, 2001 at 09:08:18AM +0200, Juergen Vigna wrote:
[...]
It REALLY looks good. IMO we should change the ERT inset to this
type. Please I would like to hear opinions from others too! We would have
a nicer editor. On the other hand people who
On Wed, Oct 24, 2001 at 09:57:03AM +0200, Herbert Voss wrote:
Jose Abilio Oliveira Matos wrote:
[...]
I agree with Jürgen. It looks prety, but I am one of the people who would
like to see a inline version, if possible, as we have now.
have a look at attached gif for some more
On 23-Oct-2001 Jose Abilio Oliveira Matos wrote:
This question is probably for Juergen.
Why the long tables arguments get a negative value? Like this
... endhead=-3 endfirsthead=-3 endfoot=-3 endlastfoot=-3 ...
When some code is both a header and a footer?
Did you try it? Anyway I
On 23-Oct-2001 Jose Abilio Oliveira Matos wrote:
While in the docbook model you can have how many head rows and foot rows
you want to.
Same in LaTeX!
My solution as to enable both (if present) firsthead and head rows to be
present in the header, by this order, and foot and last foot
On Wed, Oct 24, 2001 at 10:09:18AM +0200, Juergen Vigna wrote:
On 23-Oct-2001 Jose Abilio Oliveira Matos wrote:
While in the docbook model you can have how many head rows and foot rows
you want to.
Same in LaTeX!
Ok.
My solution as to enable both (if present) firsthead and
On Wed, Oct 24, 2001 at 10:03:40AM +0200, Juergen Vigna wrote:
On 23-Oct-2001 Jose Abilio Oliveira Matos wrote:
This question is probably for Juergen.
Why the long tables arguments get a negative value? Like this
... endhead=-3 endfirsthead=-3 endfoot=-3 endlastfoot=-3 ...
When
On 24-Oct-2001 Andre Poenitz wrote:
Will we have an inlined view that retains state during
save/re-opening/spellchecking?
What I thought about this is that we shouldn't use a InsetCommand
Type inset as that does not have inline view (just the button view
which for some is not enough). We
On 24-Oct-2001 Herbert Voss wrote:
sure, but where is the sense? Jürgens idea of a wysiwyg ERT is
much nore better than my GUI solution!!! But there are still
(not easy to solve - am I right??) problems with it, so I thought,
it's better to choose a solution with a clear background:
I
On Wed, Oct 24, 2001 at 09:08:18AM +0200, Juergen Vigna wrote:
http://www.educat.hu-berlin.de/~voss/lyx/ERT.html
It REALLY looks good. IMO we should change the ERT inset to this
type. Please I would like to hear opinions from others too! We would have
a nicer editor. On the other hand
On 24-Oct-2001 Jose Abilio Oliveira Matos wrote:
I have decided that they are the same since there isn't any distintion
between them in docbook.
So in docbook you don't have the distinction between first header and header
and last footer and footer?
Much more clear, what is going on.
On 24-Oct-2001 Garst R. Reese wrote:
This PM CVS
checking a 50p doc with figures and tables and lots of Accept this word
or Ignores,
Completion bar is very erratic and there are long delays. Finally it
just died.
This is a pspell problem. I tried to contact Kevin a few times but he
never
On Wed, Oct 24, 2001 at 10:52:14AM +0200, Juergen Vigna wrote:
On 24-Oct-2001 Jose Abilio Oliveira Matos wrote:
I have decided that they are the same since there isn't any distintion
between them in docbook.
So in docbook you don't have the distinction between first header and
On Wed, Oct 24, 2001 at 10:40:37AM +0200, Juergen Vigna wrote:
What I thought about this is that we shouldn't use a InsetCommand
Type inset as that does not have inline view (just the button view
which for some is not enough). We would have to use the actual ERT
inset but we don't permit
On Wednesday 24 October 2001 10:26, Jean-Marc Lasgouttes wrote:
Juergen == Juergen Vigna [EMAIL PROTECTED] writes:
Juergen What I thought about this is that we shouldn't use a
Juergen InsetCommand Type inset as that does not have inline view
Juergen (just the button view which for some is
A few trivial changes.
* lyx_gui.C: whitespace change
* undo_funcs.[Ch]: putting duplicated code into helper function,
whitespacce changes
* undo_stack.[Ch]: change interface to be more similar to std::stack
* vspace.C: whitespace changes
I have had the undo changes in my local tree for a
Lars Gullik Bjønnes wrote:
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| This seems a bit complicated to me... Editing both in a popup or in
| inline view.
|
| One very good thing about Herbert proposal is that we would just avoid
| using insettext for ert (which avoids a lot of
With the actual tabular code you can have as much as you want!
How?
endhead, endfirsthead, endlastfoot and endfoot are just integers.
Well you have to know how LaTeX work to be able to understand this :)
Anyway the number is only the row under which I write the f.ex.: \endfoot
command.
We would have the inline view and the button-view (collapsed).
Sorry for being slow again: What was the difference between inline view
and button view?
Try it just click with the right mousebutton on a ERT inset and select
the different possible views!
Jug
--
On 24-Oct-2001 Jean-Marc Lasgouttes wrote:
This seems a bit complicated to me... Editing both in a popup or in
inline view.
No I don't want to edit in the inline view I just want it as a display
option! But it seems Dekel is having an other opinion and his arguments
are not wrong IMO.
Of
Juergen Vigna wrote:
On 24-Oct-2001 Jose Abilio Oliveira Matos wrote:
Much more clear, what is going on. :-)
BUt not for 1.2.0 I guess, no?
Well I would regard this as a bug fix in the GUI interface and would
add the needed calls to the set the (double-border) options in the
On Wed, Oct 24, 2001 at 11:51:08AM +0200, Lars Gullik Bjønnes wrote:
| I have had the undo changes in my local tree for a week or so now and have
| not had any problems.
Get somebody else to test it as well, the changes is good so it should
go in, but a tiny bit more testing first...
Ok...
On 24-Oct-2001 Jean-Marc Lasgouttes wrote:
Was it in good shape?
Well we surely would have to adapt it to the new inset interface but
for simple ascii inset IMO it was good enough. But we would have to
have a look at it!
Jug
--
What's the Right Way to create a temporary file in LyX?
Andre'
--
André Pönitz .. [EMAIL PROTECTED]
* pure whitespace changes
* two occurences of else-removal in if (...) { ...; return; } else {...}
* two occurances of string const t = foo(); return t; - return foo();
Not done:
- #ifdef __EMX__
- Path p(user_lyxdir);
- #endif
where p is never used afterwards...
Andre'
--
Lars Gullik Bjønnes wrote:
| I do have the following idea on improving the current ERT inset:
| (recall that the ERT inset has 3 states: open, collapsed, and inline)
| When you press ctrl+l, an inline inset is generated. If the user presses
| enter or C-enter, than the inset automatically
On Wed, Oct 24, 2001 at 11:56:44AM +0200, Juergen Vigna wrote:
Well you have to know how LaTeX work to be able to understand this :)
We want also, as long as possible, spare the user to the latex details.
And in this case that is very easy.
I read the longtable.dvi that comes with tetex,
On 24-Oct-2001 Herbert Voss wrote:
again: the only reason for my ERT were the
problems with the actual one. with all my proposals you
do the same: discussing what should really be ...
a bit annoying
Sure but as you said they are proposals and IMO proposals should be
discussed. It would be
Juergen Vigna wrote:
On 24-Oct-2001 Herbert Voss wrote:
again: the only reason for my ERT were the
problems with the actual one. with all my proposals you
do the same: discussing what should really be ...
a bit annoying
Sure but as you said they are proposals and IMO proposals
On Wed, Oct 24, 2001 at 12:46:56PM +0200, Lars Gullik Bjønnes wrote:
Andre Poenitz [EMAIL PROTECTED] writes:
| -cmdret const c = do_popen(kpsecmd);
| -
| -lyxerr[Debug::LATEX] kpse status = c.first \n
| - kpse result = ` strip(c.second, '\n')
On 24-Oct-2001 Herbert Voss wrote:
I'm a bit astonished that you talk about these facts ... because
there are some tables with some formats
on the other hand, I don't change the fileformat.
I don't follow you here? If you mean the new tabular format then that
format was discussed for
Hi Dekel (this is probably to you),
if I set the flags in the configuration file for the convertion
docbook-html to
resultdir=$$b,resultfile=t1.html
the preview work as it should. I view the html and the right file is shown.
But when I try to export it to html, I have
On 24-Oct-2001 Jose Abilio Oliveira Matos wrote:
I read the longtable.dvi that comes with tetex, if that is what you mean.
:-) I have it open for more than 24 hours to iluminate me with your design.
;-) But now I got it from your explanation. :-)
I know I'm too good sometimes ;)
Ok, I
Hi,
when you use the special column in tabular layout, the alignment ist
correctly exported to latex, but the width is ignored, this creates
invalid latex-code.
This bug is included in 1.1.6fix3 and the actual 1.2.0cvs development
version.
If someone has a one liner patch for it, i would
On 24-Oct-2001 Christoph M. Friedrich wrote:
when you use the special column in tabular layout, the alignment ist
correctly exported to latex, but the width is ignored, this creates
invalid latex-code.
Please heed that if you use the special column fields YOU have to provide
the exact
On Wed, Oct 24, 2001 at 02:21:04PM +0200, Juergen Vigna wrote:
[...]
I know I'm too good sometimes ;)
That's too kind of you. ;-)
You could provide more visual feedback for header and footer, say with
bold fonts. Those are the visual expectations we have related to both of
them.
On 24-Oct-2001 Jose Abilio Oliveira Matos wrote:
My point is to make the users' live easier. Imagine that I like to put the
footers in the end of the table, the preamble in the begin and the table
body in the middle. Even although we have to export the code in a different
order than what
On 24-Oct-2001 Jose Abilio Oliveira Matos wrote:
I have called the Table Examples from examples and got 2 error when I
tried to display it. Could you have a look?
There is a problem with the compatibility read for minipages. The closing
} of the {\centering tag around the minipage is
On Wed, Oct 24, 2001 at 02:35:35PM +0200, Juergen Vigna wrote:
On 24-Oct-2001 Christoph M. Friedrich wrote:
when you use the special column in tabular layout, the alignment ist
correctly exported to latex, but the width is ignored, this creates
invalid latex-code.
Please heed that if
On 24-Oct-2001 Dekel Tsur wrote:
I think that the problem that this is not clear from the dialog.
Here is a suggestion for clearer dialog arrangement:
(* denotes a radio button, denotes a text input field)
[snip]
Well don't you think this takes up a bit too much space? I would have
to
On Wed, Oct 24, 2001 at 01:25:28PM +0100, Jose Abilio Oliveira Matos wrote:
Hi Dekel (this is probably to you),
if I set the flags in the configuration file for the convertion
docbook-html to
resultdir=$$b,resultfile=t1.html
the preview work as it should. I view the html
On Wed, Oct 24, 2001 at 04:24:02PM +0200, Lars Gullik Bjønnes wrote:
| if (::rename(from.c_str(), to.c_str()) == -1)
| if (lyx::copy(from, to)) {
| lyx::unlink(from);
| return true;
| } else
|
On 24-Oct-2001 Juergen Spitzmueller wrote:
Please tell me when you have implemented the needed stuff. I can
probably help you with the GUI-work.
No matter if this takes a bit time, since my time is a little bit
limited now, too.
Done, go for it ;)
Forget about the Rows info in the
On Wednesday 24 October 2001 6:26 pm, Lars Gullik Bjønnes wrote:
[EMAIL PROTECTED] writes:
| CVSROOT:/usr/local/lyx/cvsroot
| Module name:lyx-devel
| Repository: lyx-devel/src/mathed/
| Changes by: [EMAIL PROTECTED] 01/10/24 19:14:05
|
| Modified files:
|
On Wednesday 24 October 2001 7:14 pm, Richard E. Hawkins wrote:
I only noticed this today. We have export pdf, but pdf isn't an option
in the custom export window.
o.b. wish: custom export to remember a couple of formats for me.
hawk
I REALLY don't see the point of this. Why not define
On Wed, Oct 24, 2001 at 08:10:21PM +, [EMAIL PROTECTED] wrote:
Log message:
Compilation fixes.
Thanks.
Andre'
--
André Pönitz .. [EMAIL PROTECTED]
On Wed, Oct 24, 2001 at 07:30:06PM -0400, Richard E. Hawkins wrote:
ControlSpellchecker.C
this means a change in your tree conflicts with a change made externally.
The first hunk (before the === line) is what you originally had, the second
one the server version.
Merge the second with the
Hi all,
I just wanted to give you a heads up on possible
problems with new RedHat 7.2 (I spent some time debugging it - I am hoping to
spare other people from same work). All of the following applies to
1.1.6fix3.
First of all -
available rpm's for redhat will not rebuild properly - i.e.
On 23-Oct-2001 Herbert Voss wrote:
> seems to be that it's not interesting, maybe that there are
No I find it really interesting already by your description yesterday,
but I didn't find the time to have a look at it.
> no problems with it ...
> anyway, a small preview:
>
>
On Wed, Oct 24, 2001 at 09:08:18AM +0200, Juergen Vigna wrote:
[...]
> It REALLY looks good. IMO we should change the ERT inset to this
> type. Please I would like to hear opinions from others too! We would have
> a nicer editor. On the other hand people who complained that they would like
> to
On Wed, Oct 24, 2001 at 09:08:18AM +0200, Juergen Vigna wrote:
> It REALLY looks good. IMO we should change the ERT inset to this type.
> Please I would like to hear opinions from others too! We would have a
> nicer editor. On the other hand people who complained that they would
> like to see
Jose Abilio Oliveira Matos wrote:
> On Wed, Oct 24, 2001 at 09:08:18AM +0200, Juergen Vigna wrote:
> [...]
>
> > It REALLY looks good. IMO we should change the ERT inset to this
> > type. Please I would like to hear opinions from others too! We
> > would have a nicer editor. On the other hand
Jose Abilio Oliveira Matos wrote:
>
> On Wed, Oct 24, 2001 at 09:08:18AM +0200, Juergen Vigna wrote:
> [...]
> > It REALLY looks good. IMO we should change the ERT inset to this
> > type. Please I would like to hear opinions from others too! We would have
> > a nicer editor. On the other hand
On Tue, Oct 23, 2001 at 04:44:26PM +0100, Jose Abilio Oliveira Matos wrote:
> On Mon, Oct 22, 2001 at 08:04:28PM +0200, ben wrote:
> > Hi,
>
> Hi Ben, I think this discussion is better suited for the lyx-devel so I
> have move it to here.
[...]
> > What do you think ?
>
> Probably it will
On Tue, Oct 23, 2001 at 12:58:15PM -0400, Richard E. Hawkins wrote:
I cannot reproduce this, so maybe it got fixed in the meantime as 'road
kill'...
> (gdb) bt
> #0 0x28522574 in kill () from /usr/lib/libc.so.4
> #1 0x2855fab9 in abort () from /usr/lib/libc.so.4
> #2 0x82331eb in lyx::abort
Jose Abilio Oliveira Matos wrote:
>
> On Wed, Oct 24, 2001 at 09:08:18AM +0200, Juergen Vigna wrote:
> [...]
> > It REALLY looks good. IMO we should change the ERT inset to this
> > type. Please I would like to hear opinions from others too! We would have
> > a nicer editor. On the other hand
On Wed, Oct 24, 2001 at 09:57:03AM +0200, Herbert Voss wrote:
> Jose Abilio Oliveira Matos wrote:
[...]
> > I agree with Jürgen. It looks prety, but I am one of the people who would
> > like to see a inline version, if possible, as we have now.
>
> have a look at attached gif for some more
On 23-Oct-2001 Jose Abilio Oliveira Matos wrote:
> This question is probably for Juergen.
> Why the long tables arguments get a negative value? Like this
> ... endhead="-3" endfirsthead="-3" endfoot="-3" endlastfoot="-3" ...
>
> When some code is both a header and a footer?
Did you try it?
On 23-Oct-2001 Jose Abilio Oliveira Matos wrote:
> While in the docbook model you can have how many head rows and foot rows
> you want to.
Same in LaTeX!
> My solution as to enable both (if present) firsthead and head rows to be
> present in the header, by this order, and foot and last
On Wed, Oct 24, 2001 at 10:09:18AM +0200, Juergen Vigna wrote:
>
> On 23-Oct-2001 Jose Abilio Oliveira Matos wrote:
>
> > While in the docbook model you can have how many head rows and foot rows
> > you want to.
>
> Same in LaTeX!
Ok.
> > My solution as to enable both (if present)
On Wed, Oct 24, 2001 at 10:03:40AM +0200, Juergen Vigna wrote:
>
> On 23-Oct-2001 Jose Abilio Oliveira Matos wrote:
> > This question is probably for Juergen.
> > Why the long tables arguments get a negative value? Like this
> > ... endhead="-3" endfirsthead="-3" endfoot="-3" endlastfoot="-3"
On 24-Oct-2001 Andre Poenitz wrote:
> Will we have an inlined view that retains state during
> save/re-opening/spellchecking?
What I thought about this is that we shouldn't use a InsetCommand
Type inset as that does not have inline view (just the button view
which for some is not enough). We
On 24-Oct-2001 Herbert Voss wrote:
> sure, but where is the sense? Jürgens idea of a "wysiwyg" ERT is
> much nore better than my GUI solution!!! But there are still
> (not easy to solve - am I right??) problems with it, so I thought,
> it's better to choose a solution with a clear background:
On Wed, Oct 24, 2001 at 09:08:18AM +0200, Juergen Vigna wrote:
> > http://www.educat.hu-berlin.de/~voss/lyx/ERT.html
>
> It REALLY looks good. IMO we should change the ERT inset to this
> type. Please I would like to hear opinions from others too! We would have
> a nicer editor. On the other
On 24-Oct-2001 Jose Abilio Oliveira Matos wrote:
> I have decided that they are the same since there isn't any distintion
> between them in docbook.
So in docbook you don't have the distinction between first header and header
and last footer and footer?
> Much more clear, what is going
On 24-Oct-2001 Garst R. Reese wrote:
> This PM CVS
> checking a 50p doc with figures and tables and lots of Accept this word
> or Ignores,
> Completion bar is very erratic and there are long delays. Finally it
> just died.
This is a pspell problem. I tried to contact Kevin a few times but he
On Wed, Oct 24, 2001 at 10:52:14AM +0200, Juergen Vigna wrote:
>
> On 24-Oct-2001 Jose Abilio Oliveira Matos wrote:
>
> > I have decided that they are the same since there isn't any distintion
> > between them in docbook.
>
> So in docbook you don't have the distinction between first header
On Wed, Oct 24, 2001 at 10:40:37AM +0200, Juergen Vigna wrote:
> What I thought about this is that we shouldn't use a InsetCommand
> Type inset as that does not have inline view (just the button view
> which for some is not enough). We would have to use the actual ERT
> inset but we don't permit
On Wednesday 24 October 2001 10:26, Jean-Marc Lasgouttes wrote:
> > "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
>
> Juergen> What I thought about this is that we shouldn't use a
> Juergen> InsetCommand Type inset as that does not have inline view
> Juergen> (just the button view
A few trivial changes.
* lyx_gui.C: whitespace change
* undo_funcs.[Ch]: putting duplicated code into helper function,
whitespacce changes
* undo_stack.[Ch]: change interface to be more similar to std::stack
* vspace.C: whitespace changes
I have had the undo changes in my local tree for a
Lars Gullik Bjønnes wrote:
>
> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>
> | This seems a bit complicated to me... Editing both in a popup or in
> | inline view.
> |
> | One very good thing about Herbert proposal is that we would just avoid
> | using insettext for ert (which avoids a
>> With the actual tabular code you can have as much as you want!
>
> How?
> endhead, endfirsthead, endlastfoot and endfoot are just integers.
Well you have to know how LaTeX work to be able to understand this :)
Anyway the number is only the row under which I write the f.ex.: \endfoot
>> We would have the inline view and the button-view (collapsed).
>
> Sorry for being slow again: What was the difference between "inline view"
> and "button view"?
Try it just click with the right mousebutton on a ERT inset and select
the different possible views!
Jug
--
On 24-Oct-2001 Jean-Marc Lasgouttes wrote:
> This seems a bit complicated to me... Editing both in a popup or in
> inline view.
No I don't want to edit in the inline view I just want it as a display
option! But it seems Dekel is having an other opinion and his arguments
are not wrong IMO.
>
Juergen Vigna wrote:
> On 24-Oct-2001 Jose Abilio Oliveira Matos wrote:
> > Much more clear, what is going on. :-)
> > BUt not for 1.2.0 I guess, no?
>
> Well I would regard this as a bug fix in the GUI interface and would
> add the needed calls to the set the (double-border) options in the
>
On Wed, Oct 24, 2001 at 11:51:08AM +0200, Lars Gullik Bjønnes wrote:
> | I have had the undo changes in my local tree for a week or so now and have
> | not had any problems.
>
> Get somebody else to test it as well, the changes is good so it should
> go in, but a tiny bit more testing first...
On 24-Oct-2001 Jean-Marc Lasgouttes wrote:
> Was it in good shape?
Well we surely would have to adapt it to the new inset interface but
for simple ascii inset IMO it was good enough. But we would have to
have a look at it!
Jug
--
What's the Right Way to create a temporary file in LyX?
Andre'
--
André Pönitz .. [EMAIL PROTECTED]
* pure whitespace changes
* two occurences of "else-removal" in if (...) { ...; return; } else {...}
* two occurances of "string const t = foo(); return t;" -> "return foo();"
Not done:
- #ifdef __EMX__
- Path p(user_lyxdir);
- #endif
where p is never used afterwards...
Lars Gullik Bjønnes wrote:
> | I do have the following idea on improving the current ERT inset:
> | (recall that the ERT inset has 3 states: open, collapsed, and inline)
> | When you press ctrl+l, an inline inset is generated. If the user presses
> | enter or C-enter, than the inset automatically
On Wed, Oct 24, 2001 at 11:56:44AM +0200, Juergen Vigna wrote:
>
> Well you have to know how LaTeX work to be able to understand this :)
We want also, as long as possible, spare the user to the latex details.
And in this case that is very easy.
I read the longtable.dvi that comes with
On 24-Oct-2001 Herbert Voss wrote:
> again: the only reason for my ERT were the
> problems with the actual one. with all my proposals you
> do the same: "discussing what should really be ..."
> a bit annoying
Sure but as you said they are "proposals" and IMO proposals should be
discussed. It
Juergen Vigna wrote:
>
> On 24-Oct-2001 Herbert Voss wrote:
>
> > again: the only reason for my ERT were the
> > problems with the actual one. with all my proposals you
> > do the same: "discussing what should really be ..."
> > a bit annoying
>
> Sure but as you said they are "proposals" and
On Wed, Oct 24, 2001 at 12:46:56PM +0200, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> | -cmdret const c = do_popen(kpsecmd);
> | -
> | -lyxerr[Debug::LATEX] << "kpse status = " << c.first << "\n"
> | -<< "kpse result = `"
On 24-Oct-2001 Herbert Voss wrote:
> I'm a bit astonished that you talk about these facts ... because
> there are some tables with some formats
> on the other hand, I don't change the fileformat.
I don't follow you here? If you mean the new tabular format then that
format was discussed
Hi Dekel (this is probably to you),
if I set the flags in the configuration file for the convertion
docbook->html to
resultdir=$$b,resultfile=t1.html
the preview work as it should. I view the html and the right file is shown.
But when I try to export it to html, I have
On 24-Oct-2001 Jose Abilio Oliveira Matos wrote:
> I read the longtable.dvi that comes with tetex, if that is what you mean.
>:-) I have it open for more than 24 hours to iluminate me with your design.
> ;-) But now I got it from your explanation. :-)
I know I'm too good sometimes ;)
> Ok,
Hi,
when you use the special column in tabular layout, the alignment ist
correctly exported to latex, but the width is ignored, this creates
invalid latex-code.
This bug is included in 1.1.6fix3 and the actual 1.2.0cvs development
version.
If someone has a one liner patch for it, i would
On 24-Oct-2001 Christoph M. Friedrich wrote:
> when you use the special column in tabular layout, the alignment ist
> correctly exported to latex, but the width is ignored, this creates
> invalid latex-code.
Please heed that if you use the special column fields YOU have to provide
the exact
On Wed, Oct 24, 2001 at 02:21:04PM +0200, Juergen Vigna wrote:
[...]
>
> I know I'm too good sometimes ;)
That's too kind of you. ;-)
> > You could provide more visual feedback for header and footer, say with
> > bold fonts. Those are the visual expectations we have related to both of
> >
On 24-Oct-2001 Jose Abilio Oliveira Matos wrote:
>
> My point is to make the users' live easier. Imagine that I like to put the
> footers in the end of the table, the preamble in the begin and the table
> body in the middle. Even although we have to export the code in a different
> order than
On 24-Oct-2001 Jose Abilio Oliveira Matos wrote:
> I have called the Table Examples from examples and got 2 error when I
> tried to display it. Could you have a look?
There is a problem with the compatibility read for minipages. The closing
} of the {\centering tag around the minipage is
On Wed, Oct 24, 2001 at 02:35:35PM +0200, Juergen Vigna wrote:
> On 24-Oct-2001 Christoph M. Friedrich wrote:
> > when you use the special column in tabular layout, the alignment ist
> > correctly exported to latex, but the width is ignored, this creates
> > invalid latex-code.
>
> Please heed
On 24-Oct-2001 Dekel Tsur wrote:
> I think that the problem that this is not clear from the dialog.
> Here is a suggestion for clearer dialog arrangement:
> (* denotes a radio button, denotes a text input field)
[snip]
Well don't you think this takes up a bit too much space? I would have
1 - 100 of 108 matches
Mail list logo
