table* not visible in articlenewline not working with booktabs?Libertine/Biolinum suddenly...
Does an object always see its latest internal state irrespective of thread?
How does quantile regression compare to logistic regression with the variable split at the quantile?
How much RAM could one put in a typical 80386 setup?
Paid for article while in US on F-1 visa?
RSA: Danger of using p to create q
How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?
LWC SFDX source push error TypeError: LWC1009: decl.moveTo is not a function
Why is 150k or 200k jobs considered good when there's 300k+ births a month?
Maximum likelihood parameters deviate from posterior distributions
Why can't we play rap on piano?
How can bays and straits be determined in a procedurally generated map?
What's the output of a record needle playing an out-of-speed record
LaTeX: Why are digits allowed in environments, but forbidden in commands?
Which country benefited the most from UN Security Council vetoes?
Does detail obscure or enhance action?
I'm flying to France today and my passport expires in less than 2 months
Accidentally leaked the solution to an assignment, what to do now? (I'm the prof)
Is it legal for company to use my work email to pretend I still work there?
Revoked SSL certificate
What's that red-plus icon near a text?
Theorems that impeded progress
Today is the Center
Why does Kotter return in Welcome Back Kotter?
Watching something be written to a file live with tail
table* not visible in article
newline not working with booktabs?Libertine/Biolinum suddenly missing/corrupted?Nested itemize in a table columnBibliography in LaTeX with Biblatex and Biber as backendpdflatex.exe - .synctex not written properlyXeLaTex - fontawesome: compiles without errors, but doesn't show symbolsExtra pages generated by afterpagepsfrag in combination with epstopdf not working (MikTeX)Table with many rows causes errors with acronymspgf package + pstricks | MikTeX | still 'broken'
I have run into a really weird issue. Consider the following MWE:
documentclass{article}
usepackage{here}
begin{document}
Test
begin{table*}[H]
begin{tabular}{ll}
A & B\
end{tabular}
end{table*}
Test
end{document}
The output document with pdfLaTeX has no table in it. There are no warnings and no errors. I tried multiple online editors as well, but without any luck - the table remains invisible and does not even consume any space. If I replace the table*
environment by a table
environment, it works fine.
Background: I used a table*
like this one in a document that I update each year since at least 2014. Only this year it stopped working after an update of my local MikTeX setup. I cannot pinpoint the exact version, but it worked on multiple MikTeX installations across multiple machines in the past. I do not understand why it stopped working. I suspect that it might have to do with the here
package.
Question: Is this a bug or - if not - why did it work previously and why am I not seeing any warnings or errors? Note: I'll happily use table
instead of table*
for now, but I want to avoid missing content/tables in my documents.
tables pdftex miktex
|
show 1 more comment
I have run into a really weird issue. Consider the following MWE:
documentclass{article}
usepackage{here}
begin{document}
Test
begin{table*}[H]
begin{tabular}{ll}
A & B\
end{tabular}
end{table*}
Test
end{document}
The output document with pdfLaTeX has no table in it. There are no warnings and no errors. I tried multiple online editors as well, but without any luck - the table remains invisible and does not even consume any space. If I replace the table*
environment by a table
environment, it works fine.
Background: I used a table*
like this one in a document that I update each year since at least 2014. Only this year it stopped working after an update of my local MikTeX setup. I cannot pinpoint the exact version, but it worked on multiple MikTeX installations across multiple machines in the past. I do not understand why it stopped working. I suspect that it might have to do with the here
package.
Question: Is this a bug or - if not - why did it work previously and why am I not seeing any warnings or errors? Note: I'll happily use table
instead of table*
for now, but I want to avoid missing content/tables in my documents.
tables pdftex miktex
4
[H]
can not be used withtable*
(what would it mean?)
– David Carlisle
8 hours ago
I originally had double-column documents and thought that usingtable*
in a single-column document would not make a difference. It did indeed make no difference in the last few years that I continued usingtable*
s.
– Andreas Unterweger
8 hours ago
Sorry yes I didn't notice originally that it was a single column document, but givenH
can't work whentable*
is being used for two column, it's not that surprising if it doesn't work in single columntable*
. I can't recall if it did in my originalhere
package but that was withdrawn in the 1990'shere
has just been a wrapper that inputs thefloat
package since that time.
– David Carlisle
8 hours ago
@DavidCarlisle: I did not know that. I will look for a better solution if the package is no longer intended to be used. Thank you.
– Andreas Unterweger
7 hours ago
I just tried the supplied file with texlive2016,texlive2017,texlive2018,texlive2019 with same result in all.
– David Carlisle
7 hours ago
|
show 1 more comment
I have run into a really weird issue. Consider the following MWE:
documentclass{article}
usepackage{here}
begin{document}
Test
begin{table*}[H]
begin{tabular}{ll}
A & B\
end{tabular}
end{table*}
Test
end{document}
The output document with pdfLaTeX has no table in it. There are no warnings and no errors. I tried multiple online editors as well, but without any luck - the table remains invisible and does not even consume any space. If I replace the table*
environment by a table
environment, it works fine.
Background: I used a table*
like this one in a document that I update each year since at least 2014. Only this year it stopped working after an update of my local MikTeX setup. I cannot pinpoint the exact version, but it worked on multiple MikTeX installations across multiple machines in the past. I do not understand why it stopped working. I suspect that it might have to do with the here
package.
Question: Is this a bug or - if not - why did it work previously and why am I not seeing any warnings or errors? Note: I'll happily use table
instead of table*
for now, but I want to avoid missing content/tables in my documents.
tables pdftex miktex
I have run into a really weird issue. Consider the following MWE:
documentclass{article}
usepackage{here}
begin{document}
Test
begin{table*}[H]
begin{tabular}{ll}
A & B\
end{tabular}
end{table*}
Test
end{document}
The output document with pdfLaTeX has no table in it. There are no warnings and no errors. I tried multiple online editors as well, but without any luck - the table remains invisible and does not even consume any space. If I replace the table*
environment by a table
environment, it works fine.
Background: I used a table*
like this one in a document that I update each year since at least 2014. Only this year it stopped working after an update of my local MikTeX setup. I cannot pinpoint the exact version, but it worked on multiple MikTeX installations across multiple machines in the past. I do not understand why it stopped working. I suspect that it might have to do with the here
package.
Question: Is this a bug or - if not - why did it work previously and why am I not seeing any warnings or errors? Note: I'll happily use table
instead of table*
for now, but I want to avoid missing content/tables in my documents.
tables pdftex miktex
tables pdftex miktex
asked 8 hours ago
Andreas UnterwegerAndreas Unterweger
23828
23828
4
[H]
can not be used withtable*
(what would it mean?)
– David Carlisle
8 hours ago
I originally had double-column documents and thought that usingtable*
in a single-column document would not make a difference. It did indeed make no difference in the last few years that I continued usingtable*
s.
– Andreas Unterweger
8 hours ago
Sorry yes I didn't notice originally that it was a single column document, but givenH
can't work whentable*
is being used for two column, it's not that surprising if it doesn't work in single columntable*
. I can't recall if it did in my originalhere
package but that was withdrawn in the 1990'shere
has just been a wrapper that inputs thefloat
package since that time.
– David Carlisle
8 hours ago
@DavidCarlisle: I did not know that. I will look for a better solution if the package is no longer intended to be used. Thank you.
– Andreas Unterweger
7 hours ago
I just tried the supplied file with texlive2016,texlive2017,texlive2018,texlive2019 with same result in all.
– David Carlisle
7 hours ago
|
show 1 more comment
4
[H]
can not be used withtable*
(what would it mean?)
– David Carlisle
8 hours ago
I originally had double-column documents and thought that usingtable*
in a single-column document would not make a difference. It did indeed make no difference in the last few years that I continued usingtable*
s.
– Andreas Unterweger
8 hours ago
Sorry yes I didn't notice originally that it was a single column document, but givenH
can't work whentable*
is being used for two column, it's not that surprising if it doesn't work in single columntable*
. I can't recall if it did in my originalhere
package but that was withdrawn in the 1990'shere
has just been a wrapper that inputs thefloat
package since that time.
– David Carlisle
8 hours ago
@DavidCarlisle: I did not know that. I will look for a better solution if the package is no longer intended to be used. Thank you.
– Andreas Unterweger
7 hours ago
I just tried the supplied file with texlive2016,texlive2017,texlive2018,texlive2019 with same result in all.
– David Carlisle
7 hours ago
4
4
[H]
can not be used with table*
(what would it mean?)– David Carlisle
8 hours ago
[H]
can not be used with table*
(what would it mean?)– David Carlisle
8 hours ago
I originally had double-column documents and thought that using
table*
in a single-column document would not make a difference. It did indeed make no difference in the last few years that I continued using table*
s.– Andreas Unterweger
8 hours ago
I originally had double-column documents and thought that using
table*
in a single-column document would not make a difference. It did indeed make no difference in the last few years that I continued using table*
s.– Andreas Unterweger
8 hours ago
Sorry yes I didn't notice originally that it was a single column document, but given
H
can't work when table*
is being used for two column, it's not that surprising if it doesn't work in single column table*
. I can't recall if it did in my original here
package but that was withdrawn in the 1990's here
has just been a wrapper that inputs the float
package since that time.– David Carlisle
8 hours ago
Sorry yes I didn't notice originally that it was a single column document, but given
H
can't work when table*
is being used for two column, it's not that surprising if it doesn't work in single column table*
. I can't recall if it did in my original here
package but that was withdrawn in the 1990's here
has just been a wrapper that inputs the float
package since that time.– David Carlisle
8 hours ago
@DavidCarlisle: I did not know that. I will look for a better solution if the package is no longer intended to be used. Thank you.
– Andreas Unterweger
7 hours ago
@DavidCarlisle: I did not know that. I will look for a better solution if the package is no longer intended to be used. Thank you.
– Andreas Unterweger
7 hours ago
I just tried the supplied file with texlive2016,texlive2017,texlive2018,texlive2019 with same result in all.
– David Carlisle
7 hours ago
I just tried the supplied file with texlive2016,texlive2017,texlive2018,texlive2019 with same result in all.
– David Carlisle
7 hours ago
|
show 1 more comment
0
active
oldest
votes
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
});
}
});
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%2f483403%2ftable-not-visible-in-article%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f483403%2ftable-not-visible-in-article%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
4
[H]
can not be used withtable*
(what would it mean?)– David Carlisle
8 hours ago
I originally had double-column documents and thought that using
table*
in a single-column document would not make a difference. It did indeed make no difference in the last few years that I continued usingtable*
s.– Andreas Unterweger
8 hours ago
Sorry yes I didn't notice originally that it was a single column document, but given
H
can't work whentable*
is being used for two column, it's not that surprising if it doesn't work in single columntable*
. I can't recall if it did in my originalhere
package but that was withdrawn in the 1990'shere
has just been a wrapper that inputs thefloat
package since that time.– David Carlisle
8 hours ago
@DavidCarlisle: I did not know that. I will look for a better solution if the package is no longer intended to be used. Thank you.
– Andreas Unterweger
7 hours ago
I just tried the supplied file with texlive2016,texlive2017,texlive2018,texlive2019 with same result in all.
– David Carlisle
7 hours ago