You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be nice if a closeread doc could "fail gracefully" when rendered to a different format like pdf or html. Right now it does so fairly well with the exception of the @cr-mysticky which remain visible in the narrative blocks after rendering. A few options:
Appeal to Quarto devs to add cr- as a protected prefix. Then we could have Quarto scrub them.
Switch closeread to a filter that could be run even on different formats. When run on those formats, all it'd run is a trigger scrubber.
Add options to closeread-html to also produce an alternate (non-scrolly) format.
The text was updated successfully, but these errors were encountered:
Haha, I was trying to remember why we decided to hold off on the filter for now and ... I really couldn't remember our rationale for sticking with a format for the time being!
It'd be nice if a closeread doc could "fail gracefully" when rendered to a different format like pdf or html. Right now it does so fairly well with the exception of the
@cr-mysticky
which remain visible in the narrative blocks after rendering. A few options:cr-
as a protected prefix. Then we could have Quarto scrub them.closeread-html
to also produce an alternate (non-scrolly) format.The text was updated successfully, but these errors were encountered: