-
Notifications
You must be signed in to change notification settings - Fork 6
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
Gap between column titles and table body in LibreOffice Writer #7
Comments
Hi @kpl05. Interesting observation. Our primary target has been making sure things render correctly within Microsoft Word, as in the pharma industry, these RTF documents often get handed off to medical writers who use Microsoft Word to assemble their reports. And even though word reads and writes RTF code, it still converts it to its own flavor in the background. It would help if you provide a screenshot of the gap you're seeing and an example file. I'm curious if the gap is something coming from the huxtable table output or something being done by pharmaRTF. |
Hi Mike, Here is the LibreOffice screenshot as requested: Unfortunately, Github does not seem to let me attach RTF files unless there is another way to do this so I have added a PDF file to show things in more detail. Regards, John |
Hi Mike, Just trying a DOCX file made in LibreOffice to see if that helps in any way because that retains the gap. Regards, John |
Thanks - one more question, can you provide the code you used? Or create a reprex? That will help us out as well. |
Hi Mike, Here is some of the code that was used: c19v_latest %>% A REPREX may take longer so I hope the above helps to add clarity. Regards, John |
Hi,
Thanks for creating this. One thing that I have noticed is that the generated RTF files look different in LibreOffice Writer compared to how they look in Microsoft Word. In LibreOffice, there is an extra gap between the column heading and the table body that is not present in Word. While it looks as if things are being rendered differently, it this something that can be addressed?
Many thanks,
John
The text was updated successfully, but these errors were encountered: