![]() ![]() It seems that there is a threshold thickness of 2px where Chrome PDF Viewer starts giving inconsistent results on table borders. This article was the one that pointed me to the possibility that it was the fine-line renderer. ![]() This works, but this was an unusable option for me since our server was processing PDFs via PhantomJS and modification to how Chrome operated within it would have unknown effects on other custom PDF solutions we were offering. Most sources say to disable Chrome PDF Viewer so that it can fall back to Adobe Reader. This has been an issue for several years, which is compounded by the fact that Chrome PDF Viewer has had issues rendering table borders since at least 2011. Do the borders show back up? If so, then your issue is with how Chrome PDF viewer handles fine line rendering. Here are the key details: When earlier versions ran on Mojave, several tools in the Source and Preview toolbars were missing. As I said in my first message, the same source uses in different LaTeX classes produced different results: the article document had no problems, the. What still bugs me though (well, sort of), is that the phenomenon is so unpredictable. The main purpose of the release is to x TeXShop bugs when running on Mojave, and to support Dark Mode there. Printing through Preview turned up the same problems as printing through TexShop. ![]() How thick are you setting the borders? Download the PDF, open it in chrome, and then zoom in to around 400%. TeXShop Changes 4.08 This version of TeXShop works on Yosemite and above, but has been compiled on Mojave. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |