what ever happened to that one?
georg, i guess you know?
thanks, edwin
hi guys,
i hacked together elementary booktab support for the stable tree (was
fed up with the ERT in my documents...)
patch attached in case anyone is interested
regards, edwin
booktabs.diff.gz
Description: GNU Zip compressed data
I have updated the booktabs branch to current trunk. It works for me, and
I will try to finish it so that it can be merged back in the not so far
future, but of course bug fixing for 1.4.1 has higher priority for some
time.
Georg
,6 +133,9 @@ TabularFeature tabularFeature[] =
{ LyXTabular::SET_SPECIAL_MULTI, "set-special-multi" },
{ LyXTabular::SET_BOOKTABS, "set-booktabs" },
{ LyXTabular::UNSET_BOOKTABS, "unset-booktabs" },
+ { LyXTabular::SET_TOP_SPACE, "set-top-space" },
+
On Wednesday 07 June 2006 01:45, Edwin Leuven wrote:
> i = i + 1
For 1.5.x it is acceptable (and recommended) to use
i += 1
It is easier to read and the restriction to use python 1.5.2 has been
lifted. I know the code was there before but the warning remains. :-)
--
José Abílio
Georg Baum wrote:
> Remaining tasks: Add support for interline space (half finished, see
> attached) and testing.
I had a quick look. It looks good. However, it should be possible to use
\addlinespace (without optional argument). I guess most of the time you'll
need the same linespace, which is
Am Mittwoch, 7. Juni 2006 02:45 schrieb Edwin Leuven:
> the attached patch includes qt4 (haven't had time to test yet, added
> booktabs but didn't check out interline space)
Thanks, I put the stuff without the interlinespace changes in. The current
diff is now attrached. I sti
atch adds that. It goes in now, please test.
Known problems: qt4 crashes if you want to change the spaces, I don't know
why.
I have no further plans for the booktabs branch. Is anything missing?
Edwin, could you please have a look at the qt4 problem? After that is
fixed the branch could
Georg Baum wrote:
Edwin, could you please have a look at the qt4 problem? After that is
fixed the branch could be merged.
will do (saw the space problem too, but have been unable to trace down
the culprit...)
e linespace, which is then globally defined.
>
> This patch adds that. It goes in now, please test.
Very good, thanks. However, I think the "default" switches should be disabled
initially at least for non-booktabs tables. It looks rather odd for those (on
screen and output).
Also th
Am Sonntag, 25. Juni 2006 19:41 schrieb Juergen Spitzmueller:
> Very good, thanks. However, I think the "default" switches should be
disabled
> initially at least for non-booktabs tables. It looks rather odd for
those (on
> screen and output).
Only bottom_space makes se
Georg Baum wrote:
> Am Sonntag, 25. Juni 2006 19:41 schrieb Juergen Spitzmueller:
> > Very good, thanks. However, I think the "default" switches should be
>
> disabled
>
> > initially at least for non-booktabs tables. It looks rather odd for
>
> thos
Juergen Spitzmueller wrote:
> OK. Then I'll disable the setting of the spaces initially. BTW I'd like to
> adapt the spaces UI more to the other spaces UI in LyX, that is instead of
> the check boxes: a combo "none", "default", "custom". Agreed?
Yes.
> You have used the wrong signal. The attache
", "custom". Agreed?
>
> Yes.
OK, attached is a patch that does that and
- sets spaces to "none" initially
- moves the booktabs button to "borders" as well, since it looks more obvious
there.
- changed the input validators, so it is now possible to insert
Juergen Spitzmueller wrote:
> OK, attached is a patch that does that and
> - sets spaces to "none" initially
> - moves the booktabs button to "borders" as well, since it looks more
> obvious there.
> - changed the input validators, so it is now possible to inse
Georg Baum wrote:
> I see that you used validators for unsigned lengths. I agree that this is
> the normal case, but maybe it should be possible to insert a negative
> length in special cases?
Right, I didn't think about that.
> > OK to apply?
>
> Yes, but I have some comments:
>
> +
:setBookTabs(bool what)
| +{
| + use_booktabs = what;
| +}
| +
| +
| +bool LyXTabular::useBookTabs() const
| +{
| + return use_booktabs;
| +}
| +
| +
we have often used
void LyXTabular::bookTabs(bool onoff)
{
use_booktabs = onoff;
}
bool LyXTabular::bookTabs() const
{
Can you tell briefly what booktap is as well?
"booktabs is to enable the easy production of tables such as should
appear in published scientific books and journals. What distinguishes
these from plain LaTeX tables is the default use of additional space
above and below rules, and rules of va
Edwin Leuven <[EMAIL PROTECTED]> writes:
>> Can you tell briefly what booktap is as well?
>
| "booktabs is to enable the easy production of tables such as should
| appear in published scientific books and journals. What distinguishes
| these from plain LaTeX tables i
Lars Gullik Bjønnes wrote:
Actually I am not sure if I prefere that anymore
La donna é mobile
Qual piuma al vento,
Muto d'accento - e di pensiero.
;-)
Edwin Leuven <[EMAIL PROTECTED]> writes:
> La donna à mobile
> Qual piuma al vento,
> Muto d'accento - e di pensiero.
The woman à mobile
Which piuma to the wind,
Dumb of accent - and thought.
Could anyone provide a better translation than Google?
/Andreas
On Fri, Nov 05, 2004 at 05:46:34PM +, Andreas Vox wrote:
> Edwin Leuven <[EMAIL PROTECTED]> writes:
>
> > La donna é mobile
> > Qual piuma al vento,
> > Muto d'accento - e di pensiero.
>
> The woman é mobile
> Which piuma to the wind,
piuma -> (more or less) feather
> Dumb of accent -
Andreas Vox wrote:
> Edwin Leuven <[EMAIL PROTECTED]> writes:
>
>> La donna à mobile
>> Qual piuma al vento,
>> Muto d'accento - e di pensiero.
>
> The woman à mobile
> Which piuma to the wind,
> Dumb of accent - and thought.
>
> Could anyone provide a better translation than Google?
something
Josà AbÃlio Oliveira Matos wrote:
>> Could anyone provide a better translation than Google?
>
> Do you want to stop Alfrado's work just for that? ;-)
LOL... But I'd gladly exchange the translation for some bug fixing...
Alfredo
> >> La donna à mobile
> >> Qual piuma al vento,
> >> Muto d'accento - e di pensiero.
A woman is volatile [or variable or in flux]
like a feather in the wind
weak in words and in thoughts
> I think that it then goes on saying that still, they are worth to make love
> with...
ROTFL :) I.e. what a
On Fri, Nov 05, 2004 at 11:50:49AM +0100, Edwin Leuven wrote:
> hi guys,
>
> i hacked together elementary booktab support for the stable tree (was
> fed up with the ERT in my documents...)
What about xforms?
Andre'
What about xforms?
something like the attached?
edwin
booktabs2.diff.gz
Description: application/gzip
tabular create
dialog and in the tabular dialog itself (options "classic", "frameless",
"elegant" or whatever non-latex name for booktabs there is).
I think that you should disable vertical lines and add some gui for
\addlinespace. Apart from that, the patch looks very good IMHO.
Regards,
Jürgen
options "classic", "frameless",
> "elegant" or whatever non-latex name for booktabs there is).
>
> I think that you should disable vertical lines and add some gui for
> \addlinespace. Apart from that, the patch looks very good IMHO.
I like it, too, because
Georg Baum wrote:
> I like it, too, because booktabs tables aim at high typographical quality.
> The question now is: What to do with it? This patch does change the file
> format (although tables with booktabs=true can still be read by unpatched
> versions, but the latex output
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
| Georg Baum wrote:
>> I like it, too, because booktabs tables aim at high typographical quality.
>> The question now is: What to do with it? This patch does change the file
>> format (although tables with booktabs=t
f bugs that I'm
able to fix is limited).
Wrt booktabs, I just fear that I'll see native support (which I need for my
daily work) not before 2007. The changes are not severe and if there might be
some bugs, I am willing to fix these.
Jürgen
w that Alfredo and Andre seem to find more time again (I check
| bugzilla regularly if I have some spare time, but the scope of bugs that I'm
| able to fix is limited).
| Wrt booktabs, I just fear that I'll see native support (which I need for my
| daily work) not before 2007. The chang
;s new
> | hope now that Alfredo and Andre seem to find more time again (I check
> | bugzilla regularly if I have some spare time, but the scope of bugs
that I'm
> | able to fix is limited).
The same holds for me.
> | Wrt booktabs, I just fear that I'll see native sup
y yesterday in order to try it
> out). Changes from Edwins original version:
> - lyx2lyx support
> - Disable vertical rules for latex and plaintext output. They are not yet
> disabled in the frontends. I think that the rules should not be deleted
> if one checks the booktabs checkb
On Sun, Nov 07, 2004 at 07:56:10PM +0100, Georg Baum wrote:
@@ -1526,7 +1693,8 @@ def convert(file):
235 : [convert_paperpackage],
236 : [convert_bullets, add_begin_header, add_begin_body,
normalize_papersize, strip_end_space],
- 237
On Sun, Nov 07, 2004 at 08:09:29PM +0100, Juergen Spitzmueller wrote:
> Georg Baum wrote:
> > Ok. I think it should be done in CVS. Jürgen, should I create a branch
> > (following Alfredos hints, I did it never before)?
>
> That'd be good (so we could work on it together). I never created a branch
Georg Baum wrote:
>> I'd like the booktabs patch developed and stabilized outside the main
>> branch in CVS. Either completely outside CVS or in a separate branch.
>
> Ok. I think it should be done in CVS. JÃrgen, should I create a branch
> (following Alfredos hints,
I did try not to respond to this.
On Sun, Nov 07, 2004 at 08:57:10PM +0100, Andre Poenitz wrote:
> I'd rather officially lift the freeze for a short while and let
> everybody work on his pet project in this time. This also includes XML
> support as this is a thing of fairly high 'public interest
Andre Poenitz wrote:
>> That'd be good (so we could work on it together). I never created a
>> branch myself, though.
>
> Working with branches is a pain, frustrates people and eats into already
> scrace resources.
>
> I'd rather officially lift the freeze for a short while and let
> everybody wo
Alfredo Braunstein <[EMAIL PROTECTED]> writes:
| PS: I'm wondering... maybe you could as well work directly in CoordBranch?
| Dunno what would be the disadvantages...
If the CoordBranch is fruitless then you'll get a hell a lot of work
to do.
Separate branch or none at all.
--
Lgb
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Sun, Nov 07, 2004 at 08:09:29PM +0100, Juergen Spitzmueller wrote:
>> Georg Baum wrote:
>> > Ok. I think it should be done in CVS. Jürgen, should I create a branch
>> > (following Alfredos hints, I did it never before)?
>>
>> That'd be good (so we co
Alfredo Braunstein wrote:
> (cannot wait to have Juergen and Georg's skills employed in fixing core
> bugs ;-))
As to me: don't hold your breath (but at least I fixed two critical bugs in
the last week, and that's surprising enough for a human scientist) ;-)
Jürgen
Juergen Spitzmueller wrote:
> As to me: don't hold your breath (but at least I fixed two critical bugs
> in the last week, and that's surprising enough for a human scientist) ;-)
I know. That's more than most of us go human sciences!
Alfredo
On Sun, Nov 07, 2004 at 08:58:55PM +, John Levon wrote:
>
> I did try not to respond to this.
>
> On Sun, Nov 07, 2004 at 08:57:10PM +0100, Andre Poenitz wrote:
>
> > I'd rather officially lift the freeze for a short while and let
> > everybody work on his pet project in this time. This also
lready did half the work
and chances are really low that it breaks anything (almost everything
enclosed in "if (use_booktabs)" and since there are at least three of us
who need this I thought that it should be added.
As it stands now I will not do further work on the booktabs stuff. I really
eature freeze, too, and that I do not come
| up with arbitrary new features, but since Edwin already did half the work
| and chances are really low that it breaks anything (almost everything
| enclosed in "if (use_booktabs)" and since there are at least three of us
| who need this I thou
added.
> | As it stands now I will not do further work on the booktabs stuff. I
> | really don't know wether that has any influence on the number of fixed
> | bugs or not.
>
> I might be swayed if all three of you test and "perfect" this patch.
I offer myself to test it if somebody explain me what's about ;-)
Alfredo
Alfredo Braunstein <[EMAIL PROTECTED]> writes:
> > I might be swayed if all three of you test and "perfect" this patch.
>
> I offer myself to test it if somebody explain me what's about
"Any layout with a vertical line can be improved immediately by removing
that line" -- I don't remember where
Andreas Vox wrote:
> "Any layout with a vertical line can be improved immediately by removing
> that line" -- I don't remember where this quote comes from, but as you
> will have noticed, most LaTeX tables have lots of vertical lines which can
> be improved ;-)
>
> Formal tables have only one hor
you want.
Or, as the masters tell it:
http://www.dante.de/CTAN/macros/latex/contrib/booktabs/booktabs.pdf
/Andreas
Lars Gullik Bjønnes wrote:
> | As it stands now I will not do further work on the booktabs stuff. I
> | really don't know wether that has any influence on the number of fixed
> | bugs or not.
That'd be a pity.
> I might be swayed if all three of you test and "perfe
ain ugly (to say the least). Booktabs
has thick rules (for top and bottom) and thin rules (for inbetween) and
other stuff that makes a table look like it should for good typography.
Additional to Andreas' link, I'd like to redirect your eye to this:
http://www.tug.org/tex-archive/info/ger
Juergen Spitzmueller wrote:
>> I might be swayed if all three of you test and "perfect" this patch.
>
> Well, then let's do our best ;-)
Well said.
> Seriously, Georg, if we had a branch, it would be much easier to improve
> and test in parallel (given that someone (you?) is willing to "maintai
Am Dienstag, 9. November 2004 18:28 schrieb Juergen Spitzmueller:
> Lars Gullik Bjønnes wrote:
> > I might be swayed if all three of you test and "perfect" this patch.
>
> Well, then let's do our best ;-)
> Seriously, Georg, if we had a branch, it would be much easier to improve
and
> test in par
Jürgen,
I have created the branch for the booktabs support. The current diff against
HEAD is attached.
You can update an existing tree with
cvs update -P -r BooktabBranch
TODO list:
1. Disable changing of vertical rules in the frontends if booktabs are
enabled. The output of vertical rules
On Sun, Nov 07, 2004 at 08:57:10PM +0100, Andre Poenitz wrote:
> Working with branches is a pain, frustrates people and eats into already
> scarce resources.
Balderdash, I say!
I've worked with code on 3 different branches, simultaneously. The
only problem I encountered was remembering which bra
On Fri, Dec 03, 2004 at 06:00:38PM -0500, candide wrote:
> No, the only three real problems with branches are:
>
> - Unfamiliarity with them, possibly combined with fear of them.
I have worked with them although I am afraid of them. I was no happy and
I don't see the benefits outweighting the cos
Andre Poenitz <[EMAIL PROTECTED]> writes:
>>(Only needed for patches affecting code you're working on.
>> Otherwise, just Merge Early and Often.)
>
| Lars's patches tend to touch lots of files, so you most certainly get
| lots of conflicts if you are not close to HEAD and have similar patc
Georg Baum wrote:
> I have created the branch for the booktabs support. The current diff
> against HEAD is attached.
Cool. I'm already updating.
> TODO list:
>
> 1. Disable changing of vertical rules in the frontends if booktabs are
> enabled. The output of vertical rule
Am Donnerstag, 11. November 2004 20:09 schrieb Georg Baum:
> TODO list:
>
> 1. Disable changing of vertical rules in the frontends if booktabs are
> enabled. The output of vertical rules is already suppressed.
The attached patch implements this.
Georg
Index: src/frontends/qt
Georg Baum wrote:
> > 1. Disable changing of vertical rules in the frontends if booktabs are
> > enabled. The output of vertical rules is already suppressed.
>
> The attached patch implements this.
Looks good.
Jürgen
P.S.: I have tried the booktabs branch yesterday. Looks very
Am Sonntag, 14. November 2004 11:37 schrieb Juergen Spitzmueller:
> P.S.: I have tried the booktabs branch yesterday. Looks very good so
far. Then
> I noticed how bad the shape of the tabular code is ATM. Multicolumn is
> disabled; rotate_cell does not work; UNSET_ALL_LINES is
Hi!
Disclaimer: Since I have only three weeks left for finishing my PhD thesis, I
am still using 1.4.6svn -- no time for any upgrade surprises anymore.
I have only recently been pointed to booktabs (a style for non-ugly tables
suitable for books) -- has anyone used that with LyX yet? (How
(Arbeitskopie)
@@ -106,10 +106,11 @@ void QTabularDialog::closeEvent(QCloseEv
}
-void QTabularDialog::on_booktabsCB_stateChanged(int checked)
+void QTabularDialog::on_booktabsCB_stateChanged()
{
form_->changed();
- form_->controller().booktabs(checked);
+ form_->controller()
The booktabs support is fully functional now (except gtk frontend). One
feature is missing: Suport for left and right adjustment of \clines.
Since I don't know when I will be able to implement that, and since I want
the current booktabs support in before the next freeze I plan to merge
On Saturday 12 January 2008 20:53:35 Hans Meine wrote:
> Hi!
>
> Disclaimer: Since I have only three weeks left for finishing my PhD thesis,
> I am still using 1.4.6svn -- no time for any upgrade surprises anymore.
>
> I have only recently been pointed to booktabs (a style f
> I have only recently been pointed to booktabs (a style for non-ugly tables
> suitable for books) -- has anyone used that with LyX yet? (How?)
For LyX 1.4 you need some ERT. But it is not difficult and I wrote my diploma thesis with LyX 1.3
using this method. Attached an example.
&
On Samstag 12 Januar 2008, Uwe Stöhr wrote:
> > Is it planned to officially support that package?
>
> LyX 1.5 supports this except of some specialities like e.g. the alignment
> of the table rules.
Thanks to José and you for this information.
> > I have only recently bee
Georg Baum wrote:
> Since I don't know when I will be able to implement that, and since I want
> the current booktabs support in before the next freeze I plan to merge
> the branch back soon.
Good plan!
Jürgen
Georg Baum <[EMAIL PROTECTED]> writes:
| The booktabs support is fully functional now (except gtk frontend). One
| feature is missing: Suport for left and right adjustment of \clines.
|
| Since I don't know when I will be able to implement that, and since I want
| the current bookt
>>>>> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> The booktabs support is fully functional now (except gtk
Georg> frontend). One feature is missing: Suport for left and right
Georg> adjustment of \clines.
Georg> Since I don't know
parsing.
>
> +2004-11-11 Edwin Leuven
> +
> + * insettabular.C (getStatus, tabularFeatures): handle booktabs feature
> +
> 2004-11-10 Jean-Marc Lasgouttes
> <[EMAIL PROTECTED]>
>
> * insetlatexaccent.h (isLetter): implement, so that word selection
>
> Is this
Georg Baum wrote:
This goes mainly to Edwin and Jürgen, they did a great part of it.
1 + 1 + 1 = 4
MAT (Arbeitskopie)
@@ -1,6 +1,19 @@
LyX file-format changes
---
+2006-07-03 Georg Baum <[EMAIL PROTECTED]>
+
+ * format incremented to 248: Basic booktabs support
+
+ The tag has a new switch: booktabs="true|false".
+ An absent switch is equivalent to booktabs=&q
the following new attributes:
+ topspace, bottomspace and interlinespace. All take a LyXLength
+ as value, or the special keyword "default".
Are these new spacing for booktabs only?
JMarc
Jean-Marc Lasgouttes wrote:
> A question:
> + The tag of tabulars has the following new attributes:
> + topspace, bottomspace and interlinespace. All take a LyXLength
> + as value, or the special keyword "default".
>
> Are these new spacing for
Hi,
Since some time I'm contemplating implementing booktabs a.k.a. tableaux
support for 1.3.x. Would that have a chance to go in, if properly done? I.e.
are any new features allowed into 1.3.x? I might have asked that before, but
have forgotten the answer since :) *
I'm thinking o
Kuba Ober wrote:
>
> Hi,
>
> Since some time I'm contemplating implementing booktabs a.k.a. tableaux
> support for 1.3.x. Would that have a chance to go in, if properly
done? I.e.
> are any new features allowed into 1.3.x? I might have asked that
before, but
> have
Kuba Ober wrote:
> Since some time I'm contemplating implementing booktabs a.k.a. tableaux
> support for 1.3.x. Would that have a chance to go in, if properly done?
> I.e. are any new features allowed into 1.3.x? I might have asked that
> before, but have forgotten the answer si
On Thursday 29 January 2004 10:22, Juergen Spitzmueller wrote:
> Kuba Ober wrote:
> > Since some time I'm contemplating implementing booktabs a.k.a.
> > tableaux support for 1.3.x. Would that have a chance to go in, if
> > properly done? I.e. are any new features a
... -> 229
||
+---> xxx -->+
where xxx is the new format. And we have not yet talked about backwards
conversion.
My personal opinion is to change nothing in 1.3 that requires a file format
change. The time needed for adjusting lyx2lyx is better spent with fix
> [1] If you need booktabs tabulars in lyx: you know that there are some ERT
> tricks to use booktabs within the lyx tabulars?
Yep I know, but I find that it's easier to use just plain old ERT.
Kuba
> > I'm not the one to decide this, but I think there are no (major) new
> > features allowed for 1.3.x. Why not code it up for 1.4? [1]
>
> Note that tables are severely broken in 1.4... Of course, you are welcomed
> to fix them on the way going (not easy I suspect)
That's why I wanted to do it f
On Thursday 29 January 2004 07:41 am, Georg Baum wrote:
> Kuba Ober wrote:
> > I'm thinking of adding a per-table "Book-style table" checkbox which will
> > limit what you can do to the table - i.e. no vertical lines, as well as
> > adding support for top/mid/bottom rule and cmidrule. Since this wo
> Here's a limited patch for 1.4cvs.
WOW!
> It has several limitations:
>
> * As Alfredo wrote, tables don't work currently in 1.4cvs, so they're a
> bit hard to test :)
:)
> * Vertical bars are not disabled. Should they? And they're
> systematically removed at creation time (yay! ;-))
They sh
On Thursday 29 January 2004 20:47, Kuba Ober wrote:
> >
> > The problem is not the actual conversion, this would indeed be trivial.
> > The problem is something else:
> > File format changes without changing the file format version number
> > will bring serious compatibility problems.
>
> Well, I d
> "Georg" == Georg Baum <[EMAIL PROTECTED]> writes:
Georg> My personal opinion is to change nothing in 1.3 that requires a
Georg> file format change. The time needed for adjusting lyx2lyx is
Georg> better spent with fixing 1.4 bugs.
Not only that, but the policy is to make sure that all 1.3.x
Am Montag, den 01.04.2019, 09:03 +0200 schrieb Kornel Benko:
> I get following compiler errors for GuiTabular.cpp
Should be fixed. The bad news is that we now (again) have to manually
edit ui files generated with Qt 5.12.
Jürgen
signature.asc
Description: This is a digitally signed message part
Am Montag, 1. April 2019, 09:20:32 CEST schrieb Jürgen Spitzmüller:
> Am Montag, den 01.04.2019, 09:03 +0200 schrieb Kornel Benko:
> > I get following compiler errors for GuiTabular.cpp
>
> Should be fixed. The bad news is that we now (again) have to manually
> edit ui files generated with Qt 5.12
Am Montag, 1. April 2019, 10:21:42 CEST schrieb Kornel Benko:
> Am Montag, 1. April 2019, 09:20:32 CEST schrieb Jürgen Spitzmüller:
> > Am Montag, den 01.04.2019, 09:03 +0200 schrieb Kornel Benko:
> > > I get following compiler errors for GuiTabular.cpp
> >
> > Should be fixed. The bad news is tha
Am Montag, den 01.04.2019, 10:21 +0200 schrieb Kornel Benko:
> Sorry for making trouble.
It's not you making trouble, but Qt.
Jürgen
signature.asc
Description: This is a digitally signed message part
Am Montag, den 01.04.2019, 10:58 +0200 schrieb Kornel Benko:
> Meant is 'horizontal' I suppose?
Yes, right. Thanks.
Jürgen
signature.asc
Description: This is a digitally signed message part
Maybe some arguments of \cmidrule could be set automatically without
additional UI?
For example, if a column with a \cmidrule underneath is set to "align
center" then this should be inherited by its \cmidrule, i.e.
\cmidrule(c){...}
Also, a \cmidrule should never stretch over more than one (
On 20.10.2017 11:06, racoon wrote:
For example, if a column with a \cmidrule underneath is set to "align
center" then this should be inherited by its \cmidrule, i.e.
\cmidrule(c){...}
Or maybe if all columns just below a \cmidrule are set to "align
center"? In this way it is still possible to
On Fri, Oct 20, 2017 at 08:13:53AM +, racoon wrote:
> On 20.10.2017 11:06, racoon wrote:
> > For example, if a column with a \cmidrule underneath is set to "align
> > center" then this should be inherited by its \cmidrule, i.e.
> >
> > \cmidrule(c){...}
> Or maybe if all columns just below a \
On 20.10.2017 23:56, Scott Kostyshak wrote:
Please make sure to add your thoughts to the ticket, so they don't get
lost.
Done. http://www.lyx.org/trac/ticket/3072#comment:11
Daniel
97 matches
Mail list logo
