tabu m-column vertical alignment not working after package updates
3
After MIKTEX package updates vertical m-column alignment in tabu does not work anymore. See MWE below
documentclass{article}
usepackage{tabu}
begin{document}
tabulinesep=3pt
Result using tabu:
begin{tabu} to linewidth {|X[p]| X[m]| X[b]|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabu}
vspace*{1cm}
Result using tabular:
begin{tabular}{|p{0.3linewidth}|m{0.3linewidth}|b{0.3linewidth}|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabular}
end{document}
The results is:
Both tables should be equal but m-column in tabu is broken.Does anyone know which package is responsible for that? Here is the list of packages that were updated:
tabu vertical alignment
asked May 10 '18 at 13:34
MichaMicha
182
|
show 3 more comments
3
After MIKTEX package updates vertical m-column alignment in tabu does not work anymore. See MWE below
documentclass{article}
usepackage{tabu}
begin{document}
tabulinesep=3pt
Result using tabu:
begin{tabu} to linewidth {|X[p]| X[m]| X[b]|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabu}
vspace*{1cm}
Result using tabular:
begin{tabular}{|p{0.3linewidth}|m{0.3linewidth}|b{0.3linewidth}|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabular}
end{document}
The results is:
Both tables should be equal but m-column in tabu is broken.Does anyone know which package is responsible for that? Here is the list of packages that were updated:
tabu vertical alignment
asked May 10 '18 at 13:34
MichaMicha
182
Welcome to TeX.SX! Just to mention it: TL2018 (fully updated) is also affected.
– TeXnician
May 10 '18 at 13:45
In my case I never use thetabupackage alone, since it needs thelongtable,tabularx,arrayandmultirrowpackages, if I compile your code with my normal configuration I have no problems, I get the same as with the tabular environment, you should know that tabu is not a self-contained package, it is a set of macros that other table libraries use to create beautiful tables ....
– J Leon V.
May 10 '18 at 15:16
@JLeonV. do you have the 2018-04-01 latex release?
– David Carlisle
May 10 '18 at 16:35
@DavidCarlisle, it's an honor to answer you... Yes, LaTeX2e <2018-04-01> patch level 3, And I compile with pdfTeX, Version 3.14159265-2.6-1.40.19 (MiKTeX 2.9.6670 64-bit)
– J Leon V.
May 10 '18 at 20:11
@JLeonV. it shouldn't work I think, can you check you have array.sty2018/04/30 v2.4h
– David Carlisle
May 10 '18 at 20:24
|
show 3 more comments
3
3
3
1
After MIKTEX package updates vertical m-column alignment in tabu does not work anymore. See MWE below
documentclass{article}
usepackage{tabu}
begin{document}
tabulinesep=3pt
Result using tabu:
begin{tabu} to linewidth {|X[p]| X[m]| X[b]|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabu}
vspace*{1cm}
Result using tabular:
begin{tabular}{|p{0.3linewidth}|m{0.3linewidth}|b{0.3linewidth}|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabular}
end{document}
The results is:
Both tables should be equal but m-column in tabu is broken.Does anyone know which package is responsible for that? Here is the list of packages that were updated:
tabu vertical alignment
asked May 10 '18 at 13:34
MichaMicha
182
After MIKTEX package updates vertical m-column alignment in tabu does not work anymore. See MWE below
documentclass{article}
usepackage{tabu}
begin{document}
tabulinesep=3pt
Result using tabu:
begin{tabu} to linewidth {|X[p]| X[m]| X[b]|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabu}
vspace*{1cm}
Result using tabular:
begin{tabular}{|p{0.3linewidth}|m{0.3linewidth}|b{0.3linewidth}|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabular}
end{document}
The results is:
Both tables should be equal but m-column in tabu is broken.Does anyone know which package is responsible for that? Here is the list of packages that were updated:
tabu vertical alignment
tabu vertical alignment
asked May 10 '18 at 13:34
MichaMicha
182
asked May 10 '18 at 13:34
MichaMicha
182
asked May 10 '18 at 13:34
MichaMicha
182
asked May 10 '18 at 13:34
MichaMicha
182
asked May 10 '18 at 13:34
MichaMicha
182
182
Welcome to TeX.SX! Just to mention it: TL2018 (fully updated) is also affected.
– TeXnician
May 10 '18 at 13:45
In my case I never use thetabupackage alone, since it needs thelongtable,tabularx,arrayandmultirrowpackages, if I compile your code with my normal configuration I have no problems, I get the same as with the tabular environment, you should know that tabu is not a self-contained package, it is a set of macros that other table libraries use to create beautiful tables ....
– J Leon V.
May 10 '18 at 15:16
@JLeonV. do you have the 2018-04-01 latex release?
– David Carlisle
May 10 '18 at 16:35
@DavidCarlisle, it's an honor to answer you... Yes, LaTeX2e <2018-04-01> patch level 3, And I compile with pdfTeX, Version 3.14159265-2.6-1.40.19 (MiKTeX 2.9.6670 64-bit)
– J Leon V.
May 10 '18 at 20:11
@JLeonV. it shouldn't work I think, can you check you have array.sty2018/04/30 v2.4h
– David Carlisle
May 10 '18 at 20:24
|
show 3 more comments
Welcome to TeX.SX! Just to mention it: TL2018 (fully updated) is also affected.
– TeXnician
May 10 '18 at 13:45
In my case I never use thetabupackage alone, since it needs thelongtable,tabularx,arrayandmultirrowpackages, if I compile your code with my normal configuration I have no problems, I get the same as with the tabular environment, you should know that tabu is not a self-contained package, it is a set of macros that other table libraries use to create beautiful tables ....
– J Leon V.
May 10 '18 at 15:16
@JLeonV. do you have the 2018-04-01 latex release?
– David Carlisle
May 10 '18 at 16:35
@DavidCarlisle, it's an honor to answer you... Yes, LaTeX2e <2018-04-01> patch level 3, And I compile with pdfTeX, Version 3.14159265-2.6-1.40.19 (MiKTeX 2.9.6670 64-bit)
– J Leon V.
May 10 '18 at 20:11
@JLeonV. it shouldn't work I think, can you check you have array.sty2018/04/30 v2.4h
– David Carlisle
May 10 '18 at 20:24
Welcome to TeX.SX! Just to mention it: TL2018 (fully updated) is also affected.
– TeXnician
May 10 '18 at 13:45
Welcome to TeX.SX! Just to mention it: TL2018 (fully updated) is also affected.
– TeXnician
May 10 '18 at 13:45
In my case I never use the
tabu package alone, since it needs the longtable, tabularx, array and multirrow packages, if I compile your code with my normal configuration I have no problems, I get the same as with the tabular environment, you should know that tabu is not a self-contained package, it is a set of macros that other table libraries use to create beautiful tables ....– J Leon V.
May 10 '18 at 15:16
In my case I never use the
tabu package alone, since it needs the longtable, tabularx, array and multirrow packages, if I compile your code with my normal configuration I have no problems, I get the same as with the tabular environment, you should know that tabu is not a self-contained package, it is a set of macros that other table libraries use to create beautiful tables ....– J Leon V.
May 10 '18 at 15:16
@JLeonV. do you have the 2018-04-01 latex release?
– David Carlisle
May 10 '18 at 16:35
@JLeonV. do you have the 2018-04-01 latex release?
– David Carlisle
May 10 '18 at 16:35
@DavidCarlisle, it's an honor to answer you... Yes, LaTeX2e <2018-04-01> patch level 3, And I compile with pdfTeX, Version 3.14159265-2.6-1.40.19 (MiKTeX 2.9.6670 64-bit)
– J Leon V.
May 10 '18 at 20:11
@DavidCarlisle, it's an honor to answer you... Yes, LaTeX2e <2018-04-01> patch level 3, And I compile with pdfTeX, Version 3.14159265-2.6-1.40.19 (MiKTeX 2.9.6670 64-bit)
– J Leon V.
May 10 '18 at 20:11
@JLeonV. it shouldn't work I think, can you check you have array.sty
2018/04/30 v2.4h– David Carlisle
May 10 '18 at 20:24
@JLeonV. it shouldn't work I think, can you check you have array.sty
2018/04/30 v2.4h– David Carlisle
May 10 '18 at 20:24
|
show 3 more comments
1 Answer
1
active
oldest
votes
6
UPDATE 2019-01-14
A workaround for this issuse has been included in tabu 2.9 which has been submitted to ctan.
tabu probably needs an update to match the latest array, but you can force the use of the old array by using the new [=... optional argument to usepackage.
documentclass{article}
usepackage{array}[=2016-10-06]
usepackage{tabu}
begin{document}
tabulinesep=3pt
Result using tabu:
begin{tabu} to linewidth {|X[p]| X[m]| X[b]|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabu}
vspace*{1cm}
Result using tabular:
begin{tabular}{|p{0.3linewidth}|m{0.3linewidth}|b{0.3linewidth}|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabular}
end{document}
answered May 10 '18 at 13:51
David CarlisleDavid Carlisle
486k4111231867
I have no idea what tabu should do to correct the problem, but the cause is that array now uses vbox instead of vcenter for the m-column and as tabu tests forcurrentgrouptypeit doesn't get 12 but 4 and so takes the wrong path.
– Ulrike Fischer
May 10 '18 at 14:44
Thanks for the quick help. I didn't expect such a fast answer :). I found out that the problem persists if the usepackage{siunitx} is loaded before. usepackage{array}[=2016-10-06] should be loaded first to avoid any problems. Thank you!
– Micha
May 10 '18 at 20:18
1
@Micha I have mailed the tabu author pointing out this incompatibility, so hopefully he'll update to match the latestarray.
– David Carlisle
May 11 '18 at 22:14
@DavidCarlisle Don't hold your breath.
– cfr
Jun 14 '18 at 0:56
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f430973%2ftabu-m-column-vertical-alignment-not-working-after-package-updates%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
6
UPDATE 2019-01-14
A workaround for this issuse has been included in tabu 2.9 which has been submitted to ctan.
tabu probably needs an update to match the latest array, but you can force the use of the old array by using the new [=... optional argument to usepackage.
documentclass{article}
usepackage{array}[=2016-10-06]
usepackage{tabu}
begin{document}
tabulinesep=3pt
Result using tabu:
begin{tabu} to linewidth {|X[p]| X[m]| X[b]|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabu}
vspace*{1cm}
Result using tabular:
begin{tabular}{|p{0.3linewidth}|m{0.3linewidth}|b{0.3linewidth}|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabular}
end{document}
answered May 10 '18 at 13:51
David CarlisleDavid Carlisle
486k4111231867
I have no idea what tabu should do to correct the problem, but the cause is that array now uses vbox instead of vcenter for the m-column and as tabu tests forcurrentgrouptypeit doesn't get 12 but 4 and so takes the wrong path.
– Ulrike Fischer
May 10 '18 at 14:44
Thanks for the quick help. I didn't expect such a fast answer :). I found out that the problem persists if the usepackage{siunitx} is loaded before. usepackage{array}[=2016-10-06] should be loaded first to avoid any problems. Thank you!
– Micha
May 10 '18 at 20:18
1
@Micha I have mailed the tabu author pointing out this incompatibility, so hopefully he'll update to match the latestarray.
– David Carlisle
May 11 '18 at 22:14
@DavidCarlisle Don't hold your breath.
– cfr
Jun 14 '18 at 0:56
add a comment |
6
UPDATE 2019-01-14
A workaround for this issuse has been included in tabu 2.9 which has been submitted to ctan.
tabu probably needs an update to match the latest array, but you can force the use of the old array by using the new [=... optional argument to usepackage.
documentclass{article}
usepackage{array}[=2016-10-06]
usepackage{tabu}
begin{document}
tabulinesep=3pt
Result using tabu:
begin{tabu} to linewidth {|X[p]| X[m]| X[b]|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabu}
vspace*{1cm}
Result using tabular:
begin{tabular}{|p{0.3linewidth}|m{0.3linewidth}|b{0.3linewidth}|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabular}
end{document}
answered May 10 '18 at 13:51
David CarlisleDavid Carlisle
486k4111231867
I have no idea what tabu should do to correct the problem, but the cause is that array now uses vbox instead of vcenter for the m-column and as tabu tests forcurrentgrouptypeit doesn't get 12 but 4 and so takes the wrong path.
– Ulrike Fischer
May 10 '18 at 14:44
Thanks for the quick help. I didn't expect such a fast answer :). I found out that the problem persists if the usepackage{siunitx} is loaded before. usepackage{array}[=2016-10-06] should be loaded first to avoid any problems. Thank you!
– Micha
May 10 '18 at 20:18
1
@Micha I have mailed the tabu author pointing out this incompatibility, so hopefully he'll update to match the latestarray.
– David Carlisle
May 11 '18 at 22:14
@DavidCarlisle Don't hold your breath.
– cfr
Jun 14 '18 at 0:56
add a comment |
6
6
6
UPDATE 2019-01-14
A workaround for this issuse has been included in tabu 2.9 which has been submitted to ctan.
tabu probably needs an update to match the latest array, but you can force the use of the old array by using the new [=... optional argument to usepackage.
documentclass{article}
usepackage{array}[=2016-10-06]
usepackage{tabu}
begin{document}
tabulinesep=3pt
Result using tabu:
begin{tabu} to linewidth {|X[p]| X[m]| X[b]|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabu}
vspace*{1cm}
Result using tabular:
begin{tabular}{|p{0.3linewidth}|m{0.3linewidth}|b{0.3linewidth}|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabular}
end{document}
answered May 10 '18 at 13:51
David CarlisleDavid Carlisle
486k4111231867
UPDATE 2019-01-14
A workaround for this issuse has been included in tabu 2.9 which has been submitted to ctan.
tabu probably needs an update to match the latest array, but you can force the use of the old array by using the new [=... optional argument to usepackage.
documentclass{article}
usepackage{array}[=2016-10-06]
usepackage{tabu}
begin{document}
tabulinesep=3pt
Result using tabu:
begin{tabu} to linewidth {|X[p]| X[m]| X[b]|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabu}
vspace*{1cm}
Result using tabular:
begin{tabular}{|p{0.3linewidth}|m{0.3linewidth}|b{0.3linewidth}|}
hline
centering header p &
centering header m &
centering header b tabularnewline
hline
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column &
text which is considerably longer than the width of the column
tabularnewline
hline
end{tabular}
end{document}
answered May 10 '18 at 13:51
David CarlisleDavid Carlisle
486k4111231867
edited Jan 14 at 20:39
answered May 10 '18 at 13:51
David CarlisleDavid Carlisle
486k4111231867
answered May 10 '18 at 13:51
David CarlisleDavid Carlisle
486k4111231867
answered May 10 '18 at 13:51
David CarlisleDavid Carlisle
486k4111231867
486k4111231867
I have no idea what tabu should do to correct the problem, but the cause is that array now uses vbox instead of vcenter for the m-column and as tabu tests forcurrentgrouptypeit doesn't get 12 but 4 and so takes the wrong path.
– Ulrike Fischer
May 10 '18 at 14:44
Thanks for the quick help. I didn't expect such a fast answer :). I found out that the problem persists if the usepackage{siunitx} is loaded before. usepackage{array}[=2016-10-06] should be loaded first to avoid any problems. Thank you!
– Micha
May 10 '18 at 20:18
1
@Micha I have mailed the tabu author pointing out this incompatibility, so hopefully he'll update to match the latestarray.
– David Carlisle
May 11 '18 at 22:14
@DavidCarlisle Don't hold your breath.
– cfr
Jun 14 '18 at 0:56
add a comment |
I have no idea what tabu should do to correct the problem, but the cause is that array now uses vbox instead of vcenter for the m-column and as tabu tests forcurrentgrouptypeit doesn't get 12 but 4 and so takes the wrong path.
– Ulrike Fischer
May 10 '18 at 14:44
Thanks for the quick help. I didn't expect such a fast answer :). I found out that the problem persists if the usepackage{siunitx} is loaded before. usepackage{array}[=2016-10-06] should be loaded first to avoid any problems. Thank you!
– Micha
May 10 '18 at 20:18
1
@Micha I have mailed the tabu author pointing out this incompatibility, so hopefully he'll update to match the latestarray.
– David Carlisle
May 11 '18 at 22:14
@DavidCarlisle Don't hold your breath.
– cfr
Jun 14 '18 at 0:56
I have no idea what tabu should do to correct the problem, but the cause is that array now uses vbox instead of vcenter for the m-column and as tabu tests for
currentgrouptype it doesn't get 12 but 4 and so takes the wrong path.– Ulrike Fischer
May 10 '18 at 14:44
I have no idea what tabu should do to correct the problem, but the cause is that array now uses vbox instead of vcenter for the m-column and as tabu tests for
currentgrouptype it doesn't get 12 but 4 and so takes the wrong path.– Ulrike Fischer
May 10 '18 at 14:44
Thanks for the quick help. I didn't expect such a fast answer :). I found out that the problem persists if the usepackage{siunitx} is loaded before. usepackage{array}[=2016-10-06] should be loaded first to avoid any problems. Thank you!
– Micha
May 10 '18 at 20:18
Thanks for the quick help. I didn't expect such a fast answer :). I found out that the problem persists if the usepackage{siunitx} is loaded before. usepackage{array}[=2016-10-06] should be loaded first to avoid any problems. Thank you!
– Micha
May 10 '18 at 20:18
1
1
@Micha I have mailed the tabu author pointing out this incompatibility, so hopefully he'll update to match the latest
array.– David Carlisle
May 11 '18 at 22:14
@Micha I have mailed the tabu author pointing out this incompatibility, so hopefully he'll update to match the latest
array.– David Carlisle
May 11 '18 at 22:14
@DavidCarlisle Don't hold your breath.
– cfr
Jun 14 '18 at 0:56
@DavidCarlisle Don't hold your breath.
– cfr
Jun 14 '18 at 0:56
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f430973%2ftabu-m-column-vertical-alignment-not-working-after-package-updates%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Welcome to TeX.SX! Just to mention it: TL2018 (fully updated) is also affected.
– TeXnician
May 10 '18 at 13:45
In my case I never use the
tabupackage alone, since it needs thelongtable,tabularx,arrayandmultirrowpackages, if I compile your code with my normal configuration I have no problems, I get the same as with the tabular environment, you should know that tabu is not a self-contained package, it is a set of macros that other table libraries use to create beautiful tables ....– J Leon V.
May 10 '18 at 15:16
@JLeonV. do you have the 2018-04-01 latex release?
– David Carlisle
May 10 '18 at 16:35
@DavidCarlisle, it's an honor to answer you... Yes, LaTeX2e <2018-04-01> patch level 3, And I compile with pdfTeX, Version 3.14159265-2.6-1.40.19 (MiKTeX 2.9.6670 64-bit)
– J Leon V.
May 10 '18 at 20:11
@JLeonV. it shouldn't work I think, can you check you have array.sty
2018/04/30 v2.4h– David Carlisle
May 10 '18 at 20:24