-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
table caption style in yaml not used #112
Comments
addition: it is not specifically a problem in the yaml as using
gives the same result |
Hello, This isnt a complete answer to your query but I modified your code a bit for it to be reproducible for others who may want to troubleshoot.
Secondly, I have uploaded a template that I have been working on here. Based on the little I know you need to call the "style_name" in the YAML where the "style_type" is "table". In your example you have the following in your YAML
but if you look at the styles info If you look at the
|
Hi Jesse, I'm encountering the same issue. Have you found a solution? |
No, I never did. I use a simple workaround to style the table that I don't really mind using, so I stopped trying to get it to work.
Table caption styles sort of work out of the box but seem always to get centered, I don't know why, maybe I'm overlooking something, but I use the following ugly hack for that:
where "Tabeltitel" is a style defined in my word file. I feel I must add that overall I think the package is fantastic and I know of no other way for getting acceptable word output, so I gladly live with or work around these small flaws. |
I have an rmarkdown document:
It is using the default style reference_docs in your package and specifies to use the style 'caption' for tables and plots. However the captions tyles seem different on output and I think only the plot caption has the correct formatting.
It could be that I'm mistaken on how to specify the style or what the style actually does, if so: please enlighten me! And many thanks for making this package.
session info:
The text was updated successfully, but these errors were encountered: