You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
2Please post a complete minimal working example, Your code uses nonstandard commands and column specifiers and it's hard to figure out how they're defined or what packages they come from, so I can't test your code.– frabjousCommented May 19, 2022 at 18:04
-
1You added some packages. That's a good first step. But that's not all of them, as the rotating package is not there, and we still don't know how you're defining those custom column specifiers. Your code needs to be a complete document that compiles as is and shows the problem. Please test before posting.– frabjousCommented May 19, 2022 at 18:13
-
@frabjous Thank you for your feedback and I'm very sorry for the confusing/unclear question. I think that it might be a package in the preamble that hinders the correct referencing of my table in the text because I tested the code above with the rotating packaging and it worked fine. Unfortunately, I have so many /usepackages in my preamble that I'll probably have to go one by one until I find out the one that I have to remove. Sorry for wasting your time.– TFTCommented May 19, 2022 at 18:20
-
2Sounds like you're going about it the right way. If you figure out which package it is, and you still can't figure out why, do update your question.– frabjousCommented May 19, 2022 at 18:24
-
@frabjous I've just found out that the problem was caused by \usepackage{subfig}. After removing it from the preamble, the table cross-referencing works perfectly. I'm wondering if there is a better general approach to quickly check which code in the preamble might be the cause for compiling issues ...– TFTCommented May 19, 2022 at 18:33
|
Show 1 more comment
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. tikz-pgf), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-tex